Hi folks --
I've searched through the archives and haven't found much on this problem.
I've got DSPAM 3.6.8 running in daemon mode, with virtual users and the
DSPAM database in Mysql 5.0.32, Postfix 2.3.8, delivering with Maildrop
2.0.2.
I've set up the system as described in the DSPAM postfix.txt, DSPAM as a
LMTP server. I'm putting the signatures, and the virtual UIDs into the
message header, filtering SPAM off to each user's Spam folder and using
Dovecot with the dspam-mysql plugin to do retraining based on IMAP copy
operations. Connections to Mysql are through the socket file.
It all works great, works perfectly... until...
Roughly 24 hours after I start the DSPAM daemon, it will simply stop
processing the messages. It stops putting the DSPAM headers in the
messages and from what I can tell, it's not even looking at them because
it is not logging messages in the DSPAM logs. The only thing that gets
logged is the 'unable to initialize tools context' message; killing and
restarting the daemon process fixes the problem. Just this morning I've
enabled debugging on DSPAM to see what gets logged that way.
This is a tiny system compared to the other users seeing this problem
roughly a year ago. I'm only receiving mail for about 20 users, 4
domains, and only have DSPAM enabled for about 5 of those users.
I've seen references to DSPAM not being able to reach Mysql but it looks
like to me that Mysql is fine since Postfix and Dovecot both are still
able to get virtual user info out of it during when DSPAM isn't working.
I've tried:
upping DSPAM 'MySQLConnectionCache' to 25
upping MySQL 'max_connections' to 200
Any suggestions on where to go from here? I suppose I could simply kill
and restart the DSPAM daemon every 18 hours or something, but I'd rather
have a solution rather than a hack.
Thanks for any help!
Rob Klingsten
