On 01/20/2014 12:43 PM, Matus UHLAR - fantomas wrote:
On 01/20/2014 11:37 AM, Matus UHLAR - fantomas wrote:
I heave received a ham message, that hit BAYES_50 at the time I
received
it. After feeding to "spamassassin -k" and rechecking it gives
BAYES_99: Unfortunately, feeding message to sa-learn explains it
was not
learntL
On 20.01.14 13:05, Axb wrote:
Try adding token reports to your scanned msgs.
(http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.txt)
_HAMMYTOKENS(N)_ the N most significant hammy tokens (default, 5)
_SPAMMYTOKENS(N)_ the N most significant spammy tokens (default, 5)
report Report _SPAMMYTOKENS(25)_
report Report _HAMMYTOKENS(25)_
That may help you trouble shoot cases like this
I have added:
add_header all tokens-spam _SPAMMYTOKENS(25)_
add_header all tokens-ham _HAMMYTOKENS(25)_
add_header all tokens-sum _TOKENSUMMARY_
the last header says:
X-Spam-tokens-sum: Tokens: new, 0; hammy, 3; neutral, 50; spammy, 97.
there are many spammy tokens that should be considered hammy. Still
wondering why it was BAYES_50 before...
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"To Boot or not to Boot, that's the question." [WD1270 Caviar]
