Warm Up 100 Email Accounts: Cost, Ramp and Setup

To warm up 100 email accounts in BobWork Email Warm-up, a new account pays $180/month: 10 mailboxes are free and 90 are paid extras. Once ramped, 100 mailboxes can send up to 3,000 warm-up emails per day before weekend reduction. This guide gives the setup order, CSV format, ramp maths, pool choice, domain spread, and fleet checks.

If you already have the accounts, open the CSV bulk import guide first and keep this page for the numbers. At 100 mailboxes, small mistakes repeat 100 times. DNS, app passwords, and domain spread matter more than the final upload button.

What does 100 accounts cost?

BobWork Email Warm-up is free for up to 10 mailboxes on new accounts. Every active mailbox above 10 is paid. The price is $5/month per extra mailbox, $3 each from 10 extra, and $2 each from 50 extra.

At exactly 100 mailboxes, a new account pays $180/month. Billing is handled by Stripe, prorated, and you can cancel any time. Extra mailboxes pause without billing.

Early users, meaning accounts created before 27 October 2026, keep 20 free mailboxes for as long as they use the service. Paid prices are unchanged. At 100 mailboxes, early users pay $20 less than new accounts.

The default account limit is 200 mailboxes, so a 100-mailbox fleet does not need a special limit increase. Larger fleets can request a higher limit at info@bobwork.ai.

If you compare vendors, compare the same mailbox count. A one-inbox price can look cheap and become expensive at fleet size. The 50+ inbox warm-up cost breakdown is useful if you are modelling several fleet sizes.

How do you warm up 100 email accounts?

Use CSV upload. In the dashboard, go to Add mailbox → Many mailboxes: upload a CSV. Paste rows or upload a file.

For Gmail, Yahoo, and iCloud, BobWork fills in the mail host settings. For other domains, add the IMAP host when needed. Every row gets the same IMAP and SMTP login test as a single mailbox. Failed rows are listed with the reason. Already-connected rows are skipped, so re-uploading a corrected file is safe.

For Gmail or Google Workspace, use app passwords for the cleanest bulk setup. Google app passwords require 2-Step Verification. Google explains the current process in its app password help page. If an account cannot create app passwords, fix that in Google before you upload the CSV.

Use this CSV shape for Gmail, Yahoo, and iCloud presets:

For other IMAP mailboxes, add the IMAP host when the preset cannot infer it.

Do not start with all 100 rows. Test one mailbox manually. Confirm IMAP and SMTP access. Then upload 5–10 rows. After those pass, upload the full file.

This staged setup prevents one wrong password format, disabled IMAP setting, or provider security rule from creating 100 failures.

For Google Workspace, separate the two connection routes. The recommended bulk route is IMAP with app passwords. One-click Google sign-in also exists, but Google may show an unverified-app notice because BobWork has not completed the CASA audit. Google also caps unverified apps at 100 users. A Workspace admin can mark the app as trusted in the Admin console.

If your fleet is Gmail-only, use the Gmail bulk warm-up guide for account preparation and common login failures.

What ramp should you expect?

Each mailbox ramps on its own schedule. The default ramp starts at 3 emails per day, adds 2 per day, and caps at 30 warm-up emails per day. The cap is editable per mailbox, up to 100.

For 100 mailboxes, multiply the per-mailbox number by 100. Day 1 is 300 planned warm-up emails. Day 7 is 1,500. Day 14 is 2,900. Once every mailbox reaches 30 per day, the fleet can reach 3,000 per day.

Weekends run at 30% volume. A fully ramped 100-mailbox fleet plans up to 3,000 warm-up emails on normal weekdays and about 900 on weekend days.

BobWork spreads sends across 09:00–18:00 in each mailbox’s own time zone. Sending decisions run every 15 minutes with randomness. A pair of mailboxes never writes to each other twice within 3 hours.

The engine also picks peers on a different domain or provider twice as often. That helps when your fleet uses several domains, because it reduces repeated same-domain patterns.

Replies are part of the pattern. About 40% of received warm-up mail gets a reply, and threads end after 3 messages. Messages are plain-text office notes with no links, no images, and first-name greetings.

Do not treat warm-up volume as cold-email volume. During campaigns, keep warm-up at 10–15 per day per mailbox. For real outreach, stay around 30–50 emails per day per mailbox and add mailboxes instead of forcing more volume through one account. The safe cold-email volume guide covers the outreach side.

Which pool should 100 use?

BobWork uses a shared warm-up network by default. Every active mailbox on the service exchanges warm-up emails with other active mailboxes across accounts. One mailbox is enough to start because it can warm with the network.

