# complex multipart test # excerpt from RFC2049 MIME-Version: 1.0 From: Nathaniel Borenstein To: Ned Freed Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT) 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 blank between the boundary and the start of the text in this part means no header fields were given and this is text in the US-ASCII character set. 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 ICAuLi4gYmFzZTY0LWVuY29kZWQgODAwMCBIeiBzaW5nbGUtY2hhbm5lbAogICAgICBtdS1s YXctZm9ybWF0IGF1ZGlvIGRhdGEgZ29lcyBoZXJlIC4uLgo= --unique-boundary-2 Content-Type: image/jpeg Content-Transfer-Encoding: base64 ICAuLi4gYmFzZTY0LWVuY29kZWQgaW1hZ2UgZGF0YSBnb2VzIGhlcmUgLi4uCg== --unique-boundary-2-- --unique-boundary-1 Content-type: text/enriched This is enriched. as defined in RFC 1896 Isn't it cool? --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=20text=20in=20ISO-8859-1=20goes=20here ... --unique-boundary-1--