Topic Last Modified: 2008-03-21
The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine if delivery status notifications (DSNs) on the Exchange Server computer are being rendered as standard messages:
If the Exchange Server Analyzer finds the RenderDSNsAsMessages registry entry present and configured with a value greater than 0, a non-default configuration message is displayed.
As its name implies, the RenderDSNsAsMessages registry entry represents a configuration opportunity that enables administrators to control how DSNs are rendered on Exchange 2000 Server and Exchange Server 2003 computers:
- If the value data for RenderDSNsAsMessages is set to 0,
DSNs (which include delivery reports and non-delivery reports) are
rendered as standard MAPI messages.
- If the value data for RenderDSNsAsMessages is set to any
value greater than 0, DSNs are rendered as multipart/mixed MIME
This registry value is not present by default and must be added manually to be used. In addition, for the entry to have the appropriate effect on Exchange 2000 Server, the computer must be running a minimum of the September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup.
|This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.|
To revert to the default configuration
Open a registry editor, such as Regedit.exe or Regedt32.exe.
Delete the RenderDSNsAsMessages registry entry.
Close the registry editor and restart the Microsoft Exchange Information Store service for the change to take effect.
- Before you edit the registry, and for information about how to
edit the registry, see the Microsoft Knowledge Base article 256986,
"Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).
- For more information about delivery status notification format
issues, see the Knowledge base article 812806, "Exchange user
unexpectedly receives a standard NDR instead of a custom NDR"
- For more information about the Exchange 2000 Server
Post-Service Pack 3 Rollup, see the Knowledge Base article
824282, "September 2003 Exchange 2000 Server Post-Service
Pack 3 Rollup" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=824282).