Comparison

Custom SMTP vs FluentSMTP.

This is the rare comparison where price decides nothing: both plugins are genuinely, entirely free. The differences live elsewhere, in why each one is free, in what each one considers its job, and in where your credentials travel. Every claim about FluentSMTP below comes from their own site, documentation or listing, checked on 30 July 2026 and linked at the bottom.

01 · Common ground

Where the two
are identical.

More is identical here than in any other comparison on this site, starting with the one thing most SMTP plugins gate: the price of the useful parts.

  • Both replace unauthenticated server mail with delivery through a provider you configure, which is the actual fix for WordPress email.
  • Both are entirely free. No paid tier, no feature gates, no sending limits. Their pledge is in writing: “100% free and open source. We will never monetize it.” Ours is the same, phrased as no paid version to move features to.
  • Both ship the diagnostic core free: an email log with resend, and failure notifications, the two features that answer “did it arrive?”.
  • Both are GPL, installed from WordPress.org, with no account required to send.

02 · The split

Free for two
different reasons.

Neither gratuity is a trick. But they are not the same gratuity, and the difference shapes both plugins.

FluentSMTP is free the way a well-built lobby is free: it belongs to a house. WPManageNinja says so themselves, on the page where they explain the choice: the plugin was built because their own paid products, Fluent Forms, FluentCRM, FluentBooking, needed reliable delivery, and it doubles as a contribution to the ecosystem their customers live in. That is a legitimate model, executed generously, and the plugin gates nothing.

Custom SMTP is free because it is the entire offer of a solo maintainer: there is no suite behind it, no other product it leads to, and nothing else it needs to serve. The visible consequence is scope. FluentSMTP is also infrastructure for marketing email, with several simultaneous connections, per-sender routing, a fallback connection and reporting dashboards; Custom SMTP covers transactional sending, its log and its alerts, and deliberately stops there.

03 · Side by side

Feature by feature,
sourced and dated.

Everything in both columns is free; the differences are in coverage, not in price. Sources for every row are at the bottom of the page.

Comparison · 30 July 2026 both free
FluentSMTPCustom SMTP
Send through your provider15+ connections, SMTP and APIs12 presets + any SMTP server
Amazon SESAccess key + secret key, stored in the database or wp-configAPI with IAM role, no stored keys
Gmail / Google WorkspaceOAuth API: create your own Google Cloud app, authorization redirects via fluentsmtp.comSMTP with an app password, no third party in the flow
Email log, resendLog, resend, reporting dashboardLog, preview, resend, CSV export
Failure notificationsEmail, Slack, Telegram, DiscordEmail, webhook, admin notice
Volume-spike alertsNot advertisedAbsolute hourly and daily thresholds
Multiple connections, routing, fallbackSeveral providers at once, per-sender routing, fallback connectionNot offered
WordPress notification switchesNot advertisedFree, one switch per email
Settings locked in codeCredentials via wp-config constantsEvery setting, PHP constants and environment variables
WordPress 7.0Tested up to 6.9.5; last release December 2025Tested up to 7.0, PHPMailer 7.0.2
PriceFree, pledged never monetisedFree, no paid version

A nuance that cuts their way on Outlook: their Microsoft connection uses the OAuth API, which is not affected by Microsoft’s staged retirement of basic SMTP authentication; our Outlook preset is SMTP and is. The Outlook guide documents that timeline.

04 · Credit where due

What FluentSMTP
does better.

An honest comparison has this section, and not as a formality. If these points decide it for you, take their plugin.

  • Several connections at once. Multiple providers configured simultaneously, routing by sender address, and a fallback connection that takes over when the primary fails. Nothing equivalent exists here.
  • OAuth connections for Gmail and Outlook. API sending survives Google and Microsoft turning the screws on passwords; our presets for those two ride on app passwords and SMTP, with the limits that come with that.
  • Notification channels out of the box. Telegram, Discord and Slack alerts without building anything; our webhook can reach the same places, but you assemble the receiving end.
  • Scale and track record. 600,000+ active installations, 4.8 stars over 388 reviews, and a company with an entire plugin suite standing behind it.
  • Reporting. A delivery dashboard with charts and summaries; our log is a table you filter, by design, but it is a table.

05 · The other side

Where Custom SMTP
is ahead.

The same standard applies in this direction: each point is verifiable, in the code or on the screen.

  • Amazon SES without stored secrets. Sending through the SES API authenticated by the server’s IAM role, no access keys anywhere, is a free feature here; their SES connection asks for an access key and a secret key and keeps them in the database or wp-config.
  • No third party in any flow. Our Gmail preset is SMTP with an app password: nothing transits anyone else’s domain. Their Gmail OAuth setup routes the authorization redirect through fluentsmtp.com, their own documented redirect URI.
  • Configuration as code, completely. Every setting, not just credentials, can be forced from a PHP constant or an environment variable, network-wide on multisite. Their constants cover the connection credentials.
  • Alerts beyond failures. Volume spikes with absolute hourly and daily thresholds, consecutive-failure and failure-rate rules: the compromised-form scenario is covered, not only the broken-password one.
  • WordPress notification switches. Turning off the automatic emails WordPress sends on its own, one by one, ships free here and is not advertised on their pages.
  • Current WordPress, today. Tested against WordPress 7.0 and PHPMailer 7.0.2; their listing declares 6.9.5, with the last release in December 2025.
  • French, completely. The plugin and this entire documentation site exist in both English and French; their documentation is English-only.

06 · The short version

How to
choose.

Two sentences each, no hedging.

Take FluentSMTP if you run several providers at once, want routing and a fallback connection, prefer OAuth API sending for Gmail or Outlook, want Telegram or Discord alerts without wiring a webhook, or already live in the Fluent suite. It is genuinely free and their pledge is public.

Take Custom SMTP if you want one provider configured plainly over SMTP, Amazon SES with no stored keys, every setting forceable from code, spike alerts as well as failure alerts, the WordPress notification switches, and a plugin with no ecosystem attached, in English and in French. That is the whole offer.

Sources, all checked on 30 July 2026: the FluentSMTP site (“Free Forever”, connections, fallback, notification channels, reporting), their “why is it free” page (built for their product suite), their Amazon SES documentation (access key and secret key, storage), their Gmail documentation (Google Cloud app, fluentsmtp.com/gapi/ redirect URI) and the FluentSMTP listing on WordPress.org (installations, reviews, never-monetize pledge, tested-up-to and last release). Facts about Custom SMTP are verifiable in its public code. Found something outdated? Say so on the support forum and this page gets fixed.