Simon Byrnand writes: >0.000 0 28070 0 non-token data: nspam >0.000 0 44894 0 non-token data: nham >0.000 0 102780 0 non-token data: ntokens >0.000 0 14341 0 non-token data: oldest age >0.000 0 53621 0 non-token data: current scan-count >0.000 0 52516 0 non-token data: last expiry scan-count > >0.035 0 6 53544 8.11.6 >0.666 23617 18961 53632 H*r:8.11.6p2 >0.011 2 302 53544 8.11.6p2
OK, that's it just there -- when it appears in the Received headers, it emerges as the token "H*r:8.11.6p2" -- ie. "header, Received, "8.11.6p2". When it appears in the *body* though, it doesn't get the special "H*r:" prefix. and that's appeared 302 times in your ham, only twice in spam, therefore it's a hamsign ;) --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/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
