Email Logs and the Deliverability Checker

The email log

Every email your site sends is logged — recipient, subject, status, and the exact provider error when something fails. “Did the order confirmation go out?” takes ten seconds to answer, not an afternoon of digging through server logs.

• Logs clean themselves up after 30 days, automatically.
• You can switch email logging off entirely in Settings if you’d rather not store recipient, subject, and body in your database.
• Uninstalling the plugin leaves your logs and settings alone, so you can reinstall without losing anything. The only thing that wipes your data is the explicit Delete all data button in Settings — it never runs on its own.

The deliverability checker (SPF, DKIM, DMARC & MX)

Even with a good provider, email lands in spam when your domain’s DNS isn’t set up to vouch for it — and most people never find out. Mailyard’s Deliverability screen reads your sending domain’s SPF, DKIM, DMARC, and MX records, grades them A–F, and tells you exactly which DNS record to add.

Run it right after connecting your provider, and again whenever you add a new sending domain. That one missing record is usually the whole difference between the inbox and the spam folder.

Privacy note: the checker uses your server’s own DNS resolver first, and only falls back to Cloudflare’s public DNS if that fails — which sees the domain name and nothing more. No email content is ever involved.

The dashboard

The Mailyard Dashboard shows your sending health at a glance: the last 14 days of volume, recent activity, and one-click test sends so you can confirm mail is flowing at any time.

When something fails

Open the log entry — the provider’s exact error message is stored with it. Common culprits: a revoked or mistyped API key, an unverified sender domain at the provider, or a provider outage (which is what failover is for). Once fixed, use Send test to confirm, or ask a connected AI assistant to diagnose the whole chain for you.