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 Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  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

Previous Topic/Section
TCP/IP Electronic Mail RFC 822 Standard Message Format Processing and Interpretation
Previous Page
Pages in Current Topic/Section
1
Next Page
MIME Message Format Overview, Motivation, History and Standards
Next Topic/Section

TCP/IP Enhanced Electronic Mail Message Format: Multipurpose Internet Mail Extensions (MIME)

The RFC 822 e-mail message format is the standard for the exchange of electronic mail in TCP/IP internetworks. Its use of simple ASCII text makes it easy to create, process and read e-mail messages, which has contributed to the success of e-mail as a worldwide communication method.

Unfortunately, while ASCII text is great for writing simple memorandums and other short messages, it provides no flexibility to support other types of communication. To allow e-mail to carry multimedia information, arbitrary files, and messages in languages using character sets other than ASCII, the Multipurpose Internet Mail Extensions (MIME) standard was created.

In this section I describe MIME and how it is used for modern e-mail messaging. I begin with an overview of MIME and discussion of its history and the standards that define it. I describe the two overall MIME message structures and provide a summary of the important MIME-specific headers. I then explain the important MIME Content-Type header in more detail, and discuss MIME discrete media types, subtypes and parameters. I discuss the more complex MIME multipart and encapsulated message structures, and then the different methods by which data can be encoded into MIME message bodies. I conclude with the special MIME extension to allow support for non-ASCII characters in ordinary e-mail headers.

Background Information: MIME is a message format that augments the basic RFC 822 message format, rather than replacing it. This section assumes that you have basic familiarity with the RFC 822 format and the more important e-mail message headers.


Note: While MIME was developed specifically for mail, its encoding and data representation methods have proven so useful that it has been adopted by other application protocols as well. One of the best known of these is the HyperText Transfer Protocol (HTTP), which uses MIME headers for indicating the characteristics of data being transferred. Some elements of MIME were in fact developed not for e-mail but for use by HTTP or other protocols, and I indicate this where appropriate. Be aware, however, that HTTP only uses elements of MIME; there are important differences, and HTTP messages are not MIME-compliant.


Quick navigation to subsections and regular topics in this section



Previous Topic/Section
TCP/IP Electronic Mail RFC 822 Standard Message Format Processing and Interpretation
Previous Page
Pages in Current Topic/Section
1
Next Page
MIME Message Format Overview, Motivation, History and Standards
Next Topic/Section

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!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - 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.