Authentication vs inbox placement
Passing SPF, DKIM, and DMARC gets your mail through the door and ties it to your domain. It doesn't decide which folder it lands in. The DMARC standard says so directly: a pass "indicates only that the use of the Author Domain has been validated," it "does not carry an explicit or implicit value assertion about that message or the Domain Owner," and receivers "MAY choose to reject or quarantine a message even if it passes". Inbox placement is decided after that, by complaints, reputation, list quality, and each receiver's own filters.
So when a team says "we fixed DMARC and we're still in spam," nothing is necessarily broken. They've cleared the first gate, and the rest of the gates are about whether people want the mail. If you're working through a specific spam-folder problem, start with Why are my emails going to spam. This article explains the layers behind it.
Three questions every receiver asks
It helps to think of inbox placement as three separate questions. Providers don't publish their filtering formulas, so treat this as a working model, not a spec.
- Will we accept it? Authentication, the provider's sender requirements, and basic infrastructure such as valid reverse DNS and TLS.
- Do we trust this sender? Reputation and complaint history for the sending IPs and domains.
- Do our users want it? Engagement, content, and how the list was built.
Authentication mostly answers question 1, and it feeds question 2 by giving the receiver a verified domain to attach a reputation to (see IP and domain reputation). It can't answer question 3.
Where authentication does affect delivery
For bulk senders, the big providers have made authentication a hard floor. Missing it can get mail deferred, rejected, or filtered, which is why it feels like a deliverability lever.
- Gmail. For bulk senders, misaligned From headers, missing SPF or DKIM, missing reverse DNS, no TLS, and malformed messages can all lead to temporary or permanent failure codes, or land in spam. Since November 2025, Gmail has been ramping up enforcement, including temporary and permanent rejections. Unauthenticated mail might be marked as spam or rejected with a 5.7.26 error.
- Yahoo. Bulk senders need SPF and DKIM, and "DMARC must pass".
- Outlook.com. High-volume senders that don't meet Microsoft's bar can get
550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level. Microsoft's pages disagree on whether that mail is rejected or junked; Microsoft and Outlook authentication rules covers both. - Microsoft 365 business mailboxes. Inbound mail gets a composite authentication result (
compauth), but a composite authentication failure doesn't directly result in a message being blocked. It weighs other signals too.
The full requirement lists are on Google, Yahoo, and Microsoft sender requirements, with the detail in Google and Yahoo sender requirements and Microsoft and Outlook authentication rules. Meeting them is a floor. Even when you follow them, some legitimate messages may be marked as spam.
What decides inbox placement once you're authenticated
Spam complaints. Providers put numbers on this one. Google tells bulk senders to keep the user-reported spam rate below 0.1% and never reach 0.3%. Its FAQ says the effect is "graduated," that "rates of 0.3% or higher have an even greater negative impact," and that rates above 0.1% already hurt inbox delivery. Yahoo uses 0.3% too, and calculates the rate "based on mail delivered to the inbox". For what the rate measures and how to lower it, see What is a spam complaint rate?.
Reputation. Yahoo lists IP, URL, domain, sender, and ASN reputation among its inputs, alongside DKIM and DMARC, and says it "usually do[es] not redirect mail to the Spam folder for poor reputation alone". Microsoft's SNDS page opens with "Deliverability to Outlook.com is based on your reputation". Google calls reputation "only one of many factors affecting deliverability". The details are in IP and domain reputation.
How you send. The practical rules are concrete: send only to people who signed up, don't buy lists, don't mix promotions into receipts, use separate IPs per message type if you use more than one, and keep the same From address for each category of mail. Yahoo also wants confirmed opt-in, removing invalid recipients, and matching the frequency people signed up for.
What recipients do. Marking a message as spam or not spam changes what happens to the next one. So does being in the recipient's contacts.
Why your DMARC reports can't show placement
A DMARC aggregate report tells you which sources sent mail as your domain, what SPF and DKIM said, and what the receiver did with failing mail. It doesn't tell you whether passing mail went to the inbox or the spam folder. That's deliberate. Disclosing message placement (inbox or spam) in reports is strongly discouraged. There's a field-by-field tour in A field-by-field walk-through of a DMARC aggregate report.
A high DMARC pass rate is an authentication number. It isn't an inbox rate. BIMI Certifications' DMARC reporting and visual analysis shows you which of your sources pass SPF, DKIM, and aligned DMARC. For placement signals, use the providers' own tools: Gmail Postmaster Tools for spam rate and compliance status, and Microsoft SNDS for IP-level data at Outlook.com.
Common mistakes
- Reading "compliant" as "inbox." A green compliance status in Postmaster Tools means you meet Google's requirements. It doesn't promise placement.
- Fixing authentication and ignoring the spam rate. A rate under 0.3% but over 0.1% is already costing you at Gmail.
- Sending marketing and transactional mail on one stream. Complaints about promotions can drag down password resets and receipts.
- Treating p=reject as a deliverability upgrade. No provider source says enforcement improves placement. It's an anti-spoofing request for mail that fails (see When you are ready for p=reject).
- Expecting a logo to fix it. BIMI is a display feature for mail that already passed (see Why BIMI is not a deliverability shortcut).
What to check next
If authentication passes and mail still lands in spam:
- Confirm the pass is aligned with your From domain, not just SPF passing for your ESP's domain (Identifier alignment for SPF and DKIM).
- Check your spam rate in Gmail Postmaster Tools, and Yahoo's Complaint Feedback Loop if you're enrolled.
- Look at how the list was built and when it was last cleaned.
- Separate message streams if marketing and transactional mail share a From address or IP.
- Read IP and domain reputation for what the provider tools can and can't show about reputation.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
Does DMARC improve deliverability?
Not on its own. Gmail and Yahoo require a DMARC record from bulk senders, and Outlook.com requires one from high-volume senders, so missing it can hurt. Once you meet the requirement, no provider says a stricter policy improves placement. What DMARC does is let receivers tie your mail to your domain and treat forgeries differently.
We pass DMARC. Why are we in spam?
Because a pass carries no judgment about whether the message is wanted. Check complaints, list quality, and reputation next. At Yahoo, a combination of poor reputation and high complaints can send mail to the spam folder.
Can DMARC reports show inbox placement?
No. Reporting placement is discouraged, and the standard report format has no field for it.