Re: Uncaught Python 2.3.4 Exception

Alfred Ganz wrote:
> ------------------------------------------------------------------------------
> The following envelope sender will cause a Python Exception:
> 	"St0ckAlertbijfc@"@gmail.com
> as follows:
>   IOError: failure delivering message to command "('/usr/sbin/sendmail', 
>     '-i', '-f', 'ganz+confirm', '--', '"St0ckAlertbijfc@"@gmail.com')" 
>     (command "( '/usr/sbin/sendmail', '-i', '-f', 'ganz+confirm', '--', 
>     '"St0ckAlertbijfc@"@gmail.com')" exited 67  ())
> 
> Since this is an attempt for getting a confirmation from a spammer, this 
> particular case isn't very important, and I can well understand that 
> sendmail doesn't like such a sender. However, in a more generic way it
> would be nice, if this could be handled without getting an exception.
> 
> My question is, is there a way to catch such an address before the sendmail 
> call fails, such that it could be reported in a better way than in the debug 
> log, which in my understanding is supposed to report things that are poorly 
> configured.

I don't think TMDA can (or should) attempt to predict if the sendmail 
command is going to fail.

As such, I would clasify this as expected behaviour.

You could try using contrib/smtp-check-sender to filter out bad sender 
addresses earlier, but be sure you understand how it works first.

-- 
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
[email protected]     http://www.wwwdotorg.org/pgp.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFD9OvPhk3bo0lNTrURAipqAJ9/TVmOLshUgURlUNE2NGTn0rp4/wCeOjiu
HNngTvNtLAnbr2sNIa1xgXA=
=GSQc
-----END PGP SIGNATURE-----