That's not SpamAssassin declaring the message whitelisted. MailScanner is. A SA whitelist will show up as a rule hit named USER_IN_WHITELIST.
Check the file pointed to by your "Is Definitely Not Spam" configuration in /etc/MailScanner/MailScanner.conf [EMAIL PROTECTED] wrote: > I had my system consisting of Mailscanner Version 4.55.10-3 + postfix+ > ClamAV 0.88.4 + SpamAssassin 3.1.5 working fine until my spam assassin > started treating all the mail as being whitelisted. I have not changed > anything, any configuration at all. > > this is how my mail log looks like > Sep 21 12:59:31 mx1 MailScanner[7021]: New Batch: Scanning 1 messages, > 1917 bytes > Sep 21 12:59:31 mx1 MailScanner[7021]: Spam Checks: Starting > Sep 21 12:59:31 mx1 MailScanner[7021]: Message 11A222200D8.D9718 from > 217.160.173.36 ([EMAIL PROTECTED]) is whitelisted > Sep 21 12:59:31 mx1 MailScanner[7021]: Virus and Content Scanning: Starting > Sep 21 12:59:32 mx1 MailScanner[7021]: Requeue: 11A222200D8.D9718 to > 258942200DB > Sep 21 12:59:32 mx1 postfix/qmgr[6954]: 258942200DB: > from=<[EMAIL PROTECTED]>, size=1467, nrcpt=1 (queue active) > Sep 21 12:59:32 mx1 MailScanner[7021]: Uninfected: Delivered 1 messages > S > > > before it would have been > > Sep 17 04:09:28 mx1 MailScanner[3132]: New Batch: Scanning 1 messages, > 3363 bytes > Sep 17 04:09:28 mx1 MailScanner[3132]: Spam Checks: Starting > Sep 17 04:09:40 mx1 MailScanner[6109]: Message F2A562200F5 from > 63.170.10.91 ([EMAIL PROTECTED]) to beautybase.com is spam, SpamAssassin > (score=11.659, requ > ired 5, BAYES_99, HTML_MESSAGE, SPF_HELO_SOFTFAIL, UPPERCASE_25_50, > URIBL_JP_SURBL, URIBL_SBL) > Sep 17 04:09:45 mx1 MailScanner[6109]: Spam Checks: Found 1 spam messages > Sep 17 04:09:46 mx1 MailScanner[6109]: Spam Actions: message F2A562200F5 > actions are deliver > > > Please help > > > > >
