Share via


View or Modify an Existing Custom DSN Message

 

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

You can use the Shell to view or modify a custom delivery status notification (DSN) message on a computer running Microsoft Exchange Server 2010 that has the Hub Transport server role or the Edge Transport server role installed.

You can only use the Set-SystemMessage cmdlet to modify DSN messages that have already been customized by using the New-SystemMessage cmdlet. If you want to customize the original text of a default DSN message provided by Exchange 2010, you must use the New-SystemMessage cmdlet to create a custom DSN. For more information about how to create a custom DSN message, see Create a Custom DSN Message.

Looking for other management tasks related to DSNs? Check out Managing Delivery Status Notifications.

Prerequisites

Before you perform these procedures, you must specify the identity of the message and prepare the text that you want to include in the message. For more information about how to specify the identity of a DSN message and how to work with the text of a customized DSN message, including how to format HTML DSN messages, see DSN Message Identity and DSN Message Text.

Use the Shell to change the text of a custom DSN message

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "DSNs" entry in the Transport Permissions topic.

Note

You can't use the EMC to change the text of a custom DSN message.

Use the Set-SystemMessage cmdlet to modify the settings of a custom DSN message. This example changes the text assigned to the DSN customized for DSN code 5.1.2 for the English language.

Set-SystemMessage En\Internal\5.1.2 -Text "The mailbox you tried to send an e-mail message to is disabled and is no longer accepting messages. Please contact the Help Desk at extension 123 for assistance."

For detailed syntax and parameter information, see Set-SystemMessage.

Use the Shell to view a list of custom DSN messages in your organization

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "DSNs" entry in the Transport Permissions topic.

Note

You can't use the EMC to view a list of custom DSN messages in your organization.

By default, the Get-SystemMessage cmdlet, which you use to view the configuration of custom DSN messages, returns a summary list of all custom DSN messages in your organization. This example returns a tabular list of all custom DSNs in your organization.

Get-SystemMessage

For detailed syntax and parameter information, see Get-SystemMessage.

Use the Shell to view a list of built-in DSN messages

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "DSNs" entry in the Transport Permissions topic.

Note

You can't use the EMC to view a list of built-in DSN messages.

This example, which requires the Get-SystemMessage command with the Original parameter, returns a list of the original DSN messages included with Exchange 2010.

Get-SystemMessage -Original

For detailed syntax and parameter information, see Get-SystemMessage.

Use the Shell to view detailed information about a custom DSN message

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "DSNs" entry in the Transport Permissions topic.

Note

You can't use the EMC to view detailed information about a custom DSN message.

Use the Get-SystemMessage command to view detailed configuration about a custom DSN message. This example shows detailed configuration for the internal 5.1.2 DSN customized for English.

Get-SystemMessage En\Internal\5.1.2 | Format-List

For detailed syntax and parameter information, see Get-SystemMessage.

 © 2010 Microsoft Corporation. All rights reserved.