DEV Community: Siva Devaki

Email Deliverability Expert: What They Do, Why You Need One, and How to Find the Right Fit

Siva Devaki — Fri, 03 Apr 2026 11:29:29 +0000

Nearly 17% of all emails never reach the inbox. They get blocked, filtered, or silently swallowed by spam folders before a single person sees them. That's one in six emails, gone before an open is even possible.

Here's the harder question: do you know if yours are in that 17%?

Most Salesforce teams don't find out until open rates quietly drop, a client mentions they never received your message, or a critical campaign goes out to 40,000 contacts and returns an inexplicably low response. By that point, the damage to your sender reputation is already compounding.

That's exactly where an email deliverability expert earns their place. Not as a luxury for enterprise teams, but as a structural necessity for anyone serious about email performance.

This guide covers what a deliverability expert actually does, why the job has gotten harder in 2025 and 2026, the warning signs you need one right now, and what to look for when choosing the right solution for a Salesforce environment.

What Is an Email Deliverability Expert?

An email deliverability expert is a specialist who ensures your emails consistently land in the inbox, not the spam folder, not the promotions tab, and not a bounce report.

The role sits at the intersection of technical infrastructure, authentication protocols, and sender reputation management. It is not a campaign strategy role. A deliverability expert doesn't write your subject lines or design your templates. Their job is to make sure everything your marketing team builds actually reaches the people it was built for.

Think of them this way: your email marketer builds the message. Your deliverability expert builds the road it travels on.

In a Salesforce context, this distinction matters even more. Salesforce has its own authentication architecture, sending limits, bounce-handling behavior, and API-level quirks. An expert who understands generic ESPs may still miss critical configuration gaps inside Salesforce, gaps that quietly erode inbox placement while your campaign metrics look fine on the surface.

Why Email Deliverability Has Gotten Harder in 2025 and 2026

The rules have changed. What worked in 2022 won't reliably work now.
In 2024, Google and Yahoo introduced stricter bulk-sender requirements, mandating DMARC for high-volume senders and enforcing one-click unsubscribe compliance. These weren't just policy updates. They were enforcement shifts. Senders who had technically compliant records but misaligned configurations started seeing inbox placement deteriorate.

At the same time, Gmail and Microsoft Outlook rolled out AI-powered spam filtering models. These systems evaluate behavioral signals including engagement trends, complaint velocity, and sending consistency, not just authentication records. A domain can pass every technical check and still route to spam if recipient behavior signals low relevance.

BIMI (Brand Indicators for Message Identification) has also emerged as a new credibility layer. Senders with verified BIMI records display their logo directly inside Gmail inboxes. It's not a ranking signal in itself, but it signals to recipients, and increasingly to filters, that you're a verified, trustworthy sender.
The result: the floor for "good enough" deliverability has risen significantly. Teams that haven't updated their configurations in the last 18 months are almost certainly operating with gaps they don't know about.

Now let's talk about what an expert actually does about it.

What an Email Deliverability Expert Actually Does

Sets Up and Audits Authentication Protocols
Authentication is the foundation. Without properly aligned SPF, DKIM, and DMARC records, mailbox providers have no mechanism to trust that your emails are legitimate.
An email deliverability expert doesn't just check whether these records exist. They audit whether the records are correctly configured and properly aligned, because a misconfigured SPF record that technically resolves can still fail DMARC alignment and cause filtering.

What this looks like in practice:

SPF records that explicitly authorize all servers sending on behalf of your domain, including third-party tools and Salesforce's sending infrastructure
DKIM signatures that are validated, properly keyed, and consistent with your sending domain
DMARC policies set at appropriate enforcement levels (none to quarantine to reject), with reporting configured so you actually know what's failing

In a Salesforce environment specifically, this means aligning Salesforce's outbound mail infrastructure with your domain's DNS records, something that requires platform-specific knowledge that a generic deliverability consultant may not have.

2. Monitors Sender Reputation Continuously

Your sender reputation is not a static score. It shifts with every campaign, responding to complaint rates, bounce rates, engagement patterns, and sending volume fluctuations.

