Bernd Plagge wrote:
Although pythonfilter and RBL blocking are working fine we sometimes
having customers complaining - not very nicely - about too much spam.
There's lots that you can do to improve spamassassin's performance. Most
notably, make sure the perl's Net::DNS module is installed, so that it
can do RBL tests, and consider increasing the score of some of those
RBLs. Although you may not trust all of them enough to use them to
outright "BLOCK" messages, they can be a good source of data for
spamassassin.
Consider adding pyzor to your system, so that spamassassin can benefit
from its content checks.
Also make sure that you use the sa-update script to refresh your test
definitions periodically.
Spamassassin isn't the best spam filtering software that I've ever used,
but configured properly it can be very good.
There are lines like "New message for x...@y.com" in the log; we could
count them.
Spamassassin issues lines like "Identified spam" ..
Could we have log lines like
"message for x...@y.com rejected by <filter>"
where <filter> would be SPF, blacklist, clamav ??
Yeah, that should be possible. I'll try to patch something up for you to
test in the next day or two. I've been very busy, having recently taken
up a new job.
3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Logging
