reconcile_reply_capture
Ensure every active mailbox has a working inbound routing rule — sends are gated on it.
›Run reply-capture reconciliation and explain any mailbox that was skipped or errored.
What it does
Walks every active mailbox and makes sure an inbound routing rule exists forwarding replies to the capture worker. It runs hourly on its own; this tool fires the pass on demand.
The reason it exists is that reply capture is a hard gate, not a nice-to-have. A mailbox whose replies cannot be captured is a mailbox whose warmup cannot be verified, and Raechly will not send from it. Running this after any DNS change is the fastest way to clear a stalled mailbox.
The summary distinguishes captured, skipped and errored mailboxes. Skips are usually intentional: a domain whose MX points at Google Workspace cannot route inbound through Cloudflare without hijacking the company mail, so it is correctly left alone.
Errors are different and worth reading individually. A malformed mailbox address, a zone that moved to a different DNS provider, or a revoked API token all surface here rather than failing silently at send time, which is the entire reason the pass runs hourly instead of only at mailbox creation.
Parameters
None. Call it with an empty object — there is nothing to configure.
* required · Maps to POST /api/mailboxes/reconcile-capture
What comes back
Per-pass summary: checked, captured, skipped, errored.
The thing people get wrong
If your apex domain uses Google Workspace or Microsoft 365, enabling routing on it would hijack your real MX. That is why those domains are skipped — warm from a dedicated domain instead.
Use it with
More mailboxes tools
See all 22 tools and the connection string on the MCP server page.