(1) From: Tail Wagging Offers News Letter <[EMAIL PROTECTED]> X-Spam-Score: 5 X-Spam-Level: ***** (5) X-Spam-Flag: NO X-Scanned-By: MIMEDefang 2.28 (www.roaringpenguin.com/mimedefang)
My spam threshold is set to 1.5. This email should have been flagged as spam.
OK, I'm assuming that you have MIMEDefang calling SpamAssassin, rather than running them separately.
When run through MIMEDefang, all SpamAssassin does is report the score, threshold, and rules hit. All these headers are generated by MIMEDefang, and it's MD that's determining the value of X-Spam-Flag.
Check your mimedefang-filter to see if it's checking $hits > 5 instead of $hits >= $req
It sounds to me like you may want to ask about this over on the MIMEDefang list.
Also, you should upgrade to a newer version of MIMEDefang. Older versions only send SA the headers the message came in with, which means that your own server's Received header is not present, and any checks based on Received headers (including DNSBLs) will be missing the "real" info about the server that sent you the message. 2.34 and later will construct a Received header for your own server, so the SA tests will have the correct information. Be sure to search the ChangeLog for "INCOMPATIBILITY" - some functions and defaults have changed.
Kelson Vibber
SpeedGate Communications <www.speed.net>
------------------------------------------------------- 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
