Most Salesforce email problems aren’t sending problems—they’re delivery problems. Your org confirms the send. The contact never sees it. Inbox providers evaluate every message against authentication records, sender reputation, list quality, and engagement history before deciding whether to deliver, filter, or reject it. Salesforce controls none of those signals for you. This guide covers the six practice areas that determine whether your emails reach inboxes consistently.

1. Authenticate Every Send with SPF, DKIM, and DMARC

Email authentication is no longer optional. Since February 2024, Google has required SPF, DKIM, and DMARC for all bulk senders and began permanently rejecting non-compliant traffic in November 2025. Yahoo and Microsoft enforce equivalent standards.

SPF authorizes Salesforce’s servers to send on behalf of your domain. Add include:_spf.salesforce.com to your DNS TXT record—one record per domain, under ten DNS lookups.

DKIM cryptographically signs each message. Navigate to Setup → Email → DKIM Keys, generate a 2048-bit key, and publish the CNAME records in DNS. DKIM survives forwarding, making it the preferred DMARC alignment mechanism.

DMARC ties both together with a policy. Start with p=none, collect aggregate reports for four weeks, then move to quarantine once every sending source passes. See the Salesforce email authentication guide and DMARC policy reference for a full walkthrough.

2. Protect Your Sender Reputation

Sender reputation is the trust score mailbox providers assign to your domain and IP. Google’s Postmaster Tools tracks domain reputation, IP reputation, spam rate, and authentication pass rates in real time. Review these dashboards weekly to catch issues before they escalate into filtering events.

Three factors erode reputation fastest: hard bounces above 2%, spam complaint rates above 0.1%, and sudden volume spikes on cold IPs. Native Salesforce routes sends through shared IP pools, so your reputation is partly influenced by other tenants. A dedicated IP isolates your sending history. New dedicated IPs require a gradual warm-up before carrying full campaign volume. See how to improve Salesforce email deliverability with a strong IP strategy.

3. Practice Consistent List Hygiene

Every invalid address in your Salesforce database is a liability. Hard bounces signal to inbox providers that your list is poorly maintained, triggering throttling of your domain. Keep hard bounce rates below 2% and remove bounced contacts immediately.

Run email verification before any large send to confirm addresses are active. Suppress contacts with no engagement in six months—continuing to send to disengaged contacts trains inbox providers to filter your domain. For bounce tracking, see the Salesforce email bounce report guide.

4. Optimize Content and Sending Cadence

Inbox providers score message content as part of their filtering logic. Spam-trigger vocabulary, excessive links, and HTML-to-text ratio imbalances all raise the probability of filtering. Test every campaign with an inbox placement tool before sending to your full list.

Cadence matters as much as content. Sending too frequently burns engagement; sending sporadically after long gaps looks suspicious to providers watching volume consistency. Establish a predictable rhythm and segment your audience so each message is relevant. Higher engagement—opens, clicks, replies—signals to providers that your emails are wanted. For timing strategy, see Salesforce email scheduling best practices. For subject line testing, see Salesforce email A/B testing.

5. Honor Unsubscribes and Maintain Compliance

Compliance and deliverability are the same problem from different angles. CAN-SPAM requires a functional unsubscribe in every commercial email. GDPR requires explicit consent. Google requires a one-click unsubscribe in the email header for bulk senders, honored within two days. Subscribers who can’t find an unsubscribe link click “Report Spam” instead—the most damaging reputation signal an inbox provider receives.

Keep spam complaint rates below 0.1%—Google’s threshold per their Email sender guidelines. A preference center reduces unsubscribes and complaints by letting subscribers choose content types and frequency. See the Salesforce email preference center guide and email opt-out management guide for implementation details.

6. Monitor Deliverability Metrics Continuously

Salesforce confirms a send, not inbox delivery. Real monitoring requires tracking bounce rates by campaign, spam complaint trends, open and click rates by segment, and authentication pass rates. Declining open rates without a content change often signal filtering, not disengaged recipients.

Use Salesforce Email Log Files (Setup → Email Log Files) for 30-day delivery diagnostics and Google Postmaster Tools for domain and IP reputation. For Salesforce-native engagement data on Contact and Lead records, see Salesforce email tracking and analytics. For current enforcement trends, see Salesforce email deliverability trends.

Key Takeaways

• Authentication is mandatory: SPF, DKIM, and DMARC are required by Gmail, Yahoo, and Microsoft. Configure all three before any campaign send.
• Reputation is cumulative: Hard bounces, spam complaints, and volume spikes compound over time. Monitor Google Postmaster Tools weekly.
• List hygiene protects inbox placement: Remove hard-bounced contacts immediately and suppress disengaged contacts every six months.
• Content and cadence are scored: Spam-trigger content and inconsistent send volume both raise filtering risk.
• Compliance is a deliverability investment: One-click unsubscribe and low complaint rates protect your sender reputation as much as authentication does.

Salesforce confirms sends, not delivery: Add Google Postmaster Tools, bounce reporting, and engagement tracking to see the full inbox placement picture.