---
schema_version: "1"
id: 29510ab8e522c526c58d36310196641e6e97f3c4f7d5b3a8877250222c47e8d7
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/262-0-0/rn_experience_secondary_sender.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_experience_secondary_sender.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2dfd9f1595aa07712334036fd89f7d00a2179ee7e30999995ebe1502e55d3a90
description: Guard against relay interception by sending sensitive emails from your Aura or LWR site directly from Salesforce Mail Transfer Agent (MTA) instead of your corporate email relay. To ensure that 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 DMARC standards without modifying your primary domain’s DKIM settings.
products:
  - Cross Cloud
release: "262"
---
# Send Sensitive Emails Securely with a Secondary Sender Email Address

Guard against relay interception by sending sensitive emails from your Aura or LWR site directly from Salesforce Mail Transfer Agent (MTA) instead of your corporate email relay. To ensure that 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 DMARC standards without modifying your primary domain’s DKIM settings.

**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.

**When:** Secondary sender is available starting in July 2026.

**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-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/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 for Email Verification](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)