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

Trace, resending, and trust

06

Trace fields record handling; Resent fields describe a new sending event without changing original authorship.

Related RFCs and changes

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

DIAGRAM§ 3.6.7 ↗
RFC 5322 · § 3.6.7EXAMPLE
4 / 4
Trace, resending, and trustTrace fields record handling; Resent fields describe a new sending event without changing original authorship.Trace records handling, not verified identityNEWEST FIRSTReceived: by relay BReceived: by relay AResent-From / Resent-DateOriginal From and Message-ID remainparse legacy syntax → generate current syntaxvalid format ≠ authenticated senderUse the appropriate authentication checks.
04
Check trust separately.

Syntax and display names do not authenticate the sender.

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

Valid syntax does not prove identity.

  • Received fields are prepended, with the most recent handling at the top.
  • Receivers interpret obsolete syntax; generators use current syntax.
DETAILS

Resent fields form a distinct block. Authentication and transport need separate specifications.

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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