Multipurpose Internet Mail Extensions
MIME

This document provides links to information about Multipurpose Internet Mail Extensions (MIME). MIME extends the format of Internet mail to allow non-US-ASCII textual messages, non-textual messages, multipart message bodies, and non-US-ASCII information in message headers.

NOTE

Please do NOT send MIME-related questions directly to the maintainer of this site. If you cannot find the answers to your questions at this site, please check out the comp.mail.mime FAQ.



RFC's

The following RFC's define Multipurpose Internet Mail Extensions (MIME):

Full TOC
RFC 2045: MIME Part One: Format of Internet Message Bodies
RFC 2046: MIME Part Two: Media Types
RFC 2047: MIME Part Three: Message Header Extensions for Non-ASCII Text
RFC 2048: MIME Part Four: Registration Procedures
RFC 2049: MIME Part Five: Conformance Criteria and Examples

Conversion of RFC's to HTML based on ASCII versions. If you notice any errors, please send a message to Earl Hood, earl@earlhood.com.

Related RFC's

RFC 1524: The formal description of mailcap files. Mailcap files describe how to handle media types.
RFC 2015: MIME Security with Pretty Good Privacy (PGP).
RFC 2110: MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML).
RFC 2111: Content-ID and Message-ID Uniform Resource Locators.
RFC 2112: The MIME Multipart/Related Content-type.
RFC 2183: Defines the syntax and sematics of the "Content-Disposition" header to convey presentational information.
RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
RFC 2440: OpenPGP Message Format
RFC 2633: S/MIME Version 3 Message Specification
RFC 2821: Simple Mail Transfer Protocol
RFC 2822: Internet Message Format
RFC 3156: MIME Security with OpenPGP

Obsolete RFC's

The following RFC's have been replaced by RFC's 2045 thru 2049:

RFC 1521: MIME Part One
RFC 1522: MIME Part Two

Other MIME Related Information

Google

$Date: 2006/04/25 04:23:15 $
Earl Hood, earl@earlhood.com