Incorrect MIME Interpretation of EMail

Aspose.Email Product Family
1

Hi

We are using Aspose Network to retrieve and read emails and on the whole it works fine, except in the following circumstances.

We have received and email without a body, but with an attachment, the header [partially] looks like:

Received: from XXXXX with Microsoft SMTPSVC(6.0.3790.3959);
Mon, 15 Dec 2008 10:28:40 +0000
Received: (qmail 18089 invoked from network); 15 Dec 2008 10:25:30 -0000
Received: from mail141.messagelabs.com (85.158.137.99)
by XXXX with SMTP; 15 Dec 2008 10:24:13 -0000
X-VirusChecked: Checked
X-Env-Sender: mdbprod1@pust250.centrica.co.uk
X-Msg-Ref: server-4.tower-141.messagelabs.com!1229336651!19675709!1
X-Originating-IP: [194.9.189.218]
…
MIME-Version: 1.0
Subject: Test
Content-Type: multipart/mixed;
boundary=“simply boundary”

–simple boundary
Content-Type: text/plain;
charset=“iso-8859-1”
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename=/mdb/mdbprod/var/out/mdbprumr/BGC01_PN096037.UMR
Content-Description: BGC01_PN096037.UMR

“A00”,399,“UMR”,20081215,101702,096037
“U01”,7440288709,20081212,“M”,“N”,“S00093139913”," 17988",“00”,"","","","","","",""

More detail removed …

–simple boundary–

Aspose is interpreting this as an email without attachments with the attached text file as the body of the email, which is incorrect as the Content-Disposition is correctly set as “attachment”.

Can you please provide an explanation and/or solution to this issue?

Thanks
Tony Hodgson

2

Hi Tony,

Thanks for considering Aspose.

Could you please download such email with Outlook Express or Microsoft Outlook, save the eml/msg and post a file here. We will look into the problem, why the attachment data is included in body.

3

Hello,

The eml file you attached has some errors in it. Its boundary value is wrong. The "simplY boundary" does not equal to the "simplE bounday". So the code cannot find the proper boundary for mime parts.

How you generate the eml file?

Content-Type: multipart/mixed;
boundary="simply boundary"

--simple boundary

Thanks

4

Hi

Apologies, this was my fault, I have poted and incorrect file. I have uploaded the actual eml file that causes the problem (and not the cut down version that I mistakenly posted previously).

Thanks for the response