You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Kai Schaetzl <ma...@conactive.com> on 2008/10/22 18:33:54 UTC
Re: Really force a Bayes expire
Graham Murray wrote on Fri, 29 Aug 2008 19:42:34 +0100:
> As does the 'normal' Bayes expiry mechanism of triggering (or
> attempting) an expire when the number of tokens reaches the threshold.
coming back to this old thread. Unfortunately, the expiry uses the same
algorithm for all Bayes storage engines. So, if it fails on dbm it also
fails on SQL. I may have misunderstood that, but my understanding from the
postings on this list over the past few years was that the expiry
algorithm for the SQL store would be more "intelligent" and thus succeed
where it doesn't succeed on dbm. That's definitely not true. It's the same
and fails the same ;-)
After conversion I had to extract the latest records up to the number I
wanted to keep into a new table, replace the old table bayes_token with
it, flush bayes_seen and adjust bayes_vars accordingly. As I'm now way
under my normal expiry limit I don't know if the normal expiry will work
now, but I hope it. If not, it's definitely easier to "manually" expire
the Bayes database once it's in SQL.
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com