Route Cold Email Leads by Mail Provider: Google, Microsoft, Gateways and the Rest

Routing leads by mail provider means sending each provider group as its own campaign, with its own cap and its own numbers. Look up the MX records behind every lead's domain, label the row Google Workspace, Microsoft 365, gateway (Proofpoint, Mimecast, Barracuda and others), Microsoft consumer, other consumer, or other host, and build one segment per label. Then cap each segment's daily share per inbox, read bounce and reply rates per segment, and slow only the segment that goes wrong. Provider matching, where Google inboxes send to Google recipients, is worth testing but is not documented by either provider.

This is the sending side of a topic we cover from the reporting side in segmenting a list by mailbox provider. That post is about reading MX records and tracking results. This one is about what each route needs before and during a campaign.

Step 1: label every lead by provider

The provider is in the domain's MX records. A few patterns cover most B2B lists:

MX host contains	Label	Notes
google.com, googlemail.com	Google Workspace	Personal @gmail.com addresses are a separate consumer label
mail.protection.outlook.com	Microsoft 365	Business tenants on Exchange Online
pphosted.com, ppe-hosted.com	Proofpoint gateway	Sits in front of Google or Microsoft
mimecast.com	Mimecast gateway	Same
barracudanetworks.com	Barracuda gateway	Same
Domain is outlook.com, hotmail.com, live.com, msn.com	Microsoft consumer	Personal accounts, not a company
Anything else	Other host	Hosting companies, self-hosted servers, regional providers

You do not need to do this by hand. Paste the list into the bulk email provider lookup and it labels each row. For a single domain, the email provider lookup shows the provider and the MX records behind it.

A gateway label hides the real mailbox provider. A Proofpoint domain may run on Microsoft 365 behind it. For routing, the gateway is what matters, because it is the first server your mail meets and the one that decides whether to let it through.

Step 2: verify, then read the results per provider

Verification results differ by provider, so read them group by group rather than as one total.

Route	What verification usually shows	Why
Google Workspace	Mostly valid or invalid; some catch-all	Google answers mailbox checks for most domains
Microsoft 365	Valid or invalid on many tenants; a share look catch-all	Depends on tenant settings, including Directory-Based Edge Blocking
Gateways	A high share of catch-all and unknown	Many gateways accept every address at the door or slow unknown senders
Microsoft consumer	Risky	Outlook.com and Hotmail hide mailbox status during checks
Other hosts	Mixed	Depends on the server

SimpleVerifier never reports a mailbox it could not confirm as valid, so gateway and Microsoft consumer rows come back risky far more often. That is honest, but it changes the plan: a gateway segment with a large catch-all share needs the catch-all rules, not the valid-lead rules. Our posts on verifying emails behind security gateways and why Outlook leads come back risky explain the limits in detail.

Step 3: give each route its own rules

Route	Daily share per inbox	Sequence	Watch for
Google Workspace, valid	Your normal volume	Normal	Spam-folder placement; Gmail's 0.3% spam rate line for personal Gmail
Microsoft 365, valid	Normal, but start lower on a new domain	Normal	Junk-folder placement; 451 4.7.650 throttling
Gateway, valid	Lower	Normal or shorter	Delayed bounces and quarantines that never reply
Gateway, catch-all	A small minority of any inbox's day	Short: step 1 and one follow-up	Late bounces; one company producing most of them
Microsoft consumer	Small, or skip for B2B	Short	Bounces and complaints; these are personal inboxes
Other hosts	Normal for valid rows	Normal	Greylisting deferrals on small servers

Two rules matter more than the exact numbers:

1. Never let a risky route fill an inbox's day. If one inbox sends 40 emails a day, the gateway catch-all share might be five of them. One bad domain should not be able to push that inbox over its bounce threshold. Our catch-all leads in sequences post has the step-by-step version.
2. Send the safest route first each day. Start with confirmed Google and Microsoft leads, then the riskier routes.

Step 4: decide on provider matching

Provider matching means Google Workspace inboxes send to Google-hosted recipients and Microsoft 365 inboxes send to Microsoft-hosted recipients. Several sequencers offer it as a setting, and it is common advice in cold email communities.

What we can say honestly:

• Neither Google's sender guidelines nor Microsoft's sender documentation says mail from their own platform gets better treatment.
• Each provider filters on authentication, reputation and recipient behaviour. Those apply whichever platform sent the mail.
• Matching does keep each provider's problems in one place. If your Microsoft 365 inboxes are being throttled, your Google-hosted prospects are not affected.

So treat matching as an experiment. Split one provider group in two, send half from each inbox type for two weeks, and compare bounce, reply and complaint rates. If the difference is small, route by capacity instead. If you are deciding which inbox provider to buy, our Google Workspace vs Microsoft 365 for cold email comparison covers the limits on each side.

Step 5: report and act per route

Keep one row per route in your weekly numbers:

Measure	Why per route
Bounce rate	A gateway segment can bounce several times more than a Google segment
Delayed bounces	Gateways and catch-all domains bounce later; see bounces from one domain
Reply rate	Falling replies at one provider only point to filtering there, not to your copy
Deferrals (4xx)	A cluster at one provider is a sending problem, not a list problem

When one route moves, act on that route alone:

• Bounces up on one route: pause it, re-verify the rest of that segment, and check whether a few domains caused most of it.
• Replies down on one route, bounces flat: suspect spam-folder placement at that provider. Check authentication and reduce volume on that route.
• Deferrals at one provider: slow down and check your blocklist status. Do not delete the addresses.

A worked example (illustrative)

A team has 3,000 verified leads. After the provider lookup and verification:

Route	Leads	Valid	Risky
Google Workspace	1,350	1,180	170
Microsoft 365	1,050	820	230
Gateways	420	140	280
Microsoft consumer	60	0	60
Other hosts	120	90	30

They run five campaigns. Google and Microsoft valid leads go first each morning at the normal pace. Gateway valid leads get a lower cap. The 280 gateway risky leads become a short two-step campaign capped at a sixth of each inbox's day. The 60 Microsoft consumer addresses are dropped, because for this B2B offer a personal Hotmail address is rarely the buyer. Two weeks in, the gateway risky campaign shows most of its bounces at three companies, so those domains are removed and the rest continue.

Where SimpleVerifier fits

SimpleVerifier checks each address and tells you when it could not confirm a mailbox, so the risky share of each route is visible before you send. Label providers with the free bulk email provider lookup, then upload the list on the verify page. The first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.