what needs to be changed to direct email to a third party remote spam filter

Skip to main content

Configure outbound spam filtering in EOP

• Article
• 01/06/2022
• 21 minutes to read

Is this page helpful?

Feedback will be sent to Microsoft: Past pressing the submit push button, your feedback volition be used to improve Microsoft products and services. Privacy policy.

In this article

Applies to

• Commutation Online Protection
• Microsoft Defender for Function 365 plan 1 and plan 2
• Microsoft 365 Defender

In Microsoft 365 organizations with mailboxes in Commutation Online or standalone Substitution Online Protection (EOP) organizations without Substitution Online mailboxes, outbound email messages that are sent through EOP are automatically checked for spam and unusual sending activity.

Outbound spam from a user in your organization typically indicates a compromised business relationship. Suspicious outbound messages are marked as spam (regardless of the spam confidence level or SCL) and are routed through the high-take a chance delivery pool to assist protect the reputation of the service (that is, keep Microsoft 365 source electronic mail servers off of IP block lists). Admins are automatically notified of suspicious outbound email activity and blocked users via alarm policies.

EOP uses outbound spam policies every bit part of your system's overall defence force confronting spam. For more than data, see Anti-spam protection.

Admins tin can view, edit, and configure (but non delete) the default outbound spam policy. For greater granularity, you tin likewise create custom outbound spam policies that employ to specific users, groups, or domains in your organization. Custom policies always take precedence over the default policy, only you can change the priority (running order) of your custom policies.

You can configure outbound spam policies in the Microsoft 365 Microsoft 365 Defender portal or in PowerShell (Exchange Online PowerShell for Microsoft 365 organizations with mailboxes in Exchange Online; standalone EOP PowerShell for organizations without Exchange Online mailboxes).

The basic elements of an outbound spam policy in EOP are:

• The outbound spam filter policy: Specifies the actions for outbound spam filtering verdicts and the notification options.
• The outbound spam filter rule: Specifies the priority and recipient filters (who the policy applies to) for a outbound spam filter policy.

The difference between these two elements isn't obvious when you manage outbound spam polices in the Microsoft 365 Defender portal:

• When y'all create a policy, yous're really creating a outbound spam filter rule and the associated outbound spam filter policy at the same time using the same proper name for both.
• When yous modify a policy, settings related to the name, priority, enabled or disabled, and recipient filters alter the outbound spam filter rule. All other settings modify the associated outbound spam filter policy.
• When you remove a policy, the outbound spam filter rule and the associated outbound spam filter policy are removed.

In Exchange Online PowerShell or standalone EOP PowerShell, you manage the policy and the rule separately. For more information, see the Apply Exchange Online PowerShell or standalone EOP PowerShell to configure outbound spam policies section after in this article.

Every organization has a built-in outbound spam policy named Default that has these properties:

• The policy is applied to all recipients in the organization, fifty-fifty though in that location's no outbound spam filter rule (recipient filters) associated with the policy.
• The policy has the custom priority value Lowest that you lot can't modify (the policy is always applied last). Whatever custom policies that you create always take a college priority than the policy named Default.
• The policy is the default policy (the IsDefault belongings has the value True), and you can't delete the default policy.

To increase the effectiveness of outbound spam filtering, you can create custom outbound spam policies with stricter settings that are applied to specific users or groups of users.

What practice you lot need to know before you begin?

• Y'all open the Microsoft 365 Defender portal at https://security.microsoft.com. To go directly to the Anti-spam settings page, utilise https://security.microsoft.com/antispam.

• To connect to Exchange Online PowerShell, see Connect to Substitution Online PowerShell. To connect to standalone EOP PowerShell, come across Connect to Exchange Online Protection PowerShell.

• You lot demand to exist assigned permissions in Exchange Online earlier y'all tin can do the procedures in this article:

  • To add, alter, and delete outbound spam policies, y'all need to be a member of the Organization Management or Security Administrator part groups.
  • For read-only access to outbound spam policies, you need to be a member of the Global Reader or Security Reader role groups.

  For more information, run into Permissions in Exchange Online.

  Notes:

  • Adding users to the corresponding Azure Active Directory role in the Microsoft 365 admin center gives users the required permissions and permissions for other features in Microsoft 365. For more than information, see About admin roles.
  • The View-Just Organization Management part group in Exchange Online as well gives read-merely access to the feature.

