WordPress.org’s Free SMTP Plugin: Should You Switch?

On 16 November 2026 the WordPress.org Plugins Team announced a plugin called SMTP. It’s free, it’s listed under the author “WordPress.org”, and it does one job: send your site’s email through a proper mail server instead of hoping the web server can do it.
Most site owners only notice mail problems when a client asks “did you not get my form?” So we installed it on our test site, sent mail through it, broke it on purpose, and read the code. Here’s what it is, what it isn’t, and who should switch from WP Mail SMTP, FluentSMTP or Post SMTP.
Last updated 18 November 2026. Tested with SMTP 1.2.0 on WordPress 7.0.2 and PHP 8.4.26, sending to Mailpit, a local mail catcher, so nothing left our machine.
Why WordPress email fails without SMTP
When WordPress sends an email (a password reset, a WooCommerce order, a contact form notification) it calls wp_mail(). Out of the box, that hands the message to PHP’s mail() function, which passes it to whatever mail program happens to live on your web server.
Two things go wrong with that. Plenty of hosts switch the mail program off or limit it. And even when it works, the message leaves from a server that has no permission to send for your domain. Gmail and Outlook check for that permission (the SPF, DKIM and DMARC records, which are basically a signed note saying “this server may send for example.com”). No note, and your email lands in spam or quietly disappears.
SMTP fixes it by sending through a real mail account or service (your host’s mail server, Google Workspace, Brevo, Amazon SES and so on) that logs in and is allowed to send for you. The announcement puts the failure mode nicely: “WordPress fails quietly.”
What the new plugin is (and isn’t)
It’s not WordPress core. It’s an ordinary plugin you install from the directory, with the slug smtp. Version 1.2.0 needs WordPress 6.3 and PHP 7.4, and its readme says “Tested up to: 6.9”. It worked fine on 7.0.2 for us.
It’s also not something the Plugins Team will look after. In the announcement’s own words: “The Plugins Team has started this plugin, but it doesn’t belong to the team, and the team doesn’t provide support for it.” Help comes from the community, the support forum and the GitHub repo.
The slug isn’t new either. It belonged to an older plugin called SMTP, maintained for years by Sorin Iclanzan, who agreed to hand it over. If you ran that one, you get this version as a normal update. Host, port, encryption and username come across automatically, but the old plugin encrypted passwords with mcrypt, which PHP dropped in 7.2, so expect a notice asking you to type the password again.
Why it took this long
People have asked for SMTP settings in core for a long time. Ticket #7284, opened in 2008, was closed as “wontfix” by Andrew Nacin around 2010. Ticket #29069, a 2014 patch proposal, was closed as “maybelater” around 2016 by Dion Hulse (dd32), who wrote: “WordPress follows the Decisions, Not Options philosophy. WordPress users shouldn’t be given options which they don’t actually need.” The new announcement agrees: “Core’s long-standing position is that this belongs in plugin territory, and we agree.” So this is the compromise. Still a plugin, but a neutral one with no upsells.
What’s inside
We downloaded the 1.2.0 zip and read through it. The short version:
- One provider. The only built-in option is “Generic SMTP”: host, port, encryption (None, SSL or TLS), username, password, From email and From name. Developers can add more through a
smtp_providersfilter. There’s no API sending yet. The readme says HTTP API providers are “Not yet” supported, and the announcement calls that layer “the next big step”. - Constants.
SMTP_HOST,SMTP_PORT,SMTP_ENCRYPTION,SMTP_USER,SMTP_PASSWORDandSMTP_FROM_EMAILinwp-config.phpoverride the screen, so the password never sits in the database. - An email log. Its own table,
wp_smtp_logs, with seven columns: id, created_at, recipient, subject, status, error and provider. No body, no headers, no attachments. A daily job deletes rows older than 30 days (developers can change that with a filter). - Alerts. One channel ships: Slack, through an incoming webhook. At most one alert every 15 minutes, with failures in between counted in the next one. Developers can register more channels with
smtp_alert_channels. - WP-CLI.
wp smtp status,wp smtp testandwp smtp settings set. It refuses passwords typed as arguments, since they’d land in your shell history.
Everything lives under Tools > SMTP, in four tabs: Email log, Settings, Test and Alerts.
What we saw when we tested it
We pointed it at Mailpit on 127.0.0.1 port 1025, no login, no encryption:
wp smtp settings set host=127.0.0.1 port=1025 encryption=none auth=0
wp smtp test [email protected]
Success: Test email sent to [email protected].
Then we sent a real Contact Form 7 submission. Both showed up in Mailpit, and the log got a row for each, status sent, with the recipient and the subject line. The visitor’s message wasn’t anywhere in the log, exactly as promised.
Then we broke it. We changed the port to 1026, where nothing listens, and sent again.
- The CLI test failed with exit code 1 and
Error: SMTP Error: Could not connect to SMTP host. Failed to connect to server. Adding--connection-logshowed the real cause underneath:Connection refused (111). - The second form submission got CF7’s “There was an error trying to send your message. Please try again later.” on screen, and a log row with status
failedand the same SMTP error. - The Test tab in wp-admin went one better and added a plain-English hint: “The server could not be reached. Check the host and port. Port 465 needs SSL and port 587 needs TLS. If they are correct, your hosting company may be blocking the port, so try 587 or ask them.”
- Every admin screen showed a red notice: “SMTP: 4 emails failed to send in the last 24 hours.” with a “View failed emails” button.
- No Slack alert, because we hadn’t set a webhook. Without one, the admin notice is your only warning, and you only see it when you log in.
Two things worth knowing from that. First, the log tells you that a contact form email failed, not what the person wrote. If your form plugin doesn’t save entries (Contact Form 7 doesn’t on its own, more on that in does Contact Form 7 store data), that message is gone. Second, “sent” only means the mail server accepted it. A bounce later on doesn’t show up.
One cleanup gotcha: we removed it with wp plugin delete smtp, and the log table and three settings stayed in the database. WP-CLI’s delete just removes files. The plugin’s uninstall routine (which drops the table) runs when you delete from the Plugins screen or use wp plugin uninstall.
How it compares
We checked each cell below against the plugin’s current readme on WordPress.org (WP Mail SMTP 4.10.4, FluentSMTP 2.4.5, Post SMTP 4.0.3). We only tested SMTP itself. “Not checked” means the readme doesn’t say and we didn’t install it to find out.
| SMTP 1.2.0 | WP Mail SMTP (Lite) | FluentSMTP | Post SMTP (free) | |
|---|---|---|---|---|
| Paid version | No | Yes (Pro) | No, readme says “No Pro Version” | Yes (Pro) |
| Email log in the free plugin | Yes, metadata only, 30 days | No, Pro only | Yes, with headers, body and server response | Yes (“Detailed Email Logs”) |
| Failure alerts in the free plugin | Slack | No, Pro only | Telegram, Slack, Discord, Pushover | Email, Slack, webhook, Chrome extension, mobile app (SMS and Teams are Pro) |
| API sending (not just SMTP) | No, SMTP only | Yes, 14 named mailers in Lite; Microsoft, Amazon SES and Zoho are Pro | Yes, 14 API connections | Yes; Microsoft 365 one-click, SES and Zoho via Pro |
| Backup connection if the main one fails | No | Pro only | Yes | Readme lists it as a feature and under Pro; not checked |
| Resend failed emails | No | Pro only | Yes | Pro |
| WP-CLI | Yes (tested) | Not checked | Yes | Not checked |
| Credentials in wp-config.php | Yes | Not checked | Yes | Not checked |
| Active installs (wp.org) | 600+ | 4,000,000+ | 700,000+ | 300,000+ |
Should you switch?
Switch, or at least try it, if you send through plain SMTP (your host’s mailbox, Google Workspace SMTP, Brevo’s SMTP relay) and you’re on WP Mail SMTP Lite. You’d gain a free failure log and Slack alerts, and you’d lose the setup wizard and upgrade prompts. It’s also a sensible default for client sites: small, boring, no upsells.
You already switched if you ran the old SMTP plugin. Check Tools > SMTP and re-enter the password if it asks.
Stay where you are if:
- You send through a provider’s API (Amazon SES API, Gmail or Microsoft 365 sign-in, Postmark), or your host blocks SMTP ports. This plugin can’t do that yet.
- You rely on reading or resending full emails from the log. FluentSMTP stores bodies and resends; this one deliberately doesn’t. (That’s a privacy upside too: no customer messages piling up in your database.)
- You need a backup connection, or alerts somewhere other than Slack.
- You’re on Post SMTP for the phone app. Nothing like it here.
Whatever you pick, run one plugin that changes how mail is sent, not two. Two fighting over wp_mail() is a classic cause of “it worked yesterday”. If you’re chasing a specific Contact Form 7 problem, our guide to Mail (2) not sending covers the usual suspects.
Where Trinity Forms fits
Full disclosure: Trinity Forms is ours. It’s a form builder, and it doesn’t send mail itself, so you still need SMTP. The SMTP plugin fixes the sending. What a form plugin can add is tying each failure to the entry it belongs to, which a site-wide log can’t do.
- Every entry is saved, so a failed email never loses the message.
- Each entry keeps a note of every email it sent and, when one couldn’t go out, the reason.
- It warns you when form emails are failing.
- Its test email shows why a send failed.
- Once mail is fixed, “Resend notifications” sends the ones that didn’t go out.
It needs PHP 8.2 or newer, and it’s a free download from our site. For a wider checklist that works with any form plugin, see how to know if a WordPress form email failed.
Frequently asked questions
Is the WordPress.org SMTP plugin part of WordPress core?
No. It is a normal plugin with the slug smtp, started by the Plugins Team and maintained by the community. The Plugins Team says it does not provide support for it, and core has long said SMTP belongs in plugins.
Does the SMTP plugin store the content of my emails?
No. Its log keeps the date, recipient, subject, status, error and provider for each email. The message body, headers and attachments are never stored, and log rows are deleted after 30 days.
Can I replace WP Mail SMTP or FluentSMTP with it?
If you send through a plain SMTP server, yes, and you get a free failure log and Slack alerts. If you send through a provider API such as Amazon SES or Gmail sign-in, need full email bodies in the log, resending or a backup connection, stay with what you have for now.