A Guide to RFC 2822 Internet Message Format

RFC 2822 is a standard that defines the format for internet email messages. This format is widely used and supported by most email clients and servers.

The standard specifies that an email message consists of a header section, a blank line, and a body section. The header section contains metadata about the email, such as the sender's email address and the subject line.

A From field is required in the header section, and it specifies the sender's email address. The email address is usually in the format of local-part@domain.

The standard also defines several other header fields, including the To field, which specifies the recipient's email address, and the Subject field, which specifies the email's subject line.

Suggestion: Email Sender Accreditation

The Internet Message Format is the backbone of email communication, and it's defined by RFC 2822.

This format is used to describe the structure and content of email messages, which can be sent, received, and stored by email clients and servers.

Broaden your view: How to Make Outlook Email Format Html

The format includes a header section that contains metadata about the message, such as the sender's and recipient's email addresses.

The header section is followed by a blank line, which separates it from the message body.

The message body contains the actual content of the email, such as text, images, and attachments.

The format also allows for the inclusion of additional headers, such as "Subject" and "From", which provide more information about the message.

These headers are used by email clients and servers to process and display the message correctly.

The format is flexible and can accommodate different types of email messages, including plain text and HTML emails.

See what others are reading: How to Get Email Headers

Structured field bodies in rfc 2822 have specific syntactical structure more restrictive than unstructured field bodies.

These structured field bodies are sequences of specific lexical tokens as described in sections 3 and 4 of this standard.

Many of these tokens are allowed to be introduced or end with comments as well as the space (SP, ASCII value 32) and horizontal tab (HTAB, ASCII value 9) characters.

Structured field bodies are subject to header "folding" and "unfolding" as described in section 2.2.3.

The process of unfolding is called "unfolding" and it involves simply removing any WSP that follows a CRLF.

This unfolding process is used to convert a folded representation of a header field into its single-line representation.

Line length is a crucial aspect of RFC 2822, and it's essential to understand the limits that are in place. Each line of characters MUST be no more than 998 characters.

Implementations that send, receive, or store Internet Message Format messages often have limitations that can't handle more than 998 characters on a line. This is why it's recommended to handle an arbitrarily large number of characters in a line for robustness sake, even though many implementations don't accept messages with more than 1000 characters per line.

The more conservative 78 character recommendation is in place to accommodate user interfaces that display messages, which may truncate or disastrously wrap displays of more than 78 characters per line.

Curious to learn more? Check out: Android Forward Text Messages to Email

Line Length Limits are crucial when working with text-based communication, and there are specific limits to keep in mind.

The 998 character limit is a hard limit, meaning a line of characters MUST be no more than 998 characters, excluding the CRLF.

This limit exists because many implementations that send, receive, or store Internet Message Format messages can't handle more than 998 characters on a line.

In fact, there are so many implementations that don't accept messages with more than 1000 characters per line, including the CR and LF, that it's essential to avoid creating such messages.

The more conservative 78 character recommendation is in place to accommodate user interfaces that display messages and may truncate or wrap long lines.

Even though this limitation is non-conformant, it's still important for implementations that display messages to handle an arbitrarily large number of characters in a line for the sake of robustness.

Discover more: How to Send Text Messages from Email

Long Header Fields are a bit tricky, but basically, each header field is logically a single line of characters, comprising the field name, the colon, and the field body.

The field body portion of a header field can be split into a multiple line representation, which is called "folding". This is done to deal with the 998/78 character limitations per line.

Folding involves inserting a CRLF (carriage return and line feed) before any WSP (whitespace) characters. For example, a header field can be represented as multiple lines.

The general rule is that folding can occur wherever this standard allows for folding white space, not just WSP characters.

Intriguing read: Valid Characters in Email Addresses

Header fields are lines composed of a field name, followed by a colon, followed by a field body, and terminated by CRLF. A field name MUST be composed of printable US-ASCII characters, except colon.

A field body may be composed of any US-ASCII characters, except for CR and LF. However, a field body may contain CRLF when used in header "folding" and "unfolding" as described in section 2.2.3.

There are two types of field bodies: unstructured and structured. Unstructured field bodies are simply a single line of characters with no further processing, except for header "folding" and "unfolding". Structured field bodies, on the other hand, have specific syntactical structure and are sequences of specific lexical tokens as described in sections 3 and 4 of this standard.

Here are the main differences between unstructured and structured field bodies:

Header Field Bodies are lines composed of a field name, followed by a colon, followed by a field body, and terminated by CRLF.

In this standard, some field bodies are defined simply as "unstructured" with no further restrictions, meaning they can be composed of any US-ASCII characters except for CR and LF.

These unstructured field bodies are treated as a single line of characters with no further processing, except for header "folding" and "unfolding" as described in section 2.2.3.

Structured field bodies, on the other hand, have specific syntactical structure and are sequences of specific lexical tokens as described in sections 3 and 4 of this standard.

