Newsletter Mailgun Addon 4.3.7

Look, if you’re still trying to blast thousands of emails through your shared host’s default wp_mail(), you need an intervention. Your server IP is probably blacklisted to oblivion.

I recently had to salvage a client’s setup where their marketing team was complaining about a 10% open rate. The culprit? Everything was landing in spam. To fix this, I ripped out their bloated SMTP plugin and hooked up the Newsletter Mailgun Addon.

Here’s my unfiltered take after deploying this on a heavy production site.

The Good: Actually Bypassing the Spam Folder

The Newsletter Mailgun Addon does exactly one thing, and thankfully, it doesn’t screw it up. It routes the core Newsletter plugin’s outgoing queue directly through Mailgun’s API instead of relying on standard SMTP.

Why does this matter? Because SMTP is slow as hell. When you push 50,000 emails, standard SMTP connections will choke your PHP workers and spike CPU usage. API routing is infinitely faster.

Setup is mostly painless. You go to Newsletter -> Settings -> Delivery, select Mailgun, and dump your API key and sending domain in there.

The Bad: Hardcoded Endpoints and EU Region Headaches

Here’s where my blood pressure started rising. My client uses Mailgun’s EU region. If you just paste the API key, the addon defaults to the US endpoint (api.mailgun.net).

I opened the Mailgun dashboard and saw zero traffic. Checked my server logs, nothing. I had to dig into the plugin files. If you look inside newsletter-mailgun/class-mailgun.php, you’ll see how it constructs the API call. Thankfully, they recently added a toggle for the EU region in the UI, but older versions required a manual filter hook to rewrite the base URL.

Also, watch your SSL certificates. I ran into a cURL error 60 (SSL certificate problem) because the server’s CA bundle was outdated. I had to temporarily throw add_filter('https_ssl_verify', '__return_false'); into my child theme’s functions.php just to test the connection while server support updated the certs. Don’t leave that in production, obviously.

Bounce Webhooks: The Real Nightmare

The biggest selling point of the Newsletter Mailgun Addon is automatic bounce processing. If an email hard-bounces, Mailgun pings your site, and the plugin changes the subscriber status to “Bounced”.

Sounds great, right? Until your security setup blocks it.

I spent two hours debugging why bounces weren’t registering. DevTools won’t help you here since it’s server-to-server. I had to check Mailgun’s webhook logs and saw straight 403 Forbidden errors. Wordfence and Cloudflare were blocking Mailgun’s POST requests to the /?na=mailgun endpoint because it looked like a bot attack.

The Fix: I had to manually whitelist Mailgun’s IP ranges in Cloudflare’s WAF rules and exclude that specific query string from Wordfence’s brute-force protection.

Licensing and Usage

I originally grabbed a GPL version of this to test on my local staging environment before making the client buy anything. Honestly, it’s a lifesaver. The GPL release is fully working with unlimited website usage.

There are no obnoxious admin notices screaming at you to input a license key just to access the settings. It just works. You do have to handle manual updates, though. I usually just overwrite the folder via SFTP when a new version drops. No big deal.

Developer FAQ

Does this addon slow down the WP Cron?

Not really. It offloads the heavy lifting to the API. But if you have a massive queue, make sure you trigger WP Cron via a real server-side cron job (cPanel/CLI) every 5 minutes, not the default AJAX-based wp-cron.php.

Why are my open tracking stats suddenly zero?

Check your DNS records. If you enabled click/open tracking in Mailgun, you need a CNAME record pointing email.yourdomain.com to Mailgun. If that’s missing, the tracking pixels will 404. Check the Network tab in DevTools on an opened email to verify the pixel URL.

Can I use multiple Mailgun domains for different lists?

No. The plugin settings are global. It binds one domain to the entire Newsletter installation. If you need multi-domain routing, you’ll have to write a custom integration hooking into newsletter_message_send.