---
schema_version: "1"
id: e9ea3b04f9cec0cd07b76ff2791370b711156b22bf756cdd5c7730330bfb0b19
title: Email Configuration
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_sales_productivity_email_configuration.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_email_configuration.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c29c82eae0b3de99c3461f8e8051edcaae9ea7413db5df4804eea75ae13c613f
description: If you previously worked with Salesforce Customer Support to disable email change verifications, set up authorized email domains instead.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Email Configuration

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)](https://help.salesforce.com/s/articleView?id=release-notes.rn_adopt_authorized_email_domains.htm&release=260&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_email_substitute_unverified.htm&release=260&type=5)**  
    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 uses `email@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](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_check_domain_verification_status.htm&release=260&type=5)**  
    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](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_dkim_reply_to.htm&release=260&type=5)**  
    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.