Ivona MikulčićNovember 19, 20267 min read

ESP matching: why sending Gmail to Gmail and Outlook to Outlook helps cold email

Same email, two different outcomes. Send it from Gmail to Gmail and you get a 4.1% reply rate. Send it from a Microsoft mailbox to that same Gmail inbox and replies drop. The copy did not change. The provider did.

That gap is what esp matching fixes. It routes each email through a sending mailbox that matches the recipient’s provider, so Google talks to Google and Microsoft talks to Microsoft.

In this article, I’ll walk through what esp matching does, why it moves reply and bounce rates, and how to check your own list’s provider split before you buy a single mailbox. You’ll also see where matching does not pay off and the setup mistakes that quietly cancel out its benefit.

Get this right and your infrastructure stops fighting the inbox and starts working with it.

What ESP matching is

Here is the simplest way to picture it:

Lead’s provider

Your sending mailbox

Google Workspace

Your Google Workspace mailbox

Microsoft 365

Your Microsoft 365 mailbox

The routing happens automatically when your sending tool supports it and you have mailboxes on both providers connected.

Why it can help inbox placement

When an email stays inside one provider’s network, it follows internal routing paths. Google receiving a message from another Google Workspace tenant, for example, can verify the sender through its own infrastructure without relying on external reputation checks alone. The same applies to Microsoft 365 receiving from another Microsoft 365 tenant. Fewer cross-provider handoffs mean fewer opportunities for an intermediary filter to flag the message.

That said, matching is a marginal gain. It works on top of SPF, DKIM, DMARC, warm-up, and clean lists. It does not rescue a mailbox with poor sender reputation.

lemlist internal data from its users (all markets, 46.1M leads) shows a measurable difference in reply rates and bounce rates depending on whether the sending provider matches the recipient’s provider:

Route

Email reply rate

Bounce rate

Google to Google

4.1%

4.5%

Microsoft to Microsoft

3.2%

5.6%

Microsoft to Google

2.6%

6.1%

Google to Microsoft

2.5%

6.4%

Same provider (combined)

3.5%

5.5%

Crossed provider (combined)

2.7%

6.3%

Source: lemlist internal data from its users.

Campaigns that send from the same provider as the prospect reply at 3.5%, compared to 2.7% when the provider is crossed. Open rates follow the same pattern: Google to Google reaches 46.2%, Microsoft to Microsoft 41.3%, and crossed routes land between 38% and 39%.

How to know which provider your leads use

The MX record of a lead’s domain tells you which provider handles their inbound email. An MX record is a DNS record that names the servers receiving email for a domain, and it shows which provider hosts a company’s email, such as Google Workspace or Microsoft 365.

A primary MX of aspmx.l.google.com indicates Google Workspace. A primary MX ending in mail.protection.outlook.com indicates Microsoft 365.

You can check a single domain from the command line or use a bulk MX lookup tool to process your entire lead list at once. The important step is to check your list’s provider split before you buy mailboxes, so you know how many Google and Microsoft senders you need.

How to set up ESP matching

1. Check your lead list’s provider split

Run your lead domains through an MX lookup. Count how many fall under Google Workspace, how many under Microsoft 365, and how many under other providers (Zoho, self-hosted, security gateways). This split determines your mailbox buying plan.

If 60% of your leads are on Google and 30% on Microsoft, your sending infrastructure should reflect that ratio.

2. Buy mailboxes on both providers in the same ratio

Match your mailbox count to the provider split you found. A list that skews 70/30 Google needs roughly 70/30 Google to Microsoft mailboxes.

Each mailbox should sit on a dedicated cold email domain, separate from your main company domain. For a deeper comparison of the two providers, see Google vs Outlook for cold email.

3. Authenticate and warm up every mailbox

Every new mailbox needs SPF, DKIM, and DMARC configured before it sends a single cold email. Skipping authentication on one provider while the other is set up correctly creates an uneven reputation that defeats the purpose of matching.

Follow the full checklist in email sender requirements, then warm up your email account on both providers. Warm-up builds the sending history that providers look at before deciding whether to place your message in the inbox or the spam folder.

