DMARC passes, but mail still goes to spam

On every plan

Passing DMARC tells a mailbox provider that the mail really comes from your domain. It does not tell the provider that your recipients want it. Where a passing message lands depends on other things the provider weighs, such as how often recipients mark your mail as spam and whether they can unsubscribe easily.

Check that the mail in spam passes

"DMARC passes" can be true of one service and not of another. Find the service that sent the message that landed in spam, and look for it on the domain's Sources page. If that source fails, fix it. Mail that a recipient forwards to another mailbox can fail too, even when your own sending passes. See forwarded and mailing-list mail.

What mailbox providers ask for beyond DMARC

Google asks senders to keep the spam rate below 0.1 percent, and never to let it reach 0.3 percent. Yahoo asks every sender to keep it below 0.3 percent. Google Postmaster Tools shows the rate Gmail measures for your domain. Bulk senders also need one-click unsubscribe in marketing mail. The guide What Google, Yahoo and Microsoft ask of senders lists each provider's rules, quoted from its own pages.

What the reports can show

An aggregate report counts the mail from each sending server, and whether it passed SPF, DKIM and DMARC. It also says what the mailbox provider did under your DMARC policy: delivered, sent to spam or refused. For mail that passes, the policy asks for nothing, so the report shows it as delivered.

The report does not say whether a passing message then went to the inbox or to the spam folder. It holds no spam complaints and no message content. So Mailmoni shows you which services pass and which do not, but not where a passing message landed.

Learn has a guide to mail that goes to spam although SPF, DKIM and DMARC pass. It goes through the other causes in detail.

Published 27 October 2026 · Checked 27 October 2026