The email your store sends, and the proof that it went out.
WordPress hands order confirmations, password resets and receipts to whatever the server happens to offer, and when one of them does not arrive there is nothing left to look at. MevvMail takes the send over instead: it delivers through connections you configure, moves to the next one when the first refuses, retries later rather than giving up, and writes every attempt to a table in your own database. Ten connection types, the failover chain, the log and the WooCommerce order box are all in the free plugin. The log stays on your server — no part of your email is sent to us.
All prices include VAT.
1 USD = 50,1047 ₺ (İşbank rate)
What it does
Each capability exists to remove a specific operational friction.
SMTP, PHP mail(), Brevo, SendGrid, Mailgun, Postmark, SparkPost, Elastic Email, SMTP2GO and Resend. Not one of them is behind a licence and we impose no send limit, because a delivery plugin that rations delivery is selling you the problem back. You use your own account and your own key with each provider.
Every connection has a priority, and the list is walked in that order until one accepts the message. A provider that is rate limiting, out of quota or simply down costs you the attempt, not the email. The whole chain is one row in the log, not three — a single email should not read as three separate failures.
When every connection has refused, the message is queued and tried again after one minute, five minutes and thirty minutes. Three attempts and it stops: an address that does not exist will not start existing on the fortieth try. The retries are scheduled through WP-Cron, so on a quiet site they run whenever the next visitor arrives.
Time, recipients, subject, status, which connection handled it and which part of the site produced it — filterable by status, source and date. It is a table in your own database. Nothing about your email is sent to us: no telemetry, no content scanning, no licence call from the free plugin.
Any entry can be sent again from the list, which is usually faster than asking the customer to trigger the email themselves. Keeping the message body is a setting, and turning it off is a real choice with two consequences: an entry logged without its body cannot be resent, and a failed send is not queued for the retry ladder either — in both cases there is nothing left to send. Retention is yours to set — 7, 30, 90 days or forever.
With WooCommerce active, each order gets a box listing the emails that order produced and how each one went. The delivery question is answered against the order instead of in a log you have to search. Without WooCommerce the plugin works exactly the same; the box is simply not there.
In 1.0.0 the eight API providers do not send attachments, and MevvMail does not pretend otherwise: an email carrying a file skips those connections and looks for an SMTP one. So keep a single SMTP connection in the chain and invoices, tickets and PDFs keep working. With no SMTP connection configured, such an email is logged as failed rather than delivered without its file.
With no connection defined the filter hands the send straight back to WordPress. A plugin that swallowed a store’s email while somebody worked out the settings would be worse than the problem it set out to solve.
Pro adds the WooCommerce email designer, open tracking, failure alerts and conditional routing. Delivery, failover and the log stay in the free plugin and keep running whatever the licence says — a lapsed licence costs you the designer screen, never the ability to send an email.
Where your email goes
A delivery plugin sits on the one path every order confirmation, password reset and invoice takes. Some of them use that position to send the message somewhere else as well — for scoring, for filtering, for “content protection”. That is a second copy of your customer’s email leaving your server, and it is the thing we deliberately did not build.
Your message· posted to somebody else’s endpoint
Whatever the endpoint does with it, you can no longer say the message never left.
Two destinations· the provider you chose, and your own database
The free plugin does not even call home for a licence — there is no licence to call about.
Read on 4 September 2026 in the source of one competing SMTP plugin whose “content guard” posts the message body to its vendor’s API. We have not audited every mailer on the market and the vendor may change it — check the one you are comparing against. What is fixed is our side: the only outbound request the free plugin makes that is not your own email is a twice-daily update check carrying the plugin slug and its version number, and the copy on WordPress.org does not even contain that file.
Before you install it
Every one of these is in the plugin’s own readme. They are here because the moment to learn them is before the store depends on it.
The eight API providers do not send attachments in 1.0.0. Each of those APIs wants a file in a different shape and eight half-tested encoders were not worth shipping. An email with a file skips them and looks for SMTP, so the practical rule is one line long: keep one SMTP connection in the chain.
Storing the message body is optional, and switching it off is a reasonable answer on a site where the body is personal data. It has two consequences and neither is hidden: that entry cannot be resent, and a failed send is not retried on the one, five and thirty minute ladder either, because in both cases nothing was kept to send.
It is a pixel, and a mailbox that blocks images or a proxy that caches them makes it silent or early. Pro records the first open as a single timestamp and nothing else — no IP address, no email client, no referrer, no location, no open count. There is no open rate anywhere in the product, because the number would not mean what a reader would take it to mean.
Next
The documentation covers the connection screen field by field, the order the chain is walked in, what the log keeps, how a failed message is tried again, and what changes when a Pro licence is active.
Product information