-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason R. Mastaler wrote: > Stephen Warren <[EMAIL PROTECTED]> writes: > >> I'm certainly fine with such complete information being sent there >> *but* I *also* want some kind of well-formatted error to be returned >> to the SMTP client *as well* (and some of the text returned to the >> client could be derived from the exception text, although obviously >> the client wouldn't receive the entire stack trace). > > I don't disagree. Let's just figure out how to do it in a manner > that's not going to cause confusing or non-standard behavior for users > as was the case last time we tried to address this.
On this specific point - what should the behavior be? I'm honestly confused *why* the person who reported the problem with the exception handler that I added thought the behavior was incorrect - there *was* a problem, and it was reported as an SMTP error message. 1) Current behavior: Connection gets dropped, not error message information transferred to SMTP client. 2) Behavior I added: Exception is trapped. Information regarding what went wrong is transferred to SMTP client in the error message. I would expect any well written SMTP client to display an error message dialog to the end-user in *both* cases. Most clients seem to hide the specific error details, so I'd guess the error message the user sees would often be the same in both cases (perhaps with a details button so the raw SMTP error message could be displayed in the 2nd case). Now, the problem reporter said (2) above made the end-user think there was a problem with the mail system. Well, If I Recall Correctly, there *was* a problem - the SMTP server behind tmda-ofmipd rejected the message. In that scenario, shouldn't tmda-ofmipd (and also the MUA) report this as a problem to the user? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFVVY9hk3bo0lNTrURAtXEAJ9Zi11qTQEWmYRYgzGra9sIK+qrZwCdEbn0 N/mOBpoXe7JTQPL1FwCBMFg= =Bc/b -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
