>From: Reindl Harald <h.rei...@thelounge.net>
>Sent: Monday, March 20, 2017 6:08 AM
>To: David Jones; SpamAssassin Users ML
>Subject: Re: SpamAssassin score

>Am 20.03.2017 um 11:52 schrieb David Jones:
>>> From: Bernard <bernard+spamassas...@rosset.me>
>>> Sent: Monday, March 20, 2017 5:37 AM
>>> To: SpamAssassin Users ML
>>> Subject: Re: SpamAssassin score
>>
>>> Thanks for that information.
>>> After ~1750 messages having been digested, still no improvement:
>>> 0.000          0          3          0  non-token data: bayes db version
>>> 0.000          0         23          0  non-token data: nspam
>>> 0.000          0       1729          0  non-token data: nham
>>> 0.000          0     123471          0  non-token data: ntokens
>>> 0.000          0 1358530476          0  non-token data: oldest atime
>>> 0.000          0 1489938564          0  non-token data: newest atime
>>> 0.000          0          0          0  non-token data: last journal sync 
>>> atime
>>> 0.000          0          0          0  non-token data: last expiry atime
>>> 0.000          0          0          0  non-token data: last expire atime 
>>> delta
>>> 0.000          0          0          0  non-token data: last expire 
>>> reduction count

>why don't you read what you quote before make assumptions?
>what does the "23" tell you?

> >> 0.000          0         23          0  non-token data: nspam
> >> 0.000          0       1729          0  non-token data: nham

>for me it tells too few sample messages

Sorry.  Honest mistake.  I was looking at that on a small laptop screen.

Even after the OP trains 200 ham, there could still be a problem that
my suggestions below could help the OP or others.  Don't be so
critical.  Just let some of this stuff go without responding.  Others
did and gave good, positive advice to check the SA wiki.

> If you don't see any BAYES_* rule hits make sure the plugin is enabled:
>
> v320.pre:loadplugin Mail::SpamAssassin::Plugin::Bayes
>
> Run a debug lint and check for bayes output:
>
> spamassassin -D --lint 2>&1 | grep -i bayes
>
> You should see a BAYES_ in the test= line near the end.
>
> Another common problem is the Bayes training is done as one user
> while spamassassin is being called by a different user.  This depends on
> how/what is launching SA -- amavis-new, spamd, MailScanner, etc.
>
> You can force the bayes_path in the local.cf to make sure all users
> use the same Bayes DB if you are using a global (not individual) Bayes
    

Reply via email to