An email deliverability expert tracks these signals across mailbox providers. They don't wait for a customer complaint or an open rate drop. They watch:

Domain reputation scores via Google Postmaster Tools and Microsoft SNDS
Hard and soft bounce rates per campaign and per list segment
Spam complaint rates (the danger threshold is 0.10% at Gmail; above 0.30% triggers active filtering)
Blacklist listings across major registries

Catching a rising complaint rate at 0.08% is a very different intervention than responding to blacklisting after you've crossed 0.30%. That gap is what continuous monitoring closes.

3. Improves Inbox Placement Through List and Segment Strategy

Authentication and reputation are necessary but not sufficient. Inbox placement also depends on whether recipients actually want your emails.
Mailbox providers now weight engagement signals heavily. An email sent to 50,000 contacts where only 12% engage sends a different signal than one sent to 15,000 highly engaged subscribers. The expert's job is to shape that signal deliberately.

This means:

Suppressing inactive contacts who haven't engaged in 90-plus days
Segmenting sends by engagement recency rather than total list size
Running re-engagement sequences before suppressing cold segments
Timing sends to align with historical open patterns by segment

The goal is a smaller, higher-quality sending footprint, not blasting the full list every time.

4. Manages Sending Infrastructure and IP Strategy

Infrastructure decisions have long-term reputation consequences. The choice between a dedicated IP address and a shared IP, for example, determines whether your reputation is fully your own or partially dependent on the behavior of other senders on the same pool.

An email deliverability expert evaluates:

Whether your sending volume justifies a dedicated IP (typically required above roughly 100,000 emails per month)
IP warm-up strategy for new domains or dedicated IPs, gradually ramping volume from hundreds to thousands before hitting full scale
Sending velocity controls to prevent sudden volume spikes that trigger filtering
Subdomain strategy for separating marketing sends from transactional sends, keeping different reputation pools for different use cases

For Salesforce users, this also includes understanding how Salesforce's native sending infrastructure interacts with your IP and domain setup, and where external tools like MassMailer fill gaps that Salesforce's default architecture doesn't cover.

5. Executes Reputation Recovery When Things Go Wrong

When deliverability breaks down, open rates fall off a cliff, complaint rates spike, or a domain lands on a blacklist. Recovery isn't just pressing undo. It requires a structured, sequenced intervention.

An email deliverability expert manages:

Blacklist removal requests to major registries (Spamhaus, Barracuda, Microsoft)
IP warm-up sequences to rebuild trust with mailbox providers after damage
Engagement re-seeding campaigns targeting the most active segment first
Sending pattern adjustments to stabilize complaint and bounce rates before scaling back up

Trying to do this without a clear playbook typically makes the situation worse. Continuing to send at normal volume while blacklisted compounds the damage. The expert's value here is the playbook itself.

5 Warning Signs You Need an Email Deliverability Expert Right Now

Most teams don't seek out a deliverability expert proactively. They wait until something breaks. That's the mistake.

Here are the signals that mean you're already in a problem, and the longer you wait, the harder the recovery.

1. Open rates have declined steadily over the past 3 to 6 months with no clear campaign reason.
A slow, sustained open rate decline is almost always a reputation signal, not a content problem. If your subject lines haven't changed dramatically but opens keep falling, inbox placement is eroding.

2. Your bounce rate has crossed 2%.
Hard bounces above 2% indicate list hygiene problems. Left unaddressed, they compound into domain reputation damage. Mailbox providers use bounces as a signal that you're sending to stale or purchased lists.

3. You've never set up or audited your DMARC record.
If you don't know your DMARC policy or when it was last reviewed, it's likely misaligned. Since Google and Yahoo enforced DMARC requirements in 2024, misaligned records create active filtering risks for bulk senders.

4. You recently migrated to a new domain, ESP, or sending IP.
Each of these resets your reputation in some form. Without a structured warm-up and monitoring plan, migrating platforms without expert guidance is the single most common cause of catastrophic deliverability drops.

