Your Salesforce Emails Stopped Working. Here’s How to Find the Problem in 5 Minutes.

Most Salesforce email failures are silent—no error, no alert, just emails that never arrive. This guide surfaces the root cause quickly.

When Salesforce email breaks, symptoms are vague, but damage is immediate: campaigns vanish silently, workflow alerts never fire, and recipients never see messages your org marks as “sent.” Most issues trace to eight root causes. This guide walks through each with exact diagnostic steps and fixes.

Emails Not Sending: Check Deliverability Settings First

Navigate to Setup → Email → Deliverability and confirm Access Level is “All Email.” Sandboxes default to “System Email Only,” blocking all external email. When orgs are cloned from sandboxes to production, this restriction carries over silently—no error, no warning, just emails that vanish.

If access level is correct, check Org-Wide Email Addresses (Setup → Email → Organization-Wide Addresses)—unverified addresses fail silently in Flows and alerts. Also, verify the sending user’s email is confirmed under Setup → Users. For a full configuration walkthrough, see our email deliverability guide.

Authentication Failures: SPF, DKIM, and DMARC Errors

When emails land in spam or get rejected, view full email headers and look for “spf=fail,” “dkim=fail,” or “dmarc=fail.” SPF failures: add include:_spf.salesforce.com to your DNS TXT record. DKIM failures: check Setup → Email → DKIM Keys for activation status and published CNAME records. DMARC failures: ensure SPF and DKIM align with your domain policy.

Since November 2025, Google’s sender requirements have rejected unauthenticated bulk email with permanent SMTP errors. Multiple SPF records on one domain invalidate all of them—consolidate into one and keep DNS lookups under 10. Salesforce Ben’s guide covers the full setup. For step-by-step fixes, see our email authentication guide.

Diagnosing Bounce Spikes and Reputation Damage

A sudden increase in email bounces signals stale list data, infrastructure issues, or reputation damage. Create a report filtered on Email Bounce Date ≠ null, grouped by bounce reason. “User unknown” means list cleaning is needed. “Policy rejection” means your sender reputation is compromised.

Enable Bounce Management under Setup → Email → Deliverability—without it, Salesforce keeps sending to dead addresses. Check Google Postmaster Tools for Gmail reputation and Microsoft SNDS for Outlook. Keep hard bounce rates below 2%. See our bounce management guide for a complete strategy.

Workflow Alerts and Flow Emails Not Firing

When automated emails stop, the issue is usually automation logic, not email. For workflow alerts: verify rule criteria match your data model, confirm the linked template is active, and check that referenced merge fields still exist. Review Setup → Email Log Files—if the email isn’t in logs, the automation never triggered.

For Flow Builder: confirm the Send Email action references a verified Org-Wide Email Address and active template. Check Paused and Failed Flow Interviews under Setup for queued failures. External alerts count against your 5,000 daily limit—verify capacity isn’t exhausted before investigating further.

Emails Landing in Spam Instead of the Inbox

If emails are sent but land in spam, check authentication first (above), then content triggers: all-caps subjects, spam words (“free,” “urgent”), image-heavy emails with minimal text, URL shorteners, and missing unsubscribe headers. Gmail and Yahoo require one-click List-Unsubscribe headers for bulk senders.

Check sender reputation via Google Postmaster Tools and Microsoft SNDS. Low reputation requires reducing volume to engaged recipients, aggressive list cleaning, and 2–4 weeks of trust rebuilding. Dedicated IPs isolate your reputation from other Salesforce orgs on shared infrastructure. See our guide on fixing Salesforce emails going to spam.

Hitting the Daily Sending Limit

Salesforce caps all orgs at 5,000 mass emails per day—shared across every user, campaign, workflow, Flow, and Apex call. No real-time counter exists. When hit, sends fail immediately with no queue or retry. A single 4,000-contact campaign leaves only 1,000 emails for all other operations.

Diagnose by downloading email log files (Setup → Email → Email Log Files) and counting sends by date. Common culprits: bulk data imports triggering workflow alerts, overlapping automated sequences, or multiple teams sending simultaneously. Establish capacity budgets per team and stagger large sends.

Email Relay Errors Blocking Outbound Email

A misconfigured relay can block every outbound email from the entire org. Common failures: wrong SMTP host or port, expired TLS certificates, changed SMTP credentials not updated in Salesforce, and missing Email Domain Filters (relay won’t activate without at least one). Check Setup → Email → Email Relays and Setup → Email → Email Domain Filters.

Always test the relay in a sandbox first. Verify your mail server whitelists Salesforce’s IP ranges, and TLS is enabled. If emails stopped after the relay configuration, disable it temporarily to confirm the source. Relay changes the delivery path but doesn’t bypass the 5,000 daily limit. For setup details, see our email relay guide.

Template Rendering Failures and Tracking Gaps

Broken merge fields occur when templates reference fields the sending user can’t access (field-level security), deleted fields (Visualforce templates break silently), or unavailable record relationships. Preview each template with a specific record in Lightning Email Templates to catch rendering issues before sending.

Tracking gaps—Salesforce shows “sent” but no opens, clicks, or placement data—are a platform limitation. Native mass email provides only aggregate counts. Use email tracking with campaign performance reports for better visibility. Native platforms like MassMailer write every open, click, bounce, and unsubscribe directly to Salesforce records.

Tired of diagnosing email problems after they’ve already hit your recipients? MassMailer catches issues before they cause damage—real-time authentication monitoring, automated bounce suppression, pre-send verification, and inbox placement dashboards. Install MassMailer free and start troubleshooting proactively →

Key Takeaways

  • Check deliverability access level first—“System Email Only” blocks all external email silently, especially in orgs cloned from sandboxes.
  • Inspect email headers for “spf=fail,” “dkim=fail,” or “dmarc=fail”—Gmail and Yahoo reject unauthenticated bulk email with permanent SMTP errors since November 2025.
  • Suppress hard bounces immediately—rates above 2% trigger ISP throttling across your entire sending domain.
  • Check Email Log Files to diagnose automation failures—if an email isn’t in logs, the workflow or Flow never triggered.
  • The 5,000 daily limit is shared org-wide with no real-time counter—one large campaign can exhaust capacity for every other operation.
  • Test relay changes in the sandbox first—a misconfigured relay blocks all outbound email from the entire org.