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_at_boi.hp.com
This posting is for informational purposes only. It is not a statement of the Hewlett-Packard Co.
From sender_at_host.domain Mon Aug 2 00:04:08 MDT 1999
Subject: Test-Mail
Message-ID: <0056900002735610000002L002*_at_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--
Received on Mon 02 Aug 1999 04:10:15 PM GMT
This archive was generated by hypermail 2.3.0 : Sat 13 Mar 2010 03:46:11 AM GMT GMT