XFOR: The Correlation Between a Message and a Report for Exchange Development Kit Connectors

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

SYMPTOMS

A connector for Exchange 2000 may not map reports [(N)DR, (N)RN] to the reports' related original messages, which were created by the connector and sent to an Exchange 2000 mailbox.

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

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.

MORE INFORMATION

A connector creates an IPM (envelope with an embedded message) in the MTS-IN folder, and then sends it to a mailbox in Exchange 2000. Exchange 2000 creates the DR (envelope with an embedded message), and then sends it to the connector's MTS-OUT folder.

After a user uses Microsoft Outlook 2000 to read the message in the Inbox, a read notification (RN) is created and submitted to the connector's MTS-OUT folder. The connector itself now has to map the original message (as created by the user) to the generated DR and RN.

Because a gateway is only a transporting system, a gateway can only determine whether a message can be transported or not. A gateway cannot indicate anything about the delivery status for each specific recipient; therefore, a gateway cannot create a delivery report. A delivery report must be created somewhere within Exchange 2000.

The PR_MTS_SUBJECT_ID of the report should contain the PR_MTS_ID value of the original message, rather than the PR_MTS_ID value of the report itself, and should therefore allow the connector to perform proper message- report matching, as the connector did earlier in Exchange Server 5.5.

Properties

Article ID: 309197 - Last Review: October 24, 2013 - Revision: 1.4
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbexchange2000presp2fix kbexchange2000sp2fix kbfix KB309197

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