Microsoft small business knowledge base

Article ID: 254893 - Last Review: January 10, 2015 - Revision: 5.0

Hotfix Download Available
View and request hotfix downloads
This article has been archived. It is offered "as is" and will no longer be updated.


If you send an e-mail message to an invalid domain name that contains a trailing space (for example, ), 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
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.


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:
Collapse this imageExpand this image
Download Q248838engi.exe now (
Collapse this imageExpand this image
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.


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.
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical KB254893
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support