I am looking more from the lay user perspective so it is a question
of how the e-mail client presents the information;
Right; I don't much care how it's presented to the end user. That's
between the UA's authors and its users.
message/delivery-status is typically reduced to a solid line across
the screen so we can both have what we want if your mailserver uses
message/delivery-status or message/rfc822; does it?
[...]
Do you accept multipart/mixed as well as multipart/report? The
former is not strictly RFC3462 but seems quite widely used.
I just checked. The code accepts multipart/report and multipart/mixed
(and treats them identically in this respect); it requires a
message/rfc822 or text/rfc822-headers portion, which it takes as
containing the bounced message (or at least its headers).
Yes, the message-ID is in the original message but what I saying here
is that there is no imperative to display it;
True at the user-agent level; false, I believe, at the
bounce-generation level.
Unless you're talking about the inteded-for-humans text portion of the
bounce, with the message-ID appearing like any other header in the
message/rfc822 or text/rfc822-headers part, in which case I have no
argument with it.
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML
mouse(_at_)rodents(_dot_)montreal(_dot_)qc(_dot_)ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg