Unable to view message content through webmail, encoding pb?

[Die's Man]

Hello there !

We've been struggling to understand a content displaying problem through the Ability Webmail, with it displaying correctly on other webmail or mail clients, but showing no content on Ability Webmail.

First we thought about a "truncation" problem, but now I see that the content is actually in the mail that Webmail shows, but appears only when the message is displayed with "Source" view.

Here's a glimpse at what is displayed:

Code: Select all

Received: from xxxxxxxxxxxx
   with SMTP (Code-Crafters Ability Mail Server 2.60);
   xxxxxxxxxxxx
From: xxxxxxxxxxxx
To: xxxxxxxxxxxx
Date: xxxxxxxxxxxx
Subject: xxxxxxxxxxxx
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="f3a22eaf-7b6d-47f3-9fe2-663dece5be24"


--f3a22eaf-7b6d-47f3-9fe2-663dece5be24
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable



--f3a22eaf-7b6d-47f3-9fe2-663dece5be24
Content-Type: message/rfc822

Received: from xxxxxxxxxxxx
(Clearswift SMTPRS 5.2.9) with SMTP id xxxxxxxxxxxx;
xxxxxxxxxxxx
thread-index: AcgXxKDDZo2z9dEIRK2NK9Qj6SAPMA==
Thread-Topic: dt-01b xxxxxxxxxxxx ASP.NET Log Error
From: <xxxxxxxxxxxx>
To: <xxxxxxxxxxxx>
Subject: dt-01b xxxxxxxxxxxx ASP.NET Log Error
Date: xxxxxxxxxxxx
Message-ID: <006c01c817c4$a0c3bb30$0800000a@BONUS.LOCAL>
MIME-Version: 1.0
Content-Type: multipart/alternative;
   boundary="----=_NextPart_000_006D_01C817D5.644C8B30"
X-Mailer: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198

This is a multi-part message in MIME format.

------=_NextPart_000_006D_01C817D5.644C8B30
Content-Type: text/plain;
   charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


[[ASP.NET ERROR MESSAGE .....]]


------=_NextPart_000_006D_01C817D5.644C8B30
Content-Type: text/html;
   charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

[[Same error message, but on a single line]]
------=_NextPart_000_006D_01C817D5.644C8B30--



--f3a22eaf-7b6d-47f3-9fe2-663dece5be24--



Would anyone have an idea on what the problem is ?

In fact, it's not only display, it's content handling I think. Because when the account forwards the message to itself, there is nothing left in it, not even in "Source" view.

[rob]

Could you please zip up and send the entire original source to my personal email address: rob@code-crafters.com. This way I can perform tests on the source.

[Die's Man]

The information asked was sent to you in the previous days.

If by any hazard you received nothing, let me know !

Thanks,

Gaël Marmillod

[Die's Man]

Ok, so with a bit more details, the exact final problem I had was some truncation on very long lines.

It indeed appeared that everything after approximately 1000 chars was cut.

This is simply due to the fact that AMS implements an SMTP RFC defining this limit.

Rob told me that ways to work around this is to use quoted-printable or base64 encoding.


Thanks a lot for the support !

Gaël