Be cautious about adding RBLs
Right you are -- I had to revert the two new RBLs less than 12 hrs later.
Before trying any more lists, I figured out a command to let me test them first.
The command below:
- scans /var/log/qpsmtpd/current for all email that was successfully delivered
- looks up the sending IP address using the blocklist specified (b.barracudacentral.org in the sample below)
- for each email that would be blocked by the test blocklist, outputs:
- the spam score assigned by the system
- the 'from' email address
- the 'to' email address(es)
- the dnsbl A result (127.0.0.x)
- the dnsbl TXT result
TESTBL=b.barracudacentral.org
#
grep logging::logterse.*\(queue\) /var/log/qpsmtpd/current \
|awk -v DNSBL=$TESTBL '{split($7,ip,".");print "echo -ne \"" ($15) \
"\tFrom: " gensub("[<>]","","g",$10) \
"\tTo: " gensub("[<>]","","g",$11) \
"\tA: `dig +short " ip[4] "." ip[3] "." ip[2] "." ip[1] "." DNSBL \
"`\tTXT: \" ; echo -e \"`dig +short txt " ip[4] "." ip[3] "." ip[2] "." ip[1] "." DNSBL "`\""}' \
|bash | grep 127\.0 |less -S
Digging a little more, I found that
pyzor wasn't working on my system (apparently it stopped working around the time of the 7.5 update), so I got that working again (
Bug 5973).
I also tried enabling
auto_whitelisting using
config setprop spamassassin UseAutoWhitelist 1, and ran into some issues with that. My notes on how I got that working have been added to
Bug 6130.