
Two inboxes on the same domain, with the same copy, can perform very differently because of how each mailbox is set up. Sender names, signatures, security settings, forwarding rules, and sending-tool connections all affect trust and deliverability. This guide shows how to configure mailboxes for cold email: identity, security, the settings that quietly hurt deliverability, connecting to your sending tool, Google Workspace and Microsoft 365 specifics, and a checklist for every new inbox.
Two Inboxes, Same Domain, Very Different Results
💡 TL;DR
Configure mailboxes for cold email with a real sender name and simple address, a profile photo, a short text signature with a postal address, MFA and current recovery details, no auto-forwarding or out-of-office replies, OAuth connection to your sending tool, and daily caps of 25–40 emails. Check SPF, DKIM, and DMARC pass on a test message before launch, and keep every mailbox's settings consistent.
An SDR team sets up two inboxes on the same outreach domain. One belongs to "Jordan Lee," with a photo, a clean signature, and a simple address. The other is "sales3," with no photo, an image-heavy signature with four links, and an auto-forward rule to a shared inbox. Same domain, same copy. The second inbox gets noticeably fewer replies and more of its emails land in spam.
Mailbox configuration is easy to overlook because it feels cosmetic. It isn't. It shapes how recipients judge the sender — and how filters judge the messages.
By the end of this, you'll know exactly how to configure mailboxes for cold email so every inbox starts with the same healthy setup. For the wider stack, see cold email infrastructure setup.
Identity: Name, Address, Photo and Signature
Recipients decide in a second whether a sender looks real. Make it easy.
Setting | Do | Avoid |
|---|---|---|
Display name | A real person's name, e.g. "Jordan Lee" | "Sales Team," "Info," or a company name only |
Address format | firstname@ or firstname.lastname@ | sales3@, noreply@, random strings |
Profile photo | A real, professional photo | No photo, logos, or stock images |
Signature | Name, title, company, website, postal address | Large images, many social icons, multiple links |
Reply-to | The same address that sent the email | A different domain or a shared inbox |
Keep signatures short and mostly text. Each extra link and image adds weight and potential filter signals. Point the website link to your real site, not a tracking link. Include a postal address and a simple opt-out line in either the signature or the email body — see our CAN-SPAM guide.
Security Settings That Protect the Mailbox
A compromised outreach mailbox can send spam under your brand in minutes. Lock each one down.
Turn on multi-factor authentication for every mailbox and admin account.
Set recovery email and phone to company-controlled details, not a former employee's.
Use strong, unique passwords stored in a password manager.
Restrict third-party app access to the sending tools you actually use.
Keep admin rights separate — senders don't need admin access to their own mailbox settings.
Review access monthly and remove leavers the same day.
Full admin access to the Google Workspace or Microsoft 365 account makes all of this possible. With SMTP-only accounts, you can't control most of these settings.
Settings That Quietly Hurt Deliverability
These settings rarely get noticed and often cause trouble.
↪️Auto-forwarding
Forwarding every message to another inbox can confuse reply detection and, depending on setup, cause authentication problems. Use your sending tool's unified inbox instead.
🏖️Out-of-office replies
Auto-replies to every inbound message — including other people's auto-replies — create mail loops and noise. Keep them off on outreach inboxes.
📛Sending from aliases
Sending as an alias on a different domain breaks alignment with your SPF and DKIM. Send from the mailbox's own address.
🖼️Heavy HTML signatures
Large images and many links add weight to every email.
🔗Shared tracking domains
Link tracking on a shared domain ties your reputation to other senders. Use a custom tracking domain, or turn tracking off.
Here's the advice we'd push back on: "Turn on open tracking for every email so you can measure everything." Open tracking adds a tracking pixel to every message and opens are unreliable anyway. Many cold email teams turn it off and measure replies instead — see cold email KPIs.
Connecting to Your Sending Tool
How you connect each mailbox affects both stability and safety.
Connect by OAuth, not passwords. Google has phased out password-only access for third-party apps, and Microsoft has been retiring Basic authentication.
Set daily caps in the tool: 15–20 per inbox at launch, rising to 25–40.
Set the send window and recipient time zones — see the best time to send cold emails.
Confirm reply detection works so sequences stop when someone answers.
Decide where the signature lives — in the mailbox or in the tool — and use one, not both.
Add the inbox to rotation with the rest of its domain's inboxes.
Litemail inboxes support one-click OAuth export to common tools such as Instantly and Smartlead, so connection takes minutes rather than an afternoon.
Google Workspace vs Microsoft 365 Specifics
Most settings apply to both, but where you set them differs.
Task | Google Workspace | Microsoft 365 |
|---|---|---|
Display name and photo | Admin console user profile or the user's account | Microsoft 365 admin center or the user's profile |
Signature | Gmail settings, or set centrally via the Gmail API | Outlook settings, or set centrally with Exchange tools |
Auto-forwarding | Gmail settings; admins can restrict forwarding | Outlook rules; admins can control external forwarding |
Third-party app access | Admin console API controls | Entra ID app consent settings |
DKIM | Admin console (Authenticate email) | Exchange Online PowerShell or Defender portal |
For automating these at scale, see automating Google Workspace mailbox provisioning and Microsoft 365 mailbox provisioning.
Keep Every Mailbox Consistent Over Time
Teams usually configure mailboxes for cold email carefully at launch, then let settings drift. A new SDR changes their signature, someone turns on forwarding during a holiday, a photo gets removed. Months later, inboxes on the same domain look and behave differently.
Set signatures centrally where your platform allows, so individuals can't drift from the standard.
Restrict forwarding at the admin level rather than relying on each sender.
Audit a sample monthly — open five inboxes and compare them to your checklist.
Re-check after people change — when an inbox moves to a new sender, update the name, photo, and signature the same day.
Document the standard in one place everyone can see.
In practice, the best time to configure mailboxes for cold email consistently is before you have many of them. Ten inboxes are easy to audit by hand; a hundred need central settings and a written standard. Build those habits early, while every inbox still fits on one screen.
A Mailbox Configuration Checklist
Use this list to configure mailboxes for cold email the same way every time — run it for every new inbox before its first send.
Real sender name and simple address format
Professional profile photo
Short text signature with company, website, and postal address
MFA on; recovery details company-controlled
Auto-forwarding and out-of-office replies off
Domain's SPF, DKIM, and DMARC passing — confirmed in a test email's headers (see our authentication guide)
Connected to the sending tool by OAuth
Daily cap and send window set; reply detection confirmed
Added to your inventory with owner, platform, and domain
Symptom | Likely mailbox cause | Fix |
|---|---|---|
One inbox underperforms its domain | Missing photo, odd name, heavy signature | Match the configuration of your best inbox |
Replies not detected | Forwarding or a broken connection | Remove forwarding; reconnect by OAuth |
Mail loops with auto-replies | Out-of-office turned on | Turn it off |
Authentication fails on one inbox only | Sending as an alias | Send from the mailbox's own address |
Then keep spam complaints under 0.1%, per Google's email sender guidelines.
Mailboxes that arrive configured — Litemail Google Workspace and Microsoft 365 inboxes come with SPF/DKIM/DMARC pre-configured, full admin access to set identity and security, dedicated US and EU IPs, and one-click OAuth export to your sending tool. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: Cold Email Infrastructure Setup · Set Up Multiple Domains for Cold Email · Monitor Email Infrastructure Health · Google Workspace Pre-Warmed Accounts
Key Takeaways
Configure mailboxes for cold email with a real sender name, simple address, photo, and short text signature.
Turn on MFA, set company-controlled recovery details, and restrict third-party app access.
Turn off auto-forwarding and out-of-office replies, and send only from the mailbox's own address.
Connect by OAuth and set caps of 15–20 at launch, rising to 25–40 per inbox per day.
Confirm SPF, DKIM, and DMARC pass on a test email before any mailbox goes live.
Use one checklist for every inbox so configuration stays consistent.
Frequently Asked Questions
How do I configure mailboxes for cold email?
Give each mailbox a real sender name and simple address, a photo, and a short text signature; secure it with MFA; turn off forwarding and auto-replies; connect it by OAuth with daily caps; and verify authentication.
What sender name should a cold email inbox use?
A real person's name. Generic names like "Sales Team" or addresses like sales3@ look less trustworthy.
Should cold email inboxes have signatures?
Yes — short, mostly text, with name, title, company, website, and postal address. Avoid large images and many links.
Should I turn on auto-forwarding for outreach inboxes?
It's better not to. Use your sending tool's unified inbox for replies instead.
Should I use open tracking on cold emails?
Many teams turn it off. Opens are unreliable, and tracking adds a pixel to every message. Measure replies instead.
How should mailboxes connect to a cold email tool?
By OAuth. Google has phased out password-only access for third-party apps, and Microsoft has been retiring Basic authentication.
Do Litemail mailboxes come configured?
Litemail inboxes come with SPF/DKIM/DMARC pre-configured, full admin access for identity and security settings, dedicated US and EU IPs, and one-click OAuth export.
Start Every Inbox From a Clean Setup
Litemail pre-warmed inboxes come with sending history, SPF/DKIM/DMARC configured, full admin access, dedicated US and EU IPs, and free domain replacement if a domain is ever blacklisted.
Plans from $39/month · Google Workspace and Microsoft 365 · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Pre-Warmed Inboxes · Microsoft 365 Inboxes · Cold Email Spam Trigger Words · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


