Salesforce is taking steps to help prevent email delivery disruption when Salesforce removes your temporary email-sending domain allowlist. Starting June 23, 2026, we turn on a substitute email address for unverified domains.
Where: This change applies to Lightning Experience and Salesforce Classic in all editions except Salesforce Free Suite and Database.com. This change has no impact on trial orgs.
When: Salesforce plans to enable the “Use a substitute email address for unverified domains” Deliverability setting in Government Cloud orgs the week of July 7, 2026. For all other orgs, we plan to enable that setting June 23–July 3, 2026.
To review when Salesforce removes temporary allowlists, see Mandatory Sending-Email Domain Verification Timeline.
Why: Salesforce only sends email from an unverified domain if the email domain is on the temporary allowlist or the substitute email address is enabled in your org. If you can't verify your allowlisted domains before Salesforce removes the temporary allowlist, the substitute email address enables those users to keep sending email from Salesforce. Similarly, if you add users with a new email domain, this setting enables those users to send email from Salesforce until you can verify the new email domain.
How: No action is required if you previously verified your email-sending domains and you want Salesforce to send email for users with an unverified email domain.
If you prefer not to use the substitution email address, from Setup, in the Quick Find box, enter Deliverability, and then select Deliverability. Deselect Use a substitute email address for unverified domains, and then save your changes.
If you turn off that setting, Salesforce no longer sends email from unverified domains, including new email domains. To enable users to send email from Salesforce via a new email domain, verify that domain with a DKIM key or authorized email domain.