Important Update on Salesforce Email Restrictions
With Salesforce’s most recent release, new restrictions were introduced around sending emails. Here's what you need to know:
- Email Alerts and Automation: If you have Email Alerts triggered by automation (like Flows, Process Builder, or Workflow Rule) and the email is set to come from the user who triggered it (e.g., a Community user), the email will fail unless the sender's email is listed as a Verified Organization-Wide Address. Check out this article for details on configuring Org-Wide email addresses.
- Older Email Actions: Email Actions created before this update may also fail if the Sender Type was not set, since this option didn't exist when they were created.
- Community Emails: If your Community settings include a default sender or owner with an unverified email address (often still set to the Liaison user), emails such as Forgot Password, Change Password, or Welcome Emails will not be delivered.
What You Should Do
- Check your Email Alerts and Flows to make sure the sender email is verified.
- Update any old Email Actions to specify the Sender Type.
- Verify or update the Community email sender to use a valid, verified address.