WordPress plugin intelligence profile

Mailyard

Sends your WordPress email through Amazon SES, Postmark, Resend, Brevo, Mailgun, SendGrid, or any SMTP — and switches to a backup when a send fails.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.1.0
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 7.0 · PHP 7.4
Directory statusactive
Last directory update9 Oct 202624d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Mailyard version 1.1.0 as active, updated 24d ago and tested up to WordPress 7.1.

Overview

About this plugin

WordPress hands your email to your web host, and most hosts are bad at email. Messages get blocked, land in spam, or disappear without a trace. So every site I’ve run ended up with an SMTP plugin — and every SMTP plugin I tried did the same thing when the provider failed.

It wrote a log entry and gave up. The password reset, the order receipt, the form reply: gone.

That felt wrong.

So I built Mailyard. It sends your email through a real service — Amazon SES, Postmark, Resend, Brevo, Mailgun, SendGrid, SMTP2GO, Mailjet, MailerSend, Maileroo, or any SMTP server — and if that service fails, it retries the same email through your backup, on the same send. Not in a retry queue.

Not tomorrow. The email still goes out.

That is Mailyard, and all of it is free. No locked buttons, no upgrade nags. co/mailyard.

What it does

  • A backup that takes over. The moment a send fails, your backup provider tries the same email.
  • Sixteen ways to send. Amazon SES, Postmark, Resend, Brevo, Mailgun, SendGrid, SMTP2GO, Mailjet, MailerSend, Maileroo, Gmail, Microsoft 365 (signed in or app-only), Zoho Mail, custom SMTP, or plain PHP mail.
  • A log of every email. Every send and every failure, with the provider’s exact error in plain words. Search, filter, resend, export to CSV. Kept 30 days by default — or 7, 90, or forever.
  • Alerts before a customer tells you. An email when sending fails or a backup had to take over (sent by your server, so it arrives even when the provider is what broke), on Slack, Discord or Teams too, plus an optional weekly summary.
  • A deliverability checker. Your SPF, DKIM, DMARC, and MX records, graded A–F, with the exact DNS record to add.
  • Sender routing. Receipts through Postmark, newsletters through Brevo — the right provider per sender, automatically.
  • Bounce tracking. Amazon SES, Postmark, Resend, and Brevo webhooks, normalized into one mailyard_bounce hook.
  • Control WordPress’s own emails. Switch off new-user, password-change, comment and auto-update notifications. Password resets always go out.
  • Background sending and Offline mode. Pages don’t wait on the mail server; staging sites log everything and send nothing.
  • Multisite. Set email up once on the main site for the whole network, or let each site do its own.
  • Credentials kept your way. In wp-config.php, encrypted in the database, or plain — and a one-file settings backup.
  • AI tools. Claude, Cursor, or Codex can check your setup and read the log — every tool has its own off switch, and nothing is exposed until you set it up.

Setup takes a minute: pick a provider, paste a key, send a test. Coming from WP Mail SMTP, Easy WP SMTP, FluentSMTP or Post SMTP? Mailyard finds your setup and imports it in one click.

If another plugin is fighting you, Mailyard says so.

Which provider?

  • Resend — easiest to start with
  • Brevo — has a free tier, 300 emails a day
  • Postmark — best inbox placement, made for stores
  • Amazon SES — cheapest at high volume
  • Mailgun, SendGrid, SMTP2GO, Mailjet, MailerSend, Maileroo — already have an account with one? Use it
  • Gmail, Microsoft 365, Zoho Mail — send from the mailbox you already have, signed in with OAuth (no password stored)
  • Custom SMTP — any SMTP server
  • PHP mail — your host’s server; no setup, but don’t count on it

Source code

The admin screens are React, built with @wordpress/scripts. com/plugpressco/mailyard under src/ — npm install, then npm run build.

Privacy

Mailyard only talks to the email service you set up. It doesn’t phone home and it doesn’t track you. The deliverability checker reads your domain’s DNS records via your server’s resolver, falling back to Cloudflare’s public DNS only if that fails (it sees the domain name and nothing more).

If email logging is on (it is by default), each email’s recipient, subject, and body are saved to your database — turn it off in Settings whenever you want.

External services

Mailyard sends your WordPress email through a third-party email service that you choose and set up with your own account and API key. Nothing is sent anywhere until you pick a provider and enter its credentials, and then it only goes to that one provider (plus its fallback, if you added one).

What gets sent is the email your site is already trying to send: the recipient address(es), the sender, the subject, the body, and any attachments. It’s sent at the moment WordPress sends that email — a password reset, a WooCommerce order, a contact-form reply, and so on.

Resend — email delivery API, used if you pick Resend. com/emails.

com/legal/privacy-policy

Brevo (formerly Sendinblue) — email delivery API, used if you pick Brevo. com/v3/smtp/email.

com/legal/privacypolicy/

Postmark — email delivery API, used if you pick Postmark. com/email.

com/privacy-policy

Amazon SES (Simple Email Service) — Amazon’s email delivery API, used if you pick Amazon SES. com/v2/email/outbound-emails. com first).

com/privacy/

Mailgun — email delivery API, used if you pick Mailgun. net for the EU region).

com/legal/privacy-policy/

SendGrid (Twilio) — email delivery API, used if you pick SendGrid. com/v3/mail/send.

com/en-us/legal/privacy

SMTP2GO — email delivery API, used if you pick SMTP2GO. com/v3/email/send.

com/privacy/

Mailjet — email delivery API, used if you pick Mailjet. 1/send.

com/legal/privacy-policy/

MailerSend — email delivery API, used if you pick MailerSend. com/v1/email.

com/legal

Maileroo — email delivery API, used if you pick Maileroo. com/api/v2/emails.

com/privacy-policy

Google (Gmail API and Google sign-in) — used if you pick Gmail. com/token. com/gmail/v1/users/me/messages/send.

No password is stored.

com/privacy

Microsoft (Microsoft Graph and the Microsoft identity platform) — used if you pick Microsoft 365. 0/me/sendMail (or /users/{mailbox}/sendMail for app-only). No password is stored.

com/privacystatement

Zoho (Zoho Mail API and Zoho accounts) — used if you pick Zoho Mail. {your data center}/api/accounts. No password is stored.

html

Custom SMTP — if you pick the Custom SMTP option, email goes to the SMTP host and port you enter. That’s whatever SMTP service or server you choose, so check its own terms and privacy policy.

Chat webhook — only if you add a webhook URL in Settings → Alerts (Slack, Discord, Microsoft Teams, or any address you choose). Mailyard posts the alert to that URL: your site name and address, how many emails failed, and the provider’s error message. Email contents and recipients are never posted.

The service behind the URL is one you picked, so its own terms and privacy policy apply.

Cloudflare DNS over HTTPS — only used by the deliverability checker, and only as a fallback when your server’s own DNS lookup fails. com/dns-query. No email content is involved.

1/privacy/public-dns-resolver/

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • email log
  • deliverability
  • mailer
  • smtp
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 7.0 · PHP 7.4
Update activity9 Oct 202624d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.0.11.1.0
WordPress compatibility7.0.47.1.3
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.