SMTP Warmup: How to Warm Up a Custom SMTP Sender (2026)

What SMTP Warmup Actually Is

When you send email through raw SMTP, you control the entire sending path: the server or relay, the connecting IP, and the authentication records. Mailbox providers — Gmail, Outlook, Yahoo — have never seen that sender before, so they treat it with maximum suspicion. They throttle how many messages they accept per connection, route borderline mail to spam, and watch closely for abuse signals.

SMTP warmup solves this by ramping volume slowly while generating positive signals: low bounce rates, near-zero spam complaints, and genuine engagement (opens, replies, and mail being moved out of the spam folder). Over a few weeks, the provider accumulates enough evidence that your sender is legitimate and begins to trust it — raising acceptance limits and moving your mail to the inbox.

Why Raw SMTP and Dedicated-IP Senders Need It Most

Not every sender faces the same warmup burden. The senders who most need SMTP warmup are:

• Custom SMTP servers (self-hosted Postfix, Exim, or a VPS mail server) — brand-new IP, brand-new domain, zero reputation.
• Dedicated IPs on an ESP— even on SendGrid or Amazon SES, a dedicated IP starts from scratch and must be warmed independently of the provider's shared reputation.
• New accounts on shared-IP relays — SendGrid, Mailgun, Postmark, and SES shared pools carry some inherited IP reputation, but your domain is still new and needs ramping.

The common thread: whenever the combination of your sending IP and your sending domain has no history with the ISPs, you must build that history deliberately. Sending at full volume on day one is the single most reliable way to get throttled or blacklisted.

SMTP Warmup vs Gmail/Outlook OAuth Warmup

This is the distinction most people miss. When you warm up a Gmail or Outlookmailbox, you connect via OAuth and your mail rides on Google's or Microsoft's shared, already-warm IP infrastructure. Those IPs have years of positive reputation. Your warmup work is therefore almost entirely about domain reputation and individual mailbox behavior.

With raw SMTP, you own the whole path. That means warmup also has to cover:

• IP reputation — the connecting IP is yours (dedicated) or shared with other tenants, and it must earn trust.
• Authentication you configure yourself — SPF, DKIM, and DMARC alignment are on you, not handled automatically by a provider.
• Connection and rate limits — ISPs deliberately throttle unknown SMTP sources, so you must respect their acceptance limits while ramping.

For a deeper look at the IP-specific side, see our IP warmup guide. For the mailbox-provider side, see the Google Workspace warmup guide and Outlook warmup guide.

The SMTP Warmup Ramp Schedule

The schedule below is a safe starting point for a new SMTP sender. It assumes authentication is already configured and passing. Shared-IP relays can often move faster; dedicated IPs should move slower. The rule that matters more than the exact numbers: only increase volume when your complaint and bounce rates stay clean.

SPF, DKIM, and DMARC: The Prerequisites

Authentication is not part of warmup — it is the foundation warmup sits on. Before you send a single warmup email over SMTP, confirm all three are configured and passing:

• SPF — a TXT record authorizing your sending IP or relay (e.g. v=spf1 include:sendgrid.net ~all or v=spf1 ip4:YOUR.SERVER.IP ~all for a self-hosted server).
• DKIM — a cryptographic signature on every message, with the public key published in DNS. Most ESPs generate this for you; a self-hosted server signs with its own key.
• DMARC — start at p=none to monitor, then progress to p=quarantine and eventually p=reject once reports are clean.

Warming up a sender that fails authentication is wasted effort — ISPs filter or reject it no matter how careful your ramp is. Our SPF, DKIM & DMARC setup guide walks through the exact records for every provider.

Provider Notes: SendGrid, SES, Mailgun, Postmark, Custom SMTP

The warmup principles are identical across relays, but the mechanics differ:

• SendGrid — offers automated IP warmup on dedicated IPs, but shared-IP senders still need domain warmup. Authenticate your domain in the Sender Authentication panel first.
• Amazon SES — new accounts start in the sandbox with strict limits; SES auto-increases your sending quota as you send clean volume, which is a warmup ramp in itself. Dedicated IPs need manual warmup.
• Mailgun — provides dedicated IP warmup scheduling, but you own domain reputation. Keep bounce and complaint rates low to avoid a paused account.
• Postmark — enforces strict content and bounce policies, so warmup here is as much about list hygiene and transactional-quality content as about volume.
• Custom SMTP (self-hosted) — the hardest case: new IP, new domain, no inherited reputation. You need the full ramp above plus daily blacklist monitoring.

Common SMTP Warmup Mistakes

• Sending at full volume on day one. The fastest way to a Spamhaus listing. Always start low.
• Skipping authentication. Warming up an unauthenticated sender wastes weeks of effort.
• Warming to cold, unengaged lists. Warmup needs positive engagement; blasting a purchased list generates complaints, not trust.
• Inconsistent volume. 50 emails Monday and 5,000 Friday looks like abuse. Spread volume evenly across the week.
• Ignoring bounces. A bounce rate above 2–3% during warmup signals list problems and damages reputation fast.
• Pausing and restarting aggressively. Long pauses decay reputation; you have to re-warm before returning to full volume.

How to Warm an SMTP Sender With a Tool

Hand-scheduling a warmup ramp — and generating real opens, replies, and spam-folder rescues — is tedious and hard to do at the scale ISPs want to see. A warmup tool automates all of it. MailPilot connects over SMTP/IMAP (in addition to Gmail and Outlook OAuth), so it works with SendGrid, Amazon SES, Mailgun, Postmark, and self-hosted servers. It sends, receives, opens, replies to, and rescues your mail from spam across a network of real mailboxes — building the exact positive engagement history ISPs reward.

MailPilot pricing is flat, not per-mailbox: a free tier to start, then Starter at $9/mo, Growth at $25/mo, and Scale at $59/mo for unlimited mailboxes — all with a 14-day free trial. For a custom SMTP sender or a fleet of them, that flat pricing is a meaningful advantage over tools that charge per inbox.