Where this lives. Sign in and open /accounts in the app.
What it does
Accounts is where every sending mailbox lives: ones you connect yourself, ones a Google Workspace or Microsoft 365 admin authorizes in bulk, and ones that were provisioned on a domain you own. Each row tracks connection health, warm-up state, daily sending usage, deliverability grade, and DNS and blocklist status. It is also where you pause, disconnect, or repair a mailbox. In the signed-in app, this whole area is part of what emailcampaign.ai calls Campaign Cloud.
Before you start
- Connecting, pausing, disconnecting, or changing caps needs the "manage_provider_connections" permission. Viewing the list only needs a signed-in workspace member.
- For OAuth connections you need to be able to sign in as the mailbox owner, or, for a tenant-wide connection, as the Google Workspace or Microsoft 365 admin.
- Gmail and Outlook consumer addresses cannot be connected over SMTP. They must use OAuth.
Set it up, step by step
- On the Accounts page, click Connect account to add one mailbox you already have.
- Choose an infrastructure path: Platform managed (fastest, a shared OAuth app), Private infrastructure (your own Google Cloud or Azure app, configured under Settings, OAuth infrastructure), or SMTP / IMAP (manual host, port, and app password).
- For Platform or Private, click Gmail / Google Workspace or Outlook / Microsoft 365 to start OAuth consent. For SMTP / IMAP, fill in the mailbox address, SMTP host, port and security, username, and app password. You can also add IMAP so replies and bounces can be read, then click Connect over SMTP.
- To connect many mailboxes at once, click Bulk connect. Pick a provider, then choose Individual OAuth links, where each owner signs in themselves, or Admin tenant connection, where a Google Workspace or Microsoft 365 admin grants consent once and you pick an allowlist of mailboxes to import. Paste the address list, click Validate, then Generate invites or Prepare admin consent.
- Set fleet-wide caps from the health strip. Type a number in the send-per-day field (any value from 1 to 2000, though each mailbox is still capped at what its provider allows) and click Set send/day, or set a shared ramp target and click Set warmup/day.
- To tune one mailbox precisely, open it and use the General tab: Daily limit (capped at that provider's own maximum), Minimum gap between sends in minutes, Random jitter, Timezone, sending Window start and end hours, and Weekdays only.
What you should see
- Each row shows Status, Auth/Token, Warmup, Usage (used of limit, plus the recommended cap and minimum gap), Grade with a numeric health score, Placement percentage, DNS status, Blocklist state, and campaign count.
- A health score of 90 or above grades A, 75 or above grades B, 60 or above grades C, 40 or above grades D, and anything lower grades F. A lower grade also tightens the recommended daily cap automatically.
- A newly connected mailbox often shows "pending invite" until its owner finishes sign-in, then moves to a connected or ready state once its token is active.
- The per-mailbox Daily limit field defaults to 30 if you have not set one; the fleet-wide send-per-day field starts at 200 and the warmup-per-day field starts at 40, and both accept any number you type within their limits.
Common problems
- Reconnect appears when a token has expired or been revoked. It restarts OAuth on the same mailbox row, so tags, client, campaigns, and history all survive, and it refuses a token from a different account. SMTP/IMAP mailboxes cannot use Reconnect; use Verify SMTP instead.
- Disconnect immediately revokes tokens and stops sending, but keeps the mailbox row, tags, campaigns, and history so you can reconnect later. Remove deletes the mailbox from Campaign Cloud and destroys its stored tokens, though send history stays and the real mailbox at Google or Microsoft is untouched.
- Pause (on the mailbox's own page) stops sending and also pauses any warm-up that is running. Resume re-checks the real connection rather than flipping the mailbox straight back to active, so one that is still broken comes back showing its real status, not "ready."
- A retired mailbox, meaning its domain expired, can only be reactivated after the domain is renewed. Reactivate checks the real expiry date before it proceeds.
- The "Create mailboxes" link on this page opens a domain and tenant batch-provisioning console for Microsoft 365, a more advanced operations flow rather than a simple buy button. [VERIFY: whether a self-serve "buy new mailboxes" flow is currently reachable anywhere in the product; a Buy / provision mailboxes drawer exists in the code but is not wired to any visible button today.]
Related
How many inboxes per domain should I use for cold email?
Two is the working number, and three is the ceiling. The domain, not the mailbox, is the unit a provider eventually blocks, so five inboxes on one domain multiplies the loss rather than the throughput. One inbox per domain is also fine and is the safest shape of all.
How many cold emails per day can one mailbox send?
Eight to ten at steady state, with five to fifteen as the hard band. That is total outbound for the mailbox, counting every follow-up and any warm-up still running. It is far below the provider ceilings because those ceilings describe when the provider stops you, not when the provider starts distrusting you.
How many inboxes do I need to send 1,000 cold emails a day?
About a hundred mailboxes across fifty domains, at two mailboxes a domain and ten sends each. For 500 a day, halve it: roughly fifty mailboxes on twenty-five domains.
Should I use Google Workspace or Microsoft 365 for cold email?
Google gives the best placement at Gmail, where most business replies come from, and provisions most simply. Microsoft suits corporate Outlook recipients and contains damage inside a tenant boundary, at about twenty-five users per fresh tenant. Large fleets usually end up mixed, which is also the most resilient answer.
How often should I rotate cold email inboxes?
Rotate on evidence rather than on a calendar. A rising count of provider-level refusals, the 5.7.x family, is the earliest reliable signal that a domain is finished, and it appears weeks before the reply rate falls.
Read next
- Cold email infrastructure explained
- Google Workspace for cold email
- Microsoft 365 mailboxes for cold email
Common questions
How many inboxes per domain should I use for cold email?
Two is the working number, and three is the ceiling. The domain, not the mailbox, is the unit a provider eventually blocks, so five inboxes on one domain multiplies the loss rather than the throughput. One inbox per domain is also fine and is the safest shape of all.
How many cold emails per day can one mailbox send?
Eight to ten at steady state, with five to fifteen as the hard band. That is total outbound for the mailbox, counting every follow-up and any warm-up still running. It is far below the provider ceilings because those ceilings describe when the provider stops you, not when the provider starts distrusting you.
How many inboxes do I need to send 1,000 cold emails a day?
About a hundred mailboxes across fifty domains, at two mailboxes a domain and ten sends each. For 500 a day, halve it: roughly fifty mailboxes on twenty-five domains.
Should I use Google Workspace or Microsoft 365 for cold email?
Google gives the best placement at Gmail, where most business replies come from, and provisions most simply. Microsoft suits corporate Outlook recipients and contains damage inside a tenant boundary, at about twenty-five users per fresh tenant. Large fleets usually end up mixed, which is also the most resilient answer.
How often should I rotate cold email inboxes?
Rotate on evidence rather than on a calendar. A rising count of provider-level refusals, the 5.7.x family, is the earliest reliable signal that a domain is finished, and it appears weeks before the reply rate falls.
Read next
- Cold email infrastructure explained
- Google Workspace for cold email
- Microsoft 365 mailboxes for cold email
Last updated September 19, 2026. Written by the team that operates the platform.