Now that Salesforce requires domain-level and user-level verification to send email from a site, enable people who use public email services to send messages from the site.
- Enable All Site Users to Send Email
Salesforce now requires both domain-level and user-level verification to send email. Enable users whose email domains you can't verify to send email from your sites. For example, enable people who use public email services such as yahoo.com or icloud.com to send messages from a site. - 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. - Pinpoint Fields with Sensitive Data to Hide from Guest Users
A new warning icon next to field names in the Guest User Sharing Rule Access Report identifies fields that potentially expose personal information. For example, on the account object, the icon flags fields with revenue data or address and contact information. You can review these fields case by case to decide whether to change their sharing rules to hide the fields—and their data—from unauthenticated users.