On Wednesday 24 January 2007 21:29, Chris Purves wrote: > I was wondering what is the best way to deal with spam that comes > through on mailing lists? For mailing lists like spamassassin I > whitelist all mail because I expect to see examples of spam, but for > other lists, is it a good idea to run 'sa-learn --spam'? What about > reporting those spam to razor/pyzor or spamcop?
Check what header fields the mailing list software adds, and exclude them from
bayes with bayes_ignore_header if they aren't already on the built-in ignore
list. Most are covered, but I've found some that are not (at least
Resent-Sender and Resent-Message-ID from Debian's list server). If the list
server filters out spam well, the prevalence of ham means that everything
added by the list software will be seen as a ham sign.
Add the mailing list server to trusted_networks and even internal_networks,
provided that you believe it not to be accessible to spammers. In practise it
acts like an MX that receives mail addressed (indirectly) to you and forwards
it to you. Putting it in internal_networks means that some DNSBL rules will
work better.
--
Magnus Holmgren [EMAIL PROTECTED]
(No Cc of list mail needed, thanks)
"Exim is better at being younger, whereas sendmail is better for
Scrabble (50 point bonus for clearing your rack)" -- Dave Evans
pgpzXaHt6Ho8I.pgp
Description: PGP signature
