[Mailman-Users] Training Mailman to find email address from NDR

[Grant Taylor]

On 5/15/19 10:55 AM, Mark Sapiro wrote:
> This message is a disaster. Is this an actual bounce as received? It 
> almost looks like an RFC 3464 compliant DSN except see comment below.

~chuckle~

Agreed.

> The message body is that of a MIME multipart message, but the main 
> content type is text/plain instead of
> 
> multipart/mixed; boundary="66728b7fa14ce3ed"

RFC 3464 wants a Content-Type of message/delivery-status.

> so the whole body is just one plain text part and is quoted-printable 
> encoded so that just changing the above Content-Type: won't work because 
> there is quoted-printable encoded content in the sub-parts including 
> sub-part headers.
> 
> I have seen the other replies in this thread, so I'm not adding much here.
> 
> Trying to recognize this in Mailman would be a major kludge and not 
> worth the effort.

I would argue against hacking Mailman to recognize this as a failed 
attempt at an RFC 3464 Delivery Status Notification.

RFC 3464 has been out for 17 years.  I think it's past time that we stop 
coddling people that can't conform to it.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4008 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20190515/cad3be2d/attachment-0001.bin>