Article ID: 303022
Article Last Modified on 2/21/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q303022
SYMPTOMS
If you send a message using a one-off X.400 address on the To line, you may receive a non-delivery report (NDR). For example, if the mail is addressed exactly in the following format below
[x400:g=givenname;s=surname;o=exchange;p=orgname;a= ;c=us;]
the message generates the following NDR:
Your message did not reach some or all of the intended recipients.
Subject: reversed address
Sent: 5/14/01 5:24 PM
The following recipient(s) could not be reached:
'g=givenname;s=surname;o=exchange;p=orgname;a= ;c=us;' on 5/14/01 5:24 PM
The e-mail account does not exist at the organization this
message was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.
server.domain.com #5.1.1
If the message is addressed using the more conventional format of c=us;a= ;p=, and so on, the address gets correctly resolved, and the message is delivered correctly. Therefore, if you resend the message that is addressed as follows, delivery will be successful:
[X400:c=us;a= ;p=orgname;o=exchange;s=surname;g=givenname;]
CAUSE
The reversed-format address is not being read correctly, resulting in the NDR.
RESOLUTION
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 the hotfix should have the following file attributes or later:
Component: GWART
| File name | Version |
|---|---|
| Gwart.dll | 6.0.4720.18 |
| Drviis.dll | 6.0.4720.18 |
| Exsmtp.dll | 6.0.4720.18 |
| Store.exe | 6.0.4720.18 |
| Jcb.dll | 6.0.4720.18 |
| Exoledb.dll | 6.0.4720.18 |
| Excdo.dll | 6.0.4720.18 |
| Mdbsz.dll | 6.0.4720.18 |
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
STATUS
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 2.
Keywords: kbbug kbexchange2000presp2fix kbexchange2000sp2fix kbfix KB303022
