Message Identifier Tracking for Outbound Messages
Message Identifier Tracking for Outbound Messages
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
The following topics discuss message identifier (ID) tracking when a message is transferred from the Microsoft® Exchange server to the foreign system, and when a delivery or nondelivery report is returned from the foreign system to the server. It is important to track message IDs so that useful debugging information ends up in the Exchange System Manager error logs. This avoids message loops, and allows users to receive proper reports about a message.
Client to Server Message Transfer
Server to Gateway Message Transfer
Gateway to Foreign System Message Transfer
Foreign System to Gateway Report Transfer
Gateway to Server Report Transfer
Server to Client Report Transfer
These topics correspond to the following steps:
The client application creates a new message and submits it to the server.
The server transfers the message to a gateway.
The gateway translates the message into the message format of the foreign system and submits it to the foreign system.
The foreign system sends a report back to the gateway.
Note This report might not be sent until a substantial time after the gateway sends the message that triggered the report.
The gateway translates the report into a MAPI message and submits it to the server.
The server delivers the report to the user who sent the original message.
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.