If you previously worked with Salesforce Customer Support to disable email change verifications, set up authorized email domains instead.
- Adopt Authorized Email Domains (Release Update)
If you previously worked with Salesforce Customer Support to disable email change verifications, set up authorized email domains instead. Salesforce is retiring the existing exemption process for disabling this feature, and authorized email domains provide the same benefit. This update is available starting in Spring ’26. - Send Email for Users with an Unverified Email Domain
Enable users whose email domains you can't verify—such as users with public email addresses, consultants, and site users—to send email from Salesforce. With your substitute email address, the user's display name and reply-to address remain unchanged, but the From address usesemail@UniqueId.sfcustomeremail.com, where UniqueId is your org ID or Experience Cloud site ID. This option also applies to system-generated emails and emails sent via shared email accounts with an unverified domain. - Check Your Domain’s Verification Status
To avoid email delivery failures for emails sent from Salesforce, check your domain’s verification status. Salesforce now sends emails only from verified domains. - DKIM Signatures Protect the Reply-To Header
When you sign email sent by Salesforce with a DomainKeys Identified Mail (DKIM) key, the signature configuration now includes the Reply-To header. To protect against conversation hijacking, this change prevents modification of the Reply-To address during delivery. If you use DKIM keys, you get this benefit automatically. Otherwise, set up DKIM keys to securely sign outgoing email sent by Salesforce.