dman wrote: d> | whitelist_from *root* d> d> How about d> whitelist_from *root*Cron Daemon*
I think the whitelist checks against the address part, and not the "Real Name" or (Comment Name) parts. So *root* or root* should work here. d> ... d> | OK, yeah, that looks like a good way to go. Maybe extend it to: d> | header CRON X-Cron-Env =~ /\w/ which is even less likely to be present d> | in a header if not a real cron message. d> d> Unless a spammer decides to add it just to trigger that rule. Most spammers aren't that sophisticated, nor do many have the ability easily to add arbitrary headers. In any case, I think that's probably a pretty decent rule -- we can set the score to something small but -ve and let the GA figure out a good score for the 2.30 release. C _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
