Why does Salesforce show "sent" when your emails are sitting in someone's spam folder? That's the problem. Salesforce has no way to tell you whether a message hit the inbox or got filtered out. Most teams only find out when open rates tank or replies stop coming.

Spam troubleshooting illustration

Salesforce emails go to spam when authentication records (SPF, DKIM, DMARC) are missing, shared IPs carry a bad reputation, or deliverability settings are misconfigured. Fixing it means setting up authentication, configuring Email Relay, and adjusting a few settings most teams overlook.

Below, we cover how to diagnose the issue, fix the root causes, and stay compliant with Gmail and Yahoo's 2025-2026 sender rules.

How to Tell If Your Salesforce Emails Are Landing in Spam

Salesforce does not report whether an email reached the inbox or the spam folder. It only confirms the message was handed off to the mail server. To find out where your emails actually land, you need to check three things outside of Salesforce's native reporting.

Check Delivery Logs and Bounce Reports in Salesforce

Go to Setup > Email > Deliverability and pull your bounce reports. Look at your hard bounce rate. If it's above 2%, you have a list quality problem that needs fixing before anything else. Enable Bounce Management if it isn't already active so Salesforce flags invalid addresses on Contact, Lead, and Person Account records automatically.

Use Google Postmaster Tools to Track Reputation

Google Postmaster Tools shows how Gmail grades your sending domain. Add your domain, verify it with a DNS TXT record, and watch three numbers: domain reputation (should stay at "High" or "Medium"), spam complaint rate (should stay below 0.3%), and authentication pass rate (should be close to 100%). If any of these shift suddenly, that's usually when emails start hitting spam.

Run an Inbox Placement Test

Send a test email from Salesforce to seed accounts across Gmail, Outlook, Yahoo, and Apple Mail before launching a campaign. This tells you exactly which providers are filtering your messages. Make this a regular step in your campaign process, not a one-time check.

Why Salesforce Emails Land in Spam (and How to Fix Each One)

Salesforce emails go to spam because of authentication gaps, shared IP contamination, content triggers, stale lists, misconfigured settings, or damaged domain reputation. Most orgs have more than one of these working against them. Here's what causes each problem and exactly how to fix it.

Missing Email Authentication (SPF, DKIM, DMARC)

Inbox providers verify every email against three DNS records. If any are missing, your messages look spoofed and get filtered.

Add include:_spf.salesforce.com to your domain's existing SPF record. Don't create a second one. Multiple SPF records on a domain invalidate all of them. Generate a 2048-bit DKIM key under Setup > Email > DKIM Keys, publish the two CNAME records your IT team gets from Salesforce, then go back and click Activate. Set a DMARC record starting with p=none for monitoring. Move to p=quarantine after two weeks of clean pass rates, then p=reject.

Shared IP Address Contamination

Salesforce sends through shared IPs by default, so another org's high bounce rates or spam complaints on the same IP drag your deliverability down, even if your own sending is clean.

The most reliable way to isolate your reputation is to configureEmail Relay (Setup > Email > Email Relays) so outbound email routes through your own mail server. This removes the "via salesforce.com" header and puts you in full control. After setup, turn off "Activate Bounce Management" and "Enable compliance with standard email security mechanisms" under Deliverability settings so the relay handles bounces and headers correctly. High-volume senders (50,000+ emails/month) should also look at a dedicated IP with a 2- to 4-week warm-up.

Content That Triggers Spam Filters

Spam filters evaluate patterns across the entire email, not individual keywords. All-caps subject lines, excessive exclamation marks, image-heavy layouts with little text, URL shorteners, and missing unsubscribe links all raise red flags.

A few guardrails that prevent most content-related filtering:

  • Subject lines under 50 characters
  • A 60/40 text-to-image ratio or higher
  • Branded tracking domains instead of URL shorteners
  • Both HTML and plain-text versions included
  • A functional one-click unsubscribe link in every marketing email

Poor List Hygiene and Stale Data

Sending to invalid addresses or contacts who stopped engaging months ago tells inbox providers you're not maintaining your data. Hard bounces compound fast. Hitting a single spam trap can trigger aggressive filtering across your entire domain.

Start by enabling Bounce Management (Setup > Email > Deliverability) so Salesforce flags invalid addresses automatically. From there, remove contacts with no engagement in six months or longer, and verify addresses at the point of entry before they reach your send list. The benchmarks to stay under: 2% hard bounce rate, 0.3% spam complaint rate.

