Tony Baker wrote: > Hi ! > > I have recently updated Spamassassin (3.2.3), amavis-new and clamav. > > > Everything seems fine, > then yesterday I replied to an external piece of mail and CC'd a > couple of colleagues on the reply. > > The mail was marked as SPAM > > Part of the headers as follows: >> X-Virus-Scanned: amavisd-new at co.uk >> X-Spam-Flag: YES >> X-Spam-Score: 5.373 >> X-Spam-Level: ***** >> X-Spam-Status: Yes, score=5.373 tagged_above=-999 required=2.7 >> tests=[ALL_TRUSTED=-1.8, AWL=9.772, BAYES_00=-2.599] > > The body of my reply had a lot of pricing included in it eg $30 > > Can someone tell me why has a mail generated internally been marked as > SPAM?
Looks like at some point, your sender address sent something very spammy and drove their average score up to +15 or so... The high postive score of the AWL rule shows that.. This message itself matched no spam rules. It's strictly based on the score-averaging behavior of the AWL.. You might want to try using the check_whitelist script to dump the contents of your AWL, see if your own average is high for some reason. Beyond that, you can use spamassassin --remove-addr-from-whitelist [EMAIL PROTECTED] to delete your own record.. You also should look into why your average was high.. Do you ever get any spam that matches ALL_TRUSTED? This should never happen, but it's possible the trust-path guesser is confused by your mail setup. This could lead to the AWL confusing outside spammers forging your email address with the real you. See http://wiki.apache.org/spamassassin/TrustPath
