Visual RFC.
ALL RFCs / RFC 2045
Read the RFC ↗
RFC 2045 / MECHANISM GUIDE

MIME entity headers

01

MIME headers describe the body entity without replacing SMTP envelope routing.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3 ↗
RFC 2045 · § 3EXAMPLE
3 / 3
MIME entity headersMIME headers describe the body entity without replacing SMTP envelope routing.MIME entity headersMIME-Version: 1.0Content-Type: text/plain; charset=utf-8Content-Transfer-Encoding: base64[body bytes]SMTP envelope remains a separate layer
03
Deliver the body

Envelope routing remains separate from these body descriptions.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
Earlier MIME descriptionsRFC 2045 §6.6

This revision points to RFC 2049’s explicit canonical encoding model to clarify newline handling and the distinction between charsets and transfer encodings.

Read the updated RFC section ↗
KEY POINT

MIME-Version: 1.0 identifies this MIME format.

  • MIME-Version: 1.0 identifies this MIME format.
  • Content-Type describes the media type and parameters.
  • Content-Transfer-Encoding describes how body bytes were encoded for transport.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. MIME entity headers
  2. Content type and charset
  3. Quoted-printable bytes
  4. Base64 body encoding
  5. Canonical form and safety
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