Hi all I run a site for more than 2000 mailboxes with Postfix, SA 3.1.8 and procmail. Every user has his own bayes db. Allow_user_rules is deactivated.
I have a number of problems: A number of emails passes spamd unfiltered due to spamd child timeout. Looking at the scantime it often is far more than the 220s that are defined as a timeout value. Some emails have a scantime of more than 900 seconds. Although I use SARE rules I do not blame them because I had this problem already with SA 3.0|1.x. It is possible that this problem is linked to the second problem. I have a timeout on auto_expiry. To address both issues I followed the hints and tipps that already were discussed here not long ago. Yesterday I disabled auto_expiry and now run sa-learn --force-expire --sync manually for those users that are concerned by the expiry problem. I impossibly can run a force-expire job on a daily cron basis for all users. This would simply use up the 24h a day has. Also I have noticed that some users do have 1 to 2 million tokens in the bayes db. A number between 150k to 200k is normal. bayes_expiry_max_db_size default would be 150'000 and I havn't changed this value. What are the possible reasons why auto_expiry wouldn't expire such a huge number of tokens? I do not see a relation to a huge load on the SpamAssassin Servers (I have 2 of them). The timeout problems happen when there is small load (10 out of 20 spamds marked Busy) as well as when there are 45 spamds forked with 35 marked Busy. I wonder if I have to migrate from bayes db per user to a site-wide bayes db. What would change? In particular, these are the error messages: spamd[27428]: child processing timeout at spamd line 1086, <GEN209> line 503. spamd[3692]: bayes: expire_old_tokens: child processing timeout at spamd line 1086, <GEN245> line 56. Thank you very much in advance for any hints. I'd be really grateful. Philipp
