On 11/3/06, Matt Kettler <[EMAIL PROTECTED]> wrote:
Simon wrote:
> Hi There,
>
> Using spamassassin 3.1.3-0bpo1 from backports.org on debian sarge. We
> did have the standard 3.0.x sarge package. Using amavis-new to call
> spamassassin and after upgrading spamassassin we are now getting these
> messages in the mail.log. Would someone please be able to assist in
> where to go with this one?
Looks like for some reason a SA instance couldn't get a lock on the AWL
database to update it before amavis killed it.
Provided you don't have your bayes or AWL stored on an NFS share, you
might consider switching to lock_method flock. That will speed up
lock/release operations.
However, it's very strange that it timed out locking the AWL.. Normally
SA processes aren't in the AWL very long.
Is your amavis set with an abnormally short timeout for SA?
Hmm.. Where do find this setting in my amavis conf file? These are the
current settings:
$sa_tag_level_deflt = 0.0; # add spam info headers if at, or above that level
$sa_tag2_level_deflt = 4.0; # add 'spam detected' headers at that level
$sa_kill_level_deflt = 5.0; # triggers spam evasive actions
$sa_dsn_cutoff_level = 999; # spam level beyond which a DSN is not sent
$sa_mail_body_size_limit = 200*1024; # don't waste time on SA if mail is larger
$sa_local_tests_only = 0; # only tests which do not require internet access?
$sa_auto_whitelist = 1; # turn on AWL in SA 2.63 or older (irrelevant
# for SA 3.0, cf option is 'use_auto_whitelist')
Thanks!
