---
schema_version: "1"
id: 8770d3b76bf7a8b16a49f794b8e4476318db095987ab108ab8d757b629074f37
title: Send Sensitive Emails Securely with a Secondary Sender Email Address
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_experiences_secondary_sender.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_experiences_secondary_sender.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d567ec0fd8720c385ba671c41fbfc534d6cf573199d5d51212cbdff5463fac57
description: Guard against relay interception by sending sensitive emails from your site directly from Salesforce Mail Transfer Agent (MTA) instead of your corporate email relay. To ensure emails that contain sensitive data, like the Forgot Password email, follow a more secure path, set up a verified secondary sender address. Use secondary sender to meet strict security requirements and align with Domain-based Message Authentication, Reporting, and Conformance (DMARC) standards without modifying your primary domain’s DomainKeys Identified Mail (DKIM) settings. Secondary sender was first released in late Summer ’26.
products:
  - Cross Cloud
release: "264"
---
# Send Sensitive Emails Securely with a Secondary Sender Email Address

Guard against relay interception by sending sensitive emails from your site directly from Salesforce Mail Transfer Agent (MTA) instead of your corporate email relay. To ensure emails that contain sensitive data, like the Forgot Password email, follow a more secure path, set up a verified secondary sender address. Use secondary sender to meet strict security requirements and align with Domain-based Message Authentication, Reporting, and Conformance (DMARC) standards without modifying your primary domain’s DomainKeys Identified Mail (DKIM) settings. Secondary sender was first released in late Summer ’26.

**Where:** This change applies to [Aura, LWR, and Visualforce sites](https://help.salesforce.com/s/articleView?id=experience.exp_cloud_basics_glossary.htm&type=5&language=en_US) accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

**How:** In Setup, verify the email-sending subdomain for your secondary sender email address. System-generated emails from an unverified email-sending domain aren’t delivered, even if you verify the From email address.

To add a secondary sender email address, go to **Workspaces** | **Administration** | **Emails** for your site. Select **Secondary Sender Email** and enter an email address.

![The secondary sender section of the Emails configuration page](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-264-0-0-production-enus/550ba85b-db1a-4608-9cd4-9a65ec96e1fa/salesforce_release_notes/images/experience_cloud/secondarysender.png)

After you verify the email address, emails that contain sensitive information are sent directly from Salesforce via the secondary sender email address and don't route through your company's Simple Mail Transfer Protocol (SMTP) server. Site emails that don’t contain sensitive information—such as Welcome New Member messages sent to existing internal or single sign-on (SSO) users who don't require password credentials—are sent via your configured email relay and network sender address.

#### See Also

- [_Salesforce Help_: Customize Email Sent from Experience Cloud Sites](https://help.salesforce.com/s/articleView?id=experience.networks_customize_email.htm&language=en_US)
- [_Salesforce Help_: Requirements to Send Email from Salesforce](https://help.salesforce.com/s/articleView?id=xcloud.security_email_verification_requirements.htm&language=en_US)