summaryrefslogtreecommitdiffstats
path: root/comm/mailnews/test/data/multipart-complex2
blob: 0898d02810f61a0f4f00a39e6a99956c030a48c4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
From - Mon Jun 02 19:00:00 2008
Content-Type: multipart/mixed; boundary="bou"
Message-Id: <123456@example.com>

Part 1
--bou                       
Content-Type: multipart/related; boundary="bound"

Part 2
--bound
Content-Type: multipart/digest; boundary="boundar"

Part 3
--boundar
Content-Type: multipart/alternative; boundary="boundary"

Part 4
--boundary
Content-Type: application/octet-stream

Wow, what alternatives!

We're trying to confuse the parser here.

--bou

--bound

--boundar

--boundary
Content-Type: application/pdf

A choice between a PDF and an octet stream! How marvellous!

--boundary--

--boundar
Content-Type: multipart/mixed; boundary="boundary123456"

--boundary123456
Content-Type: text/plain

This is the correct answer.

--boundary123456--

--boundar--

--bound
Content-Type: text/plain

One last attempt at confusing the parser.

--bound--

--bou
Content-Type: text/html

<html><body>No harm in making another.</body></html>

--bou--