Attachments Getting Munged

[KevinH]

Any other thoughts on this issue? Today I received an email with two attachments. Both Word documents. One document came through fine. The other one did not.

It's getting to the point where I am seriously contemplating shutting off my Zimbra server as I can't trust that the attachments people are sending me are going to make it through.

Can you reproduce it with the one that did not come thought? Were both attachments the same size? Sent from the same mail client on the same mail path? What was wrong with the one that didn't come through or did you not get it at all? If so how did you know you didn't get it?

[taliskar]

In the multiple attachment message, there were two attachments sent. The message sent came from a person I don't normally receive messages from. It appears from the message source that the sender used Squirrelmail to send the attachments from a hosted service.

The total message size was 81Kb. The first attachment (I could open this one) was 32.8Kb and the second attachment (I could not open this one) was 23.8Kb (or the message fragment was that size).

When you look at the message source (see zip file below), you see the appropriate file header and footer for the first attachment but only the header for the second.

This is consistent with the behavior I saw in previous messages where attachments were getting munged. Zimbra cut off the footer for the second attachment.

[anand]

taliskar,

kevinh has been beating me up about your problem.

From your initial posts it appears that the bottom portion of the message is chopped off even before it gets to amavisd-new.

Apr 21 10:49:45 email amavis[25617]: (25617-01) WARN: MIME::Parser error: part did not end with expected boundary

So question is ... is this a bug in amavisd-new/MIME parser, or was the message corrupt even before it got to amavisd-new and/or postfix. One way to find out is to stop amavisd-new (even though it is enabled in postfix). This will cause postfix to queue files into the deferred queue. Then we can look at that queue file and see if the message was corrupt by the time it reached postfix. If it is OK in the postfix queue, and corrupt per amavisd-new we have a bug we need to track down (for which we would need the original message anyway, so this exercise is required either way).

To stop amavisd-new do this as the zimbra user:

$ zmamavisdctl stop

Then send the message and look for the queue file.

$ mailq
D125A828AF0      554 Wed May  3 11:21:57  anandp@phillip.liquidsys.com
...

Now locate where that queue file is and run postcat on it:

# /opt/zimbra/postfix/sbin/postcat  /opt/zimbra/postfix/spool/deferred/D/D125A828AF0

Now see what the message contents are? Does it look OK? If it is already chopped then the problem is somewhere upstream of Zimbra. If not can you please post your queue file as an attachment.

[anand]

PS: don't forget to start your amavisd back up after CSI has left the building.

[taliskar]

OK, sorry to take so long to get to this.

Here's what I did:

1. Stopped amavisd-new per instructions
2. Sent one email with two file attachments (122Kb and 167Kb) from my work email account.
3. Identified the queue file for the message on my Zimbra server
4. Ran the Postcat command on the queue file and captured output in a text file (attached as sdresen-postcat.zip)
5. Review of postcat output suggests email is whole and intact as expected.
6. Rebooted the server
7. Went to look at email and find that it is munged as expected (attached as sdresen-munged-message.zip)


So, by your comments, this is an amavisd-new bug?

Thanks for all you help on this strange one!

[anand]

I am looking at your postcat output and the message clearly is damaged before it reached amavisd-new and most likely damaged before it reached postfix. You could edit master.cf and add -v -v at the end of the smtp service (smtpd -v -v -v) and try to run these messages and you should be able to log the SMTP incoming transaction to postfix, and you will most likely see that the message is already truncated when given to postfix. Beware - that is a very verbose log level - you should turn it off when you are done.

[taliskar]

Is it possible fetchmail is doing this? I'm using fetchmail to grab mail from my ISP and bring it into my Zimbra server.

What you're suggesting I do with the master.cf file is close to the edge of my mail admin abilities.

I don't know quite what else to do. I didn't have this problem before I migrated to Zimbra so I can only deduce that the problem is somewhere on the Zimbra server.

Not sure where to go next . . . . .

Scott

[taliskar]

I was able to resolve my munged attachment problem.

Solution: I shut down my Zimbra server and moved my mail over to Fastmail.

I no longer have issues receiving email attachments.

[pbruna]

Im having this same problem, did you find any solution?

[jholder]

Im having this same problem, did you find any solution?

What Zimbra version are you running?

Also, can you do a show original and zip it to this thread?

Thanks
john