PDF file attachments gets corrupted

[Baylink]

If you look at the headers originally posted, langs, you'll see that the content-transfer-encoding on the one that's working is base64, and the one that's not is quoted printable.

That's the problem.

Re-reading the whole thread now, though, langs, it's not clear if *your* messages are being entered via ZCO, web, or some other fashion; clarify?

(the rest of this was written when I thought langs was the OP, and I'm too late for work to adjust it now. :-)

Your PDF's contain a binary stream, and ASCII-7 channels -- which email is -- can't pass that.

You need to figure out which program is attaching the PDF to the email with the wrong encoding, and why it's doing that. <strike>I didn't read the bug linked, but the message suggested that it might be pertinent to your problem.</strike> I've just read the bug, and it seems exactly on point: Outlook is stupid. :-)

It would be interesting -- to me -- to know if the same version of Outlook, presented with the same body and attachments, but sending via SMTP direct -- screwed the same thing up the same way.

[uushaggy]

I am having problems with 5.0.9_GA_2533.UBUNTU8 corrupting PDFs that I receive from others or send myself. This happens if I attach via IMAP in Outlook or via IE on the web interface.

Has there been any other information regarding this?

This is not a good behavior and I would think would have been resolved by now. Other mails servers I have used have not done this so I am concerned about supporting an install of Zimbra.

[uushaggy]

Ok, so I have narrowed it down to this:

-Mail I recevie directly to my domain works good
-Mail I pickup from other accounts via fetchmail get corrupted

In my sceanrio I have a third level domain that I have several accounts. Email sent to these accounts work fine in and out.

Each account also recieves email from a Comcast.net pop account via fetchmail. It seems that any PDFs that are handled here get corrupted.

I was using the web interface to setup the pop mail pickup, but found there was no way to make this persistent if you didn't have the web interface open.

Any ideas?

[Chadsel Chen]

Originally Posted by nrc

So it seems likely that everything is ok with Zimbra. It sounds like either Gmail is taking a different path to your customer and avoiding a broken SMTP server or their MTA recognizes the broken SMTP service and handles it.

If your recipient can provide you with a full copy of received headers from the Gmail message and the Zimbra message that may show the difference in paths and identify potentially broken relays.

My user sent within the same Zimbra domain but still got PDF corrupted.
Here is the header.

Thanks
Chadsel

X-Zimbra-ItemId: 68294
X-Zimbra-FolderId: 2
X-Zimbra-Tags:
X-Zimbra-Flags: au
X-Zimbra-Received: 1232395677000
X-Zimbra-Modified: 1232395677000
X-Zimbra-Change: 170538
X-Zimbra-Revision: 170538
X-Zimbra-Conv: -68294
Return-Path: xxxx@christoffersonrobb.com
Received: from mail.christoffersonrobb.com (LHLO
mail.christoffersonrobb.com) (10.10.1.50) by mail.christoffersonrobb.com
with LMTP; Mon, 19 Jan 2009 15:07:57 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.christoffersonrobb.com (Postfix) with ESMTP id 6534A17D8781;
Mon, 19 Jan 2009 15:07:57 -0500 (EST)
X-Virus-Scanned: amavisd-new at ms01.christoffersonrobb.com
X-Spam-Flag: NO
X-Spam-Score: -3.879
X-Spam-Level:
X-Spam-Status: No, score=-3.879 tagged_above=-10 required=6.6
tests=[ALL_TRUSTED=-1.8, AWL=0.517, BAYES_00=-2.599,
FROM_OFFERS=0.001, HTML_MESSAGE=0.001, OBSCURED_EMAIL=0.001]
Received: from mail.christoffersonrobb.com ([127.0.0.1])
by localhost (mail.christoffersonrobb.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id dG8nl-KTgb3f; Mon, 19 Jan 2009 15:07:54 -0500 (EST)
Received: from mail.christoffersonrobb.com (mail.christoffersonrobb.com [10.10.1.50])
by mail.christoffersonrobb.com (Postfix) with ESMTP id 6371417D877F;
Mon, 19 Jan 2009 15:07:54 -0500 (EST)
Date: Mon, 19 Jan 2009 15:07:54 -0500 (EST)
From: xxxx@christoffersonrobb.com>
To: xxxx@christoffersonrobb.com>, xxxx@crc.ky>,
xxxx@christoffersonrobb.com>
Message-ID: <565943511.111191232395674093.JavaMail.root@ms01.c hristoffersonrobb.com>
In-Reply-To: <CA313DA571C042BAA1C2AF77D0250345@NYLEONIDDESK>
Subject: Re: Start 2 FD 20.5 M
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_2644_1420927202.1232395674089"
X-Originating-IP: [208.122.21.2]
X-Mailer: Zimbra 5.0.11_GA_2695.RHEL5_64 (ZimbraWebClient - FF3.0 (Win)/5.0.11_GA_2695.RHEL5_64)

[daniel.shachtman]

I am using ZCS 5.0.15 and have multiple users whom are seeing this issue. Is there a Bug posting or an RFE open to actually address the problem?

[tolenaars]

We're also on 5.0.15 here and experiencing the same problem with pdf's getting corrupted. The workaround i suggested to our users was to zip the pdf before sending. This seems to protect the pdf's from getting corrupted in our case. Waiting to see if the latest patch fixes this before filing a ticket..

[Klug]

I think this is related to firefox being used...

The fix is in 5.0.16, upgrade.
Bug 32536 : Zimbra too trusting of MIME-type sent by client