Meow Mailer is a brand-new free WordPress mailer plugin from Jordy Meow, the developer behind AI Engine, Meow Gallery, and Meow Analytics. It is the plugin to look at if the deciding factor for your site is a stated, permanent commitment to no paid tier and no email tracking. The vendor puts the first commitment in the plugin description directly: “There is no Pro version. The log, the alerts, all fourteen providers: everything is free, and everything stays free.” The tracking commitment sits next to it: “Your recipients are not watched, and that will never become a paid feature.” Both are unusual enough in this category to be the reason a reader would pick this plugin over the more established options.
That is the framing. The plugin itself is a first release, version 0.2.5 as of September 2026, with 600-plus active installs and a 4.9 rating across twelve reviews on wordpress.org. It is a very small, very new entrant in a category dominated by 4-million-install incumbents. Under the hood it does what any WordPress mailer plugin does: it takes over wp_mail() and hands every outgoing message to a provider you have configured, with a log, alerts, a fallback provider, and OAuth 2.0 for the three provider families where it matters (Gmail and Google Workspace; Microsoft 365 and Outlook; Zoho Mail).
For the WordPress operator reading this because the “no Pro, no tracking” line landed, Meow Mailer is worth trying if you also do not need per-sender routing and are comfortable running a pre-1.0 plugin on a 600-site install base. For an operator who wants the same philosophy on a plugin with three orders of magnitude more installs and a mature codebase, FluentSMTP covers most of the same ground. For a first-time mailer install on a single WordPress site, WP Mail SMTP still owns the setup-wizard advantage.
What ships in the plugin
Fourteen transports come out of the box: generic SMTP, ten API providers (Mailgun, Brevo, SendGrid, Amazon SES, Postmark, SMTP2GO, Mailjet, Resend, MailerSend, Maileroo), and three OAuth integrations covering Gmail with Google Workspace, Microsoft 365 with Outlook, and Zoho Mail. The Zoho Mail OAuth flow and the Maileroo API integration are the two entries worth calling out here. Neither is in FluentSMTP’s free tier, and both are recent enough that the larger plugins have been slow to add them.
The feature most operators reach for first is the email log. Every send is recorded with recipient, subject, headers, body, attachments, and delivery status, including the Cc, Bcc, and Reply-To rows that the smaller SMTP-only plugins in this category typically drop. Failed sends can be re-attempted from the log directly, one click. Around the log sit the pieces that decide what happens when a send does fail: a fallback provider that engages on primary-provider failure (WordPress’s own default wp_mail() path can serve as the fallback for a zero-setup safety net, at the cost of the lower deliverability that motivated installing the plugin in the first place), failure alerts by email, and webhook alerts to Slack, Discord, and Microsoft Teams. A weekly summary email rolls up delivery statistics for operators who prefer to review deliverability on a cadence rather than a per-incident push.
Setup and day-two operations get their own group. A one-click importer detects an existing WP Mail SMTP or Easy WP SMTP configuration and lifts credentials across, including from wp-config.php constants when they are the source of truth. An offline mode captures every send to the log without transmitting it, which is the mode operators reach for on staging environments where the last thing anyone wants is a partially-configured plugin bcc’ing production customers on a data-refresh from prod. A background-send option returns the page request immediately and dispatches the send asynchronously, so mail-server latency does not extend page-load time. This is single-message backgrounding, not a persistent spool queue. On multisite, a Shared Settings mode on the main site applies one provider configuration to the entire network; the per-site logs stay per-site. The log itself exports to CSV and filters across dates, providers, statuses, and recipients.
Credential handling picks up the deployment-hardening features. Stored credentials can be encrypted, keyed off WordPress security keys, an option added in 0.2.5; the vendor flags the trade-off directly in the FAQ, that if the security keys change (a migration, a security plugin rotating them) the encrypted credentials become unreadable and have to be re-entered. wp-config.php constants stand alongside the database as an alternative credential store, useful for multi-environment deployments where credentials should not live in the database at all.
The plugin also warns on three of the most common causes of a mailer plugin appearing to do nothing: another plugin bypassing wp_mail(), a form plugin overriding the From address, and a From address on a different domain than the site. A dashboard health-analysis tab summarises recent send patterns and flags issues, which is unusual for a mailer plugin in this category and too new to weigh heavily against the plugin’s established features, but worth naming.
What it deliberately does not do
The absences are as much of the product as the features. Each is a reason a specific operator profile picks a different plugin.
Per-sender routing is not offered. The plugin uses one active provider by design, with a fallback that engages only on failure, so the FluentSMTP pattern of transactional mail through Postmark and marketing mail through SendGrid needs a different plugin. Open and click tracking are not offered, and the vendor states they will not be, so this is a hard product-line decision rather than a Pro-tier upsell; vendors that build a business on click-tracking sit in a different category, and Meow Mailer will not follow them into it. A persistent send queue is not offered. Background send returns the request quickly, but there is no Action Scheduler-style spool that survives a PHP fatal or restarts on the next cron tick, so sites that send mail in bursts large enough to require a real queue face the same PHP-timeout constraints as any non-queueing mailer plugin.
Push-notification alerts to a mobile app are not offered. Post SMTP is the only plugin in the category that ships this, and it stays the pick for operators who want alerts on the channel they actually watch away from a desk. A paid support contract is not offered, because there is no Pro tier to hang it off. Support runs through the 
wordpress.org plugin forum and Meow Apps’s channels; response is best-effort, no SLA.
The “no Pro, no tracking” question
A plugin that gives away a feature set its largest competitor charges $99 a year for, published by a small established indie developer, invites the same question the FluentSMTP answer settled: how does this sustain, and what is the catch?
The Meow Apps commercial portfolio sits in adjacent products. 
AI Engine is the paid anchor at $79, with Code Engine Pro and SEO Engine Pro alongside it and a stack of AI Engine add-ons. Meow Gallery, Meow Analytics, and Meow Lightbox sit in the free product line, and Meow Mailer joins them. The pattern is the same one WPManageNinja runs with FluentSMTP against Fluent Forms Pro and FluentCRM: the mailer is not directly monetised; the brand value feeds the products one tier up.
The tracking commitment is a separate line. Most free mailer plugins in the category avoid tracking by omission; Meow Mailer avoids it by declaration. The distinction matters for operators who have been burned before by a free plugin adding a tracking tier under new ownership: a stated permanent commitment is not a guarantee, but it is more than silence.
Where Meow Mailer stands against the alternatives
The comparison that matters most is against FluentSMTP, because the two plugins solve the same problem with the same commercial model. FluentSMTP has 600,000-plus active installs to Meow Mailer’s 600, a mature 2.4.0 release to Meow Mailer’s pre-1.0 0.2.5, and per-sender connection routing that Meow Mailer lacks. Meow Mailer has Zoho Mail OAuth and Maileroo that FluentSMTP does not, a weekly summary email that FluentSMTP does not, and a stated permanent no-tracking commitment where FluentSMTP’s silence on the question leaves the position implicit.
Against WP Mail SMTP: the four-million-install setup wizard remains the reason a first-time operator on a single site picks it. Meow Mailer does not have the wizard, does not have the four-million-install forum and community around it, and does not have the free coverage for Amazon SES, Microsoft 365, or Zoho Mail that WP Mail SMTP gates behind Pro. Meow Mailer has those integrations in the free tier because it does not have a Pro tier to gate behind.
Against Post SMTP: Meow Mailer does not compete on push-notification alerts. Operators who need to hear about a broken order-confirmation flow on a phone stay with Post SMTP.
Against the official single-provider plugins (the SMTP2GO plugin, the Mailgun plugin): Meow Mailer trades install simplicity for provider portability. Operators who want to keep the provider account decoupled from the plugin decision get that with Meow Mailer; operators who want the in-admin provider-stats tab that the official plugins ship do not get it here.
Assessment
Meow Mailer earns its place on a WordPress site whose operator has read the “no Pro, no tracking, ever” positioning and finds it decisive. The feature set is enough to run the site’s transactional email through a professional provider, log every send, resend from the log, and get alerted when delivery fails. Those are the four things most operators actually need from a mailer plugin. The absence of per-sender routing narrows the fit; the pre-1.0 version number and the 600-site install base narrow it further. Neither is a defect for the operators the plugin is right for.
The recommendation calibrates to installed base and maturity: Meow Mailer for the specific-profile operator described above; FluentSMTP for the general free-and-feature-rich case; WP Mail SMTP for the first-time single-site install where the wizard earns its keep; Post SMTP when push-notification alerts are the operational requirement.
The plugin is worth watching. A Meow Apps developer with an existing paid-product commercial model, publishing a mailer plugin at fourteen releases in roughly ten weeks, is unusually plausible ground for a plugin that keeps its stated commitments. The next data point is the 1.0 release; the one after that is how the install base moves once the plugin has been listed on wordpress.org for a full quarter.
For the broader setup the plugin slots into, see how to set up WordPress email.
Plugin data verified September 2026 against wordpress.org/plugins/meow-mailer and meowapps.com/meow-mailer. Tested against version 0.2.5.