skip_warmup
Mark a mailbox ready immediately, bypassing the ramp.
›Skip warmup on john@acme.com — it is an established inbox we are migrating in, not a new address.
What it does
Sends a mailbox straight to `ready` without the gradual schedule. There is exactly one situation where this is the right call: the address is genuinely established, with real sending history and real inbound mail, and you are bringing it into Raechly rather than creating it fresh.
On a cold address it is actively harmful. A brand-new domain that starts emailing strangers at volume is the single most reliable way to land in spam, and skipping the ramp removes the only mechanism preventing that.
Kept as an explicit, separately-named tool rather than a flag on warmup precisely so nobody sets it by accident.
Note that it changes the warmup stage only. Reply capture is still required before the mailbox can send, so skipping warmup on a mailbox with no verified inbound path achieves nothing except removing the ramp you would have wanted. The gate is independent of warmup state by design.
Parameters
| Name | Type | Notes |
|---|---|---|
| mailbox_id * | string | From `list_mailboxes`. |
* required · Maps to POST /api/warmup/skip
What comes back
The updated mailbox with warmup stage `ready`.
The thing people get wrong
Only skip on mailboxes with real history. On a fresh domain this converts a slow, boring ramp into a fast, permanent reputation problem.
Use it with
More warmup tools
See all 22 tools and the connection string on the MCP server page.