Attachments Getting Munged

[taliskar]

I'm having an irregular issue with Zimbra and file attachments.

I'm running v3.1 on RHEL 4 (Twin 3Ghz Processors w/1Gb RAM)

Occassionally, when attachments are sent, they are being corrupted. I'm convinced it's being done by my Zimbra server as I've been able to replicate it with a specific message I have with attachments. I have been able to successfully receive this same message at my work email and at a gmail account without problems with the attachments.

The errors in my /var/log/zimbra.log file are:

Apr 21 10:49:45 email amavis[25617]: (25617-01) WARN: MIME::Parser error: part did not end with expected boundary
Apr 21 10:49:46 email amavis[25617]: (25617-01) spam_scan: not wasting time on SA, message longer than 65536 bytes: 1566+79606
Apr 21 10:49:46 email amavis[25617]: (25617-01) BAD HEADER from <username@organization.com>: MIME error: error: part did not end with expected boundary

This behavior is seen regardless of whether I'm using the web frontend to Zimbra or using Thunderbird to connect via IMAP.

Any ideas?

Thanks!

[bobby]

can you attach (or pm) the full mime message here?

[taliskar]

Yes, I can. But, I'm not quite sure what you want me to attach. Could you be a bit more specific? I could attach the actual email or I could attach the full log for the message.

But, I suspect you're wanting something different. Sorry if your request is clear as a bell and I'm not getting it

[bobby]

no problem. in zimbra, you can right-click on a message in the list and select "Show original" to get the full mime-encoded message. other mail programs will also usually have ways to view this.

[taliskar]

OK, here it is.
------------------------

Received: from localhost (localhost.localdomain [127.0.0.1])
by email.dresen.org (Postfix) with ESMTP id 148A7D5C4BA
for <scott@dresen.org>; Fri, 21 Apr 2006 15:55:52 -0400 (EDT)
Received: from email.dresen.org ([127.0.0.1])
by localhost (email.dresen.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 25623-03 for <scott@dresen.org>;
Fri, 21 Apr 2006 15:55:48 -0400 (EDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
by email.dresen.org (Postfix) with ESMTP id B2B00D5C4B7
for <scott@dresen.org>; Fri, 21 Apr 2006 15:55:45 -0400 (EDT)
Received: from mail.comcast.net [216.148.227.80]
by localhost with POP3 (fetchmail-6.2.5)
for scott@dresen.org (single-drop); Fri, 21 Apr 2006 15:55:45 -0400 (EDT)
Received: from spoon.dreamhost.com ([66.33.219.19])
by rwcrmxc20.comcast.net (rwcrmxc20) with ESMTP
id <20060421195406r2000j29qme>; Fri, 21 Apr 2006 19:54:06 +0000
X-Originating-IP: [66.33.219.19]
Received: from securemail.med.wayne.edu (med-tw02.med.wayne.edu [146.9.18.152])
by spoon.dreamhost.com (Postfix) with ESMTP id ADF2444564
for <scott@dresen.org>; Fri, 21 Apr 2006 12:54:05 -0700 (PDT)
Received: from 146.9.19.220 by securemail.med.wayne.edu with ESMTP (
WSUSoM Email Firewall SMTP Relay); Fri, 21 Apr 2006 15:53:48 -0400
X-Server-Uuid: A44DD072-8C1C-45CC-8600-2A2DF52569E8
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: PDF Attachment
Date: Fri, 21 Apr 2006 15:54:05 -0400
Message-ID: <F635E637657F8445863241E4A1ED86B0A8771F@MED-CORE03-MS2.med.wayne.edu>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: PDF Attachment
Thread-Index: AcZlfVgkda4rFfozSQCM6O1iFBE1WA==
From: "Dresen, Scott" <sdresen@med.wayne.edu>
To: scott@dresen.org
X-WSS-ID: 6857E7C64GW3854-01-01
Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C6657D.4E8E3EE9"
X-Virus-Scanned: amavisd-new at
X-Amavis-Alert: BAD HEADER MIME error: error: part did not end with expected boundary

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6657D.4E8E3EE9
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C6657D.4E8E3EE9"
Content-Transfer-Encoding: 7bit


------_=_NextPart_002_01C6657D.4E8E3EE9
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Did it make it through?

------_=_NextPart_002_01C6657D.4E8E3EE9
Content-Type: text/html;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D951415319-21042006><FONT face=3DArial size=3D2>Did it =
make it=20
through?</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_002_01C6657D.4E8E3EE9--

------_=_NextPart_001_01C6657D.4E8E3EE9
Content-Type: application/octet-stream;
name=wsu_campus_map.pdf
Content-Transfer-Encoding: base64
Content-Description: wsu_campus_map.pdf
Content-Disposition: attachment;
filename=wsu_campus_map.pdf

< I cut out the actual message attachment since it was so long, I presumed you don't want that part and it's the info above that's important>

[KevinH]

Originally Posted by taliskar

I cut out the actual message attachment since it was so long, I presumed you don't want that part and it's the info above that's important>

We want the entire thing. Please save it to a file. zip the file and attach using the 'Manage Attachments' option. Do not just copy/paste the data in as it will lose some formatting.

[taliskar]

OK, here's the zipped file. Let me know if this is not what you wanted.

[KevinH]

It's pretty clear the part is truncated. As the error stated the message doesn't have a tailing boundary on the last part.

[taliskar]

Yes, that appears to be the case. So my question is, what is Zimbra doing to cause this?

Attached are two zip files. I resent the same message from the same source. Except this time I used two recipients of the message. One to my Zimbra account and one to a Google Mail account.

The attachment was munged coming into Zimbra but was fine coming in Google Mail. You'll notice on the Google Mail zip file that the attachment has the necessary footers you would expect that the Zimbra message does not.

Thoughts?

[KevinH]

Hard to say but seems the problem is at Postfix since amavis already is complaining about the missing boundary before it gets passed off to Zimbra via LMTP. Can you post a more complete log from /var/log/zimbra.log when the mail arrives?