Private pool is optional. In the dashboard, go to Mailbox pool → Pool mode and switch to Private pool. Then only your account’s mailboxes write to each other. A private pool needs at least two mailboxes.

For 100 mailboxes, private pool is usually the cleaner choice. BobWork recommends private pool for big fleets once you have 50+ mailboxes. At 100, you have enough internal variety to warm without relying on outside accounts.

Private pool does not fix poor domain planning. If all 100 mailboxes sit on one domain, your fleet still has a concentration problem. Pool mode controls who exchanges mail. It does not make one domain behave like many domains.

Every warm-up email is generated by the engine. Users do not write the text, so nobody can push links or spam copy through the network. BobWork identifies warm-up mail with its own hidden header. Real mail is never read, moved, or answered.

Warm-up mail found in Spam is moved to Inbox, marked read, labelled Warm-up, and archived after 24 hours. Only warm-up mail carrying the engine’s marker is touched. For Zoho API senders, a known subject is used.

For the full mechanics, read the private pool versus public network guide. The engine behaviour page lists the current ramp, timing, reply, and rescue rules.

How should you spread domains?

A 100-mailbox fleet should not live on one domain. A typical cold-email setup uses 2–5 mailboxes per domain. That keeps each domain’s sender footprint smaller and prevents one domain problem from affecting every mailbox.

At 100 mailboxes, that usually means many sending domains. The exact number depends on your risk tolerance, sending plan, brand structure, and provider rules. Start with domain capacity, then assign mailboxes.

Every domain needs DNS checked before warm-up and before outreach. SPF, DKIM, and DMARC are the baseline. BobWork checks SPF, DKIM, and DMARC daily via DNS and shows the result per domain.

For Google recipients, use Google’s current email sender guidelines as the primary source. Google says to keep spam rates reported in Postmaster Tools below 0.1% and avoid ever reaching 0.3%.

Yahoo’s sender guidance requires SPF and DKIM, DMARC at least p=none and passing, aligned From domains, one-click unsubscribe for bulk mail, and spam rates under 0.3%. Check Yahoo’s sender best practices before large campaigns.

Use the same DNS standard for every domain, even if one domain sends less mail.

Set DNS before the first warm-up email. Wait for propagation, then confirm the records in the dashboard. The SPF, DKIM and DMARC guide gives a practical record checklist.

New domains need more time. BobWork’s published recommendation is 7 days for an existing domain and 2–3 weeks for a new one. The new domain warm-up plan covers the slower route.

How do you read results?

At 100 mailboxes, averages hide problems. Read results by mailbox and by domain. One domain can be healthy while another drifts into spam. One mailbox can fail login while the rest continue warming.

BobWork’s spam rate is the share of a sender’s warm-up mail that receiving mailboxes found in Spam over 7 days. It is measured directly in the receiving mailbox. BobWork does not use third-party seed lists.

The health score runs from 0 to 100. Healthy is 85 or above. Watch is 60–84. At risk is below 60. Blocked means the login or permission failed.

A mailbox is ready for outbound only when all three conditions are true:

Use this gate per mailbox. Do not start all 100 because the account average looks acceptable. Start with the senders that pass. Leave the others warming.

If a mailbox rises above 5% spam rate, pause it for a few days. Check DNS, login status, provider warnings, and domain load. Do not compensate by pushing more volume through healthy mailboxes on the same domain.

For agencies, label accounts and domains before import. Keep a sheet with client, domain, provider, app-password status, DNS status, pool mode, warm-up start date, and readiness.

If you plan to send campaigns from the same warmed mailboxes, warm-up can keep running while outreach sends. BobWork’s optional Outbound product only lets mailboxes send after they pass the ready gate. It sends from your own warmed mailboxes and costs $2 per 1,000 emails sent. The warm up while sending guide explains the safer pattern.

Do this before upload

Use this checklist before uploading all 100 accounts. It catches the errors that become expensive at fleet size.

A 100-mailbox setup is mostly process. The technical work is simple, but repetition magnifies weak records, bad passwords, and poor domain planning.

Start small, confirm the login path, then upload the full fleet. Use private pool if you want your own 100 mailboxes warming each other. Watch readiness per mailbox, not as one blended number.

BobWork Email Warm-up supports this workflow with CSV bulk upload, shared warm-up network or private pool per account, daily SPF/DKIM/DMARC checks, and a ready-for-outbound gate. You can start at emailwarmup.bobwork.ai with 10 free mailboxes, no card, and add the rest when the fleet is ready.

Frequently asked questions