How to warm up a fresh SMTP IP: the schedule that keeps you out of the spam folder

A new sending IP has no reputation. Warmup is how it earns one, and the schedule is the whole game.

How to warm up a fresh SMTP IP: the schedule that keeps you out of the spam folder

A new sending IP address has no reputation. That is not a problem to fix later, it is the one thing standing between your campaigns and the inbox. Gmail, Outlook and every major receiving platform make a cold, simple decision about each connection: does this IP have a history of wanted mail, or is it unknown? Unknown gets filtered. Reputation is built by sending mail that people want, gradually, in a way the inbox providers can observe. That process is called warmup, and skipping it is the most reliable way to turn a fresh mail setup into a dead one inside a fortnight.

This is the schedule we work from, written for self-hosted senders running their own SMTP and campaign platform. The numbers are deliberately conservative: going slower costs you two weeks, going faster can cost you the IP.

Week one: tiny, clean, authenticated

Start at 20 to 30 messages per day. Not per campaign. Per IP, total. Every message should go to an address that has asked for your mail and is known to receive it: your own seeded accounts, colleagues, existing opt-in contacts who open their mail. Before the first message leaves, three records must be correct, because no volume schedule survives missing authentication:

SPF, publishing which servers may send for your domain. DKIM, signing every message with at least a 2048-bit key. DMARC, starting at p=none with rua reporting so you receive aggregate reports showing which mail passes and which fails. If you are sending more than a few thousand messages a day to Gmail recipients, authentication is not optional anyway: the large inbox providers require SPF, DKIM and DMARC for bulk senders and expect spam rates to stay well under one percent, with 0.3 percent the published ceiling where deliverability degrades.

Week one exists to let the receiving platforms see a trickle of fully authenticated mail from one consistent IP, with no bounces and no complaints. Nothing else happens in week one.

Week two: double, and watch two numbers

If week one's mail did not bounce and did not land in spam folders at your seeded accounts, raise the daily volume to 60 to 100. Then keep doubling roughly every two or three days while the numbers hold. The two numbers that decide everything are:

Bounce rate. Keep hard bounces under 2 percent at all times. A new IP that starts spraying bounces is telling every filter it is guessing at addresses, which is exactly what spammers do. If a list pushes your bounce rate up, shrink the list, do not slow the sending.

Spam placement. Seed the major providers with accounts you control, or use a monitoring service, and check daily whether your mail is arriving in the inbox or the junk folder. If placement slips for two consecutive days, freeze the volume for three days and let the history stabilise. Volume never fixes placement. Sending more mail nobody wants is the one error the filters never forgive.

Weeks three and four: toward real volume

By week three you should be around 500 to 1,000 messages a day on a healthy IP, still drawing from the most engaged, cleanest segments of your list first. By the end of week four, a few thousand per day is achievable if every metric stayed clean. The pattern matters as much as the total: a consistent daily rhythm builds reputation, weekend bursts after silent weekdays erode it. If your platform schedules campaigns, keep the sending spread across the day rather than dumped in one window.

Full intended volume, if you plan to run serious campaign traffic, is a 30 to 90 day project rather than a month of doubling. There is no shortcut and no software trick that replaces the time element: the mailbox providers weight consistency over time more heavily than any single good week.

Why self-hosted senders rotate pools

A single IP that trips a filter takes your whole operation with it. This is the argument for an SMTP pool rather than one workhorse server: reputation spreads across several addresses, a bad segment only burns one of them, and a blocked IP can be rested and re-warmed while the others carry the traffic. Managed from one panel, a small pool of warmed IPs with per-server bounce limits is more resilient than one perfectly warmed address, because volume spikes and list quality are the things you cannot fully control.

The rest of the stack

Three habits keep a warmed IP warm. First, list hygiene: validate addresses before they enter the list, remove hard bounces immediately, and prune contacts who have not opened or clicked in months, because sending to the disinterested is how complaint rates creep past the ceiling. Second, make unsubscribing work: a visible, one-click unsubscribe honoured promptly is a bulk-sender requirement and, more importantly, it converts a would-be complaint into a clean exit. Third, monitor with the providers' own tools: Google Postmaster Tools for domain and IP reputation against Gmail, Microsoft's sender tools for Outlook, and a Spamhaus check on the IP before you even start, because some freshly leased addresses arrive with old sins attached.

Warmup is boring on purpose. The senders who reach the inbox at volume are not the clever ones, they are the consistent ones: authenticated, gradual, clean-listed, and patient. Set the schedule, watch the two numbers, and do not let an eager campaign talk you into skipping a week.

This guide is part of the ProMailer blog, notes for people running their own email infrastructure. The sign in page takes you into the platform where the warmup schedule becomes daily routine: lead lists, SMTP pools and sending limits in one panel.