Microsoft KB Archive/254893

Knowledge Base

XFOR: Internet Mail Service Does Not Generate the Non-Delivery Report to the Sender

Article ID: 254893

Article Last Modified on 10/26/2006

---

APPLIES TO

• Microsoft Exchange Server 5.5 Service Pack 3

---

This article was previously published under Q254893

SYMPTOMS

If you send an e-mail message to an invalid domain name that contains a trailing space (for example, SMTP:joeuser@invaliddomain.com ), a non-delivery report (NDR) that indicates an invalid host is generated as expected. But if you click Send Again, you do not receive an additional NDR message. Instead, the Internet Mail Service logs the following event 4120 error message, and moves the message into the Archive folder:

Event Type: Error
Event Source: MSExchangeIMC
Event Category: Internal Processing
Event ID: 4120
Date: 1/11/2000
Time: 3:17:57 PM
User: N/A
Computer: BACON610
Description:
In the process of creating a notification of delivery failure to the sender of a message, an error occurred causing the notification to be aborted. The sender is not informed that his original message failed to be delivered.

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:

191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack

The following files are available for download from the Microsoft Download Center:

x86: Download Q248838engi.exe now
Alpha: 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 Service Pack 3. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Keywords: kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB254893

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.