SPF PermError
SPF evaluation fails permanently due to policy or lookup errors.
Problem summary
SPF evaluation fails permanently due to policy or lookup errors.
Symptoms
- Authentication-Results shows spf=permerror
- Validators report permanent evaluation failure
- DMARC cannot use SPF for that message path
Possible causes
- Multiple SPF records
- More than ten DNS-terminating lookups
- Invalid syntax or void includes that fail closed
How to diagnose
- Count v=spf1 TXT records at the evaluated name
- Expand include/a/mx/redirect chains and count lookups
- Validate mechanism syntax with an SPF checker
How to fix
- Collapse to one valid SPF record under the ten-lookup limit
- Replace deep include trees with flatter IP/CIDR authorization where appropriate
- Fix or remove broken include targets
How to verify
- spf=permerror disappears on controlled tests
- Checker reports a clean pass/fail evaluation path
Prevention
- Re-validate SPF after every new ESP include
- Prefer subdomain sending for overflow senders
When to escalate
- Production mail is failing for a material share of recipients after remediation attempts