Stop landing in spam.
Start landing revenue.

The problem with blunt suppression

Open rates are a broken metric since Apple Mail Privacy Protection started pre-fetching pixels. A contact with zero recorded opens might open every email on iPhone and never register. Suppress by opens alone and you're cutting real customers.

The correct approach segments by address quality first, then by engagement signals you can trust — clicks, purchases, site visits, and replies. Bounces and complaints stay the priority. Open rate comes last.

Step 1: Validate every address for deliverability risk

Before you touch engagement data, run the full list through Bouncer. Validation separates contacts into categories that have nothing to do with engagement:

• Valid — the address exists and will accept mail. Keep sending.
• Invalid — hard-bounce guaranteed. Suppress immediately, no re-engagement attempt.
• Risky — catch-all domains, disposable addresses, role-based inboxes (info@, support@). Treat with caution: move to low-frequency sends and monitor bounce rates closely.
• Unknown — the server didn't respond. Queue for a second validation pass before deciding.

For a 100,000-contact list with typical decay, expect 15,000–25,000 addresses to come back invalid or risky. Remove the invalids before your next send. The risky segment needs a separate strategy, not deletion.

Step 2: Segment what remains by engagement signal

After validation, sort the valid addresses into four engagement tiers based on the most reliable signals available to you:

• Tier 1 — Active: Clicked any email in the last 60 days, or made a purchase in the last 90 days. Send every campaign.
• Tier 2 — Warm: Clicked in the last 180 days, or visited your site from an email link. Send most campaigns — skip the lowest-priority broadcast sends.
• Tier 3 — Cold: No click or purchase in 180+ days but address validated as deliverable. Send a targeted re-engagement sequence before any promotional content.
• Tier 4 — Unresponsive: No signal of any kind in 365+ days. Run one final re-engagement attempt, then suppress on no response.

Step 3: Run a re-engagement sequence before suppressing cold contacts

Cold and unresponsive contacts represent real people who opted in. Some went quiet because the timing was wrong, not because they're gone. A three-email re-engagement sequence recovers a meaningful percentage before you suppress the rest.

Email 1 (Day 1): A plain-text message from a real name, not the brand. Subject line: "Still want to hear from us?" No images, no heavy HTML. Ask directly whether they want to stay on the list. Give them a clear yes link and a clear unsubscribe.

Email 2 (Day 5): Your strongest recent piece of content or your best offer. Not a discount necessarily — your most useful thing. Subject: "In case you missed this." This tests whether the content itself can re-engage them.

Email 3 (Day 10): The goodbye email. "We're removing you from our list on [date] unless you'd like to stay." This generates clicks from people who want to remain — and that engagement signal improves your deliverability, not just your list quality.

Anyone who clicks any link in any of the three emails moves back to Tier 2. Everyone else gets suppressed, not deleted. Keep a record — you may be able to re-permission them through other channels later.

Step 4: Prevent decay with real-time validation at signup

Cleaning a dirty list solves yesterday's problem. The real win is stopping bad addresses from entering in the first place. Bouncer's API validates addresses at the point of form submission — before the contact lands in your ESP. A bad address gets rejected with a user-facing message asking for correction, rather than silently entering your list and accumulating until your next cleaning cycle.

The API call adds roughly 200–400ms to form submission time — imperceptible to users, and a fraction of the cost of a bounce-driven reputation hit months later.

What to expect after cleaning

Open rates and click rates will rise — not because more people opened, but because you removed the dead weight dragging your denominators down. Bounce rate will drop sharply. Complaint rate will drop if your risky segment was generating them. Deliverability scores typically improve within two to three send cycles as providers see your cleaner engagement ratios.

List size will shrink. Revenue per email will increase. That's the trade, and it's worth it every time.

How IP reputation actually works

Every email leaves a server from a specific IP address. Mailbox providers — Gmail, Outlook, Yahoo — track the sending behavior of that IP over time. High bounce rates, complaint rates, or spam trap hits from that IP build negative reputation. Consistent, engaged sends build positive reputation. That reputation score influences whether mail from that IP reaches the inbox.

On a shared IP, your reputation is pooled with every other sender using the same address. On a dedicated IP, your sending history is yours alone — for better or worse.

When shared IPs make sense

Shared IP pools work well under specific conditions. Reputable providers like SMTP2GO actively manage their shared pools — monitoring complaint rates, removing abusive senders quickly, and maintaining warm, established pool IPs with long positive histories. For senders in the right range, a managed shared pool outperforms a cold dedicated IP.

• Send volume under 50,000 emails/month. Low-volume senders on a dedicated IP have inconsistent sending patterns — sporadic sends don't build reputation as effectively as steady shared-pool traffic.
• Send frequency of less than daily. A dedicated IP that sends weekly looks suspicious to providers. Shared pools maintain consistent daily volume that keeps reputation scores warm.
• List quality is high. Clean lists on a managed shared pool rarely encounter problems caused by other senders on the pool.
• No budget for dedicated infrastructure. Dedicated IPs add $10–$50/month per IP at most providers, plus require managed warmup.

When dedicated IPs are worth it

Dedicated IPs give you full control over your sending reputation. No other sender's bad behavior touches you. The tradeoff is that you own the warmup process from zero — and if your list is dirty or your content is flagged, there's no pool average to cushion the impact.

• Sending more than 100,000 emails/month. At this volume, the reputation signals from your sends outweigh pool-wide signals, and you want them attributed to your IP alone.
• Daily or near-daily send frequency. Consistent volume maintains dedicated IP reputation; infrequent sends do not.
• Separating transactional from marketing sends. Running these on separate IPs — or separate dedicated pools — protects time-sensitive transactional mail from any reputation spillover from promotional campaigns.
• Compliance or enterprise requirements. Some industries require that only authorized IPs send on behalf of a domain.

