ISP vs ESP: What Cold Emailers Need to Know in 2026

TL;DR

• ISP in email talk means the mailbox provider that hosts the recipient's inbox: Gmail, Outlook.com, Yahoo, or a corporate Microsoft 365 or Google Workspace tenant. It decides inbox, spam, or reject.
• ESP means the email service provider that sends mail for you, usually in bulk: SendGrid, Mailchimp, Brevo, Amazon SES.
• The ESP sends. The mailbox provider decides. Your domain reputation, authentication, and complaint rate matter more than which ESP you pick.
• Bulk ESPs ban cold lists in their acceptable use policies. Sending cold outreach through them gets accounts suspended.
• Cold email runs on real mailboxes on secondary domains, warmed for 2 to 4 weeks, at 30 to 50 emails per inbox per day, with Gmail spam complaints under 0.1%.

Overview

ISP vs ESP is the first distinction every cold emailer needs to get right, because mixing them up is how domains get burned and sending accounts get banned. An ISP, or more accurately a mailbox provider, is the company that receives and filters your email. An ESP is the company that sends it.

Most articles on this topic stop at the definitions. This guide goes further: how each one affects inbox placement, what the ESPs' own policies say about cold lists, and why outbound teams send from Google Workspace and Microsoft 365 mailboxes instead.

It's written for founders, SDR leaders, and agencies running B2B outbound. If you only send newsletters to opted-in subscribers, the ESP sections still apply, but the cold email rules won't.

ISP vs ESP: The Short Answer

An ISP (mailbox provider) receives email and decides whether it reaches the inbox. An ESP sends email on your behalf and manages lists, templates, and sending infrastructure.

They sit at opposite ends of the same delivery path. Here is how they compare.

What Is an ISP in Email?

Strictly, an ISP is an internet service provider: the company that connects you to the internet, like Comcast or BT. Email people kept the term from the early days, when your ISP also gave you your email address.

Today, when a deliverability guide says ISP, it almost always means the mailbox provider on the receiving end.

ISP vs Mailbox Provider

The more precise term is mailbox provider (MBP), sometimes called a mailbox access provider. Gmail is not an internet service provider, but it is the biggest mailbox provider in the world.

For B2B cold email, the mailbox providers that matter are Google (Gmail and Google Workspace) and Microsoft (Outlook.com, Hotmail, and Microsoft 365). Most business inboxes run on one of the two, often behind an extra security gateway like Mimecast or Proofpoint.

What Mailbox Providers Judge

Mailbox providers score every incoming message on signals they can measure. The big ones are below.

• Authentication: SPF, DKIM, and an aligned DMARC record prove the mail really comes from your domain.
• Domain reputation: the history of mail from your sending domain, built over weeks. Read our guide to email sender reputation for how it is scored.
• IP reputation: the history of the server that handed over the message.
• Complaints and bounces: spam reports and invalid addresses are the fastest way to lose trust.
• Engagement: replies, moves out of spam, and deletes without reading.

What Is an ESP?

An ESP is a service that sends email on your behalf, typically to many recipients at once. It gives you sending servers, an API or SMTP endpoint, list and unsubscribe management, and reporting.

ESPs split into two broad groups: marketing platforms like Mailchimp and Brevo, and transactional or API senders like SendGrid, Amazon SES, Mailgun, and Postmark. Some do both.

Shared vs Dedicated IPs

On a shared IP, your mail goes out from the same addresses as many other customers. Their behavior affects your IP reputation, good or bad, and the ESP polices abuse hard to protect the pool.

A dedicated IP is yours alone. It only makes sense at steady high volume, because mailbox providers need consistent traffic to build a reputation for it, and a new dedicated IP must be warmed up first.

Either way, mailbox providers increasingly judge the domain in your From and DKIM signature, not just the IP. Changing ESPs does not reset a damaged domain.

SMTP Relay vs Marketing Platform

An SMTP relayis a server that accepts your message and forwards it to the recipient's mail server. Amazon SES, SendGrid, and Mailgun all offer one, so you can plug them into an app, a CRM, or a sequencer.

A marketing platformadds a list database, drag-and-drop templates, segmentation, and campaign analytics on top. Both still run on the ESP's IPs and fall under the same acceptable use policy.

Your own mailbox also has an SMTP server. Connecting a Microsoft 365 account to a sending tool uses Microsoft's SMTP, which we cover in Office 365 SMTP settings.

Why Cold Email Tools Call Gmail an ESP

Here is where the terms get messy. Cold email sequencers often label Google and Microsoft as ESPs, for example in ESP matching features that send from Google mailboxes to Gmail recipients and from Microsoft mailboxes to Outlook recipients.

In that context, ESP just means the mailbox platform your sending account lives on. It does not mean Google Workspace is a bulk sender like SendGrid, and it does not change the rules either side enforces.

How an Email Travels From Sender to Inbox

Every email passes through both an ESP role and a mailbox provider role. The path looks the same whether you send a newsletter or a cold email.

1. You write and queue the email in a marketing platform, a sequencer, or your mail client.
2. The sending service signs it with DKIM and hands it to its outbound SMTP server. For a bulk ESP, that is the ESP's IP. For a Workspace or Microsoft 365 mailbox, that is Google's or Microsoft's.
3. The sending server looks up the recipient domain's MX record and connects to the mailbox provider's receiving server.
4. The mailbox provider checks the connection: IP reputation, reverse DNS, TLS, and rate limits. It can defer or reject here.
5. It authenticates the message: SPF, DKIM, and DMARC alignment against your domain.
6. It filters the content and sender: domain reputation, complaint history, content, and links.
7. It places the message: primary inbox, a tab like Promotions, spam, or a bounce back to you.

