PageRenderTime 101ms CodeModel.GetById 20ms app.highlight 2ms RepoModel.GetById 19ms app.codeStats 10ms

/Lib/email/test/data/msg_38.txt

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