Send WordPress email through Mailgun
Connect WordPress to Mailgun with NimblyMail SMTP for reliable delivery, built-in email validation, and full send logs in wp-admin.
Why pair Mailgun with NimblyMail
Mailgun pairs developer-grade sending infrastructure with tools most providers charge extra for — real-time email validation, detailed delivery logs, and flexible regional routing. NimblyMail connects your WordPress site to Mailgun in minutes, so every transactional email, WooCommerce notification, and form submission goes out through Mailgun’s infrastructure instead of your host’s unreliable default mail function.
Mailgun is built for developers who want visibility into what happens after “send.” Its per-domain SMTP credentials keep sending isolated and easy to audit, and its dashboard gives you bounce, complaint, and open/click data without needing a separate analytics tool. For WordPress sites already sending password resets, order confirmations, and admin alerts, Mailgun’s validation API is a genuine differentiator — you can catch typo’d or disposable addresses before a WooCommerce order ever gets stuck on a bad email.
Mailgun also supports both US and EU sending regions, which matters if you need to keep customer data processing within Europe. Combined with NimblyMail’s per-site connection settings, you get provider-grade deliverability without touching a line of code beyond the plugin’s settings screen.
Connect Mailgun in three steps
Generate domain SMTP credentials
In your Mailgun dashboard, go to Sending > Domains, add or select your sending domain, and open its SMTP credentials tab to generate a username and password (this is separate from your Mailgun account login).
Configure NimblyMail
In WordPress, go to NimblyMail SMTP > Settings, choose Mailgun as your mailer, and enter the SMTP hostname smtp.mailgun.org with port 587 (STARTTLS) — or port 465 if you prefer implicit TLS — along with the domain SMTP username and password from step 1.
Send a test email
Save your settings and send a test email from the NimblyMail dashboard to confirm authentication succeeds and mail arrives.
Mailgun requires you to verify your sending domain before it will deliver mail reliably. Add the TXT (SPF), CNAME (tracking), and DKIM TXT records Mailgun provides under Sending > Domains > DNS Records to your domain's DNS zone, then click Verify DNS Settings in Mailgun. Unverified domains are rate-limited and more likely to land in spam.
Mailgun + WordPress, answered
Yes. Mailgun's free tier (roughly 100 emails/day) supports SMTP relay, so you can connect and test immediately; upgrade when your site's volume grows.
NimblyMail SMTP connects via SMTP relay (smtp.mailgun.org), which is simpler to set up and works on any host that allows outbound SMTP. Mailgun's HTTP API is an alternative some developers prefer for high-volume sending, but it isn't required for typical WordPress/WooCommerce use.
The most common cause is using your Mailgun account password instead of the domain-specific SMTP password — regenerate the SMTP credentials under your domain's settings and re-enter them.
Yes — if your domain is set up under Mailgun's EU region, use smtp.eu.mailgun.org as the hostname instead of the US endpoint.
Not by default on outbound SMTP sends — validation is a separate Mailgun feature (Validate) you'd call from your own integration; NimblyMail's role is delivering the mail, not pre-validating recipient lists.
More integrations
View all integrations
Standard SMTP
FreeHost, port, encryption, optional authentication. If it speaks SMTP, NimblyMail connects to it.
Setup guide
SMTP2GO
ProConnect WordPress to SMTP2GO with NimblyMail SMTP — redundant global infrastructure, a permanent free plan, and simple SMTP-only setup.
Setup guide
Resend
FreeModern transactional API with a clean dashboard. Sandbox keys, instant verification, and DKIM that just works.
Setup guide
SparkPost
ProConnect WordPress to SparkPost with NimblyMail SMTP for advanced deliverability analytics and predictive engagement insights.
Setup guide