[Mailman-Users] Fwd: Uncaught bounce notification

Mark Sapiro mark at msapiro.net
Wed May 31 21:25:18 EDT 2017

On 05/31/2017 10:33 AM, zd wrote:
> Seems the attachment is missing, so here it is:

Thank you for the report. Unfortunately, this bounce is unrecognized
because it is missing critical information.

> Content-Type: multipart/report; report-type=delivery-status;
> 	boundary="__1496213893893132371abhmp0012.oracle.com"
> --__1496213893893132371abhmp0012.oracle.com
> Content-Type: text/plain; charset=utf-8
> This is an automatically generated Delivery Status Notification.
> --__1496213893893132371abhmp0012.oracle.com
> Content-Type: message/delivery-status
> --__1496213893893132371abhmp0012.oracle.com
> Content-Type: message/rfc822

This is a correctly formatted RFC 3464 Delivery status notification
except information is missing. In particular, the first text/plain part
according to RFC 3462 is

   1) [Required] The first body part contains human readable message.
   The purpose of this message is to provide an easily understood
   description of the condition(s) that caused the report to be
   generated, for a human reader who may not have a user agent capable
   of interpreting the second section of the Multipart/Report.

Clearly the text
"This is an automatically generated Delivery Status Notification." does
not satisfy this requirement.

The second message/delivery-status part is

   (2) [Required] A machine parsable body part containing an account of
   the reported message handling event. The purpose of this body part is
   to provide a machine-readable description of the condition(s) that
   caused the report to be generated, along with details not present in
   the first body part that may be useful to human experts.  An initial
   body part, Message/delivery-status is defined in [RFC 3464].

This part is what we look at and we are looking for fields like
Original-Recipient:, Final-Recipient: and Action:. These fields and
others should be there, but this part is empty in this message.

Either the MTA that sent it is broken or some content filter removed
that information before it got to Mailman. Whatever the reason. there is
no information in this report to identify the address that bounced or
the reason for the bounce so we can't possibly recognize it.

Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

More information about the Mailman-Users mailing list