• For our recommended settings for outbound spam policies, meet EOP outbound spam filter policy settings.

• The default alert policies named Email sending limit exceeded, Suspicious email sending patterns detected, and User restricted from sending email already send email notifications to members of the TenantAdmins (Global admins) group about unusual outbound email activity and blocked users due to outbound spam. For more information, see Verify the alert settings for restricted users. We recommend that you apply these alarm policies instead of the notification options in outbound spam policies.

Use the Microsoft 365 Defender portal to create outbound spam policies

Creating a custom outbound spam policy in the Microsoft 365 Defender portal creates the spam filter dominion and the associated spam filter policy at the same time using the same proper noun for both.

1. In the Microsoft 365 Defender portal at https://security.microsoft.com, get to Email & Collaboration > Policies & Rules > Threat policies > Anti-spam in the Policies section. To go straight to the Anti-spam settings page, apply https://security.microsoft.com/antispam.

2. On the Anti-spam policies page, click Create policy so select Outbound from the drop downward list.

3. The policy wizard opens. On the Name your policy page, configure these settings:

   • Name: Enter a unique, descriptive name for the policy.
   • Clarification: Enter an optional description for the policy.

   When you're finished, click Next.

4. On the Users, groups, and domains page that appears, place the internal recipients that the policy applies to (recipient weather):

   • Users: The specified mailboxes, mail users, or mail contacts in your organization.
   • Groups: The specified distribution groups, mail-enabled security groups, or Microsoft 365 Groups in your organization.
   • Domains: All recipients in the specified accepted domains in your arrangement.

   Click in the appropriate box, showtime typing a value, and select the value that yous desire from the results. Repeat this process every bit many times every bit necessary. To remove an existing value, click remove adjacent to the value.

   For users or groups, you tin can utilize most identifiers (name, brandish proper name, alias, email address, account proper noun, etc.), just the corresponding display name is shown in the results. For users, enter an asterisk (*) by itself to see all available values.

   Multiple values in the same condition utilise OR logic (for example, <recipient1> or <recipient2>). Dissimilar weather condition use AND logic (for case, <recipient1> and <member of group 1>).

   • Exclude these users, groups, and domains: To add exceptions for the internal recipients that the policy applies to (recpient exceptions), select this option and configure the exceptions. The settings and beliefs are exactly like the conditions.

   When you're finished, click Adjacent.

