IP Warmup Schedule — Ramping a New Sending Server in AcelleMail

A fresh sending IP has zero reputation. Send 50,000 emails on day one and every major mailbox provider routes you to spam. AcelleMail's Warmup Strategies grow your volume gradually using one of three presets. This guide walks the admin UI plus a realistic ramp plan.

Why a new IP needs ramping

When you provision a new sending IP — a fresh Amazon SES verified domain, a new dedicated IP from your ESP, a brand-new SMTP relay — receiving servers (Gmail, Outlook, Yahoo) have no reputation data on it yet. Their default treatment of an unknown IP is conservative: a brand-new IP suddenly pushing high volume looks like a compromised host, so the mail lands in spam or gets rejected.

Warmup means sending in small batches at first and growing the daily volume gradually over several weeks. Each clean batch teaches the receiving servers "this IP sends legitimate mail at this volume." Once you have earned a baseline reputation, full volume becomes sustainable.

Skip warmup and you can be filtered or blocked for weeks while reputation slowly recovers from a bad first impression.

What AcelleMail gives you

Two controls do the work, and you do not need to write any code or babysit a spreadsheet:

  1. Sending limit (per sending server) — a cap on how many emails AcelleMail hands to that server per unit of time (per minute / hour / day). This is the manual lever.
  2. Warmup Strategies (admin) — a reusable plan that automatically grows the daily volume day over day, with safety rules that pause the ramp if bounce or complaint rates climb. You build it once and attach it to any new server.

The rest of this guide walks both, starting with the per-server limit and ending with the automated strategy.

Before you start

  • The Warmup Strategy feature lives in the admin area, not the customer dashboard — you need operator access to build a strategy and attach it to a server.
  • Have the new sending server already added and tested (use Test connection / send a test email from the server detail before warming it).
  • Warm using your most engaged subscribers first. A segment of people who opened recently produces high open rates, which lifts reputation fastest. Starting with cold or re-engagement segments makes warmup take far longer.

A realistic ramp to aim for

A warmup plan grows from a small starting volume toward your target. The exact numbers depend on your list size and how aggressive you can afford to be, but a typical ramp looks like this:

Week Daily volume range What to watch
Week 1 1,000 → 8,000 Bounce rate under 2%, complaint rate under 0.1%
Week 2 15,000 → 50,000 First reputation check at Gmail Postmaster Tools
Week 3 100,000+ Hold if complaint rate creeps above 0.15%
Week 4 Full volume Warmup complete once signals stay clean

The point of the AcelleMail strategy presets below is that you do not have to manage this table by hand — the strategy generates a per-day plan for you and enforces it. The exact day-by-day curve it produces is shown in the Strategy preview chart when you build the strategy.

Step 1 — Set the per-server sending limit

Open the sending-server detail

In AcelleMail's sidebar, open Sending → Sending servers. The list shows every server connected to this account with its name, quota chip, status, and the date it was created:

Customer sending-server list

Click into the row you want to configure. The detail page is organised into a Connection card (host / credentials) and a Configuration card (server name, defaults, sending limit), with Test connection and a test-send action in the toolbar:

Server detail — Connection + Configuration

In the Configuration card, the Sending limit dropdown caps how many emails AcelleMail will hand to this server per unit of time (per minute / per hour / per day). For the very first day of warmup, set this low — around 1,000 per day. AcelleMail enforces the cap: when the rolling-window counter hits the limit, the queue holds back until the window slides.

If you only have a few servers and a small list, you can warm up by raising this dropdown by hand each day following the ramp table above. For anything larger, use a Warmup Strategy (next step) so the increase happens automatically.

Step 2 — Build a Warmup Strategy (admin)

In the admin sidebar, open Warmup Strategies. This screen lists every reusable warmup plan with its name, preset, warmup length, target volume, risk level, and an Active / Inactive status chip:

Admin Warmup Strategies list

Click Add strategy to open the create form. It is organised in sections.

1. Basic information. Give the strategy a clear internal name (for example Balanced — New Domains) and a short description of when to use it. Then pick a Preset. AcelleMail ships three:

Preset Behaviour Use it for
Cautious Slow ramp, lower daily increment, tighter safety thresholds A brand-new IP with no prior reputation — buys deliverability insurance
Balanced Moderate, steady linear ramp — the recommended default Most warmups; a sensible middle ground
Aggressive Faster growth toward full volume A known-good IP on a new account, or when you are under time pressure

The preset just fills in sensible starting values — you can still customise every field below it.

2. Volume plan. This is where the ramp shape comes from:

  • Starting volume — emails allowed on day 1.
  • Growth strategyLinear (add a fixed amount each period) or Exponential (multiply each period).
  • Daily increment (for linear) or Exponential factor (for exponential — e.g. 1.20 means +20% per step).
  • Quota type — the time unit the growth is counted in (Daily / Hourly / Monthly).
  • Limit type — what ends the warmup: a Per day cap, a cumulative Target volume, or Stop after days.
  • Send on weekends — leave off if your audience does not engage on Saturday/Sunday.

Safety rules. Keep Enable safety checks on and Pause on negative signals on while reputation is still forming. Set Max bounce rate and Max complaint rate to the thresholds at which the strategy should automatically slow down or pause the ramp instead of pushing through bad signals.

As you fill the form, the Strategy preview panel updates live — it shows the Start volume, the Estimated full warmup day count, a Risk level (Low / Medium / High), and a chart of planned daily volume against cumulative volume. Use the preview to sanity-check that the ramp lands where you want before you save.

Click Create strategy. It appears in the list as Active.

Step 3 — Attach the strategy to the new server

