test/expected/msg_38.txt

   1 From test Sat Feb  1 00:00:00 2014
   2 MIME-Version: 1.0
   3 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
   4
   5 ------- =_aaaaaaaaaa0
   6 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa1"
   7 Content-ID: <20592.1022586929.1@example.com>
   8
   9 ------- =_aaaaaaaaaa1
  10 Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa2"
  11 Content-ID: <20592.1022586929.2@example.com>
  12
  13 ------- =_aaaaaaaaaa2
  14 Content-Type: text/plain
  15 Content-ID: <20592.1022586929.3@example.com>
  16 Content-Description: very tricky
  17 Content-Transfer-Encoding: 7bit
  18
  19
  20 Unlike the test test_nested-multiples-with-internal-boundary, this
  21 piece of text not only contains the outer boundary tags
  22 ------- =_aaaaaaaaaa2--
  23
  24 ------- =_aaaaaaaaaa1
  25
  26 and
  27 ------- =_aaaaaaaaaa1--
  28
  29 ------- =_aaaaaaaaaa0
  30
  31 but puts them at the start of a line! And, to be even nastier, it
  32 even includes a couple of end tags, such as this one:
  33
  34 ------- =_aaaaaaaaaa1--
  35
  36 and this one, which is from a multipart we haven't even seen yet!
  37
  38 ------- =_aaaaaaaaaa4--
  39
  40 This will, I'm sure, cause much breakage of MIME parsers. But, as
  41 far as I can tell, it's perfectly legal. I have not yet ever seen
  42 a case of this in the wild, but I've seen *similar* things.
  43
  44
  45 ------- =_aaaaaaaaaa2
  46 Content-Type: application/octet-stream
  47 Content-ID: <20592.1022586929.4@example.com>
  48 Content-Description: patch2
  49 Content-Transfer-Encoding: base64
  50
  51 XXX
  52
  53 ------- =_aaaaaaaaaa2--
  54
  55 ------- =_aaaaaaaaaa1
  56 Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa3"
  57 Content-ID: <20592.1022586929.6@example.com>
  58
  59 ------- =_aaaaaaaaaa3
  60 Content-Type: application/octet-stream
  61 Content-ID: <20592.1022586929.7@example.com>
  62 Content-Description: patch3
  63 Content-Transfer-Encoding: base64
  64
  65 XXX
  66
  67 ------- =_aaaaaaaaaa3
  68 Content-Type: application/octet-stream
  69 Content-ID: <20592.1022586929.8@example.com>
  70 Content-Description: patch4
  71 Content-Transfer-Encoding: base64
  72
  73 XXX
  74
  75 ------- =_aaaaaaaaaa3--
  76
  77 ------- =_aaaaaaaaaa1
  78 Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa4"
  79 Content-ID: <20592.1022586929.10@example.com>
  80
  81 ------- =_aaaaaaaaaa4
  82 Content-Type: application/octet-stream
  83 Content-ID: <20592.1022586929.11@example.com>
  84 Content-Description: patch5
  85 Content-Transfer-Encoding: base64
  86
  87 XXX
  88
  89 ------- =_aaaaaaaaaa4
  90 Content-Type: application/octet-stream
  91 Content-ID: <20592.1022586929.12@example.com>
  92 Content-Description: patch6
  93 Content-Transfer-Encoding: base64
  94
  95 XXX
  96
  97 ------- =_aaaaaaaaaa4--
  98
  99 ------- =_aaaaaaaaaa1--
 100
 101 ------- =_aaaaaaaaaa0
 102 Content-ID: <20592.1022586929.15@example.com>
 103 MIME-Version: 1.0
 104 Content-Type: text/plain; charset="utf-8"
 105 X-MIME-Autoconverted: from us-ascii to utf-8 by test id mimedecode
 106
 107 --
 108 It's never too late to have a happy childhood.
 109
 110 ------- =_aaaaaaaaaa0--