If you're using Mailgun for cold email in 2026, you're probably running into one of three problems: your emails aren't landing in inboxes, you're not sure if you're configured correctly, or you're getting bounces you don't understand.

The good news is that Mailgun, when set up right, is one of the most reliable sending platforms for cold email campaigns. The bad news is that "set up right" means more than just plugging in your API key and sending. Most people skip the infrastructure part and wonder why their deliverability tanks.

This is the actual guide to using Mailgun for cold email - what to configure, what numbers to expect, and how to diagnose when something breaks.

Why Mailgun for Cold Email (And When You Shouldn't)

Mailgun is built for transactional email, not marketing. That's actually an advantage for cold email, because Mailgun doesn't have the same sender reputation penalties that general-purpose email platforms carry. You get better deliverability starting from day one, and you have actual control over your infrastructure.

The tradeoff: you need to understand SMTP, SPF, DKIM, and DMARC. If you're not willing to spend 2-3 hours on initial setup, Mailgun might feel like overkill.

You should use Mailgun if:

You shouldn't use Mailgun if:

Initial Setup: The Non-Negotiable Parts

Before you send a single email through Mailgun, you need to configure your domain correctly. Skip this and you'll spend weeks debugging deliverability issues.

1. Domain Verification and DNS Records

Add your sending domain to Mailgun (not your main business domain - use something like mail.yourdomain.com or create a subdomain). Mailgun will give you three DNS records to add:

The SPF record should look like:

v=spf1 include:mailgun.org ~all

If you already have an SPF record, add the include statement to your existing record rather than creating a new one. Multiple SPF records break email authentication.

Add the DKIM record exactly as Mailgun provides it. This is the part that actually proves you own the domain. Without it, Gmail and Outlook will deprioritize your emails.

2. DMARC Policy (Critical)

Most people skip DMARC or set it to monitoring mode. For cold email, you want DMARC configured - but not enforced yet.

Create a DMARC record that looks like:

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]

This tells email providers "monitor my domain, send me reports, but don't reject emails yet." After 30 days of clean reports, you can change p=none to p=quarantine, then eventually p=reject. Don't skip this step - DMARC reports show you exactly where your emails are failing.

3. Warm-Up Strategy (Before You Send at Scale)

Mailgun doesn't warm up domains automatically. You need to do this manually or use a tool. The strategy is simple:

This builds sender reputation. If you send 500 emails on day one from a brand new domain, ISPs flag you as spam immediately.

Configuration That Actually Matters

API Key vs SMTP

Mailgun offers two ways to send: HTTP API or SMTP. For cold email campaigns, use SMTP. It's more reliable, gives better bounce data, and integrates with most cold email tools.

Your SMTP credentials from Mailgun will look like:

Use port 587 with TLS unless your tool specifically requires port 465.

From Address Configuration

This is where most people mess up. Your "From" address needs to match your verified domain. If your domain is mail.yourdomain.com, your From address should be [email protected] (the root domain, not the subdomain).

Add authorized senders in Mailgun for each person on your team. If you're sending from [email protected], verify that address specifically.

Bounce and Complaint Handling

In Mailgun, set up webhooks to track bounces and complaints. This is critical - every hard bounce needs to remove that email from your list immediately, and every complaint needs to log which person marked you as spam.

Without this, you'll resend to dead addresses and destroy your sender reputation.

What Good Deliverability Actually Looks Like

After 30 days of proper setup and warm-up, here are the baseline numbers you should expect:

If you're seeing bounce rates above 8%, your list is dirty - check our list cleaning guide. If complaints are above 0.5%, your copy or targeting is off.

Track deliverability in Mailgun's dashboard, but also in your cold email tool. The two should roughly match - if they don't, something's wrong with how your tool is parsing bounces.

Common Mailgun Problems (And Fixes)

Emails Going to Spam

This usually means DKIM or SPF isn't configured correctly. Log into Mailgun and check your domain status - it should show all three records as verified (green). If any show as red, fix the DNS record and wait 24 hours for propagation.

Bounces Without Warning

Mailgun temporarily suppresses emails to addresses that bounce. These suppressions last 3 days by default. You can manually remove addresses from suppression in the dashboard, but honestly, if an address bounced, you shouldn't resend to it anyway.

Sending Too Fast and Getting Rate Limited

Mailgun has limits based on your plan, but more importantly, sending too fast (more than 300 emails per minute) will trigger ISP rate limits. Spread your sends across the day using your cold email tool's scheduling - don't blast 1,000 emails in an hour.

Mailgun Pricing Reality Check

Mailgun's free tier is genuinely useful - 100 emails per day forever. If you're at 5,000 emails per month, you're on a paid plan ($25-100/month depending on volume). This is cheap compared to the infrastructure headaches you avoid.

The cost is worth it if you're running serious cold email campaigns. If you're sending 200 emails a month, it's probably overkill.

When Setup Stops Being The Bottleneck

Once Mailgun is working, the limiting factor shifts to lead quality, copy, and frequency. You can have perfect infrastructure and still get 0 replies if your targeting is bad or your email is generic.

Mailgun is the foundation. Everything else is the building.

Related Guides