Expand the New-TransportRule –RejectMessageReasonText parameter to allow 1024 characters and add HTML support
Expand the New-TransportRule –RejectMessageReasonText parameter to allow 1024 characters and add HTML support. Adding a RejectMessageReasonURL parameter to add a URL that would be referenced for NDRs of blocked messages would be good, too.
Victor S. (OC) commented
Having these suggestions implemented would be very useful and reduce confusion for recipients.
The RejectMessageReasonText text blends into the rest of the NDR to the point where many recipients don't notice it; they are overwhelmed with all of the other technical information in the NDR. Some internal recipients open a help desk ticket when they cannot send a specific email, even though the fix is simple and explained in the text. Changing some of the text to ALL CAPS makes it more noticable for some people, but not for everyone.
External recipients often reply to the NDR even though the text specifically tells them not to. This results in the email going to our postmaster address instead of the intended recipient.
Allowing more than 128 characters:
Some reasons and fixes are difficult to explain in 128 characters. Sometimes, just a few additional characters would make the text more comprehensible. It would also allow text that is more professional; non-standard abbreviations would not have to be used and more appropriate words can be used in place of shorter words that are less meaningful.
Adding a URL:
If HTML and more characters were allowed, a separate parameter would not be needed since the URL could be incorporated into the text. If the the admin wants the URL separated from the rest of the text, line breaks can be used.
Yes, I would like to see that too! Especially the HTML part, I would like to have a custom NDR like "You message has been denied, CLICK HERE to read our company policy".
I say YES! We want More!