1 | MIME-Version: 1.0 |
---|
2 | From: Lord John Whorfin <whorfin@yoyodyne.com> |
---|
3 | To: <john-yaya@yoyodyne.com> |
---|
4 | Subject: A complex nested multipart example |
---|
5 | Content-Type: multipart/mixed; |
---|
6 | boundary=unique-boundary-1 |
---|
7 | |
---|
8 | The preamble of the outer multipart message. |
---|
9 | Mail readers that understand multipart format |
---|
10 | should ignore this preamble. |
---|
11 | If you are reading this text, you might want to |
---|
12 | consider changing to a mail reader that understands |
---|
13 | how to properly display multipart messages. |
---|
14 | --unique-boundary-1 |
---|
15 | |
---|
16 | Part 1 of the outer message. |
---|
17 | [Note that the preceding blank line means |
---|
18 | no header fields were given and this is text, |
---|
19 | with charset US ASCII. It could have been |
---|
20 | done with explicit typing as in the next part.] |
---|
21 | |
---|
22 | --unique-boundary-1 |
---|
23 | Content-type: text/plain; charset=US-ASCII |
---|
24 | |
---|
25 | Part 2 of the outer message. |
---|
26 | This could have been part of the previous part, |
---|
27 | but illustrates explicit versus implicit |
---|
28 | typing of body parts. |
---|
29 | |
---|
30 | --unique-boundary-1 |
---|
31 | Subject: Part 3 of the outer message is multipart! |
---|
32 | Content-Type: multipart/parallel; |
---|
33 | boundary=unique-boundary-2 |
---|
34 | |
---|
35 | A one-line preamble for the inner multipart message. |
---|
36 | --unique-boundary-2 |
---|
37 | Content-Type: image/gif |
---|
38 | Content-Transfer-Encoding: base64 |
---|
39 | Content-Disposition: inline; filename="3d-vise.gif" |
---|
40 | Subject: Part 1 of the inner message is a GIF, "3d-vise.gif" |
---|
41 | |
---|
42 | R0lGODdhKAAoAOMAAAAAAAAAgB6Q/y9PT25ubnCAkKBSLb6+vufn5/Xes/+lAP/6zQAAAAAAAAAA |
---|
43 | AAAAACwAAAAAKAAoAAAE/hDJSau9eJLMOyYbcoxkaZ5oCkoH6L5wLMfiWqd4btZhmxbAoFCY47EI |
---|
44 | qMJgyWw2ATjj7aRkAq5YwDMl9VGtKO0SiuoiTVlscsxt9c4HgXxUIA0EAVOVfDKT8Hl1B3kDAYYl |
---|
45 | e202XnGGgoMHhYckiWVuR3+OTgCGeZRslotwgJ2lnYigfZdTjQULr7ALBZN0qTurjHgLKAu0B5Wq |
---|
46 | opm7J72etQN8t8Ijury+wMtvw8/Hv7Ylfs0BxCbGqMmK0yOOQ0GTCgrR2bhwJGlXJQYG6mMKoeNo |
---|
47 | WSbzCWIACe5JwxQm3AkDAbUAQCiQhDZEBeBl6afgCsOBrD45edIvQceGWSMevpOYhl6CkydBHhBZ |
---|
48 | QmGKjihVshypjB9ClAHZMTugzOU7mzhBPiSZ5uDNnA7b/aTZ0mhMnfl0pDBFa6bUElSPWb0qtYuH |
---|
49 | rxlwcR17YsWMs2jTql3LFkQEADs= |
---|
50 | |
---|
51 | --unique-boundary-2 |
---|
52 | Content-Type: image/gif |
---|
53 | Content-Transfer-Encoding: base64 |
---|
54 | Content-Disposition: inline; filename="3d-eye.gif" |
---|
55 | Subject: Part 2 of the inner message is another GIF, "3d-eye.gif", but |
---|
56 | the terminating boundary is bad! |
---|
57 | |
---|
58 | R0lGODdhKAAoAPMAAAAAAAAAzN3u/76+voiIiG5ubszd7v///+fn5wAAAAAAAAAAAAAAAAAAAAAA |
---|
59 | AAAAACwAAAAAKAAoAAAE/hDJSau9eJbMOy4bMoxkaZ5oCkoD6L5wLMfiWns41oZt7lM7VujnC96I |
---|
60 | RVsPWQE4nxPjkvmsQmu8oc/KBUSVWk7XepGGLeNrxoxJO1MjILjthg/kWXQ6wO/7+3dCeRRjfAKH |
---|
61 | iImJAV+DCF0BiW5VAo1CElaRh5NjlkeYmpyTgpcTAKGiaaSfpwKpVQaxVatLrU8GaQdOBAQAB7+y |
---|
62 | XliXTrgAxsW4vFabv8BOtBsBt7cGvwCIT9nOyNEIxuC4zrqKzc9XbODJvs7Y5ewH3d7Fxe3jB4rj |
---|
63 | 8t6PuNa6r2bhKQXN17FYCBMqTGiBzSNhx5g0nEMhlsSJjiRYvDjwE0cdGxQ/gswosoKUkmuU2FnJ |
---|
64 | csSKGTBjypxJsyaICAA7XXXXXXuniqueboundary2Theepiloguefortheinnermultipartmess |
---|
65 | |
---|
66 | --unique-boundary-2-- |
---|
67 | |
---|
68 | --unique-boundary-1 |
---|
69 | Content-type: text/richtext |
---|
70 | |
---|
71 | This is <bold>part 4 of the outer message</bold> |
---|
72 | <smaller>as defined in RFC1341</smaller><nl> |
---|
73 | <nl> |
---|
74 | Isn't it <bigger><bigger>cool?</bigger></bigger> |
---|
75 | |
---|
76 | --unique-boundary-1 |
---|
77 | Content-Type: message/rfc822; name="nice.name"; |
---|
78 | |
---|
79 | From: (mailbox in US-ASCII) |
---|
80 | To: (address in US-ASCII) |
---|
81 | Subject: Part 5 of the outer message is itself an RFC822 message! |
---|
82 | Content-Type: Text/plain; charset=ISO-8859-1 |
---|
83 | Content-Transfer-Encoding: Quoted-printable |
---|
84 | |
---|
85 | Part 5 of the outer message is itself an RFC822 message! |
---|
86 | |
---|
87 | --unique-boundary-1-- |
---|
88 | |
---|
89 | The epilogue for the outer message. |
---|
90 | |
---|