On Wed, 09 Jan 2013 17:14:05 -0500 Ben Johnson wrote: > About five months ago, I experienced a problem that I *thought* I had > resolved, but I am observing similar behavior after retraining the > Bayes database. While the symptoms are similar, the root cause seems > to be different (thankfully). The original problem is documented at > http://spamassassin.1065346.n5.nabble.com/Very-spammy-messages-yield-BAYES-00-1-9-td101167.html > .. > > In any case, I am again seeing SA scores that seem way too low for the > message content in question. My "glue", as it were, is Amavis-New. > > In particular, certain messages that are clearly SPAM are scored > between 0 and 3 when processed via Amavis. However, if I process the > same messages with the "spamassassin" binary, directly, the scores > are much higher and much more in-line with what one would expect. >... > When I process the same message with spamassassin, directly > (spamassassin -t -D < /tmp/msg.txt), the header looks like this: > > ---------------------------------------------------------------------- > X-Spam-Status: Yes, score=7.5 required=5.0 > tests=BAYES_50,MISSING_DATE,MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,NO_HEADERS_MESSAGE,NO_RECEIVED,NO_RELAYS > autolearn=disabled version=3.3.1
This is not better, it indicates that SA didn't recognise it as an email, not that it recognised it as a spam. Whatever /tmp/msg.txt was it wasn't a properly formatted email.
