SpamAssassin Cache Size?
Fabien Penso
fabienpenso at gmail.com
Sun Sep 17 11:14:25 IST 2006
On 9/15/06, Matt Kettler <mkettler at evi-inc.com> wrote:
(...)
> That's not the SpamAssassin cache (which is a thing MailScanner creates, not
> SA). That's a spamassassin owned file, and is the temp-file being used by SA to
> expire bayes tokens. Those left-over files are caused by MailScanner errantly
> timing-out SA processes during opportunistic bayes expiry.
>
> Fix suggestion:
>
> Simple: Massively extend your timeout for spammassassin in MailScanner.conf
> SpamAssassin Timeout = 600
Hmm might be it, it was setup to "10", far too short I guess. I've
changed it to 100 and I'll see what happens.
> More involved:
> Do the above AND:
> -Disable bayes_auto_expire in /etc/mail/spamassassin/local.cf
> bayes_auto_expire 0
>
> -Create a daily cron-job to run sa-learn --force-expire. Make sure your
> spam.assassin.prefs.conf is linked to a .cf file in /etc/mail/spamassassin/, or
> use the -p option to tell sa-learn to parse your spam.assassin.prefs.conf.
I'll do that if it continues. Thanks for the fix, I feel it'll work fine now.
--
http://penso.info/
More information about the MailScanner
mailing list