"554 5.6.0" NDR when you try to send messages that have attachments in an Exchange Server 2007 environment

View products that this article applies to.

Symptoms

Assume that you try to send a message that has an attachment to a distribution list in a Microsoft Exchange Server 2007 environment. However, the message is not delivered, and you receive a non-delivery report (NDR) that contains the following information:

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

Additionally, if content conversion tracing is enabled, the following information is recorded in a content conversion tracing file:

Microsoft.Exchange.Data.Storage.ConversionFailedException: Content conversion: Corrupt summary tnef content.
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.GetMimeMessageClass()
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItemInternal(MimePromotionFlags promotionFlags)
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.<>c__DisplayClasse.<ConvertToItem>b__c()
at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall)
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItem(MimePromotionFlags promotionFlags)
at Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertAnyMimeToItem(Item itemOut, EmailMessage messageIn, InboundConversionOptions options, MimePromotionFlags promotionFlags, Boolean isStreamToStream)
at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToItem(Item itemOut, EmailMessage messageIn, InboundConversionOptions options, MimePromotionFlags flags)
InboundConversionOptions:
- preferredCharset: Charset
- trustAsciiCharsets: True
- isSenderTrusted: False
- imceaResolveableDomain: Domain�
- preserveReportBody: False
- clearCategories: True
- userADSession:
- recipientCache: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- clientSubmittedSecurely: False
- serverSubmittedSecurely: False
- disableNewXHeaderMapping: True
- convertReportToMessage: False
- treatInlineDispositionAsAttachment: False
- preferredInternetCodePageForShiftJis: Code page�
- combineMixedContentBodies: True
ConversionLimits:
- maxMimeTextHeaderLength: Length�
- maxMimeSubjectLength: Length�
- maxSize: Size�
- maxMimeRecipients: Number�
- maxRecipientPropertyLength: Length�
- maxBodyPartsTotal: Number�
- maxEmbeddedMessageDepth: Number
- exemptPFReplicationMessages: True

↑ Back to the top

Cause

This issue occurs because of a race condition when Exchange server submits messages. The race condition occurs when different threads process a message at the same time. Therefore, the categorizer treats the message as corrupted and blocks the message submission.

↑ Back to the top