Centralizing the Receipt of NDRs

To have nondelivery reports (NDRs) arrive at a central location when multiple instances of your client are running simultaneously

1. Set PR_REPORT_ENTRYID, PR_REPORT_NAME, and PR_REPORT_SEARCH_KEY to the appropriate values for the account that is to receive the reports. Create the entry identifier by calling IAddrBook::CreateOneOff if necessary.
2. Understand that there are messaging systems that will ignore the account you've requested for reports and send them to the originator. Reduce the impact that this will have on administrators that will need to move reports around by:
   • Giving your original message a distinct message class, such as IPM.Note.MSNNews. Look for incoming messages with class Report.IPM.Note.MSNNews.NDR and forward them to the account you intended reports to come to. At the same time, send e-mail to the messaging system that ignored your nondelivery report account to the affect that it should honor the PR_REPORT_ENTRYID property.
   • Most messaging systems which do not honor PR_REPORT_ENTRYID will not honor the MAPI message class conventions either. Therefore, you'll receive something that looks like a note. This is a little harder to deal with since the input is so variable. Look at the subject and forward it if you find either something from a list of words that mean "undeliverable" or something from your original subject.
   1. Be prepared to tune these lists over time.