testmsgs/multi-nested_decoded.mime4j.xml

   1 <message>\r
   2 <header>\r
   3 <field>\r
   4 MIME-Version: 1.0</field>\r
   5 <field>\r
   6 From: Lord John Whorfin &lt;whorfin@yoyodyne.com&gt;</field>\r
   7 <field>\r
   8 To: &lt;john-yaya@yoyodyne.com&gt;</field>\r
   9 <field>\r
  10 Subject: A complex nested multipart example</field>\r
  11 <field>\r
  12 Content-Type: multipart/mixed;\r
  13      boundary=unique-boundary-1</field>\r
  14 </header>\r
  15 <multipart>\r
  16 <preamble>\r
  17 The preamble of the outer multipart message.\r
  18 Mail readers that understand multipart format\r
  19 should ignore this preamble.\r
  20 If you are reading this text, you might want to\r
  21 consider changing to a mail reader that understands\r
  22 how to properly display multipart messages.</preamble>\r
  23 <body-part>\r
  24 <header>\r
  25 </header>\r
  26 <text-body name="multi-nested_decoded_1_1.txt"/>\r
  27 </body-part>\r
  28 <body-part>\r
  29 <header>\r
  30 <field>\r
  31 Content-type: text/plain; charset=US-ASCII</field>\r
  32 </header>\r
  33 <text-body name="multi-nested_decoded_1_2.txt"/>\r
  34 </body-part>\r
  35 <body-part>\r
  36 <header>\r
  37 <field>\r
  38 Subject: Part 3 of the outer message is multipart!</field>\r
  39 <field>\r
  40 Content-Type: multipart/parallel;\r
  41      boundary=unique-boundary-2</field>\r
  42 </header>\r
  43 <multipart>\r
  44 <preamble>\r
  45 A one-line preamble for the inner multipart message.</preamble>\r
  46 <body-part>\r
  47 <header>\r
  48 <field>\r
  49 Content-Type: image/gif</field>\r
  50 <field>\r
  51 Content-Transfer-Encoding: base64</field>\r
  52 <field>\r
  53 Content-Disposition: inline; filename="3d-vise.gif"</field>\r
  54 <field>\r
  55 Subject: Part 1 of the inner message is a GIF, "3d-vise.gif"</field>\r
  56 </header>\r
  57 <binary-body name="multi-nested_decoded_1_3_1.bin"/>\r
  58 </body-part>\r
  59 <body-part>\r
  60 <header>\r
  61 <field>\r
  62 Content-Type: image/gif</field>\r
  63 <field>\r
  64 Content-Transfer-Encoding: base64</field>\r
  65 <field>\r
  66 Content-Disposition: inline; filename="3d-eye.gif"</field>\r
  67 <field>\r
  68 Subject: Part 2 of the inner message is another GIF, "3d-eye.gif"</field>\r
  69 </header>\r
  70 <binary-body name="multi-nested_decoded_1_3_2.bin"/>\r
  71 </body-part>\r
  72 <epilogue>\r
  73 \r
  74 The epilogue for the inner multipart message.\r
  75 </epilogue>\r
  76 </multipart>\r
  77 </body-part>\r
  78 <body-part>\r
  79 <header>\r
  80 <field>\r
  81 Content-type: text/richtext</field>\r
  82 </header>\r
  83 <text-body name="multi-nested_decoded_1_4.txt"/>\r
  84 </body-part>\r
  85 <body-part>\r
  86 <header>\r
  87 <field>\r
  88 Content-Type: message/rfc822; name="/evil/filename";</field>\r
  89 </header>\r
  90 <message>\r
  91 <header>\r
  92 <field>\r
  93 From: (mailbox in US-ASCII)</field>\r
  94 <field>\r
  95 To: (address in US-ASCII)</field>\r
  96 <field>\r
  97 Subject: Part 5 of the outer message is itself an RFC822 message!</field>\r
  98 <field>\r
  99 Content-Type: Text/plain; charset=ISO-8859-1</field>\r
 100 <field>\r
 101 Content-Transfer-Encoding: Quoted-printable</field>\r
 102 </header>\r
 103 <text-body name="multi-nested_decoded_1_5_1.txt"/>\r
 104 </message>\r
 105 </body-part>\r
 106 <epilogue>\r
 107 \r
 108 The epilogue for the outer message.\r
 109 \r
 110 </epilogue>\r
 111 </multipart>\r
 112 </message>\r