testmsgs/multi-2evil.xml

   1 <message>\r
   2 <header>\r
   3 <field>\r
   4 Return-Path: eryq@rhine.gsfc.nasa.gov</field>\r
   5 <field>\r
   6 Sender: john-bigboote</field>\r
   7 <field>\r
   8 Date: Thu, 11 Apr 1996 01:10:30 -0500</field>\r
   9 <field>\r
  10 From: Eryq &lt;eryq@rhine.gsfc.nasa.gov&gt;</field>\r
  11 <field>\r
  12 Organization: Yoyodyne Propulsion Systems</field>\r
  13 <field>\r
  14 X-Mailer: Mozilla 2.0 (X11; I; Linux 1.1.18 i486)</field>\r
  15 <field>\r
  16 MIME-Version: 1.0</field>\r
  17 <field>\r
  18 To: john-bigboote@eryq.pr.mcs.net</field>\r
  19 <field>\r
  20 Subject: Two images for you...</field>\r
  21 <field>\r
  22 Content-Type: multipart/mixed; boundary="------------299A70B339B65A93542D2AE"</field>\r
  23 </header>\r
  24 <multipart>\r
  25 <preamble>\r
  26 This is a multi-part message in MIME format.\r
  27 </preamble>\r
  28 <body-part>\r
  29 <header>\r
  30 <field>\r
  31 Content-Type: text/plain; charset=us-ascii</field>\r
  32 <field>\r
  33 Content-Transfer-Encoding: 7bit</field>\r
  34 </header>\r
  35 <body>\r
  36 When unpacked, this message should produce two GIF files:\r
  37 \r
  38         * The 1st should be called "3d-compress.gif"\r
  39         * The 2nd should be called "3d-eye.gif"\r
  40 \r
  41 Different ways of specifying the filenames have been used.\r
  42 \r
  43 -- \r
  44    ____           __\r
  45   / __/__________/_/  Eryq (eryq@rhine.gsfc.nasa.gov)\r
  46  / __/ _/ / / , /     Hughes STX Corporation, NASA/Goddard\r
  47 /___/_/ \  /\  /___ \r
  48         /_/ /_____/   http://selsvr.stx.com/~eryq/\r
  49 </body>\r
  50 </body-part>\r
  51 <body-part>\r
  52 <header>\r
  53 <field>\r
  54 Content-Type: image/gif</field>\r
  55 <field>\r
  56 Content-Transfer-Encoding: base64</field>\r
  57 <field>\r
  58 Content-Disposition: inline; filename="/evil/because:of\path\3d-=?ISO-8859-1?Q?=63?=om=?US-ASCII*EN?Q?pr?=ess.gif"</field>\r
  59 </header>\r
  60 <body>\r
  61 R0lGODdhKAAoAOMAAAAAAAAAgB6Q/y9PT25ubnCAkKBSLb6+vufn5/Xes/+lAP/6zQAAAAAA\r
  62 AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJLMOyYbcoxkaZ5oCkoH6L5wLMfiWqd4btZhmxbA\r
  63 oFCY47EIqMJgyWw2ATjj7aRkAq5YwDMl9VGtKO0SiuoiTVlscsxt9c4HgXxUIA0EAVOVfDKT\r
  64 8Hl1B3kDAYYle202XnGGgoMHhYckiWVuR3+OTgCGeZRslotwgJ2lnYigfZdTjQULr7ALBZN0\r
  65 qTurjHgLKAu0B5Wqopm7J72etQN8t8Ijury+wMtvw8/Hv7Ylfs0BxCbGqMmK0yOOQ0GTCgrR\r
  66 2bhwJGlXJQYG6mMKoeNoWSbzCWIACe5JwxQm3AkDAbUAQCiQhDZEBeBl6afgCsOBrD45edIv\r
  67 QceGWSMevpOYhl6CkydBHhBZQmGKjihVshypjB9ClAHZMTugzOU7mzhBPiSZ5uDNnA7b/aTZ\r
  68 0mhMnfl0pDBFa6bUElSPWb0qtYuHrxlwcR17YsWMs2jTql3LFkQEADs=</body>\r
  69 </body-part>\r
  70 <body-part>\r
  71 <header>\r
  72 <field>\r
  73 Content-Type: image/gif; name="3d-eye-is-an-evil-filename because of excessive length and verbosity.  Unfortunately what can we do given an idiotic situation such as this?"</field>\r
  74 <field>\r
  75 Content-Transfer-Encoding: base64</field>\r
  76 </header>\r
  77 <body>\r
  78 R0lGODdhKAAoAPMAAAAAAAAAzN3u/76+voiIiG5ubszd7v///+fn5wAAAAAAAAAAAAAAAAAA\r
  79 AAAAAAAAACwAAAAAKAAoAAAE/hDJSau9eJbMOy4bMoxkaZ5oCkoD6L5wLMfiWns41oZt7lM7\r
  80 VujnC96IRVsPWQE4nxPjkvmsQmu8oc/KBUSVWk7XepGGLeNrxoxJO1MjILjthg/kWXQ6wO/7\r
  81 +3dCeRRjfAKHiImJAV+DCF0BiW5VAo1CElaRh5NjlkeYmpyTgpcTAKGiaaSfpwKpVQaxVatL\r
  82 rU8GaQdOBAQAB7+yXliXTrgAxsW4vFabv8BOtBsBt7cGvwCIT9nOyNEIxuC4zrqKzc9XbODJ\r
  83 vs7Y5ewH3d7Fxe3jB4rj8t6PuNa6r2bhKQXN17FYCBMqTGiBzSNhx5g0nEMhlsSJjiRYvDjw\r
  84 E0cdGxQ/gswosoKUkmuU2FnJcsSKGTBjypxJsyaICAA7</body>\r
  85 </body-part>\r
  86 <epilogue>\r
  87 That was a multi-part message in MIME format.\r
  88 \r
  89 </epilogue>\r
  90 </multipart>\r
  91 </message>\r