Outlook+MAPI and viewing "inline HTML" eMails

[mars solutions]

Hello,

can anybody give a hint on the following problem?

When using Scalix, the MAPI & Outlook 2000/03

HTML mails get displayed as attachments and not "inline".

Outgoing AND Incoming...

Even when HTML as email format is selected in the Outlook Options.
Everything is configured fine for the client... ?!

[ScalixSupport]

Just to clarify, do mean that images within html messages are turned into attachments, or the entire (text and all) html msg is coming into OL as an attachment?

Let me know,

Matthew
Support

[mars solutions]

Hello Matthew,

well, the whole e-mail is meant. When receiving HTML mails, the "hello world" is an .html
attachment named like the subject.

e.g. Empty Body in the big field where OL used to display the "hello world" + having an attachment like
Subject.HTML
containing the "hello world" from the sender of the mail.

Thanks in advance!

[ScalixSupport]

What client is sending these messages? If you send OL to OL within Scalix does this happen? from (e.g.) gmail to OL/Scalix?

It is likely caused by the sending client. We are aware of an issue where embedded images can arrive as attachments, but not entire html messages.

Matthew
Support

[mars solutions]

Hello,

it doesn't matter which client sends the email (on remote side).
(Tested: Outlook, Thunderbird, etc.)

We experience this (on our side) with the default
installation of either OL 2000 or 2003 + MAPI.

The Scalix Web Access curiously interprets everything correct, with it
such mails display fine!

This is the receiving side.

Now, when we send, the same happens. People with different clients get mail
from us as HTML-attachment (whole mail) only.

Regards,
Sebastian Krajenski.

[ScalixSupport]

So this is happening in Scalix-to-Scalix scenarios?

Have you edited any configuration files? Are there any 3rd-party plug-ins installed on the OL clients? Any Anti-Virus/Anti-spam running on the desktops?

Let me know,

Matthew
Support

[wheelc]

Hello,

Noticed this thread. I have been having the same problem. It was introduced at version 9.2. Version 9.1 was fine.

regards

Chris.

[ScalixSupport]

Hi,

This issue is almost always caused by how the client is configured. Double-check that the client is configured to not send messages as attchments, and that (for OL) all 3rd-party plug-ins are disabled.

Also, check/disable any local AV/AS app on the desktop, and if runing ClamAV on the server, check you configuration for that.

Regards,

Matthew
Support

[kali]

Hi Matthew,

Not sure I totally agree with you.... I too have seen the same thing occur in Outlook. It is not likely that messages are being "sent as attachements" (that's actually a fwd'ing option) because the offending emails display fine in other clients - notably OE.

So it appears to be the way that Outlook displays? Or difference in the MIME storage? That part I can only guess at.

[ScalixSupport]

Here's a test to run. Send an html message from a Scalix user using T-bird to a Scalix user using OL. If the message arrives ok, then the problem exists between the remote system and Scalix (perhaps a Scalix smart host/perimeter server running an AV app or similar setup). If the message does not arrive as it should (not inline), then there is a Scalix issue or misconfiguration.

Matthew
Support

[Valerion]

I have also had that on certain (very few) incoming emails, where Outlook would render everything as an attachment, although it displays perfectly in SWA.

I have captured an example, that contains a Content-Type: text/html with Content-Disposition: inline tag, so Outlook shouldn't render it this way. The only other attachments are Content-Type: image/gif attachments.

The full email is 16k in size, so I had to strip it down a lot. If you need any more info, I'll be happy to provide it.

Return-Path: <yyy@yyy.yyy>
Received: from xxx (xxx [xx.xx.xx.xx])
by xx.xx.xx.xx (8.13.1/8.13.1) with ESMTP id jBEBgeDU023425
for <xxx@xxx.xxx>; Wed, 14 Dec 2005 13:42:40 +0200
Received: from localhost (localhost.localdomain [127.0.0.1])
by xxx (8.13.4/8.13.4) with ESMTP id jBEBgeGl008074
for <xxx@xxx.xxx>; Wed, 14 Dec 2005 13:42:40 +0200
Received: from yyy [yy.yy.yy.yy]
by localhost with POP3 (fetchmail-6.2.5.2)
for xxx (single-drop); Wed, 14 Dec 2005 13:42:40 +0200 (SAST)
Received: (Astro-SpamKill 24087 invoked from network); 14 Dec 2005 11:04:35 -0000
Received: from unknown (HELO AspEmail) (yy.yy.yy.yy)
by 0 with SMTP; 14 Dec 2005 11:04:35 -0000
Date: Wed, 14 Dec 2005 13:04:36 +0200
From: "SAOL" <yyy@yyy.yyy>
Sender: yyy@yyy.yyy
To: xxx@xxx.xxx
Message-ID: <200512141142.jBEBgeGl008074@xxx>
Subject: Support Notice
Delivered-To: xxx@xxx.xxx
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="--=C5C4FA9064AD4084886E_2E78_7178_33D6"

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: Quoted-Printable
Content-Disposition: inline

<!-- saved from url=3D(0022)http://internet.e-mail -->
<html>
<head>
***** SNIPPED *****
</head>
<body>

***** SNIPPED *****

</body>
</html>


----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="1.gif"
Content-Transfer-Encoding: base64
Content-ID: <1>
Content-Disposition: attachment;
filename="1.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="2.gif"
Content-Transfer-Encoding: base64
Content-ID: <2>
Content-Disposition: attachment;
filename="2.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="3.gif"
Content-Transfer-Encoding: base64
Content-ID: <3>
Content-Disposition: attachment;
filename="3.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="4.gif"
Content-Transfer-Encoding: base64
Content-ID: <4>
Content-Disposition: attachment;
filename="4.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="5.gif"
Content-Transfer-Encoding: base64
Content-ID: <5>
Content-Disposition: attachment;
filename="5.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="bg.gif"
Content-Transfer-Encoding: base64
Content-ID: <bg>
Content-Disposition: attachment;
filename="bg.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6
Content-Type: image/gif;
name="div.gif"
Content-Transfer-Encoding: base64
Content-ID: <div>
Content-Disposition: attachment;
filename="div.gif"

***** SNIPPED *****

----=C5C4FA9064AD4084886E_2E78_7178_33D6--