Staying out of spam: the infrastructure decisions that are made before the first email

When a campaign lands in spam, the first instinct is to rewrite the email. It is almost never the email. It is the domain it was sent from, the age of the mailbox, the number of messages that mailbox sent yesterday, and whether the last list was verified. All of those are decided before anyone writes a subject line, and most of them cost a few dollars a mailbox to get right.

Never send cold from your main domain

Your company domain carries your invoices, your customer replies and your password resets. Cold sending damages the reputation of whatever domain it runs on, and reputation damage is not something you can undo by stopping. Cold campaigns run on separate look-alike domains that redirect to the real site, and the real domain stays out of it entirely. This is the single most important decision in the list and it is made once.

The DNS records are not optional and not hard

SPF, DKIM and DMARC are three records that say this server is allowed to send for this domain, here is how to check a signature, and here is what to do with a message that fails. Providers reject or bury mail that lacks them, and Google and Microsoft both tightened their requirements for bulk senders. The reason to pay an infrastructure provider is largely that these get written correctly and automatically, at the moment the domain is created, instead of being someone task for later.

Count the mailboxes, not the volume

Decide how many emails a day you need to send, divide by a conservative number per mailbox, and that is how many mailboxes you buy. At 2.60 to 4.30 dollars a mailbox per month, the estate is cheap. What is expensive is pushing that volume through half as many senders because the sending tool charges per mailbox. The cost model of your sequencer should never be the thing that decides your sending pattern.

Warm up, then ramp slowly

A brand new mailbox sending fifty cold emails on day one is a spam filter training exercise. Warm-up sends and receives real conversations for a few weeks so that the mailbox has a history before it meets a stranger. Then the volume climbs gradually. Nobody wants to hear that the honest answer to when can we start is in three weeks, but the alternative is burning domains faster than you can buy them.

Verify the list, every time

Bounces are the fastest way to lose a domain reputation, and verification costs a fraction of a credit per address at several providers. There is no list clean enough to skip it, including a list you bought from a provider that claims to verify. Run it at the end of the chain, on everything, immediately before the send.

Decide about the dedicated IP, once

A dedicated IP at 170 dollars a month means your reputation is entirely yours, for better and for worse. On low volume that is a bad trade: a shared pool is warmer than anything you can build alone, and a quiet dedicated IP looks suspicious. It becomes right when volume is high and constant enough that the pool no longer explains your sending. Until then, shared.

Rotation, and why one mailbox should never carry a campaign

Sending the same sequence from one address at volume creates a pattern that any filter can read: identical wording, identical timing, one source. Spreading it across an estate with rotation breaks the pattern, and it also limits the damage when one mailbox does get flagged, because the campaign keeps running on the others while that one cools down.

This is why the mailbox count should be driven by deliverability and never by the invoice. At a few dollars a mailbox a month, the estate is the cheapest insurance in the whole operation, and the temptation to save forty dollars by sending twice as much from half as many senders is how domains die.

What infrastructure will not do

It will carry your email to the inbox. It will not make anyone answer it, and it cannot rescue a list that does not match the offer. When the deliverability is right and the replies are still zero, the problem has finally moved to the copy, and that is the only situation where rewriting the email is the correct response.