-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason R. Mastaler wrote: > Stephen Warren <[EMAIL PROTECTED]> writes: > >> Aha! So, this bug is still there. >> >> I recently made a checkin to solve the dropped-connection issue. >> However, it caused other issues and I reverted it the next release. > > Is it really a "bug" though? Todd is testing with telnet. People > don't send mail with telnet. In practice, every mail client I've ever > used tmda-ofmipd with (except tbird) properly detects when a > connection is dropped, raises a flag for the user, and no mail is > lost.
Well, the issue is that an exception is being thrown inside tmda-ofmipd, and it isn't being caught anywhere in tmda-ofmipd, but instead inside the core Python module (asynchat I think) that tmda-ofmipd uses for implementation. I'd personally classify this as a crash in tmda-ofmipd (even if the process doesn't actually exit) and as such would certainly like to fix it. As Todd mentioned, I believe this behaviour violates the SMTP protocol too - we really should simply return a properly formatted SMTP error code, not just drop the connection. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFVVE5hk3bo0lNTrURAqO2AJwJ7iCTuxeOdIg1b4bPPvWgl0VyqACeK7UI rwcEZp0nFYv1yos0DhhnF0E= =5Kuo -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
