Keeping Shared IPs Clean

SMTP Zen uses shared delivery IPs so every customer enjoys the same high-quality mail routes. That benefit comes with a catch: damage caused by one sender drags everyone down. This guide lays out how we defend our IP pools and what we expect from you in return.

Signals mailbox providers watch

Mailbox providers score every sending IP and domain. Some of the strongest signals include:

• Patterns: Slow, predictable sending wins; sudden surges look suspicious.
• Engagement: High complaints or hard bounces tank the score quickly.
• Volume consistency: Daily output that whiplashes up or down raises flags.
• Authentication: SPF, DKIM, and DMARC must align, or the rest barely matters.
• Presentation: Broken MIME formatting or “spammy” structure sets off alarms.

Our shared approach only works when these signals stay quiet and boring.

Why we obsess over this

Before SMTP Zen, we watched real companies with legitimate use cases get blocked by Gmail, Microsoft, Yahoo, and friends simply because their host didn’t defend its IPs. We built this platform to do better. Deliverability is not a side effect - it is the product - so investing in IP hygiene is non-negotiable.

How we keep IPs healthy

Multiple layers catch risky traffic long before it reaches outside networks.

Guardrails at the start

• Reject deliveries aimed at clearly invalid or unverified recipients.
• Stop bulk uploads that do not pass verification checks.
• Watch for suspicious fingerprints or spam signatures via open-source tooling.
• Throttle automated bursts when needed to keep reputation stable.

Automated outbound scanning

Every message runs through tools such as SpamAssassin and Rspamd, plus custom logic. They focus on formatting, headers, and other technical cues - not the meaning of your text.

Privacy note: Filtering is automated. No one reads your email contents; the scanners only flag patterns known to correlate with spam or malware.

Adaptive relay routing

We operate multiple relay pools. If an IP shows even mild trouble, it is pulled for inspection, traffic shifts to clean IPs, and we only reintroduce the suspect IP after remediation.

Backup relay network

If a destination drags its feet, we automatically retry the message through alternate relay pools with different IPs and pacing. Retries continue for up to 24 hours before you receive a bounce.

Your part of the bargain

Healthy IPs are a team sport.

Do:

• Keep recipient lists clean and genuinely opt-in.
• Honor unsubscribes right away.
• Send only what people explicitly signed up to receive.
• Maintain SPF, DKIM, and DMARC.
• Investigate bounce spikes and fix root causes.

Don’t:

• Buy, rent, or scrape addresses.
• Message people who never opted in.
• Ignore rising complaint or bounce rates.
• Blast bulk mail without proper list hygiene.
• Use bait-and-switch subjects or misleading content.

Troubleshooting checklist

1. Have the recipient scan their spam/junk folder - sometimes filters misfire even with good IPs.
2. Double-check SPF, DKIM, and DMARC alignment in your DNS.
3. Run a message through mail-tester.com to see an unbiased score.
4. Re-evaluate the copy; certain keywords or layouts trip filters regardless of sender reputation.
5. Factor in the recipient’s provider - some inboxes run unusually strict policies.

Our promise

We will keep rotating out problem IPs, maintain clean infrastructure, and be transparent about policies that guard deliverability. In return, we ask that you send only high-quality, consented mail. Together we can keep SMTP Zen’s reputation exceptional even as global filtering tightens.