2 From: Lord John Whorfin <whorfin@yoyodyne.com>
\r
3 To: <john-yaya@yoyodyne.com>
\r
4 Subject: A complex nested multipart example
\r
5 Content-Type: multipart/mixed;
\r
6 boundary=unique-boundary-1
\r
8 The preamble of the outer multipart message.
\r
9 Mail readers that understand multipart format
\r
10 should ignore this preamble.
\r
11 If you are reading this text, you might want to
\r
12 consider changing to a mail reader that understands
\r
13 how to properly display multipart messages.
\r
16 Part 1 of the outer message.
\r
17 [Note that the preceding blank line means
\r
18 no header fields were given and this is text,
\r
19 with charset US ASCII. It could have been
\r
20 done with explicit typing as in the next part.]
\r
23 Content-type: text/plain; charset=US-ASCII
\r
25 Part 2 of the outer message.
\r
26 This could have been part of the previous part,
\r
27 but illustrates explicit versus implicit
\r
28 typing of body parts.
\r
31 Subject: Part 3 of the outer message is multipart!
\r
32 Content-Type: multipart/parallel;
\r
33 boundary=unique-boundary-2
\r
35 A one-line preamble for the inner multipart message.
\r
37 Content-Type: image/gif
\r
38 Content-Transfer-Encoding: base64
\r
39 Content-Disposition: inline; filename="3d-compress.gif"
\r
40 Subject: Part 1 of the inner message is a GIF, "3d-compress.gif"
\r
42 R0lGODdhKAAoAOMAAAAAAAAAgB6Q/y9PT25ubnCAkKBSLb6+vufn5/Xes/+lAP/6zQAAAAAA
\r
43 AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJLMOyYbcoxkaZ5oCkoH6L5wLMfiWqd4btZhmxbA
\r
44 oFCY47EIqMJgyWw2ATjj7aRkAq5YwDMl9VGtKO0SiuoiTVlscsxt9c4HgXxUIA0EAVOVfDKT
\r
45 8Hl1B3kDAYYle202XnGGgoMHhYckiWVuR3+OTgCGeZRslotwgJ2lnYigfZdTjQULr7ALBZN0
\r
46 qTurjHgLKAu0B5Wqopm7J72etQN8t8Ijury+wMtvw8/Hv7Ylfs0BxCbGqMmK0yOOQ0GTCgrR
\r
47 2bhwJGlXJQYG6mMKoeNoWSbzCWIACe5JwxQm3AkDAbUAQCiQhDZEBeBl6afgCsOBrD45edIv
\r
48 QceGWSMevpOYhl6CkydBHhBZQmGKjihVshypjB9ClAHZMTugzOU7mzhBPiSZ5uDNnA7b/aTZ
\r
49 0mhMnfl0pDBFa6bUElSPWb0qtYuHrxlwcR17YsWMs2jTql3LFkQEADs=
\r
51 Content-Type: image/gif
\r
52 Content-Transfer-Encoding: base64
\r
53 Content-Disposition: inline; filename="3d-eye.gif"
\r
54 Subject: Part 2 of the inner message is another GIF, "3d-eye.gif"
\r
56 R0lGODdhKAAoAPMAAAAAAAAAzN3u/76+voiIiG5ubszd7v///+fn5wAAAAAAAAAAAAAAAAAA
\r
57 AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJbMOy4bMoxkaZ5oCkoD6L5wLMfiWns41oZt7lM7
\r
58 VujnC96IRVsPWQE4nxPjkvmsQmu8oc/KBUSVWk7XepGGLeNrxoxJO1MjILjthg/kWXQ6wO/7
\r
59 +3dCeRRjfAKHiImJAV+DCF0BiW5VAo1CElaRh5NjlkeYmpyTgpcTAKGiaaSfpwKpVQaxVatL
\r
60 rU8GaQdOBAQAB7+yXliXTrgAxsW4vFabv8BOtBsBt7cGvwCIT9nOyNEIxuC4zrqKzc9XbODJ
\r
61 vs7Y5ewH3d7Fxe3jB4rj8t6PuNa6r2bhKQXN17FYCBMqTGiBzSNhx5g0nEMhlsSJjiRYvDjw
\r
62 E0cdGxQ/gswosoKUkmuU2FnJcsSKGTBjypxJsyaICAA7
\r
63 --unique-boundary-2--
\r
65 The epilogue for the inner multipart message.
\r
68 Content-type: text/richtext
\r
70 This is <bold>part 4 of the outer message</bold>
\r
71 <smaller>as defined in RFC1341</smaller><nl>
\r
73 Isn't it <bigger><bigger>cool?</bigger></bigger>
\r
76 Content-Type: message/rfc822
\r
78 From: (mailbox in US-ASCII)
\r
79 To: (address in US-ASCII)
\r
80 Subject: Part 5 of the outer message is itself an RFC822 message!
\r
81 Content-Type: Text/plain; charset=ISO-8859-1
\r
82 Content-Transfer-Encoding: Quoted-printable
\r
84 Part 5 of the outer message is itself an RFC822 message!
\r
86 --unique-boundary-1--
\r
88 The epilogue for the outer message.
\r