Send Emails with Mandrill is a single-provider WordPress mailer for Mailchimp Transactional Email, the service formerly sold as Mandrill. It replaces wp_mail() with a call to Mandrill’s HTTPS API, falls back to native wp_mail() when the send fails for a reason other than a rejected recipient, and exposes a small set of Mandrill-specific filters plus a static wpMandrill::mail() function for direct use from other plugins. For the full install sequence (API key, DNS, plugin fields, first test send), see Mandrill SMTP plugin for WordPress.
The plugin is a community fork maintained by Miller Media. The original wpMandrill plugin went unmaintained; Miller Media’s Matt Miller forked the abandoned codebase and has continued shipping releases under the Send Emails with Mandrill name. The current release (1.7.0, November 2026) requires PHP 8.1 and WordPress 5.9 and is tested up to WordPress 7.1. The code is GPL 2.0 and the public repository is at
Miller-Media/send-emails-with-mandrill.
The narrow case
Three paths connect a WordPress site to Mailchimp Transactional, and the choice between them is operational, not deliverability-related. All three reach the same infrastructure with the same authentication, sign with the same DKIM key, and meet the same SPF policy.
The first path is generic SMTP via any mailer plugin pointed at smtp.mandrillapp.com on port 587, authenticated with PLAIN or LOGIN, using a Mailchimp Transactional API key as the password. FluentSMTP, Post SMTP, WP Mail SMTP free and other mailers all handle this configuration. The credentials are interchangeable across them, so switching mailer plugins later requires no change to the Mandrill side.
The second path is a general mailer plugin’s built-in Mandrill mailer. WP Mail SMTP, Post SMTP, and Easy WP SMTP each ship one in the free plugin; FluentSMTP does not. The mailer calls the Mandrill HTTPS API directly rather than connecting over SMTP, and the configuration is one API key with no host or port to set. This skips the SMTP handshake on every send and ties the integration to the plugin that holds the key.
The third path is Send Emails with Mandrill. It also calls the API directly, and adds three capabilities that neither of the other paths offers: automatic per-message tagging by the originating WordPress hook, a mandrill_payload filter for per-send payload mutation, and a wpMandrill::mail() static function that other plugins can invoke without going through wp_mail() at all.
For most sites sending through Mandrill, the first path is the cleanest choice. Generic SMTP configuration is portable, easy to migrate off, and benefits from whichever mailer plugin’s logging and routing features the site already runs. Pick Send Emails with Mandrill only when one of three Mandrill-specific features is the reason for the install:
- Sites that need to alter the message payload before send (custom merge variables, per-recipient metadata, Mandrill template handles) use the
mandrill_payloadfilter, which has no portable equivalent. - Sites that want every WordPress email auto-tagged in the Mandrill dashboard by the function that sent it (
wp_retrieve_passwordfor password resets, and so on) get that classification for free; the generic paths send untagged. - Sites with custom plugins that send transactional email directly through
wpMandrill::mail()rather thanwp_mail()need this plugin to expose that entry point.
If none of these apply, install one of the generic mailers or use the built-in Mandrill option in WP Mail SMTP, Post SMTP, or Easy WP SMTP. A single-provider mailer is overhead when nothing in its API earns its place. (For the comparable case where a single-provider plugin does earn its install on capability grounds, see the Mailgun for WordPress review, where API-mode delivery over port 443 is the differentiator.)
Configuration
The API key is the configuration. Generate a Mailchimp Transactional API key in the dashboard under SMTP & API Credentials, then either enter it at Settings > Mandrill or define it as a constant in wp-config.php:
define( 'SEWM_API_KEY', 'your-api-key-here' );
Defining the key in wp-config.php keeps it out of the WordPress database and out of any settings export. The Mailchimp marketing API key will not authenticate; the key has to be the Transactional one, generated in the Transactional dashboard area. Mandrill signs with the mte1 and mte2 DKIM selectors and requires a DMARC policy on the sending domain. The DNS auth checker reads how those records resolve from the receiver’s perspective, so a stale nameserver or a mistyped selector shows up before the fallback-to-native wp_mail() path fires in production.
Settings > Mandrill also has a Template setting that wraps every message in a stored template. Since 1.7.0 its dropdown lists templates created in Mailchimp alongside the account’s Mandrill templates, and the plugin sends with the matching API call for each kind; a mandrill_mc_template_version filter picks the published or draft version of a Mailchimp template.
There is no allow-list or per-site exclusion in the free plugin: every wp_mail() call goes through Mandrill, and the only escape hatch is to set $message['force_native'] = true inside a mandrill_payload filter to route a specific send through native wp_mail() instead. Use this for emails that should not touch the transactional provider (an internal heartbeat to localhost, a notification that needs to ship from a different From domain than the site’s authenticated Mandrill identity).
The fallback to native wp_mail() triggers when the API call fails (a connection error, an error response) or when Mandrill refuses the message for a reason tied to the message or the account. It does not trigger when Mandrill rejects a recipient because the address unsubscribed, filed a spam complaint, bounced or is invalid. If Mandrill accepts at least one recipient, there is no fallback, so the accepted recipients do not get a duplicate. If every recipient is rejected for one of those recipient reasons, wp_mail() returns false and fires wp_mail_failed with the reasons. When the fallback does run, it skips the recipients Mandrill rejected for those reasons, so the native mailer cannot reach an address on Mandrill’s suppression list. Versions before 1.6.5 handed rejected recipients to the native mailer too.
The fallback is a failure path, not a routing decision: a sending-domain authentication problem at Mandrill will not be fixed by handing the message to PHP’s mail() on the same host, and a host with no working mail() configuration will silently drop the fallback message. Most managed WordPress hosts (Kinsta, WP Engine, Pressable, Pantheon and others) block outbound mail() or restrict it to their own outbound relay; for sites on those hosts, the native fallback is theatre. The mechanism’s real value is for transient Mandrill API errors (an outage, a rate limit) on hosts where mail() actually works.
The plugin writes Mandrill errors, fallback errors and sends where Mandrill rejected every recipient to the PHP error log, whatever WP_DEBUG is set to. A recipient rejected on a send that Mandrill accepted for someone else is not logged there; it shows in the Mandrill activity log. The readme still says WP_DEBUG adds plugin messages through the send process, a note carried over from the original plugin; the 1.7.0 code does not check WP_DEBUG. The free plugin has no admin log table of its own; the per-message activity log lives in the Mandrill dashboard with 30 days of retention.
Hooks and the wpMandrill static class
The plugin has seven filters and two actions of its own; it also runs WordPress core’s wp_mail, wp_mail_from and wp_mail_from_name filters and fires wp_mail_failed. The wp_mail_native action is the observability hook for the fallback path described above: it fires every time a send falls through to native wp_mail(). It does not fire when every recipient is rejected, since that send gets no fallback, so a monitoring plugin that counts failed Mandrill sends has to listen on wp_mail_failed as well.
| Hook | Purpose |
|---|---|
mandrill_payload |
Mutate the message payload before send. Setting $message['force_native'] = true skips Mandrill and uses native wp_mail() for that send. |
mandrill_nl2br |
Toggle the <br/> substitution applied to plain-text bodies per message. Used to exclude WooCommerce or password-reset emails from the rewrite. |
mandrill_http_request_args |
Change the arguments passed to wp_remote_request() for each Mandrill API call (timeout, SSL verification). Added in 1.6.4. |
mandrill_mc_template_version |
Send the published (default) or draft version of a Mailchimp-managed template. Added in 1.7.0. |
wpmandrill_is_woocommerce_active |
Override the WooCommerce detection behind the plugin’s WooCommerce line-break fix. |
wpmandrill_enable_reports |
Disable the reports area programmatically; this also stops the background stats calls to Mandrill and hides the dashboard widget. |
wpmandrill_enable_widgets |
Disable the admin dashboard widget programmatically. |
wp_mail_native (action) |
Fires when a send falls back to native wp_mail(). The observability hook for fallback events. |
mandrill_response_received (action) |
Fires with Mandrill’s per-recipient API response for a wp_mail() send, before the plugin decides between success, failure and fallback. It does not fire when the API call itself errors. |
A typical mandrill_nl2br filter, taken from the plugin’s own documentation, excludes password reset emails from the line-break rewrite by checking the automatic tags the plugin attaches to each message:
function disable_nl2br_for_password_resets( $nl2br, $message ) {
if ( in_array( 'wp_retrieve_password', $message['tags']['automatic'], true ) ) {
$nl2br = false;
}
return $nl2br;
}
add_filter( 'mandrill_nl2br', 'disable_nl2br_for_password_resets', 10, 2 );
The wpMandrill::mail() static function is the plugin’s other entry point for custom code. Custom plugins can call wpMandrill::mail( $to, $subject, $html, $headers, $attachments, $tags, $from_name, $from_email, $template_name ) directly, and the parameters after those cover Mandrill options that wp_mail() has no argument for: merge variables, metadata, a subaccount, an IP pool, a scheduled send time. It returns Mandrill’s per-recipient response (or a WP_Error) rather than a true or false, and it never falls back to the native mailer: the calling code sees which recipients were sent, queued or rejected, and decides what to do. It does not skip the WordPress mail filters. The wp_mail filter and mandrill_payload both still run on every call, so a logging plugin hooked on wp_mail sees these sends too. Of the three Mandrill-specific features that justify this plugin over generic SMTP, this is the one with the cleanest fit-or-not test: if the codebase has a custom sender that needs Mandrill’s per-send options or its per-recipient result, the plugin earns the install on that ground alone.
Automatic tagging in the Mandrill dashboard
Every send through wp_mail() is automatically tagged with the name of the function that called wp_mail(), prefixed wp_: wp_retrieve_password for password resets, and a class method as wp_Class->method or wp_Class::method. The tag names the sending function, not the email type. WooCommerce sends its emails from one method, so on a reading of the WooCommerce and plugin source its order emails share one tag rather than getting one per order status. The plugin also adds the general tags set under Settings > Mandrill to every message. The tags appear in the Mandrill dashboard’s reporting and are filterable as a facet.
For a WordPress site with a mix of WooCommerce order emails, contact form submissions, comment notifications and password resets, this surfaces deliverability problems by sending plugin or core function: a spike in wp_retrieve_password bounces is visible at a glance without reading individual log entries. None of the generic SMTP paths produce this classification. The tagging is a Mandrill API field, set by the plugin per send.
Two display limits apply at the dashboard layer. Daily statistics show data for the first 20 senders and the first 40 tags. Each sending function is one tag, so a site whose plugins send mail from more than 40 distinct functions in a day passes that limit; once it does, the daily breakdown truncates and the dashboard becomes incomplete as a per-source debugging tool. The underlying activity log still records every send; the truncation is a reporting-view limit, not a data loss.
Where it sits against the alternatives
Generic SMTP via FluentSMTP or Post SMTP brings free email logging in addition to the routing this plugin handles; WP Mail SMTP free does not log without the Pro upgrade. For sites that need a log of outbound messages and do not need the three Mandrill-specific features above, FluentSMTP or Post SMTP pointed at smtp.mandrillapp.com is the more complete answer than Send Emails with Mandrill plus a separate logger.
The built-in Mandrill mailers in WP Mail SMTP, Post SMTP, and Easy WP SMTP match Send Emails with Mandrill’s setup cost (one API key, no host configuration) and are the shorter path for sites already on one of those plugins. The trade-off is platform lock-in: the configuration is tied to that plugin, does not carry over if another mailer is installed, and does not produce the dashboard tagging or expose the wpMandrill::mail() static function.
The remaining slot is for sites that need exactly what Send Emails with Mandrill provides and not the additional surface of a multi-provider mailer. Single-purpose, single-provider, three Mandrill-specific features, no logging table, no provider switching, no upsell.
The platform context
Send Emails with Mandrill is a thin layer on top of Mailchimp Transactional Email: if the platform is the wrong fit for the site, the plugin will not change that. Mailchimp Transactional has a $40/month minimum (a Mailchimp Standard plan at $20/month plus one 25,000-email block at $20), and the per-message economics only become competitive above roughly 100,000 emails per month. For WordPress sites under that volume that are not already running Mailchimp for marketing, Postmark, SMTP2GO and Brevo are usually the better defaults.
See nanoPost’s Mailchimp Transactional Email service review for the full pricing comparison and DNS authentication setup. That review covers the “should we use Mandrill at all” question; this one covers “we are using Mandrill, what plugs us in”.
Assessment
Miller Media maintains the code actively. The wp.org listing shows steady releases through 2026 (1.6.2 in February, then 1.6.3 through 1.7.0 in November, with fallback, header and template fixes), the PHP 8.1 baseline and WordPress 7.1 testing match a current managed-hosting environment, and the GPL 2.0 licence and public repository keep the option to fork further if Miller Media steps back. The plugin is one of the few single-provider mailers in the WordPress ecosystem that survives the discontinue-the-original cycle on community maintenance rather than vendor renewal, and the maintenance record is the part of the case that has changed most since the original Mailchimp release.
The plugin does not change the case for Mailchimp Transactional itself. That decision lives one layer up.
Verification
This review verified the plugin’s current version, install count, listing rating, PHP and WordPress requirements, hook list, code example, and changelog against the wp.org listing at wordpress.org/plugins/send-emails-with-mandrill/, the readme.txt and source in the Miller-Media/send-emails-with-mandrill GitHub repository, and the publication’s own Mailchimp Transactional Email service review for platform-level claims. Plugin data as of August 2026; tested against version 1.6.2 (wp.org last-updated 2026-02-17). The fallback rules, hook list, template setting, wpMandrill::mail() behaviour and tagging were re-verified against the 1.7.0 source and changelog in November 2026 (wp.org last-updated 2026-11-13). Mailchimp Transactional (Mandrill) re-verified as an active Mailchimp product at mailchimp.com/developer/transactional/.
For the broader setup the plugin slots into, see how to set up WordPress email.
Corrections
- 2026-11-16: an earlier version said
wpMandrill::mail()bypasses thewp_mailfilter. It runs that filter on every call; what it skips is the native-mailer fallback. - 2026-11-16: an earlier version gave
wc_order_status_completedandcomment_notificationas automatic tags. The plugin tags each send with the name of the function that calledwp_mail(), prefixedwp_, so neither tag is produced. - 2026-11-16: an earlier version listed no test tool and said
WP_DEBUGadds plugin messages. Settings > Mandrill has a test-send form, and the plugin logs errors whateverWP_DEBUGis set to. - 2026-11-09: an earlier version gave Mandrill’s DKIM selector as
mandrill._domainkey. Since March 2024 Mandrill’s DKIM records are two CNAMEs at themte1andmte2selectors. - 2026-10-22: an earlier version described WP Mail SMTP as the only general mailer plugin with a built-in Mandrill mailer; Post SMTP and Easy WP SMTP ship one too.
- 2026-11-05: an earlier version said the WP mail config generator returned a
define()block for this plugin’s constant. The generator does not offer this plugin as a delivery method.

