diff options
Diffstat (limited to 'unittest/data/parser/input/mbox/jwz/61')
| -rw-r--r-- | unittest/data/parser/input/mbox/jwz/61 | 55 |
1 files changed, 55 insertions, 0 deletions
diff --git a/unittest/data/parser/input/mbox/jwz/61 b/unittest/data/parser/input/mbox/jwz/61 new file mode 100644 index 00000000..5215c58c --- /dev/null +++ b/unittest/data/parser/input/mbox/jwz/61 @@ -0,0 +1,55 @@ +Path: flop.mcom.com!news.Stanford.EDU!agate!library.ucla.edu!info.ucla.edu!csulb.edu!paris.ics.uci.edu!ucivax!gateway +From: moore@cs.utk.edu (Keith Moore) +Subject: Re: MIME Content-MD5 header +Message-ID: <199508140639.CAA17658@wilma.cs.utk.edu> +In-reply-to: Your message of "Fri, 11 Aug 1995 09:34:10 BST." + <Q9+PDBACYxKwIAQs@turnpike.com> +content-type: multipart/mixed; boundary="frotz" +MIME-Version: 1.0 +Newsgroups: comp.mail.mime +Lines: 42 +Date: 14 Aug 95 06:39:48 GMT +X-URI: http://www.cs.utk.edu/‾moore/ + +--frotz +content-type: text/plain; charset=us-ascii + +> Thanks for the pointers to mpack/munpack - but we are left with a +> mystery. We were emailed a quoted printable message containing an MD5 +> signature by Yanling Qi using "CDE dtmail". However, although our MD5 +> calculations agree with mpack/munpack, I can't get either to agree with +> the Content-MD5 header on that message. (However, munpack won't directly +> decode the message so I have to decode it first and see what MD5 mpack +> puts on it when its re-encoded!). +> +> We are uncertain where the problem lies, so we would be grateful for +> some more examples of quoted printable text with Content-MD5 headers. + +My guess would be that one of the implementations is not using the +canonical form for end-of-line in text/plain. The newlines in a +quoted-printable should be interpreted as 0D 0A for the purpose of +computing MD5 (as for all other purposes). I'll bet one or more of +the implementations is treating it as either just 0D or just 0A, so +you get a different MD5 value. + +Here is the same file encoded twice: one in quoted-printable, another +in base64. They have the same canonical form and thus the same MD5. +See whether they get the same MD5 on your system: + +--frotz +Content-type: text/plain; charset=us-ascii +content-transfer-encoding: quoted-printable +content-md5: JBUsEwk6AEsrJxeDnYDj2g== + +=46rom moore@cs.utk.edu Mon Aug 14 01:49:07 1995 +=46rom moore@cs.utk.edu Mon Aug 14 01:51:53 1995 +=46rom moore@cs.utk.edu Mon Aug 14 02:17:26 1995 +--frotz +Content-type: text/plain; charset=us-ascii +content-transfer-encoding: base64 +content-md5: JBUsEwk6AEsrJxeDnYDj2g== + +RnJvbSBtb29yZUBjcy51dGsuZWR1IE1vbiBBdWcgMTQgMDE6NDk6MDcgMTk5NQ0KRnJvbSBtb29y +ZUBjcy51dGsuZWR1IE1vbiBBdWcgMTQgMDE6NTE6NTMgMTk5NQ0KRnJvbSBtb29yZUBjcy51dGsu +ZWR1IE1vbiBBdWcgMTQgMDI6MTc6MjYgMTk5NQ0K +--frotz-- |