RE: octet-stream attachment

---------

From: Tom von Alten (tom_vonalten@boi.hp.com)
Date: Mon Aug 02 1999 - 09:07:55 CDT


Well, I captured a message sent directly to me, with a PDF and a JPG attachment, before Outlook got its hands on it. (If I forward
from Outlook back to the archive, it works correctly - that's testing Outlook, not the Notes system that I think has the problem.)

The bad (?) news is that v2a23 handled this message properly, and the filenames did NOT get the "_" appended to their suffixes.
It's still misconfigured in that the jpeg should be better identified from the sender than "application/octet-stream attachment"
(imho - so I can inline the images the way I want to).

But with this one message, at least, the earlier problem does not repeat. :-/ I'll keep trying to capture a message that does show
the problem.

A synopsis of the "ok" message is attached, with a single space indent. (I tried to tell Outlook not to wrap the lines, but the
first two Content-Type headers may wrap; they're all on one line in the original.)

_____________ Hewlett-Packard Computer Peripherals Bristol
Tom von Alten mailto:Tom_vonAlten@boi.hp.com

          This posting is for informational purposes only.
          It is not a statement of the Hewlett-Packard Co.

 From sender@host.domain Mon Aug 2 00:04:08 MDT 1999
 Subject: Test-Mail
 Message-ID: <0056900002735610000002L002*@MHS>
 Date: Mon, 2 Aug 1999 08:00:22 -0400
 MIME-Version: 1.0
 Content-Type: multipart/mixed; boundary="Boundary=_0.0_=0056900002735610"

 --Boundary=_0.0_=0056900002735610
 Content-Type: text/plain; charset=iso-8859-1; name="MEMO 08/02/99 07:59:59"
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline

 Text deleted

 --Boundary=_0.0_=0056900002735610
 Content-Type: application/octet-stream; name=grab002.JPG
 Content-Transfer-Encoding: base64
 Content-Disposition: attachment; filename=grab002.JPG

 encoded bits deleted

 --Boundary=_0.0_=0056900002735610
 Content-Type: application/octet-stream;
               name="testing pdf weirdly named.pdf"
 Content-Transfer-Encoding: base64
 Content-Disposition: attachment; filename="testing pdf weirdly
                      named.pdf"

 encoded bits deleted

 --Boundary=_0.0_=0056900002735610--


---------

This archive was generated by hypermail 2.1.5.