SPF names a record receivers can't follow
Your SPF record has an include: or redirect= that receivers can't follow: the name it points to has no SPF record, has more than one, or leads back to a record already on the way. Receivers stop there with an error (permerror), so SPF fails for mail from every service listed after that term. Mail from a service listed before it still passes. A broken redirect= is read last, so every message that matched no earlier term fails.
On the result:
SPF names a record receivers can't follow
An include or redirect names a record that is missing, has more than one SPF record, or points back to itself, so SPF fails for mail from a service listed after it.
RFC 7208 section 5.2 says what an include does when the name has no SPF record: a result of none makes the include "return permerror". Section 6.1 says the same for redirect=: "if no SPF record is found … the result is a "permerror" rather than "none"". Section 4.5 covers two records: "If the resultant record set includes more than one record, check_host() produces the "permerror" result."
The usual causes:
- A service you left. It removed the SPF record its include named, or its domain expired.
- A typing mistake, such as
include:_spf.gogle.com. - A name with two SPF records, often your own subdomain after a second service asked you to add one.
- A loop: a record that includes itself, directly or through another record. This happens most often with
redirect=between your own domains.
Find the term
See the lookups → under the finding opens the SPF checker. It lists each term in the order receivers read it and marks the one that fails: "has no SPF record", "finds nothing", "has more than one SPF record" or "includes itself". Details → on the result shows your record.
To look it up yourself, put the name from the include in place of _spf.example-service.com:
dig +short TXT _spf.example-service.com
On Windows, use nslookup -type=TXT _spf.example-service.com. No line containing v=spf1 means no SPF record; two such lines mean two records.
Fix it
- A service you no longer use: remove its
include:orredirect=from your record. - A service you still use: copy the current include from its setup page or support, and replace the old one. Services do rename them.
- A
redirect=to a name of your own with no SPF record: publish the record there, or point theredirect=at the right name. - A name of your own with two SPF records: merge them into one, as More than one SPF record explains.
- A loop: point the
redirect=orinclude:at a record that doesn't lead back to the one it is in. - Run the check again.
Last updated .