On 08/20/2014 04:35 PM, redtailjason wrote:
Thank you for your response! Our Bayes is MySQL. Currently, the expiry runs
via cron job to run during low volume times.
Here is the dump from one of the scanners:
netset: cannot include 127.0.0.1/32 as it has already been included
0.000 0 3 0 non-token data: bayes db version
0.000 0 613 0 non-token data: nspam
0.000 0 0 0 non-token data: nham
0.000 0 50382 0 non-token data: ntokens
0.000 0 1362372138 0 non-token data: oldest atime
0.000 0 1396547409 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
Please let me know if you need additional information.
is that really your production bayes DB? So little data?
> 0.000 0 613 0 non-token data: nspam
> 0.000 0 0 0 non-token data: nham
pls post the output of
spamassassin --lint -D bayes
and make sure you do this under the same user which is used by SA