Steps 1 and 2 are the ESP's job. Steps 4 to 7 belong entirely to the mailbox provider. That is why the receiving side, not your sending tool, sets the rules.

Who Decides Inbox Placement: Mailbox Provider Rules

Google, Yahoo, and Microsoft publish their sender requirements. Your ESP or sequencer can help you meet them, but it can't negotiate them.

The table summarizes Google's email sender guidelines, Yahoo's sender best practices, and Microsoft's requirements for high-volume Outlook senders.

Cold outbound rarely crosses 5,000 a day to one provider, but treat these as the floor anyway. Our email deliverability checklist turns them into a pre-send routine, and how to avoid spam filters covers the setup step by step.

Why Cold Email Can't Run on Bulk ESPs

Cold email can't run on bulk ESPs because their terms forbid sending to people who haven't opted in. Even if an account slipped through, the shared infrastructure and bulk-mail fingerprint work against one-to-one outreach.

What ESP Acceptable Use Policies Say

We read each ESP's own policy page. None of them carve out an exception for B2B cold outreach.

The practical result: ESPs monitor bounce and complaint rates per account, and cold lists produce both. Expect a suspension, sometimes mid-sequence, with your contact data stuck in a platform you can't send from.

The Infrastructure Mismatch

Policy aside, bulk ESPs are built for the wrong job. Their mail carries bulk fingerprints: HTML templates, tracking pixels, rewritten links, list headers, and IP ranges mailbox providers know as marketing senders.

That is fine for a newsletter people asked for, which lands happily in the Promotions tab. A cold email that looks like a newsletter from a stranger gets filtered or ignored.

Cold email works when it looks like what it claims to be: a short, plain-text note from one person to another. Real mailboxes produce exactly that.

How Cold Email Infrastructure Actually Works

Cold email runs on ordinary business mailboxes from Google Workspace or Microsoft 365, spread across secondary domains and driven by a sequencer. The mailbox provider's own SMTP sends each message, so it leaves from Google or Microsoft servers like any colleague's email.

Our guide to the best email hosting for cold email compares the mailbox options. A typical setup looks like this.

1. Secondary domains. Buy lookalike domains (for example, getacme.com for acme.com) and redirect them to your main site. Never cold email from your primary domain.
2. 2 to 3 mailboxes per domain. Real named users on Google Workspace or Microsoft 365, each with SPF, DKIM, and DMARC set up.
3. 2 to 4 weeks of warmup. Mailboxes exchange low volumes of mail and replies to build a positive history before any cold sends.
4. 30 to 50 emails per inbox per day. Counting follow-ups. To send 1,000 a day you need roughly 25 warmed inboxes, not one inbox pushed harder.
5. A sequencer connects to every mailbox over SMTP or OAuth, rotates sends, spaces them out, and handles replies. Our list of unlimited email sending platforms covers the options.
6. Verified lists. Every address checked within 30 days of sending to keep hard bounces under 2%.
7. Monitoring. Google Postmaster Tools for the Gmail spam rate, bounce logs for Outlook errors, and regular placement tests. Our email deliverability test guide shows how to run them.

One honest caveat: Google and Microsoft's terms also prohibit spam, and Google Workspace caps each user at around 2,000 messages a day. Cold email stays on the right side of both by sending relevant, low-volume, individually addressed messages with an easy opt-out, not by hiding behind more inboxes.

The law still applies too. CAN-SPAM in the US requires a working opt-out and a physical address, and GDPR in the EU requires a legitimate-interest basis for B2B outreach.

When You Should Use an ESP

ESPs are the right tool for mail people asked for. Use one when the recipient opted in or triggered the email themselves.

• Transactional email: password resets, receipts, onboarding, and product notifications. SES, SendGrid, and Postmark are built for this.
• Newsletters and product updates to subscribers who signed up.
• Nurture sequences to inbound leads who downloaded content or booked a demo.
• Customer marketing to existing users, with one-click unsubscribe.

Many teams run both: an ESP or marketing automation platform for opted-in mail, and a separate cold stack on secondary domains. If your marketing platform is HubSpot, our HubSpot email deliverability guide covers that side.

Keep the two on different domains. If a cold domain gets damaged, your receipts and newsletters keep landing.

Common ISP vs ESP Mistakes

These are the mistakes we see most often when teams confuse the two roles.

• Blaming the ESP for spam placement. Switching tools rarely fixes inbox placement, because the mailbox provider is judging your domain and list. Fix authentication, bounces, and complaints first.
• Uploading a cold list to Mailchimp or SendGrid. It breaks their policies and usually ends in a suspension within days.
• Cold emailing from the primary domain. Damage to its reputation hits every email your company sends, including invoices and support replies.
• Assuming a dedicated IP fixes deliverability. A cold IP with low, bursty volume has no reputation, and a bad domain still sinks it.
• Ignoring blocklists. A listing on Spamhaus can block mail at many providers at once. See our IP blacklist removal guide if you land on one.
• Sending to unverified data. A 5% bounce rate tells every mailbox provider your list is bought or stale.

Conclusion

The ISP vs ESP question comes down to one line: the ESP sends, the mailbox provider decides. Gmail, Outlook, and Yahoo set the rules, and they judge your domain, authentication, complaints, and bounces, whatever tool you send from.

Use ESPs for opted-in and transactional mail. Run cold outreach from warmed Google Workspace and Microsoft 365 mailboxes on secondary domains, at 30 to 50 sends per inbox per day, to verified contacts.

The list is the part most teams skip. Try SyncGTM free to find and verify B2B emails through a multi-provider waterfall at 0.1 credits per check, or see pricing for higher volumes.