Am 18.12.2013 15:36, schrieb Paul J Stevens: > 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.
would packet loss help to debug? in that case i can recommend VMware Workstation there are settings for network-interfaces to set packet-loss in % as well as limit upstream and downstream - if you have a test you want to run against a remote dbmail-server with a bad connection please ping me, i could set packet loss and full debugging for a coordinated timeframe and send you the log
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
