How to integrate Mailforge with Smartlead in 2026

How Mailforge and Smartlead Work Together

Mailforge handles infrastructure: domain purchasing, inbox creation, and warmup. Smartlead handles execution: sequences, A/B testing, reply routing, and inbox rotation. Connect them once via SMTP credentials and every inbox Mailforge creates becomes a sending account Smartlead rotates through automatically. The split keeps deliverability management separate from campaign logic, and that separation is worth protecting.

The data flow is one-directional. Mailforge doesn't pull anything from Smartlead. Smartlead authenticates against Mailforge's SMTP server, sends through those inboxes, and handles all reply tracking internally. Mailforge is the pipe; Smartlead is what flows through it.

Mailforge is the right call for anyone serious about inbox placement at scale. Smartlead's native domain setup works for testing, but the moment you're running 10+ inboxes, dedicated infrastructure pays for itself. Teams in this configuration typically see 20-30% higher inbox placement versus Smartlead's built-in domain management, per practitioners in the LeadGenHub Slack community. Mailforge's warmup runs on infrastructure that doesn't co-mingle warmup traffic with live sends.

How to Connect Mailforge to Smartlead: 6 Steps

The setup takes 6 steps: create the inbox in Mailforge, wait out warmup, retrieve SMTP and IMAP credentials, add a sending account in Smartlead, set daily limits, and run a test send. Done correctly, your first campaign email goes out within 20 minutes of completing warmup. Done out of order, you'll spend an hour on an authentication error that was actually a warmup timing issue.

