How to Set Up Mautic for Cold Email Infrastructure: 2026 Guide
By Puzzle Inbox Team · May 22, 2026 · 7 min read read
Setting up Mautic for cold email infrastructure in 2026 requires careful SMTP, warmup, and deliverability config. Here is the operator-grade setup walkthrough with real numbers.
How to Set Up Mautic for Cold Email Infrastructure
Mautic is the leading open-source marketing automation platform, and in 2026 it is increasingly used as a self-hosted alternative to Smartlead and Instantly for cold email infrastructure. The cost savings are real - roughly $0 in software fees versus $97-297/month - but the setup demands serious deliverability discipline.
This guide walks through the cold-email-specific Mautic configuration: SMTP routing, throttling, bounce handling, and integration with pre-warmed inbox pools. General Mautic install guides skip 80% of what cold senders actually need.
Prerequisites: server, domain, and inboxes
You need a VPS (4GB RAM minimum, Hetzner CX22 at 5.83 EUR/month works), a Mautic-only subdomain like mautic.yourcompany.com, and a separate cold-sending domain stack (5-10 throwaway domains with mailboxes). Never run Mautic on the same domain you send cold from.
Step 1: Install Mautic 5.x
Mautic 5.2 (latest stable as of May 2026) requires PHP 8.1+, MySQL 8.0+, and Composer. Install via composer create-project mautic/recommended-project. Skip the Docker images for production - they have a known queue worker issue under high send volume.
Step 2: Configure SMTP per-mailbox
Default Mautic uses a single SMTP. For cold email you need per-mailbox SMTP rotation. Install the "Multi SMTP" plugin or build a custom Email Transport. Each cold mailbox connects via its own SMTP credentials - typically Google Workspace SMTP (smtp.gmail.com:587 with app password) or Microsoft 365 (smtp.office365.com:587).
Step 3: Set throttling correctly
Under Configuration > Email Settings, set "Messages Per Second" to 0.01 (one email every 100 seconds per mailbox) and "Process Messages Every" to 5 minutes. Anything faster triggers GWS rate limits (Gmail caps at 2,000/day per mailbox but throttles aggressively above 50/hour for cold patterns).
Step 4: Configure bounce processing
Enable Monitored Email Boxes pointing at each sending mailbox's IMAP. Set bounce action to "Mark as Do Not Contact" for hard bounces and "Unsubscribe" for soft bounces after 3 occurrences. Without this, you will accumulate dead addresses and torch your domain reputation within 2 weeks.
Step 5: Warmup is not built-in
Mautic has zero warmup functionality. You must either build it (cron jobs sending peer-to-peer between your mailboxes) or buy pre-warmed inboxes externally. Puzzle Inbox sells pre-warmed GWS and Outlook inboxes at $3-4.50 each with ongoing warmup at $0.35-0.50 per inbox per month, which plugs directly into Mautic via SMTP without needing to build warmup infrastructure.
Step 6: Authentication for every sending domain
Each of your throwaway sending domains needs SPF including your Mautic server IP plus the SMTP relay (smtp.gmail.com or outlook.com), DKIM published from the mailbox provider, and DMARC at p=quarantine minimum. Follow our SPF, DKIM, DMARC setup guide per domain - this is non-negotiable for 2026 Gmail/Outlook bulk sender rules.
Step 7: Build the campaign correctly
Use Mautic Campaigns (not Email Broadcasts) for cold sequences. Campaigns support delays, conditional branches, and reply detection via IMAP polling. Set inter-step delays to minimum 2 business days. Use the Conditions module to stop sequences on reply detection - Mautic polls IMAP every 15 minutes by default, increase to 5 minutes for sales workflows.
Step 8: List hygiene
Mautic does not verify emails. Use Bouncer, MillionVerifier, or NeverBounce via API before import. Reject anything above 5% risk score. Cold lists with greater than 10% invalid addresses guarantee account disables within a week regardless of warmup quality. See our cold email warmup guide for volume curves that survive list noise.
Mautic versus commercial tools
Mautic saves money but costs time - figure 40-60 hours initial setup and 5-10 hours/month maintenance. For teams under 10 SDRs, Smartlead or Instantly pay for themselves in saved engineering hours. Mautic wins above 50 SDRs or when sending to highly regulated verticals where data residency matters. Our Maildoso comparison covers managed-infrastructure alternatives.
Common Mautic cold email pitfalls
The top three failure modes: queue worker dying silently (configure systemd + monit), IMAP bounce processing running out of memory at 50k+ contacts (increase PHP memory_limit to 1G), and DKIM signing failing because Mautic signs with its own key instead of the mailbox provider key (disable Mautic DKIM, rely on SMTP relay signing).
For deliverability issues post-launch, see fixing cold emails landing in spam.