Hi, My company was used dbmail 2.x about 5 years. But now it's time for an upgrade and we have successfully migrated from version 2.x to 3.1.7 using imapsync. It took a few weeks, but it was not a problem because in transition we used nginx which have switched migrated users to the new dbmail 3.1.7 server.
After the upgrade, we have found over time that dbmail-lmtpd is unstable. In standalone mode, the demon was sometimes unavailable - as described in the release notes. In xinetd mode dbmail-lmtpd processes was not closed after the connection. I tried to make a wrapper script which kills process after 5 minutes, but during this time the connection to the database used by the daemon. So I decided to try to use dbmail-deviler and all was well, except for eating memory dbmail-timsieved, which seems to be solved by rebuilding in our own PPA(we are using ubuntu precise). A few days ago, I attempted to upgrade to version 3.1.8 in hope that the described problems are solved. But found one problem: if sieve processing is enabled, then delivery to user which uses simple rules always leads to freezedbmail-deliver process with 100% CPU. Has anyone encountered a similar problem? How can I try to solve or workaround it? Does it make sense to build git snapshot? If it helps: https://launchpad.net/~dezhin/+archive/dbmail - 3.1.8 PPA, https://launchpad.net/~dezhin/+archive/dbmail-test - 3.1.7 PPA. _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
