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. The log stays on your server — the message body is never handed to us, which is the opposite of how the hosted alternatives work. The product is being built now: the delivery engine runs, the screens around it are not written yet, and nothing is on sale.
What it does
Each capability exists to remove a specific operational friction.
The send is taken over completely rather than the mailer being reconfigured, so when a connection refuses the message the next one is tried on the same request. 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 failed 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.
Recipient, subject, status, the provider’s own reply and the attempt count are written to a table in your database. Nothing about your email is sent to us. Keeping the body is a setting, so on a site where the body is personal data you can keep the log and drop the content.
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.
A message can carry a source label — a form, a recovery email, a WooCommerce notification — that is recorded in its own column and taken off the message before it goes out. The label tells you where the email came from without ever reaching the person who receives it.
Generic SMTP and PHP mail() are written today. Brevo, SendGrid, Mailgun, Postmark, SparkPost, Elastic Email, SMTP2GO and Resend come next, each over its own API and each behind the same connection screen.
The WooCommerce link is designed and not yet written: an order’s emails will be tied to the order itself, so the order screen can answer whether the confirmation reached the customer — and send it again from there.
Not a newsletter tool and not a sending service. There is no plan to move your email content onto our machines, because the reason to install this is that it does not.
Product information