You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-AntiPhishPolicy.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,7 +128,7 @@ This setting is part of spoof protection.
128
128
The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are:
129
129
130
130
- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
131
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
131
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
132
132
133
133
```yaml
134
134
Type: SpoofAuthenticationFailAction
@@ -588,7 +588,7 @@ The MailboxIntelligenceProtectionAction parameter specifies what to do with mess
588
588
- BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message.
589
589
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
590
590
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
591
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
591
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
592
592
- Redirect: Redirect the message to the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter.
593
593
594
594
This parameter is meaningful only if the EnableMailboxIntelligence and EnableMailboxIntelligenceProtection parameters are set to the value $true.
@@ -798,7 +798,7 @@ The TargetedDomainProtectionAction parameter specifies the action to take on det
798
798
- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message.
799
799
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
800
800
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
801
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
801
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
802
802
- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter.
803
803
804
804
```yaml
@@ -891,7 +891,7 @@ The TargetedUserProtectionAction parameter specifies the action to take on detec
891
891
- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message.
892
892
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
893
893
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
894
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
894
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
895
895
- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -286,7 +286,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m
286
286
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
287
287
- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
288
288
- NoAction
289
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
289
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
290
290
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
291
291
292
292
```yaml
@@ -557,7 +557,7 @@ The HighConfidenceSpamAction parameter specifies the action to take on messages
557
557
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
558
558
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
559
559
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
560
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
560
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
561
561
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
562
562
563
563
```yaml
@@ -1037,7 +1037,7 @@ The PhishSpamAction parameter specifies the action to take on messages that are
1037
1037
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
1038
1038
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
1039
1039
- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins.
1040
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1040
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1041
1041
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
1042
1042
1043
1043
```yaml
@@ -1172,7 +1172,7 @@ The SpamAction parameter specifies the action to take on messages that are marke
1172
1172
- Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
1173
1173
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
1174
1174
- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
1175
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1175
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1176
1176
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ This setting is part of spoof protection.
131
131
The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are:
132
132
133
133
- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
134
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
134
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
135
135
136
136
```yaml
137
137
Type: SpoofAuthenticationFailAction
@@ -589,7 +589,7 @@ The MailboxIntelligenceProtectionAction parameter specifies what to do with mess
589
589
- BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message.
590
590
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
591
591
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
592
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
592
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
593
593
- Redirect: Redirect the message to the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter.
594
594
595
595
This parameter is meaningful only if the EnableMailboxIntelligence and EnableMailboxIntelligenceProtection parameters are set to the value $true.
@@ -767,7 +767,7 @@ The TargetedDomainProtectionAction parameter specifies the action to take on det
767
767
- BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message.
768
768
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
769
769
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
770
-
- Quarantine: Move the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
770
+
- Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
771
771
- Redirect: Redirect the message to the recipients specified by the TargetedDomainActionRecipients parameter.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -288,7 +288,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m
288
288
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
289
289
- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
290
290
- NoAction
291
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
291
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
292
292
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
293
293
294
294
```yaml
@@ -558,7 +558,7 @@ The HighConfidenceSpamAction parameter specifies the action to take on messages
558
558
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
559
559
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
560
560
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
561
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
561
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
562
562
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
563
563
564
564
```yaml
@@ -1059,7 +1059,7 @@ The PhishSpamAction parameter specifies the action to take on messages that are
1059
1059
- Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
1060
1060
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
1061
1061
- MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
1062
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1062
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1063
1063
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
1064
1064
1065
1065
```yaml
@@ -1178,7 +1178,7 @@ The SpamAction parameter specifies the action to take on messages that are marke
1178
1178
- Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
1179
1179
- ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
1180
1180
- MoveToJmf: This is the default value. Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder. In standalone Exchange Online Protection environments, you need to configure mail flow rules in your on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
1181
-
- Quarantine: Move the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1181
+
- Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
1182
1182
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
0 commit comments