-   Linux - Networking (
-   -   554 5.6.0 STOREDRV.Deliver; Corrupt message content (

telakenesys 04-30-2009 08:05 PM

554 5.6.0 STOREDRV.Deliver; Corrupt message content
When one of my colleagues tries to send and email with *.PDF attachment they get the following undeliverable response:

#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##

I have using ClarkConnect 4.2 and my SMTP mail. It only seems to happen when the receiving server is M$ Exchange 2007.

The email is sent from a Mac running Thunderbird. I got them to send the email to my external personal address and it works fine. Although Evolution reports the attachment as:

Macintosh BinHex-encoded file attachment (filename.pdf)

Restarting the postfix service fixes the problem for a short time.

unSpawn 05-02-2009 05:59 AM


Originally Posted by telakenesys (Post 3526261)
It only seems to happen when the receiving server is M$ Exchange 2007.

If you put it that way then this is not an interoperability problem on the GNU/Linux side of things. This is the Linux - Networking forum. Not a mcrsft forum. That'll be /General. Please first search the vendors knowledgebase first for support for their proprietary commercial products. In this case you might want to check the software for available service packs as I understand there's been some fixes for conversion errors, else check Technet for troubleshooting at "Managing Content Conversion Tracing". Thanks for understanding that a freely accessable, provided-at-no-cost, volunteer-driven GNU/Linux forum should not have to cater to problems on the proprietary, commercial, standard-breaking ClippyOS side of things.

telakenesys 05-03-2009 08:08 PM

Well since the Exchange server(s) are outside of my network and therefore outside of my control I don't know quite how I would be able to install service packs and updates on them.

unSpawn 05-03-2009 08:23 PM

Maybe inform the ones who are supposed to be in control.

telakenesys 05-03-2009 10:03 PM

If you are not willing to try and help me with an issue that I have with the GNU/Linux side of things, that is all you have to say.

I only receive an back error from Exchange servers. The emails is received fine by other mail servers, but the attachment is not reported as the correct mime type. The file is still readable though.

I have contacted the people responsible for the servers we are having problems with, and they say that they are not having issues with email from any other source. Since there are many of them, and only one of us, it makes sense to start with our server.

I have also posted on the ClakConect forum, with no luck either. It seems that the community is no longer willing to help us guys who need the help.

unSpawn 05-05-2009 04:20 PM

Let's break things down so you understand: your colleague uses an OSS MUA. You use an OSS MUA. You admitted you received the email OK using another email address (other MTA mail route). You clearly said that your colleague had a problem when sending email through a certain brand MTA and the returned message supports that. I say the fact that you find you do not receive the answer you expect does in no way reflect back on this community or its willingness to help out. That said, BinHex makes sense because it's a Mac but if you believe it's something with the MIME type then you should have posted that more clearly and support it with the necessary details.

telakenesys 05-06-2009 01:26 AM

I'm sorry, I thought that I was clear with my problem.
What is it that I can tell you that might make it easier to find the problem, and in turn find a solution?

unSpawn 05-06-2009 04:06 AM

NP. Ask your colleague to resend the attachment but have him configure MUA compression for "AppleDouble" or "base64" (UUE) format. If that doesn't work ask him to compress it with (tar and) gzip and then use 'mpack' to send it. Let me know if those arrive OK through the troublesome MTA.

telakenesys 05-06-2009 07:56 PM

I have had them pack the file into a zip. This email was received fine, but the attachment couldn't be opened at the other end. I am waiting on them to try using AppleDouble or base64. Will report with the results.

telakenesys 05-06-2009 08:21 PM

Opened Thunderbird and went to Preferences. Under Advanced tab clicked 'Config Editor' button. Changed the value for 'mail.content_disposition_type' to '1'.

verything seems to be working now. The thing that has me confused is that it all worked fine when ever the CC box was restarted.


unSpawn 05-07-2009 04:23 AM

Well done fixing things.

All times are GMT -5. The time now is 08:29 AM.