RFC 2822

E708917

RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (2)

Label Occurrences
RFC 2822 canonical 4
Internet Message Format 1

Statements (47)

Predicate Object
instanceOf Internet standard
Request for Comments document
appliesTo Internet email
SMTP-transmitted messages
area Applications
category Standards Track
defines addressing syntax for email messages
comments in header fields
date and time specification for email messages
folding of long header fields
format for text-based email messages
line length limits for email headers
message body structure for Internet email
semantics for Internet email headers
syntax for Internet email headers
white space handling in header fields
definesField Bcc header field
Cc header field
Date header field
From header field
In-Reply-To header field
Message-ID header field
Received header field
References header field
Reply-To header field NERFINISHED
Resent-* header fields
Sender header field
Subject header field
To header field
doesNotDefine MIME content types
message transport
language English
obsoletedBy RFC 5322 NERFINISHED
obsoletes RFC 822 NERFINISHED
publishedBy Internet Engineering Task Force
surface form: IETF

Internet Engineering Task Force
relatedTo RFC 5321 NERFINISHED
SMTP NERFINISHED
replaces RFC 822 NERFINISHED
RFCNumber 2822
scope syntax and semantics of Internet message headers
specifies ABNF grammar for email message format
standardizes Internet message format NERFINISHED
status Obsoleted
title Internet Message Format NERFINISHED
updates RFC 822 NERFINISHED
updatesProtocol Internet Message Format NERFINISHED

Referenced by (5)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 822 obsoletedBy RFC 2822
RFC 822 influenced RFC 2822
RFC 2821 relatedTo RFC 2822
RFC 5322 title RFC 2822
this entity surface form: Internet Message Format
RFC 5322 obsoletes RFC 2822