On Sat, 3 Mar 2007, John Andersen wrote:
On Saturday 03 March 2007, Chris wrote:
The above line in my local.cf on version 3.1.7 produced
X-Spam-Status: Yes, score=48.6 required=5.0tests=AWL=1.313,BAYES_99=5,
????????BOTNET=5,DCC_CHECK=2.17,DIGEST_MULTIPLE=0.765,FM_MULTI_ODD2=1.1,
????????
This has quit working for 3.1.8 and only produces this output
-Spam-Status: Yes, score=56.8 required=5.0 tests=BAYES_95,BOTNET,CLAMAV,
????????DATE_IN_FUTURE_03_06,DIGEST_MULTIPLE,DNS_FROM_RFC_ABUSE,HELO_DYNAMI
C_IPADDR2,
I've cut it down by a few lines. I've checked and don't see where I needed
to make any changes between the two versions to get the same output. Is
there any reason why the actual rule scores stopped being in the output?
In local.cf change something like this:
add_header all .... tests=_TESTS_ .....
to something like:
add_header all .... tests=_TESTSSCORES .....
per
http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html#template_tags
Per the docs, there is a trailing underscore. I.e.:
add_header all .... tests=_TESTSSCORES_ .....
I can vouch the same thing is happening here. I just made the switch over
to bayes filtering at the user level and made the same header changes. The
tests are displayed without scores for the _TESTSSCORES_ template tag.
Both servers here tested with 3.1.8. Both servers only have ONE
spamassassin installed. Both servers are using spamd/spamc combo.
However, if I use the spamassassin to verify the results, the scores are
in fact within the header. I.e.:
spamassassin -t < testmessage.msg > testmessage.out
testmessage.out does in fact have the correct results.
It appears something within spamd/spamc is causing the incorrect results.
