The receiving server looked up the SPF record of the envelope sender’s domain — the Return-Path, not the From address — and found that the IP address the message came from is explicitly not allowed to send for it. Usually a service that sends for you is missing from the record, or the message was forwarded.
spf=fail (google.com: domain of notifier@example.com does not designate 192.0.2.1 as permitted sender) smtp.mailfrom=notifier@example.com
How other mail servers write it
Microsoft 365 and Outlook.com
spf=fail (sender IP is 192.0.2.1) smtp.mailfrom=example.com
Microsoft’s Received-SPF
Received-SPF: Fail (protection.outlook.com: domain of example.com does not designate 192.0.2.1 as permitted sender)
Yahoo and AOL
spf=fail smtp.mailfrom=example.com
Older Gmail headers
spf=hardfail (google.com: domain of notifier@example.com does not designate 192.0.2.1 as permitted sender)
| Result | spf=fail |
| Usually fixed by | The sender, or whoever forwarded it |
| Published as | -all at the end of the SPF record |
| Checks | The envelope sender (Return-Path), not the From address |
| Standard | RFC 7208 §2.6.4 |
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 answers one question: may this IP address send mail for the envelope sender’s domain? A fail is the record saying no, firmly. What the receiver does next is its own choice — RFC 7208 lets it reject the message or accept and mark it — and under DMARC a fail matters less when DKIM passes for the From domain.
Why it happens
- A service that sends as your domain — a newsletter tool, a CRM, a new mail provider — is missing from the record.
- The message was forwarded: SPF checks the last server it came from, which is the forwarder’s, not yours.
- Someone is sending as your domain without permission — the result doing its job.
- Your provider or server started sending from new IP addresses.
How to fix it
- Find the IP address in the result, and which service it belongs to.
- Add that service’s include:, ip4: or ip6: to your one SPF record, staying within ten lookups.
- For forwarded mail, rely on DKIM, which survives forwarding when nothing is changed — you cannot list every forwarder.
- Check the record with the tool above.
See it for yourself
dig TXT example.com +short
Look up the domain in smtp.mailfrom — often a subdomain or a sending service’s own domain, not the one in From.
Questions
SPF failed but the message was delivered. Why?
SPF is one signal among several. If DKIM passed for the From domain, DMARC passes and most receivers deliver the message. Forwarded mail fails SPF routinely.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 7208 — rfc-editor.org
- Anti-spam message headers — learn.microsoft.com
- How email authentication works in Microsoft 365 — learn.microsoft.com
- Troubleshoot SPF issues — knowledge.workspace.google.com