Re: Munged attachment names (again?)

From: Tom von Alten <>
Date: Tue, 30 Nov 1999 10:49:37 -0700 (MST)
Message-Id: <>

Here is a sample message that shows the attachment naming problem. Hopefully, I've kept the essential bits after eliding the content. v2b27 named and tagged the file as:

  <LI>application/octet-stream attachment:   <A HREF="att-0011/01-imeDxtr.doc_">imeDxtr.doc_</A>

It looks like it might be as simple as recognizing/handling filenames whether or not they're quoted?!

Tom von Alten

This posting is for informational purposes only and is provided with no warranty of any kind. It is not a statement of the Hewlett-Packard Co.

>From Tue Nov 30 06:33:09 MST 1999

To: <>
Message-ID: <0056900005659777000002L072*_at_MHS> Date: Tue, 30 Nov 1999 14:23:28 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="Boundary=_0.0_=0056900005659777" Status: R


Content-Type: text/plain; charset=iso-8859-1; name="MEMO 11/30/99 14:21:34"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Some mime q-p text


Content-Type: application/octet-stream; name=TimeDxtr.doc
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=TimeDxtr.doc


--Boundary=_0.0_=0056900005659777-- Received on Tue 30 Nov 1999 09:03:40 PM GMT

This archive was generated by hypermail 2.3.0 : Sat 13 Mar 2010 03:46:11 AM GMT GMT