XCON: NDR Shows the Exchange DN of User Instead of X.400 Address

ID: Q198392

The information in this article applies to:

SYMPTOMS

When you send messages using a Personal Distribution List to an invalid recipient on a remote site, you receive a non-delivery report (NDR) showing the the intended recipient's X.500 Distinguished Name (DN) ID instead of the X.400 address.

An example NDR showing this problem: 


   From: System Administrator
   Sent: Friday, June 12, 1998 5:37 PM
   To: c=US;a=;p=Microsoft;o=Laptop;dda:MSXCHNGE=//o=MICROSOFT//ou=Laptop
   //cn=Recipients//cn=101300;
   Subject: Undeliverable: Test message

   Your message did not reach some or all of the intended recipients.

   Subject: Test message
   Sent: 6/12/98 5:35 PM

   The following recipient(s) could not be reached:

   c=US;a=;p=Microsoft;o=Laptop;dda:MSXCHNGE=//o=MICROSOFT//ou=Laptop
   //cn=Recipients//cn=101300; on 6/12/98 5:37 PM
   The recipient name is not recognized
   MSEXCH:MSExchangeMTA:Laptop:CALGARY


CAUSE

The function call, EcDeliverReport, no longer returns the MH_T_DIRECTORY_NAME attribute to the Exchange Server information store after the application of Exchange Server 5.0 Service Pack 2 or Exchange Server 5.5 Service Pack 1.


RESOLUTION

Exchange Server 5.0

A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/support/supportnet/default.asp
The English version of this fix should have the following file attributes or later:
Component: Message Transfer Agent (MTA) 

   File Name      Version
   --------------------------
   Address.dll    5.0.1461.81
   Dbserver.sch   5.0.1461.81
   Dcprods.cat    5.0.1461.81
   Ems_rid.dll    5.0.1461.81
   Emsmta.exe     5.0.1461.81
   Infoblog.cfg   5.0.1461.81
   Infoplog.cfg   5.0.1461.81
   Infotlog.cfg   5.0.1461.81
   Infoxlog.cfg   5.0.1461.81
   Mmiext.dll     5.0.1461.81
   Mtacheck.exe   5.0.1461.81
   Mtamsg.dll     5.0.1461.81
   P2.xv2         5.0.1461.81
   P3.tpl         5.0.1461.81
   P772.tpl       5.0.1461.81
   X400om.dll     5.0.1461.81
   X400omv1.dll   5.0.1461.81

NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support

Exchange Server 5.5

A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/support/supportnet/default.asp
The English version of this fix should have the following file attributes or later:
Component: Message Transfer Agent (MTA) 

   File Name      Version
   -------------------------
   Dbserver.sch   5.5.2512.0
   Dcprods.cat    5.5.2512.0
   Ems_rid.dll    5.5.2512.0
   Emsmta.exe     5.5.2512.0
   Info4log.cfg   5.5.2512.0
   Infoblog.cfg   5.5.2512.0
   Infodlog.cfg   5.5.2512.0
   Infollog.cfg   5.5.2512.0
   Infotlog.cfg   5.5.2512.0
   Mtacheck.exe   5.5.2512.0
   Mtamsg.dll     5.5.2512.0
   P2.xv2         5.5.2512.0
   X400om.dll     5.5.2512.0
   X400omv1.dll   5.5.2512.0

NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0 Service Pack 2 and Microsoft Exchange Server version 5.5 Service Pack 1.

Additional query words: 


Keywords          : 
Version           : winnt:5.0 SP2,5.5 SP1
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 12, 1999