Mailboxes and warmup
Kata sends from your own mailboxes. Each has a status and a daily cap.
When a mailbox sends
A mailbox sends only when all of this is true:
- the mailbox is
active, and so is its domain; - an active campaign uses it (by default, campaigns use every active mailbox);
- it has room under its daily cap today.
Kata never activates a mailbox on its own. Only you, set_mailbox or create_mailbox do, and each change is logged. Kata does pause mailboxes by itself when bounces rise: see Sender health.
Providers
| Provider | How it gets in |
|---|---|
| AgentMail | create_mailbox creates a new inbox, on a verified domain or @agentmail.to. sync_mailboxes imports the inboxes already in your AgentMail account, paused. |
| Zapmail (Google Workspace) | create_mailbox with provider: "zapbox" connects an existing mailbox by its address. |
Connecting a domain
connect_domain takes a domain from your Cloudflare account and connects it to AgentMail: it writes the DNS records, starts verification, then creates the mailboxes you asked for. It stops if the domain already receives email elsewhere, unless you pass force. check_domains finishes the job once the domain is verified; it also runs every 5 minutes.
Use 3 mailboxes per domain, with real first names.
Daily caps
New mailboxes start at 10 emails a day unless you say otherwise. Change it with set_mailbox (one address, or every mailbox of a domain). Limits are per mailbox, not per domain. The planner spreads each mailbox's emails over the rest of the day, with random gaps.
Warmup
New mailboxes should warm up for 2 to 3 weeks before cold sending. Warmup runs in Instantly: paste an Instantly API key in Integrations, then use warmup_enable (20 warmup emails a day by default), warmup_status and warmup_disable. AgentMail mailboxes not yet in Instantly are added on their own; other providers must be connected in Instantly first.
Removing
remove_mailbox and remove_domain remove them from Kata only, not from the provider or your DNS. Their queued emails are cancelled.