Sample MIME Message
Sample MIME Message
MIME works by using headers and separators that tell a UA what processing is required to re-create the message. An example with no encoded body parts is:
From: John Doe <email@example.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="XXXXboundary text" This is a multipart message in MIME format. --XXXXboundary text Content-Type: text/plain this is the body text --XXXXboundary text Content-Type: text/plain; Content-Disposition: attachment; filename="test.txt" this is the attachment text --XXXXboundary text--
This example shows the use of a MIME message to send a text message and an attached text file. Both are body parts of this message.
MIME-Version:" header tells the receiving UA to treat this as a MIME message.
Content-Type:" header specifies "
multipart/mixed". This tells the receiving UA that this message has parts separated by the string argument defined in "
boundary=". A MIME-compliant UA will only display or otherwise process content following the specified "
boundary=" text strings. The actual boundaries are constructed using the "
boundary=" string, prepended by "
--". The final body part is followed by the "
boundary=" string with the "
--" both prepended and appended.
In the preceding example, the courtesy message "
This is a multipart message in MIME format."will not be displayed or otherwise processed by the MIME UA since it does not follow a "
boundary=" string. A UA that does not support MIME will display it, and at least this part of the message will be readable no matter what features the reader supports. If our example had encoded parts, they would make no sense to the human reader using a non-MIME-compliant UA, but at least the courtesy message would give the user a hint as to why.
There are two message body parts in our example. Each body part has headers of its own, in addition to the overall message headers. Each body part begins with the boundary string. If there were no headers in the body parts, then the blank line that must follow headers in RFC 822 messages would follow the boundary string. The first body part is a plain text message. It is the message the sender might have typed into a UA. Its single "
Content-Type:" header identifies it as "
text/plain", meaning US-ASCII characters are used exclusively and any UA should be able to display this body part. Text/plain is the default content type.
The second body part in this example contains the file attachment. Since the file attachment is an ASCII text file, it is sent with no encoding and its content-type is given as text/plain. The "
Content-Disposition: attachment" header has a parameter, "
filename=", which specifies a suggested name for the file. This header specifies that this body part is to be treated as a file rather than being displayed to the user and is to be saved on local storage under the suggested file name.