Share via

Nonread Receipts

  • Article

Nonread Receipts

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. Nonread receipts are similar to read receipts, delivery reports, and nondelivery reports. They have message class strings of the form REPORT.X.NRN, where X is the message class of the message that the receipt corresponds to (usually IPM.Note). Nonread receipts inform a sender that a recipient has deleted a message without opening it. Read receipts are generated by the e-mail client software of the recipient. No other component of a messaging system can be guaranteed to know when a user deletes a message.

Whether a gateway can support nonread receipts depends on the capabilities of the foreign system. If the foreign system does support nonread receipts, gateways should perform the following tasks:

  • For an outgoing message, the gateway should convert the value stored in the PR_NON_RECEIPT_NOTIFICATION_REQUESTED property of the message into whatever format the foreign system requires for nonread receipt requests.
  • For an incoming nonread receipt, the gateway should convert the content of the receipt into a message of the message class REPORT.IPM.Note.NRN, and deliver this message to the sender of the original message.

For more information about the properties required on nonread receipts, see About Message Properties in the MAPI Programmer's Reference Online link.

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.