Stew2 wrote:
I'm having trouble with spamd hanging; it seems related to bayes
processing. When this occurs, mail delivery stops until one clears
the bayes data (sa-learn --clear) and restarts exim, which restarts
spamd. All is then well until the system is trained on enough ham and
spam to do bayes evaluations. Then, within a few hours, it will hang
again. Up until the hang, the bayes classification is correct. The
trouble is not related to a specific message; training on only newly
received messages does not help. spamd is running on a VPS account,
invoked as
/usr/bin/spamd -d --allowed-ips=127.0.0.1 --pidfile=/var/run/spamd.pid
--max-children=5
SA updated to version 3.2.0 on May 3, but did not start causing trouble
until early June.
What makes you believe that SA has hung and isn't actually doing
something? Without any indication that SA has actually hung I would
suspect that a bayes auto expiry is taking place. If you prefer, you
could disable bayes_auto_expire and run expiries via a cron job.
There is another minor problem, don't know if it may be related: All
messages are tagged RDNS_NONE. However, forward DNS by SA is working
(blocklist results are correct), and reverse DNS by other processes is
ok (e.g. last shows correct host names). The VPS is also a DNS
server, and /etc/resolv.conf points to its own public IPs. The DNS
server is configured to block external queries from external sources,
but if you query it for a PTR record with dig, nslookup, etc., the
correct results are returned.
It's not related. It's probably being caused by a milter/whatever or
your MTA config. If you provide sample headers and a description of
your setup someone may be able to suggest why it's happening.
Daryl