5. A major campaign underperformed with no clear explanation.
If a campaign to an engaged segment returned unusually low open rates or clicks, it's worth investigating whether the issue is filtering rather than the content itself. Unexplained underperformance is almost always a deliverability flag.

Conclusion

An email deliverability expert isn't a specialist you call when your campaigns are already in crisis. The ones who get the most value from this expertise are the teams that build it into their operations before problems compound.

The technical environment has shifted. AI-powered spam filtering, stricter authentication enforcement from Google and Yahoo, and BIMI adoption have collectively raised the floor for inbox performance. Meeting that floor requires structured expertise, not just good content.

For Salesforce teams specifically, the gap between generic deliverability advice and platform-specific guidance is real. The right solution closes that gap at the infrastructure level, not just the campaign level.

Salesforce Email Blacklist Removal for Gmail: A Step-by-Step Fix

Siva Devaki — Wed, 01 Apr 2026 08:51:58 +0000

You check your campaign reports. Open rates have tanked. Half your audience is on Gmail. Something's wrong but Salesforce says the emails sent fine.

Welcome to one of the more frustrating deliverability problems in the Salesforce ecosystem. Gmail isn't blocking you with a neat error. It's just quietly routing you to spam. Or occasionally bouncing you with a vague 5.7.x code that tells you almost nothing useful.

The phrase "Gmail blacklist" gets thrown around a lot here, but it's a bit misleading. Gmail doesn't run a traditional public blocklist you can request removal from. It evaluates every sender based on a mix of reputation signals, and when those signals go bad, your inbox placement goes with them.

Here's how to diagnose what's actually happening and fix it properly.

First, figure out if you have a block or a spam problem

These look similar on the surface but they're different problems with different fixes.

A hard block means Gmail is rejecting the email outright and returning an SMTP error. Look for codes like 421 (temporary failure), 550 (message rejected), or 5.7.x (policy or authentication violation).

Spam placement means Gmail accepted the email but dropped it in the spam folder. No bounce, just silence and terrible engagement.

Check your Salesforce email logs and bounce reports. If Gmail performance is significantly worse than other providers, you're dealing with a Gmail-specific reputation issue rather than a global one.

Two tools that actually help here: Google Postmaster Tools shows your domain reputation, spam complaint rate, and delivery errors directly from Gmail's side. Email headers let you pull the raw authentication results. Gmail stamps SPF, DKIM, and DMARC pass/fail clearly in every delivered message.

Stop digging the hole deeper

Before fixing anything, reduce volume. This feels counterintuitive but it matters.

If Gmail's trust in your domain is already low, continuing to send at full volume makes recovery slower. Every ignored or spam-marked email is another negative signal stacking up.

For a week or two:

Pause or sharply reduce Gmail-heavy campaigns
Only send to contacts who have engaged in the last 30 to 60 days
Stop sending to anything old, unverified, or purchased

You are stabilizing the situation before making changes, not giving up on sending entirely.

Fix your authentication, this is almost always part of the problem

SPF, DKIM, and DMARC misconfigurations are one of the most common causes of Gmail blocking Salesforce emails. Salesforce teams tend to accumulate sending tools over time, and DNS records don't always keep up.

The classic SPF mistake is publishing multiple records. Only one is allowed per domain. Merge everything into a single record like this:

; Correct: one SPF record with all senders combined
v=spf1 include:_spf.salesforce.com include:sendgrid.net ~all

For DKIM, make sure signing is enabled in Salesforce and that the From domain matches the signing domain. Mismatches here will silently fail alignment even if the key itself is valid.

For DMARC, if you haven't set it up yet, start in monitoring mode so you can see what's failing before you enforce anything:

_dmarc.yourdomain.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

Once SPF and DKIM alignment is confirmed, move to p=quarantine, then p=reject.

List hygiene is usually the actual root cause

Authentication gets the most attention but list quality is often what's really dragging you down.

Gmail doesn't care how big your list is. It cares about engagement. Every email that gets ignored, deleted without opening, or marked as spam chips away at your domain reputation. If you have been emailing a lot of stale contacts, that damage accumulates quietly.

