On 18-12-13 11:56, Daniel Schütze wrote: > Having run 3.1.8 overnight I’m afraid I’m still seeing spinning at 100% > cpu load and dbmail 3.1.8 not accepting connections.
I'm sorry to hear that. Fixing the network code is going to take some time, study and careful coding. Until it is fixed I would strongly recommend putting a proxy in front of dbmail's IMAP and POP3 services. The problems in DBMail all revolve around handling broken client connections, as far as I can tell. This is very difficult to test - at least I haven't found the correct way to test it yet. Simply dropping FIN packets has helped solving some of the problems, but apparently not all. Fixing it for good will take some careful refactoring and auditing of the network code. A proxy like nginx has a proven track record in this regard and will handle broken client connections gracefully without disturbing dbmail. You will find example configs and code at: http://git.dbmail.eu/paul/dbmail/tree/contrib/nginx -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, github, linkedin * Premium Hosting Services and Web Application Consultancy * www.nfg.nl/[email protected]/+31.85.877.99.97 ________________________________________________________________ _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
