MIME attachment appearing as text. Help
ABC
Party A( Outlook 2000) sends me an email with attachment.
I(Eudora7.1) received the email with the attachment as a text garble.
In fact the entire message was not properly decoded, with all the raw
message headers appearing like this:
"X-server-Uuid:
X- Archive-out
X-Wss-ID:
etc.
This is a multi-part message in MIME format
..............."
This only happens with party A and me. I can ask A to send the email
to my friend who receives it with the attachment properly. Friend can
then forward the email to me and it is also OK.
I also have no problem with attachments from any other persons. Party
A has not problem sending attachment to any other person.
Any clue what could have cause my Eudora to refuse to decode the MIME
attachment??
Any suggestion appreciated.
ABC
John H Meyers
> an email with attachment... was not properly decoded
> This only happens with party A and me. I can ask A to send the email
> to my friend who receives it with the attachment properly.
> Friend can then forward the email to me and it is also OK.
Have the sender put both you and the other person
in the "To:" field of one message, to better assure that
you both receive identical messages.
Post the complete headers, after pressing the "Blah blah" button
in the received message window, and copy everything until the message
body begins, obscuring any actual email addresses as "xxx...@xxxx.xxx"
It might be useful to continue with the entire message,
removing the content of each section, but retaining
the headers of each section.
An even better way to do this would be to set "leave mail on server"
before having Eudora check for mail, then use a "webmail" application
(provided by an ISP, or by mail2web.com or myemail.com)
to display the "original" (raw) message,
exactly as it resides on the POP server,
and copy it from this unprocessed source,
upstream from where Eudora ever sees it.
Or, have a copy sent as well to your Gmail account
(sign up for one if you don't already have one),
because Gmail also has a built-in "show original" function,
which faithfully presents the original, exactly as received.
A second email client on your own computer can also serve
as a "verifier" of everything else in your own local environment,
including receiving the message via your own local ISP
(setting the "leave mail on server" option
is useful for such "parallel testing" of two POP clients).
Are you, by the way,
limiting the maximum size of messages that Eudora may download?
("Incoming mail" - "skip messages over [NN]k in size")
Or is your ISP limiting the maximum message size?
--
John H Meyers
> an email with attachment... was not properly decoded
> This only happens with party A and me. I can ask A to send the email
> to my friend who receives it with the attachment properly.
> Friend can then forward the email to me and it is also OK.
By the way, what programs (see any "X-Mailer:" headers)
are the other two parties using?
--
ABC
<jhme...@nomail.invalid> wrote:
>Post the complete headers, after pressing the "Blah blah" button
>in the received message window, and copy everything until the message
>body begins, obscuring any actual email addresses as "xxx...@xxxx.xxx"
>
Thanks. here are the headers. It appears to be a problem where my
Eudora refuses to decode the MIME. I can see the line " This is a
multi-part message in MIME format." in the failed message. Also the
line :"MIME-Version: 1.0" is missing . This line is NOT missing in
the other emails I received from other people using OE 6 where I can
receive the attachment.
The sender uses Outlook 2000
I will post the webmail version when I get them:
**********************************************************************************
Received by Outlook Express 6( attachment properly decoded)
Return-Path: <xxxxxxx@xxxxxxxxxxx>
Received: from mail.hastings-hk.com (mail.hastings-hk.com
[203.198.157.145])
by linux.hastings-hk.com (8.13.3/8.13.3/SuSE Linux 0.7) with
SMTP id l938vCBl009608;
Wed, 3 Oct 2007 16:57:18 +0800
Message-Id: <200710030857....@linux.hastings-hk.com>
Received: from guardian2.dahsing.com ([202.64.240.15])
by mail.hastings-hk.com (SMSSMTP 4.1.11.41) with SMTP id
M2007100316275512701
; Wed, 03 Oct 2007 16:27:55 +0800
X-Server-Uuid: 44FEAE7E-1455-4FB3-9A87-5A15D3C4EF66
content-class: urn:content-classes:message
Subject: Testing ...
Date: Wed, 3 Oct 2007 16:31:43 +0800
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Testing ...
Thread-Index: AcgFl9OM1htS3y1jRqW9HZAJtCRfnA==
From: "Teddy Kwok" <xxxxxxxxx@xxxxxxx>
To: "Tommy Wong (E-mail)" <yyy@yyyyyyy>,
"Tommy Wong2 (E-mail)" <zzzz@zzzzzzz>, aa...@aaaaa.com
X-Archive-Out: Out
X-WSS-ID: 6B1D8CFA26C993244-01-01
Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C80597.D438392E"
X-UIDL: U"Q"!$'e"!ZC-"!pe)#!
*************************************************************************************
As received by Eudora (attachment NOT decoded)
Return-Path: <xxxxxx@xxxxxx>
Received: from mail.hastings-hk.com (mail.hastings-hk.com
[203.198.157.145])
by linux.hastings-hk.com (8.13.3/8.13.3/SuSE Linux 0.7) with
SMTP id l938vCBl009608;
Wed, 3 Oct 2007 16:57:18 +0800
Message-Id: <200710030857....@linux.hastings-hk.com>
Received: from guardian2.dahsing.com ([202.64.240.15])
by mail.hastings-hk.com (SMSSMTP 4.1.11.41) with SMTP id
M2007100316275512701
; Wed, 03 Oct 2007 16:27:55 +0800
X-Server-Uuid: 44FEAE7E-1455-4FB3-9A87-5A15D3C4EF66
content-class: urn:content-classes:message
Subject: Testing ...
Date: Wed, 3 Oct 2007 16:31:43 +0800
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Testing ...
Thread-Index: AcgFl9OM1htS3y1jRqW9HZAJtCRfnA==
From: "Teddy Kwok" <xxxxxx@xxxxxx>
To: "Tommy Wong (E-mail)" <yyy@yyyyyy>,
"Tommy Wong2 (E-mail)" <zzzz@zzzzzzzz>, aa...@aaaaaaa.com
X-Archive-Out: Out
X-WSS-ID: 6B1D8CFA26C993244-01-01
Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C80597.D438392E"
X-UIDL: WD^"!ch[!!P`["!O*("!
This is a multi-part message in MIME format.
------_=_NextPart_001_01C80597.D438392E
Content-Type: text/plain;
charset=big5
Content-Transfer-Encoding: quoted-printable
<<01.jpg>>=20
********************************************************************************************
Outlook express 6 forward whole email to Eudora( Attachment decoded
OK)
Return-Path: <zzzz@zzzzzzzzzz>
Received: from mail.hastings-hk.com (mail.hastings-hk.com
[203.198.157.145])
by linux.hastings-hk.com (8.13.3/8.13.3/SuSE Linux 0.7) with
SMTP id l93AYe4w013867
for <yyy@yyyyyyyyy>; Wed, 3 Oct 2007 18:34:42 +0800
Received: from imsantv36.netvigator.com ([210.87.250.140])
by mail.hastings-hk.com (SMSSMTP 4.1.11.41) with SMTP id
M2007100318051614263
for <yyy@yyyyyyyy>; Wed, 03 Oct 2007 18:05:16 +0800
Received: from imsantv40.netvigator.com (imsantv36 [127.0.0.1])
by imsantv36.netvigator.com (8.13.8/8.13.1) with ESMTP id
l93AACkZ027409
for <yyy@yyyyyyyy>; Wed, 3 Oct 2007 18:10:12 +0800
Received: from edwinng (ipvpn084158.netvigator.com [203.198.157.158])
by imsantv40.netvigator.com (8.13.8/8.13.8) with SMTP id
l93AA7wF005144
for <yyy@yyyyyyyy>; Wed, 3 Oct 2007 18:10:07 +0800
Message-ID: <000e01c805a5$9a804760$1ec0c0c0@edwinng>
Reply-To: "Jannie Chan" <zzzz@zzzzzzzzzz>
From: "Jannie Chan" <zzzz@zzzzzzzzzz>
To: "Wong Tommy" <yyy@yyyyyyyy>
Subject: Fw: Testing ...
Date: Wed, 3 Oct 2007 18:10:19 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_000B_01C805E8.A86063E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-UIDL: 5Zm"!1V)!!=<`"!2SN"!
----- Original Message -----
From: "Teddy Kwok" <xxxxxxx@xxxxxxxxxxx>
,,,,,,,etc.
**************************************************************************************************
Any help appreciated
ABC
ABC
>Or, have a copy sent as well to your Gmail account
>(sign up for one if you don't already have one),
>because Gmail also has a built-in "show original" function,
>which faithfully presents the original, exactly as received.
Experiment just finished, Yes. The same email(with the attachment)
sent to my other accout,using another instance of Eudora 7.1, is also
bad(non-decoded).
The same email sent to my ISP's webmail is also received as text. Same
problem. Line "MIME-version: 1.0" is not there.
It seems email and attachment from this guy's Outlook 2000 can only be
decoded by Outlook.
any help appreciated.
ABC
John H Meyers
> The same email sent to my ISP's webmail is also received as text.
> Same problem. Line "MIME-version: 1.0" is not there.
>
> It seems email and attachment from this guy's Outlook 2000
> can only be decoded by Outlook.
> Content-Type: multipart/mixed;
> boundary="----_=_NextPart_001_01C80597.D438392E"
That identifies a string used to separate the body into distinct parts,
each of which has its own header.
> ------_=_NextPart_001_01C80597.D438392E
> Content-Type: text/plain;
> charset=big5
> Content-Transfer-Encoding: quoted-printable
That's the header of one part, identified as a type (text/plain)
which is supposed to be displayed in-line (in the message body window);
if what follows is not readable text,
then the message wasn't properly constructed.
Where's another similar header for any other part,
such as an attachment that isn't supposed to be displayed?
If you search for the same string as was originally identified
as the "boundary" string, then you should be able to find
all remaining headers; HOWEVER: Eudora may strip some of these,
and in particular removes all non-inline attachments (and their headers),
so only _other_ programs (Outlook Express, Gmail, some Webmail sites)
actually show a true view of the _original_ (raw) message,
exactly as it came from the POP server.
> X-MS-TNEF-Correlator:
Outlook, in particular, can be set to send mail in only a proprietary format,
in which there would be an attachment with a file name "winmail.dat"
which then contains all the other attachments (even any HTML part, I believe);
Outlook Express, being itself another Microsoft proprietary product,
expects and handles this format, which was never adopted as an internet standard,
but other mail clients, such as Eudora, simply store that (if sent properly)
as an attached file, and do not attempt to look inside to understand it.
This proprietary "winmail.dat" format is suitable for intra-company email
within an organization which forces all its members to use it,
but sometimes people within such organizations forget to change that,
when sending to people outside of their own company,
in which case those recipients are often unable to read their mail.
At other times, senders may create _both_ a readable standard format
plus an extra "winmail.dat" attachment, in which case a recipient
can simply throw away the extra useless "winmail.dat" file.
The above information was limited to only the very first,
displayable part of your message, so I can't discern anything else,
and have added remarks about Outlook which may or may not apply to your case,
just in case it happens to be related to your situation.
About Outlook potentially sending "winmail.dat":
http://email.about.com/od/outlooktips/qt/et121705.htm
http://support.microsoft.com/kb/278061
Re "MIME-version: 1.0" header: see section 4 of
http://www.faqs.org/rfcs/rfc2045.html
http://www.ietf.org/rfc/rfc2045.txt
Although this header is declared to be mandatory,
it also says that only one MIME version exists, and:
In the absence of a MIME-Version field, a receiving mail user agent
(whether conforming to MIME requirements or not) may optionally choose
to interpret the body of the message according to local conventions.
This allows any email (or webmail) program to make its own policy,
so it's obviously better for the sending program to include the header;
I'm quite surprised if Outlook 2000 doesn't include it,
but thus far, things point to a problem on the sender's side,
and some references above suggest how the sender can correct it.
--
John H Meyers
Your sender was evidently not only using MS Outlook (as you said),
but also via a "Microsoft Exchange Server" -- better tell them
to "send real mail" :)
MS Outlook Express is obliged to accept it;
I don't know what Thunderbird does;
see what happens with Eudora if the sender
follows the instructions about "sending real mail":
http://email.about.com/od/outlooktips/qt/et121705.htm
http://support.microsoft.com/kb/278061
--
ABC
<jhme...@nomail.invalid> wrotd:
>If you search for the same string as was originally identified
>as the "boundary" string, then you should be able to find
>all remaining headers; HOWEVER: Eudora may strip some of these,
>and in particular removes all non-inline attachments (and their headers)=
Just found the attachment header right there under the virus scan
report. The text part of the message is readable just underathe first
boundary.
This is the whole header (email with an attachment called 01.jpg
garbled):
******************************************************************
Return-path: <xxxx@xxxxxx>
Envelope-to: aaa@aaaaaaa
Delivery-date: Wed, 03 Oct 2007 20:24:18 +0800
Received: from [202.60.252.12] (helo=wwwww.wwwww.com)
by atm.cyberec.com with esmtp (Exim 3.36 #1)
id 1Id3Gw-0007pe-00
for aaa@aaaaaaa; Wed, 03 Oct 2007 20:24:14 +0800
Received: from MailerDaemon by www.wwwwwww.com with local-bsmtp (Exim
4.63)
(envelope-from <xxxx@xxxxxx>)
id 1Id3HV-00006r-Ky
for aaa@aaaaaaa; Wed, 03 Oct 2007 20:24:49 +0800
Received: from mail-kr.bigfoot.com ([211.115.216.252]:1266)
by gateway.cyberec.com with smtp (Exim 4.63)
(envelope-from <xxxx@xxxxxx>)
id 1Id3HR-0008Ul-GM
for aaa@aaaaaaa; Wed, 03 Oct 2007 20:24:47 +0800
Received: from guardian2.dahsing.com ([202.64.240.15])
by BFLITEMAIL-KR5.bigfoot.com (LiteMail v3.03(BFLITEMAIL-KR5))
with SMTP id 0710031734_BFLITEMAIL-KR5_777918_3454611;
Wed, 03 Oct 2007 17:35:08 +0900 EST
X-Server-Uuid: 44FEAE7E-1455-4FB3-9A87-5A15D3C4EF66
content-class: urn:content-classes:message
Subject: Testing ...
Date: Wed, 3 Oct 2007 16:31:43 +0800
X-MS-Has-Attach: yes
Thread-Topic: Testing ...
Thread-Index: AcgFl9OM1htS3y1jRqW9HZAJtCRfnA==
From: "Teddy Kwok" <xxxx@xxxxxx>
To: "Tommy Wong (E-mail)" <yyyy@yyyyyyy>,
"Tommy Wong2 (E-mail)" <zzz@zzzzzzz>,
X-Archive-Out: Out
X-WSS-ID: 6B1D8CFA26C993244-01-01
Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C80597.D438392E"
X-cff-LastScanner: as
Message-Id: <E1Id3HV-...@wwwwwww.wwww>
X-CyberAntiVirus-MailScanner-Information: Please contact the ISP for
more information
X-CyberAntiVirus-MailScanner: Found to be clean
Status:
This is a multi-part message in MIME format.
------_=_NextPart_001_01C80597.D438392E
Content-Type: text/plain;
charset=big5
Content-Transfer-Encoding: quoted-printable
<<01.jpg>>=20
Best Regards,
Teddy Kwok
__________ NOD32 2569 (20071003) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
------_=_NextPart_001_01C80597.D438392E
Content-Type: image/jpeg;
name=01.jpg
Content-Transfer-Encoding: base64
Content-Description: 01.jpg
Content-Disposition: attachment;
filename=01.jpg
/9j/4AAQSkZJRgABAAEAyADIAAD//gAfTEVBRCBUZWNobm9sb2dpZXMgSW5jLiBWMS4wMQD/2wCE
ABkREhYSDxkWFBYcGhkeJT8pJSIiJU03Oi0/W1BgXlpQWFZlcZF7ZWuJbVZYfqx/iZaaoqSiYXmy
etc
******************************************************************************
ABC
<jhme...@nomail.invalid> wrotd:
Thanks. Will try this anyway. My problematic emails do NOT have
winmail.dat as an attachment.
Will report soon.
BTW, please explain the "Microsoft Exchange Server" point. The above
instructions seem to deal with the attachment "winmail.dat" when
sending email in Richtext format.
ABC
John H Meyers
> please explain the "Microsoft Exchange Server" point.
A "Microsoft Exchange Server" is a corporate internal mail server,
taking the place of other ISP-supplied POP/IMAP/SMTP servers;
Microsoft Outlook is designed especially to hook into it.
I would expect it to send a special header of its own, such as:
X-MimeOLE: Produced By Microsoft Exchange...
However, your posts show neither that header
nor the RFC2045 required "MIME-Version" header
(your sender might like to contact the Exchange server administrator
to find out whether they should be generating the required header,
and if they can adjust that, then it would serve them well,
when sending mail outside of their organization).
When receiving messages which do not conform to standards,
various email clients have to make their own choice about what to do.
Some clients may assume that all incoming messages are intended
to be in MIME format; this assumption will "fix" some cases,
but may end up doing worse on some other cases;
given the present day situation, where MIME is prevalent,
it might be good to make that assumption,
but if Eudora doesn't, and shows an entire message as a single "body,"
instead of separating text, html, and attachments, then it isn't "wrong,"
although of course it also doesn't compensate for sender problems,
at least not as well as some other clients may have elected to do.
Page 50 of the "Eudora 7.1 for Windows User Guide" (PDF)
offers a suggestion for decoding attachments that appear
merged into the message itself (the suggestion is
to save the entire message as a text file,
then use an external decoding program).
You might try this, just to see what happens;
for a "decoding program," try WinZip (from winzip.com),
which is designed to "decode" a number of special files, including MIME messages
(it usually works on entire Thunderbird mailbox files, by the way,
allowing the individual extraction of every message and every attachment).
Be sure to rename the saved message text file to "xxxx.mim"
before opening with WinZip.
The ".mim" extension is usually "registered" by WinZip,
especially for this purpose; dragging such a suitably named file
to a desktop shortcut for WinZip will also usually work.
I would be very interested to hear whether this works on your messages, thanks.
--
John H Meyers
When saving an incompletely interpreted message as text from within Eudora,
for the purpose of extracting its separate MIME parts using WinZip,
please be sure to check "Include headers" in the "Save as" dialog box,
as well as subsequently renaming the saved file to "xxxxx.mim"
before presenting it to WinZip, thanks.
Note that Windows XP built-in "Compressed (zipped) folders"
does not take the place of WinZip for this purpose.
Additional links of potential interest:
"Sending RTF with Attachment as MIME Loses Attachment"
http://support.microsoft.com/kb/181953
"When you send a message with a MIME attachment from an MS-Exchange client
and have configured an Internet recipient to
'Always send to this recipient as RTF',
and that recipient uses a POP3 client,
the recipient will not receive the attachment."
"Decoding Internet Attachments"
http://pages.prodigy.net/michael_santovec/decode.htm
--
John H Meyers
> The same email sent to my ISP's webmail is also received as text.
This would be additional evidence of a sender-side problem,
or at least that it is a problem for any interpreter
which is either not especially made
to understand the sender's non-conforming message format,
or does not second-guess about and repair some sender-side error.
> Same problem. [Header] "MIME-version: 1.0" is not there.
Mandatory for MIME email, per RFC2045, although some clients
may decide to ignore its absence and assume it,
if some vendors (Microsoft Outlook/Exchange) refuse to include it.
The arguments between "proprietary" (e.g. Microsoft Outlook/Exchange)
and "open" systems (e.g. RFC internet standards) may never end,
but inter-operability is obviously better and more universal
where vendors are more compliant.
> It seems email and attachment from this guy's Outlook 2000
> [and MS Exchange Server] can only be decoded by Outlook [or Outlook Express]
Just as millions of web sites have been "designed for Internet Explorer"
(with quite a few even refusing to talk to other web browsers,
especially to those which have followed every universal internet standard
right down to the last dotted "i").
Almost the way USA tries to make other countries
conform to its own internal way of life,
and become a captive "customer," one might add.
--
ABC
<jhme...@nomail.invalid> wrotd:
>Additional note:
>
>When saving an incompletely interpreted message as text from within Eudora,
>for the purpose of extracting its separate MIME parts using WinZip,
>please be sure to check "Include headers" in the "Save as" dialog box,
>as well as subsequently renaming the saved file to "xxxxx.mim"
>before presenting it to WinZip, thanks.
>
You are brilliant. I saved the whole message to .mim. Winzip decoded
it into a txt file for the message and a jpg file which is the
attachment. So now at least I can get the attachment.
Further experiment with Yahoo webmail shows that Yahoo can decode it
while my ISP webmail cannot. I assume this is what you said that some
client assumes the MIME content even without the line of
"Mime-Version: 1.0". OE must have been doing that.
Since My eudora can decode the same message forwarded from OE (but not
from Outlook 2000),obviously OE includes the MIME line. Just wondering
why Microsoft would have different arrangements for 2 similar email
client??
Now what should my friend do with his Outlook 2000 to get the MIME
header back? We used to have no such problem for a few years and he
swears that he has not changed anything to his Outlook.
Many thanks
ABC
ABC
receiving emails and attachment from this man. I dug up the old email
and this was the header at that time. As you can see, there is a
line X-Mime OLE .... and the MIME Version : 1.0 is there.
*****************************************************************************************
__Return-Path: <xxx@xxx>
Received: from mail.yyy (mail.yyy [203.198.157.145])
by yyy.com (8.11.6/8.11.6/SuSE Linux 0.5) with SMTP id
j8K1ci608659
for <yyy@yyy>; Tue, 20 Sep 2005 09:38:44 +0800
Received: from mail3.xxx ([202.64.240.14])
by mail.yyy (SAVSMTP 3.1.1.32) with SMTP id M2005092010025324225
for <yyy@yyy>; Tue, 20 Sep 2005 10:02:53 +0800
Received: from DSBXCHSRV02A.corp.dahsing.com (unverified) by
mail3.xxx (Email Gateway) with ESMTP id
<T737f5af8340a00050e1274@zzz> for <yyy@yyy>;
Tue, 20 Sep 2005 09:51:47 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C5BD85.DC3073EC"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: XXX Our Ref. XXX
Date: Tue, 20 Sep 2005 09:51:47 +0800
Message-ID:
<077561BE6181B34D8360...@DSBXCHSRV02A.zzz>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: XXX
Thread-Index: AcW7MHIYNIaD4p6YS5CyGPUJYwukdgCVGoaw
From: "XXX" <xxx@xxx>
To: "YYY \(E-mail\)" <yyy@yyy>
X-UIDL: 6;P!![<i"!`!k"!\W8"!
Dear Tommy
Copy of LD's letter dd 12-Sept-2005 is forwarded for your attention.
<<0498_001.tif>>
*****************************************************************************************************************
Since then, suddenly we went into problems. I realise that his email
header had changed. This is the header of the 1st problematic email.
What can you see from this? Is there any solution?
ABC
****************************************************************************************************************
Return-Path: <xxx@xxx>
Received: from mail.yyy (mail.yyy [203.198.157.145])
by mail2.yyy (8.11.6/8.11.6/SuSE Linux 0.5) with SMTP id
jAU2eNb10527
for <yyy@yyy>; Wed, 30 Nov 2005 10:40:23 +0800
Message-Id: <200511300240.jAU2eNb10527@zzz>
Received: from guardian2.zzz ([202.64.240.15])
by mail.hastings-hk.com (SMSSMTP 4.1.9.35) with SMTP id
M2005113010560701528
for <yyy@yyy>; Wed, 30 Nov 2005 10:56:07 +0800
X-Server-Uuid: 7BDB3865-763F-4534-84CA-595DD2C2A364
content-class: urn:content-classes:message
Subject: ??: XXX
Date: Wed, 30 Nov 2005 10:54:26 +0800
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: XXX
Thread-Index: AcX0jInEthIgjC7FRni+0ghr6E368AAzCXHw
From: "XXX" <xxx@xxx>
To: "YYY(E-mail)" <yyy@yyy>
cc: "AAA (E-mail)" <aaa@aaa>
X-Archive-Out: Out
X-WSS-ID: 6F93CBE80BK109298-01-01
Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C5F559.60724C86"
X-UIDL: 1Qa"!4<[!!3)o!!E43!!
This is a multi-part message in MIME format.
------_=_NextPart_001_01C5F559.60724C86
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
***************************************************************************************************
John H Meyers
> I dug up old email and this was the header at that time:
| MIME-Version: 1.0
| Content-Type: multipart/mixed;
| boundary="----_=_NextPart_001_01C5BD85.DC3073EC"
| X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
> Since then, suddenly we went into problems. I realise that his email
> header had changed. This is the header of the 1st problematic email:
| X-Server-Uuid: 7BDB3865-763F-4534-84CA-595DD2C2A364
| Content-Type: multipart/mixed;
| boundary="----_=_NextPart_001_01C5F559.60724C86"
> Yahoo [and OE] can decode it, while my ISP webmail [and Eudora] cannot.
It looks to me as if the company may have updated or modified
their Microsoft Exchange server (and possibly the Outlook clients also).
The significance of the "X-MimeOLE" and "X-Server-Uuid" headers is mentioned in:
http://www.computerworld.com.au/index.php/id;1808495145;pp;7;fp;2;fpid;37
All that I can suggest is to have your correspondent
contact the administrators of that server/client system,
and take special note of the fact that the "MIME-Version:" header,
declared mandatory by RFC2045, is currently missing,
which leads to an inability to parse the message,
in clients which strictly interpret the RFC;
it is probably to their advantage to fix this,
rather than to be incompatible with any segment of the rest of the world.
Meanwhile, the only recipient-side remedies appear to be
either to use clients which are more forgiving of the RFC violation,
or to extract attachments from unparsed messages using other software,
such as WinZip, which fortuitously includes MIME decoding in its abilities.
Best wishes.
--
ABC
ABC
On Sat, 06 Oct 2007 11:46:42 -0500, "John H Meyers"
<jhme...@nomail.invalid> wrotd:
>All that I can suggest is to have your correspondent