Eric Shubert wrote:
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.
This should be the default local.cf:
# These values can be overridden by editing ~/.spamassassin/user_prefs.cf
# (see spamassassin(1) for details)
# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.
ok_locales all
skip_rbl_checks 1
required_score 5
report_safe 0
rewrite_header Subject ***SPAM***
use_pyzor 1
use_auto_whitelist 1
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1
----------------------------
I've never had an issue with it myself. Out of curiosity, what hardware
do you run?
---------------------------------------------------------------------------------
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]
