| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 08:44:40 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=qK6P85H30NVtXpNjLLemAGVbWCS0NNsDz.Wesmky7gU-1759999480-1.0.1.1-r6L9chvzZV2KQQ_x_i0fzPtLCPtQS6pMqd8uEF7xXfFrOn5Dkr1mRib546DCjrE6AzeeF.adKtlPmfgow_LaKZycQ9_GO4PccDz.YSYDsBU; path=/; expires=Thu, 09-Oct-25 09:14:40 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc98e76b2b8cf1-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2822 » RFC Editor
Search RFCs
RFC 2822
Internet Message Format, April 2001
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 822
- Obsoleted by:
- RFC 5322
- Updated by:
- RFC 5335, RFC 5336
- Author:
- P. Resnick, Ed.
- Stream:
- IETF
- Source:
- drums (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2822
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2822
Abstract
This document specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us