Messages and attachments not decoding properly in Outlook 2003

[DC]

A few emails I have received lately with attachments have not been decoding
properly. They come through as raw text without even having subjects or
sender info displayed. It seems to happen with HTML messages and things
encoded in base64 with the transfer encoding being quoted-printable. Here is
the only common links I have found in the raw text-


Content-Type: multipart/mixed;
boundary="--6c963a6c2aa62a54"
This is a multi-part message in MIME format.
----6c963a6c2aa62a54
Content-Disposition: inline
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Content-Type: multipart/mixed;
boundary="----=_NextPart_000_000E_01C64CF7.AB678880"
This is a multi-part message in MIME format.
------=_NextPart_000_000E_01C64CF7.AB678880
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_000F_01C64CF7.AB678880"
This is a multi-part message in MIME format.
------=_NextPart_001_000F_01C64CF7.AB678880
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="us-ascii";format=flowed

That's info from 2 of them. They both had base64 attachments. They both have
Content-Type: multipart/mixed; and Content-Transfer-Encoding:
quoted-printable. Is there any way to fix this issue? I can copy and decode
the files by hand, but with larger files it's a huge pain. Is it possible
that this is an ISP issue and not Outlook? Lastly it seems to happen the
most when the email comes from a Mac users.

 

[Brian Tillman]

A few emails I have received lately with attachments have not been
decoding properly. They come through as raw text without even having
subjects or sender info displayed. It seems to happen with HTML
messages and things encoded in base64 with the transfer encoding
being quoted-printable. Here is the only common links I have found in
the raw text-

Outlook 2003 has no trouble with either Base64 or Quoted-Printable encoding.
If you are seeing the raw data instead of the decoded message, then
something PRIOR to the headers you included may be causing the issue.

 

[DC]

It seems to be mostly when I get email from Mac users.

 

[Brian Tillman]

It seems to be mostly when I get email from Mac users.

Outlook seems to be fairly unforgiving when it comes to variations in the
message headers. Perhaps the Macs are adding something Outlook doesn't
expect or removing something it can't live without and confusing it as to
where the parts of the message occur. It may help if yiou could post the
complete headers (changing IP addresses and mail addresses if needed to keep
things anonymous) and perhaps someone will spot the difference.

 

[DC]

This is the header that appears in the body of the message-

Received: from [255.255.255.255] (helo=priv-edtnes10.myisp.net)by
mx.perfora.net (node=mxus0) with ESMTP (Nemesis),

id 0MKuxu-1FQvw12PKi-00043U for (e-mail address removed);

Tue, 04 Apr 2006 20:31:46 -0400

Received: from priv-edtnaa05.myisp.net ([255.255.255.255]) by
priv-edtnes10.myisp.net (InterMail vM.6.01.05.04
201-2131-123-105-20051025) with ESMTP id
<20060405003144.PQAV11104.priv-edtnes10.myisp.net@priv-edtnaa05.myisp.net>
for <[email protected]>;

Tue, 4 Apr 2006 18:31:44 -0600

Received: from [192.168.0.104] (s142-179-167-137.ab.hsia.myisp.net
[255.255.255.255])by priv-edtnaa05.myisp.net (BorderWare MXtreme Infinity
Mail Firewall) with ESMTP id 1FSX4GR4KNfor <[email protected]>;

Tue, 4 Apr 2006 18:31:41 -0600 (MDT)

Mime-Version: 1.0 (Apple Message framework v623)

To: Me <[email protected]>

Message-Id: <[email protected]>

From: Him <[email protected]>

Subject: from my sister

Date: Tue, 4 Apr 2006 17:32:19 -0600

X-Mailer: Apple Mail (2.623)

Envelope-To: (e-mail address removed)

Content-Type: multipart/mixed;

boundary="Apple-Mail-1-530099239"



This is a multi-part message in MIME format.



--Apple-Mail-1-530099239

Content-Type: text/plain;

charset=US-ASCII;format=flowed

Content-Transfer-Encoding: quoted-printable



Does that give any clues?

 

[Brian Tillman]

This is the header that appears in the body of the message-

Received: from [255.255.255.255] (helo=priv-edtnes10.myisp.net)by
mx.perfora.net (node=mxus0) with ESMTP (Nemesis),

id 0MKuxu-1FQvw12PKi-00043U for (e-mail address removed);

Tue, 04 Apr 2006 20:31:46 -0400

Received: from priv-edtnaa05.myisp.net ([255.255.255.255]) by
priv-edtnes10.myisp.net (InterMail vM.6.01.05.04
201-2131-123-105-20051025) with ESMTP id
<20060405003144.PQAV11104.priv-edtnes10.myisp.net@priv-edtnaa05.myisp.net>
for <[email protected]>;

Tue, 4 Apr 2006 18:31:44 -0600

If it's exactly like this, it's no wonder you're having trouble with so many
embedded blank lines.

 

[DC]

Actually no, for some reason it came out like that when I pasted it.

This is the header that appears in the body of the message-

Received: from [255.255.255.255] (helo=priv-edtnes10.myisp.net)by
mx.perfora.net (node=mxus0) with ESMTP (Nemesis),

id 0MKuxu-1FQvw12PKi-00043U for (e-mail address removed);

Tue, 04 Apr 2006 20:31:46 -0400

Received: from priv-edtnaa05.myisp.net ([255.255.255.255]) by
priv-edtnes10.myisp.net (InterMail vM.6.01.05.04
201-2131-123-105-20051025) with ESMTP id
<20060405003144.PQAV11104.priv-edtnes10.myisp.net@priv-edtnaa05.myisp.net>
for <[email protected]>;

Tue, 4 Apr 2006 18:31:44 -0600

If it's exactly like this, it's no wonder you're having trouble with so
many embedded blank lines.

 

[Brian Tillman]

Actually no, for some reason it came out like that when I pasted it.

Then please post the EXACT headers.