On Page Navigation
On Page Navigation
MountDev Cloudflare Email SMTP is a free plugin that sends every WordPress email through Cloudflare Email Service instead of your web server. It replaces wp_mail, so core notices and plugin messages both leave over an authenticated connection. You get a full send log, a from name and from address you control, and a test send that confirms the setup before a customer discovers it is broken. The plugin is free. Cloudflare's sending service is not.
Small plugin, narrow job
Most SMTP plugins support twenty providers at once, and the settings screen shows it. This one connects to Cloudflare Email Service and nothing else, so there is no provider picker to wade through and the fields you fill in are the ones Cloudflare actually asks for. It is free on the Plugin Directory, and nothing is held back for a paid tier. Here is what that looks like in practice.
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. This one targets Cloudflare Email Service alone, so the settings screen asks for what Cloudflare needs and then stops.
There is no pro version and no license key. Nothing described on this page is quietly switched off until you upgrade, because all of it ships in the plugin you install from the Plugin Directory. 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.
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. The plugin tracks what Cloudflare ships, and the send log lets you watch how your own mail is actually behaving.
The usual fix for a wrong sender name is a filter pasted into your theme's functions file. It works until the theme updates, and then it is gone and nobody remembers why the emails suddenly changed. Here the sender settings live in the plugin, so a theme update leaves them alone.
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. There is a test send because setup fails in predictable ways, and there is a log because the ticket we answer most often is somebody saying an email never arrived.
How it compares
A general SMTP plugin supports every provider at once, and that is a real strength while you are still choosing one. Once you have picked Cloudflare, the same breadth becomes configuration you will never use. Here is where the two approaches part ways.
We ask for the specific things Cloudflare requires, down to the token username it expects. A generic form gives you a host, a port and a password field, then leaves you to work out for yourself what Cloudflare wants in each one.
Every feature is in the free plugin. Elsewhere the logging, or the second sender, or the backup route sits behind a paid license, which makes the free version you installed a trial of the one you actually wanted.
Your send history stays in your own WordPress install, where you can query it like any other table. Push that log to a hosted dashboard, as several competitors do, and you have picked up another account, another login, and a copy of your email metadata on somebody else's server.
You set how long log rows survive. Without a retention control the table simply grows, and the way you usually find out is a database backup that has doubled in size on the busiest site you run.
A test send from the settings screen surfaces a bad token or an un-onboarded domain while you are still sitting in that screen. Without one, you find out later, from a customer whose password reset never came.
We say up front that nothing sends until you have a Workers Paid plan and an onboarded domain. Gloss over a provider prerequisite and you end up debugging WordPress while the actual problem is sitting on your Cloudflare account.
Who this fits
This is a narrow tool for people who have already decided to send through Cloudflare. If you are still comparing providers, install a multi-provider plugin instead. It is the better fit for where you are, and this one will only get in your way. But if your DNS and your Workers already live on Cloudflare, keeping email there takes one more vendor out of the stack.
The process
Three steps, and only the first one takes any real thought. Get the Cloudflare side ready, connect the plugin, then confirm it with a test send. After that WordPress carries on exactly as before, except that everything it sends now leaves through Cloudflare.
1
Before WordPress enters the picture you need a Cloudflare account on the Workers Paid plan, the domain you will send from onboarded for Email Sending, and an API token with permission to send. None of that is something the plugin can do on your behalf, which is also why most setup problems start here. Have the token in hand before you move on.
2
Install from the Plugin Directory, activate, and open the settings screen. Point it at Cloudflare's SMTP host on port 465, use api_token as the username, and paste your token as the password. Then set the from address and from name you want the whole site to use, and save. Nothing else in WordPress has to change.
3
Send a test message from the settings screen. 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. Either way, the log starts recording from that point on.
Pricing
Plan
DETAILS
Testimonials
Our team handles daily updates to the WordPress core, ensuring your site is always running the latest and most secure version. These updates include performance tweaks and database optimizations, helping your site stay fast and stable. We also clear cached data and proactively fix issues before they affect users. With us managing your updates, you never have to worry about falling behind or breaking your site.
Joe Q.
I can't say enough about how grateful I am to [Cascadia] for helping me resolve my tech problems. I was in a real bind, and [they] calmly and cooly fixed the problem--something two other tech support folks could not do. [They are] gonna be my go-to from now on.
Sandi S.
Our team handles daily updates to the WordPress core, ensuring your site is always running the latest and most secure version. These updates include performance tweaks and database optimizations, helping your site stay fast and stable. We also clear cached data and proactively fix issues before they affect users. With us managing your updates, you never have to worry about falling behind or breaking your site.
Naomi T.
[Cascadia] is amazing! They are so patient and explains things in such a clear way. I'm very grateful to them for making me feel more confident in my work with the CRM. Can't recommend them enough!!
Aventurina K.
Andrew K.
Carl B.
Everything in the plugin
