Connecting Maildoso to Smartlead: setup, sync, and gotchas in 2026

How the Maildoso + Smartlead Integration Works

Maildoso provisions Google Workspace or Microsoft 365 inboxes with auto-warming built in, then hands you SMTP and IMAP credentials. Smartlead uses those credentials to send sequences and pull replies. There's no native API sync between the two tools. The connection is a standard SMTP handshake, and it takes about 10 minutes to configure per inbox.

What does sync: outbound sends, bounce detection, and reply tracking. What doesn't sync: Maildoso's warm-up activity log and inbox health score. You'll monitor those in Maildoso's dashboard separately, which takes about 2 minutes a week.

The problem most teams hit isn't the connection itself. It's running Maildoso's warm-up and Smartlead's built-in warm-up simultaneously on the same inbox. Two warm-up systems create overlapping activity patterns that trigger Google's anomaly detection on accounts under 30 days old. The fix is in step 7 below.

Step-by-Step Setup: Maildoso to Smartlead in 7 Steps

The full setup takes 15-20 minutes if your DNS records are already in place. The most common failure point isn't the SMTP config. It's a DMARC record set to the wrong policy, which quietly rejects outbound mail before it reaches anyone on your list.

1. Order inboxes from Maildoso. Choose Google Workspace or Microsoft 365. Google is the safer default for most cold email use cases. Microsoft is worth considering if your prospects are in financial services or government contracting, where Google sender reputation gets filtered more aggressively.
2. Connect your sending domain. Add your cold email domain in the Maildoso dashboard and apply the MX records they provide. Never send cold outbound from your main company domain.
3. Configure DNS records. Add SPF, DKIM, and DMARC records for your sending domain. Set DMARC to p=none initially. Starting at p=quarantine or p=reject blocks your own outbound mail until the policy propagates across all resolvers, which takes 24-72 hours.
4. Let the warm-up run. Maildoso auto-warms new inboxes. Give it 14 days minimum before connecting to Smartlead. 21 days is the safer target. A cold inbox sending 40 emails/day on day one will collect complaints before it collects replies.
5. Copy SMTP credentials from Maildoso. In the Maildoso dashboard, find SMTP settings for each inbox: host (smtp.gmail.com or smtp.office365.com), port 587, the full email address as username, and an app-specific password. This is not your account login password.
6. Add the account in Smartlead. Go to Email Accounts > Add Account > SMTP/IMAP. Paste the credentials from step 5. Smartlead tests the connection immediately. If it fails on the first try, the cause is almost always the password type.
7. Set sending limits and disable Smartlead's warm-up. Cap daily sends at 30-40 for the first 30 days. Then disable Smartlead's built-in warm-up for this inbox entirely under Email Accounts > select account > Warmup Settings > toggle off. Running two warm-up systems on one inbox is the single most common reason new Maildoso accounts get flagged in week two.

Sending Benchmarks: What to Expect in 2026

A properly warmed Maildoso inbox running through Smartlead should hit under 2% bounce rate and over 95% inbox placement by day 21. These numbers assume clean, verified lists and personalized first lines. One spam complaint per 500 emails can reverse weeks of progress on a new inbox.

Three inboxes is the minimum viable configuration for a campaign. One inbox gets flagged fast with no rotation buffer. Five inboxes per campaign is the sweet spot for teams sending to 300-500 contacts per month, per our experience across 3,000+ campaigns.

When This Stack Makes Sense

The Maildoso + Smartlead combination works for teams running 3-15 inboxes per campaign with clean, targeted lists. Below 3 inboxes the volume's too thin to generate reliable signal. Above 15, you likely need a more complex routing layer to avoid mixing signals across campaigns and domains.

Three scenarios where this stack delivers:

• Founders doing their own outbound. Total cost stays under $80/month for 5 inboxes. No SDR overhead. Smartlead's inbox rotation handles the complexity after initial setup.
• Agencies managing multiple clients. Maildoso provisions new inboxes in under 24 hours. Each client gets their own domain workspace. Keeping infrastructure separate prevents cross-contamination of sender reputation between clients.
• Teams testing a new ICP before hiring. Spin up 5 inboxes, run 500 targeted contacts through Smartlead's A/B features, and measure reply rates before committing budget to a full sales hire. Total cost: under $120 for a 90-day test.

If you're already running Instantly, the Maildoso connection process is identical. Same SMTP credentials, same port settings, same warm-up logic applies.

Too Busy to Run Outbound Yourself?

Modern Inbound handles research, infrastructure, warm-up, account lists, copy tests, sending, replies, and routing. The system has booked 2,700+ B2B meetings and influenced $20M+ in pipeline.

Frequently Asked Questions

Does Maildoso integrate natively with Smartlead?

No native API integration exists. You connect via standard SMTP and IMAP credentials. Maildoso provides Google Workspace or Microsoft 365 SMTP settings, and Smartlead accepts them under Email Accounts > Add Account > SMTP/IMAP. No API sync needed for standard campaign use.

Can I run both warm-up systems at the same time?

You shouldn't. Running Maildoso's and Smartlead's warm-up simultaneously creates overlapping email volume that looks anomalous to Google and Microsoft filters. Disable Smartlead's warm-up entirely for inboxes provisioned through Maildoso. Maildoso's system is purpose-built for this; Smartlead's is a secondary feature.

What's the safe maximum send volume per inbox?

For inboxes under 60 days old, stay at 40-50 emails/day. After 60 days of clean history with under 2% bounces, you can push to 60-80/day. Sending over 100/day in months 1-2 triggers Google's abuse detection regardless of warm-up status.

What do I do when Smartlead shows SMTP Authentication Failed?

You're using your account password instead of an app-specific password. In Google, go to Security > 2-Step Verification > App Passwords and generate one for Smartlead. Microsoft has the same flow under Security settings. This resolves the error in under 2 minutes.

If you'd rather hand off the full infrastructure layer - domains, inboxes, deliverability, and campaign execution - that's exactly what Modern Inbound does. You show up to warm replies. See our pricing page to find out if it's a fit.