5. On the Protection settings page that opens, configure the following settings:

   • Message limits: The settings in this section configure the limits for outbound electronic mail messages from Commutation Online mailboxes:

     • Prepare an external bulletin limit: The maximum number of external recipients per hr.
     • Set an internal message limit: The maximum number of internal recipients per hour.
     • Fix a daily message limit: The maximum total number of recipients per solar day.

     A valid value is 0 to 10000. The default value is 0, which means the service defaults are used. For more than information, come across Sending limits.

   Enter a value in the box, or apply the increment/decrease arrows on the box.

   • Restriction placed on users who reach the message limit: Select an action from the drop downward list when any of the limits in the Protection settings department are exceeded.

     For all actions, the recipients specified in the User restricted from sending e-mail alert policy (and in the at present redundant Notify these users and groups if a sender is blocked due to sending outbound spam setting later on this folio) receive email notifications.

     • Restrict the user from sending mail service until the following day: This is the default value. Electronic mail notifications are sent, and the user will be unable to send any more messages until the following mean solar day, based on UTC time. In that location is no style for the admin to override this cake.
       • The alert policy named User restricted from sending e-mail notifies admins (via email and on the Incidents & alerts > View alerts page).
       • Any recipients specified in the Notify specific people if a sender is blocked due to sending outbound spam setting in the policy are also notified.
       • The user volition be unable to send whatsoever more messages until the post-obit day, based on UTC time. There is no way for the admin to override this block.
     • Restrict the user from sending mail: Email notifications are sent, the user is added to Restricted users https://security.microsoft.com/restrictedusers in the Microsoft 365 Defender portal, and the user can't ship electronic mail until they're removed from Restricted users past an admin. After an admin removes the user from the list, the user won't be restricted over again for that day. For instructions, see Removing a user from the Restricted Users portal after sending spam email.
     • No activeness, alert just: Email notifications are sent.

   • Forwarding rules: Employ the settings in this department to control automated email forwarding by Exchange Online mailboxes to external senders. For more data, see Control automatic external email forwarding in Microsoft 365.

     Notation

     When automatic forwarding is disabled, the recipient will receive a non-delivery report (too known as an NDR or bounce message) if external senders transport electronic mail to a mailbox that has forwarding in place. If the message is sent by an internal sender and the forwarding method is mailbox forwarding (also known as SMTP forwarding), the internal sender will get the NDR. The internal sender does not get an NDR if the forwarding occurred due to an inbox dominion.

     Select one of the following actions from the Automatic forwarding rules drop downwardly listing:

     • Automatic - System-controlled: Allows outbound spam filtering to control automatic external electronic mail forwarding. This is the default value.
     • On: Automated external e-mail forwarding is not disabled past the policy.
     • Off: All automated external electronic mail forwarding is disabled by the policy.

   • Notifications: Use the settings in the section to configure boosted recipients who should receive copies and notifications of suspicious outbound email letters:

     • Send a re-create of suspicious outbound that exceed these limits to these users and groups: This setting adds the specified recipients to the Bcc field of suspicious outbound messages.

       Annotation

       This setting only works in the default outbound spam policy. It doesn't work in custom outbound spam policies that you create.

       To enable this setting, select the check box. In the box that appears, click in the box, enter a valid e-mail accost, and and then press Enter or select the complete value that's displayed below the box.

       Echo this step equally many times as necessary. To remove an existing value, click remove next to the value.

   • Notify these users and groups if a sender is blocked due to sending outbound spam

     Important

     • This setting is in the process of existence deprecated from outbound spam policies.

     • The default alert policy named User restricted from sending electronic mail already sends email notifications to members of the TenantAdmins (Global admins) group when users are blocked due to exceeding the limits in the Recipient Limits section. We strongly recommend that you use the alarm policy rather than this setting in the outbound spam policy to notify admins and other users. For instructions, see Verify the warning settings for restricted users.

   When yous're finished, click Next.

6. On the Review page that appears, review your settings. You tin select Edit in each department to change the settings within the department. Or yous can click Back or select the specific page in the wizard.

   When you're finished, click Create.

7. On the confirmation page that appears, click Done.

Utilize the Microsoft 365 Defender portal to view outbound spam policies

1. In the Microsoft 365 Defender portal at https://security.microsoft.com, go to E-mail & Collaboration > Policies & Rules > Threat policies > Anti-spam in the Policies department. To get directly to the Anti-spam settings page, use https://security.microsoft.com/antispam.

2. On the Anti-spam policies folio, look for one of the following values:

   • The Type value is Custom outbound spam policy
   • The Proper name value is Anti-spam outbound policy (Default)

   The following backdrop are displayed in the list of anti-spam policies:

   • Proper name
   • Condition
   • Priority
   • Blazon

3. When you lot select an outbound spam policy by clicking on the name, the policy settings are displayed in a flyout.

Utilize the Microsoft 365 Defender portal to change outbound spam policies

1. In the Microsoft 365 Defender portal, go to Email & Collaboration > Policies & Rules > Threat policies > Anti-spam in the Policies section.

2. On the Anti-spam policies page, select an outbound spam policy from the list past clicking on the name:

   • A custom policy that you lot created where the value in the Type column is Custom outbound spam policy.
   • The default policy named Anti-spam outbound policy (Default).

3. In the policy details flyout that appears, select Edit in each section to alter the settings within the section. For more information about the settings, run into the previous Utilise the Microsoft 365 Defender portal to create outbound spam policies section in this article.

   For the default outbound spam policy, the Applied to department isn't available (the policy applies to anybody), and you lot can't rename the policy.

To enable or disable a policy, set the policy priority order, or configure the end-user notifications, see the following sections.

Enable or disable custom outbound spam policies

Y'all tin't disable the default outbound spam policy.

1. In the Microsoft 365 Defender portal, become to Electronic mail & Collaboration > Policies & Rules > Threat policies > Anti-spam in the Policies section.

2. On the Anti-spam policies page, select a policy with the Type value of Custom outbound spam policy from the listing by clicking on the proper noun.

3. At the height of the policy details flyout that appears, y'all'll come across i of the following values:

4. In the confirmation dialog that appears, click Turn on or Turn off.

