A fresh Google Workspace mailbox looks ready the moment you finish checkout. It isn't. Google ships new accounts with DKIM signing turned off, applies lower send limits while you're still in trial, and judges your outbound almost entirely on domain reputation — because every Workspace message leaves through Google's own shared outbound IPs, not yours. That combination trips up more new senders than bad copy does.
This post is specific to Google Workspace. If you want the general theory behind warm-up, read What Is Email Warmup, and Does It Still Work in 2026?. What follows is what changes when Google is the one doing the sending.
Fix the Workspace setup before you send a single warm-up message
Warm-up on a misconfigured tenant just teaches Gmail and Outlook that your domain sends unauthenticated mail. Every hour of ramping on top of a broken setup is wasted, and some of it is actively harmful. Work through this list before anything else.
- Turn DKIM on manually. Admin console → Apps → Google Workspace → Gmail → Authenticate email. Generate a 2048-bit key, publish the TXT record at google._domainkey, then come back and click Start authentication. Until you click that last button, Google signs your mail with a generic gappssmtp.com key — which authenticates Google, not you, and leaves DMARC unaligned.
- Publish SPF and DMARC. SPF should include _spf.google.com and nothing you don't actually send from. Start DMARC at p=none with an rua address, read a week of reports, then move to quarantine. Step-by-step in SPF, DKIM, and DMARC for Cold Email.
- Use real user seats, not aliases. A send-as alias shares the parent user's daily limit and its reputation. Three aliases on one seat give you zero extra capacity — they just make one mailbox look busier than it is.
- Get off the trial. Google throttles trial accounts to a few hundred messages a day and can hold brand-new domains at reduced limits for the first couple of weeks. Add billing before you start ramping so your limits are stable while you climb.
- Pick your connection method deliberately. OAuth is cleaner than an app password: it survives password changes, doesn't require 2-step gymnastics, and produces a normal-looking authorization event in the audit log. If you must use SMTP, enable 2-step verification first and generate an app password — plain username/password SMTP no longer works on Workspace.
- Finish the human details. Full name, profile photo, a plain-text signature with a real postal address and phone number. It takes ten minutes and it's the cheapest legitimacy signal available to you.
- Verify the domain in Google Postmaster Tools. You won't see data for a while, but you want history accumulating from day one rather than starting the clock when something goes wrong.
What Google's sending limits actually are
Google publishes roughly 2,000 messages per day per user on paid Workspace plans, with substantially lower caps during trial. That's the point at which Gmail hard-blocks you with a 550-5.4.5 error and locks sending for up to 24 hours. It is a ceiling, not a target. A new mailbox that sends 400 cold emails on day three will be sitting in spam folders long before it comes anywhere near Google's number.
The figure that actually governs your fate is Gmail's bulk-sender spam threshold: keep the complaint rate in Postmaster Tools under 0.10% and never let it spike past 0.30%. Do the arithmetic on a small mailbox and you'll see why early volume has to stay low. At 40 emails a day, one complaint puts you at 2.5% for that day. Tiny denominators punish you hard, which is the real reason to ramp slowly — not some superstition about Google watching your first week.
There's a second limit people forget: recipients per message, and external recipients per day. Sending the same message to 20 addresses at once burns through those allowances fast and looks nothing like the one-to-one mail you're trying to imitate. Cold sequences should always be individual sends.
The Workspace-specific difference: IP reputation is out of your hands
When you send through your own SMTP server or a dedicated relay, you're building IP reputation from scratch and every message contributes to it. With Workspace, your mail exits through Google's shared egress pools alongside millions of legitimate business messages. That's both a gift and a trap.
The gift is that you inherit decent baseline IP reputation on day one. This is the main reason Workspace mailboxes routinely out-deliver cheap self-hosted SMTP for the first few months, and why buying a VPS to "control your own IP" is usually a downgrade unless you have real volume and a deliverability engineer.
The trap is that because the IP tells receiving filters nothing distinctive about you, everything else gets weighted more heavily: your domain age and history, DKIM d= alignment, content patterns, link domains, and recipient engagement. There is no IP warm-up to perform. One hundred percent of your warm-up effort goes into domain reputation and per-mailbox engagement history. If your domain is new, that's the constraint — see Should You Use Your Main Domain for Cold Email? for how to think about which domain carries the risk.
A four-week ramp that respects Google's pacing
Assume a new domain that has had DNS in place for at least two weeks and a brand-new Workspace user seat. All numbers are per mailbox, per business day.
| Week | Warm-up messages/day | Cold emails/day | What you're watching |
|---|---|---|---|
| 1 | 4–8 | 0 | SMTP errors, DKIM pass with d=yourdomain in headers |
| 2 | 8–15 | 5–10 | Replies, spam-folder placement in seed tests |
| 3 | 15–20 | 15–25 | Bounce rate under 2%, first Postmaster signals |
| 4 | 15–20 | 25–40 | Complaint rate, reply quality, Primary vs Promotions |
After week four, most Workspace mailboxes settle safely at 30–50 cold emails per day with warm-up continuing in the background. Pushing a single seat toward 100+ is technically possible, but the marginal risk is poor value when the fix — another $6–7 seat — is so cheap. If you need serious volume, spread it across mailboxes rather than stressing one. How Many Mailboxes Do You Need to Send 1,000 Cold Emails a Day? works through that math.
One Workspace-specific nuance: don't ramp five new seats on the same domain simultaneously at full pace. Domain reputation is shared across every seat on it, so five mailboxes making the same mistake in parallel is five times the damage to one asset. Stagger new seats by a week or two. That also gives you a control group — if mailbox one is landing in Primary and mailbox four isn't, the difference is the mailbox, not the domain.
What warm-up traffic should actually look like
The purpose of warm-up is to build a history of messages Google can observe being received, opened by a human, replied to, and occasionally rescued from the wrong folder. The quality of those interactions matters far more than the raw count. Twenty good threads beat two hundred synthetic pings.
- Replies, not just sends. A thread with three genuine back-and-forth messages is worth more than thirty one-shot sends that sit unread.
- Rescue from Spam and Promotions. A warm-up message that lands in Spam and gets marked "not spam," or lands in Promotions and gets dragged to Primary, is the single strongest positive signal you can generate for a new mailbox.
- Labels, stars, archives. Real user actions taken inside the workspace. Note that deleting unread is a negative signal — make sure your warm-up process isn't quietly generating it at scale.
- Mixed recipient providers. Some Gmail, some Microsoft 365, some smaller business domains. A Workspace mailbox that only ever emails other Google addresses tells you nothing about how Outlook will treat you on launch day.
- Plain formatting. No tracking pixels, no image-heavy templates, no link shorteners in warm-up mail. Warm-up should look like the ordinary internal email it's imitating.
Be cautious with third-party warm-up pools that connect thousands of unrelated mailboxes into your Workspace account over IMAP. Google sees unusual login geography and access patterns, and the reciprocal mail is often obviously synthetic: near-identical bodies, sends at suspiciously even intervals, no natural gaps for nights and weekends. Warm-up that happens inside your own workspace with real labeled messages is a safer shape than warm-up that rents you a network of strangers.
Five Workspace mistakes that undo the work
These are the ones that show up repeatedly in accounts that warmed up correctly and still ended up throttled.
- Catch-all routing left enabled. A catch-all on your sending domain collects spam-trap and backscatter mail and inflates your exposure for no benefit. Set unknown addresses to reject.
- Auto-forwarding chains. Forwarding replies out to a personal Gmail breaks SPF alignment on the forwarded hop and can create loops when an autoresponder is involved. Handle replies in one unified inbox instead.
- Reusing the same recovery phone and payment card across a dozen tenants. Google links accounts by these signals. One suspension can cascade across everything you own.
- Sending from an alias while signing with a different domain. DKIM d= must align with the From: domain or DMARC fails, no matter how clean your ramp was.
- Skipping list verification. A 6% bounce rate on a freshly warmed mailbox will get it throttled regardless of how patient you were. Verify before you send — here's why.
How to know the warm-up actually worked
Don't judge it by open rates. Google's image proxy and corporate security scanners fire tracking pixels that never involved a human, so a 70% open rate on a new mailbox may be mostly machines. Use three harder signals instead.
First, seed-mailbox placement tests across Gmail, Outlook, and a couple of real business domains — that tells you where mail actually lands rather than whether a pixel loaded. Second, bounce rate holding under 2% across a few hundred sends. Third, Postmaster Tools domain reputation sitting at Medium or High, though be aware the charts need a few hundred Gmail-bound messages a day before they populate at all, which many single-mailbox senders never reach.
If placement tests come back Primary on Gmail and Inbox on Outlook by week four, and your bounce and complaint numbers are clean, you're out of warm-up and into normal operations. That still means keeping a low background rate of warm-up traffic running indefinitely — reputation decays, and a mailbox that goes quiet for six weeks and then blasts 40 cold emails behaves like a brand-new one.
Where Sendvanta fits
Sendvanta connects Google Workspace mailboxes over OAuth, warms them gradually using real labeled messages inside your own workspace rather than a rented external pool, and scores deliverability health across mailbox, domain, DKIM, and IP — slowing or pausing a mailbox automatically when a risk threshold is crossed, instead of after the damage shows up in your reply rate. Drafts get SpamAssassin-scored before they send, seed-mailbox tests check real inbox placement, and engagement is classified bot-aware so scanner clicks don't get counted as buyer interest. Suppression and one-click unsubscribe are on by default, which matters directly for Gmail's bulk-sender requirements. The free plan is $0 forever — no credit card, 1,000 active leads, 3,000 emails a month, and up to 10 of your own mailboxes — which is enough to run a complete four-week Workspace ramp before you pay anything. Paid plans start at $29/mo. Details at /features.
How long does it take to warm up a Google Workspace mailbox?
Three to four weeks for a new mailbox on a new domain before you send meaningful cold volume. If the domain already has clean sending history and aligned DKIM, a new seat on it can usually be ready in about two weeks.
Do I need to warm up a Workspace mailbox if the domain is already established?
Yes, but a shorter ramp. Domain reputation carries over, so you inherit most of the benefit. The new seat still needs its own engagement history — start at 5–10 cold emails a day and roughly double each week.
Is DKIM enabled by default in Google Workspace?
No. Google signs with a generic gappssmtp.com key until you generate a domain key in the Admin console, publish the TXT record, and click Start authentication. Check a received message's headers for d=yourdomain.com to confirm it's working.
Can I send cold email from a Google Workspace alias instead of paying for another seat?
You can, but it adds no capacity. Aliases share the parent user's daily send limit and reputation. If you need more volume, add a real user seat or a mailbox on a second sending domain.
How many cold emails per day can a warmed Google Workspace mailbox handle?
30–50 per day is the safe operating range for most senders. Google's hard ceiling is far higher, but spam filters — not Google's published limits — are what stop you first.
Setup steps and limits in this post reflect Google Workspace behavior as of February 2026; Google adjusts trial restrictions and sending caps periodically, so confirm current numbers in your Admin console before planning volume.
Ready to send outbound that lands?
Create your free Sendvanta workspace — no credit card required.
Start free