Salesforce email
Komodo Publications Planning leverages Salesforce's standard email functionality. To function as intended, Salesforce must be authorized by your hosted domain to send emails on its behalf. Without this authorization, emails sent from Salesforce may encounter issues, such as:
Email deliverability issues, e.g. the recipient's email server rules may reject the email
Content may be missing from the email
HTML in the email may not render
Kalos Pharma, a pharmaceutical company that uses Komodo Publications Planning, authorized Salesforce to send outbound emails on behalf of its domain. As a result, when Riley Equest, a call center agent at Kalos Pharma, emails Dr. Dory Octor a Fulfillment Package, the email renders correctly when Dr. Dory Octor opens the email, and the sender on the email is listed as MedInfo@kalos.pharma.com, even though the email was sent from qwertyuiop-12edcrfv345-zxc@salesforce.com. Dr. Dory Octor's email server was able to authenticate the email sent by Riley Equest. Even though the email was sent through Salesforce's servers, Kalos Pharma has authorized delivery for the kalos.pharma.com domain from Salesforce.
Complete these steps to set up your hosted Domain Name System (DNS), not local DNS, with Salesforce:
Create a DomainKeys Identified Mail (DKIM) key to enable Salesforce to sign outbound emails. Visit Salesforce's Create a DKIM Key documentation.
Update the Sender Policy Framework (SPF) record for your domain to allow Salesforce mail servers. Visit Salesforce's Sender Policy Framework and Salesforce SPF Records documentation.
On the Email Deliverability setup page:
Uncheck the Activate bounce management checkbox under the Bounce Management (Emails from Salesforce or Email Relay Only) section.
Uncheck the Enable compliance with standard email security mechanisms checkbox under the Email Security Compliance (Emails from Salesforce or Email Relay Only) section.
Visit Salesforce's SPF and DKIM Alignment Fails documentation for more information on deliverability settings.