XCON: NDR for X.400 One-Off Address That Contains a Slash Mark (301020)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q301020 SYMPTOMS
On an Exchange 2000 server with regional settings than are different than United States settings, if you send a message to an X.400 one-off address that corresponds to a local mailbox and uses the slash mark (/) character (for example, [X400:/C=US/A= /P= MyCompany/O=corp/S= MyLastName/G= MyFirstName]), the message may generate a non-delivery report (NDR) that is similar to the following NDR:
The following recipient(s) could not be reached:
/C=US/A= /P=MyCompany/O=corp/S=MyLastName/G=MyFirstName on 05.04.2001 13:40
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.
<myserver.mycompany.com #5.1.1>
The following event ID 9004 error message is logged in the Application event log:
While processing user 'x400:/C=US/A= /P=MyCompany/O=corp/S=MyLastName/G=MyFirstName', the function 'CPhatCat::ProcessRecipient' called 'HrHandleOneOffOrContact' which returned error code '0xc0040557' (Some malformed property of the recipient caused it to be NDRd
). A DSN has been generated. ( U:\transmt\src\cat\sinks\phatcat\cptproc.cpp@232 )
RESOLUTIONTo 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: Transport core
|
| Resvc.dll | 6.0.4720.6 | 14-Jun-2001 | 0:23 | 327,952 | | Phatq.dll | 6.0.4720.6 | 14-Jun-2001 | 0:23 | 463,120 | | Tranmsg.dll | 6.0.4720.6 | 14-Jun-2001 | 0:23 | 184,592 | | Reapi.dll | 6.0.4720.6 | 14-Jun-2001 | 0:14 | 569,616 | | Mtaroute.dll | 6.0.4720.6 | 13-Jun-2001 | 19:39 | 82,192 |
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
STATUSMicrosoft 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.
| Modification Type: | Minor | Last Reviewed: | 6/5/2003 |
|---|
| Keywords: | kbbug kberrmsg kbExchange2000SP2Fix kbfix KB301020 |
|---|
|