attachment error relating to MIME boundary

J

joesavona

Hi,
I'm trying to open some email with Outlook and Outlook Express and keep
getting errors with the attachments they contain. Outlook/OE both
recognize that an attachment is present and show the correct filename,
but the application (excel, winzip, powerpoint) fails upon opening the
attachment, claiming a corrupt file. If I change the message source
first, so that there is a blank line after the base 64 encoded file
body (2 CRLF's instead of just one, see bottom of my post) and before
the MIME boundary, the programs do not complain. Having only a single
CRLF is RFC compliant, and the attachments open properly when the email
is read with other clients. Is this a known bug? Thanks in advance for
the help,

Joe

for example:

this fails in Outlook/OE (though not for a .doc or .pdf):
......message body, beginning of base64 encoded attachment...
319024327419237491273491723417932479
--boundary1234

this works in all clients:
......message body, beginning of base64 encoded attachment...
319024327419237491273491723417932479

--boundary1234
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

removed attachment is still there but not accessible (OL 2003) 7
Attachment encoding problem 1
HTML Body Appears as Attachment 0
MIME-encoded emails not displaying properly, why? 0
Some Internet Headers stripped, even when fwd as attachment in OL2 2
outlook 2003 + vista mail problem 3
Mixed-up Email Messages 1
Lotus user to Outlook user Attachments missing 0

Top