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

Message IDs and reply threads

05

Each new message has its own ID; reply fields describe relationships to earlier messages.

Related RFCs and changes

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

RFC 5322 · § 3.6.4EXAMPLE
3 / 3
Message IDs and reply threadsEach new message has its own ID; reply fields describe relationships to earlier messages.New message, new ID; replies retain ancestryOriginal AID: a@examplereplyReply BID: b@exampleB In-Reply-To: a@exampleReply CID: c@exampleC References: A, BSchematic example identifiers · subject text is not the ID.
03
Extend the chain.

References retains the ancestry described by the RFC.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A reply gets a new identifier.

  • Message-ID should be present and must be globally unique when used.
  • In-Reply-To names parents; References describes the reference chain.
DETAILS

A matching subject is not a unique thread identifier, and IDs do not authenticate senders.

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 ↗