Re: Badly formed return address causes TMDA exception

"Todd A. Jacobs" <[email protected]> writes:

> On Sat, May 02, 2009 at 02:05:21PM -0400, Lloyd Zusman wrote:
>
>> Ideally, I'd like to catch the exception in the appropriate place
>> within the TMDA code, because there are a number of ways to send bogus
>> return addresses, and I don't want to try to come up with a pattern
>> that matches every possible form of a bad address.
>
> I responded to your coding question in tmda-workers, but I think there's
> another solution that you might look at: getting your MTA to reject or
> rewrite invalid addresses. Postfix can do this, I think; see
> trivial-rewrite(8) and cleanup(8) for the specifics.
>
> [ ... ]

Yes, I just now read your reply in the workers list, and thanks. I
haven't been to my email for a few days.

The address in error is not part of the envelope; it's on the "From"
line and therefore, it's part of the DATA segment. I'm using postfix and
am already rejecting malformed addresses in the envelope.

I'm going to dig through the TMDA code and look into Address.py, as you
suggested in the post in the workers list. I'll handle such malformed
addresses within that code. Once I get this working, I'll post a patch.

Thanks again for your help.


-- 
 Lloyd Zusman
 [email protected]
 God bless you.


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
tmda-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tmda-users