The stack
The best email in the world lands in spam if the plumbing underneath it is wrong. Here is the whole stack — domains, mailboxes, authentication, servers, warmup — what each layer does, and why renting it is not the same as building it.
Six layers
Never send cold email from your primary domain. Burn it once and your invoices and your team's mail go to spam too. Use dedicated look-alike domains (yourcompany-hq.com, getyourcompany.com) that carry the campaign risk on their own.
A brand-new mailbox that sends 50 cold emails on day one is a mailbox mailbox providers distrust. Warmup is six weeks of low, human-looking volume that builds a reputation before the campaign starts. Skip it and nothing else on this list saves you.
The three DNS records that prove your mail is really yours. Since 2024 Google and Yahoo require them for bulk senders; without them, volume gets throttled or junked before a human sees it. This is the one layer you can check right now.
Shared sending platforms put you on IP ranges other people can burn. Owning the SMTP path — your own servers, your own IPs — means your reputation is yours alone, earned and protected rather than borrowed.
Every mailbox has a ceiling, and hitting it hard is a spam signal. The right pattern is a slow climb: a handful a day, rising only as fast as the reputation does. Volume comes from many warmed mailboxes sending a little, never a few sending a lot.
Mailboxes get burned; it is a when, not an if. A serious setup keeps warmed mailboxes in reserve and rotates them in the moment one degrades, so a campaign never pauses waiting for new infrastructure to warm.
Build, do not rent
This is the whole argument. A shared sending platform is fast to start and puts your mail on infrastructure other people can burn. Building the stack — your own domains, your own warmed mailboxes, your own SMTP and servers — means the reputation you spend six weeks earning belongs to you alone, and nobody else’s bad campaign can take it down. That is the half of deliverability no scan can see, and it is the half we build for a living. See exactly how we build it, or check the one layer you can verify today with the free deliverability test.
Questions
The sending stack underneath a cold email campaign: the domains you send from, the mailboxes on them, the authentication records (SPF, DKIM, DMARC), the SMTP path and servers, and the warmup and sending-limit discipline that keeps all of it trusted. Good copy on bad infrastructure is invisible copy — it lands in spam before anyone reads it.
You can, and you should not. Cold email carries reputation risk, and if your primary domain gets flagged, your normal business mail — invoices, contracts, replies to warm leads — degrades with it. Use separate sending domains so the risk is quarantined to infrastructure you can afford to lose.
The records and mailboxes take a day. The part you cannot rush is warmup: about six weeks of gradual sending before a mailbox can safely carry campaign volume. Any setup that promises to send at volume immediately is setting your domains on fire to save you a month.
Tools rent you a slice of shared infrastructure, which is fast and fine to start, but your reputation sits next to everyone else's on the same platform. Building it — your own domains, mailboxes, SMTP and servers — means the reputation is yours alone. We build it for clients for exactly that reason.
Fewer than you think, especially early. A warmed mailbox settles into a modest daily ceiling; pushing past it is a spam signal. Scale comes from running many warmed mailboxes, each sending a little, not from squeezing one mailbox hard.
Infrastructure is one chapter of the cold email playbook. Once the plumbing is right, the sequence and the ask decide the replies.