Mapping Message Identifiers

  • Article

Mapping Message Identifiers

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.

It is important to keep track of the various identifiers (IDs) that are assigned to a message as it is transferred between the Microsoft® Exchange server and the foreign system. These IDs are used to monitor the progress of the message and to construct delivery and nondelivery reports. These reports must be able to reference the original message ID at any point along the message path. This is because message IDs created in one system might not be usable in another system, due to incompatible formats.

A message can have up to four different IDs during the transfer process. These are:

  • A MAPI message ID for the message content.
  • A MAPI message ID for the message transfer envelope (MTE).
  • An Exchange Server message identifier (PR_MTS_ID).
  • A foreign system message identifier (PR_FOREIGN_ID).

The PR_MTS_ID and PR_FOREIGN_ID properties of all transferred messages are recorded by the Exchange System Manager in the accounting and audit log. The gateway stores all transferred messages for a length of time that is specified by the Exchange System Manager. This allows the gateway to construct complete delivery and nondelivery reports.

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.