Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|| The TCP/IP Guide|
9 TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
9 TCP/IP Key Applications and Application Protocols
9 TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
9 TCP/IP Electronic Mail System: Concepts and Protocols (RFC 822, MIME, SMTP, POP3, IMAP)
9 TCP/IP Electronic Mail Message Formats and Message Processing: RFC 822 and MIME
TCP/IP Electronic Mail Standard Message Format: RFC 822
One of the most astute observations
I have read about internetworking applications is that their usefulness
is proportional to the number of people who use them. TCP/IP e-mail
is a great example: it is a powerful communication method in large part
because almost everyone with a computer today participates in the system.
The more people who sign on to use e-mail, the more powerful it becomes.
The creators of TCP/IP email realized
that people who use the system would employ many different types of
hardware and software. To ensure that everyone was able to understand
all e-mail messages, regardless of who sent them, they specified a common
message format for electronic mail messages. This format doesn't have
an official fancy name; it is simply known by the name of the standard
that defines it: the RFC 822 message format.
In this section I describe the RFC
822 message format, which forms the basis for electronic mail message
transfer in TCP/IP. I begin with an overview of the format and the general
structure of messages, and some of the overall rules used to format
RFC 822 messages. I then describe the many headers used in RFC 822 e-mail
messages, and how they are arranged into groups. I conclude with a brief
look at how RFC 822 messages are processed and their contents interpreted.
Related Information: This section may make certain references to the one on SMTP, but was designed so that you could read it prior to reading about SMTP without getting confused. Well, I tried, anyway. J
|If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!|
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.