Re: Probable bug in handling message/rfc822

Bob Rogers <[email protected]> Thu, 7 Jan 2010 21:59:36 -0500
Newsgroups gmane.mail.spam.tmda.devel
Message-ID <[email protected]>
   From: Nils Ackermann <[email protected]>
   Date: Wed, 06 Jan 2010 21:17:58 -0600

   . . .

   The thread 

   http://thread.gmane.org/gmane.mail.spam.tmda.user/16395

   describes how mail delivery through tmda-ofmipd is impeded by this same
   problem: a message/rfc822 attachment throws an error in tmda processing
   *after* the email has already been accepted by the tmda-ofmipd server.
   The message disappears silently, is never delivered, and no error
   message is produced by tmda-ofmipd.  I haven't used message/rfc822
   attachments for a couple of years because of this problem.

Interesting.  It looks like fixing this particular mishandling of
message/rfc822 bodies would also fix the tmda-ofmipd problem.

   I believe tmda-ofmipd should in any case catch errors in tmda-processing
   after accepting emails for delivery and send a bounce back to the email
   sender if a problem occurs.

   Cheers,
   Nils

Absolutely; no mail transport system component should be this sensitive
to MIME formatting, let alone by dropping the message.

					-- Bob

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
tmda-workers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tmda-workers