Re: Bugs in tmda-ofmipd?

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

Todd A. Jacobs wrote:
> What exactly is the error? Is it something I can code around in an
> expect script, or is it something fundamental?

(I hope you don't mind me CC'ing the mailing list; good for the archives!)

I'm not sure exactly what the error is - I'm hoping you'll be able to
add the exception handler code to tmda-ofmipd and tell us! It's not
something you could code around with expect though; it's internal to the
Python code in tmda-ofmipd.

I added the exception handling code that I mentioned before to trap some
exceptions that tmda-ofmipd was throwing internally - I think in my
case, it was triggered by incorrect syntax in the outgoing filter.
Without the exception handler, tmda-ofmipd would crash and drop the
connection, as you saw.

When I added that code back a month or two ago, it masked other errors,
and somebody complained (see mailing list archives). So, I tested what I
*thought* was the original trigger, and couldn't reproduce the issue.
Also, I looked inside the standard Python modules that tmda-ofmipd uses,
and found that it *looked* like all exceptions would all be handled
gracefully anyway.

So, I removed the exception handler again, after just one release.

Now, it seems that you've found a way to trigger that exception, and I'd
certainly like to see what exception it is, so it can be trapped, and an
SMTP error returned, rather than having tmda-ofmipd crash and close the
connection.

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

iD8DBQFFVVDKhk3bo0lNTrURAnwJAKCkNCQ74goJfcWDAhg0Gc//PIsExQCfcmwR
XyOQf9Xp3C/QrrYDQNj7l80=
=J359
-----END PGP SIGNATURE-----