Structured field bodies can contain comments, space characters, and horizontal tab characters, which are subject to header "folding" and "unfolding" as described in section 2.2.3.

Folding is the process of taking a long header field and splitting it into multiple lines for convenience, and it's allowed wherever this standard allows for folding white space.

The general rule for folding is that a CRLF may be inserted before any WSP, but it's recommended to limit folding to higher-level syntactic breaks, such as after a comma separating structured items.

Character Handling is a crucial aspect of RFC 2822. Some characters are reserved for special interpretation, such as delimiting lexical tokens.

To permit use of these characters as uninterpreted data, a quoting mechanism is provided. This mechanism allows the "\" character to be used as a literal character, rather than for its special interpretation.

A "\" character that appears as part of a quoted-pair is semantically "invisible".

Japanese characters can be a challenge for many developers, with Kanji characters requiring a minimum of 3 bytes of storage space and Hiragana and Katakana requiring 2 bytes each.

In Japanese, Kanji characters are often used in combination with Hiragana and Katakana to convey different nuances and grammatical functions.

Kanji characters are logograms, meaning they represent words or concepts rather than sounds, and can have multiple readings and meanings.

Hiragana is used to indicate grammatical function, such as the subject or object of a sentence, and is often used to write particles and inflectional endings.

Katakana is used to write foreign loanwords, onomatopoeias, and emphasis, and is often used to write words related to technology and science.

Japanese text can be encoded in various ways, including Shift JIS, EUC-JP, and UTF-8, with UTF-8 being the most widely used and recommended encoding standard.

Quoted characters are used to permit the use of reserved characters as uninterpreted data. This is done to allow characters that are typically used for special interpretation, such as delimiting lexical tokens, to be used as plain text.

Some characters are reserved for special interpretation, such as delimiting lexical tokens. These characters include those used for quoting, folding, and other purposes.

To permit use of these characters as uninterpreted data, a quoting mechanism is provided. This mechanism allows characters that are typically used for special interpretation to be used as plain text.

The "\" character, in particular, is used as a quoting mechanism. When the "\" character appears as part of a quoted-pair, it is semantically "invisible". This means that it does not have any special meaning and is treated as a regular character.

The "\" character may appear in a message where it is not part of a quoted-pair. However, when it does appear in a quoted-pair, it is treated as a regular character and does not have any special meaning.

Quoted-pairs currently appear in several places in this standard, including ccontent, qcontent, dcontent, no-fold-quote, and no-fold-literal.

Related reading: Html vs Plain Text Email

In a room, the character's behavior can be influenced by the physical space.

A character's interactions with objects in a room can reveal their personality and background.

The layout of a room can also impact a character's actions, such as a narrow hallway making them feel trapped.

The cleanliness and organization of a room can give clues about a character's habits and values.

A cluttered room can suggest a character's disorganization or lack of priorities, while a tidy room can indicate their attention to detail.

The room's lighting can also set the tone for a character's mood and behavior, with dim lighting potentially making them feel anxious.

Here's an interesting read: Making Folders and Filing Important Emails

Bog BOS is a crucial aspect of character handling, as it can greatly impact a character's development and interactions with others.

In the context of the article, Bog BOS refers to the tendency of some characters to become bogged down in their own biases and opinions, making it difficult for them to see things from other perspectives.

This can lead to a lack of empathy and understanding, causing characters to come across as insensitive or even cruel.

In the article, we explored the example of a character who refused to consider the feelings of others, even when it was clear that they were suffering.

This behavior is a prime example of Bog BOS, and it can have serious consequences for the character and those around them.

Characters who struggle with Bog BOS often have trouble forming and maintaining healthy relationships, as they are unable to put themselves in others' shoes and understand their needs and feelings.

In one example, a character's refusal to listen to their friend's concerns led to a rift in their relationship that took months to repair.

If this caught your attention, see: Email Bounce Back Message Example

RFC 2822, the standard for email messages, has undergone several updates to improve its functionality and compatibility.

The most notable update was in 2001, when RFC 2822 replaced RFC 822, which had been the standard for email messages since 1982.

You might enjoy: Rfc for Email Addresses

In 2008, an update was proposed to enhance the standard, but it has not yet been implemented.

One of the key features of RFC 2822 is its ability to handle internationalized email addresses.

This is achieved through the use of the "utf-8" character set, which allows for the representation of non-ASCII characters in email addresses.

Email addresses in RFC 2822 must conform to a specific syntax, which includes the local part, the "@" symbol, and the domain name.

The local part can contain letters, numbers, and special characters, but it cannot exceed 64 characters in length.

The domain name must be a fully qualified domain name (FQDN), which is a string of characters that identifies a domain on the internet.

The "@" symbol is used to separate the local part from the domain name.

The domain name is case-insensitive, meaning that it can be written in either uppercase or lowercase letters.

The email address "[email protected]" is a valid example of an email address in RFC 2822 format.

See what others are reading: Get Domain Name and Email Addresses