Which Email Setup is Best for My Org?
|Knowledge Article Number||000239741|
|Description||Salesforce offers a few ways to send integrated emails from within Salesforce. This document describes the primary solutions and which one is best-suited for your organization’s needs.|
|Resolution||Users can send emails through the following methods:
If your org is using:
Considerations for Using Send through Gmail and Send through Office 365
Send through Gmail and Send through Office 365 allow Gmail and Office 365 users to send their Salesforce email through their Gmail or Office 365 accounts. This is limited to emails sent through the Lightning Email Composer or certain emails sent via the API. Emails sent through workflow, API, and system emails continue to be sent through Salesforce or Email Relay depending on the configuration.
Emails will be sent using your user’s Gmail or Office 365 inbox so emails won’t be tagged with sent via or “firstname.lastname@example.org on behalf of [sender name]” annotations in the recipient’s inbox.
Setup is easy and secure. Each user will be asked to allow Salesforce to send emails through Gmail or Office 365 using the OAuth industry standard; no user credentials are stored. There also isn’t any need to set up additional email authentication methods like Sender Policy Framework (SPF) or DomainKeys Identified Mail (DKIM) in your DNS.
For more information, see Let Users Send Email through Gmail or Office 365 in the Salesforce Help.
Considerations for Using Email Relay
Email relay automatically routes Salesforce-generated emails through your company’s mail service.
Email relaying is configured for your Salesforce org only. Email relaying enables you to store copies of all email for auditing. You can also append content such as standard footers into all emails. Bounce management is also supported.
For more information about setting up email relaying, see Setting Up Email Relaying in the Salesforce Help.
Considerations for Using Send through Salesforce
Your users can also send emails through Salesforce without integrating with an external email service. This a great approach if you’re using Salesforce Classic, need bounce management, or aren’t using Gmail or Office 365 with Lightning Experience.
Setup Recommendations for Send through Salesforce
If your email address domain is owned by your company (such as mycompany.com):
1. Turn OFF “Enable compliance with standard email security mechanisms”
2. Turn OFF "Enable Sender ID compliance"
3. Add Salesforce’s SPF record to client’s domain DNS to indicate that Salesforce is an approved sender e.g SPF record: "v=spf1 mx include:_spf.salesforce.com ~all"
4. Set up DKIM for better deliverability.
If your email address domain is not owned by your company and ends in @gmail.com, @aol.com or @yahoo.com, you need to register for a domain that you control, and use this new domain for all of your emails sent from Salesforce due to the Domain-based Message Authentication, Reporting & Conformance (DMARC) policy at Gmail, AOL and Yahoo. See here for more information. Otherwise:
1. Turn ON “Enable compliance with standard email security mechanisms”
2. Turn OFF “Enable Sender ID compliance”. We recommend enabling Sender ID compliance only if you have recipients using the Sender ID email authentication protocol, which isn’t widely used.