Post SMTP solves the WordPress email reliability problem: default wp_mail sends through PHP mail, which lands in spam folders or vanishes entirely — a different maintenance headache than what tools like site reset and recovery address, but just as invisible until it bites. The plugin routes transactional email through proper SMTP or email APIs — with OAuth 2.0 authentication for providers like Gmail that reject password auth — and adds an email log so failed notifications (orders, password resets, form submissions) become visible instead of silent. Against minimal SMTP connectors, Post SMTP differentiates on the log-and-resend workflow: every message is recorded, failures flagged, and resendable — the diagnostic loop that makes email debugging solvable rather than guesswork.
The 4.x line expanded the service roster: SMTP.com and Cloudflare as email providers joined in 3.10.0 (the 4.0.1 release rolled back a 4.0.0 beta, landing as a stable point), Sweego API updates, and OAuth verification improvements. For WordPress 7.x sites, email deliverability remains the most common silent failure — Post SMTP is the standard diagnostic-first fix.
Competitive Features
- OAuth 2.0 authentication — Gmail and Microsoft without password-based auth
- Complete email log — every message recorded with status, resending failed ones
- Multiple service integrations — SMTP.com, Cloudflare, SendGrid, Brevo, Mailgun, Amazon SES, Gmail, and more
- Failed email alerts — notifications when critical messages fail
- HTML and attachment support — full-fidelity transactional email
- Priority delivery for critical mail — password resets and orders prioritized
- Diagnostic workflow — test email with configuration validation
Key Features
- SMTP configuration — host, port, encryption (SSL/TLS/STARTTLS) control
- Email log with resend — troubleshooting and re-delivery from the admin
- Service API integrations — API-based sending for major providers
- Fallback SMTP — backup delivery path on primary failure
- Connection validation — pre-flight configuration testing
- Multisite compatible — network email configuration
- WP-CLI support — log operations scriptable
Comparison with Competitors
Post SMTP vs WP Mail SMTP Pro
| Aspect | Post SMTP | WP Mail SMTP Pro |
|---|---|---|
| Interface | Diagnostic-heavy (log, resend) | Setup-focused, polished |
| Email log | Built in, resending | Pro feature |
| Service integrations | Broad set | Broadest set |
| OAuth handling | Mature | Mature |
| Alerts | Failed-email notifications | Email alerts (Pro) |
| Pricing | Free core + Pro | Free core + Pro |
Bottom line: Both are excellent SMTP layers with the same service roster. Post SMTP’s log-and-resend workflow is the stronger diagnostic tool; WP Mail SMTP Pro’s setup wizard is more hand-holding. Debugging-minded admins lean Post SMTP.
Post SMTP vs FacetWP (different category)
| Aspect | Post SMTP | FacetWP |
|---|---|---|
| Layer | Email delivery | Content filtering |
| Shared infra | None | None |
| Complementary | Yes | Yes |
| Overlap | Zero | Zero |
Bottom line: Entirely different layers of the stack — email reliability versus faceted filtering. They coexist on any WordPress site without interaction; the pairing with Post SMTP that matters is your form plugin, whose notifications depend on it.
Recommended Stack — email reliability pairs with form reliability: Post SMTP ensures the notifications from funnel-integrated forms or any form plugin actually arrive, with the log proving delivery.
Official Changelog
Version 4.0.1
Release Date: August 25, 2026
- Rolled back from 4.0.0-beta.1 to stabilize the release line.
Version 3.9.5
Release Date: June 24, 2026
- Tweak: Updated dashboard banners and removed the Extensions screen from the plugin menu.
Version 3.9.4
Release Date: June 3, 2026
- Fix: Resolved failed builds reported by Plugintests.com.
- Fix: Addressed PHP deprecation notices related to using null as an array offset.
Frequently Asked Questions
Why aren’t my WordPress emails arriving?
Almost always the default wp_mail path — PHP mail lacks authentication, and receiving servers reject or spam-filter it. Post SMTP routes through authenticated SMTP or an email API, with the log confirming delivery. Installing it is the first diagnostic step for missing password resets and order notifications.
What is OAuth authentication and why does it matter?
Gmail and Microsoft no longer accept plain password SMTP. OAuth 2.0 lets Post SMTP authenticate via account authorization — required for those providers, and more secure than stored passwords.
What happened with version 4.0.1?
The 4.0.0-beta line was rolled back, landing 4.0.1 as a stable point after 3.10.0’s service additions (SMTP.com, Cloudflare). The rollback pattern shows conservative release management for infrastructure software.
Can failed emails be resent?
Yes — the email log records every message with status, and failed messages resend from the admin. The failed-email alert option notifies you when critical mail (password resets, orders) fails rather than failing silently.
Does it work on multisite?
Yes — network-level configuration covers subsites, with the log accessible for diagnosing email across the network.
Leave a Reply