Understanding SPF authentication results: mfrom vs. helo
SPF doesn’t check one thing. It checks two. Every SPF result is tied to a scope: either mfrom or helo. Knowing which identity was evaluated is the key to reading SPF results in your DMARC reports.
SPF checks two identities
During the SMTP conversation, a sending server announces two separate identities before the message body is ever transmitted. SPF (RFC 7208) can authorise the sending IP against either one:
scope=mfromthe MAIL FROM / envelope sender (Return-Path)The domain in the SMTP MAIL FROM:<…> command: the bounce address, also called the envelope-from or Return-Path. This is the identity SPF was primarily designed to validate, and the one DMARC uses.
scope=helothe HELO / EHLO hostnameThe hostname the server gives in its EHLO mail.example.com greeting. SPF checks this as a fallback, and it’s the only identity available when the envelope sender is empty, as it is for bounce messages (MAIL FROM:<>).
Why the empty envelope matters
When a server sends a bounce or delivery-status notification, the envelope sender is deliberately empty to prevent mail loops. With no MAIL FROM domain to check, SPF has nothing to evaluate at mfrom scope, so RFC 7208 falls back to the HELO identity. That’s why scope=helo results show up in reports even though most normal mail is judged on mfrom.
Where you’ll see scope
DMARC aggregate reports (RUA) carry a structured SPF result for each source. Historically, the report schema in RFC 7489 defined a <scope> element whose valid values were mfrom and helo:
<record> <row> <source_ip>198.51.100.20</source_ip> <policy_evaluated> <spf>pass</spf> </policy_evaluated> </row> <auth_results> <spf> <domain>xmpl.example</domain> <scope>mfrom</scope> <result>pass</result> </spf> </auth_results> </record>
The same distinction appears in the live message’s Authentication-Results header (RFC 8601), where the identity is named with a property instead: smtp.mailfrom for the envelope sender and smtp.helo for the HELO name:
Authentication-Results: mx.example.net; spf=pass smtp.mailfrom=bounce@xmpl.example; spf=pass smtp.helo=mail.xmpl.example
Updated in DMARCbisRFC 9990 · May 2026Since RFC 9990, the only valid scope is mfrom
RFC 9990 (the DMARCbis aggregate-reporting standard that replaces RFC 7489) makes this explicit: “Only the ‘MAIL FROM’ identity (see Section 2.4 of RFC 7208) is used in DMARC. The only valid value for the ‘scope’ element is ‘mfrom’.” In other words, DMARC authentication is now defined to rest on the mfrom identity alone, and conforming reports no longer carry a helo-scope SPF result.
The helo identity hasn’t disappeared. SPF still evaluates it per RFC 7208, and it still appears as smtp.helo in the live Authentication-Results header. It simply isn’t reported as a DMARC scope anymore, because it never contributed to the DMARC verdict in the first place. Older reports following the RFC 7489 schema may still include it.
Which scope counts for DMARC
DMARC only uses the mfrom scope. For SPF to contribute to a DMARC pass, the MAIL FROM domain must both pass SPF and align with the From-header domain. A helo-scope pass does not satisfy DMARC on its own. It’s primarily there to authenticate bounces and to give receivers a signal when the envelope is empty.
| Scope | Identity checked | Used by DMARC? |
|---|---|---|
| mfrom | Envelope sender / Return-Path | Yes |
| helo | EHLO/HELO hostname | No (dropped from reports in RFC 9990) |
How ClearSPF surfaces it
When ClearDMARC parses your aggregate reports, each SPF result is labelled with its scope, so you can tell at a glance whether a source passed on the envelope sender or only on its HELO name. A source passing helo but failing mfrom alignment is a common reason a stream looks "mostly passing" yet still fails DMARC. It’s exactly the case worth investigating.
- RFC 7208: Sender Policy Framework (SPF), §2.3 (HELO identity) and §2.4 (MAIL FROM identity).
- RFC 7489: DMARC (Informational, 2015). Appendix C: original aggregate-report schema (
SPFDomainScope=helo|mfrom). - RFC 9990: DMARC Aggregate Reporting (DMARCbis, May 2026). Table 13 “Contents of the spf Element”: the only valid
scopeismfrom. rfc-editor.org/rfc/rfc9990 - RFC 8601: Authentication-Results header field (
smtp.mailfromandsmtp.heloproperties).