My Bayesian filter keeps getting screwed up and causing mail flow to
stop. The problem seems to be expiring tokens out of the database. My
expiry setting is set to 200,000. I've tried many different settings for
this but they all seem to behave about the same. Auto learn is also on.
When this
On 3/9/10 1:24 PM, Curtis MacDuff wrote:
My Bayesian filter keeps getting screwed up and causing mail flow to
stop. The problem seems to be expiring tokens out of the database. My
expiry setting is set to 200,000. I've tried many different settings
for this but they all seem to behave about
On Tue, 09 Mar 2010 10:24:19 -0800
Curtis MacDuff curtis.macd...@pspinc.com wrote:
My Bayesian filter keeps getting screwed up and causing mail flow to
stop. The problem seems to be expiring tokens out of the database. My
expiry setting is set to 200,000. I've tried many different settings
Curtis MacDuff wrote on Tue, 09 Mar 2010 10:24:19 -0800:
My Bayesian filter keeps getting screwed up and causing mail flow to
stop. The problem seems to be expiring tokens out of the database. My
expiry setting is set to 200,000. I've tried many different settings for
this but they all
On Tue, 9 Mar 2010, Curtis MacDuff wrote:
When this happens the mysqld service eats up loads of CPU and stops
responding to requests from Amavisd-new.
Verify your schema, and that you're not missing any indexes.
And, as others have suggested, turn off auto-expiry and expire from a cron
job
I've tried the manual idea with the --force-expire before. Had the same
problem doing it this way, unless its required to stop Amavis during
this process?
You seemed to have hit the nail on the head though with the Sql module bit:
bayes_store_module Mail::SpamAssassin::BayesStore::SQL
On 9.3.2010 20:24, Curtis MacDuff wrote:
My Bayesian filter keeps getting screwed up and causing mail flow to
stop. The problem seems to be expiring tokens out of the database. My
expiry setting is set to 200,000. I've tried many different settings for
this but they all seem to behave about
