X-MailScanner-SpamCheck: spam, SpamAssassin (score=7.4, required 6, AWL 0.00, BAYES_30 -0.93, HTML_40_50 0.74, HTML_FONT_COLOR_BLUE 0.10, MIME_HTML_ONLY 0.10)
I'd try running it through command-line SA with the AWL on. I suspect that MailScanner isn't reporting the correct score for the AWL, because it's not a static score. I'd have to look at the MS code, but I think it tries to find out the rule scores after the mail is processed. And of course, by then, the answer to "what is the score of the rule AWL?" is "there is no score. 0".
That said, read the mailscanner mailing list archives for my lengthy explanation why you almost NEVER want to use the AWL with mailscanner. (hint: the AWL really only works properly if each user has a separate AWL database. If you have all mail run against a single AWL database like mailscanner does, you get strange score-smearing effects. The use of all_spam_to statements causes severe problems with this, even if the message isn't delivered as a single multi-recipient message it will have a persistent huge negative score in the AWL database)
------------------------------------------------------- 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