5. Click Shut in the policy details flyout.

Dorsum on the main policy page, the Status value of the policy will be On or Off.

Ready the priority of custom outbound spam policies

Past default, outbound spam policies are given a priority that's based on the order they were created in (newer policies are lower priority than older policies). A lower priority number indicates a college 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 take the same priority, and policy processing stops after the first policy is applied.

To change the priority of a policy, you click Increase priority or Decrease priority in the backdrop of the policy (you can't directly modify the Priority number in the Microsoft 365 Defender portal). Irresolute the priority of a policy only makes sense if you have multiple policies.

Notes:

• In the Microsoft 365 Defender portal, y'all can only change the priority of the outbound spam policy after you create information technology. In PowerShell, you tin override the default priority when you create the spam filter dominion (which tin bear on the priority of existing rules).
• Outbound spam policies are candy in the order that they're displayed (the first policy has the Priority value 0). The default outbound spam policy has the priority value Lowest, and you lot can't alter information technology.

1. In the Microsoft 365 Defender portal, go to Email & Collaboration > Policies & Rules > Threat policies > Anti-spam in the Policies department.

2. On the Anti-spam policies page, select a select a policy with the Blazon value of Custom outbound spam policy from the list past clicking on the name.

3. At the summit of the policy details flyout that appears, y'all'll run across Increase priority or Decrease priority based on the current priority value and the number of custom policies:

   • The outbound spam policy with the Priority value 0 has only the Decrease priority option available.
   • The outbound spam policy with the lowest Priority value (for example, iii) has only the Increment priority choice available.
   • If y'all have three or more than outbound spam policies, the policies betwixt the highest and lowest priority values take both the Increase priority and Decrease priority options available.

   Click Increase priority or Decrease priority to modify the Priority value.

4. When yous're finished, click Close in the policy details flyout.

Apply the Microsoft 365 Defender portal to remove custom outbound spam policies

When you use the Microsoft 365 Defender portal to remove a custom outbound spam policy, the spam filter rule and the respective spam filter policy are both deleted. You lot tin can't remove the default outbound spam policy.

1. In the Microsoft 365 Defender portal at https://security.microsoft.com, go to Electronic mail & Collaboration > Policies & Rules > Threat policies > Anti-spam in the Policies section. To go direct to the Anti-spam settings page, employ https://security.microsoft.com/antispam.

2. On the Anti-spam policies page, select a policy with the Blazon value of Custom outbound spam policy from the list past clicking on the name. At the top of the policy details flyout that appears, click More than actions > Delete policy.

3. In the confirmation dialog that appears, click Yes.

Employ Commutation Online PowerShell or standalone EOP PowerShell to configure outbound spam policies

As previously described, an outbound spam policy consists of an outbound spam filter policy and an outbound spam filter rule.

In Substitution Online PowerShell or standalone EOP PowerShell, the difference between outbound spam filter policies and outbound spam filter rules is apparent. You manage outbound spam filter policies by using the *-HostedOutboundSpamFilterPolicy cmdlets, and you manage outbound spam filter rules past using the *-HostedOutboundSpamFilterRule cmdlets.

• In PowerShell, you create the outbound spam filter policy outset, then you create the outbound spam filter rule that identifies the policy that the rule applies to.
• In PowerShell, y'all modify the settings in the outbound spam filter policy and the outbound spam filter dominion separately.
• When you remove a outbound spam filter policy from PowerShell, the corresponding outbound spam filter rule isn't automatically removed, and vice versa.

Apply PowerShell to create outbound spam policies

Creating an outbound spam policy in PowerShell is a two-step procedure:

1. Create the outbound spam filter policy.

2. Create the outbound spam filter rule that specifies the outbound spam filter policy that the dominion applies to.

   Notes:

   • Yous tin create a new outbound spam filter dominion and assign an existing, unassociated outbound spam filter policy to it. An outbound spam filter rule tin can't be associated with more than one outbound spam filter policy.
   • You lot can configure the following settings on new outbound spam filter policies in PowerShell that aren't available in the Microsoft 365 Defender portal until after you create the policy:
     • Create the new policy every bit disabled (Enabled $simulated on the New-HostedOutboundSpamFilterRule cmdlet).
     • Set the priority of the policy during creation (Priority <Number>) on the New-HostedOutboundSpamFilterRule cmdlet).
   • A new outbound spam filter policy that yous create in PowerShell isn't visible in the Microsoft 365 Defender portal until you lot assign the policy to an outbound spam filter rule.

