The domain the message was sent from — the envelope sender in smtp.mailfrom — has no SPF record, so the receiver cannot tell which servers may send for it. Often it is a subdomain or a sending service’s bounce domain rather than your main domain, because subdomains do not inherit the parent’s record.
spf=none (google.com: bounce@example.com does not designate permitted sender hosts) smtp.mailfrom=bounce@example.com
How other mail servers write it
Microsoft 365 and Outlook.com
spf=none (sender IP is 192.0.2.1) smtp.mailfrom=example.com
Microsoft’s Received-SPF
Received-SPF: None (protection.outlook.com: example.com does not designate permitted sender hosts)
Yahoo and AOL
spf=none smtp.mailfrom=example.com
| Result | spf=none |
| Usually fixed by | The sending domain’s owner |
| Checks | The domain in smtp.mailfrom — or, for a bounce, the server’s HELO name |
| Required by | Gmail and Yahoo: SPF or DKIM for every sender, both for bulk senders |
Check the sender’s SPF record
Enter the domain from smtp.mailfrom (the envelope sender): we read its SPF record, follow every include and count the lookups.
What it means
SPF is looked up for the envelope sender’s exact domain; a record on example.com does not cover mail.example.com. For a bounce, which has no envelope sender, SPF checks the sending server’s HELO name instead.
Since 2024 Gmail and Yahoo require every sender to pass SPF or DKIM, and bulk senders both; a message with no SPF and no DKIM will not get through.
Why it happens
- The domain has no SPF record.
- The envelope sender is a subdomain — a bounce or return-path domain set up at a sending service — with no record of its own.
- The server’s HELO name has no record (for bounces).
How to fix it
- Publish an SPF record on the exact domain shown in smtp.mailfrom.
- For a return-path subdomain set up at a sending service, add the record the service gives you.
- For a domain that sends no mail at all, publish v=spf1 -all.
See it for yourself
dig TXT bounce.example.com +short
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 7208 — rfc-editor.org
- How email authentication works in Microsoft 365 — learn.microsoft.com
- Email sender guidelines — support.google.com
- Sender Best Practices — senders.yahooinc.com