--On Monday, December 17, 2001 1:07 PM -0800 "Paul Hoffman / IMC"
Instead, how about encouraging the use of multipart/mixed which starts
with text/rfc822-headers. Any headers in that first part are to replace
the same headers on display only.
I think a better solution is to encapsulate the original message as a
message/rfc822 part within an outer message, whose headers can be arbitrary
(within the bounds of rfc2822). Then the recommendation would be for
clients to present the embedded message/rfc822 part as the 'real' message
to the user when the message/rfc822 is at the top-level of the MIME
structure. This also has the advantage that it makes it easier to store the
original message (header and content), throwing away the outer header, if
needed, without having to 'reconstruct' it from the multipart/mixed,
text/rfc822-headers .... construct you suggest.