Consider the following scenario:
- In Microsoft Exchange Server 2013, you create a customized delivery status notification (DSN) message by running the following New-SystemMessage cmdlet:New-SystemMessage -DsnCode 5.7.111 -Language en -Internal $true -Text "text_from_system_message"
- You create a transport rule. In the new rule, you do the following:
- Set the RejectMessageReasonText value to reject messages
- Add the DSN code
This issue occurs because the reject reason is passed as the dsnExplanation value of the SmtpResponse response. If the SmtpResponse response contains the RejectMessageReasonText value, it cannot be overridden by running the New-SystemMessage cmdlet.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 3003986 - Last Review: Dec 9, 2014 - Revision: 1
Exchange Server 2013 Enterprise, Exchange Server 2013 Standard Edition