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