# Cold email infrastructure, explained: domains, mailboxes and servers

> What cold email infrastructure is, the three reputations inbox providers judge you on, why shared servers put you at risk, and how to build a setup that lands.

- URL: https://senderpools.com/blog/cold-email-infrastructure
- Author: Sender Pools Team
- Published: 2026-11-17
- Topic: Infrastructure

Most cold email advice is about the email: the subject line, the opener, the call to action. But whether that email reaches an inbox is decided before anyone reads a word. It is decided by the infrastructure underneath it: the domains you send from, the mailboxes on those domains, and the servers that actually hand your message to Gmail or Outlook.

This guide explains what cold email infrastructure is, how inbox providers judge it, and why the server you send from matters more than most people think.

## What cold email infrastructure is

Cold email infrastructure is everything between your sending tool and your prospect's inbox. It has three layers, stacked on top of each other:

| Layer | What it is | Where it comes from |
| --- | --- | --- |
| Server | The machine, and its IP address, that delivers your email | Google, Microsoft, or an SMTP provider |
| Domain | The name after the @, like acme.com | A registrar such as GoDaddy, Namecheap or Porkbun |
| Mailbox | The address you send from, like mike@acme.com | Created on the domain, hosted on a server |

One server can carry many domains. One domain can carry several mailboxes. Around those three layers sit the settings that tie them together: DNS records (SPF, DKIM and DMARC), warmup, and rotation.

A sequencer, the tool that schedules your campaigns, sits on top of all of this. It is not infrastructure. It tells the mailboxes what to send and when. If the layers underneath are weak, the best sequencer in the world will still deliver to spam.

## The three reputations inbox providers check

When your email arrives, Gmail and Outlook do not ask one question. They look at three reputations and combine them into one overall judgment of whether you belong in the inbox.

**Domain reputation.** How mail from acme.com has behaved over time: bounce rates, spam complaints, how often people open and reply. This is why you should never send cold email from your company's main domain. If that domain's reputation drops, your invoices and password resets drop with it. (More on that in our guide to [secondary domains](/blog/secondary-domains-for-cold-email).)

**Email address reputation.** Each mailbox builds its own history. mike@acme.com and tyler@acme.com can have very different standing on the same domain, depending on how much each one sends, how it was warmed up and how recipients react to it.

**Server reputation.** The IP address your email leaves from has a reputation too, built from everything that has ever been sent from it. This is the layer most people never think about, and it is the one you control least.

A strong domain on a damaged server still struggles. A clean server cannot rescue a domain that has been burned. All three need to be healthy at the same time.

## Shared servers

When you buy a Google Workspace or Microsoft 365 mailbox, your email goes out through servers that are shared with a very large number of other senders.

That is not a bad thing. Google and Microsoft are the best known senders on the internet, and their IP addresses carry a reputation that a brand new server cannot match. Inbox providers see mail from them every second of the day and give it a level of trust from the start. That built-in trust is a big part of why Google and Microsoft mailboxes are a core piece of any cold email setup.

The catch is that you share that trust with everyone else on the same servers, so part of your reputation is set by your neighbors. And you do not always stay on the best servers. Microsoft, for example, is known to move mail from senders with poor reputation onto separate, lower quality IP pools, where it is far more likely to land in spam.

Picture one sending server with three well-run senders on it: acme.com, another.com and anvil.com. Each sends sensibly, and the server keeps a good reputation, so mail from all three lands.

Now a fourth sender joins: stranger.com. It blasts a scraped list with spammy copy. Complaints and bounces climb. Inbox providers do not only mark down stranger.com; the server it shares with everyone else starts to look worse too. Mail from acme.com, another.com and anvil.com begins slipping into spam, and none of them changed anything.

You cannot pick your neighbors on a shared server, and you usually cannot tell when one goes bad. You only see your placement fall. That is why the strongest setups do not rely on shared servers alone.

## Private servers: only your mail, only your reputation

The alternative is a server that carries only your own domains. On a private SMTP server, the only mail leaving that IP is yours. Its reputation is built entirely by how you send, so a stranger's campaign can never drag you down.

There is a second benefit that matters just as much. Google Workspace and Microsoft 365 are built for everyday business email, and both can suspend accounts they see sending cold email at volume. When that happens, the mailbox stops sending overnight and its history goes with it. A private server built for cold email does not have that problem. Cold email is what it is there for, so you never have to worry about the account being shut down for doing exactly what you set it up to do.

Private servers also scale cleanly. When you need more volume, you add another server with its own set of domains and mailboxes, rather than piling more onto one. Each server is its own contained unit, so a problem on one does not spread to the others.

The trade-off is work. Someone has to set up the servers, keep them healthy and watch their reputation. That is real infrastructure management, and it is the part most teams would rather not own.

## Why most setups use a mix

Different inbox providers trust different senders. Gmail tends to treat mail from Google servers one way, Outlook treats Microsoft servers another way, and both judge independent SMTP servers on their own track record. A setup that spreads mailboxes across Google, Microsoft and SMTP is not betting everything on one provider's opinion. If placement slips on one type, the others keep sending.

The right mix depends on who you are emailing. A list full of Outlook users may land better from Microsoft mailboxes. The only reliable way to know is to measure placement per mailbox type and shift volume toward what is working.

## What a working setup needs

Whichever servers you use, the same checklist applies before the first email goes out:

1. **Secondary domains** that look like your brand, never your main domain.

2. **Three to five mailboxes per domain**, so one bad domain takes out only a little of your capacity. Our guide to [how many mailboxes you need](/blog/how-many-mailboxes-for-cold-email) does the math.

3. **No more than 25 cold emails a day per mailbox**, paired with 25 warmup emails a day. Keeping each mailbox's cold volume low, with a steady flow of warmup alongside it, keeps its sending pattern looking normal to inbox providers.

4. **SPF, DKIM and DMARC** published on every domain. See [how to set them up](/blog/how-to-setup-spf-dkim-and-dmarc-for-cold-emails).

5. **Warmup** on every new mailbox before it sends to prospects, and kept running after. More in [Email warmup in 2026](/blog/email-warmup-2026).

6. **Rotation**, so volume spreads across mailboxes and domains, and anything that starts to slip is pulled out before it hurts the rest.

7. **Monitoring** of bounces, complaints and placement, per mailbox and per domain.

None of these steps is hard on its own. The cost is that they never stop. Domains burn out, mailboxes need replacing, servers need watching, and the cycle repeats every month.

## How Sender Pools handles it

Sender Pools comes with the infrastructure built in, so it is not something you have to assemble.

When you sign up, we buy your secondary domains, publish the DNS records, and build mailboxes across Google, Microsoft and our own SMTP servers. We warm them up, rotate sending across them, and monitor every one. When a mailbox or domain starts to slip, we replace it automatically. Your main domain is never used.

You do not pay for domains, mailboxes or warmup. You pay for how many emails you send a day, starting at $50 a month. If you would rather spend your time on targeting and copy than on servers and DNS, the [pricing page](/pricing) shows how it works.