1. Create your inbox in Mailforge. Log into the Mailforge dashboard, click "Add Inbox," and select your domain. Mailforge auto-configures SPF, DKIM, and DMARC on domains it manages. Bringing an existing domain means adding those DNS records manually before continuing.
2. Complete the warmup period. Don't skip this. Mailforge's warmup runs a minimum of 14 days. Adding a cold inbox to Smartlead before warmup finishes starts your inbox placement below 60%, per Mailforge's internal benchmarks. Nothing downstream fixes that starting point.
3. Retrieve SMTP credentials. In Mailforge, go to Inbox Settings, then SMTP Configuration. You'll find the host (smtp.mailforge.ai), port (587 for TLS or 465 for SSL), your full email address as the username, and a generated app password. Copy all four values exactly.
4. Add a sending account in Smartlead. Go to Email Accounts, then Add Account, then Custom SMTP/IMAP. Paste the SMTP host, port, username, and password from step 3. For IMAP (required for reply sync), use imap.mailforge.ai on port 993 with SSL enabled. Leaving IMAP blank is the most common silent failure in this setup.
5. Set daily send limits. Smartlead defaults to unlimited sends per day on custom SMTP accounts. Cap at 30-40 emails for the first 30 days post-warmup, then increase to 80-100. Mailforge's warmup builds to around 200/day, but starting lower protects you if an early prospect marks you as spam.
6. Send a test email. Use Smartlead's built-in test send to confirm the connection. A failure message tells you whether it's a credential mismatch (wrong password) or a timeout (wrong port or Mailforge's IP blocked by your outbound firewall).

SMTP and IMAP Field Mapping

Smartlead's Add Account form has 8 fields. Mailforge's SMTP panel shows 6 values. Three mismatches cause 90% of failed connections: the IMAP host entered in the SMTP field, port 25 instead of 587 or 465, and the Mailforge login password instead of the generated app password. The table below maps every value correctly.

Common Errors and How to Fix Them

Three errors account for 80% of failed Mailforge-to-Smartlead connections. Authentication failures come first, from using your Mailforge login password instead of the generated app password. Timeouts come second, caused by port 25 or a firewall block. The third is silent: IMAP left blank means Smartlead sends fine but never surfaces replies in the unified inbox.

"Authentication failed" on test send. Go to Mailforge, regenerate the app password under Inbox Settings, and paste it fresh. Passwords copied with a trailing space fail silently with this exact error. Confirm your SMTP username is the full email address including the @ domain, not just the local part.

"Connection timed out." Switch the SMTP port from 465 to 587, or the reverse. Some corporate networks block 465. If both ports fail, Mailforge's sending IP may be blocked by your outbound firewall. Contact Mailforge support for their current IP ranges to whitelist.

Replies not showing in Smartlead unified inbox. IMAP isn't configured. Set imap.mailforge.ai as the IMAP host with port 993 and SSL enabled. Without this, Smartlead sends but can't read the inbox, so the unified reply view stays at zero even when prospects write back.

Deliverability drops after three weeks. Send limits weren't set at account creation. Smartlead's default is unlimited sends on custom SMTP. Uncapped sending on a 14-day warmed inbox collapses domain reputation fast. Set the cap when you connect the inbox, not after the damage is done.

Deliverability Benchmarks After Integration

A Mailforge-plus-Smartlead stack with 14+ day warmed inboxes and daily sends capped at 40-50 per inbox should hit 88-93% inbox placement in the first 90 days. Reply rates on solid sequences run 3-7% in this range, per internal Modern Inbound data across 3,000+ campaigns. Below 85% inbox placement points to one of two problems: warmup was cut short, or the contact list is poor quality.

The stack beats Smartlead's built-in infrastructure in one measurable way: bounce rate. Mailforge's MX verification at inbox creation keeps bounce rates below 2% on fresh domains. Teams using unverified lists on Smartlead's native domains report 4-8% bounces on the first campaign, per LeadGenHub community data. Clear 5% bounce rate and you're in spam-folder territory with Google and Microsoft.

If you're running Instantly or Lemlist in parallel with Smartlead, don't cross-send from the same Mailforge inbox through multiple platforms. Doing so doubles your actual send volume without triggering any alerts, and your deliverability collapses within 30 days. One inbox, one sending platform.

Pricing and Plan Requirements

Mailforge costs about $3/inbox/month for managed Google Workspace inboxes. Smartlead's Basic plan is $94/month for unlimited sending accounts and 6,000 active leads. Five Mailforge inboxes into one Smartlead workspace runs roughly $109/month before domain registration. That's cheaper than a single seat of Outreach or Salesloft, both of which start at $100/user/month with no inbox infrastructure included.

You don't need Smartlead Pro ($174/month) when Mailforge handles warmup. Upgrade to Pro only if you need more than 6,000 active leads, custom webhooks for CRM routing, or the analytics reporting tier. The Mailforge side doesn't change either way.

For agency setups, Mailforge has no restriction on how many Smartlead workspaces one account feeds. Smartlead's Custom plan is required for client-facing white-labeling, but the Mailforge account stays single regardless of client volume.

If you'd rather skip building this stack yourself, Modern Inbound handles the full infrastructure: domains, Mailforge inboxes, warmup, and Smartlead campaign execution, for a flat ₹1,50,000/month retainer.

Scale Outreach Without Hiring SDRs

Most B2B teams underestimate the work before sending: buyer-language research, list logic, DNS, warm-up, deliverability, copy testing, and reply handling. Modern Inbound runs the operating layer so founders can stay focused on sales calls.

Frequently Asked Questions

Four questions come up on every Mailforge plus Smartlead setup. The answers are specific: no native API exists between the two platforms, inbox limits come down to budget not platform caps, warmup can't be skipped without tanking deliverability, and Smartlead isolates inbox suspensions so one bad actor doesn't kill the whole campaign.

Does Mailforge integrate directly with Smartlead via API?
No. There's no native API between the two as of 2026. The connection is manual: copy SMTP and IMAP credentials from Mailforge and paste them into Smartlead's custom account setup. About 5 minutes per inbox, no developer needed.

How many Mailforge inboxes can I connect to one Smartlead account?
Smartlead's Basic plan supports unlimited sending accounts. No cap on Smartlead's side. Your practical limit is Mailforge's per-inbox cost. Most teams at 500-1,000 emails per day use 10-15 inboxes in one workspace.

Can I use Mailforge inboxes in Smartlead before warmup is complete?
Technically yes. Don't. Skipping 14-day warmup drops inbox placement below 60%, per Mailforge's own benchmarks. Complete warmup first.

What happens to Smartlead campaigns if a Mailforge inbox is suspended?
Smartlead marks that account inactive and pauses sends from it automatically. Your other inboxes keep running. You'll get a notification in the Smartlead dashboard within 24 hours.