Hi.
I tried to migrate ~/.spamassassin to a new system but that failed.
I had to remove auto_whitelist and bayes_*.
Then I retrained the bayesian learner with sa-learn --ham and --spam
and now I get:
bayes: expire_old_tokens: child processing timeout at /usr/sbin/spamd line
1085
After googling
Sure. Run it as often as needed. It may block bayes access while it is
running, so if you have a really busy system (and it sounds like you do) you
want to run it often enough to keep the processing time for each shot down
to something reasonable.
Strange thing is that its not a very busy syst
Is it reasonable to set up a cron job that will run "sa-learn" more
frequently than every 24 hours (eg 6 hourly), or is there another
solution to this (short of upgrading my ancient hardware)?
Sure. Run it as often as needed. It may block bayes access while it is
running, so if you have a rea
s: expire_old_tokens: child processing timeout at
/usr/sbin/spamd line 1086.
After a while SA seems to pack up completely and spammy messages stop
getting filtered.
I tried to fix up this by creating a daily cron job that runs the following:
sa-learn --force-expire --sync
I still notice that I am
