That should do it. Just make sure the script is executable by root.
Daily is really quite often enough, but hourly shouldn't be a problem.

Noel Rivera (Border Less) wrote:
Thanks Eric I put the auto expire in my local.cf

And I create and autoexpire.sh in /etc/cron/hourly

When I put autoxpire.sh in /etc/cron.hourly that's all or I have to do
something else to run?



-----Original Message-----
From: news [mailto:[email protected]] On Behalf Of Eric Shubert
Sent: Jueves, 04 de Junio de 2009 10:28 a.m.
To: [email protected]
Subject: Re: [qmailtoaster] another problem

I would use
bayes_auto_expire 0
and install the script below in /etc/cron.daily/. That will keep the auto expire feature from being run during an smtp session and causing a timeout problem.

FWIW, from the spamassassin documentation:
bayes_auto_expire is used to specify whether or not SpamAssassin ought to opportunistically attempt to expire the Bayes database. The default is 1 (yes).

Noel Rivera (Border Less) wrote:
Thanks Eric I put 660 in my spamdyke configuration and here is my local.cf

ok_locales all
skip_rbl_checks 1

required_score 5
report_safe 1
rewrite_header Subject ***SPAM***

use_pyzor 1

use_auto_whitelist 1

use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1

dns_available no
[r...@mailserver spamassassin]# nano local.cf
  GNU nano 1.3.12              File: local.cf

report_safe 1
rewrite_header Subject ***SPAM***

use_pyzor 1

use_auto_whitelist 1

use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1

dns_available no



-----Original Message-----
From: news [mailto:[email protected]] On Behalf Of Eric Shubert
Sent: Jueves, 04 de Junio de 2009 09:10 a.m.
To: [email protected]
Subject: Re: [qmailtoaster] another problem

I use 660. There used to be a bug in the 3.x versions where some rather large (15M or so) emails would time out. I thought it was fixed, but still use 660 just to be safe. ;)

Also, you might want to check to see if you have bayes_auto_expire turned on on /etc/mail/spamassassin/local.cf. That can take over 5 minutes (depending on your cpu) when it kicks in, causing timeouts. Better to handle that in a daily cron job:

#!/bin/sh
# written 11/17/06 by Eric 'shubes' <[email protected]>
# force journal sync and expiration of spamassassin bayes database
#
sa-learn -u vpopmail --force-expire
chown vpopmail:vchkpw /home/vpopmail/.spamassassin/bayes_toks


Hey Jake, does the stock spamassassin-toaster still have this enabled? Might be better to include this cron job in the package instead, and have it turned off.





--
-Eric 'shubes'


---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to