Visual RFC.
ALL RFCs / RFC 5322
Read the RFC ↗
RFC 5322 / EMAIL MESSAGE FORMAT

Message anatomy

01

Header fields and an optional body are separated by an empty line.

Related RFCs and changes

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

DIAGRAM§ 2.1 ↗
RFC 5322 · § 2.1EXAMPLE
3 / 3
Message anatomyHeader fields and an optional body are separated by an empty line.A message has two different partsDate: Fri, 1 Jan 2027 12:00:00 +0000From: Ana <ana@example.org>To: Bo <bo@example.net>Subject: A short noteempty CRLF lineHello Bo,The body starts here.Format describes the letter; SMTP delivers it.
03
Read the body.

Following content belongs to the message body.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 2822RFC 5322

RFC 5322 obsoletes RFC 2822. Appendix B records the format changes; the separation of fields and body remains.

Read the updated RFC section ↗
KEY POINT

The empty line is a structural boundary.

  • Header fields describe the message; the body follows a blank CRLF line.
  • SMTP delivery is specified separately in RFC 5321.
DETAILS

MIME and internationalized fields extend this base format.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. Message anatomy
  2. Folding long fields
  3. Mailboxes and groups
  4. Authors, senders, and recipients
  5. Message IDs and reply threads
  6. Trace, resending, and trust
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