Previous: Appendix B -- General Guidelines For Sending Email Data
Next: Appendix D -- Collected Grammar

Appendix C -- A Complex Multipart Example

What follows is the outline of a complex multipart message. This message has five parts to be displayed serially: two introductory plain text parts, an embedded multipart message, a richtext part, and a closing encapsulated text message in a non-ASCII character set. The embedded multipart message has two parts to be displayed in parallel, a picture and an audio fragment.

      MIME-Version: 1.0
      From: Nathaniel Borenstein <>
      To: Ned Freed <>
      Subject: A multipart example
      Content-Type: multipart/mixed;

      This is the preamble area of a multipart message.
      Mail readers that understand multipart format
      should ignore this preamble.
      If you are reading this text, you might want to
      consider changing to a mail reader that understands
      how to properly display multipart messages.

         ...Some text appears here...
      [Note that the preceding blank line means
      no header fields were given and this is text,
      with charset US ASCII.  It could have been
      done with explicit typing as in the next part.]

      Content-type: text/plain; charset=US-ASCII

      This could have been part of the previous part,
      but illustrates explicit versus implicit
      typing of body parts.

      Content-Type: multipart/parallel;

      Content-Type: audio/basic
      Content-Transfer-Encoding: base64

         ... base64-encoded 8000 Hz single-channel
             mu-law-format audio data goes here....

      Content-Type: image/gif
      Content-Transfer-Encoding: base64

         ... base64-encoded image data goes here....


      Content-type: text/richtext

      This is <bold><italic>richtext.</italic></bold>
      <smaller>as defined in RFC 1341</smaller>
      <nl><nl>Isn't it

      Content-Type: message/rfc822

      From: (mailbox in US-ASCII)
      To: (address in US-ASCII)
      Subject: (subject in US-ASCII)
      Content-Type: Text/plain; charset=ISO-8859-1
      Content-Transfer-Encoding: Quoted-printable

         ... Additional text in ISO-8859-1 goes here ...


Previous: Appendix B -- General Guidelines For Sending Email Data
Next: Appendix D -- Collected Grammar