🚀 go-pugleaf

In article <1993Jan11.001838.13304@lut.ac.uk> M.T.Hamilton@lut.ac.uk ([*] M.T.Hamilton) writes:
>  Lines: 24
>
>  ###MIME headers follow###
>  Content-Type: text/richtext

Yes, this is precisely the sort of thing I meant.  Except that '#' is
probably not a good character to use - see RFC 1341 Appendix B.
If a tag is thought necessary, I suggest

  .)MIME

but perhaps a better scheme would be:

The message (or file) is scanned until the end, or the first line that
doesn't start with one of the five text strings used to represent MIME
"headers" in RFC 1341.  If a MIME-Version "header" is found, the file
is considered to contain MIME; any detected MIME headers are removed from
the content of the file as used by the application.

The remaining problem is with "Received:" headers, which have a habit of
being moved to message texts by gateways sending to non-RFC822 domains.
But then MUAs can do ad hoc processing (perhaps removing them altogether
or creating a new MIME text body part to contain them); this problem will
not be present in non-message-transfer applications.