> > Sep 20 22:34:18 logger amavis[21071]: (21071-01-16) SA TIMED OUT, > > backtrace: at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/ > > EvalTests.pm line 973
> Nope.. processing the real whitelist, not the AWL, in that trace. > > What's your amavis timeout set for? The default amavisd-new timeout when calling SA is 30 seconds (settable with $sa_timeout). > It may just be too short, as it doesn't > look like SA is hung up, it just looks like it did some bayes DB > maintenance and amavis gave up on it. > > If you've got bayes, I'd suggest at least 120 seconds, if not more, > as a timeout. This is indeed the most common reason. And aborted auto-expiry only means that there will be a next time-consuming attempt soon, which most likely will fail as well. > Either that or disable bayes auto expire in your local.cf and run > expiry manually with a cronjob. Indeed. Or switch Bayes to SQL, where expiry is MUCH faster, and completely avoids this problem. Mark
