Gary Funck writes: > I noticed the same thing. Seems like this can be a bit of problem for > those of us who would like to collect spam (and mis-classified ham) that > that is later fed to sa-learn, or that is used to calibrate local scores > via mass check. It is my understanding that the Bayes scoring, and > various rules process the header and look at the data in the received > lines. They can't do this if the Received headers aren't there. Worse, > Spamassassin will appear to be a word that often shows up in spam > (because of the string "with SpamAssassin (2.55 > 1.174.2.19-2003-05-19-exp)" that appears in the rewritten Received > headers. This seems like a potential rather serious bug.
That's the SpamAssassin markup, encapsulating the spam mail. To quote the sa-learn doco: Messages learnt as spam will have SpamAssassin markup removed, on the fly. I've just created a new Bayes section in the FAQ for this, and related questions. --j. ------------------------------------------------------- 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
