Loading
The Trailblazer Community is now read-only Read More

Salesforce Email Delivery: Why Emails Sent from Salesforce Are Rejected or Marked as Spam and How SPF and DKIM Fix It

Publish Date: Oct 13, 2026
Description

When you generate email logs in Salesforce, you may see that the sender address has been modified to Variable Envelope Return Path (VERP) format (for example, test=xyz.com__abc123@abc123.bnc.salesforce.com).

Initially, Salesforce recommended enabling "Enable Compliance with standard email security mechanisms," which modifies the envelope sender to a VERP format. Because the email then appears to originate from a Salesforce-managed domain (bnc.salesforce.com), the recipient is more likely to accept it.

However, due to increasingly strict email security checks, recipient servers (like Gmail and others) now require proper domain authentication through Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM). Without these, emails are more likely to be marked as spam or rejected entirely.

Salesforce always recommends implementing SPF and DKIM records to ensure reliable email delivery.

Resolution

This article answers how to ensure Salesforce-sent emails are reliably delivered by properly authenticating your sending domain, instead of relying on the Variable Envelope Return Path (VERP) workaround.

Authenticate Your Sending Domain with SPF and DKIM

Implement Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) records for your sending domain.

Disable Deliverability Settings After SPF and DKIM Are Configured

Once SPF and DKIM are properly configured, disable these two deliverability settings:

  1. Activate bounce management
  2. Enable compliance with standard email security mechanisms
Knowledge Article Number

004633801

 
Loading
Salesforce Help | Article