If the enhanced text does not have headers then how can it be
Content-Domain: rfc822 ?
I agree that NOT ALL headers should be put into the enhanced text.
If you are NOT going to have a mechanism to allow the specification of
whether there are /are not headers in the enhanced part then maybe you
can persuade the MIME people to remove the Content-Type and Content-Transfer-
Encoding: etc header lines into the body and to use some marker line
in the body to signify that this is a MIME message...
If the content domain says rfc822 then I believe that there should be headers
and that the UA when de-enhancing should then re-parse those headers when it
displays the message.
Sure, we lose some information such as routing etc, but nothing in the non
enhanced text can be trusted anyway! and we don't lose information that CAN
be used for further processing such as de-MIMEing it.
So should we have the default Content-Domain to be say text, rather than
rfc822. Or rfc822-body if you want to keep the implied formatting limits that
goes with rfc822 messages.
Pete.