Reports

  • Article

Reports

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. Microsoft® Exchange Server gateways generate reports to inform the originator of a message whether the message has been delivered and received. Four classes of reports are supported:

A gateway should always generate nondelivery reports when messages cannot be delivered. Successful delivery reports are optional.

Users can request reports and receipts on a per-message basis. Gateways should inspect outgoing messages for the following MAPI properties to determine whether reports and receipts have been requested for the message:

  • PR_ORIGINATOR_DELIVERY_REPORT_REQUESTED
  • PR_ORIGINATOR_NON_DELIVERY_REPORT_REQUESTED
  • PR_READ_RECEIPT_REQUESTED
  • PR_NON_RECEIPT_NOTIFICATION_REQUESTED

Note  The PR_NON_RECEIPT_NOTIFICATION_REQUESTED property corresponds to a request for a nonread receipt.

All reports should conform to the minimum required content and semantics of the X.400 specification. Additional content and functionality is optional. For example, nondelivery reports often include the original message content, even though it is not required by the X.400 specification. This feature allows the originator to fix addressing problems and resend the message.

Fore more information about the differences between Exchange Server reports and the X.400 standard, see Deviations from the X.400 Standard.

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.