A growing number of Email Service Providers (ESPs) are changing how you set up SPF (Sender Policy Framework) records, eliminating the need to add them as TXT DNS records. However, this doesn’t mean SPF is becoming obsolete; it’s still essential. The shift indicates that some ESPs are adopting a different approach to implement SPF. Here’s a clearer explanation.
Why SPF TXT Records Are Not Always Provided By ESPs
When using an ESP, the “Mail From” address (the one displayed in the “from” field of your email, such as email@yoursite.com) can differ from the “Return-Path” address (the address used for bounced messages and tracking reports, like bouncy_bounceface@tv.csfts.com).
If you examine the header code of any email you send, both addresses will be visible.
Email services, like Gmail, verify your SPF record against the Return-Path address, not the Mail-From address. They do this by looking up your DNS records to find and check the SPF record for correctness.
So, if the TXT DNS record isn’t verifying the Return-Path address, what was its purpose?
Originally, this TXT record verified your SenderID, which is linked to your “Mail From” address. However, SenderID is largely obsolete in today’s email strategies, especially with ESPs. Now, ensuring an SPF record is active for the Return-Path address suffices.
By no longer requiring a separate TXT DNS record for SPF, some ESPs simplify the verification process.
What’s the New Approach?
With the shift away from SPF TXT records, there’s a greater focus on DMARC (Domain-based Message Authentication, Reporting, and Conformance). ESPs now might ask you to configure DMARC alongside a CNAME record. This alignment ensures both your Mail-From and Return-Path addresses reflect your brand’s domain, enhancing your domain’s reputation, and moving you away from an old, obsolete technology (SenderID).
The CNAME record provided by your ESP directs your Return-Path address (e.g. mailinglist@yourdomain.com) to the ESP’s own Return-Path address (e.g. bouncy_bounceface@tv.csfts.com).
With this set up (here’s the punchline), the SPF and MX records relevant to your emails are managed at the ESP’s end, so there’s no need for you to set them up.
Two Important Notes
First, this information applies only to certain ESPs. If you’re managing your own mail servers or using some CRMs, you’ll likely still need to maintain your own TXT SPF records.
Second, always check domain verification requirements with the ESP and other services you’re using. It’s important to understand what’s needed, and to get this right from the get-go. This should be part of the research to do when selecting the best ESP to use. If you can’t find this information in your ESPs documentation, message their support teams.
