RFC 5322 3.6.5
RFC 5322 3.6.5
The informational fields are all optional. The "Subject:" and "Comments:" fields are unstructured fields as defined in section 2.2.1, and therefore may contain text or folding white space.
denotes header fields that may be used with MIME parts *
RFC 5322 3.6.3.
RFC 5322 3.6.3.
The destination fields of a message consist of three possible fields, each of the same form: the field name, which is either "To", "Cc", or "Bcc", followed by a comma-separated list of one or more addresses
Type of the destination (To, Cc, Bcc)
Destination address
Other Email addresses
RFC 5322 3.6.2.
RFC 5322 3.6.2.
The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message.
Email of the person
List of other autors of this email.
Any field that is not parsed to EmailHeaderFiled types
description of header, including its codec *
RFC 5322 3.6.4
RFC 5322 3.6.4
The "In-Reply-To:" and "References:" fields are used when creating a reply to a message. They hold the message identifier of the original message and the message identifiers of other messages (for example, in the case of a reply to a message that was itself a reply). The "In-Reply-To:" field may be used to identify the message (or messages) to which the new message is a reply, while the "References:" field may be used to identify a "thread" of conversation.
Id of the message
Id of other messages
Created by pach on 17/10/17.
RFC 5322 3.6.4
RFC 5322 3.6.4
The "Message-ID:" field provides a unique message identifier that refers to a particular version of a particular message. The uniqueness of the message identifier is guaranteed by the host that generates it (see below). This message identifier is intended to be machine readable and not necessarily meaningful to humans. A message identifier pertains to exactly one version of a particular message; subsequent revisions to the message each receive new message identifiers.
Value of known header is not RFC compliant Only for decoding of incoming emails.
RFC 5322 3.6.1
RFC 5322 3.6.1
The origination date specifies the date and time at which the creator of the message indicated that the message was complete and ready to enter the mail delivery system.
Created by pach on 17/10/17.
RFC 5322 3.6.4
RFC 5322 3.6.4
The "In-Reply-To:" and "References:" fields are used when creating a reply to a message. They hold the message identifier of the original message and the message identifiers of other messages (for example, in the case of a reply to a message that was itself a reply). The "In-Reply-To:" field may be used to identify the message (or messages) to which the new message is a reply, while the "References:" field may be used to identify a "thread" of conversation.
Id of the message
Id of other messages
RFC 5322 3.6.6:
RFC 5322 3.6.6:
Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.
For instance, the "Resent-Date:" field corresponds to the "Date:" field
RFC 5322 3.6.6:
RFC 5322 3.6.6:
Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.
For instance, the "Resent-From:" field corresponds to the "From:" field
RFC 5322 3.6.6:
RFC 5322 3.6.6:
Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.
For instance, the "Resent-Message-ID:" field corresponds to the "Message-ID:" field
RFC 5322 3.6.6:
RFC 5322 3.6.6:
Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.
For instance, the "Resent-Sender:" field corresponds to the "Sender:" field
RFC 5322 3.6.6:
RFC 5322 3.6.6:
Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.
For instance, the "Resent-To:" field corresponds to the "To:" field
Type of the destination (To, Cc, Bcc)
Destination address
Other Email addresses
RFC 5322 3.6.7:
RFC 5322 3.6.7:
The "Return-Path:" header field contains a pair of angle brackets that enclose an optional addr-spec.
RFC 5322 3.6.2:
RFC 5322 3.6.2:
if a secretary were to send a message for another person, the mailbox of the secretary would appear in the "Sender:" field and the mailbox of the actual author would appear in the "From:" field.
RFC 5322 3.6.5
RFC 5322 3.6.5
The informational fields are all optional. The "Subject:" and "Comments:" fields are unstructured fields as defined in section 2.2.1, and therefore may contain text or folding white space.
type of message destination *
Created by pach on 17/10/17.
Created by pach on 13/10/17.