Strategies are attached from the admin sending-server detail page (the customer-facing server detail does not expose warmup). Open the server in the admin Sending servers area and find its Warmup section. Use the Select strategy dropdown to pick the strategy you just built, then click Save selection.

The server now follows that plan automatically — the daily allowance grows day over day according to the strategy, and the safety rules hold the ramp if bounce or complaint rates breach your thresholds. You no longer have to raise the Sending limit dropdown by hand.

Step 4 — Watch the warmup statistics

From the server's Warmup section, click View Statistics to open the warmup stats page for that server. It charts the planned ramp against what actually sent, day by day, with Total Sent / Total Failed counts and which warmup day the server is currently on.

Check it daily during the ramp (it takes about five minutes):

  1. Planned vs actual — the actual line should track the planned line. A big gap usually means the queue can't keep up or the source list is smaller than the plan expects.
  2. Failed count — a rising failed count is your early warning. Cross-check the campaign Bounce log to see why (hard vs soft, and the receiving server's reason text).
  3. External reputation — pair this with Gmail Postmaster Tools and Microsoft SNDS. IP reputation there should climb over the warmup; if it stays poor after the first couple of weeks, the problem is content or list quality, not volume.

If you ever need to restart a server's warmup from day one, the Reset Warmup button on the same screen does exactly that (it asks for confirmation first).

What to do if warmup hits a wall

Signal What it means Action
Bounce rate climbing to 4–6% The source segment is probably stale Hold the current daily volume for a few days. Run list verification before resuming.
Bounce rate 8%+ Likely a bad import Pause the warmup. Audit the list source, clean it, then resume.
Complaint rate 0.2%+ Content or subject-line problem, not volume Hold volume and review the campaigns going out during warmup.
Gmail/SNDS reputation still poor after ~2 weeks Engagement is too low Narrow to your most-engaged segment for several days, then re-evaluate.
Daily quota exhausted by mid-morning The sending limit cap is set lower than the day's plan needs Raise the per-server Sending limit, or warm a second server in parallel to share the load.

If you run several new IPs at once, stagger them: warm one fully before introducing the next, a few days apart. That way a problem on one IP does not coincide with low reputation on all of them.

Common UI questions

Question Answer
Where are the warmup presets? Admin → Warmup StrategiesAdd strategy → the Preset dropdown (Cautious / Balanced / Aggressive).
Why is there no warmup option on my customer dashboard? Warmup Strategies are an admin feature. Set them up as an operator, then attach them to servers from the admin sending-server detail.
My ramp didn't increase yesterday If you were raising the Sending limit by hand, you missed a day. Attach a Warmup Strategy so the increment is automatic.
Can I change a preset's numbers? Yes — the preset only fills in starting values. Every field in the Volume plan and Safety rules sections is editable before you save.

What to do after

Related articles

17 comments

8 comments

  1. danrey.dev
    For very low-volume senders (< 5k/month), does warmup even matter? Or just send and let the provider's shared pool absorb the trickle?
    1. admin
      Suppression list import via CSV captures all opt-outs including preference-center ones if you exported with the right field set. The export filter defaults exclude some — check the 'include unsubscribed' checkbox on Mailchimp's export wizard...
    2. admin (edited)
      Yes — strict alignment requires the From: domain to match exactly. Subdomain-level (`bounce.example.com` vs `example.com`) passes relaxed but fails strict. Most operators run relaxed; the rare strict-DMARC setups need explicit subdomain DKIM configuration.
    3. admin (edited)
      good question. the campaign:rerun audit writes to laravel.log only when the audit decides to force-resume — pure noop runs are silent. we'll add an info-level heartbeat in a future acelle release to make it easier to monitor.
    4. admin (edited)
      For your specific case, I'd recommend testing with `--dry-run` first. The behavior under high load isn't 100% deterministic and we want you to see your own pattern before committing
    5. admin (edited)
      Good catch. The bounds (200/32) are hardcoded in the runtime. We've discussed making them configurable; not a ner-term priority but it's tracked
    6. admin (edited)
      We don't recommend that approach in production. It works in dev but has subtle race conditions under concurrent load. Stick with the documented pattern.
  2. tnovak.cz
    confirming the postmaster tools data lag — sometimes 48 hours, sometimes longer. don't make decisions on a single day's data
  3. m.schmidt78
    We hit a Spamhaus listing once. Self-service delisting was actually fast (< 24h) but the reputation recovery took weeks. Not the listing itself that hurt — the user complaints that caused it.
    1. admin
      Worth noting — your config diverges from the recommended one in one place that often bites people. We'll send a separate note with the suggested change. lol
  4. ravi.kumar.del…
    The Postmaster Tools section is gold. Most senders don't even know it exists.
    1. admin
      Appreciate it. If anything in this needs updating, ping us — we revisit articles every few months.
  5. sobrien.kw
    if you're warming a new ip after a known issue, consider seeding with transactional mail first (password resets, order confirmations). higher engagement rate per send than marketing — helps the reputation ramp.
  6. bos.devops
    does engagement-based segmentation help during warmup? e.g. only sending to the most-engaged 20% during week 1?
    1. admin
      Yes, that pattern is supported. The undocumented bit is the order — config:cache MUST come after the migration, not before. Updating the docs to make that explicit. anyway
  7. priya.iyer.ops
    this is the clearest ip warmup schedule i've found. the volume table at the top is what i'm referencing daily
  8. akira.tnk88
    we warmed up a dedicated ip last fall. the 2-week ramp this article describes is on the aggressive side — gmail in particular punishes anything faster than ~3-4 weeks. we did 4 weeks and had a clean ramp...

More in Sending & Deliverability