← Back to branch summary

~ubuntu-branches/ubuntu/utopic/apache-mime4j/utopic

« back to all changes in this revision

Viewing changes to core/src/test/resources/mimetools-testmsgs/multi-frag.msg

  • Committer: Package Import Robot
  • Author(s): David Paleino
  • Date: 2013-11-03 11:13:27 UTC
  • mfrom: (2.1.2 experimental)
  • Revision ID: package-import@ubuntu.com-20131103111327-09huep00ex05z113
Tags: 0.7.2-2
* Upload to unstable
* Fixed Vcs-* fields in debian/control
* Updated debian/watch
* Standards-Version bump to 3.9.5, no changes needed

Show diffs side-by-side

added added

removed removed

Lines of Context:
core/src/test/resources/mimetools-testmsgs/multi-frag.msg
 
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/6zQAAAAAA
 
43
AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJLMOyYbcoxkaZ5oCkoH6L5wLMfiWqd4btZhmxbA
 
44
oFCY47EIqMJgyWw2ATjj7aRkAq5YwDMl9VGtKO0SiuoiTVlscsxt9c4HgXxUIA0EAVOVfDKT
 
45
8Hl1B3kDAYYle202XnGGgoMHhYckiWVuR3+OTgCGeZRslotwgJ2lnYigfZdTjQULr7ALBZN0
 
46
qTurjHgLKAu0B5Wqopm7J72etQN8t8Ijury+wMtvw8/Hv7Ylfs0BxCbGqMmK0yOOQ0GTCgrR
 
47
2bhwJGlXJQYG6mMKoeNoWSbzCWIACe5JwxQm3AkDAbUAQCiQhDZEBeBl6afgCsOBrD45edIv
 
48
QceGWSMevpOYhl6CkydBHhBZQmGKjihVshypjB9ClAHZMTugzOU7mzhBPiSZ5uDNnA7b/aTZ
 
49
0mhMnfl0pDBFa6bUElSPWb0qtYuHrxlwcR17YsWMs2jTql3LFkQEADs=
 
50
--unique-boundary-2
 
51
Content-Type: image/gif
 
52
Content-Transfer-Encoding: base64
 
53
Content-Disposition: inline; filename="3d-eye.gif"
 
54
Subject: Part 2 of the inner message is another GIF, "3d-eye.gif", but 
 
55
 the terminating boundary is bad!
 
56
 
 
57
R0lGODdhKAAoAPMAAAAAAAAAzN3u/76+voiIiG5ubszd7v///+fn5wAAAAAAAAAAAAAAAAAA
 
58
AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJbMOy4bMoxkaZ5oCkoD6L5wLMfiWns41oZt7lM7
 
59
VujnC96IRVsPWQE4nxPjkvmsQmu8oc/KBUSVWk7XepGGLeNrxoxJO1MjILjthg/kWXQ6wO/7
 
60
+3dCeRRjfAKHiImJAV+DCF0BiW5VAo1CElaRh5NjlkeYmpyTgpcTAKGiaaSfpwKpVQaxVatL
 
61
rU8GaQdOBAQAB7+yXliXTrgAxsW4vFabv8BOtBsBt7cGvwCIT9nOyNEIxuC4zrqKzc9XbODJ
 
62
vs7Y5ewH3d7Fxe3jB4rj8t6PuNa6r2bhKQXN17FYCBMqTGiBzSNhx5g0nEMhlsSJjiRYvDjw
 
63
E0cdGxQ/gswosoKUkmuU2FnJcsSKGTBjypxJsyaICAA7
 
64
XXXXXX--unique-boundary-2--
 
65
 
 
66
The epilogue for the inner multipart message.
 
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