The Sender Policy Framework (SPF) email authentication method aims to reduce spam and
fraud by making it harder for email senders to hide their identity. SPF detects email spoofing by
providing a process to verify who is permitted to send emails on your behalf. SPF improves message
deliverability, protects the credibility and reputation of your domains, and enhances user trust
and confidence. Salesforce uses SPF and recommends that you do, too.
Required Editions
Available in: Salesforce Classic and
Lightning Experience
Available in: all editions except Database.com
Email messages contain two “from” addresses: the header from address and the envelope from
address. The header from address is in the “From:” field of an email and is visible to all users.
The envelope from address indicates which address to return, or bounce, the message back to.
Some spam detection software looks at the envelope from address to see if it matches any sites
known to send spam. To avoid this type of detection, spammers often use a false envelope from
address.
Email providers use SPF checks to verify that the sender has the authority to send on behalf of
the envelope from address. The SPF check looks up the domain name listed in the envelope from
address and compares its SPF record to the IP address sending the email. If the SPF record
includes the sending IP, the message passes SPF authentication. If it does not, the email can be
flagged as spam.
Salesforce has an SPF record that allows receiving message transfer agents (MTAs) to validate
that the sending MTAs are authorized to send email from the Salesforce domain. Salesforce
encourages customers to implement SPF to ensure that email sent from the Salesforce application
doesn't appear to be spoofed.
There are two ways that you can implement SPF for email sent from Salesforce: enabling Email
Security Compliance or including Salesforce in your SPF record.
Enable Email Security Compliance Email Security Compliance updates the envelope from address in emails sent from Salesforce. With this feature enabled, the email header from address is your email address, but the envelope from address is *.bnc.salesforce.com. Salesforce’s Sender Policy Framework (SPF) record authorizes the IPs used by our message transfer agents (MTAs) to send email from our domain. Email sent from Salesforce passes SPF checks even if you don’t have an SPF record for your email domain.
Include Salesforce in Your SPF Record If you don’t enable Email Security Compliance, we recommend that you set up a Sender Policy Framework (SPF) record for your email domain. To pass SPF checks, include Salesforce in that record.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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
Always Active
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
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
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.