test/input/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 ------- =_aaaaaaaaaa1
  23 and
  24 ------- =_aaaaaaaaaa0
  25 but puts them at the start of a line! And, to be even nastier, it
  26 even includes a couple of end tags, such as this one:
  27
  28 ------- =_aaaaaaaaaa1--
  29
  30 and this one, which is from a multipart we haven't even seen yet!
  31
  32 ------- =_aaaaaaaaaa4--
  33
  34 This will, I'm sure, cause much breakage of MIME parsers. But, as
  35 far as I can tell, it's perfectly legal. I have not yet ever seen
  36 a case of this in the wild, but I've seen *similar* things.
  37
  38
  39 ------- =_aaaaaaaaaa2
  40 Content-Type: application/octet-stream
  41 Content-ID: <20592.1022586929.4@example.com>
  42 Content-Description: patch2
  43 Content-Transfer-Encoding: base64
  44
  45 XXX
  46
  47 ------- =_aaaaaaaaaa2--
  48
  49 ------- =_aaaaaaaaaa1
  50 Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa3"
  51 Content-ID: <20592.1022586929.6@example.com>
  52
  53 ------- =_aaaaaaaaaa3
  54 Content-Type: application/octet-stream
  55 Content-ID: <20592.1022586929.7@example.com>
  56 Content-Description: patch3
  57 Content-Transfer-Encoding: base64
  58
  59 XXX
  60
  61 ------- =_aaaaaaaaaa3
  62 Content-Type: application/octet-stream
  63 Content-ID: <20592.1022586929.8@example.com>
  64 Content-Description: patch4
  65 Content-Transfer-Encoding: base64
  66
  67 XXX
  68
  69 ------- =_aaaaaaaaaa3--
  70
  71 ------- =_aaaaaaaaaa1
  72 Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa4"
  73 Content-ID: <20592.1022586929.10@example.com>
  74
  75 ------- =_aaaaaaaaaa4
  76 Content-Type: application/octet-stream
  77 Content-ID: <20592.1022586929.11@example.com>
  78 Content-Description: patch5
  79 Content-Transfer-Encoding: base64
  80
  81 XXX
  82
  83 ------- =_aaaaaaaaaa4
  84 Content-Type: application/octet-stream
  85 Content-ID: <20592.1022586929.12@example.com>
  86 Content-Description: patch6
  87 Content-Transfer-Encoding: base64
  88
  89 XXX
  90
  91 ------- =_aaaaaaaaaa4--
  92
  93 ------- =_aaaaaaaaaa1--
  94
  95 ------- =_aaaaaaaaaa0
  96 Content-Type: text/plain; charset="us-ascii"
  97 Content-ID: <20592.1022586929.15@example.com>
  98
  99 --
 100 It's never too late to have a happy childhood.
 101
 102 ------- =_aaaaaaaaaa0--