{Spam?} Re: {Spam?} Re: Cannot test spamassassin, what is going on here?

Nagy László Zsolt gandalf at shopzeus.com
Mon Sep 14 08:36:47 UTC 2015


>> But this is wrong, because the email is still identified as ham. But the live server has identified it as spam => still cannot test spamassassin.
> The only test you show is a network test (DNSWL), you have no action on
> the value returned by http://www.dnswl.org/, so it sould have returned
> one result when the live test was run and a different value when you run
> the manual test.
>
> At tmie of the manual test, it seems that the address tested is in the
> white list, hence the message is classified as ham.
>
> As a rule of thumb, the value of network test should be regarded very
> lightly when you run a single message multiple times, because they are
> very likely to change.
Yes, but the test message came from freebsd-questions. Right now I'm 
getting all of the mailing list emails with {Spam?} headers, and I get a 
HAM classification on any of them. Spam requires a score of 5.0 at 
least, and most of the messages I have tested manually scored -5.0. 
Network test might change, but this is definitely not the root of the 
problem.


More information about the freebsd-questions mailing list