---
title: "Warming up a new domain"
description: "Ramp volume on a new sending domain over the first weeks, and how the daily cap and account review interact with that ramp."
---

> **For AI agents:** the complete documentation index is at [llms.txt](/docs/llms.txt). Append `.md` to any page URL for its markdown version.

Receivers judge a new sending domain by its recent history, and a domain with no history risks rate limiting or reputation damage at volumes that would be fine for an established one. Volume ramps rather than jumps.

## Mailfully's side

Every new account starts in Mailfully's warm-up pool, where the IPs already carry standing rather than starting cold, and graduates to the shared pool once the account has a verified domain, account age, sustained volume, and rates well inside the ceilings on Policies. See [IP pools](/concepts/ip-pools) for how that assignment and graduation actually work.

## Your side: the ramp

| Week | Daily volume, as a starting point |
|---|---|
| 1 | 50-100 |
| 2 | 200-500 |
| 3 | 500-1,500 |
| 4 | 1,500-5,000 |

The right numbers shift with your own list, your content, and the receivers you send to. On the free plan the 200-recipient daily cap (see below) lets you clear week 1 comfortably, then stalls you right at the start of week 2 however flat your rates stay.

The table is only a floor; the rule underneath it governs the ramp. Raise volume only while your bounce and complaint rates stay flat. If either one rises from one week to the next, hold at the current volume until it settles back down before increasing again.

## Send your best traffic first

Send to your most recently active recipients first, ahead of anyone who's gone quiet. Early engagement (opens and clicks in the first sends) is what establishes the domain's reputation; a warm-up batch full of stale addresses produces bounces and silence instead of the signal a new domain needs.

## The ceilings you will meet

Two different kinds of ceiling show up during a ramp, and confusing them wastes time chasing the wrong fix.

**Volume ceilings** cap how much you can send and clear on their own. The free plan's daily cap and the new-account review ceiling, returning `429 account_under_review`, are both covered in [Rate limits and quotas](/concepts/rate-limits); the retry behavior for each is documented there rather than repeated here. See [Quotas and plan limits](/concepts/quotas-and-plan-limits) for what each plan includes before those ceilings fire.

**Quality ceilings** don't clear on their own: the 0.07% complaint-rate and 4% hard-bounce-rate thresholds from [Policies](/concepts/policies) suspend the account rather than throttling it. A ramp that raises volume while either metric climbs is the failure this page is written to avoid, which is why the ramp rule above is tied to those two numbers rather than to the calendar.

## What to watch

Watch your rates as you ramp, not just your volume. See [Analytics](/guides/analytics) for the counters to pull, and [Why emails go to spam](/deliverability/why-emails-go-to-spam) for what degrades them in the first place.
