Who is who in email

The email ecosystem mapped: mailbox providers, ESPs, corporate filters, blocklists, standards bodies, and who you can actually appeal to when things break.

Last updated 19 July 2026

Email has no owner. It runs on open standards implemented by thousands of independent operators, which means there is no company to call when "email" mistreats you. There are, instead, half a dozen distinct kinds of organization, each controlling one piece of your message's fate, each with its own incentives and its own (often nonexistent) support channel. Knowing which is which tells you where a problem can actually be fixed, and professionals are separated from amateurs largely by aiming their complaints at the right party. This lesson is the map.

Mailbox providers: the judges

A mailbox provider operates the inboxes your recipients read. Four of them cover most consumer mail on earth: Google (Gmail), Microsoft (Outlook.com, Hotmail, plus Microsoft 365 mailboxes on the business side), Yahoo (which also runs AOL's mail), and Apple (iCloud Mail).

These are the judges. Their filters make the inbox-or-spam decision from lesson one, and their policies are, in practice, the law of sending. When Google and Yahoo jointly announced requirements for bulk senders that took effect in early 2024 (Google's sender guidelines are the canonical text), the entire industry rebuilt itself around them within months. Nobody voted. That's what judicial power looks like here, and there's a full lesson on those rules later in the course.

Two things to internalize about the judges. Their decisions are opaque by design: they publish guidelines, but never explain individual filtering verdicts, because explanations would train spammers. And their scale means your relationship with them is with an algorithm. Google offers Postmaster Tools, a free dashboard showing aggregate reputation and spam-rate data about mail you send to Gmail, and it's the closest thing to feedback Gmail gives. A human conversation is not on the menu for ordinary senders at any of the four.

ESPs: the tools that send for you

An email service provider is the tool a sender uses to send mail to a list and track the results: Mailchimp, Klaviyo, Kit, Brevo, MailerLite, beehiiv, Constant Contact, and dozens more. If mailbox providers are the judges, ESPs are the advocates you hire: they operate sending servers, manage bounces, walk you through authentication setup, and enforce their own anti-abuse rules (an ESP that tolerates spammers watches its whole customer base's mail degrade with the reputation of its shared infrastructure).

That last point deserves a beat. On a typical ESP plan, your mail leaves from servers and IP addresses shared with thousands of other customers. Their behavior touches your reputation and yours touches theirs. It's the apartment-building model of sending, and it's why an ESP's abuse desk being strict is a feature you're paying for, not bureaucracy.

ESPs do have support lines. For anything involving your account, your sending domain setup, or their infrastructure, they are the right first call, and the only party on this map contractually obliged to answer you.

The layer under the tools

Some ESPs run their own sending infrastructure end to end. Others build their product on a separate infrastructure provider: a company selling email delivery itself (the servers and the IPs) rather than a marketing product. beehiiv, for example, provisions its custom-domain sending through SendGrid, which is why beehiiv's DNS setup has you point s1 and s2 DKIM records at sendgrid.net targets, per beehiiv's own setup docs.

You mostly don't choose this layer and can't talk to it; your contract is with the ESP above it. It matters anyway, for one diagnostic reason: the fingerprints in your DNS and headers belong to the infrastructure, and reputation problems can originate there, one level below the brand name you signed up with. When a checker or a header dump shows a company you've never heard of, this layer is usually why.

The corporate filter layer

Consumer mail flows to the big four. Business mail often passes through an extra checkpoint first: a secure email gateway, a filtering product a company buys and parks in front of its Microsoft 365 or Google Workspace mailboxes. Proofpoint, Mimecast, and Barracuda are the names you'll meet most.

For B2B senders this layer changes the game more than most realize. Each gateway has its own filtering logic, its own reputation data, its own quarantine (a holding pen for suspicious mail that recipients rarely check), and its own paying customer, who is the recipient's employer rather than you. A campaign can inbox flawlessly at Gmail and vanish into gateway quarantines at half your business prospects, and no single dashboard anywhere shows you that. Honestly, this layer is a blind spot for every monitoring product, ours included: gateways sit inside private corporate perimeters, and what can be verified from outside is your authentication and reputation posture, which is exactly what gateways weigh first.

Blocklist operators

A blocklist (historically called a blacklist, and also a DNSBL, a DNS-based blocklist, after its query mechanism) is a published set of IP addresses or domains some organization believes are sending abuse. Receivers subscribe to lists they trust and refuse or penalize listed mail.

The operator with real teeth is Spamhaus, a nonprofit whose lists are consulted by a huge share of the world's receivers. Worth knowing by name: the SBL (observed spam sources), the XBL (compromised machines and exploited IPs), the PBL (a policy list of IP ranges, like home connections, that shouldn't be sending mail directly at all), the DBL (a domain list, following the domain rather than the IP), and ZEN, the combined IP zone receivers typically query. Beyond Spamhaus sit dozens of smaller lists of wildly varying quality; some are respected, some are abandoned yet still answering queries.

Blocklists are unusual on this map: unaccountable, in that no one elected them, but mostly transparent, in that the serious ones publish listing criteria and removal processes anyone can read. On shared ESP infrastructure you can inherit a listing from a stranger's behavior on your IP, so listings need watching rather than assuming; the free checkers query the major lists as part of a domain check, and the dedicated lesson on blocklists covers delisting.

The standards bodies

Somebody has to write down what MAIL FROM means. The IETF, the Internet Engineering Task Force, is the volunteer body that publishes internet standards as RFCs, the numbered documents this course keeps linking (RFC 5321 for SMTP and its relatives). The IETF defines protocols; it enforces nothing and has no opinion about your campaign.

M3AAWG (the Messaging, Malware and Mobile Anti-Abuse Working Group) is different: an industry association where mailbox providers, ESPs, blocklist operators, and security teams meet to coordinate anti-abuse practice. Its published documents are how the industry converges on norms faster than standards can be written. Neither body is a place you appeal to; both are where the rules you'll spend this course learning actually come from.

Deliverability people

Finally, the humans this course trains you toward. Deliverability consultants and managed services exist because everything above is fragmented: no single vendor sees your DNS, your ESP account, your list practices, and your reputation data at once, so companies hire someone who can.

The actual work is less mystical than the job title suggests. A deliverability professional audits authentication against the records really published; reads header dumps and DMARC reports (authentication feedback receivers mail to domain owners); watches reputation signals like Postmaster Tools; diagnoses placement drops by timeline (what changed, and when); manages blocklist delistings; pushes clients toward list hygiene they'd rather skip; and knows which appeal channel each provider actually maintains. Larger ESPs keep such people on staff; independent consultants serve everyone else. What none of them have is an inside line that overrides a filter: anyone selling guaranteed inbox placement is selling something the ecosystem's judges deliberately make impossible to promise. The honest version of the job is measurement and method. By the end of this course you should understand every tool on that workbench.

Who picks up the phone

The map, restated as a routing table for problems. Account and setup questions go to your ESP; it has support and is obliged to help. Blocklist listings go to the list's own removal process, which for the serious operators is public and free. Mailbox provider trouble mostly routes to self-serve tooling: Postmaster Tools and the published sender guidelines at Google, sender-support forms at Microsoft and Yahoo. Everywhere, patience, because none of them staff a line for ordinary senders. Corporate gateway quarantines route through your recipient (their IT can release mail and allow-list senders; you can't). And the standards bodies aren't a support channel at all.

Notice what's missing: anyone responsible for your DNS records or your list quality. That's you. The parts of the system with no support line are the parts this course teaches you to run. That work begins with the ground floor's remaining questions, starting with the three fates every email meets: where a message can end up, and which fate reports itself.

Terms from this lesson

mailbox provider - an operator of recipient inboxes (Google, Microsoft, Yahoo, Apple); its filters make the placement decision.
Postmaster Tools - Google's free dashboard showing senders aggregate reputation and spam-rate data for their mail to Gmail.
secure email gateway - a filtering product (Proofpoint, Mimecast, Barracuda) that companies place in front of employee mailboxes; a separate filtering layer for B2B mail.
quarantine - a gateway's holding pen for suspicious mail, outside the recipient's normal mailbox and rarely checked.
blocklist (DNSBL) - a published list of IPs or domains an operator considers abusive, which receivers consult to refuse or penalize mail.
Spamhaus - the most consequential blocklist operator; runs the SBL, XBL, PBL, and DBL, combined for IP queries as ZEN.
IETF - the standards body that publishes internet protocols as RFCs; defines how email works, enforces nothing.
M3AAWG - the industry anti-abuse working group where providers, ESPs, and security teams coordinate practice.
deliverability consultant - a specialist who diagnoses placement problems across DNS, authentication, reputation, and list practice; has no magic access, only method.

Check yourself

1. Your open rates at corporate recipients collapsed while Gmail delivery stayed fine. Which layer of the ecosystem most likely explains it?

2. Which of these organizations is contractually obliged to answer your support request?

3. What is Spamhaus ZEN?

4. A consultant promises guaranteed inbox placement at Gmail for a fee. What should you conclude?