
To connect pre-warmed inboxes to ReachInbox, Google Workspace accounts use OAuth after you allow ReachInbox's client ID in the Google Admin Console, personal Gmail uses app passwords, and accounts can also be added in bulk by CSV. This 2026 guide walks through each method, the Microsoft 365 route, recommended settings for pre-warmed inboxes, troubleshooting and a first-week ramp plan.
How to Connect Pre-Warmed Inboxes to ReachInbox: The Short Answer
In ReachInbox, go to your email accounts and click Add New.
For Google Workspace, choose the OAuth method and copy ReachInbox's client ID.
In the Google Admin Console, add the client ID under Security → API Controls → App Access Control.
Return to ReachInbox and sign in with each inbox.
Set daily limits and keep warm-up light for the first week.
💡 Key Takeaways
ReachInbox's Google OAuth route only works for Google Workspace accounts, and an admin must allow the app first. Plan admin access before you start.
Before You Start
🔐Authentication is live
SPF, DKIM and DMARC pass for every sending domain (guide).
📬Inbox list ready
Addresses, sender names and which provider each inbox is on.
🧑💼Admin access available
Google Workspace OAuth flows often need an admin to allow the app.
🔁Signatures and profile photos set
Inboxes should look like real people.
📏Daily limits planned
Plan conservative per-inbox caps (safe limits).
Connecting Google Workspace Inboxes to ReachInbox
ReachInbox documents a Google OAuth method for Google Workspace that needs no app password:
Open ReachInbox and the Google Admin Console in two tabs.
In ReachInbox, click Add New, choose Google, confirm IMAP is enabled and select the OAuth method.
Copy the client ID ReachInbox shows.
In the Admin Console, go to Security → API Controls → App Access Control, click Add App and choose OAuth App Name or Client ID.
Paste the client ID, search, select ReachInbox and confirm access.
Back in ReachInbox, log in with each inbox and allow access.
ReachInbox notes that OAuth is for Google Workspace accounts; personal Gmail accounts use app passwords.
Connecting Microsoft 365 Inboxes to ReachInbox
For Microsoft 365 inboxes, use ReachInbox's Microsoft or IMAP/SMTP option as offered in your account and follow its prompts. Some tools require SMTP AUTH to be enabled for the mailbox first; check ReachInbox's current help articles. Microsoft is retiring Basic authentication for SMTP AUTH, so prefer OAuth where available (Microsoft timeline).
Connecting Inboxes in Bulk
ReachInbox lists three ways to add accounts: drag-and-drop CSV, Google OAuth and app passwords. CSV import suits IMAP/SMTP connections; OAuth inboxes are connected individually.
Recommended ReachInbox Settings for Pre-Warmed Inboxes
Setting | Recommendation |
|---|---|
Daily sending limit | Start low and ramp; pre-warmed history isn't a licence to blast |
Warm-up | Keep light warm-up running if your tool offers it |
Sending gaps | Randomised intervals in business hours |
Tracking | Prefer reply tracking; minimise open/click tracking |
Signatures | Plain text, consistent with the sender |
Inbox rotation | Spread campaigns across all connected inboxes |
Troubleshooting Connection Errors
Problem | Likely cause | Fix |
|---|---|---|
OAuth fails for Google | App not allowed in Admin Console | Add ReachInbox client ID in App Access Control |
Personal Gmail won't connect via OAuth | OAuth is for Workspace | Use app password |
Reconnect needed | Token revoked or password changed | Delete and re-add via OAuth |
Microsoft auth error | SMTP AUTH or admin consent | Enable per mailbox or grant consent |
After Connecting: First-Week Plan
Send a test email from each inbox to your own Gmail and Outlook accounts and check headers.
Start with a small first wave on your best-fit, verified list (verification).
Watch bounces and replies per inbox for a few days.
Increase volume gradually; pause any inbox that shows problems.
Monitor Gmail data in Google Postmaster Tools (how to read it).
Deliverability Basics That Still Apply
Pre-warmed inboxes give you a head start, not immunity:
🔐Authenticate every domain
SPF, DKIM and DMARC aligned (authentication guide, Google Workspace setup, Microsoft 365 setup).
🌐Use secondary sending domains
Keep your main domain out of cold outreach (domain setup, domain risks).
🔥Warm or start pre-warmed
Ramp gradually (warm-up guide) or use pre-warmed inboxes (pre-warmed vs fresh).
📉Keep per-inbox volume low
Scale with inboxes, not volume (safe sending limits, inbox sizing).
✅Verify every list
Bounces damage reputation fast (verification tools, list cleaning).
📊Monitor weekly
Spam rate, bounces and blocklists (Postmaster setup, blacklist tools).
Pre-Warmed Inboxes for ReachInbox
LiteMail | Pre-warmed Google and Microsoft inboxes
Fresh from $2.50/inbox
Official Google Workspace and Microsoft 365 inboxes for outreach
LiteMail provisions official Google Workspace and Microsoft 365 inboxes on secondary domains, configures SPF, DKIM and DMARC automatically and lists dedicated US and EU IPs. One-click bulk OAuth export covers Instantly, Smartlead, Lemlist and Pipl.ai; for ReachInbox, connect each inbox through ReachInbox's own Google or Microsoft flow. Pre-warmed Google Workspace and pre-warmed Microsoft 365 are available.
Strengths | Keep in mind |
|
|
Explore pricing, the inbox calculator, infrastructure, bulk inboxes and setups for agencies, SaaS and recruiters. Comparing providers? See Google Workspace vs Microsoft 365.
Start sending sooner with inboxes that already have history. Get Pre-Warmed Inboxes →
Frequently Asked Questions
Can I connect pre-warmed inboxes to ReachInbox?
Yes. Pre-warmed Google Workspace and Microsoft 365 inboxes connect to ReachInbox like any other mailbox of that provider.
Should I keep warm-up running in ReachInbox?
Light ongoing warm-up is common practice; ramp real campaign volume gradually.
How many emails should a pre-warmed inbox send per day?
Start conservatively and increase gradually; many teams plan around a few dozen per inbox per day.
Do I need SPF, DKIM and DMARC before connecting?
Yes — authentication should pass before you send.
Does ReachInbox support Google OAuth?
Yes, for Google Workspace accounts after allowing ReachInbox's client ID in the Admin Console.
Can I bulk import into ReachInbox?
Yes, via CSV for IMAP/SMTP accounts.
Do personal Gmail accounts work with ReachInbox?
Yes, via app passwords.
Does LiteMail export directly to ReachInbox?
LiteMail's one-click export covers Instantly, Smartlead, Lemlist and Pipl.ai; connect inboxes to ReachInbox through its own OAuth flow.
Connect, Ramp and Send With ReachInbox
Official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs.
Automated DNS · Pre-warmed options · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Pre-Warmed Inboxes · Pre-Warmed vs Fresh · How Many Pre-Warmed Inboxes · Safe Sending Limits · Smartlead Setup · Pre-Warmed Google Workspace


