Folderly Flash Send-readiness test

Fix a passing but unaligned SPF result

SPF alignment passes only when the domain authenticated by SPF aligns with the visible From domain under the published DMARC mode. Flash compares trusted receiver evidence for the RFC5321.MailFrom domain with the From domain: relaxed alignment accepts the same organizational domain, while strict alignment requires an exact domain match. An ESP can therefore produce an SPF pass for its own bounce domain without producing aligned SPF for your brand; aligned DKIM can still satisfy DMARC.

Why mailbox providers enforce this

A bare SPF pass authorizes a sending server for the envelope identity used in that check; it does not by itself validate the brand domain a recipient sees in From. Gmail and Yahoo require direct bulk mail to align that visible identity with either the SPF domain or the DKIM domain. DMARC needs only one passing, aligned mechanism, so an SPF alignment failure is not automatically a DMARC verdict failure when aligned DKIM passes. Flash reports SPF verdict, SPF DNS quality, SPF alignment, DKIM alignment and DMARC separately so the operator can fix the failed identity without treating authentication evidence as inbox-placement proof.

Primary sources for this guidance

How to fix it

  1. Use one representative message received through the production path. Record the visible From domain, Return-Path, Authentication-Results spf result and smtp.mailfrom domain, DKIM signing domain and DMARC result; DNS alone cannot show the identity a receiver evaluated.
  2. Read the exact Flash subchecks together. Fix an SPF verdict or SPF DNS failure before alignment; keep an unknown alignment result unknown when trusted receiver headers do not expose enough envelope-domain evidence.
  3. Query the DMARC record that applies to the visible From domain and read aspf. The default and r value use relaxed alignment; s uses strict alignment. Do not assume a strict policy from a provider dashboard label.
  4. Compare the authenticated RFC5321.MailFrom domain with the visible From domain. Relaxed alignment requires the same organizational domain, including public-suffix boundaries such as example.co.uk; strict alignment requires the domains to be identical.
  5. When the ESP supports it, configure a custom MAIL FROM or bounce domain under the From domain's organizational domain. Publish the provider-required DNS and authorize its real sending path with one valid SPF record.
  6. Assign the change to the system that controls the envelope sender. Changing only the visible From address or adding the ESP to an unrelated SPF record does not align the RFC5321.MailFrom identity observed by the receiver.
  7. If the provider cannot supply aligned SPF, make aligned DKIM deliberate and monitor DMARC aggregate reports. DMARC can pass through aligned DKIM, but document that SPF remains unaligned instead of calling both mechanisms fixed.
  8. After DNS and ESP configuration are observable, send the same authorized template through the same production path. Compare the SPF verdict, authenticated domain, alignment mode, DKIM alignment and DMARC verdict, and check for regressions; keep inbox placement as a separate provider observation.

Limitations

One received message can verify only the identities and verdicts exposed for that path. It cannot inventory every authorized sender, predict forwarding or other indirect mail behavior, prove that every receiver applies the same local policy, or guarantee inbox placement.

Next action Capture the visible From and authenticated RFC5321.MailFrom domains from one representative production message, apply the published aspf mode, assign the custom MAIL FROM or aligned DKIM change to its owner, then run one comparable Flash retest after the configuration is observable.
Run a free test →

FAQ

Does SPF alignment require the exact same domain?
Only in strict mode. Relaxed alignment accepts different subdomains when the authenticated SPF domain and visible From domain share the same organizational domain. The DMARC aspf tag selects the mode and defaults to relaxed when absent.
Can DMARC pass if SPF alignment fails?
Yes. DMARC passes when either SPF or DKIM passes and aligns. If aligned DKIM carries the message, record SPF as unaligned rather than changing the DMARC verdict or hiding the remaining ESP configuration gap.
Does aligned SPF guarantee inbox placement?
No. Alignment validates authorized use of the From identity for that received message. Reputation, complaints, content, blocklists and provider-specific evidence still affect handling, and Flash reports placement only when its configured provider quorum is available.

Related

Content record Owner: Folderly Flash content operations Reviewed: 2026-11-03 Maintenance trigger: Review when Flash changes its SPF-domain or organizational-domain evaluation, when RFC 9989 or sender requirements change, or when an ESP changes its custom MAIL FROM behavior.
Want a deliverability engineer to fix this for you? Hand it to Folderly →