Comment 1 for bug 266364

I am moving this to bugs as it is a bug report, not a patch.

Your list owners don't need to provide any additional
information. I understand exactly what's happening here.
(but see below)

There are two issues. The first is that we don't protect
against this loop and I think we should try to. I'll look
into fixing it, although I suspect it will not be easy as
anything I might put in the 'unrecognized bounce' message to
try to detect a loop can be munged or dropped by the MTA
that returns the next bounce.

The other part of the issue is that the MTA that is
returning the 'over quota' denial is not returning an RFC
3464 or RFC 1894 compliant DSN or any of the many other
formats that Mailman heuristically recognizes. If it were,
it would be recognized and not sent back to the list owner.

There is one thing you can provide and that is the actual
'delivery status' part of the unrecognized bounce. You can
alter addresses and domains if you wish for privacy, but if
I have the exact message including headers, I can add a
recognizer for it. What I need is the contents of the
message/rfc822 part that follows the "The attached message
was received" notice you quote above up to the first
"original message follows". I.e., just the DSN part and it's
headers, not any of the multiple preceeding messages/DSNs/etc.