Short version: most “email template” plugins for WordPress wrap every email your site sends through one global header and footer — including the newsletters and campaigns you send with FluentCRM. The result looks broken: your marketing email arrives stuffed inside your transactional receipt design. Here is the approach I actually tested to apply the template to only the senders I choose, and leave everything else clean.
Why one template ends up on every email
WordPress sends all of its mail through a single function, wp_mail(). Email-design plugins like Email Templates Customizer and Designer or WP HTML Mail hook into that function and wrap the message body in your header and footer before it leaves. Because they hook wp_mail() globally, they wrap everything that passes through it.
The catch: FluentCRM also sends its campaigns and automations through wp_mail(). So your carefully designed newsletter gets double-wrapped inside your transactional template. The same happens to password resets, WooCommerce or EDD receipts, and contact-form notifications.
Why the plugin’s built-in “skip newsletters” option isn’t enough
Some template plugins try to auto-detect builder emails and skip them. Email Templates, for example, scans the PHP call stack for a FluentCRM or Elementor path and skips wrapping when it finds one. Two reasons that misses real emails:
- It only looks a few frames deep. The check uses
debug_backtrace()limited to about 10 frames. When FluentCRM sends from a background cron job, the relevant frame is usually deeper than that, so the detection never sees it. - Pro add-ons live in a different folder. FluentCRM’s premium features ship in a folder named
fluentcampaign-pro, which doesn’t match a search for “fluent-crm” — so Pro campaigns slip straight through.
That’s why you can have “skip FluentCRM” logic in place and still watch the template land on a campaign.
The approach that works: gate by sender, not by guesswork
Instead of trusting a backtrace, decide per email using two signals you can actually rely on:
- The
Fromaddress. Whitelist the exact sender you want branded (for example[email protected]) and disable the template for everyone else. - A FluentCRM marker. Tag every FluentCRM email with a custom header so you can exclude it even if a campaign is ever sent from your branded address.
Most good template plugins expose a filter to disable themselves per email. Email Templates has mailtpl_disable_for_email; WP HTML Mail has haet_mail_use_template. Here is the version I tested for Email Templates:
<?php
add_filter( 'fluent_crm/email_headers', function ( $headers ) {
$headers[] = 'X-Mailer-Origin: FluentCRM';
return $headers;
}, 999 );
add_filter( 'mailtpl_disable_for_email', function ( $disabled, $args ) {
$headers = isset( $args['headers'] ) ? $args['headers'] : array();
$lines = is_array( $headers ) ? $headers : explode( "\n", str_replace( "\r\n", "\n", (string) $headers ) );
$from = '';
foreach ( $lines as $line ) {
if ( stripos( $line, 'x-mailer-origin: fluentcrm' ) !== false ) {
return true; // never template FluentCRM
}
if ( '' === $from && stripos( $line, 'from:' ) === 0 ) {
$from = preg_match( '/<([^>]+)>/', $line, $m ) ? trim( $m[1] ) : trim( substr( $line, 5 ) );
}
}
// Keep the template ONLY for this address; disable everywhere else.
return ( strtolower( trim( $from ) ) !== '[email protected]' );
}, 10, 2 );
Returning true skips the template for that email. The logic reads plainly: if it’s a FluentCRM email, skip it; otherwise keep the template only when the From address is your one branded sender.
Using WP HTML Mail instead
If you use WP HTML Mail, the equivalent switch is haet_mail_use_template, which passes the recipient and subject (but not the From address):
<?php
add_filter( 'haet_mail_use_template', function ( $use, $to, $subject ) {
// From isn't passed here, so gate by $to / $subject,
// or capture From in a wp_mail filter and read it back.
return $use;
}, 10, 3 );
Because From isn’t available there, capture it yourself in a wp_mail filter and store it, or gate by recipient and subject if that is enough for your case.
No disable filter? Do it yourself
If your template plugin has no per-email hook, skip the plugin and add the header and footer yourself, conditionally, on wp_mail:
<?php
add_filter( 'wp_mail', function ( $args ) {
$headers = isset( $args['headers'] ) ? $args['headers'] : array();
$lines = is_array( $headers ) ? $headers : explode( "\n", str_replace( "\r\n", "\n", (string) $headers ) );
$from = '';
foreach ( $lines as $line ) {
if ( '' === $from && stripos( $line, 'from:' ) === 0 ) {
$from = preg_match( '/<([^>]+)>/', $line, $m ) ? trim( $m[1] ) : trim( substr( $line, 5 ) );
}
}
if ( strtolower( trim( $from ) ) !== '[email protected]' ) {
return $args; // only brand this sender
}
$head = '<div style="background:#0b0b0b;padding:20px;text-align:center;color:#fff;">Your Brand</div>';
$foot = '<div style="padding:16px;text-align:center;font-size:12px;color:#888;">Your Brand · yoursite.com</div>';
$args['message'] = $head . $args['message'] . $foot;
$args['headers'] = $lines;
$args['headers'][] = 'Content-Type: text/html; charset=UTF-8';
return $args;
}, 99 );
Test it before it touches real inboxes
Don’t validate this by emailing yourself and squinting. Spin up a throwaway WordPress with a fake SMTP catcher and send one test email per sender. I use Docker and Mailpit:
services:
wordpress:
image: wordpress:php8.3-apache
ports: ["8080:80"]
environment:
WORDPRESS_DB_HOST: db
WORDPRESS_DB_USER: wp
WORDPRESS_DB_PASSWORD: wp
WORDPRESS_DB_NAME: wp
depends_on: [db]
db:
image: mariadb:11
environment:
MARIADB_ROOT_PASSWORD: root
MARIADB_DATABASE: wp
MARIADB_USER: wp
MARIADB_PASSWORD: wp
mailpit:
image: axllent/mailpit
ports: ["8025:8025", "1025:1025"]
Then add a tiny must-use plugin so WordPress hands its mail to Mailpit instead of the real world:
<?php
// wp-content/mu-plugins/mailpit.php
add_action( 'phpmailer_init', function ( $m ) {
$m->isSMTP();
$m->Host = 'mailpit';
$m->Port = 1025;
$m->SMTPAuth = false;
} );
Send one email from each sender, then open the Mailpit inbox at http://localhost:8025 and look at the raw HTML. When your branded sender shows the template and everything else comes through clean, you’re done — and you proved it without spamming a single real contact.
Gotchas worth knowing
- Update the plugin first. Per-email disable filters are relatively new. On an old version the filter simply doesn’t exist and your snippet quietly does nothing.
- Read From from the headers, not a fallback. Don’t resolve the sender through
wp_mail_fromas a fallback. If you also force a default From elsewhere, header-less emails get misclassified as your branded sender and wrongly wrapped. - Header-less emails. Core WordPress mail such as password resets often has no explicit From. With a strict whitelist those stay un-templated, which is usually what you want. If you need them branded, send them from your branded address at the source.
- Run the snippet everywhere. FluentCRM sends on cron, not inside wp-admin. If you use a snippets plugin, set the scope to run site-wide, not admin-only, or campaigns never hit your filter.
FAQ
Will this stop FluentCRM emails from sending?
No. It only stops the design template from wrapping them. FluentCRM still sends its own email exactly as you designed it.
Can I brand more than one sender?
Yes. Swap the single-address check for an array of allowed senders and use in_array() against the detected From.
Does this work with any SMTP plugin?
Yes. The template decision happens at wp_mail(), before the SMTP layer (FluentSMTP, WP Mail SMTP, and the rest) delivers the message, so your routing is unaffected.
That’s the whole trick: stop letting the template decide for you, and gate it on the one signal you can trust — who the email is from.