Application-generated email messages or email messages from a user in an external organization generate an NDR that has a 5.6.0 status code when messages are sent to an Exchange Server user

Article ID: 2710089 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenarios.

Scenario 1
  • You send an email message to a recipient.
  • The email message includes an attachment.
  • The mailbox for the recipient is hosted on Microsoft Exchange Server 2010 or on Microsoft Exchange Server 2007.
  • The mailbox for the recipient is in an external organization.
In this scenario, the email message is not delivered to the recipient as expected. When this issue occurs, you receive a non-delivery report that contains the following status code:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##
Scenario 2
  • An application generates an email message and sends the email message to a recipient.
  • The email message includes an attachment.
  • The mailbox for the recipient is hosted on Microsoft Exchange Server 2010 or on Microsoft Exchange Server 2007.
In this scenario, the email message is not delivered to the recipient as expected. When this issue occurs, a non-delivery report is generated that contains the following status code:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##
Back to the top | Give Feedback

CAUSE

This issue can occur if the attachment is encoded by using Base64 encoding.

Note Exchange Server accepts the standard mac-binhex encoding types.
Back to the top | Give Feedback

RESOLUTION

To resolve this issue, encode the attachment by using a standard mac-binhex type as defined in RFC 1741. For example, encode the attachment by using mac-binhex40 encoding.
Back to the top | Give Feedback

MORE INFORMATION

When the issue that is described in the "Symptoms" section occurs, the email message header contains the following Content-Type header value:
Content-Type: application/mac-binhex40
Content-Transfer-Encoding: base64
When you encode an attachment by using the mac-binhex40 encoding type, the message header resembles the following:
Content-Type: application/mac-binhex40
Content-Disposition: attachment; filename="filename"
Back to the top | Give Feedback

REFERENCES

For more information about the mac-binhex40 encoding type and about RFC 1741, visit the following MSDN website:
http://msdn.microsoft.com/en-us/library/gg671978(v=exchg.80).aspx
(http://msdn.microsoft.com/en-us/library/gg671978(v=exchg.80).aspx)
Back to the top | Give Feedback

Properties

Article ID: 2710089 - Last Review: May 15, 2012 - Revision: 1.1
APPLIES TO
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Exchange Server 2007 Enterprise Edition
Keywords: 
kbsurveynew kbprb kbtshoot KB2710089
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top