SpamSieve for Mac gives you back your inbox by bringing powerful Bayesian spam filtering to popular e-mail clients. It learns what your spam looks like, so it can block nearly all of it. It looks at your address book and learns what your good messages look like, so it won't confuse them with spam.
-->In Microsoft 365 organizations with mailboxes in Exchange Online or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes, inbound email messages are automatically protected against spam by EOP. EOP uses anti-spam policies (also known as spam filter policies or content filter policies) as part of your organization's overall defense against spam. For more information, see Anti-spam protection.
Admins can view, edit, and configure (but not delete) the default anti-spam policy. For greater granularity, you can also create custom anti-spam policies that apply to specific users, groups, or domains in your organization. Custom policies always take precedence over the default policy, but you can change the priority (running order) of your custom policies.
You can configure anti-spam policies in the Security & Compliance Center or in PowerShell (Exchange Online PowerShell for Microsoft 365 organizations with mailboxes in Exchange Online; standalone EOP PowerShell for organizations without Exchange Online mailboxes).
Anti-spam policies in the Security & Compliance Center vs PowerShell
The basic elements of an anti-spam policy in EOP are:
The spam filter policy: Specifies the actions for spam filtering verdicts and the notification options.
The spam filter rule: Specifies the priority and recipient filters (who the policy applies to) for a spam filter policy.
The difference between these two elements isn't obvious when you manage anti-spam polices in the Security & Compliance Center:
When you create an anti-spam policy in the Security & Compliance Center, you're actually creating a spam filter rule and the associated spam filter policy at the same time using the same name for both.
When you modify an anti-spam policy in the Security & Compliance Center, settings related to the name, priority, enabled or disabled, and recipient filters modify the spam filter rule. All other settings modify the associated spam filter policy.
When you remove an anti-spam policy from the Security & Compliance Center, the spam filter rule and the associated spam filter policy are removed.
In Exchange Online PowerShell or standalone EOP PowerShell, the difference between spam filter policies and spam filter rules is apparent. You manage spam filter policies by using the *-HostedContentFilterPolicy cmdlets, and you manage spam filter rules by using the *-HostedContentFilterRule cmdlets.
In PowerShell, you create the spam filter policy first, then you create the spam filter rule that identifies the policy that the rule applies to.
In PowerShell, you modify the settings in the spam filter policy and the spam filter rule separately.
When you remove a spam filter policy from PowerShell, the corresponding spam filter rule isn't automatically removed, and vice versa.
Default anti-spam policy
Every organization has a built-in anti-spam policy named Default that has these properties:
The spam filter policy named Default is applied to all recipients in the organization, even though there's no spam filter rule (recipient filters) associated with the policy.
The policy named Default has the custom priority value Lowest that you can't modify (the policy is always applied last). Any custom policies that you create always have a higher priority than the policy named Default.
The policy named Default is the default policy (the IsDefault property has the value
True), and you can't delete the default policy.
To increase the effectiveness of spam filtering, you can create custom anti-spam policies with stricter settings that are applied to specific users or groups of users.
What do you need to know before you begin?
You open the Security & Compliance Center at https://protection.office.com/. To go directly to the Anti-spam settings page, use https://protection.office.com/antispam.
To connect to Exchange Online PowerShell, see Connect to Exchange Online PowerShell. To connect to standalone EOP PowerShell, see Connect to Exchange Online Protection PowerShell.
You need to be assigned permissions before you can do the procedures in this topic:
To add, modify, and delete anti-spam policies, you need to be a member of one of the following role groups:
- Organization Management or Security Administrator in the Security & Compliance Center.
- Organization Management or Hygiene Management in Exchange Online.
For read-only access to anti-spam policies, you need to be a member of one of the following role groups:
- Security Reader in the Security & Compliance Center.
- View-Only Organization Management in Exchange Online.
For our recommended settings for anti-malware policies, see EOP anti-spam policy settings.
Use the Security & Compliance Center to create anti-spam policies
Creating a custom anti-spam policy in the Security & Compliance Center creates the spam filter rule and the associated spam filter policy at the same time using the same name for both.
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, click Create a policy.
In the New spam filter policy fly out that opens, configure the following settings:
Name: Enter a unique, descriptive name for the policy. Don't use the following characters:
% & * + / = ? { } | < > ( ) ; : , [ ] '.If you previously created anti-spam policies in the Exchange admin center (EAC) that contains these characters, you should rename the anti-spam policy in PowerShell. For instructions, see the Use PowerShell to modify spam filter rules section later in this topic.
Description: Enter an optional description for the policy.
(Optional) Expand the Spam and bulk actions section, and verify or configure the following settings:
Select the action to take for incoming spam and bulk email: Select or review the action to take on messages based on the following spam filtering verdicts:
- Spam
- High confidence spam
- Phishing email
- High confidence phishing email
- Bulk email
The available actions for spam filtering verdicts are described in the following table.
- A check mark ( ) indicates the action is available (not all actions are available for all spam filtering verdicts).
- An asterisk ( * ) after the check mark indicates the default action for the spam filtering verdict.
Spam High
confidence
spamPhishing
emailHigh
confidence
phishing
emailBulk
emailMove message to Junk Email folder: The message is delivered to the mailbox and moved to the Junk Email folder.1 * * * Add X-header: Adds an X-header to the message header and delivers the message to the mailbox.
You enter the X-header field name (not the value) later in the Add this X-header text box.
For Spam and High confidence spam verdicts, the message is moved to the Junk Email folder.1,2* Prepend subject line with text: Adds text to the beginning of the message's subject line. The message is delivered to the mailbox and moved to the Junk email folder.1,2
You enter the text later in the Prefix subject line with this text box.Redirect message to email address: Sends the message to other recipients instead of the intended recipients.
You specify the recipients later in the Redirect to this email address box.Delete message: Silently deletes the entire message, including all attachments. Quarantine message: Sends the message to quarantine instead of the intended recipients.
You specify how long the message should be held in quarantine later in the Quarantine box.* No action 1 In Exchange Online, the message is moved to the Junk Email folder if the junk email rule is enabled on the mailbox (it's enabled by default). For more information, see Configure junk email settings on Exchange Online mailboxes.
In standalone EOP environments where EOP protects on-premises Exchange mailboxes, you need to configure mail flow rules (also known as transport rules) in on-premises Exchange to translate the EOP spam filtering verdict so the junk email rule can move the message to the Junk Email folder. For details, see Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments.
2 You can this use value as a condition in mail flow rules (also known as transport rules) to filter or route the message.Select the threshold: Specifies the bulk complaint level (BCL) of a message that triggers the specified action for the Bulk email spam filtering verdict (greater than the specified value, not greater than or equal to). A higher value indicates the message is less desirable (more likely to resemble spam). The default value is 7. For more information, see Bulk complaint level (BCL) in EOP and What's the difference between junk email and bulk email?.
By default, the PowerShell only setting MarkAsSpamBulkMail is
Onin anti-spam policies. This setting dramatically affects the results of a Bulk email filtering verdict:MarkAsSpamBulkMail is On: A BCL that's greater than the threshold is converted to an SCL 6 that corresponds to a filtering verdict of Spam, and the action for the Bulk email filtering verdict is taken on the message.
MarkAsSpamBulkMail is Off: The message is stamped with the BCL, but no action is taken for a Bulk email filtering verdict. In effect, the BCL threshold and Bulk email filtering verdict action are irrelevant.
Quarantine: Specifies how long to keep the message in quarantine if you selected Quarantine message as the action for a spam filtering verdict. After the time period expires, the message is deleted. The default value is 30 days. A valid value is from 1 to 30 days. For information about quarantine, see the following topics:
Add this X-header text: This box is required and available only if you selected Add X-header as the action for a spam filtering verdict. The value you specify is the header field name that's added to the message header. The header field value is always
This message appears to be spam.The maximum length is 255 characters, and the value can't contain spaces or colons (:).
For example, if you enter the value
X-This-is-my-custom-header, the X-header that's added to the message isX-This-is-my-custom-header: This message appears to be spam.If you enter a value that contains spaces or colons (:), the value you enter is ignored, and the default X-header is added to the message (
X-This-Is-Spam: This message appears to be spam.).Prepend subject line with this text: This box is required and available only if you selected Prepend subject line with text as the action for a spam filtering verdict. Enter the text to add to the beginning of the message's subject line.
Redirect to this email address: This box is required and available only if you selected the Redirect message to email address as the action for a spam filtering verdict. Enter the email address where you want to deliver the message. You can enter multiple values separated by semicolons (;).
Safety Tips: By default, Safety Tips are enabled, but you can disable them by clearing the On checkbox. For more information about Safety Tips, see Safety tips in email messages.
Zero-hour auto purge settings: ZAP detects and takes action on messages that have already been delivered to Exchange Online mailboxes. For more information about ZAP, see Zero-hour auto purge - protection against spam and malware.
Spam ZAP: By default, ZAP is enabled for spam detections, but you can disable it by clearing the On checkbox.
Phish ZAP: By default, ZAP is enabled for phish detections, but you can disable it by clearing the On checkbox.
(Optional) Expand the Allow lists section to configure message senders by email address or email domain that are allowed to skip spam filtering:
Caution
• Think very carefully before you add domains here. For more information, see Create safe sender lists in EOP
• Never add accepted domains (domains that you own) or common domains (for example, microsoft.com or office.com) to the allowed domains list. This would allow attackers to send email that bypasses spam filtering into your organization.Allow sender: Click Edit. In the Allowed sender list flyout that appears:
a. Enter the sender's email address. You can specify multiple email addresses separated by semicolons (;).
b. Click to add the senders.
Repeat these steps as many times as necessary.
The senders you added appear in the Allowed Sender section on the flyout. To delete a sender, click .
When you're finished, click Save.
Allow domain: Click Edit. In the Allowed domain list flyout that appears do these steps:
a. Enter the domain. You can specify multiple domains separated by semicolons (;).
b. Click to add the domains.
Repeat these steps as many times as necessary.
Download drivers, software, firmware and manuals for your EOS 400D. Online technical support, troubleshooting and how-to’s. Canon eos 400d free download - EOS Utility, Canon EOS 20D Firmware Update, Canon EOS 10D firmware update, and many more programs. Eos 400d software mac. Non-Canon brand equipment and software that may be distributed with the Product are sold 'as is' and without warranty of any kind by Canon U.S.A. Or Canon Canada, including any implied warranty regarding merchantability or fitness for a particular purpose, and all such warranties are disclaimed. The sole warranty, if any, with the respect to. Download a user manual for your Canon product. Software Software Software. Download software for your Canon product. FAQs FAQs FAQs. Browse our frequently asked questions. Canon EOS 400D. Select your support content. Find the latest drivers for your product. Software to improve your experience with our products. Canon eos 400d free download - EOS Utility, Canon EOS 20D Firmware Update, Canon EOS D60, and many more programs.
The domains you added appear in the Allowed Domain section on the flyout. To delete a domain, click .
When you're finished, click Save.
(Optional) Expand the Block lists section to configure message senders by email address or email domain that will always be marked as high confidence spam:
Note
Manually blocking domains isn't dangerous, but it can increase your administrative workload. For more information, see Create block sender lists in EOP.
Block sender: Click Edit. In the Blocked sender list flyout that appears do these steps:
a. Enter the sender's email address. You can specify multiple email addresses separated by semicolons (;). Wildcards (*) aren't allowed.
b. Click to add the senders.
Repeat these steps as many times as necessary.
The senders you added appear in the Blocked Sender section on the flyout. To delete a sender, click .
When you're finished, click Save.
Block domain: Click Edit. In the Blocked domain list flyout that appears:
a. Enter the domain. You can specify multiple domains separated by semicolons (;). Wildcards (*) aren't allowed.
b. Click to add the domains.
Repeat these steps as many times as necessary.
The domains you added appear in the Blocked Domain list on the flyout. To delete a domain, click .
When you're finished, click Save.
(Optional) Expand the International spam section to configure the email languages or source countries that are blocked by spam filtering:
Filter email messages written in the following languages: This setting is disabled by default (Status: OFF). Click Edit. In the International spam settings flyout that appears, configure the following settings:
Filter email messages written in the following languages: Select the checkbox to enable this setting. Clear the checkbox to disable this setting.
Click in the box and start typing the name of the language. A filtered list of supported languages will appear, along with the corresponding ISO 639-2 language code. When you find the language you're looking for, select it. Repeat this step as many times as necessary.
The list of languages you selected appears on the flyout. To delete a language, click .
When you're finished, click Save.
Filter email messages sent from the following countries or regions: This setting is disabled by default (Status: OFF). To enable it, click Edit. In the International spam settings flyout that appears, configure the following settings:
Filter email messages sent from the following countries or regions: Select the checkbox to enable this setting. Clear the checkbox to disable this setting.
Click in the box and start typing the name of the country or region. A filtered list of supported countries will appear, along with the corresponding ISO 3166-1 two-letter country code. When you find the country or region you're looking for, select it. Repeat this step as many times as necessary.
The list of countries you selected appears on the flyout. To delete a country or region, click .
When you're finished, click Save.
The optional Spam properties section contains Advanced Spam Filter (ASF) settings that are turned off by default. ASF settings are in the process of being deprecated, and their functionality is being incorporated into other parts of the filtering stack. We recommend that you leave all of these ASF settings turned off in your anti-spam policies.
For details about these settings, see Advanced Spam Filter settings in EOP.
(Required) Expand the Applied to section to identify the internal recipients that the policy applies to.
You can only use a condition or exception once, but you can specify multiple values for the condition or exception. Multiple values of the same condition or exception use OR logic (for example, <recipient1> or <recipient2>). Different conditions or exceptions use AND logic (for example, <recipient1> and <member of group 1>).
It's easiest to click Add a condition three times to see all of the available conditions. You can click to remove conditions that you don't want to configure.
The recipient domain is: Specifies recipients in one or more of the configured accepted domains in your organization. Click in the Add a tag box to see and select a domain. Click again the Add a tag https://petrolucky.netlify.app/check-security-software-on-mac.html. box to select additional domains if more than one domain is available.
Recipient is: Specifies one or more mailboxes, mail users, or mail contacts in your organization. Click in the Add a tag and start typing to filter the list. Click again the Add a tag box to select additional recipients.
Recipient is a member of: Specifies one or more groups in your organization. Click in the Add a tag and start typing to filter the list. Click again the Add a tag box to select additional recipients.
Except if: To add exceptions for the rule, click Add a condition three times to see all of the available exceptions. The settings and behavior are exactly like the conditions.
When you're finished, click Save.
Use the Security & Compliance Center to view anti-spam policies
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, click to expand an anti-spam policy:
The default policy named Default spam filter policy.
A custom policy that you created where the value in the Type column is Custom anti-spam policy.
The important policy settings are displayed in the expanded policy details that appear. To see more details, click Edit policy.
Use the Security & Compliance Center to modify anti-spam policies
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, click to expand an anti-spam policy:
The default policy named Default spam filter policy.
A custom policy that you created where the value in the Type column is Custom anti-spam policy.
Click Edit policy.
For custom anti-spam policies, the available settings in the flyout that appears are identical to those described in the Use the Security & Compliance Center to create anti-spam policies section.
For the default anti-spam policy named Default spam filter policy, the Applied to section isn't available (the policy applies to everyone), and you can't rename the policy.
To enable or disable a policy, set the policy priority order, or configure the end-user quarantine notifications, see the following sections.
Enable or disable anti-spam policies
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, click to expand a custom policy that you created (the value in the Type column is Custom anti-spam policy).
In the expanded policy details that appear, notice the value in the On column.
Move the toggle to the left to disable the policy:
Move the toggle to the right to enable the policy:
You can't disable the default anti-spam policy.
Set the priority of custom anti-spam policies
By default, anti-spam policies are given a priority that's based on the order they were created in (newer polices are lower priority than older policies). A lower priority number indicates a higher priority for the policy (0 is the highest), and policies are processed in priority order (higher priority policies are processed before lower priority policies). No two policies can have the same priority.
Custom anti-spam policies are displayed in the order they're processed (the first policy has the Priority value 0). The default anti-spam policy named Default spam filter policy has the priority value Lowest, and you can't change it.
Note: In the Security & Compliance Center, you can only change the priority of the anti-spam policy after you create it. In PowerShell, you can override the default priority when you create the spam filter rule (which can affect the priority of existing rules).
To change the priority of a policy, move the policy up or down in the list (you can't directly modify the Priority number in the Security & Compliance Center).
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, find the policies where the value in the Type column is Custom anti-spam policy. Notice the values in the Priority column:
The custom anti-spam policy with the highest priority has the value 0.
The custom anti-spam policy with the lowest priority has the value n (for example, 3).
If you have three or more custom anti-spam policies, the policies between the highest and lowest priority have values n (for example, 2).
Click or to move the custom anti-spam policy up or down in the priority list.
Configure end-user spam notifications
When a spam filtering verdict quarantines a message, you can configure end-user spam notifications to let recipients know what happened to messages that were sent to them. For more information about these notifications, see End-user spam notifications in EOP.
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, click to expand an anti-spam policy:
The default policy named Default spam filter policy.
A custom policy that you created where the value in the Type column is Custom anti-spam policy.
In the expanded policy details that appear, click Configure end-user spam notifications.
In the <Policy Name> dialog that opens, configure the following settings:
Enable end-user spam notifications: Select the checkbobx to enable notifications. Clear the checkbox to disable notifications.
Send end-user spam notifications every (days): Select how frequently notifications are sent. The default value is 3 days. You can enter 1 to 15 days.
There are 3 cycles of end-user spam notification within a 24 hour period that start at the following times: 01:00 UTC, 08:00 UTC, and 16:00 UTC.
Note
If we missed a notification during a previous cycle, a subsequent cycle will push the notification. This may give the appearance of multiple notifications within the same day.
Notification language: Click the drop down an select an available language from the list. The default value is Default, which means end-user quarantine notifications use the default language of the EOP organization.
When you're finished, click Save.
Use the Security & Compliance Center to remove anti-spam policies
In the Security & Compliance Center, go to Threat management > Policy > Anti-spam.
On the Anti-spam settings page, click to expand the custom policy that you want to delete (the Type column is Custom anti-spam policy).
In the expanded policy details that appear, click Delete policy.
Click Yes in the warning dialog that appears.
You can't remove the default policy.
Use Exchange Online PowerShell or standalone EOP PowerShell to configure anti-spam policies
The following anti-spam policy settings are only available in PowerShell:
The MarkAsSpamBulkMail parameter that's
Onby default. The effects of this setting were explained in the Use the Security & Compliance Center to create anti-spam policies section earlier in this topic.The following settings for end-user spam quarantine notifications:
The DownloadLink parameter that shows or hides the link to the Junk Email Reporting Tool for Outlook.
The EndUserSpamNotificationCustomSubject parameter that you can use to customize the subject line of the notification.
Use PowerShell to create anti-spam policies
Creating an anti-spam policy in PowerShell is a two-step process:
Create the spam filter policy.
Create the spam filter rule that specifies the spam filter policy that the rule applies to.
Notes:
You can create a new spam filter rule and assign an existing, unassociated spam filter policy to it. A spam filter rule can't be associated with more than one spam filter policy.
You can configure the following settings on new spam filter policies in PowerShell that aren't available in the Security & Compliance Center until after you create the policy:
Create the new policy as disabled (Enabled
$falseon the New-HostedContentFilterRule cmdlet).Set the priority of the policy during creation (Priority<Number>) on the New-HostedContentFilterRule cmdlet).
A new spam filter policy that you create in PowerShell isn't visible in the Security & Compliance Center until you assign the policy to a spam filter rule.
Step 1: Use PowerShell to create a spam filter policy
To create a spam filter policy, use this syntax:
This example creates a spam filter policy named Contoso Executives with the following settings:
Quarantine messages when the spam filtering verdict is spam or high confidence spam.
BCL 6 triggers the action for a bulk email spam filtering verdict.
Note
New-HostedContentFilterPolicy and Set-HostedContentFilterPolicy contain an older ZapEnabled parameter, as well as newer PhishZapEnabled and SpamZapEnabled parameters. The ZapEnabled parameter was deprecated in February, 2020. The PhishZapEnabled and SpamZapEnabled parameters used to inherit their values from the ZapEnabled parameter. But, if you use the PhishZapEnabled and SpamZapEnabled parameters in a command or you use the Spam ZAP or Phish ZAP settings in the anti-spam policy in the Security & Compliance Center, the value of the ZapEnabled parameter is ignored. In other words, don't use the ZapEnabled parameter; use the PhishZapEnabled and SpamZapEnabled parameters instead.
For detailed syntax and parameter information, see New-HostedContentFilterPolicy.
Step 2: Use PowerShell to create a spam filter rule
To create a spam filter rule, use this syntax:
This example creates a new spam filter rule named Contoso Executives with these settings:
The spam filter policy named Contoso Executives is associated with the rule.
The rule applies to members of the group named Contoso Executives Group.
For detailed syntax and parameter information, see New-HostedContentFilterRule.
Use PowerShell to view spam filter policies
To return a summary list of all spam filter policies, run this command:
To return detailed information about a specific spam filter policy, use the this syntax:
This example returns all the property values for the spam filter policy named Executives.
For detailed syntax and parameter information, see Get-HostedContentFilterPolicy.
Use PowerShell to view spam filter rules
To view existing spam filter rules, use the following syntax:
To return a summary list of all spam filter rules, run this command:
To filter the list by enabled or disabled rules, run the following commands:
To return detailed information about a specific spam filter rule, use this syntax:
This example returns all the property values for the spam filter rule named Contoso Executives.
For detailed syntax and parameter information, see Get-HostedContentFilterRule.
Use PowerShell to modify spam filter policies
Other than the following items, the same settings are available when you modify a malware filter policy in PowerShell as when you create the policy as described in the Step 1: Use PowerShell to create a spam filter policy section earlier in this topic.
The MakeDefault switch that turns the specified policy into the default policy (applied to everyone, always Lowest priority, and you can't delete it) is only available when you modify a spam filter policy in PowerShell.
You can't rename a spam filter policy (the Set-HostedContentFilterPolicy cmdlet has no Name parameter). When you rename an anti-spam policy in the Security & Compliance Center, you're only renaming the spam filter rule.
To modify a spam filter policy, use this syntax:
For detailed syntax and parameter information, see Set-HostedContentFilterPolicy.
Use PowerShell to modify spam filter rules
The only setting that isn't available when you modify a spam filter rule in PowerShell is the Enabled parameter that allows you to create a disabled rule. To enable or disable existing spam filter rules, see the next section.
Otherwise, no additional settings are available when you modify a spam filter rule in PowerShell. The same settings are available when you create a rule as described in the Step 2: Use PowerShell to create a spam filter rule section earlier in this topic.
To modify a spam filter rule, use this syntax:
This example renames the existing spam filter rule named {Fabrikam Spam Filter} that might cause problems in the Security & Compliance Center.
For detailed syntax and parameter information, see Set-HostedContentFilterRule.
Use PowerShell to enable or disable spam filter rules
Enabling or disabling a spam filter rule in PowerShell enables or disables the whole anti-spam policy (the spam filter rule and the assigned spam filter policy). You can't enable or disable the default anti-spam policy (it's always always applied to all recipients).
To enable or disable a spam filter rule in PowerShell, use this syntax:
This example disables the spam filter rule named Marketing Department.
This example enables same rule.
For detailed syntax and parameter information, see Enable-HostedContentFilterRule and Disable-HostedContentFilterRule.
Use PowerShell to set the priority of spam filter rules
The highest priority value you can set on a rule is 0. The lowest value you can set depends on the number of rules. For example, if you have five rules, you can use the priority values 0 through 4. Changing the priority of an existing rule can have a cascading effect on other rules. For example, if you have five custom rules (priorities 0 through 4), and you change the priority of a rule to 2, the existing rule with priority 2 is changed to priority 3, and the rule with priority 3 is changed to priority 4.
To set the priority of a spam filter rule in PowerShell, use the following syntax:
This example sets the priority of the rule named Marketing Department to 2. All existing rules that have a priority less than or equal to 2 are decreased by 1 (their priority numbers are increased by 1).
Notes:
To set the priority of a new rule when you create it, use the Priority parameter on the New-HostedContentFilterRule cmdlet instead.
The default spam filter policy doesn't have a corresponding spam filter rule, and it always has the unmodifiable priority value Lowest.
Use PowerShell to remove spam filter policies
When you use PowerShell to remove a spam filter policy, the corresponding spam filter rule isn't removed.
To remove a spam filter policy in PowerShell, use this syntax:
This example removes the spam filter policy named Marketing Department.
For detailed syntax and parameter information, see Remove-HostedContentFilterPolicy.
Use PowerShell to remove spam filter rules
When you use PowerShell to remove a spam filter rule, the corresponding spam filter policy isn't removed.
To remove a spam filter rule in PowerShell, use this syntax:
This example removes the spam filter rule named Marketing Department.
For detailed syntax and parameter information, see Remove-HostedContentFilterRule.
How do you know these procedures worked?
Send a GTUBE message to test your spam policy settings
Note
These steps will only work if the email organization that you're sending the GTUBE message from doesn't scan for outbound spam. If it does, the test message can't be sent.
Generic Test for Unsolicited Bulk Email (GTUBE) is a text string that you include in a test message to verify your organization's anti-spam settings. A GTUBE message is similar to the European Institute for Computer Antivirus Research (EICAR) text file for testing malware settings.
Include the following GTUBE text in an email message on a single line, without any spaces or line breaks:
Allow/Block Lists
There will be times when our filters will miss the message or it takes time for our systems to catch up to it. In this cases, the antispam policy has an Allow and a Block list available to override the current verdict. This option should only be used sparingly since lists can become unmanageable and temporarily since our filtering stack should be doing what it is supposed to be doing.
Tip
There may be situations where your organization may not agree with the verdict the service provides. In this case, you may want to keep the Allow or Block listing permanent. However, if you are going to put a domain on the Allow list for extended periods of time, you should tell the sender to make sure that their domain is authenticated and set to DMARC reject if it is not.
Mail User Guide
Mail can filter junk mail from your inbox, based on what it learns from you when you mark email messages as junk or not junk and the settings in Junk Mail preferences.
Tip: If you don’t like spam, make sure the junk mail filter is on. Choose Mail > Preferences, click Junk Mail, then verify “Enable junk mail filtering” is selected.
Mark messages as junk or not junk
In the Mail app on your Mac, select a message.
Do one of the following:
If Mail incorrectly marked the message as junk: Click Move to Inbox in the message banner or click the Not Junk button in the Mail toolbar (or use the Touch Bar). Mail moves the message to your Inbox.
If Mail failed to mark the message as junk: Click the Junk button in the Mail toolbar (or use the Touch Bar). Mail moves the message to the Junk mailbox.
Spam Filtering Tools
Each time you confirm a message as junk or not junk, the junk mail filter improves so Mail can better identify junk mail.
Spam Filter For Mac Mail
Change junk mail filter settings
The default settings catch most of the junk mail you receive, but you can customize the filter.
In the Mail app on your Mac, choose Mail > Preferences, then click Junk Mail.
Specify what Mail should do when junk mail arrives.
If you want to verify what the filter identifies as junk mail, select “Mark as junk mail, but leave it in my Inbox.”
If you’re sure the filter accurately identifies junk mail, select “Move it to the Junk mailbox.”
To set up other actions, select “Perform custom actions,” then click Advanced.
Note: To make sure the filter’s database is used to identify junk mail, don’t change the default condition “Message is Junk Mail.”
Select options for exempting messages from being evaluated, such as messages received from people who use your full name.
To include in the filter any junk mail detection inherent in messages, select “Trust junk mail headers in messages.”
Reset the junk mail filter
Resetting the junk mail filter to its original state removes what Mail learned from you whenever you marked emails as junk or not junk.
Email Spam Filtering
In the Mail app on your Mac, choose Mail > Preferences, then click Junk Mail.
Click Reset.