Step-by-Step Guide to Configuring SMTP Servers for Cold Email Campaigns

SMTP (Simple Mail Transfer Protocol) is the foundational layer that moves email from your sending tool to a recipient's inbox. Understanding how SMTP works for cold email — and how to configure it correctly — is the difference between campaigns that reach the inbox and ones that get filtered before they arrive.

This guide covers SMTP configuration for cold email specifically: what servers to use, how to connect them to your sequencer, and what settings actually matter for deliverability.

SMTP in Cold Email Context: What You're Actually Configuring

When you send a cold email, here's the exact flow:

1. Your sequencer creates the email message
2. Your sequencer authenticates with your mailbox's SMTP server
3. SMTP server (Google or Microsoft) delivers the email to the recipient's mail server
4. Recipient's mail server accepts or rejects the email based on authentication, reputation, and content

The SMTP server in cold email is not something you host yourself. It's the outgoing mail service provided by Google Workspace (smtp.gmail.com) or Microsoft 365 (smtp.office365.com).

You are configuring access to these servers — authenticating your sequencer to send on behalf of your mailboxes.

Google Workspace SMTP Configuration

Google Workspace is the most common SMTP server for cold email. Here's the complete configuration:

SMTP server settings:

Recommended authentication method: OAuth 2.0

All major sequencers (Instantly, Smartlead, PlusVibe) support OAuth 2.0 authentication with Google Workspace. This is more secure than password-based authentication because:

• No password stored in the sequencer
• Access can be revoked at any time from Google Account
• Follows current security best practice
• Not disrupted by password changes

To connect via OAuth:

1. In your sequencer → Add mailbox → choose Google Workspace / Gmail
2. Authorize via Google Sign-In
3. Done — sequencer can now send on behalf of this mailbox

App Password method (fallback if OAuth has issues):

1. Google Account → Security → App Passwords
2. Select app: "Mail", device: your sequencer
3. Generate 16-character password
4. Use this password in place of your Google password in SMTP settings

Required: Enable SMTP Access in Google Workspace Admin

For Google Workspace accounts, confirm SMTP access is enabled:

1. Google Admin Console → Apps → Google Workspace → Gmail
2. Settings for Gmail → Hosting
3. Ensure "Allows users to automatically forward incoming email to another address" is ON
4. SMTP relay: For client-specific SMTP relay (advanced), set up under Apps → Google Workspace → Gmail → Routing → SMTP relay service

Microsoft 365 SMTP Configuration

Microsoft 365 (formerly Office 365) SMTP is the second major option:

SMTP server settings:

Important Microsoft 365 setup steps:

1. Enable SMTP Auth for each mailbox:

By default, Microsoft 365 disables SMTP AUTH for security. You must enable it per-mailbox:

1. Microsoft 365 Admin Center → Users → Active Users
2. Select the mailbox user → Mail → Manage email apps
3. Toggle "Authenticated SMTP" to On
4. Save

If "Authenticated SMTP" is not enabled, all SMTP connections will fail with authentication errors.

2. Modern Authentication (OAuth) — Preferred:

Microsoft 365 supports OAuth 2.0 for sequencer connections:

1. Register an Azure App in Azure Active Directory (developers only)
2. Or use sequencer-native OAuth if supported (Smartlead and Instantly both support M365 OAuth)
3. Sequencer authenticates via Azure application credentials rather than stored password

3. SMTP AUTH policy verification:

If SMTP AUTH is blocked at tenant level:

1. Microsoft 365 Admin Center → Settings → Mail flow settings
2. Check if SMTP auth is enabled at organization level
3. If disabled globally, IT admin must either enable it globally or use per-mailbox Exception policy

DKIM Integration with SMTP**

SMTP sends your email, but DKIM signs it. The DKIM signing happens server-side when you've properly configured your DKIM keys.

For Google Workspace:

1. Google Admin Console → Apps → Google Workspace → Gmail → Authenticate email
2. Select your sending domain
3. Click "Generate new record"
4. Copy the DKIM public key (TXT record)
5. Add this record to your domain's DNS
6. Wait for DNS propagation (15 min – 48 hrs)
7. Click "Start authentication" in Google Admin

After this, every email sent via smtp.gmail.com from this domain will be DKIM-signed automatically.

For Microsoft 365:

