Binary data of Excel file appears in body

Hi,

We are experiencing some weird problems with attached excel files. When collecting messages via WebDav from an Exchange 2003 server, the ones with attached excel files looks like this: (see attached msg file (zipped)).

Somehow the binary content of the excel file is displayed in the body.

Attached screenshot (zipped) shows how the message looks like in Outlook before it gets collected.

If I copy the message to another mailbox folder via Outlook and collect that copy with WebDav, it is working fine. For some reason, the copy action causes Outlook to alter the headings of the message. Because of this I cannot give you a sample msg file and I cannot reproduce it myself in our development environment. I only see it at our customer.

What could be the problem?

Here is the unaltered message header before it is collected:

Microsoft Mail Internet Headers Version 2.0

Received: from conbr330.tdk.dk ([10.106.95.34]) by VESTAPP401A.tdk.dk with Microsoft SMTPSVC(6.0.3790.4675);

Thu, 9 Aug 2012 13:00:17 +0200

Received: from conbr330.tdk.dk ([10.106.95.34]) by conbr330.tdk.dk with Microsoft SMTPSVC(6.0.3790.4675);

Thu, 9 Aug 2012 13:00:16 +0200

Received: from n750754-d1. ([10.74.123.42]) by conbr330.tdk.dk with InterScan Messaging Security Suite; Thu, 09 Aug 2012 13:00:16 +0200

Received: from n750754-d1. (localhost [127.0.0.1])

by n750754-d1. (8.13.8+Sun/8.13.8) with ESMTP id q79B0GYU000721;

Thu, 9 Aug 2012 13:00:16 +0200 (MEST)

Received: (from b00398@localhost)

by n750754-d1. (8.13.8+Sun/8.13.8/Submit) id q79B0Fvr000714;

Thu, 9 Aug 2012 13:00:15 +0200 (MEST)

Date: Thu, 9 Aug 2012 13:00:15 +0200 (MEST)

From: Batchuser - nabs rapportering

Message-Id: <201208091100.q79B0Fvr000714@n750754-d1.>

To: bjas@tdc.dk, caste@tdc.dk, dosko@tdc.dk, jgulu@tdc.dk, laoe@tdc.dk,

sra@tdc.dk, wholesale@tdc.dk, x14273@tdc.dk, x18844@tdc.dk

Cc: nabsrap@tdc.dk

Subject: Jobafv.: report1007 produceret Thu Aug 9 13:00:04 MEST 2012

Return-Path: b00398@n750754-d1

X-OriginalArrivalTime: 09 Aug 2012 11:00:16.0565 (UTC) FILETIME=[28965650:01CD761E]

Thanks

/AndreasK

Hi Andreask,


Thank you for using Aspose.Email.

Well it seems difficult for us as well to reproduce the issue at our end with the provided information. I hope you will be using the latest version of Aspose.Email v 2.0.0 in your application. Anyway, we are currently looking into it and will update you about our findings. In case, we need some more information, we will request you here. We appreciate your patience in this regard.

Hi AndreasK,


We have been looking into your said issue but so far we are unable to pin point the problem cause. We require some more information from your end. It would be of great help in identifying the reason for said behavior if you could share the same/similar message using the Outlook application from the sender end.

We also will require some clarification, such as
  • How exactly the problematic message was sent? Outlook, other messenger, Aspose.Email etc
  • When you collected the message for the first time, did you use Aspose.Email API to fetch and save the message or any other means?
  • How did you copy the message to another Outlook folder?
  • How did you collect the message after moving it to the another Outlook folder?

We hope you can understand the need of above information to determine the point where message got broken. Thank you for your cooperation.
Regards,