Mailbox warmup
Ramp mailbox activity gradually. Cool down when risk appears.
Use configurable warmup profiles, daily and hourly capacity controls, managed warmup sources, health-aware clamping, and visible ramp analytics before increasing campaign volume.
Ramping and steady states·Cooldown and pause controls·Warmup kept separate in analytics
Warmup lifecycle
Warmup state changes with mailbox health.
Choose a profile
Start with a warmup profile or customize the starting count, ramp increment, duration, steady count, total limit, and minimum interval.
Enter ramping
MailSequence begins at a lower daily target and increases activity on the configured cadence.
Spread activity
Warmup sends are scheduled across active hours and bounded by inbox and domain capacity.
Reach steady state
After the ramp window, the inbox targets its configured steady daily count subject to provider, plan, domain, and health clamps.
Cool down on risk
Health signals can reduce or halt warmup instead of continuing blindly through bounce, authentication, or sustained failure problems.
Resume with care
Operators can pause or resume. A recovering inbox returns to ramping or steady state according to its elapsed ramp window.
Warmup sources
Managed recipient pools plus an opt-in mailbox mesh.
Warmup capacity can be allocated across the managed responder pool and eligible peer inboxes. Cross-workspace mesh pairing requires both participating workspaces to opt in; otherwise pairing stays within the workspace or uses available managed seeds.
- Managed responder-pool allocation when available
- Same-workspace peer pairing by default
- Mutual opt-in required for cross-workspace mesh pairing
- Source kill switches and fallback when a source is unavailable
Capacity and analytics
Warmup and campaign sending share the same real capacity.
Hard capacity clamps
Desired warmup volume is reduced by mailbox, provider, plan, domain, and health ceilings before activity is scheduled.
Domain budget sharing
When several warmup inboxes share a domain, MailSequence distributes available capacity across them.
Explicit reporting
Warmup sends and interactions use their own pipeline and appear with clear labels. Campaign reporting excludes them.
FAQ
Frequently asked questions
How quickly does warmup ramp?
The profile controls the starting daily count, increment, interval, ramp duration, and steady target. The standard fallback is a 14-day ramp, but enforced provider, plan, domain, and health limits can reduce the resulting capacity.
Can I pause or resume warmup?
Yes. Operators can pause and resume an inbox. Resume returns it to ramping when it is still inside the ramp window or to steady state after that window.
What can trigger cooldown or pause?
The health system evaluates signals such as bounce behavior, authentication problems, rate-limit errors, sustained failures, and domain-level health. The exact response depends on the signal and configured safety controls.
Does warmup use other customer inboxes?
Same-workspace peer pairing is available by default. Cross-workspace pairing requires both ends to enable it. Managed responder and seed pools can be used when available.
Are all warmup opens and replies observed events?
No. Some interaction signals may be simulated when an observed event or real reply is unavailable. Those states are recorded separately, and warmup activity is not presented as campaign engagement.
Does warmup guarantee inbox placement?
No. Warmup is one part of sender preparation. Authentication, domain history, message relevance, audience quality, volume, provider policy, and recipient behavior still affect delivery.
Ramp gradually before increasing campaign volume.
Configure warmup, watch health and capacity, and move to steady sending when the inbox is ready.