tabris wrote: > Any new thoughts?
Not without new data. Try increasing the debug level to see what's going on. trace_syslog=4 should give you enough information. Keep it running at that for a minute or 10 (your timeout being 300) or longer if necessary to generate logs. Select a PID used by a client that is typically piling up connections. Filter out the logs for that PID and look for COMMAND logs. You can also achieve the same result by running tshark on the network interface where dbmail is listening. The idea is to find out if dbmail is causing the problem, or stunnel. netstat and lsof are your friends to scan for open network connections - don't simply trust dbmail-imapd.state. try to match up open connections between stunnel and dbmail with open connections between stunnel and the imap clients. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
