Email Delivery features

Pick the service and the host, port and encryption are filled in, along with a line telling you what its username and password actually are — which for half of them is not the thing you sign in with, and is where most people come unstuck. A site signing in to Microsoft 365 with a password is warned on its Dashboard that Microsoft switches that sign-in off by default at the end of December 2026, with a link to Microsoft's own announcement.

Not "failed" — the actual sentence it said, whether that is a sender address nobody verified, a password the service refused, or a connection your host is blocking. The username and password are taken out of it, so you can paste it into a support thread.

Here a copy of the site, or a site WordPress calls staging, holds every message in the log instead and sends nothing. When a real move to a new domain is the reason, one press on the notice sends what was held, oldest first.

The log says the backup sent it and what the main one said, and a test checks each connection on its own.

It shows what it looked up and what came back, asks your own server's DNS and no outside service, and runs daily, after a test and when you press Check again.

So a database dump on its own — the thing that gets shared with a developer, restored onto staging, or left in a backup bucket — is no longer a mailbox somebody else can send from. Against somebody holding both the files and the database it does nothing, and the screen says so rather than implying more.

Choose the address and the name your customers should see, and optionally make every plugin on the site use it — including the ones that insist on their own.

Searchable by address or subject, with a tab for the ones that did not arrive. When somebody says they never got their receipt, that stops being a guess.

Here it is held and sent again on a widening gap, a few times, and then given up on visibly rather than quietly. For a password reset that is a convenience; for an order confirmation it is a customer who does not think the shop vanished.

The notice comes first on purpose: a plugin that only emails you when email is broken is a smoke alarm wired to the fuse that just blew.

At most once a day, with a test button. The address a failed message was for is left out unless you switch it on, and the webhook address is stored scrambled and kept out of an exported settings file.

Switch on keeping the message itself and it is shown too, with nothing in it allowed to run or load from outside, and you can send it again to the same address or the one the customer meant, with the log linking the copy to the original. A password reset or new-account email from WordPress or WooCommerce only goes back to its own address, and the key in its link is hidden on the page.

Send it again sends one of them once more, the way WooCommerce's own order actions do, to the address on the order or, for the shop's own emails, to the recipients in WooCommerce's settings, and a waiting copy of a refused one is taken off the retry queue so it arrives once. In the log, each of those emails links to its order.

A revoked app password or a deleted API key is usually found at the next check, with the server's own reply on a wp-admin notice, rather than when a customer's receipt goes missing. Two refusals in a row, ten minutes apart, before it says anything. A mail server that offers no sign-in, or cannot be reached at all, is reported as that, so nobody changes a password that was right. On for new installs, and one click on the Dashboard for sites that had the plugin before.

A failed update is still emailed, and the emails telling somebody their own password or address changed always go.

The Settings screen shows those fields greyed and says where they come from. On a network a must-use plugin can give one site its own.

This configures the mailer that function already uses and listens for what it says afterwards. There is no second code path to go wrong, which is what makes it safe to put on a shop that is taking orders — and switching it off puts the site back exactly where it was.

None is stored unless you ask for it. The one exception is a message waiting to be sent again, because you cannot re-send what you did not keep, and that copy is deleted the moment it goes or is given up on.

A site whose email has stopped is often a site where something larger has gone wrong, and the first thing anybody does is open a terminal.

Spanish and French are included and complete, and every string is translatable.

WordPress has a place for a plugin to declare that, and this one uses it — so the suggested wording is there for you rather than something you have to work out.