Practical steps:

Remove every hard-bounced address. Don't wait for Salesforce to handle it automatically
Suppress anyone who hasn't engaged in 90 to 180 days
Segment before every send and target active contacts first
If your list is genuinely old, run a reconfirmation campaign and cut the non-responders

This has more impact on Gmail inbox placement than almost anything else.

Keep content simple while you recover

For the first couple of weeks, reduce anything that looks risky:
Plain text or minimal HTML
One link, not five
No image-heavy or image-only layouts
No link shorteners
A real reply-to inbox that someone actually monitors

This isn't about gaming spam filters. It's about not giving Gmail more reasons to be suspicious while your reputation is still rebuilding.

Ramp back up slowly
Recovery takes time. Gmail responds to consistent positive behaviour, not a single clean send.
A rough framework:
Week Who you're sending to
Week 1 Highest-engagement Gmail contacts only
Week 2 Expand to moderately engaged segments
Week 3+ Broaden further if spam rate stays low

Watch your Postmaster Tools dashboard throughout. If complaint rates climb or domain reputation drops, pull back and hold steady before expanding again.

Typical timelines: authentication and hard block issues can resolve within days once DNS is correct. Spam placement from reputation damage usually takes two to six weeks of clean, consistent sending to stabilize.

A few Salesforce-specific settings worth checking

Beyond DNS, some platform-level things quietly affect deliverability:

Deliverability access level in Setup should be All Email, not System Email Only
Bounce management should be enabled with automatic suppression of hard bounces. Make sure Salesforce isn't re-queuing rejected addresses
Mass Email sends are high-risk for Gmail filtering if they target large unengaged lists or fire in sudden bursts. Pace them and filter by engagement before sending
If you're using Einstein Activity Capture to sync Gmail, keep sender names and signatures consistent across synced and native Salesforce sends. Inconsistency creates noisy reputation signals

The pattern behind most Gmail and Salesforce deliverability problems

When Gmail is specifically filtering your Salesforce emails, it's almost always some combination of:

Authentication misalignment across SPF, DKIM, and DMARC
Low engagement from stale or untargeted lists
Burst or inconsistent sending patterns
Bounced addresses being repeatedly re-sent to

Fix those four things systematically and Gmail's behaviour toward your domain changes. It's not quick, but it is predictable.

Originally published on the MassMailer blog.

Salesforce Email Sync: A Technical Guide for Developers and Admins

Siva Devaki — Fri, 13 Mar 2026 04:06:28 +0000

Salesforce Email Sync is one of those features that looks straightforward on the surface but has enough technical depth to trip up even experienced admins. If you're building on top of Salesforce or configuring it for a sales or support team, understanding how email activity sync in Salesforce actually works under the hood will save you hours of debugging and a lot of user complaints.
This article walks through the architecture, setup, common failure points, and best practices for getting Salesforce Email Sync working reliably across Gmail and Outlook environments.

What Is Salesforce Email Sync?

Salesforce Email Sync is the mechanism by which email activity from external mail clients (Gmail, Outlook, etc.) is captured and stored as activity records inside Salesforce CRM. Rather than requiring reps to manually log every email they send or receive, sync creates a two-way or one-way bridge between the mail client and the CRM.

At the data model level, synced emails are stored as EmailMessage or Task records (depending on configuration) and are associated with matching Contact, Lead, or custom object records via email address matching.

Salesforce offers two primary frameworks for this:

Einstein Activity Capture (EAC): Salesforce's native, cloud-based sync engine
Salesforce Inbox: A more feature-rich layer built on top of EAC, with additional productivity tools

There is also the older Email to Salesforce feature (via a BCC address), which is simpler but less automated. Depending on your org's edition and requirements, you may be working with one or all three.

How Salesforce Email Sync Works

Data Flow Architecture
The sync process follows this general flow:

Mail Client (Gmail / Outlook)
        |
        v
OAuth 2.0 Authentication
        |
        v
