
SMTP server setup for cold email means one of three things: connecting Google Workspace or Microsoft 365 inboxes to a sequencer, entering SMTP credentials for a private SMTP provider, or building your own mail server. Each has different steps — and in 2026, authentication rules matter more than ports. Google Workspace no longer supports less secure apps, and Microsoft is retiring Basic authentication for SMTP AUTH. This step-by-step guide covers all three paths, the settings for each, and the checklist that keeps a new SMTP setup from burning domains in week one.
SMTP Server Setup: The Short Answer
Path | Effort | Best for |
|---|---|---|
Google Workspace / Microsoft 365 via OAuth | Low | Most cold email teams |
Google / Microsoft via SMTP credentials | Medium | Tools without OAuth support |
Private SMTP provider | Medium | Teams wanting dedicated IPs (providers) |
Your own SMTP server | High | Technical teams with deliverability expertise |
💡 Key Takeaways
Prefer OAuth connections to mainstream inboxes. Build your own SMTP server only if you have the skills and time to manage reputation, security and monitoring.
Path 1: Connect Google Workspace or Microsoft 365 by OAuth
Create inboxes on secondary domains with SPF, DKIM and DMARC.
In your sequencer, add a Google or Microsoft account and sign in with OAuth.
Grant the requested permissions (admins may need to approve the app).
Set daily limits, sending windows and signatures.
Warm or start with pre-warmed inboxes.
Guides: Google Workspace + Smartlead, Microsoft 365 + Smartlead, Microsoft 365 + Lemlist.
Path 2: SMTP Credentials for Google and Microsoft
Provider | SMTP host / port | 2026 authentication notes |
|---|---|---|
Google Workspace | smtp.gmail.com, 465 or 587 | Less secure apps unsupported since May 1, 2025; use OAuth or app passwords (Google guide) |
Microsoft 365 | smtp.office365.com, 587 | Basic auth for SMTP AUTH being retired; Microsoft's January 2026 update set new milestones (timeline) |
Microsoft's updated timeline keeps Basic auth working through December 2026 for existing tenants, makes it unavailable by default for new tenants after that, and says a final removal date will be announced in the second half of 2027. Plan your move to OAuth now. Port details: SMTP ports explained.
Path 3: Private SMTP Provider
Choose a provider and confirm IP model (shared vs dedicated).
Add domains; publish the SPF, DKIM, DMARC and tracking records they provide.
Create mailboxes and copy SMTP/IMAP credentials (host, port, username, password).
Add them to your sequencer as SMTP accounts.
Warm inboxes and, for new dedicated IPs, the IP (IP warming schedule).
Path 4: Build Your Own SMTP Server
Pick hosting that allows outbound port 25 — many clouds block it (Google Cloud example).
Set rDNS/PTR so the IP resolves to your mail hostname.
Install an MTA (for example Postfix) with TLS certificates.
Require authentication for submission on 587/465; never run an open relay.
Configure DKIM signing, SPF and DMARC for each domain.
Set a proper HELO/EHLO hostname matching rDNS.
Check blocklists before sending and register in SNDS (Microsoft SNDS).
Warm the IP gradually and monitor bounces and deferrals.
Is it worth it? See should you self-host an email server and SMTP relay vs SMTP server.
Test Before You Launch
✉️Send test emails
To Gmail and Outlook test accounts; check headers for SPF, DKIM, DMARC pass.
🔍Check DNS
Records resolve correctly (guide).
🧪Run a placement test
Small seed test before campaigns.
📛Check blocklists
IP and domain clean (tools).
📉Start low
Small daily volume per inbox (limits).
Common Setup Errors
Error | Meaning | Fix |
|---|---|---|
535 authentication failed | Wrong credentials or auth method disabled | Use OAuth or app password |
550 5.7.30 (Microsoft) | Basic auth not supported for client submission | Switch to OAuth |
Relay access denied | Not authenticated | Enable SMTP auth in client |
Connection timed out | Port blocked | Try 465/587 |
Full list: SMTP error codes.
Setup Is Step One — Reputation Is Ongoing
After setup, keep these in place:
🔐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).
Skip the Server Setup
LiteMail | Ready-to-connect 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. Bulk OAuth export means inboxes appear in your sequencer without SMTP credentials or server configuration.
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.
Set up in minutes, not days. Get Pre-Warmed Inboxes →
Frequently Asked Questions
How do I set up an SMTP server for cold email?
Most teams connect Google Workspace or Microsoft 365 inboxes to a sequencer by OAuth instead of running their own server.
Can I use Gmail SMTP for cold email?
You can connect Google Workspace inboxes, preferably via OAuth, within Google's sending limits and policies.
Does Google Workspace still allow less secure apps?
No. Google says Workspace accounts no longer support less secure apps from May 1, 2025.
Is Microsoft retiring SMTP AUTH?
Microsoft is retiring Basic authentication for SMTP AUTH; OAuth remains supported. Its January 2026 update set new milestones.
What port should I use for SMTP?
465 or 587 for submission; 25 is for server-to-server delivery.
Should I build my own SMTP server?
Only if you have the expertise to manage security, reputation and monitoring.
Why can't my cloud server send mail?
Many clouds block outbound port 25; use 465/587 to a relay or a provider.
What should I test after setup?
Authentication results in headers, DNS, blocklists and a small placement test.
From Zero to Sending, Without the Server
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: Smartlead Setup · Google Workspace Setup · Microsoft 365 Setup · SDR Infrastructure Setup · Pre-Warmed vs DIY Setup · Google Workspace Inboxes


