| 1 |
# complex multipart test |
| 2 |
# excerpt from RFC2049 |
| 3 |
MIME-Version: 1.0 |
| 4 |
From: Nathaniel Borenstein <[email protected]> |
| 5 |
To: Ned Freed <[email protected]> |
| 6 |
Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT) |
| 7 |
Subject: A multipart example |
| 8 |
Content-Type: multipart/mixed; |
| 9 |
boundary=unique-boundary-1 |
| 10 |
|
| 11 |
This is the preamble area of a multipart message. |
| 12 |
Mail readers that understand multipart format |
| 13 |
should ignore this preamble. |
| 14 |
|
| 15 |
If you are reading this text, you might want to |
| 16 |
consider changing to a mail reader that understands |
| 17 |
how to properly display multipart messages. |
| 18 |
|
| 19 |
--unique-boundary-1 |
| 20 |
|
| 21 |
... Some text appears here ... |
| 22 |
|
| 23 |
[Note that the blank between the boundary and the start |
| 24 |
of the text in this part means no header fields were |
| 25 |
given and this is text in the US-ASCII character set. |
| 26 |
It could have been done with explicit typing as in the |
| 27 |
next part.] |
| 28 |
|
| 29 |
--unique-boundary-1 |
| 30 |
Content-type: text/plain; charset=US-ASCII |
| 31 |
|
| 32 |
This could have been part of the previous part, but |
| 33 |
illustrates explicit versus implicit typing of body |
| 34 |
parts. |
| 35 |
|
| 36 |
--unique-boundary-1 |
| 37 |
Content-Type: multipart/parallel; boundary=unique-boundary-2 |
| 38 |
|
| 39 |
--unique-boundary-2 |
| 40 |
Content-Type: audio/basic |
| 41 |
Content-Transfer-Encoding: base64 |
| 42 |
|
| 43 |
ICAuLi4gYmFzZTY0LWVuY29kZWQgODAwMCBIeiBzaW5nbGUtY2hhbm5lbAogICAgICBtdS1s |
| 44 |
YXctZm9ybWF0IGF1ZGlvIGRhdGEgZ29lcyBoZXJlIC4uLgo= |
| 45 |
|
| 46 |
--unique-boundary-2 |
| 47 |
Content-Type: image/jpeg |
| 48 |
Content-Transfer-Encoding: base64 |
| 49 |
|
| 50 |
ICAuLi4gYmFzZTY0LWVuY29kZWQgaW1hZ2UgZGF0YSBnb2VzIGhlcmUgLi4uCg== |
| 51 |
--unique-boundary-2-- |
| 52 |
|
| 53 |
--unique-boundary-1 |
| 54 |
Content-type: text/enriched |
| 55 |
|
| 56 |
This is <bold><italic>enriched.</italic></bold> |
| 57 |
<smaller>as defined in RFC 1896</smaller> |
| 58 |
|
| 59 |
Isn't it |
| 60 |
<bigger><bigger>cool?</bigger></bigger> |
| 61 |
|
| 62 |
--unique-boundary-1 |
| 63 |
Content-Type: message/rfc822 |
| 64 |
|
| 65 |
From: (mailbox in US-ASCII) |
| 66 |
To: (address in US-ASCII) |
| 67 |
Subject: (subject in US-ASCII) |
| 68 |
Content-Type: Text/plain; charset=ISO-8859-1 |
| 69 |
Content-Transfer-Encoding: Quoted-printable |
| 70 |
|
| 71 |
... Additional=20text=20in=20ISO-8859-1=20goes=20here ... |
| 72 |
|
| 73 |
--unique-boundary-1-- |