Salesforce Sync Service (Einstein Activity Capture)
        |
        v
Email Matching Engine (by email address)
        |
        v
Activity Records in Salesforce (EmailMessage / Task)
        |
        v
Associated to: Contact, Lead, Account, Opportunity

When a user connects their Gmail or Outlook account, Salesforce requests OAuth 2.0 scopes to read mail metadata and content. EAC then continuously polls or listens for new activity and pushes matched records into the org.

Email Address Matching

This is where a lot of sync issues originate. Salesforce matches incoming emails to CRM records using the Email field on Contact and Lead objects. If an email address in a thread doesn't match any record in the org, the email still syncs but won't be automatically associated to a record. It lands in the activity timeline only for the connected user.

// Example: Querying EmailMessage records synced via EAC
List<EmailMessage> syncedEmails = [
    SELECT Id, Subject, FromAddress, ToAddress, ActivityId, RelatedToId
    FROM EmailMessage
    WHERE CreatedDate = LAST_N_DAYS:7
    AND Incoming = true
    LIMIT 50
];

for (EmailMessage em : syncedEmails) {
    System.debug('From: ' + em.FromAddress + ' | Related To: ' + em.RelatedToId);
}

Note that RelatedToId will be null if no matching record was found. This is useful for diagnosing unmatched sync records.

Supported Platforms

Platform	Sync Method	Notes
Gmail	OAuth 2.0 via Google API	Requires Google Workspace
Outlook / Microsoft 365	OAuth 2.0 via Microsoft Graph API	Works with Exchange Online
Outlook on-premise (Exchange)	EWS (Exchange Web Services)	Limited support, check version
Apple Mail	Not natively supported	Use BCC to Salesforce as workaround

Key Features of Salesforce Email Sync

1. Automatic Email Logging

With EAC enabled, emails are logged without any action from the user. The sync engine runs in the background, typically with a sync interval of a few minutes. Importantly, EAC stores email data in a separate data store (not standard Salesforce storage), which has implications for SOQL queries and data retention. More on that in the troubleshooting section.

2. Activity Tracking

Beyond just logging, Salesforce Email Sync captures:

Open tracking (if Salesforce Inbox is enabled)
Link click tracking
Reply detection
Calendar event sync (meetings, invites)

These events feed into the Activity Timeline on record pages and can be referenced in reports via the ActivityHistory related list.

3. Contact and Calendar Sync

EAC also supports bi-directional sync of:

Contacts: New contacts created in Gmail or Outlook can sync into Salesforce and vice versa
Events: Calendar events are synced as Event records in Salesforce

Both can be configured independently. You can enable email sync without enabling contact or calendar sync if your use case requires it.


## Benefits of Salesforce Email Sync

From a technical standpoint, the benefits translate to cleaner data architecture:

- **Reduced null fields on activity records:** Manual logging leads to incomplete records. Automated sync enforces consistent data capture.
- **Accurate `LastActivityDate` on Leads and Contacts:** This field drives a lot of automation logic (lead aging, re-engagement workflows). Sync keeps it current without relying on rep behavior.
- **Better signal for automation:** With reliable email activity data, Process Builder and Flow automations that depend on activity history become far more trustworthy.
- **Reporting accuracy:** Email engagement metrics in Salesforce reports reflect actual behavior rather than manually entered data.

---

## How to Set Up Salesforce Email Sync

### Prerequisites

- Salesforce edition with Einstein Activity Capture included (Sales Cloud, some Professional and above editions)
- Connected App configured in Google Workspace or Microsoft 365 Admin Center
- Salesforce admin access

### Step 1: Enable Einstein Activity Capture

Navigate to:

Setup > Einstein Activity Capture > Settings > Enable Einstein Activity Capture


Choose your email provider (Google or Microsoft) and follow the OAuth configuration steps. You'll need to register Salesforce as an authorized application in your mail provider's admin console.

### Step 2: Configure Sync Settings

Setup > Einstein Activity Capture > Settings > Configuration

**Key decisions here:**

