The default reason text that's used is Delivery not authorized, message refused.
The recipient doesn't receive the original message or notification. Returns the message to the sender in an NDR with the specified enhanced delivery status notification (DSN) code.
Online message sender code#
Reject the message with the enhanced status codeīlock the message > reject the message with the enhanced status code of When you create or modify the rule in PowerShell, you can specify the DSN code by using the RejectMessageEnhancedStatusCode parameter. The default enhanced status code that's used is 5.7.1. Returns the message to the sender in a non-delivery report (also known as an NDR or bounce message) with the specified text as the rejection reason. For more information about connectors, see Configure mail flow using connectors.īlock the message > reject the message and include an explanation Uses the specified outbound connector to deliver the message. Redirect the message to > the following connector For more information, see Quarantined email messages in EOP. Redirect the message to > hosted quarantineĭelivers the message to the quarantine in EOP. The message isn't delivered to the original recipients, and no notification is sent to the sender or the original recipients.ĭeliver the message to the hosted quarantine Redirects the message to the specified recipients. Redirect the message to > these recipients Note: This action isn't available in standalone EOP environments. Otherwise, the message is delivered to the recipients without moderation. This action only works if the sender's Manager attribute is defined. Note: This action isn't available in standalone Exchange Online Protection (EOP) environments.įorward the message for approval to the sender's managerįorward the message for approval > to the sender's managerįorwards the message to the sender's manager for approval. You can't use a distribution group as a moderator. For more information, see Use mail flow rules for message approval scenarios in Exchange Online. The names of some of the actions that are returned by the Get-TransportRuleAction cmdlet are different than the corresponding parameter names, and multiple parameters might be required for an action.įorward the message for approval > to these peopleįorwards the message to the specified moderators as an attachment wrapped in an approval request.
Online message sender full#
The short names and full click path values are shown in the EAC column in the table. Also, when you create new rules, you can sometimes (depending on the selections you make) select a short action name from a template (a filtered list of actions) instead of following the complete click path. Valid values for each property are described in the Property values section.Īfter you select an action in the Exchange admin center (EAC), the value that's ultimately shown in the Do the following field is often different from the click path you selected. The actions that are available in mail flow rules in Exchange Online and standalone EOP are described in the following table. Actions for mail flow rules in Exchange Online For example, one rule can't reject and redirect the same message.įor more information about mail flow rules, including how multiple actions are handled, see Mail flow rules (transport rules) in Exchange Online.įor more information about conditions and exceptions in mail flow rules, see Mail flow rule conditions and exceptions (predicates) in Exchange Online.įor more information about actions in mail flow rules in Exchange Server, see or Mail flow rule actions in Exchange Server. Typically, you can configure multiple actions in a rule, but some actions are exclusive. When the rule adds a disclaimer to messages, you need to specify the disclaimer text, but you can also specify where to insert the text, or what to do if the disclaimer can't be added to the message. For example, when the rule adds a header field to the message header, you need to specify both the name and value of the header. Some actions have multiple properties that are available or required.
For example, when the rule redirects a message, you need to specify where to redirect the message. For example, you can create a rule that forwards message from specific senders to a moderator, or adds a disclaimer or personalized signature to all outbound messages.Īctions typically require additional properties. In Exchange Online organizations or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, actions in mail flow rules (also known as transport rules) specify what you want to do to messages that match conditions of the rule.
0 kommentar(er)
