XFOR: Store Generates NDR to an SMTP Report If Prohibit Receive Is Enabled and Active

Article translations Article translations
Article ID: 238498 - View products that this article applies to.
This article was previously published under Q238498
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

The information store generates a non-delivery report (NDR) to an SMTP report when an SMTP report is returned to a mailbox that meets all of the following conditions:
  • The mailbox size currently exceeds the set limit.
  • The Prohibit send and receive (K) option is selected.
  • The Internet Mail Service is on a server different from the mailbox.
This could cause a message loop as the report is addressed to a null (<>) address, which means the Internet Mail Service cannot deliver the message. At this point, the NDR is returned to the originator, which was the mailbox currently unable to accept mail. This may generate yet another NDR, and the whole process repeat itself.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 How to Obtain the Latest Exchange
The following files are available for download from the Microsoft Download Center:
x86:
Collapse this imageExpand this image
Download
Download Q248838engi.exe now

Alpha:
Collapse this imageExpand this image
Download
Download Q248838enga.exe now
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server Version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Properties

Article ID: 238498 - Last Review: October 21, 2013 - Revision: 4.2
APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB238498

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com