On 1/10/2014 2:28 AM, Henrik K wrote:
On Thu, Jan 09, 2014 at 08:14:20PM -0700, Amir 'CG' Caspi wrote:
What's the way that I can inject the bayes-identified tokens (hammy or
spammy) into my SA headers, so that I can try to debug what's causing this
problem?
Manual debug:
spamassassin -t -D bayes < message | grep bayes:
(of course it's not 100% same at the time of message receival since it's
already learned, but near)
You can also try adding this to your local.cf or user_prefs:
add_header all Bayes bayes=_BAYES_,
N=_BAYESTC_(_BAYESTCLEARNED_-_BAYESTCHAMMY_+_BAYESTCSPAMMY_),
ham=(_HAMMYTOKENS(5,short)_), spam=(_SPAMMYTOKENS(5,short)_)
(this should be all one line)
This will give you a header with some basic bayes stats including the
top five ham and spam tokens for each message.
--
Bowie
