Connected: An Internet Encyclopedia
RFC 1521 - Appendix C -- A Complex Multipart Example

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1521
Prev: 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 <nsb@bellcore.com>
          To: Ned Freed <ned@innosoft.com>
          Subject: A multipart example
          Content-Type: multipart/mixed;
               boundary=unique-boundary-1

          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.
          --unique-boundary-1

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

          --unique-boundary-1
          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.

          --unique-boundary-1
          Content-Type: multipart/parallel;
               boundary=unique-boundary-2

          --unique-boundary-2
          Content-Type: audio/basic
          Content-Transfer-Encoding: base64

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

          --unique-boundary-2
          Content-Type: image/gif
          Content-Transfer-Encoding: base64

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

          --unique-boundary-2--

          --unique-boundary-1
          Content-type: text/richtext

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

          --unique-boundary-1
          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 ...

          --unique-boundary-1--

Next: Appendix D -- Collected Grammar

Connected: An Internet Encyclopedia
RFC 1521 - Appendix C -- A Complex Multipart Example