Pace 1: Use PowerShell to create an outbound spam filter policy

To create an outbound spam filter policy, use this syntax:

              New-HostedOutboundSpamFilterPolicy -Name "<PolicyName>" [-AdminDisplayName "<Comments>"] <Additional Settings>                          

This example creates a new outbound spam filter policy named Contoso Executives with the following settings:

• The recipient rate limits are restricted to smaller values that the defaults. For more information, run into Sending limits across Microsoft 365 options.

• After one of the limits is reached, the user is prevented from sending messages.

              New-HostedOutboundSpamFilterPolicy -Name "Contoso Executives" -RecipientLimitExternalPerHour 400 -RecipientLimitInternalPerHour 800 -RecipientLimitPerDay 800 -ActionWhenThresholdReached BlockUser                          

For detailed syntax and parameter information, see New-HostedOutboundSpamFilterPolicy.

Step two: Use PowerShell to create an outbound spam filter rule

To create an outbound spam filter dominion, employ this syntax:

              New-HostedOutboundSpamFilterRule -Proper noun "<RuleName>" -HostedOutboundSpamFilterPolicy "<PolicyName>" <Recipient filters> [<Recipient filter exceptions>] [-Comments "<OptionalComments>"]                          

This example creates a new outbound spam filter rule named Contoso Executives with these settings:

• The outbound spam filter policy named Contoso Executives is associated with the rule.
• The rule applies to members of the group named Contoso Executives Group.

              New-HostedOutboundSpamFilterRule -Proper noun "Contoso Executives" -HostedOutboundSpamFilterPolicy "Contoso Executives" -FromMemberOf "Contoso Executives Group"                          

For detailed syntax and parameter data, come across New-HostedOutboundSpamFilterRule.

Employ PowerShell to view outbound spam filter policies

To render a summary list of all outbound spam filter policies, run this control:

              Become-HostedOutboundSpamFilterPolicy                          

To return detailed information near a specific outbound spam filter policy, utilize the this syntax:

              Go-HostedOutboundSpamFilterPolicy -Identity "<PolicyName>" | Format-List [<Specific backdrop to view>]                          

This example returns all the property values for the outbound spam filter policy named Executives.

              Get-HostedOutboundSpamFilterPolicy -Identity "Executives" | Format-List                          

For detailed syntax and parameter information, see Get-HostedOutboundSpamFilterPolicy.

Utilize PowerShell to view outbound spam filter rules

To view existing outbound spam filter rules, employ the post-obit syntax:

              Get-HostedOutboundSpamFilterRule [-Identity "<RuleIdentity>"] [-State <Enabled | Disabled>]                          

To return a summary list of all outbound spam filter rules, run this command:

              Get-HostedOutboundSpamFilterRule                          

To filter the list by enabled or disabled rules, run the post-obit commands:

              Get-HostedOutboundSpamFilterRule -State Disabled                          

              Become-HostedOutboundSpamFilterRule -State Enabled                          

To return detailed information about a specific outbound spam filter rule, use this syntax:

              Go-HostedOutboundSpamFilterRule -Identity "<RuleName>" | Format-List [<Specific properties to view>]                          

This instance returns all the property values for the outbound spam filter dominion named Contoso Executives.

              Become-HostedOutboundSpamFilterRule -Identity "Contoso Executives" | Format-List                          

For detailed syntax and parameter data, see Get-HostedOutboundSpamFilterRule.

Utilize PowerShell to modify outbound spam filter policies

The aforementioned settings are bachelor when you change a malware filter policy in PowerShell as when you create the policy as described in the Footstep ane: Use PowerShell to create an outbound spam filter policy department before in this article.

Note

You can't rename an outbound spam filter policy (the Set-HostedOutboundSpamFilterPolicy cmdlet has no Name parameter). When you lot rename an outbound spam policy in the Microsoft 365 Defender portal, you're just renaming the outbound spam filter dominion.

To modify an outbound spam filter policy, apply this syntax:

              Gear up-HostedOutboundSpamFilterPolicy -Identity "<PolicyName>" <Settings>                          

For detailed syntax and parameter information, see Set-HostedOutboundSpamFilterPolicy.

