fbpc wrote: > I have whitelisted in my spam.whitelist.rules file: whitelist_from > *...@fbpc.com > The above file is a MailScanner config file not a SpamAssassin config file, it should NOT contain statements of that format. MailScanner's whitelisting options are formatted differently (I don't use them but they're something like "From: *...@example.com").
whitelist_from is a SpamAssassin option, and belongs in a spamassassin file (ie: local.cf), if you want to whitelist at the SpamAssassin level. That said, it looks like you've got MailScanner configured to trust ORDB as a 100% reliable indicator of spam, no matter what SA has to say. Looking at the below, SA whitelisted it (USER_IN_WHITELIST matched, and SA declared a strong negative score), but MailScanner decided it was spam anyway because of ORDB. Be wary of what you put in your spam.lists.conf. Any RBL run there will over-ride all SpamAssassin configuration. Actually, MailScanner will always over-ride anything SA says with what's in its own config files, so that's a general thing. > X-FBPC-MailScanner-SpamCheck: spam, ORDB-RBL, SpamAssassin (not cached, > score=-47.589, required 7, AWL 50.32, BAYES_44 -0.00, > HTML_50_60 0.10, HTML_MESSAGE 0.10, PORN_4 1.89, > USER_IN_WHITELIST -100.00) > X-MailScanner-From: apa...@fbpc.fbpc.com > Status: > > >
