Topic · Authentication
SPF null reverse path
An SMTP transaction can use a null MAIL FROM value, commonly for delivery-status notifications and bounce handling.
How it works
SPF can evaluate the EHLO identity in null-reverse-path cases using the identity construction defined by its specification.
What can go wrong
A tool that assumes every message has a nonempty bounce address can misreport authentication failures.
What to check or do
Inspect the SMTP envelope and HELO hostname before interpreting SPF results for bounce messages.
How to investigate SPF null reverse path
- Signal to investigate
- A bounce message has MAIL FROM:<> and SPF results appear tied to HELO rather than a bounce address.
- Evidence to collect
- Capture the SMTP session or trusted receiver log and compare HELO-domain SPF evaluation to the null envelope reverse-path.
- Common wrong conclusion
- A blank MAIL FROM in a delivery-status notification is normal and does not mean that SPF was skipped.
How to interpret the evidence
RFC 7208 specifies how SPF identity selection works for null reverse paths. Receivers may evaluate HELO identity, while DMARC alignment decisions still depend on their applicable rules.
What to change and how to verify it
Publish a correct HELO hostname and assess DSN handling separately from normal promotional-mail bounce domains.
Put this into practice
Run a focused check, then explore protection if your domain needs it.