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

Authors, senders, and recipients

04

From describes authorship, Sender the transmitting agent, and Reply-To reply destinations.

Related RFCs and changes

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

RFC 5322 · § 3.6.2EXAMPLE
3 / 3
Authors, senders, and recipientsFrom describes authorship, Sender the transmitting agent, and Reply-To reply destinations.Author, sending agent, reply destinationFrom: authorSender: agenton behalf ofreply suggested hereReply-To: help@example.orgBcc visibility and the SMTP envelope are separate.
03
Choose reply and visibility.

Reply-To can direct replies elsewhere; Bcc must protect blind-recipient details.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 5322 § 3.6.2RFC 6854 § 2.1

The later update permits group syntax in originator fields under specified conditions, while recommending against its general use. This does not authenticate authorship.

Read the updated RFC section ↗
KEY POINT

These roles are not identity proofs.

  • Multiple authors in From require Sender under the base specification.
  • Bcc handling must avoid exposing blind recipients to other recipients.
DETAILS

The SMTP envelope can differ from the displayed recipient fields.

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 ↗