Technical note · Email deliverability
Why authenticated business email can still reach spam
SPF, DKIM and DMARC provide evidence about the use of a domain. Inbox placement also depends on the receiving system’s assessment of the message and the context in which it was sent.
An invoice reaches the customer’s Junk Email folder. A reply to an established contact is accepted without a bounce but never noticed. A business application sends successfully, while its notifications are filtered at one recipient organization.
Authentication may be configured correctly in each situation. That is a useful finding, but the investigation still needs to explain what happened after the receiving system accepted the message. Repeating DNS changes without identifying the filtering decision can add risk while leaving the original problem unresolved.
Establish what “authenticated” means
A published record and a successful message check are different pieces of evidence. The investigation should inspect a representative message as received, identify the domains that were evaluated and establish which results the receiving system recorded.
SPF checks authorization for the domain used in the SMTP envelope sender. DKIM validates a signature associated with a signing domain. DMARC relates authenticated identities to the domain in the visible From address. A message can pass SPF and DKIM for a service provider’s domain while failing DMARC alignment with the organization’s From domain. Where DMARC applies, an aligned authentication pass through either mechanism can establish a DMARC pass. RFC 9989, §§4.3–4.4
Even a DMARC pass does not certify the message’s content or determine its delivery treatment. The DMARC standard leaves final handling to the receiver, which can apply its own policies to authenticated mail. Authentication therefore remains important when a message reaches spam; its successful result narrows the inquiry. RFC 9989, §5.4
Separate acceptance from inbox placement
First establish the observed outcome: rejection, temporary deferral, quarantine, delivery to Junk Email, or delivery followed by a mailbox action. These outcomes call for different evidence and potentially different corrections.
In Exchange Online, a message-trace status of Delivered does not by itself establish that the message reached the Inbox. Microsoft documents that spam-filtered messages sent to Junk Email or quarantine can appear as Delivered; the event details are needed to understand the action. A successful sending application test is similarly limited: it demonstrates the part of the path that was actually observed. Microsoft: Message Trace FAQ
An investigation should record the recipient’s actual observation alongside the sender’s logs. “The platform sent it” and “the recipient found it in Junk” can both be accurate. The task is to connect those observations through the message’s path.
Understand the receiver’s decision
Authentication is one part of a larger assessment. Microsoft identifies sender reputation, message characteristics, bulk-mail classification and user or organization overrides among the reasons legitimate messages may be filtered. A recipient’s blocked-sender setting or a tenant mail-flow rule can affect treatment even when the sender’s domain configuration is sound. Microsoft: Anti-spam protection FAQ
Content deserves examination without reducing diagnosis to a list of supposedly forbidden words. Links, formatting, attachments and message structure should be considered in the context of the recipient’s recorded verdict and applicable controls. A hypothesis about content becomes more useful when a controlled comparison supports it; an isolated change followed by one successful delivery is weak evidence of causation.
Reputation and sending behavior also need context. Gmail’s guidance for personal accounts recommends consistent sending, attention to recipient feedback and gradual changes in volume. It also addresses subscription and unsubscribe practices. Technical authorization cannot establish that recipients expect or want a particular mail stream. Google: Email sender guidelines
“Engagement” should be used carefully in this discussion. Google explicitly says it does not track open rates and cannot verify third-party open-rate figures. A low reported open rate is therefore insufficient evidence of a Gmail filtering problem. Recipient complaints, observed placement and provider diagnostics answer different questions and should be evaluated separately. Google: Email sender guidelines, Open rate
Follow evidence across representative messages
A useful starting set includes affected and unaffected recipients, the approximate time the problem began, the message type and the systems involved. Preserve complete received headers where available, together with rejection or deferral responses and relevant sending logs. Compare like with like: an application notification and an employee’s conversational reply may use different paths.
For Microsoft 365 recipients, received headers can expose authentication results and filtering information. Microsoft documents fields such as CAT, DIR, SFV and BCL. Those fields should be interpreted together with policy and trace details. Current cloud documentation specifically cautions that SCL alone does not determine the filtering verdict or action. Microsoft: Anti-spam message headers
Provider-level telemetry can broaden the picture. Google Postmaster Tools reports authentication, reputation, user-reported spam and delivery errors for mail to personal Gmail accounts. Its data is not real time, and privacy limits can suppress information at low sending volumes. A quiet or empty dashboard is consequently not proof that no filtering problem exists. Google also explains that a low user-reported spam rate can accompany substantial automatic spam placement because fewer messages reached recipients’ inboxes. Google: Postmaster Tools dashboards
These limitations matter particularly for low-volume business correspondence. Where aggregate data is incomplete, individual message evidence and the recipient administrator’s findings may carry more diagnostic value than a dashboard percentage.
Avoid corrections that obscure the problem
Several tempting responses make the investigation harder:
- Treating every failure as a DNS problem. A further SPF entry or policy change should address an identified authentication issue, rather than serve as a general response to Junk Email placement.
- Changing several variables together. Simultaneously changing the domain, sending platform, template and recipient list prevents a clean comparison. The investigation loses the ability to connect an observed improvement to a particular correction.
- Applying a broad filtering bypass. An allow entry or rule may alter one recipient organization’s treatment without correcting the sender’s wider configuration or behavior. Microsoft’s troubleshooting guidance distinguishes policy overrides from normal filtering and provides ways to trace which control acted. Microsoft: Troubleshoot anti-spam policies
- Calling one successful test a resolution. A test establishes what happened to that message at that recipient and time. Verification should reflect the affected message types and paths, while remaining explicit about what was not tested.
These are investigation disciplines, rather than a promise that every incident will yield a single cause. Several contributors can coexist, and a provider may not expose the full reasoning behind its decision.
Correct the supported finding, then verify the result
The corrective work should follow the evidence. An authentication problem calls for the appropriate record or platform change and representative message testing. A recipient-policy issue may require action by that organization’s administrator. A content or sending-practice concern requires a considered change to that mail stream, followed by observation of the relevant outcomes.
For apparent Microsoft 365 false positives, the recipient’s administrator can use Microsoft’s submission process where the required product access and permissions are available. That escalation should include the evidence needed to identify the message and its treatment; it is not a guarantee that the provider will change its classification. Microsoft: Resolve email false positives
The useful outcome is a documented account of what was established, what remains uncertain, which changes were authorized and how they were checked. Boutique Ink can investigate the sending path, authentication, configuration and available filtering evidence, then recommend or implement an agreed correction. Inbox placement remains a receiving-system decision; no investigation can honestly promise a universal outcome or a fixed recovery interval.
Primary sources
- RFC 9989 — Domain-Based Message Authentication, Reporting, and Conformance, May 2026. Current DMARC specification; supersedes RFCs 7489 and 9091. Relevant §§4.3–4.4 and 5.4.
- Google — Email sender guidelines. Sending practices, recipient feedback and limitations of open-rate interpretation.
- Google — Postmaster Tools dashboards. Available telemetry, reporting limitations and interpretation of user-reported spam.
- Microsoft — Message Trace FAQ in Exchange Online. Delivered status and inspection of event details.
- Microsoft — Anti-spam protection FAQ. Reputation, content, bulk classification and policy factors.
- Microsoft — Anti-spam message headers. Authentication and filtering fields; limits of SCL interpretation in cloud organizations.
- Microsoft — Troubleshoot anti-spam policies. Policy precedence, overrides and interpretation of filtering evidence.
- Microsoft — Resolve email false positives. Provider submission and review process.
All links were checked during research on November 10, 2026. Product controls and documentation can change; the citations do not imply access to any client’s tenant or provider-internal filtering model.
Investigate a delivery problem.
A short description of the domain, the objective and the platforms involved is enough to begin.
Discuss a delivery problemFull message headers and DMARC aggregate reports are welcome. Please omit credentials, message bodies and their attachments, and DMARC forensic/failure reports. Full inquiry guidance
Explore Email Deliverability Troubleshooting