Loading

Mandatory Sending-Email Domain Verification Timeline

Veröffentlichungsdatum: Apr 10, 2026
Beschreibung

As part of our ongoing efforts to strengthen the security of our email services, email domain verification is required. Salesforce no longer delivers emails from unverified domains, even if the email addresses are individually verified.

With this change, delivery fails for emails sent from Salesforce if the email domain—the part after the at (@) symbol—isn’t verified via either an active DKIM key or a verified entry in the authorized email domain list.

This article details the dates when this change takes effect.

Lösung

The requirement to verify email-sending domains rolls out in a staggered approach shortly after your org gets Spring ’26, patch 11. Salesforce is making every effort to start with orgs with the least volume and variability of email-sending domains. 

Allowlist Generation: In late February 2026, Salesforce generated a temporary allowlist of email-sending domains for existing orgs. See Determine Your Temporarily Allowlisted Email-Sending Domains.

 

Spring ’26, Patch 11 Deployment

Salesforce started deploying this patch:

  • In sandboxes: March 24, 2026

  • In all other orgs, including production:  March 26, 2026

To get the patch version for your org, go to Trust Status, search for your My Domain name or instance, and then click the maintenance tab. 

 

Phase 1: New Email-Sending Domains and Existing Domains 

With the initial requirement, Salesforce can send email only when the email address uses a verified domain or allowlisted domain. This means:

  • Verification is required for all email-sending domains added after February 25, 2026, regardless of whether you add the domain to a new or existing org.

  • Verification is required for existing email-sending domains that aren’t allowlisted.

Deployment Dates

  • Sandboxes: March 24–April 10

  • All other orgs, including production: April 13–24, 2026

How can you tell when this change is in effect?

When this change is in effect in your org, the Deliverability Setup page includes the Domain Verification section. See Check the Verification Status of Your Email-Sending Domains in Salesforce Help.

 

Phase 2: Enforcement for Allowlisted Domains

When this change is deployed in your org, the allowlisted domains must be verified.  Salesforce can send email only when the email address uses a verified domain. 

Deployment dates for this change

  • Sandboxes: April 14–24, 2026

  • All other orgs, including production: May 4–May 22, 2026

 

Change Log

DateNotes
March 17, 2026Initial publication
March 20, 2026
  • Clarified that the allowlists were generated over several weeks in January and February 2026. The specific dates vary for Government Cloud orgs vs all other orgs. See the linked Determine Your Temporarily Allowlisted Email-Sending Domains knowledge article for more information.
  • Removed detailed timeline schedules because the logic used to determine the rollout plan increased in complexity and potential variability.
April 2, 2026
  • Updated deployment and enforcement dates due to the delayed rollout of Spring ‘26, patch 11.
  • Converted the table of dates to bulleted lists for clarity. 
April 10, 2026In the "Phase 1: New Email-Sending Domains and Existing Domains" section, clarified that the note about a feature is to help customers identify when the change is in effect. Also changed the feature to look for, because the previous feature will be available before the change is made in some orgs.

 

Nummer des Knowledge-Artikels

005316660

 
Laden
Salesforce Help | Article