You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by BQ <b9...@gmail.com> on 2005/05/10 01:28:44 UTC

Poisoned bayes in SQL?

Hi All,

I configured SpamAssassin on a busy server.
It was/is working nicely but I can see lately that a lot of spam is
getting through with BAYES_00 being hit, which leads me to thing that
the Bayes database was poisoned.

So couple of questions for more knowledgable ...

1) I didn't touch any expire settings, so SpamAssassin should auto
expire old entries, correct? As it's SQL, I also don't need any
synchronizing?

2) What's the best thing to do now? Wipe the whole database (what's
the easies way to do that) and start from scratch?


Any other suggestions?

If it's any worth, magic dump is:

[amavis@host amavis]$ sa-learn --dump magic
0.000          0          3          0  non-token data: bayes db version
0.000          0    2132600          0  non-token data: nspam
0.000          0    1769097          0  non-token data: nham
0.000          0     727128          0  non-token data: ntokens
0.000          0 1115615649          0  non-token data: oldest atime
0.000          0 1115681295          0  non-token data: newest atime
0.000          0          0          0  non-token data: last journal sync atime
0.000          0 1115659008          0  non-token data: last expiry atime
0.000          0      43200          0  non-token data: last expire atime delta
0.000          0     370471          0  non-token data: last expire
reduction count



Cheers,

BQ