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                           9  TCP/IP Enhanced Electronic Mail Message Format: Multipurpose Internet Mail Extensions (MIME)

MIME Composite Media Types: Multipart and Encapsulated Message Structures 1 2 3 MIME Extension for Non-ASCII Mail Message Headers

One of the main reasons why MIME was created was the significant restrictions that the RFC 822 standard places on how data in e-mail messages must be formatted. To follow the rules, messages must be encoded in US ASCII, a 7-bit data representation. This means that even though each byte can theoretically have any of 256 values, in ASCII only 128 values are valid. Furthermore, lines can be no longer than 1000 characters including the carriage return and line feed (“CRLF”) characters at the end, and those two characters cannot appear elsewhere.

For some types of data, such as text files, this is no big deal, but for others it is a serious problem. This is especially the case with binary data. If you look at the data in a video clip or MP3 file or executable program, it will appear to be “random gibberish”. In fact, such data is not random but is represented using specific rules, but the data is expressed in raw binary form, where any 8-bit byte can contain any value from 0 to 255, which is why it looks like “junk” to humans. More importantly, this means that this data does not follow the rules for RFC 822 files and cannot be sent directly in this form.

MIME Composite Media Types: Multipart and Encapsulated Message Structures 1 2 3 MIME Extension for Non-ASCII Mail Message Headers