How to Connect Email Inboxes to Smartlead (And Keep Them Healthy Long-Term)
Most teams get the SMTP connection right and assume the job is done. It is not. The inboxes that look fine on setup day are often the ones quietly burning weeks later while your Smartlead campaigns keep sending into the void.
This guide covers how to connect email inboxes to Smartlead correctly, what the common failure points look like, and how to set up a monitoring layer so you catch inbox problems before they damage your campaign results.
Quick Answer
To connect email inboxes to Smartlead, you need a provisioned sending domain, properly configured DNS records (SPF, DKIM, DMARC), and SMTP credentials added to your Smartlead sender account. Google Workspace and Microsoft Azure inboxes are both supported. The connection itself takes minutes. The part most teams skip is monitoring those inboxes after they go live.
What You Need Before You Start
Before you touch Smartlead, make sure your inbox infrastructure is actually ready. Rushing the connection without completing DNS setup is one of the most common reasons cold email campaigns underperform from day one.
Provisioned sending domains
Use aged or freshly registered domains that are separate from your primary business domain. Never send cold outreach from your main domain. Each sending domain should host a small number of inboxes, typically two to four, to keep sending volume per inbox manageable.
DNS records configured correctly
Every sending domain needs three records in place before you connect it to any sequencer:
SPF tells receiving mail servers which IP addresses are authorized to send from your domain. For Google Workspace, you will typically add a TXT record pointing to Google’s SPF include. For Microsoft, the include points to Microsoft’s servers.
DKIM is a cryptographic signature that proves the email was actually sent by the authorized sender. Google Workspace generates a DKIM key in the Admin Console. You copy it into your DNS settings as a TXT record. Microsoft handles this through the Azure or Microsoft 365 admin panel.
DMARC sets a policy for how receiving servers should handle mail that fails SPF or DKIM. A basic DMARC record in monitoring mode (p=none) is the minimum. For mature sending infrastructure, you will want to move toward enforcement over time.
If any of these records are missing or misconfigured, your emails will either land in spam or get rejected outright. Verify your DNS settings with a tool like MXToolbox before connecting inboxes to Smartlead.
Warmed inboxes
Do not connect fresh inboxes directly to cold campaigns. New inboxes need a warmup period, typically two to four weeks, where they send low-volume conversational emails to build sender reputation. Connecting an unwarmed inbox to a high-volume sequence is a reliable way to get it flagged quickly.
How to Connect Email Inboxes to Smartlead
Once your domains are provisioned, DNS records are verified, and inboxes have been warmed, the connection process in Smartlead is straightforward.
Step 1: Log in to Smartlead and open Email Accounts
From the Smartlead dashboard, navigate to the Email Accounts section. This is where all your connected senders live.
Step 2: Add a new email account
Click “Add Account” and select the inbox type. Smartlead supports SMTP/IMAP connections, which covers both Google Workspace and Microsoft inboxes.
Step 3: Enter your SMTP and IMAP credentials
For Google Workspace inboxes:
- SMTP host: smtp.gmail.com
- SMTP port: 587 (TLS) or 465 (SSL)
- IMAP host: imap.gmail.com
- IMAP port: 993
Note: Google requires you to enable 2-step verification and generate an App Password for each inbox. You will use the App Password, not your regular account password, when connecting to Smartlead.
For Microsoft 365 / Azure inboxes:
- SMTP host: smtp.office365.com
- SMTP port: 587
- IMAP host: outlook.office365.com
- IMAP port: 993
Microsoft also requires you to verify that SMTP AUTH is enabled for the specific mailbox in the Microsoft 365 admin panel. Some tenants have this disabled by default.
Step 4: Set sending limits
Smartlead lets you configure daily send limits and delays between emails at the account level. For warmed inboxes, start conservatively. A common safe range is 30 to 50 emails per day per inbox, with a randomized delay between sends. These numbers can be increased gradually as the inbox builds more sending history.
Step 5: Assign inboxes to campaigns
Once the inbox is connected and tested, you can assign it to one or more campaigns. Smartlead distributes sending load across all assigned inboxes, which is useful for multi-inbox rotation setups.
The Part Most Teams Get Wrong
Getting inboxes connected to Smartlead is a setup task. Keeping them healthy is an ongoing operations task. Most teams invest heavily in step one and almost nothing in step two.
Here is what happens without inbox monitoring:
An inbox starts burning quietly. Replies drop. Bounce rates creep up. Spam placement increases. Smartlead keeps sending because it has no signal telling it to stop. By the time someone notices, the domain reputation is damaged, the sending infrastructure needs to be rebuilt, and weeks of campaign momentum are gone.
The problem is not the sequencer. Smartlead is a solid platform. The problem is that the sequencer has no native ability to tell you when an inbox is becoming unhealthy in real time. It sends. It does not watch.
That is the gap Peeker fills.
How Peeker Keeps Smartlead Inboxes Running Clean
Peeker is built specifically for teams running cold email at volume. It handles inbox provisioning, real-time deliverability monitoring, and automated inbox recovery in one system.
Inbox provisioning built for cold email
Peeker provisions Google Workspace and Microsoft Azure inboxes with DNS configuration handled as part of the setup. If you are tired of doing this manually for every new domain, Peeker’s Google Workspace Setup and Microsoft Azure Setup features take the repetitive configuration work off your plate.
Real-time burn detection
Rather than waiting for campaign performance to degrade before investigating, Peeker’s Burn Detection monitors inbox health continuously. When an inbox starts showing signs of spam placement or reputation damage, Peeker flags it immediately.
Automated inbox swaps
When a burned inbox is detected, Peeker does not just send an alert and wait for a human to act. The Auto Replacement and Swapping feature automatically replaces the damaged inbox with a healthy one and reconnects it to your Smartlead workflow. Campaigns keep running. The burned sender gets pulled from rotation.
This is the core of what Peeker calls self-healing inboxes. The system monitors, detects, and recovers without requiring manual intervention.
Smartlead-native workflow support
Peeker’s Smartlead integration is built around how Smartlead campaigns actually operate. The Peeker Smartlead use-case page covers the specific connection workflow and how auto-swaps work within active sequences.
Common Issues When Connecting Inboxes to Smartlead
SMTP authentication failing
Usually caused by not generating an App Password (Google) or not enabling SMTP AUTH at the tenant level (Microsoft). Verify both before assuming the connection is broken.
Emails landing in spam immediately after connecting
Almost always a warmup issue. An inbox that was not warmed properly before connecting to a cold campaign will have no sending reputation to lean on. Pull the inbox from the campaign, run a proper warmup, and reconnect.
High bounce rates after the first few sends
Check your prospect list quality. High bounce rates early in a campaign damage sender reputation quickly. Also verify that DMARC, SPF, and DKIM are all passing correctly using an inbox placement test.
Inbox disconnects in Smartlead
Token expiration and password changes can cause reconnect failures. Peeker’s Automatic Reconnects feature handles these automatically, preventing sending gaps caused by broken authentication.
FAQ
Does Peeker work directly with Smartlead? Yes. Peeker is built to support Smartlead workflows specifically. When an inbox burns or disconnects, Peeker can automatically swap in a replacement and reconnect it to your active Smartlead sequences. See the Smartlead use-case page for details on how the integration works.
What inbox types does Peeker support for Smartlead connections? Peeker supports both Google Workspace and Microsoft Azure inboxes. Both can be provisioned, monitored, and auto-replaced within Peeker. Setup documentation is available on the Google Workspace Setup and Microsoft Azure Setup feature pages.
How does Peeker detect a burned inbox? Peeker monitors deliverability signals continuously, including spam placement rates, authentication failures, and inbox health indicators. When signals fall below acceptable thresholds, Peeker’s Burn Detection flags the inbox and triggers the recovery workflow automatically.
How much does Peeker cost? Current pricing is available at Pricing. Peeker is built for teams running meaningful inbox volume, so pricing scales with the number of inboxes you are managing and monitoring.
Conclusion
Connecting email inboxes to Smartlead is a five-step technical process that most cold emailers can complete in under an hour. The harder problem is keeping those inboxes healthy across weeks and months of active campaigns.
Manual monitoring does not scale. By the time a human notices that an inbox is burning, the damage is usually already done. The teams running cold email at volume without blind spots are the ones who have built automated visibility and recovery into their infrastructure from the start.
Peeker handles provisioning, monitors every inbox in real time, and automatically swaps out burned senders before they affect your Smartlead results. If you are managing more than a handful of inboxes, that layer of protection is not optional.
Start tracking your deliverability in minutes. Try Peeker free at Pricing.
