Article ID: 254893 - Last Review: October 26, 2006 - Revision: 4.2 XFOR: Internet Mail Service Does Not Generate the Non-Delivery Report to the SenderThis 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. RESOLUTIONTo 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
(http://support.microsoft.com/kb/191914/EN-US/
)
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:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
Collapse this image ![]() Alpha: Collapse this image ![]() 119591
(http://support.microsoft.com/kb/119591/EN-US/
)
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.
STATUSMicrosoft 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.
| Article Translations
|

Back to the top

