-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason R. Mastaler wrote:
> Stephen Warren <[EMAIL PROTECTED]> writes:
> 
>> 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.
> 
> Ideally yes, we'd catch every possible error and handle it inside
> tmda-ofmipd.  If we can do that here I'm certainly in support of it.

Here's the confusing thing...

Around 1.1.4-6, I added a catch-all exception handler into the code,
which returned the exception text to the client. (That said, I think I
forgot to add code to dump the exception to the debug log, so I *might*
have broken that functionality during that short period).

Anway, what made me totally OK with removing that code again was that I
found a catch-all exception handler in the asyncore/SMTP code, that
looked like it did *exactly* what my code did - i.e. translate
exceptions into SMTP error codes (and *not*, I believe, drop the
connection). Certainly, in my testing, I was triggering that exception
handler in the core Python module, and hence getting the behavior that
my exception handler implemented.

So, now I'm confused why that core module exception handler isn't
triggering! Perhaps some specific exception types were "handled"
elsewhere in some module, hence the core exception handler isn't being
reached... I guess I need to see if I can reproduce the exception that
Todd is seeing (or see if Todd can) to find out what's really going on!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFVVUfhk3bo0lNTrURAlI2AJ4nMJI2Lk/Y0XGMe9FQhj7ApKNE5gCffgx6
YYl3deaEKvqwI6BxHvxFAOk=
=vUpS
-----END PGP SIGNATURE-----
_____________________________________________
tmda-users mailing list (tmda-users@tmda.net)
http://tmda.net/lists/listinfo/tmda-users

Reply via email to