XCON: Delivery Reports Contain only Distinguished Names in a Non-replicated Exchange EnvironmentID: Q166619
|
Delivery Reports (DRs) received from another Microsoft Exchange Server may only contain the Distinguished Name (DN) of the original recipient in the envelope. This behavior does not affect normal users, but if the DR is received by an EDK based agent or gateway, it is no longer possible to relate the DR to the original message. The DN used in the delivery report is not usable, since the receiving Microsoft Exchange Server doesn't have any information about the other Microsoft Exchange Organization.
This behavior can occur when the DR is generated by another Microsoft Exchange Organization that is connected by a 88 X400 Connector and Directory Replication is not configured between the two Organizations. As a result, the X.400 O/R address is stripped from the DR and when the MTA receives the DR, only the DN is left.
Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 4.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C KMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Use a 1984 X400 connection instead of a 1988 X400 connection.
The hotfix is only needed if you are working with two Microsoft Exchange
Servers that do not have Directory Replication configured between them or
that are in different Organizations. Without the fix, a DR may contain only
a DN that references the user to whom a message was delivered successfully.
The fix changes the handling of invalid DNs, so that the DR always
contains a valid, usable address. This address can be a O/R address or a
DN.
To install the fix, follow these steps:
ADDRESS.DLL, EMSMTA.EXE, MTACHECK.EXE, MMIEXT.DLL, SAALOG.DLL, EMS_RID.DLL, P2.XV2, X400OMV1.DLL
P2.XV2, INFOTLOG.CFG, INFODLOG.CFG, P3.TPL, DBSERVER.SCH, DCPRODS.CAT
ADDRESS.DLL
ADDRESS.DLL (if existing)
MTALOG.DLL
MAPI32.DLL
Keywords : kbbug4.00 kbbug5.00 kbfix5.00.sp2 XCON kbfix4.00.sp5
Version : 4.0,5.0
Platform : winnt
Issue type : kbbug
Last Reviewed: May 6, 1999