1. Microsoft 365 Defender portal → Email & collaboration policies → DKIM
2. Select your domain
3. Enable DKIM signing
4. Follow the instructions to add the two CNAME records to your DNS
5. Note: Microsoft 365 uses CNAME records (not TXT) for DKIM
6. Wait for DNS propagation, then enable

Verify DKIM is working: Send a test email to a Gmail account, open the email → "Show original" → look for dkim=pass in the Authentication-Results header.

Sequencer SMTP Settings That Impact Deliverability

Connecting your SMTP server to a sequencer is only step one. These sequencer-level settings significantly impact deliverability:

Daily Send Limit**

Setting: Max emails per day per mailbox
Recommended value: 40–50 after warmup; 20–30 during warmup
Why: Per-mailbox daily limits above 50 increase spam risk signals. Even though Google Workspace allows 2,000/day, cold email needs to look like human volume.

Minimum Send Delay Between Emails

Setting: Minimum time between consecutive emails from one mailbox
Recommended value: 90–180 seconds minimum
Why: Sending 50 emails in 50 consecutive seconds is a machine pattern. Sending 50 emails across 2 hours mimics human behavior.

Mailbox Rotation Settings

Setting: How sends are distributed across connected mailboxes
Recommended: Distribute evenly (round-robin) or weighted distribution (more sends to higher-reputation mailboxes)
Why: 15 mailboxes each sending 30/day is healthier than 5 mailboxes sending 100/day.

Send Time Randomization

Setting: Random variation in exact send time within window
Recommended value: ±15–30 minutes random variation
Why: Sending at exactly :00 every 3 minutes is mechanical. Natural human email patterns have variation.

Open Tracking**

Setting: Enable/disable open tracking pixel
Recommendation: Disable for first emails in B2B outreach; enable if reply rate optimization is critical
Why: Open tracking adds an image request that increases URL count in email, which some enterprise spam filters flag. Plain text emails have fewer tracking signals.

SMTP Troubleshooting: Common Errors and Fixes

Error: "Authentication failed" or "535 5.7.8 Error"

Causes:

• Incorrect password (use App Password, not Google account password)
• Less Secure App Access not enabled (legacy — switch to OAuth)
• Microsoft SMTP AUTH not enabled for the mailbox

Fix: Re-authenticate using OAuth. If OAuth unavailable, generate a new App Password and use that.

Error: "535 5.5.1 Authentication Required"

For Microsoft 365: SMTP AUTH not enabled for this mailbox.

Fix: Microsoft 365 Admin → Users → [user] → Mail → Manage email apps → Enable Authenticated SMTP.

Error: "550 5.7.26 Unauthenticated email from domain is not accepted"

Your domain failed DMARC authentication. SPF, DKIM, or both are failing.

Fix:

1. Check SPF record at MXToolbox
2. Verify DKIM is activated (not just configured — must be activated in Google Admin or M365)
3. Check that your sending domain matches your From: address domain exactly

Error: "421 4.7.0 Too many connections" or rate limiting

You're connecting too many simultaneous SMTP sessions.

Fix: Reduce sequencer concurrent connection settings; add delay between batch sends.

Emails delivered but landing in spam

SMTP is working — this is a reputation/content issue, not a configuration issue.

Fix:

1. Run mail-tester.com check to see SpamAssassin scoring
2. Check Google Postmaster domain reputation
3. Verify blacklist status at MXToolbox
4. Review email content for spam trigger words

Key Takeaways

• Cold email SMTP uses Google Workspace (smtp.gmail.com:587) or Microsoft 365 (smtp.office365.com:587) — not self-hosted SMTP servers or transactional relay services
• OAuth 2.0 authentication is preferred over App Passwords for security and reliability
• Microsoft 365 requires SMTP AUTH enabled per-mailbox in Admin Center before any SMTP connections work
• DKIM signing is handled server-side by Google or Microsoft after you configure and activate it via DNS
• Sequencer settings that matter: daily send limit (40–50 max), minimum delay between sends (90+ seconds), mailbox rotation enabled, and send time randomization
• "Authentication failed" errors are usually App Password vs. OAuth confusion or Microsoft SMTP AUTH being disabled

For the complete DNS authentication setup guide, see How to Configure SPF, DKIM & DMARC for Cold Email. For the complete infrastructure stack context, see Essential Components of a Cold Email Infrastructure Stack.