Separating transactional from marketing traffic

This is the most underrated infrastructure decision most growing businesses make too late. Transactional emails — order confirmations, shipping notices, password resets — have 60–80% open rates and near-zero complaint rates. Marketing campaigns generate more complaints by nature.

Mix them on the same IP and a bad promotional campaign can delay your order confirmation emails. Customers who can't get their password reset don't check the promotions folder — they contact support or churn.

Ahasend and SMTP2GO both support routing transactional and marketing traffic through separate pools. Set it up from the start — retrofitting stream separation later, once your transactional mail has accumulated reputation on a shared pool, is painful.

The warmup requirement for dedicated IPs

A new dedicated IP has zero reputation. Send at full volume from day one and providers treat it identically to a spammer's throwaway address. Every dedicated IP requires a warmup ramp — typically four to eight weeks depending on your target volume.

Run Warmy on any new dedicated IP from day one. Its 24-hour warmup sends build reputation continuously, not just during your real-list send windows. Run Folderly alongside for weekly placement tests — a dedicated IP that's warming successfully will show improving inbox placement week over week. One that's struggling will show the problem before it costs you a campaign.

The practical recommendation by volume

Diagnose before you fix anything

Reputation damage has at least four distinct causes: dirty list, poor authentication, spam-triggering content, or sending pattern problems. The recovery steps differ by cause. Treating the wrong root cause wastes time and often makes things worse — sending re-engagement emails to fix a content filter problem, for example, increases volume to an audience already generating complaints.

Before cutting volume or changing anything, pull these data points:

• Gmail Postmaster Tools: Domain and IP reputation rating (Good / Medium / Low / Bad), spam rate over the last 30 days, and authentication failure rate
• Your ESP's bounce report: Hard bounce percentage by domain (Gmail bounces vs. Outlook bounces vs. Yahoo bounces tell different stories)
• Complaint rate by campaign: Which specific send triggered the spike, not just the aggregate
• Blacklist check: Run your sending IP and domain through MXToolbox or Folderly's blacklist monitor to check against 100+ RBLs

Run a Folderly inbox placement test on your current template and sending domain. This tells you exactly where your mail is landing — inbox, spam, or missing — across Gmail, Outlook, Yahoo, and iCloud simultaneously. The provider breakdown is critical: a Gmail-specific problem (authentication-related) needs different treatment than a Yahoo-specific problem (content-related) or a universal spam placement (reputation-related).

Days 1–3: Stop the bleeding

Cut send volume to your top 10% most engaged contacts only — people who clicked something in the last 30 days. Do not send to anyone else until your reputation starts recovering. This feels drastic. It's necessary. Every send to a disengaged or unvalidated address during a reputation crisis actively worsens the score you're trying to recover.

If your complaint rate is above 0.1% in Gmail Postmaster Tools, pause all sends for 48 hours. Not reduce — pause. Let the complaint rate data age out of the window before restarting.

During the pause, validate your entire sending list with Bouncer. Remove every invalid, high-risk, and catch-all address. If your bounce rate was above 3% before the crisis, this step alone will prevent the problem from recurring.

Days 4–10: Fix the root cause

If the problem is authentication: Fix SPF, DKIM, and DMARC immediately. Verify with MXToolbox after each change. DMARC failures generate automatic aggregate reports sent to your reporting address — read them. They show which servers are sending mail claiming to be your domain.

If the problem is content: Rebuild your template from scratch in a clean editor like Stripo. Do not edit the existing template — content filter patterns can persist even after you change the text if the HTML structure is the same. Run the new template through Stripo's spam checker before sending a single email.

If you're on a blacklist: Identify which RBL listed you and follow their removal process. Most major blacklists have self-service removal for first-time listings if you can demonstrate you've fixed the underlying problem. Folderly's monitoring will confirm removal once it clears.

If the problem is sending pattern: You sent too fast, too irregularly, or to too many cold addresses. The fix is the warmup ramp — treating your domain as if it were new and rebuilding volume gradually.

Days 11–20: Rebuild with a controlled ramp

Start Warmy on your sending domain and IP immediately. Its 24-hour engagement sends generate positive reputation signals continuously — opens, replies, inbox interactions — that counterbalance the negative history you're recovering from. This is not optional during reputation repair. The warmup tool is doing work that your real sends can't do at the restricted volumes you're operating at during recovery.

Resume real sends to your top engagement tier only (clicked last 30 days). Watch your Gmail Postmaster Tools domain reputation daily. As it moves from Low to Medium, expand to your 60-day click segment. As it reaches Good, expand further.

Run Folderly placement tests after each send expansion. Inbox placement should improve week over week. If it stalls or drops, you've expanded too fast — contract back one tier and hold for another week.

Days 21–30: Sustain and monitor

By day 21, most senders see domain reputation back to Medium or Good if the root cause was correctly identified and fixed. Full recovery to pre-crisis levels typically takes 30–45 days of consistent clean sending.

Keep Warmy running at maintenance volume. Keep Folderly monitoring active — reputation problems often resurface when senders relax monitoring after recovery. Set up Gmail Postmaster Tools alerts for any reputation drop below Good so you catch problems within 24 hours instead of three weeks.

What not to do during recovery

• Do not increase volume to compensate for reduced delivery. More sends to a damaged domain make it worse.
• Do not switch to a new domain to escape the problem. Providers watch for this pattern — a new domain sending at the same volumes with the same content history gets treated as a serial spammer.
• Do not send re-engagement campaigns to your whole list. You don't have the reputation budget for it. Save re-engagement for after recovery is complete.
• Do not contact your ESP and ask them to "fix" it. ESPs can't override provider reputation scoring on your behalf. They can advise; they cannot intervene.