SPF PermError: what it means and every common cause

A permanent error means receivers could not evaluate your SPF record at all. The causes, from syntax errors to include loops.

permerror (permanent error) means the receiver could not evaluate your SPF record at all. Unlike fail, it isn't about one server: it applies to every message. DMARC treats it as an SPF failure, so all your mail then depends on DKIM alone.

The causes, most common first

  • More than 10 DNS lookups. See too many DNS lookups.
  • More than one SPF record on the domain. See multiple SPF records.
  • More than two void lookups: includes that point to names that don't exist. See void lookups.
  • Syntax errors. Typical ones:
    • include: spf.example.net: a space after the colon.
    • ip4:203.0.113.0/33: an impossible network size.
    • v=spf1 missing, misspelled (v=spf) or not at the start.
    • Smart quotes (“ ”) pasted from a document instead of straight quotes.
    • Unknown words like include= instead of include:.
  • A broken included record. If a provider's SPF record has an error, or an include points to a record that includes itself (a loop), your record inherits the permerror.
  • An included domain publishes two SPF records. Also a permerror, even though it's someone else's domain.

How to fix it

  1. Look up your record: dig TXT example.com +short, and check there is exactly one line starting with v=spf1.
  2. Run it through a checker that expands includes; it will point at the part that fails.
  3. If the error is in a provider's record, remove that include until they fix it, or contact them.