Source: dmarcian Author: John Bowers URL: https://dmarcian.com/spf-record-cleanup-techniques/
-
ONE SENTENCE SUMMARY: dmarcian provides guidance on avoiding SPF over-authentication by safely removing unnecessary or incorrectly placed SPF include statements from organizational domains.
-
MAIN POINTS:
-
Over-authentication occurs when unnecessary email sources remain in SPF records.
-
SPF statements should be regularly reviewed to remove unused email sending sources.
-
Subdomain usage is a best practice for proper SPF alignment and reducing lookup counts.
-
Active Campaign requires subdomains; remove “include:emsd1.com” from organizational SPF.
-
Adobe Marketo needs a subdomain and trusted IP; remove “include:mktomail.com”.
-
AmazonSES requires subdomains; remove “include:amazonses.com” from organizational SPF.
-
Bird (SparkPost) mandates subdomains; remove “_spf.sparkpostmail.com” or “_spf.eu.sparkpostmail.com”.
-
Cvent cannot achieve SPF alignment; rely on DKIM instead and remove “include:cvent-planner.com”.
-
Salesforce Marketing Cloud needs Sender Authentication Package; remove “include:cust-spf.exacttarget.com”.
-
SendGrid usually requires subdomains; remove “include:sendgrid.net” from organizational SPF.
-
TAKEAWAYS:
-
Regularly audit SPF records to maintain accuracy and avoid over-authentication.
-
Use subdomains consistently for SPF alignment to improve email deliverability.
-
Remove outdated or unnecessary SPF include statements from organizational domains.
-
Confirm no aligned email volume before removing SPF includes using SPF Surveyor.
-
Rely on DKIM when SPF alignment is not achievable (e.g., Cvent).