Misconfigured Salesforce Deliverability Settings

This one is silent and catches a lot of teams. Salesforce sandboxes default to "System Email Only," which blocks all external email. When a sandbox config gets cloned to production, that restriction carries over. No error message, no notification. Emails just never leave the org.

Go to Setup > Email > Deliverability and confirm the Access Level is set to "All Email." While you're there, check that every Org-Wide Email Address (Setup > Email > Organization-Wide Addresses) is verified. Unverified addresses fail silently in Flow Builder and workflow alerts.

Damaged Sender Reputation

Your domain reputation is a trust score built on past sending behavior. Spam complaints, high bounce rates, low engagement, and blacklist presence all erode it. Once it drops, even properly authenticated emails get filtered.

Recovery takes patience. Reduce volume to your most engaged contacts only and send consistently for 2 to 4 weeks to rebuild trust. Monitor your domain status using Google Postmaster Tools for Gmail and Microsoft SNDS for Outlook. Check MXToolbox and Spamhaus weekly for blacklist presence.

2025-2026 Gmail and Yahoo Bulk Sender Requirements

Gmail and Yahoo enforce three rules for any domain sending more than 5,000 emails per day: full email authentication, one-click unsubscribe headers, and spam complaint rates below 0.3%. Non-compliant senders face throttling, filtering, or outright rejection. The authentication setup covered in the previous section satisfies the first requirement. The other two need separate attention.

One-Click Unsubscribe Is Required

Every marketing email must include a List-Unsubscribe and List-Unsubscribe-Post header that lets recipients opt out in a single click. This is separate from the unsubscribe link in your email body. Gmail and Yahoo check for the header itself and increase filtering on emails that don't include it. Process every unsubscribe request within two business days to stay compliant.

Spam Complaint Rate Has a Hard Ceiling

The threshold is 0.3%, meaning no more than three spam reports per thousand emails. Google Postmaster Tools tracks this in real time for Gmail. Once your complaint rate crosses that line, both providers filter aggressively, and recovery requires weeks of clean, low-volume sending. The only reliable way to stay below the threshold is to send relevant content to contacts who actually opted in and engaged recently.

Even if your daily volume is below 5,000, following theserequirements improves inbox placement across all providers.

How to Repair Sender Reputation After Spam Damage

Reputation repair follows a different playbook depending on how far your domain score has dropped. Check your current status in Google Postmaster Tools (set up in Section 1) and match it to the right recovery tier.

Damage LevelSignsRecovery ActionsTimeline
MinorReputation at "Medium." Complaint rate briefly crossed 0.3%. No blacklistings.Send only to 30-day engaged contacts. Resume normal volume once reputation returns to "High."1–2 weeks
ModerateReputation at "Low." One or two blacklistings. Open rates dropped 30%+.Pause bulk campaigns. Send transactional only. Submit delisting requests via MXToolbox. Resume at 10–20% volume, scale weekly.2–4 weeks
SevereReputation at "Bad." Multiple blacklistings. Complaint rate above 1%. Emails rejected outright.Set up a fresh subdomain with a newIP warming schedule. Start with the 500 most engaged contacts. Increase volume 10–15% per week. Authenticate the subdomain before sending.1–3 months

After recovery: Set a recurring weekly reputation check. Remove contacts with no engagement in six months, every quarter. Most reputation collapses trace back to list decay that went unchecked.

How MassMailer Simplifies Salesforce Email Deliverability

MassMailer handles dedicated IPs, authentication monitoring, and inbox placement tracking inside Salesforce, with no external platforms or middleware.

Setting up email authentication, configuring relays, and monitoring reputation all demand manual work. MassMailer automates the heaviest parts:

  • Dedicated sending IPs with automated warm-up isolate your reputation from other Salesforce orgs
  • Pre-send email verification catches invalid addresses before they generate hard bounces
  • Real-time authentication monitoring alerts you when SPF, DKIM, or DMARC records break
  • Inbox placement dashboards show whether emails reach the inbox or the spam folder
  • Campaign-level tracking writes every open, click, bounce, and unsubscribe directly to Salesforce records

The fixes in this guide work on their own. MassMailer brings them into one workflow. Your team spends less time in DNS records andreputation monitoring dashboards. More time goes to campaigns that actually reach people.

If your Salesforce emails are still landing in spam after manual fixes, a deliverability review pinpoints what's left. Schedule a free review with our team →