https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6120
--- Comment #7 from Mark Martinec <[email protected]> 2009-05-26 15:15:23 PST --- > Probably Amavis clobbering long-running processes that exceed your Amavis > timeout of 300 seconds? Wonder if there are any Amavis specific Bayes expiry > settings. An Amavis expert please correct me. :) > There's really no good single way to deal with everyone's setup, so you need > to configure appropriately for how you're doing things. In your case, yeah, > I would disable the auto-expiry and then do the cronjob. Or, change the > Bayes backend to something that expires faster, like SQL. Or both. :) You are both right, thanks to Guenther and Theo. The default timeout for a SpamAssassin call in amavisd is two thirds of the timeout specified in $child_timeout, which is 8 minutes by default. As the caller doesn't know the SA library will be doing an expiry run, there are no special allowances. Theo's advice is best, either switch Bayes database to SQL which autoexpires *much* faster than for example a large Berkeley database (which is what I do at our site), or disable autoexpiry and do it from cron. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
