Did you know you can try the features in Microsoft 365 Defender for Office 365 Plan 2 for free? Use the 90-day Defender for Office 365 trial at the Microsoft 365 Defender portal trials hub. Learn about who can sign up and trial terms here.
- Exchange Online Protection
- Microsoft Defender for Office 365 plan 1 and plan 2
- Microsoft 365 Defender
This topic provides frequently asked questions and answers about anti-spam protection for Microsoft 365 organizations with mailboxes in Exchange Online, or standalone Exchange Online Protection (EOP) organizations without Exchange Online mailboxes.
For questions and answers about the quarantine, see Quarantine FAQ.
For questions and answers about anti-malware protection, see Anti-malware protection FAQ.
For questions and answers about anti-spoofing protection, see Anti-spoofing protection FAQ.
By default, what happens to a spam-detected message?
For inbound messages: The majority of spam is deleted via connection filtering, which is based on the IP address of the source email server. Anti-spam policies (also known as spam filter policies or content filter policies) inspect and classify messages as spam, bulk, or phishing. By default, messages that are classified as spam or bulk are delivered to the recipient's Junk Email folder, while messages classified as phishing are quarantined. You can modify the default anti-spam policy (applies to all recipients), or you can create custom anti-spam policies with stricter settings for specific groups of users (for example, you can quarantine spam that's sent to executives). For more information, see Configure anti-spam policies and Recommended anti-spam policy settings.
In hybrid deployments where EOP protects on-premises Exchange mailboxes, you need to configure two Exchange mail flow rules (also known as transport rules) in your on-premises Exchange organization to detect the EOP spam filtering headers that are added to messages. For details, see Configure EOP to deliver spam to the Junk Email folder in hybrid environments.
For outbound messages: The message is either routed through the high-risk delivery pool or is returned to the sender in a non-delivery report (also known as an NDR or bounce message). For more information about outbound spam protection, see Outbound spam controls.
What's a zero-day spam variant and how is it handled by the service?
A zero-day spam variant is a first generation, previously unknown variant of spam that's never been captured or analyzed, so our anti-spam filters don't yet have any information available for detecting it. After a zero-day spam sample is captured and analyzed by our spam analysts, if it meets the spam classification criteria, our anti-spam filters are updated to detect it, and it's no longer considered "zero-day."
If you receive a message that may be a zero-day spam variant, in order to help us improve the service, please submit the message to Microsoft using one of the methods described in Report messages and files to Microsoft.
Do I need to configure the service to provide anti-spam protection?
After you sign up for the service and add your domain, spam filtering is automatically enabled. By default, spam filtering is tuned to protect you without needing any additional configuration (aside from the previously noted exception for standalone EOP standalone customers in hybrid environments). As an admin, you can edit the default spam filtering settings to best meet the needs of your organization. For greater granularity, you can also create anti-spam policies and outbound anti-spam policies that are applied to specified users, groups, or domains in your organization. Custom policies always take precedence over the default policy, but you can change the priority (that is, the running order) of your custom policies.
For more information, see the following topics:
If I make a change to an anti-spam policy, how long does it take after I save my changes for them to take effect?
It may take up to 1 hour for the changes to take effect.
Is bulk email filtering automatically enabled?
Yes. For more information about bulk email, see What's the difference between junk email and bulk email?
Does the service provide URL filtering?
Yes, the service has a URL filter that checks for URLs within messages. If URLs associated with known spam or malicious content are detected then the message is marked as spam.
How can customers using the service send false negative (spam) and false positive (non-spam) messages to Microsoft?
Spam and non-spam messages can be submitted to Microsoft for analysis in several ways. For more information, see Report messages and files to Microsoft.
Can I get spam reports?
Yes, for example you can get a spam detection report in the Microsoft 365 admin center. This report shows spam volume as a count of unique messages. For more information about reporting, see the following links:
Exchange Online customers: Monitoring, Reporting, and Message Tracing in Exchange Online
Standalone EOP customers: Reporting and message trace in Exchange Online Protection
Someone sent me a message and I can't find it. I suspect that it may have been detected as spam. Is there a tool that I can use to find out?
Yes, the message trace tool enables you to follow email messages as they pass through the service, in order to find out what happened to them. For more information about how to use the message trace tool to find out why a message was marked as spam, see Was a message marked as spam?
Will the service throttle (rate limit) my mail if my users send outbound spam?
If more than half of the mail that is sent from a user through the service within a certain time frame (for example, per hour), is determined to be spam by EOP, the user will be blocked from sending messages. In most cases, if an outbound message is determined to be spam, it is routed through the high-risk delivery pool, which reduces the probability of the normal outbound-IP pool being added to a block list.
You can send a notification to a specified email address when a sender is blocked sending outbound spam. For more information about this setting, see Configure the outbound spam policy.
Can I use a third-party anti-spam and anti-malware provider in conjunction with Exchange Online?
Yes. Although we recommend that you point your MX record to Microsoft, we realize that there are legitimate business reasons to route your email to somewhere other than Microsoft first.
Inbound: Change your MX records to point to the third-party provider, and then redirect the messages to EOP for additional processing. For more information, see Enhanced Filtering for connectors in Exchange Online.
Outbound: Configure smart host routing from Microsoft 365 to the destination third-party provider.
Does Microsoft have any documentation about how I can protect myself from phishing scams?
Yes. For more information, see Protect your privacy on the internet
Are spam and malware messages being investigated as to who sent them, or being transferred to law enforcement entities?
The service focuses on spam and malware detection and removal, though we may occasionally investigate especially dangerous or damaging spam or attack campaigns and pursue the perpetrators. This may involve working with our legal and digital crime units to take down a spammer botnet, blocking the spammer from using the service (if they're using it for sending outbound email), and passing the information on to law enforcement for criminal prosecution.
What are a set of best outbound mailing practices that will ensure that my mail is delivered?
The guidelines presented below are best practices for sending outbound email messages.
The source email domain should resolve in DNS.
For example, if the sender is user@fabrikam, the domain fabrikam resolves to the IP address 126.96.36.199.
If a sending domain has no A-record and no MX record in DNS, the service will route the message through its higher risk delivery pool regardless of whether or not the content of the message is spam. For more information about the higher risk delivery pool, see High-risk delivery pool for outbound messages.
Outbound email server should have a reverse DNS (PTR) entry.
For example, if the email source IP address is 188.8.131.52, the reverse DNS entry would be
The HELO/EHLO and MAIL FROM commands should be consistent and be present in the form of a domain name rather than an IP address.
The HELO/EHLO command should be configured to match the reverse DNS of the sending IP address so that the domain remains the same across the various parts of the message headers.
Ensure that proper SPF records are set up in DNS.
SPF records are a mechanism for validating that mail sent from a domain really is coming from that domain and is not spoofed. For more information about SPF records, see the following links:
Signing email with DKIM, sign with relaxed canonicalization.
If a sender wants to sign their messages using Domain Keys Identified Mail (DKIM) and they want to send outbound mail through the service, they should sign using the relaxed header canonicalization algorithm. Signing with strict header canonicalization may invalidate the signature when it passes through the service.
Domain owners should have accurate information in the WHOIS database.
This identifies the owners of the domain and how to contact them by entering the stable parent company, point of contact, and name servers.
For bulk mailers, the From: name should reflect who is sending the message, while the subject line of the message should be a brief summary on what the message is about.
The message body should have a clear indication of the offering, service, or product. For example, if a sender is sending out a bulk mailing for the Contoso company, the following is what the email From and Subject should resemble:
Subject: New updated catalog for the Christmas season!
The following is an example of what not to do because it is not descriptive:
If sending a bulk mailing to many recipients and the message is in newsletter format, there should be a way of unsubscribing at the bottom of the message.
The unsubscribe option should resemble the following:
If sending bulk email, list acquisition should be performed using double opt-in. If you are a bulk mailer, double opt-in is an industry best practice.
Double opt-in is the practice of requiring a user to take two actions to sign up for marketing mail:
Once when the user clicks on a previously unchecked check box where they opt-in to receive further offers or email messages from the marketer.
A second time when the marketer sends a confirmation email to the user's provided email address asking them to click on a time-sensitive link that will complete their confirmation.
Using double opt-in builds a good reputation for bulk email senders.
Bulk senders should create transparent content for which they can be held accountable:
Verbiage requesting that recipients add the sender to the address book should clearly state that such action is not a guarantee of delivery.
When constructing redirects in the body of the message, use a consistent link style.
Don't send large images or attachments, or messages that are solely composed of an image.
When employing tracking pixels (web bugs or beacons), clearly state their presence in your public privacy or P3P settings.
Format outbound bounce messages.
When generating delivery status notification messages (also known as non-delivery reports, NDRs, or bounce messages), senders should follow the format of a bounce as specified in RFC 3464.
Remove bounced email addresses for non-existent users.
If you receive an NDR indicating that an email address is no longer in use, remove the non-existent email alias from your list. Email addresses change over time, and people sometimes discard them.
Use Hotmail's Smart Network Data Services (SNDS) program.
Hotmail uses a program called Smart Network Data Services that allows senders to check complaints submitted by end users. The SNDS is the primary portal for troubleshooting delivery problems to Hotmail.
How do I turn off spam filtering?
If you use a third-party protection service or device to scan email before it's delivered to Microsoft 365, you can use a mail flow rule (also known as a transport rule) to bypass most spam filtering for incoming messages. For instructions, see Use mail flow rules to set the spam confidence level (SCL) in messages.
If you use a mail flow rule to bypass spam filtering, high confidence phishing messages are still filtered. Other features in EOP are not affected (for example, messages are always scanned for malware).
If you use a third-party protection service or device to scan email before it's delivered to Microsoft 365, you should also enable Enhanced Filtering for Connectors (also known as skip listing) so detection, reporting, and investigation features in Microsoft 365 are able to correctly identify messages sources. For more information, see Enhanced Filtering for Connectors.
If you need to bypass spam filtering for SecOps mailboxes or phishing simulations, don't use mail flow rules. For more information, see Configure the delivery of third-party phishing simulations to users and unfiltered messages to SecOps mailboxes.