Why Your IP Reputation Matters More Than Your Copy

There is a persistent myth in cold-email circles that "your copy is what decides whether you hit the inbox." It is wrong. It is wrong in a way that costs teams months of spinning in circles, rewriting subject lines, A/B testing openers, while the real problem sits one level below in the SMTP logs.

The truth is simpler and less flattering: the remote MTA decides whether you make it to the inbox, and it decides mostly on infrastructure signals, not on the text of your message. Your copy matters for replies, not placement.

What a receiving MTA actually scores

When an email arrives at a major inbox provider — Google, Microsoft, Apple, Yahoo, Fastmail — it runs through a filtering pipeline that evaluates, in rough order of weight:

1. The sending IP's historical reputation (days and weeks of sending behavior from that IP).
2. Whether the sending domain passes SPF, DKIM, and DMARC alignment checks.
3. The sending domain's own reputation, independent of the IP.
4. TLS quality (STARTTLS offered, cert valid, optional DANE match).
5. Engagement signals from recipients who share an inbox provider with yours (replies, not-spam clicks, explicit adds to contacts).
6. The content itself — header patterns, link reputation, suspicious keyword density, attachments.

Content is the last item on that list. Items 1-5 are all infrastructure. If any of them fails hard, the content score never gets a chance to matter.

The 80/20 breakdown is generous to content

Say you have beautiful cold email copy. Personalized openers, a clear offer, one CTA, clean formatting. On a dedicated IP with 30 days of history at 40 emails per day, DKIM signing correctly, DMARC aligned, DANE enabled, and under 1% bounce rate — that copy will hit the inbox 85-92% of the time at Google, 75-85% at Microsoft. Normal, good numbers.

Now take the exact same copy and send it from an IP with no history, through a shared pool where another tenant has been flagged by Spamhaus in the last 24 hours. Inbox placement drops to 30-45% at Google and 10-20% at Microsoft. The copy is identical. The reader never sees it.

That's the shape of the 80/20. It is not "copy matters a little less". It is "copy cannot save you if infrastructure is wrong."

Why dedicated IPs win here

Three reasons:

1. Your reputation is a function of your behavior only

On a dedicated IP you control the signal. You send at a sane rate, maintain low bounce, respond to complaints — and the IP's score climbs steadily. Nothing another tenant does can move it. On a shared IP, you are averaged with everyone else on the pool. One blast campaign from a noisy neighbor and your score drops because of their behavior.

2. Reputation is slow to build and fast to lose

Major inbox providers use rolling windows of 30-90 days for IP reputation. Building clean reputation takes the full warm-up window. Losing it takes a single bad day. On a dedicated IP, you control the bad days. On a shared one, you do not.

3. Monitoring is meaningful

With your own IP you can check it against blocklists and get actionable answers. You see "this IP is on SORBS" and you know exactly who is responsible for fixing it. On a shared IP, the blocklist entry is against the pool, and the provider handles it on their own timeline — which may or may not align with yours.

What content does still decide

Once infrastructure is working, content matters for replies, not placement. And replies matter — they are the single strongest positive engagement signal a receiving MTA can use. A reply says "this inbox wanted this email." Over time, consistent reply rates pull your IP reputation upward.

So the work order is:

1. Get infrastructure right (IP, DNS, authentication, warm-up).
2. Write copy that gets replies.
3. Let the two compound over weeks.

Not:

1. Write A/B test #43 on your subject line.
2. Wonder why deliverability is unchanged.
3. Write A/B test #44.

How to know which layer is your problem

This is the single most useful diagnostic question in cold email:

Are your emails landing in spam, or are they not being delivered at all?

If emails are delivered and landing in spam: likely content + domain reputation. Rewrite the copy, lower keyword density, check links.

If emails are failing to deliver (bounces, 421 deferrals, 550 rejections): infrastructure. IP reputation, DNS records, SPF/DKIM/DMARC alignment. Copy cannot fix this.

Most teams guess at the first without checking the SMTP logs for the second. This is why so many cold email programs spend months stuck — they are rewriting copy for an infrastructure problem.

The takeaway

Infrastructure is upstream of content. A dedicated IP with clean DNS and well-configured authentication gives your copy the chance to work. A shared IP on a pool with compromised reputation takes that chance away, no matter how good the copy is.

If you want to know which layer your deliverability problem lives at, open the SMTP logs before you open the copy editor.