4
MIME-Version: 1.0</field>
6
From: Lord John Whorfin <whorfin@yoyodyne.com></field>
8
To: <john-yaya@yoyodyne.com></field>
10
Subject: A complex nested multipart example</field>
12
Content-Type: multipart/mixed;
13
boundary=unique-boundary-1</field>
17
The preamble of the outer multipart message.
18
Mail readers that understand multipart format
19
should ignore this preamble.
20
If you are reading this text, you might want to
21
consider changing to a mail reader that understands
22
how to properly display multipart messages.</preamble>
27
Part 1 of the outer message.
28
[Note that the preceding blank line means
29
no header fields were given and this is text,
30
with charset US ASCII. It could have been
31
done with explicit typing as in the next part.]
37
Content-type: text/plain; charset=US-ASCII</field>
40
Part 2 of the outer message.
41
This could have been part of the previous part,
42
but illustrates explicit versus implicit
49
Subject: Part 3 of the outer message is multipart!</field>
51
Content-Type: multipart/parallel;
52
boundary=unique-boundary-2</field>
56
A one-line preamble for the inner multipart message.</preamble>
60
Content-Type: image/gif</field>
62
Content-Transfer-Encoding: base64</field>
64
Content-Disposition: inline; filename="3d-vise.gif"</field>
66
Subject: Part 1 of the inner message is a GIF, "3d-vise.gif"</field>
69
R0lGODdhKAAoAOMAAAAAAAAAgB6Q/y9PT25ubnCAkKBSLb6+vufn5/Xes/+lAP/6zQAAAAAA
70
AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJLMOyYbcoxkaZ5oCkoH6L5wLMfiWqd4btZhmxbA
71
oFCY47EIqMJgyWw2ATjj7aRkAq5YwDMl9VGtKO0SiuoiTVlscsxt9c4HgXxUIA0EAVOVfDKT
72
8Hl1B3kDAYYle202XnGGgoMHhYckiWVuR3+OTgCGeZRslotwgJ2lnYigfZdTjQULr7ALBZN0
73
qTurjHgLKAu0B5Wqopm7J72etQN8t8Ijury+wMtvw8/Hv7Ylfs0BxCbGqMmK0yOOQ0GTCgrR
74
2bhwJGlXJQYG6mMKoeNoWSbzCWIACe5JwxQm3AkDAbUAQCiQhDZEBeBl6afgCsOBrD45edIv
75
QceGWSMevpOYhl6CkydBHhBZQmGKjihVshypjB9ClAHZMTugzOU7mzhBPiSZ5uDNnA7b/aTZ
76
0mhMnfl0pDBFa6bUElSPWb0qtYuHrxlwcR17YsWMs2jTql3LFkQEADs=</body>
81
Content-Type: image/gif</field>
83
Content-Transfer-Encoding: base64</field>
85
Content-Disposition: inline; filename="3d-eye.gif"</field>
87
Subject: Part 2 of the inner message is another GIF, "3d-eye.gif"</field>
90
R0lGODdhKAAoAPMAAAAAAAAAzN3u/76+voiIiG5ubszd7v///+fn5wAAAAAAAAAAAAAAAAAA
91
AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJbMOy4bMoxkaZ5oCkoD6L5wLMfiWns41oZt7lM7
92
VujnC96IRVsPWQE4nxPjkvmsQmu8oc/KBUSVWk7XepGGLeNrxoxJO1MjILjthg/kWXQ6wO/7
93
+3dCeRRjfAKHiImJAV+DCF0BiW5VAo1CElaRh5NjlkeYmpyTgpcTAKGiaaSfpwKpVQaxVatL
94
rU8GaQdOBAQAB7+yXliXTrgAxsW4vFabv8BOtBsBt7cGvwCIT9nOyNEIxuC4zrqKzc9XbODJ
95
vs7Y5ewH3d7Fxe3jB4rj8t6PuNa6r2bhKQXN17FYCBMqTGiBzSNhx5g0nEMhlsSJjiRYvDjw
96
E0cdGxQ/gswosoKUkmuU2FnJcsSKGTBjypxJsyaICAA7</body>
100
The epilogue for the inner multipart message.
107
Content-type: text/richtext</field>
110
This is <bold>part 4 of the outer message</bold>
111
<smaller>as defined in RFC1341</smaller><nl>
113
Isn't it <bigger><bigger>cool?</bigger></bigger>
119
Content-Type: message/rfc822; name="nice.name";</field>
124
From: (mailbox in US-ASCII)</field>
126
To: (address in US-ASCII)</field>
128
Subject: Part 5 of the outer message is itself an RFC822 message!</field>
130
Content-Type: Text/plain; charset=ISO-8859-1</field>
132
Content-Transfer-Encoding: Quoted-printable</field>
135
Part 5 of the outer message is itself an RFC822 message!
141
The epilogue for the outer message.