Corrupt attachments

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

tvmo - 02 May 2008 10:59 GMT

Hello,

1. I have two users each with Windows XP, Office 2003 and running the
same application (identical builds)

2. Both users generate Word documents from the application and then
send the documents as an attachment via emails (Word 2003>File>Send
To>Mail Recipient (as Attachment))

3. When sending these emails internal to the domain the recipients
receive the attachments with no issues.

4. Both the users also send these attachments to the same external
recipient. The recipient receives the attachment with no problems from
one of the users, but always with the second user the attachment is
corrupt.

5. Initially the problem attachments where getting stopped by
MailMarshal as 'Malformed'

6. I changed the user's local profile (Documents and Settings) and the
attachments got delivered with no issues from MailMarshal, so I
thought this was the end of it. However it appears that when the
attachments are received, they are corrupt (but only and always from
the same user)

Any ideas?

Cheers

Reply to this Message

Brian Tillman - 02 May 2008 15:23 GMT

> 6. I changed the user's local profile (Documents and Settings) and the
> attachments got delivered with no issues from MailMarshal, so I
> thought this was the end of it. However it appears that when the
> attachments are received, they are corrupt (but only and always from
> the same user)

Make sure that user is not sending the message in Rich Text format.

Signature

Brian Tillman [MVP-Outlook]

Reply to this Message

tvmo - 06 May 2008 11:11 GMT

Thanks for the reply.

The user is using HTML format (Outlook>Tools>Options>Mail format tab)

Cheers

Reply to this Message

Brian Tillman - 06 May 2008 14:50 GMT

> The user is using HTML format (Outlook>Tools>Options>Mail format tab)

Open the contact record corresponding to the person not receiving the
attachment. Double-click the email address in the E-Mail field. At the
bottom of the dialogue, do you see an "Internet format" drop-down? If so,
what does it contain?

Signature

Brian Tillman [MVP-Outlook]

Reply to this Message

tvmo - 07 May 2008 08:34 GMT

The option is 'Let Outlook decide the best sending format'.

Cheers

Reply to this Message

tvmo - 07 May 2008 10:31 GMT

I've noticed in the headers that the one that isn't working has the
following:

Content-Type: application/msword;name="Microsoft Word Document in
Database_.doc"
Content-Transfer-Encoding: base64

The one that works has the following:

Content-Type: multipart/mixed;

Does this stipulate how the email is packaged? If yes how and where do
I configure the option in Outlook or Word so I can get the one that
isn't working on the same config as the one that is working?

Cheers

Reply to this Message

Brian Tillman - 07 May 2008 13:39 GMT

> I've noticed in the headers that the one that isn't working has the
> following:
[quoted text clipped - 8 lines]
>
> Does this stipulate how the email is packaged?

You can have both of those headers in the same message. They're not
mutually exclusive. Typically, the second of the two will occur prior to
the first. The second means that there are multiple parts to the message
and that they are not all the same format. The second deals with only one
of the parts, stating that it is a Word document. All binary files are
base64 encoded when you transmit them, since Internet mail standards do not
actualy allow the transmossion of binary data. Mail agents encode them into
a standard character set that gets decoded into the original binary on the
receiving end. So, the fact that you see differences doesn't necessarily
explain why one works and the other doesn't. I'd have to see more of the
headers of the non-working one to be able to take a stab at figuring out if
the headers indicate the problem.

Signature

Brian Tillman [MVP-Outlook]

Reply to this Message

tvmo - 07 May 2008 15:49 GMT

THIS IS THE HEADER THAT WORKS FINE:

Received: from frontend.exchange.server(Not Verified[x.x.x.x]) by
mail.smtp.address)
        id <B481993920001>; Thu, 01 May 2008 10:55:30 +0100

Received: from Mail.server([x.x.x.x]) by frontend.exchange.server with
Microsoft SMTPSVC(6.0.3790.3959);
         Thu, 1 May 2008 10:52:57 +0100

Content-class: urn:content-classes:message

MIME-Version: 1.0

Content-Type: multipart/mixed;
        boundary="----_=_NextPart_001_01C8AB71.20D543E4"

X-MimeOLE: Produced By Microsoft Exchange V6.5

Subject: Microsoft Word Document in Database (3).doc

Date: Thu, 1 May 2008 10:52:55 +0100

Message-ID: 87AB8A2DE596774DA8A8470A10A25362045CE54A

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

Thread-Topic: Microsoft Word Document in Database (3).doc

Thread-Index: Acirasl6bKSKB6KAR7OOOVNun8AHKg==

From: worksforme@domain.com

To: recipient@recipient.com
Return-Path: worksforme@domain.com

X-OriginalArrivalTime: 01 May 2008 09:52:57.0613 (UTC)
FILETIME=[225B6BD0:01C8AB71]

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AB71.20D543E4
Content-Type: multipart/alternative;
        boundary="----_=_NextPart_002_01C8AB71.20D543E4"

