Post SMTP alternative
The Post SMTP Alternative, Run for You
A free WordPress plugin that sends your WordPress email through Cloudflare Email Service. Small plugin, narrow job.
What makes it different
- One provider, not twenty
- Free with nothing held back
- Honest about the beta
- No snippets in functions.php
- Your log, your database
- Built by people who run sites
Cascadia vs Post SMTP at a Glance
Three Questions That Decide It
Is Your Site on Cloudflare Workers Paid?
Will you send through a service still in beta?
How Many Mail Providers Will You Use?
Side by Side
| Post SMTP | Cascadia | |
|---|---|---|
| Mail providers | A choice of many, picked in settings | –Cloudflare Email Service only |
| Settings screen | –Settings for every supported service | Asks only what Cloudflare needs |
| Cloudflare plan needed | No Cloudflare account involved | –Workers Paid on the sending account |
| Service maturity | –Depends on the provider you pick | –Cloudflare Email Service is in beta |
| Email log | –May live in an outside dashboard | A table in your own WordPress database |
| From name and address | –Depends on how it is set up | Set once, site-wide, no snippets |
Mail Providers
Settings Screen
Cloudflare Plan Needed
Service Maturity
Email Log
From Name and Address
What Ships as Standard Here
Everything in this list ships as standard.
- Replaces wp_mail Completely
- Cloudflare Email Sending API
- Custom From Address
- Custom From Name
- Test Send And Verification
- Full Email Log
- Log Retention Controls
Where the Service Earns Its Keep
The plugin is deliberately narrow. It carries configuration for Cloudflare Email Service and nothing else, and it keeps a full email log on your own site, so a question about a missing message has somewhere to be answered.
Built by People Who Run Sites
We manage WordPress sites for a living, and this began as an internal tool for a problem we kept running into. It shows in what got built.
One Provider, Not Twenty
A multi-provider SMTP plugin has to carry configuration for every service it supports. Most of that surface is noise on your site, because you are only ever going to use one of them.
Free with Nothing Held Back
We built it for our managed clients, who needed the thing to work. It was never meant to be the front end of a paid tier.
Honest About the Beta
Cloudflare Email Service is still in beta, and Cloudflare says its APIs may change. That belongs on this page, not in a support conversation after you have already moved a store’s receipts onto it.
Who This Comparison Is For
Developers Who Want Mail Out of PHP
If you would happily never look at your host’s sendmail configuration again, this is for you.
Sites Already Running on Cloudflare Workers
Bringing in a separate email vendor adds a bill, an API key, and one more dashboard to keep track of. Email Sending is available on the Workers Paid plan you already have, so use it.
WooCommerce Stores Losing Order Receipts
Routing wp_mail through an authenticated service handles the delivery side. The log handles the other half, which is knowing which orders got their email and which did not.
Choose Post SMTP if
- You want a choice of mail providers in one plugin
- You are not on Cloudflare Workers Paid and do not plan to be
- You would rather not send through a service still in beta
Choose Cascadia if
- Your site already runs on Cloudflare Workers Paid
- You want one provider and a short settings screen
- You want the email log in your own database
How the Plugin Sends Your WordPress Email
Four steps, and only the second one takes any real thought. Get the Cloudflare side ready, connect the plugin, then confirm it with a test send.
- 1
We Assess Your Current Setup
First we look at how things run today: what you already pay for, what is configured where, and which parts are actually causing you trouble.
- 2
Get Your Cloudflare Account Ready
Have your Account ID and token in hand before you move on.
- 3
Install and Connect the Plugin
Nothing else in WordPress has to change.
- 4
Run a Test Send and Check the Log
If it arrives, wp_mail is going through Cloudflare and every plugin on the site inherits that immediately. If it does not, the error names the culprit: the token, the domain, or the from address.
What Clients Say About Working with Cascadia
“I’ve always dreaded website management, but Cascadia has done an incredible job with my WordPress site, making it one less thing for me to worry about.”
“I’ve worked with Cascadia for several years now. They are always ready to help in any way I ask and can implement my ideas with ease. A company that values their clients!”
“Cascadia has been great to work with! We recently needed some updates, and Cascadia was quick to get them completed! We highly recommend Cascadia Web Services.”
“Cascadia is very responsive and we’re happy with them as our primary IT vendor.”
“They do great work, been using for years. Prompt responses to requests.”
Ready When You Are
Talk to us about your setupAsk us
Post SMTP Alternative Questions
Straight answers about switching, pricing, and what moves with you.
See Email Delivery for CloudflareStill have a question?
How is Cascadia different from Post SMTP?
The main difference is that this plugin sends only through Cloudflare Email Service, where Post SMTP lets you choose from many providers. It was also built by people who run sites. We manage WordPress sites for a living, and this began as an internal tool for a problem we kept running into. It shows in what got built.
Is the plugin really free?
Yes. The plugin costs nothing, has no paid tier, no license key, and no features held back behind an upgrade. You install it from the WordPress Plugin Directory the same way you install any other free plugin. What is not free is the sending service behind it, which belongs to Cloudflare rather than to us. That distinction matters enough that we cover it in the next answer.
Do I need to pay Cloudflare to use it?
Yes, on Cloudflare’s side. Email Sending is available on the Cloudflare Workers Paid plan, so you need that plan on the account you send from. You also need the sending domain onboarded for Email Sending on the account that owns your API token. The plugin cannot work around either requirement. If you already run Workers Paid, there is nothing further to buy.
What is Cloudflare Email Service?
It is Cloudflare’s email product for developers, combining outbound sending with inbound routing under one service. It is built for transactional mail: password resets, order confirmations, verification messages, and alerts. You can reach it from Workers using a native binding, from any platform over its REST API, or over authenticated SMTP. This plugin uses the REST API, which is what lets ordinary WordPress talk to it without custom code.
How is this different from Cloudflare Email Routing?
Email Routing handles mail coming in, forwarding messages sent to addresses on your domain somewhere else. Email Sending handles mail going out. They sit under the same Cloudflare Email Service umbrella but solve opposite problems. This plugin is concerned only with outbound mail from your WordPress site, so Routing is not required, and switching it on will not make your site’s email start sending.
What do I need before I install it?
Three things. A Cloudflare account on the Workers Paid plan, the domain you intend to send from onboarded for Email Sending on that account, and a Cloudflare API token with permission to send. Have those ready before you install, because the plugin’s job is to use them, not to create them. Setup inside WordPress takes a couple of minutes once the token is in hand.
How do I connect the plugin to Cloudflare?
Install and activate the plugin, then open its settings screen. Enter your Cloudflare Account ID and paste your Cloudflare API token. Set the from address and from name you want the site to use, save, then run the test send. If the test message arrives, WordPress is sending through Cloudflare and you are done.
Will it cover emails from WooCommerce, Contact Form 7, and other plugins?
Yes, as long as the plugin sends through wp_mail, which the overwhelming majority do. Because this plugin replaces wp_mail itself rather than hooking one plugin at a time, anything built on the standard WordPress mail function is covered the moment you activate it. The rare exception is a plugin that opens its own connection and bypasses wp_mail entirely. Those are uncommon.
Why are my WordPress emails not sending in the first place?
Most shared hosts either block outbound mail or send it unauthenticated from an IP with no reputation attached. Mailbox providers see a message claiming to come from your domain with nothing backing that claim, so they drop it or file it as spam. Nothing errors along the way, which is why the site looks fine while receipts and password resets never land.
What does the email log record?
Each entry holds the recipient, the subject, the time the message went out, and the delivery status the send returned. That covers the question you usually have, which is whether the message left at all and when. If a customer says a receipt never arrived, you check the log first and know right away whether to look at your site or at their inbox.
How long are log entries kept?
For as long as you tell the plugin to keep them. Retention is a setting, so you decide how much history is worth holding on to. A low volume site can keep months without noticing. A busy store sending hundreds of messages a day will want a shorter window, because the log lives in your database and an unbounded table gets expensive to carry through every backup.
