Problems with ZCO with the attachments

[cadinor]

Hi to all

Last week we have a migration from Scalix to Zimbra ( Release 6.0.10_GA_2692.RHEL5_64_20101215161355 RHEL5_64 NETWORK edition).

The migration was perfect, but, when the client recibes one mail with attachment, the Outlook doesn’t show the attachment. When the user change the state of the message: read, add/modify tag.... etc, the message shows the attachment suddenly.

We upgrade from Outlook 2003 to Outlook 2007 (both with the last service pack), but the problem persist. The connector of Scalix has been removed and also we removed all registry keys with the name scalix and sclx, but the problem persist.....

This problem happens to all computers on the network. Someone has encountered this problem ?

A part from that, we also detected some problems to mark as read/unread the messages on a specific client’s PC.

thanks in advanced

[fsiegel]

This only happened with one message, or does it consistently happen? Can you send a Show Original of the message? [In the web client, right click on it and choose Show Original).

[cadinor]

Hi fsiegel,

We detected the problem on some emails, so it doesn’t seem to be consistently and we don’t see the relation between these problematic emails.

I’ve attached you the Show Original of this specific email:



From: "Xxxx, Xxxxx" <xxx.xxx@xxx.xx>
To: "Xxxxxxx"
Subject: Colores Click'In
Date: Thu, 27 Jan 2011 14:53:04 +0100
Message-ID: <D1CEF239EE4447038A38B55E76E19D20@serragrup.loca l>
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_NextPart_000_02A8_01CBC14F.AB7F3990"
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994

This is a multi-part message in MIME format.

------=_NextPart_000_02A8_01CBC14F.AB7F3990
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_02A9_01CBC14F.AB7F3990"


------=_NextPart_001_02A9_01CBC14F.AB7F3990
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit





st1\:* {
BEHAVIOR: url(#default#ieooui)
}


@font-face {

font-family: PMingLiU;
}
@font-face {
font-family: @PMingLiU;
}
@page
Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 70.85pt 2.0cm 70.85pt;
}
P.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New
Roman"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0cm 0cm 0pt;
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt
}
DIV.MsoNormal {

MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE:
12pt
}
A:link {
COLOR: blue; TEXT-DECORATION:
underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION:
underline
}
A:visited {
COLOR: purple; TEXT-DECORATION:
underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple;
TEXT-DECORATION: underline
}
SPAN.E-MailFormatvorlage17 {

FONT-FAMILY: Arial; COLOR: windowtext; mso-style-type:
personal-compose
}
P.msonospacing {
FONT-FAMILY: "Times New Roman";
MARGIN-LEFT: 0cm; FONT-SIZE: 12pt; MARGIN-RIGHT: 0cm;
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.msonospacing
{
FONT-FAMILY: "Times New Roman"; MARGIN-LEFT: 0cm; FONT-SIZE:
12pt; MARGIN-RIGHT: 0cm; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto
}
...etc