Share via

Nondelivery Reports

  • Article

Nondelivery 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. A gateway should generate nondelivery reports whenever message delivery fails. The nondelivery report is returned to the original sender. Message delivery can fail for the following reasons:

  • Address mapping fails. This means that the gateway is unable to find or generate an address for a responsibility-TRUE recipient to which it can deliver the message.
  • The gateway is unable to connect to the foreign system. Typically, a gateway will make several attempts at regular intervals before deciding that a message cannot be delivered.
  • The gateway delivers the message to the foreign system, but the foreign system returns it as undeliverable. This can happen if the address of the recipient does not exist in the foreign system, or if local problems in the foreign system prevent delivery.

Like delivery reports, nondelivery reports can be generated by calling the MAPI method IMAPISupport::StatusRecips. However, because nondelivery reports are so important, you might want your gateway to generate its own nondelivery reports. These are messages with the message class REPORT.IPM.Note.NDR. A Microsoft® Exchange Server nondelivery report should contain at least the following elements:

  • A nondelivery report envelope. This is the report message itself.
  • A nondelivery report failed recipient list.
  • The original message.
  • The original message recipient list.

The original message and its recipient list are included in the nondelivery report as an embedded message attachment. For information about the properties for the envelope and failed recipient list, see the following topics:

Nondelivery Report Envelope Properties

Nondelivery Report Failed Recipient List Properties.

The remaining topics in this section provide information that is necessary to generate well-formed 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.