Sender Policy Framework (SPF) is a simple email validation system designed to detect email spoofing. SPF provides a process to verify which providers can send emails on your behalf. It also aims to reduce spam and fraud by making it harder for anyone to hide their identity.
If you send an email from a Salesforce application and your domain is ABC.com, you can create an SPF record which authorizes Salesforce.com mail servers as allowed for the ABC.com domain. When the recipient receives your email, it checks the SPF record of ABC.com to determine if it is a valid email. The message will have a high chance of delivery if it is validated using SPF.
Salesforce has implemented an SPF record for our domain and we encourage our customers to implement SPF records for their domains as well.
The appropriate entry to include in your SPF record when sending mail from the Salesforce application is _spf.salesforce.com.
Please only use '_spf.salesforce.com' as there are a variety of SPF records for the salesforce.com domain that are for other uses and are not relevant to sending mail from the Salesforce application. Review Include Salesforce in Your SPF Record.
As an example, an SPF record would be similar to:
It could also be similar to:
To help create an SPF record from scratch, you can use tools like the SPF Record Generator from MXToolbox.
For reference, the current format of the record _spf.salesforce.com uses a macro similar to exists:%{i} which covers all the needed Salesforce MTA IPs without the need to explicitly list them.
Also See: SPF and DKIM alignment fails
To confirm that the SPF for the Salesforce record and Salesforce IPs pass validation checks, use the SPF Query Tool from Kitterman.com.
Example SPF policy details:
Mail sent from this IP address: 13.108.238.141
Mail Server HELO/EHLO identity: myaddress@salesforce.com
HELO/EHLO Results - PASS sender SPF authorized
000382664

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.