4. Turn on matching in your sending tool

Once your mailboxes are authenticated and warmed, enable ESP matching in your sending platform. The tool reads each lead’s MX record, identifies the provider, and routes the email through a connected mailbox on the same provider.

If no matching mailbox is available for a given lead, the email goes out from your default sender pool. No lead gets stuck unsent.

5. Watch volume per mailbox

ESP matching can create uneven load. If your list is 80% Google and you only have two Google mailboxes, those two mailboxes absorb most of the volume and risk burning out.

Spread volume across enough mailboxes to stay within safe daily limits. For guidance on per-mailbox caps, see how many emails can you send a day.

When ESP matching is not worth it

ESP matching adds complexity. It is not always worth the setup cost.

  • Your list is 90%+ on one provider. Buying mailboxes on the second provider for a handful of leads adds cost with minimal return.

  • You send low volumes from one or two mailboxes. The deliverability gain from matching is too small to notice at 20 emails a day.

  • A large share of your leads use Zoho, ProtonMail, or self-hosted mail servers. Matching only works for Google Workspace and Microsoft 365 in most tools, so those leads go through your regular sender pool regardless.

  • You are sending warm follow-ups or replies to inbound leads. These messages already carry engagement history, and provider matching adds nothing meaningful to an ongoing thread.

Mistakes to avoid

Buying only Google mailboxes for an Outlook-heavy list. If 60% of your leads are on Microsoft 365 and all your senders are on Google Workspace, every email crosses providers. Check the split first, then buy accordingly.

Skipping warm-up on the new provider. Adding Microsoft mailboxes to match your Outlook leads does nothing if those mailboxes have zero sending history. A fresh, unwarmed mailbox on the right provider will perform worse than a warmed mailbox on the wrong one.

Overloading the few matching mailboxes. If you connect two Google mailboxes and eight Microsoft mailboxes but your list is 70% Google, those two Google senders carry the entire load. Monitor volume per mailbox and add senders when any mailbox approaches its daily cap. If emails are landing in spam on the Microsoft side, check the troubleshooting steps in emails going to spam in Outlook.

How lemlist helps

lemlist has ESP matching built in, called Email provider matchmaker in the app. It reads the MX records of each lead’s domain to identify whether the lead uses Google Workspace or Microsoft 365, then sends from a connected mailbox on the same provider.

When no matching mailbox is connected, the email goes through the default sender pool so no lead is left out. The feature is turned on at team level in the sending settings.

lemwarm works alongside it to warm up both Google and Microsoft mailbox types, building sender reputation on each provider before cold sends begin. Combined with SPF, DKIM, and DMARC authentication, this gives each mailbox the foundation it needs before matching routes traffic to it.

Final takeaway

ESP matching is a small, measurable edge. It will not fix broken authentication, spammy copy, or an unwarmed domain. But once those fundamentals are solid, routing Google to Google and Microsoft to Microsoft gives your emails a better chance of landing where your leads will read them.

Start by checking your lead list’s provider split, buy mailboxes to match it, authenticate and warm every one of them, then turn on matching.

Build your first signal-based sequence in lemlist.

Land more emails in the inbox

Warm up your inboxes and protect your sender reputation from spam folder.

Frequently asked questions

ESP stands for email service provider. In cold email, it refers to the platform hosting a mailbox, such as Google Workspace or Microsoft 365.

No. Matching routes your email through the right provider, but the receiving server still checks your sender reputation. A mailbox that has not been warmed up will land in spam regardless of whether the provider matches.

The email goes out from your regular sender pool. Matching only applies when a connected mailbox shares the same provider as the lead. Leads on Zoho, ProtonMail, or self-hosted servers receive your email from whichever mailbox your tool selects by default.

Only if your lead list has a meaningful share of both providers. Run an MX lookup on your list first. If 95% of your leads are on one provider, a second set of mailboxes adds cost without a meaningful return.
Ivona Mikulčić

Ivona Mikulčić

Product Marketing Manager

Share this post