The receiver could not evaluate the SPF record at all: it is broken. The usual reasons are more than ten DNS lookups, two SPF records on the same name, a syntax error, or an include: pointing at a domain that no longer has SPF. Until it is fixed, SPF fails for every message.
spf=permerror (google.com: permanent error in processing during lookup of bounce@example.com: _spf.example.com not found)
How other mail servers write it
Microsoft 365 and Outlook.com
spf=permerror (sender IP is 192.0.2.1) smtp.mailfrom=example.com
Microsoft’s Received-SPF
Received-SPF: PermError (protection.outlook.com: domain of example.com used an invalid SPF mechanism)
rspamd
spf=permerror (mx.example.net: domain of example.com uses mechanism not recognized by this client)
| Result | spf=permerror |
| Usually fixed by | The sending domain’s owner |
| Lookup limit | 10 terms that query DNS (include, a, mx, ptr, exists, redirect) |
| Void lookups | At most 2 that return nothing |
| Records | Exactly one v=spf1 record per name |
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
A permanent error means the domain’s owner has to change something: the record cannot be read the way RFC 7208 defines it. Receivers that reject for it use 550 5.5.2; under DMARC, a permerror counts as SPF not passing.
Why it happens
- More than ten DNS-querying terms once every include: is followed — the most common cause, as services are added over the years.
- More than two lookups that return nothing (void lookups).
- Two SPF records on the same name — often one added by a new service beside the old one.
- A syntax error: a typo in a mechanism, a stray character, a missing space.
- An include: pointing at a domain that no longer publishes SPF.
How to fix it
- Run the check above: it counts the lookups and names the broken part.
- Merge two records into one.
- Remove includes for services you no longer use; replace others with their IP ranges where they publish them.
- Fix syntax errors, then check again.
See it for yourself
dig TXT example.com +short
Two lines starting v=spf1 is a permerror on its own.
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
- Troubleshoot email authentication in Microsoft 365 — learn.microsoft.com