- Sync direction: One-way (mail to Salesforce only) or bi-directional
- Excluded 
- email addresses: Add internal domains to prevent internal emails from syncing (this is critical for data hygiene)
- Who can use it: Assign via profiles or permission sets

// Verify EAC is enabled via Apex (useful for automated config checks)
Organization org = [SELECT Id, IsSandbox FROM Organization LIMIT 1];
System.debug('Org ID: ' + org.Id + ' | Sandbox: ' + org.IsSandbox);

// Check connected users via ConnectedApplication or OAuthToken (via REST API)
// EAC user assignments are managed via Setup UI or Metadata API


### Step 3: Assign Users

Users must explicitly connect their email account via:

User Settings > Einstein Activity Capture > Connect Account


This is a per-user action. Admins cannot connect accounts on behalf of users due to OAuth requirements.

### Step 4: Configure Sharing Settings

EAC emails are private by default. Configure sharing so that managers and team members can see synced activity where appropriate:

Setup > Einstein Activity Capture > Settings > Sharing

Options: Private, Internal Only, Everyone.

**Common Challenges and Troubleshooting**

**Sync Delays**
EAC is not real-time. Typical sync latency is 2 to 10 minutes, but can be longer under load. If users report missing emails, first check:

1. Is the user's account still connected? (OAuth tokens expire or get revoked)
2. Is the email address on the email matching a record in Salesforce?
3. Is the email being filtered by an exclusion rule?

**SOQL Limitations on EAC Data**

This is a common gotcha. EAC stores emails in an external data store, not in standard Salesforce objects. This means:

`// This will NOT return EAC-synced emails in many configurations
List emails = [SELECT Id FROM EmailMessage WHERE ...];

// Use ActivityHistory or the UI timeline to verify synced data
// For programmatic access, use the Connect REST API:
// GET /services/data/vXX.0/einstein/activity/activities`




Standard SOQL doesn't reach EAC's data store directly. Use the Einstein Activity Capture REST API for programmatic access.

**Permission Issues**
Common permission errors:

![ ](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8nwe44jtjkwormsbfcp5.jpg)

**Data Privacy Considerations**
EAC syncs email content, not just metadata. This has GDPR and CCPA implications:

- Exclude personal email domains in sync settings
- Define a data retention policy. EAC data is retained for 24 months by default
- Review Salesforce's data processing agreements if operating in regulated industries

**Best Practices for Salesforce Email Sync**

1. Always configure email exclusion lists before going live. Internal addresses, HR systems, and legal domains should never be synced.
2. Use permission sets, not profiles, to manage EAC access. This gives you more granular rollout control.
3. Monitor OAuth token health programmatically or via Salesforce Health Check. Expired tokens are the number one cause of sync outages.
4. Set sync to one-way initially. Bi-directional sync introduces complexity. Validate data quality in one direction before enabling the reverse.
5. Document your matching logic. Know which objects and fields EAC uses to match emails to records. If your org uses custom email fields, you may need supplemental automation to handle association.
6. Test in a sandbox first. EAC can be enabled in sandboxes with test Google or Microsoft accounts. Always validate exclusion rules and sharing settings before production deployment.
7. Plan for EAC's storage model. Because EAC data lives outside standard Salesforce storage, your standard data export and backup tools may not capture it. Account for this in your data governance documentation.

**Conclusion**
Salesforce Email Sync, when configured correctly, is a genuinely useful piece of infrastructure that keeps CRM data current with minimal friction for end users. But the combination of OAuth dependencies, a non-standard data store, and email matching logic means it requires careful setup and ongoing monitoring.
The key things to get right upfront are your exclusion rules, sharing settings, and a clear understanding of how EAC's data model differs from standard Salesforce objects. Get those three things locked down and the rest of the implementation is straightforward.
For teams with more complex requirements, such as high email volume, custom object associations, or deliverability concerns on outbound campaigns, native EAC may not be sufficient on its own. In those cases, it is worth evaluating purpose-built Salesforce email tools that extend EAC's capabilities or replace it with a more robust sync architecture.