The Deliverability Panic Loop: Change One Thing, Then Wait

If your emails started landing in spam and you've already changed several things, stop changing things. Freeze what you have, write it down, and change one variable at a time, giving each change about two weeks of normal sending before you judge it. Reputation data moves slowly, and if four things change in the same week you can't tell which one helped or which one made it worse.

A pattern shows up again and again in r/sales and r/coldemail threads: placement dips, so the sender rewrites the copy, adds three new domains, swaps the warm-up tool and halves volume, all inside a few days. A week later the numbers are different but nobody knows why, so they change four more things. That's the panic loop.

Why fast changes can't be measured

The systems that judge your mail don't update in real time:

• Gmail. Google's sender guidelines FAQ says Postmaster Tools spam rates and other data points are "calculated and updated daily", and that bulk senders become eligible for mitigation once their spam rate stays "below 0.3% for 7 consecutive days". Its sender contact form asks you to "allow at least 2 weeks between submissions for the changes, if any, to propagate" (both read 2 November 2026).
• Amazon SES. AWS doesn't calculate bounce or complaint rates over a fixed window but over "a representative volume", which differs for each sender (sending review FAQ).
• Spamhaus. Its sender guidelines note that it doesn't reset reputation on request. It changes as your sending changes.

So any test shorter than about two weeks mostly measures noise.

Step 1: freeze and write it down

Before changing anything else:

1. Hold volume flat or lower it. Don't add new sending inboxes or domains this week.
2. Record the current setup. For each domain: SPF, DKIM and DMARC records, sending tool, daily volume per inbox, warm-up settings, tracking on or off, the template in use and where the list came from.
3. Record the baseline numbers. Bounce rate, reply rate, spam complaints (where you can see them) and Postmaster Tools domain reputation for the last two weeks.

This takes an hour and turns the next month into an experiment instead of guessing.

Step 2: change one variable, in this order

Start with what is cheapest to check and most often the cause.

Order	Variable	What to do	What should move
1	The list	Verify it on the verify page, remove invalid and disposable addresses, split catch-all into its own campaign	Bounce rate within days
2	Authentication	Check SPF, DKIM and DMARC on every sending domain with the domain health checker	Pass/fail is immediate; placement over 1-2 weeks
3	Volume and ramp	Lower per-inbox volume, ramp slowly. Google: "Start with a low sending volume to engaged users, and slowly increase the volume over time"	Placement over 2 weeks
4	Content	One template change: remove link tracking, or cut links and images	Replies and placement over 2 weeks
5	Infrastructure	New domains or a different provider, only if 1-4 didn't help	Weeks, and a new domain starts from zero

Make one change, send normally for about two weeks (10 business days if you only send on weekdays), compare against the baseline, then keep it or roll it back. Only then move to the next row.

Why the list goes first

Hard bounces and spam-trap hits come from the list, not the subject line. A verified list that still lands in spam points somewhere else, which narrows the search. If verification takes out a large share of the list, you've probably found the cause. Our post on verified lists that still go to spam covers what to check next when the list is clean.

Things that keep the loop going

• Judging by one seed test. Placement tests send to a few seed inboxes. Our post on conflicting deliverability test results explains why they disagree with each other and with real inboxes.
• Buying new domains every time. Spamhaus says to avoid newly registered domains for at least 30 days, and a fresh domain carries the same list and volume problems with it.
• Warm-up as the fix. Warm-up doesn't make a bad list good. See warm-up done, still landing in spam.
• Reading open rates. Apple Mail Privacy Protection and security scanners inflate opens and clicks. Judge by replies and bounces.

Where SimpleVerifier fits

Verification is step 1: it removes addresses that don't exist, are disposable or point at dead domains, and marks catch-all domains, so you know the list isn't the variable. It can't fix authentication, volume or content. The first 100 checks are free with a Google sign-in on the verify page. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off, and one-time packs of 10,000 checks for $15 never expire. See pricing.