Blog Microsoft 365

Business Emails Going to Spam? SPF, DKIM and DMARC Explained

By Evolution IT Services 6 min read

A client says they never got your quote. A vendor finds your invoice in their junk folder two weeks late. A new customer only replies after you call to ask whether they saw your email. When business email starts going to spam, it rarely announces itself. You find out one missed message at a time.

Sometimes the cause is the content of the message. Much more often, it is three DNS records most small businesses have never looked at: SPF, DKIM and DMARC. Since 2024, Gmail and Yahoo have been enforcing them, and Microsoft has followed for Outlook.com. This post explains what each one does in plain English, what the big mailbox providers now require, and how to roll out DMARC without blocking your own mail.

Business owner looking at an email inbox with a junk folder on a laptop

Why Receiving Servers Are Suspicious of Your Mail

Email was designed decades ago with no way to prove who sent a message. Anyone can type your address into the "From" line. Scammers do exactly that to send fake invoices and payment-change requests that look like they came from you. To fight this, receiving mail servers check whether a message really came from a server your domain has authorized. If they cannot tell, your legitimate mail gets treated like a possible fake.

SPF, DKIM and DMARC are how your domain answers that question. They are published in your domain's DNS, the public settings that also tell the world where your website and email live.

SPF: the list of who is allowed to send

SPF (Sender Policy Framework) is a single TXT record that lists the servers allowed to send mail for your domain. If you use Microsoft 365, it includes Microsoft's servers. If you also send invoices from accounting software, newsletters from an email marketing tool, or forms from your website, those services need to be on the list too.

Common SPF mistakes:

  • Two SPF records. You may only have one. Adding a second instead of editing the first breaks both.
  • Too many lookups. SPF allows at most ten DNS lookups. Every "include" for another service uses some. Go over and SPF fails.
  • Forgotten senders. The copier that scans to email, the website host, the CRM. If it sends as your domain and is not listed, it fails.

DKIM: A Signature on Every Message

DKIM (DomainKeys Identified Mail) adds a digital signature to each outgoing message. Receiving servers look up a public key in your DNS and confirm the signature matches. If someone changes the message in transit, or a stranger sends mail pretending to be you, the check fails.

In Microsoft 365, turning on DKIM for your own domain means publishing two CNAME records (selector1 and selector2) and then enabling signing in the Microsoft Defender portal. It is one of the first things we check in a Microsoft 365 security review. Other services you send through, such as your marketing or invoicing tools, usually offer their own DKIM records. Set those up too, so their mail is signed with your domain.

IT technician editing DNS records for a business domain on a monitor

DMARC: The Policy That Ties It Together

DMARC (Domain-based Message Authentication, Reporting and Conformance) does two things. First, it requires alignment: the domain in the visible "From" line must match the domain that passed SPF or DKIM. That closes the loophole where a scammer passes SPF for their own domain while showing yours to the reader. Second, it tells receiving servers what to do with mail that fails, and where to send reports.

A DMARC record is one TXT record at _dmarc.yourdomain.com, and its policy has three levels:

  • p=none means "do not change delivery, just send me reports."
  • p=quarantine means "put failing mail in spam."
  • p=reject means "refuse failing mail outright."

What Gmail and Yahoo Require Now

In February 2024, Google and Yahoo began enforcing sender requirements. Microsoft announced similar rules for high-volume senders to Outlook.com in 2025. The details are on each provider's sender guidelines page, and they get updated, but the core of it looks like this.

Everyone who sends to Gmail or Yahoo addresses should have:

  • SPF or DKIM set up for the sending domain
  • Valid forward and reverse DNS for sending servers (Microsoft 365 handles this for its own servers)
  • An encrypted (TLS) connection for sending
  • A low spam complaint rate. Google asks senders to stay under 0.3%, and ideally under 0.1%.

Bulk senders (Google's line is around 5,000 or more messages a day to personal Gmail accounts) must also have:

  • Both SPF and DKIM
  • A DMARC record, at least at p=none
  • Alignment between the From domain and SPF or DKIM
  • One-click unsubscribe on marketing mail, honored within two days

Most small offices are nowhere near 5,000 messages a day. But a newsletter list or a marketing tool can count toward it, and these settings now affect how everyone's mail gets treated. Getting SPF, DKIM and DMARC right is simply good practice at any size, and it is part of the email security work in our small business cybersecurity services.

Rolling Out DMARC Without Blocking Your Own Mail

The mistake to avoid is jumping straight to p=reject. If your accounting software or website form is not set up correctly, you will block your own invoices and leads. A safe rollout takes a few weeks:

  1. Start at p=none with reporting. Publish a DMARC record at p=none with a reporting address (the rua tag). Reports arrive as XML files, so a DMARC reporting tool helps turn them into something readable.
  2. Find every sender. For two to four weeks, read the reports. You will see every service sending as your domain, including ones you forgot about.
  3. Fix the legitimate senders. Add them to SPF, set up DKIM for each, and make sure they align with your domain. If something should not be sending as you at all, shut it off.
  4. Move to p=quarantine. Once reports show your real mail passing, switch to quarantine. Some people step up with the pct tag, applying the policy to a portion of failing mail first.
  5. Move to p=reject. After a few more weeks of clean reports, switch to reject. Now fake mail claiming to be from your domain gets refused.
  6. Keep watching. Every time you add a new tool that sends email, update SPF and DKIM before it goes live.

DMARC at reject is one of the best defenses against someone spoofing your domain to trick your clients. That is why it is part of our cybersecurity services for small businesses, alongside MFA and phishing training. If you have ever had a client get a fake "please update our bank details" email in your name, our post on protecting transactions from wire fraud is worth a read.

Office manager reviewing an email delivery report on a laptop

Other Reasons Mail Lands in Spam

If SPF, DKIM and DMARC all pass and mail still lands in junk, look at:

  • Website forms that send "from" the visitor. A contact form that sends as the visitor's Gmail address will fail DMARC. Send from your own domain and put the visitor in Reply-To.
  • A new or recently changed domain. Brand-new domains have no sending reputation yet and get extra scrutiny.
  • Link shorteners, image-only messages and attachments with macros. These all look like phishing.
  • A compromised mailbox. If an account was sending spam, your reputation may have taken a hit. Check sign-in logs and make sure MFA is on everywhere. Our post on what to do when a phishing email hits covers the cleanup.

Short Version

  • SPF lists who may send as your domain. DKIM signs each message. DMARC checks they align and tells receivers what to do with fakes.
  • Gmail and Yahoo have enforced sender rules since 2024. Bulk senders need SPF, DKIM, DMARC and one-click unsubscribe.
  • Roll DMARC out from p=none to quarantine to reject over several weeks, using the reports to fix your real senders first.
  • Revisit SPF and DKIM every time you add a tool that sends email.
Small business team reading client emails in a bright office

Let Us Check Your Domain

We set up and maintain SPF, DKIM and DMARC as part of our Microsoft 365 setup and security services, including the slow, careful walk from p=none to reject. Text our Redmond team at (541) 239-3338 or call (541) 239-3338, and a real person answers during the business day. Or book a free IT consultation: 30 minutes, a quote, and a one-page list of what is fine and what needs fixing, email authentication included.