This due to a VERY well known scoring issue in versions 2.50-2.53.. In these versions several rules, including MSGID_GOOD_EXCHANGE and REFERENCES, had very large negative scores, resulting in the effective whitelisting of messages.
This is the very infamous bug 1589, the full details of which are outlined in bugzilla:
http://bugzilla.spamassassin.org/show_bug.cgi?id=1589
As a result of this bug 2.50 through 2.53 should NOT be used for production purposes unless you don't mind lots of false negatives.
At 09:21 AM 7/31/2003 -0700, John Schneider wrote:
I received a spam email this morning that looks like it scored high enough to be tagged spam but was not.
Here is the header info/score analysis:
X-Spam-Status: No, hits=-17.6 required=5.0 tests=BASE64_ENC_TEXT,DCC_CHECK,EMAIL_ATTRIBUTION,HTML_40_50, HTML_FONT_BIG,HTML_FONT_COLOR_RED,HTML_FONT_FACE_ODD, HTML_WITH_BGCOLOR,HTTP_ESCAPED_HOST,HTTP_EXCESSIVE_ESCAPES, IN_REP_TO,MIME_HTML_ONLY,MIME_MISSING_BOUNDARY, MSGID_GOOD_EXCHANGE,REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
