Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fifth and final document describes MIME conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography. [STANDARDS-TRACK]
Replaces RFC 1341: MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies, RFC 1342: Representation of Non-ASCII Text in Internet Message Headers, RFC 1521: MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies, RFC 1522: MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text, RFC 1590: Media Type Registration Procedure.
Normative requirements
Every sentence in this RFC carrying an RFC 2119 keyword, with the section it came from. 3 must, 0 should, 0 may.
2 MIME Conformance
- MUSTA mail user agent that is MIME-conformant MUST:
- MUSTConforming user agents MUST include proper MIME labelling when sending anything other than plain text in the US-ASCII character set.
8 Acknowledgements
- MUST NOT(8) The prose and BNF describing the multipart media type have been changed to make it clear that the body parts within a multipart object MUST NOT contain any lines beginning with the boundary parameter string.