Use PowerShell to modify outbound spam filter rules

The only setting that isn't available when you modify an outbound spam filter rule in PowerShell is the Enabled parameter that allows you to create a disabled rule. To enable or disable existing outbound spam filter rules, encounter the adjacent section.

Otherwise, no additional settings are available when you change an outbound spam filter rule in PowerShell. The same settings are available when you create a dominion every bit described in the Step 2: Apply PowerShell to create an outbound spam filter rule department earlier in this article.

To alter an outbound spam filter rule, utilize this syntax:

              Gear up-HostedOutboundSpamFilterRule -Identity "<RuleName>" <Settings>                          

For detailed syntax and parameter information, come across Fix-HostedOutboundSpamFilterRule.

Use PowerShell to enable or disable outbound spam filter rules

Enabling or disabling an outbound spam filter rule in PowerShell enables or disables the whole outbound spam policy (the outbound spam filter rule and the assigned outbound spam filter policy). Y'all can't enable or disable the default outbound spam policy (it's always applied to all recipients).

To enable or disable an outbound spam filter rule in PowerShell, employ this syntax:

              <Enable-HostedOutboundSpamFilterRule | Disable-HostedOutboundSpamFilterRule> -Identity "<RuleName>"                          

This example disables the outbound spam filter rule named Marketing Department.

              Disable-HostedOutboundSpamFilterRule -Identity "Marketing Department"                          

This case enables same dominion.

              Enable-HostedOutboundSpamFilterRule -Identity "Marketing Department"                          

For detailed syntax and parameter data, see Enable-HostedOutboundSpamFilterRule and Disable-HostedOutboundSpamFilterRule.

Utilise PowerShell to gear up the priority of outbound spam filter rules

The highest priority value you tin attack a dominion is 0. The lowest value you can set depends on the number of rules. For case, if you lot accept 5 rules, yous tin utilize the priority values 0 through iv. Changing the priority of an existing rule can have a cascading effect on other rules. For example, if you accept five custom rules (priorities 0 through iv), and you lot modify the priority of a dominion to 2, the existing rule with priority 2 is changed to priority 3, and the rule with priority 3 is inverse to priority iv.

To set the priority of an outbound spam filter dominion in PowerShell, utilise the post-obit syntax:

              Set-HostedOutboundSpamFilterRule -Identity "<RuleName>" -Priority <Number>                          

This case sets the priority of the dominion named Marketing Department to two. All existing rules that have a priority less than or equal to ii are decreased by i (their priority numbers are increased by 1).

              Fix-HostedOutboundSpamFilterRule -Identity "Marketing Department" -Priority 2                          

Notes:

• To set the priority of a new dominion when you create it, employ the Priority parameter on the New-HostedOutboundSpamFilterRule cmdlet instead.
• The outbound default spam filter policy doesn't have a corresponding spam filter rule, and it ever has the unmodifiable priority value Lowest.

Use PowerShell to remove outbound spam filter policies

When you use PowerShell to remove an outbound spam filter policy, the corresponding outbound spam filter dominion isn't removed.

To remove an outbound spam filter policy in PowerShell, utilize this syntax:

              Remove-HostedOutboundSpamFilterPolicy -Identity "<PolicyName>"                          

This example removes the outbound spam filter policy named Marketing Department.

              Remove-HostedOutboundSpamFilterPolicy -Identity "Marketing Department"                          

For detailed syntax and parameter data, see Remove-HostedOutboundSpamFilterPolicy.

Use PowerShell to remove outbound spam filter rules

When you use PowerShell to remove an outbound spam filter dominion, the corresponding outbound spam filter policy isn't removed.

To remove an outbound spam filter rule in PowerShell, use this syntax:

              Remove-HostedOutboundSpamFilterRule -Identity "<PolicyName>"                          

This example removes the outbound spam filter rule named Marketing Department.

              Remove-HostedOutboundSpamFilterRule -Identity "Marketing Department"                          

For detailed syntax and parameter information, run across Remove-HostedOutboundSpamFilterRule.

For more information

Remove blocked users from the Restricted Users portal

High-risk delivery pool for outbound messages

Anti-spam protection FAQ

Automobile-forwarded messages written report

Feedback

Submit and view feedback for

hillierfeavainnince.blogspot.com

Source: https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/configure-the-outbound-spam-policy