XIMS: Deeply Nested NDR Messages Stuck in the Outbound Queue

View products that this article applies to.

This article was previously published under Q317124

Symptoms

A very large non-delivery report (NDR) is stuck in an SMTP virtual server queue. The following event log may also be generated:

Source: MSExchangeTransport
Category: Exchange Store Driver
Event ID: 327
Type: Warning

The following call : EcLocallyDeliverMsg to the store failed. Error code : -2147220731. MDB : f6eec9a2-1a12-40bf-9524-358d0afcdc12. FID : . MID : . File : C:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\Test.EML. 

For more information, click http://search.support.microsoft.com/search/?adv=1.

↑ Back to the top

Cause

A very deeply nested MIME message (perhaps caused by an NDR bouncing between servers) is too deep for the Exchange MIME parser to handle, so the parser returns MAPI_E_TOO_BIG. This error is inadvertently regarded as a retry error, so the message is never moved to the Badmail folder. The message sticks in the Queue folder as the server repeatedly retries to parse it.

↑ Back to the top

Resolution

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

This fix causes Exchange to treat MAPI_E_TOO_BIG as a non-retry error and move these messages to the Badmail folder.

The English version of this fix should have the following file attributes or later:

Component: SMTP

File name	Version
Drviis.dll	6.0.5770.58

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

↑ Back to the top