Incorrect IP authorization
Sending infrastructure IPs are not authorized by SPF.
Problem summary
Sending infrastructure IPs are not authorized by SPF.
Symptoms
- spf=fail or softfail from your own ESP/MTA IPs
- DMARC reports show legitimate sources failing SPF
- New sending IP ranges were never added
Possible causes
- Missing ip4/ip6 or include for the active egress
- Shared pool IP change not covered by include
- MAIL FROM domain differs from the domain you edited
How to diagnose
- Capture the connecting IP from SMTP logs or Authentication-Results
- Evaluate SPF for that IP against the MAIL FROM domain
- Confirm which domain’s SPF the ESP actually uses (Return-Path)
How to fix
- Add the correct include or CIDR for the sending infrastructure
- Align Return-Path/MAIL FROM with the domain you intend to authorize
- Retire obsolete IPs from the record after cutover
How to verify
- Same egress IP now yields spf=pass
- DMARC rows for that source flip to SPF pass
Prevention
- Update SPF as part of IP/pool change tickets
- Inventory Return-Path domains per stream
When to escalate
- Production mail is failing for a material share of recipients after remediation attempts