XADM: NDRs Occur If "(040)" and "(041)" Are in Domain-Defined Attribute Addresses; Fix Requires Exchange 2000 SP2

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


If you send a message through an X.400 connector to an X.400 address that is similar to the following address, you may receive a non-delivery report (NDR) from a remote foreign message transfer agent (MTA):
c=FR;a=ATLAS ;p=INTERNET;DDA:RFC-822=user(a)domain.com


This problem can occur because Exchange 2000 sends the message with the following address in the P2 field:


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
The English version of this fix should have the following file attributes or later:

Component: MTA

Collapse this tableExpand this table
File nameVersion

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


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.


The problem can occur if the X.400 address contains (u) or (a) signs.


Article ID: 315081 - Last Review: October 24, 2013 - Revision: 5.1
  • Microsoft Exchange Server 2000 Service Pack 1
  • Microsoft Exchange 2000 Server Service Pack 2
kbnosurvey kbarchive kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB315081

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