SupermanInNY
Verified User
- Joined
- Sep 28, 2004
- Messages
- 425
Hi All,
It is SPAM Season and all the spammers are doing their job properly.
Now it is time for the RBL lists to work too.
I don't think I need to have an Add-on pluggin for basic RBL enablement.
This is a fairly new server (only a month up, so it is current since September 12th, 2006), which has the spamblocker exim file.
I have a soft link from use_rbl_domains -> domains so all my domains are 'covered' under this and they are all happy to get rid of the spam.
However, spam still finds its way through, even though exim.conf should (always use that word when basically have no clue what is going on) be configured to "block" the listed IPs.
OBVIOUSLY,. I'm missing a configuration that actually does the rejection, so I'm looking for some assistance with this configuration.
This is almost vanilla configuration, yet, as noted,. I'm still getting through this even though I see (or believe) the block is enabled.
Specifically I just got an email from: 60.191.227.122
which is listed in the njabl database as a spamming IP.
http://dnsbl.njabl.org/cgi-bin/lookup.cgi?query=60.191.227.122
So, I'm confused about how it made it through the current configuration.
My only thought is that the check is not doing a check against blackholes.njabl.org . Do I need to add this or is this supposed to be implicit in the
# deny using njabl
deny message = Email blocked by NJABL - to unblock see http://www.mydomain.com/spamlistschecker.html
hosts = !+relay_hosts
domains = +use_rbl_domains
!authenticated = *
dnslists = dnsbl.njabl.org
Do I need to add another block like this with just a different dnslist? Like this:
# deny using njabl
deny message = Email blocked by NJABL - to unblock see http://www.mydomain.com/spamlistschecker.html
hosts = !+relay_hosts
domains = +use_rbl_domains
!authenticated = *
dnslists = blackholes.njabl.org
Thanks for any input.
-Alon.
It is SPAM Season and all the spammers are doing their job properly.
Now it is time for the RBL lists to work too.
I don't think I need to have an Add-on pluggin for basic RBL enablement.
This is a fairly new server (only a month up, so it is current since September 12th, 2006), which has the spamblocker exim file.
I have a soft link from use_rbl_domains -> domains so all my domains are 'covered' under this and they are all happy to get rid of the spam.
However, spam still finds its way through, even though exim.conf should (always use that word when basically have no clue what is going on) be configured to "block" the listed IPs.
OBVIOUSLY,. I'm missing a configuration that actually does the rejection, so I'm looking for some assistance with this configuration.
This is almost vanilla configuration, yet, as noted,. I'm still getting through this even though I see (or believe) the block is enabled.
Specifically I just got an email from: 60.191.227.122
which is listed in the njabl database as a spamming IP.
http://dnsbl.njabl.org/cgi-bin/lookup.cgi?query=60.191.227.122
So, I'm confused about how it made it through the current configuration.
My only thought is that the check is not doing a check against blackholes.njabl.org . Do I need to add this or is this supposed to be implicit in the
# deny using njabl
deny message = Email blocked by NJABL - to unblock see http://www.mydomain.com/spamlistschecker.html
hosts = !+relay_hosts
domains = +use_rbl_domains
!authenticated = *
dnslists = dnsbl.njabl.org
Do I need to add another block like this with just a different dnslist? Like this:
# deny using njabl
deny message = Email blocked by NJABL - to unblock see http://www.mydomain.com/spamlistschecker.html
hosts = !+relay_hosts
domains = +use_rbl_domains
!authenticated = *
dnslists = blackholes.njabl.org
Thanks for any input.
-Alon.
Last edited: