Skip to content
  • There are no suggestions because the search field is empty.

Why are my emails going to spam

Your emails are going to spam because the receiving provider's filter decided, from many signals, that they looked unwanted or untrustworthy. Missing or misaligned SPF, DKIM, or DMARC is one common and checkable reason. It's not the only one. Mail that passes all three can still land in spam because of complaint rates, sender reputation, list quality, content, or the recipient's own rules. The job is to work out which kind of problem you have before you change anything.

Authentication is one input, not the verdict

Authentication is one input to more complex filtering decisions, not the verdict. A DMARC pass does not guarantee that delivery to the recipient's inbox would be safe or desirable, and receivers may reject or quarantine mail even when it passes. Authenticated messages are less likely to be rejected or marked as spam, and a DMARC failure is one of several factors in whether mail is rejected, sent to spam, or delivered. A composite authentication failure doesn't directly result in a message being blocked, because other signals are weighed too.

So when emails go to spam instead of the inbox, authentication is the first thing to rule in or out, not the whole answer. If SPF, DKIM, and DMARC are new to you, start with What is email authentication?.

Why do my business emails go to spam?

Company emails going to spam usually trace back to one of two groups of causes.

Authentication causes (you can check these)

  • Neither SPF nor DKIM passes for the message.
  • They pass, but not for your domain. A marketing platform sends with its own bounce domain and signs DKIM with its own domain. SPF and DKIM both pass, nothing aligns with your From domain, so DMARC fails. This is the classic third-party sender problem, explained in Envelope From vs Header From.
  • No DMARC record while sending in bulk. Each provider handles this differently. At Gmail, mail from a domain with no DMARC policy might be rejected or sent to spam, and bulk senders without one lose delivery support and mitigations. Yahoo requires bulk senders to publish DMARC and pass it. For high-volume senders to consumer Outlook.com, non-compliant mail may be rejected with 550 5.7.515, or still go to the junk folder; plan for either (Google, Yahoo, and Microsoft sender requirements).
  • Broken records: SPF permerror from too many DNS lookups, two SPF records on one domain, a missing DKIM key or selector mismatch.
  • Forwarding and mailing lists. Forwarding often breaks SPF, and list software that edits messages breaks DKIM. Google doesn't require alignment for forwarded or mailing-list mail. ARC exists for this as an experimental method, but it hasn't become widely used.

Causes that have nothing to do with authentication

  • Complaint rate. Keep your spam rate below 0.3% at both Gmail and Yahoo. At Gmail, aim below 0.1%. The effect on delivery is graduated, and rates of 0.3% or higher hurt more. Gmail Postmaster Tools is where you see that spam rate.
  • Domain and IP reputation, including the reputation of shared IPs at your email service provider.
  • List quality and engagement. Sending to people who didn't opt in, or not removing bounces, drags everything down.
  • No working one-click unsubscribe on marketing mail. The consequence is losing delivery support and mitigations, and easy, prompt unsubscribes are tied to fewer spam reports.
  • Content and formatting: misleading display names or headers, hidden content, fake "Re:" or "Fwd:" subjects, malformed messages.
  • Infrastructure: missing or mismatched reverse DNS (PTR), or no TLS.
  • Blocklists.
  • The recipient's side: personal filters, admin quarantine, or tenant policies you can't see or change.

Providers don't publish how they weight these, so don't assume one cause outranks another.

How to narrow it down

If you're looking for how to fix emails going to spam, start by finding out which group you're in. Changing DNS in a hurry can make things worse.

  1. Bounced or silently filtered? A bounce comes with a code and tells you far more than a spam-folder placement does. Collect it before you change anything.

  2. Read the Authentication-Results header on a copy that was delivered (to spam or anywhere else). Receivers should add it. You're looking for something like this:

    Authentication-Results: mx.receiver.example;
      spf=pass smtp.mailfrom=bounce.mailvendor.example;
      dkim=pass header.d=mailvendor.example;
      dmarc=fail header.from=example.com
    

    Both checks passed, but for mailvendor.example, not example.com. That's an alignment problem, not a reputation problem.

  3. If SPF or DKIM passes and aligns, and DMARC passes, look at complaints, reputation, list practices, and content next. Those are the usual next suspects.

  4. Use DMARC aggregate reports to see every source sending as your domain and whether each one passes and aligns. A new tool someone switched on last month shows up there. Who usually owns SPF, DKIM, and DMARC covers who usually reads them.

One caution on step 4: DMARC reports don't tell you whether mail landed in the inbox or in spam. They tell you about authentication. For Gmail, Postmaster Tools shows your spam rate and compliance status.

A common real-world case: Google Workspace emails going to spam after a new CRM or helpdesk starts sending as your domain without its own DKIM.

Mistakes that make it worse

  • Jumping to p=reject to "fix spam." A DMARC policy controls what receivers are asked to do with mail that fails DMARC. It doesn't touch filtering of mail that passes, and it can get your own unaligned mail blocked. What is DMARC explains the policies; The right order: SPF, DKIM, DMARC, then BIMI explains when enforcement makes sense.
  • Trusting the platform's "domain authenticated" badge. It may mean only DKIM is set up, or only a CNAME is published. Check that DMARC actually passes with alignment.
  • Testing with one personal mailbox and assuming every provider behaves the same.
  • Ignoring complaint rate because "authentication passes."
  • Expecting BIMI to help. BIMI does not change message delivery. It comes after enforcement and only affects logo display.

Where BIMI Certifications fits

Our DMARC reporting and visual analysis shows which sources send as your domain and whether SPF, DKIM, and alignment pass for each. That lets you rule authentication in or out quickly. It doesn't change a provider's filter, a mailbox rule, or your reputation, and no tool can promise to.

Free DMARC account

Turn raw DMARC reports into a readable dashboard

Point your rua address to our platform and read the results by sender and source instead of opening XML files.

  • Results grouped by sending source
  • SPF, DKIM and alignment results per sender
  • The original XML reports are still there to download

Create a free DMARC accountTalk to an expert

FAQ

Why are my emails going to spam all of a sudden?

Look for what changed. A new vendor sending as your domain, a DNS edit that broke SPF or removed a DKIM key, a list import that pushed complaints up, or a reputation drop. Check the Authentication-Results header first, then your complaint rate.

My SPF, DKIM, and DMARC all pass. Why is mail still in spam?

Authentication says the mail is from you. It doesn't make it wanted. Check complaints, reputation, list practices, and content.

Will moving to p=reject get me out of spam?

No. The policy only covers mail that fails DMARC.

Is going to spam the same as bouncing?

No. A bounce is a rejection with a code, such as 550 5.7.26 at Gmail or 550 5.7.515 at Outlook.com. Spam-foldering is a filtering decision and comes with no code.

Can a DMARC tool fix this?

It can show whether authentication is the problem and which sources fail. It can't change a provider's filter.