At 06:21 PM 5/4/04 +0800, . . wrote:
Hi
I am using SA 2.63 with SA-Exim.The score is set to 8.
After running the tests `spamassassin < sample-spam.txt` I see the score that
the particular mail gets increasing first from 500, then to 507 then to 514.
Next, running the test for sample-nonspam.txt, this message gets tagged as spam.See the logs attached.All mail even from root of the server is not tagged highly-17.0 yet before it was tagged 0.0.
This isnt normal and I am wondering if someone has seen this before.If so,please advice on the next course of action.Thanks.

<snip>

2004-05-04 13:17:01 1BKwyz-000E6K-5X SA: Action: silently tossed message: hits=17.2 required=8.0 trigger=9.0 (scanned in 0/0 secs | Message-Id: [EMAIL PROTECTED]). From <[EMAIL PROTECTED]> (local) for [EMAIL PROTECTED]

Any chance you can give us a list of which rules fired? Hard to guess what's going on with just a score.


My guess is you did not merely run sample-spam.txt through SA, but instead actually emailed yourself a copy of it using one of your own accounts. The logs above suggest you're sending emails, not merely piping through SA.

Because of the AWL, SA will remember that the sender of sample-spam.txt sends very high scoring spam. It will penalize all following emails accordingly. Technicaly this is a bug present in both the 2.5x and the 2.6x families of SA, as SA is intended to not use GTUBE in the averaging system. This bug is reportedly fixed in SA 3.0

You can fix this by using spamassassin --remove-addr-from-whitelist [EMAIL PROTECTED] to delete the AWL entries for the account that sent the GTUBE. This will basically reset that user's AWL entirely back to 0/0.

You can read a bit about the AWL and how it works on the wiki:

http://wiki.apache.org/spamassassin/AutoWhitelist



Reply via email to