------_=_NextPart_002_01C8AB71.20D543E4

Content-Type: text/plain;
        charset="US-ASCII"

Content-Transfer-Encoding: quoted-printable

This is the message in the body
Cheers
=20
Sender

------_=_NextPart_002_01C8AB71.20D543E4
Content-Type: text/html;
        charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN
class=3D422150709-01052008>JULIE=20
KENT</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN
class=3D422150709-01052008>MARK=20
OTTEN</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D422150709-01052008></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D422150709-01052008>SANDRA</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_002_01C8AB71.20D543E4--

------_=_NextPart_001_01C8AB71.20D543E4
Content-Type: application/msword;
        name="Microsoft Word Document in Database (3)_.doc"
Content-Transfer-Encoding: base64
Content-Description: Microsoft Word Document in Database (3)_.doc
Content-Disposition: attachment;
        filename="Microsoft Word Document in Database (3)_.doc"
Received: from frontend.exchange.server(Not Verified[x.x.x.x]) by
mail.smtp.address)
        id <B481abcfd0000>; Fri, 02 May 2008 08:04:29 +0100

Received: from Mail.server([x.x.x.x]) by frontend.exchange.server with
Microsoft SMTPSVC(6.0.3790.3959);
         Fri, 2 May 2008 08:01:56 +0100

Content-class: urn:content-classes:message

MIME-Version: 1.0

Content-Type: application/msword;
        name="Microsoft Word Document in Database_.doc"

Content-Transfer-Encoding: base64

Subject: Microsoft Word Document in Database.doc

Content-Description: Microsoft Word Document in Database_.doc

Content-Disposition: attachment;
        filename="Microsoft Word Document in Database_.doc"

X-MimeOLE: Produced By Microsoft Exchange V6.5

Date: Fri, 2 May 2008 08:01:53 +0100

Message-ID: 87AB8A2DE596774DA8A8470A10A25362045EF6BB@

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

Thread-Topic: Microsoft Word Document in Database.doc

Thread-Index: AcisImbNL9Z4KMZyR1O1Wu3KAxdmXA==

From: notworkingforme@domain.com

To: <Recipient@recipient.com>
Return-Path: notworkingforme@domain.com

X-OriginalArrivalTime: 02 May 2008 07:01:56.0092 (UTC)
FILETIME=[686D53C0:01C8AC22]

THIS IS THE HEADER THAT DOESN'T WORK:

Received: from frontend.exchange.server(Not Verified[x.x.x.x]) by
mail.smtp.address)
        id <B481abcfd0000>; Fri, 02 May 2008 08:04:29 +0100

Received: from Mail.server([x.x.x.x]) by frontend.exchange.server with
Microsoft SMTPSVC(6.0.3790.3959);
         Fri, 2 May 2008 08:01:56 +0100

Content-class: urn:content-classes:message

MIME-Version: 1.0

Content-Type: application/msword;
        name="Microsoft Word Document in Database_.doc"

Content-Transfer-Encoding: base64

Subject: Microsoft Word Document in Database.doc

Content-Description: Microsoft Word Document in Database_.doc

Content-Disposition: attachment;
        filename="Microsoft Word Document in Database_.doc"

X-MimeOLE: Produced By Microsoft Exchange V6.5

Date: Fri, 2 May 2008 08:01:53 +0100

Message-ID: 87AB8A2DE596774DA8A8470A10A25362045EF6BB@

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

Thread-Topic: Microsoft Word Document in Database.doc

Thread-Index: AcisImbNL9Z4KMZyR1O1Wu3KAxdmXA==

From: notworkingforme@domain.com

To: <Recipient@recipient.com>
Return-Path: notworkingforme@domain.com

X-OriginalArrivalTime: 02 May 2008 07:01:56.0092 (UTC)
FILETIME=[686D53C0:01C8AC22]

Cheers

Reply to this Message

Brian Tillman - 08 May 2008 13:38 GMT

> THIS IS THE HEADER THAT WORKS FINE:

...snip...

> THIS IS THE HEADER THAT DOESN'T WORK:

I'm puzzled by things I see in each group of headers you provided. Some
things (like Message-ID and Received headers) seem out of order to me for
both examples.

Signature

Brian Tillman [MVP-Outlook]

Reply to this Message

tvmo - 08 May 2008 13:58 GMT

Not sure what to say, those are the headers as is.

Cheers

Reply to this Message

Brian Tillman - 08 May 2008 14:49 GMT

> Not sure what to say, those are the headers as is.

Well, that's simply not possible. At the very least what you posted has
blank lines interspersed between the headers, which can't happen.

Signature

Brian Tillman [MVP-Outlook]

Reply to this Message

tvmo - 08 May 2008 16:04 GMT

No you're right I wasn't strictly accurate with my last statement, I
did put in the spaces to be able to read the headers more clearly, but
I haven't removed or added anything.

Cheers

Reply to this Message

tvmo - 16 May 2008 09:54 GMT

Any thoughts?

Reply to this Message