WordPress SMTP per site with a central email delivery log
Configure outgoing email per site with SES, SendGrid, Mailgun, Postmark, or any SMTP server. Named connections, automatic failover, and a central searchable delivery log across your whole fleet.
WordPress sends email through the server's mail function by default, and bounces, failures, and spam classification are invisible
The default WordPress mail setup uses PHP's mail() function which routes email through the server's local MTA with no authentication, no TLS, and no delivery visibility. Messages land in spam or fail silently. Diagnosing a missing password reset or a WooCommerce order confirmation requires SSH access to mail logs. Per-site SMTP with a central delivery log brings visibility and reliability to email across the whole fleet.
Under the hood
The steps that make it work, and what each one does.
Add a named email connection
Configure a named connection per site: SES with IAM credentials, SendGrid, Mailgun, or Postmark API keys, or any SMTP server with a host, port, username, and password. Credentials are encrypted at rest.
Set a failover connection
Designate a secondary connection to use if the primary fails. WPMgr automatically routes through the failover without manual intervention, and the delivery log marks which connection was used.
Watch the delivery log
Every message sent through a WPMgr-managed connection is logged with recipient, subject, status, and the connection used. Search and filter by site, date, status, or recipient across the whole fleet.
Suppress bounces and complaints
Webhook integrations receive bounce and complaint events from SES, SendGrid, Mailgun, Postmark, and other supported providers. Suppressed addresses are tracked per site to prevent repeat sends to known-bad recipients.
What's included
Every capability ships in the open-source release.
SES, SendGrid, Mailgun, Postmark, and SMTP
Named connections for the major transactional email providers and any standard SMTP server. API keys and SMTP credentials are encrypted at rest.
Automatic failover
Designate a secondary connection per site. If the primary fails, WPMgr routes through the failover automatically and marks the delivery in the log.
Central searchable delivery log
Every sent message is logged with recipient, subject, status, timestamp, and which connection was used. Searchable and filterable across the whole fleet.
Webhook bounce and complaint suppression
Bounce and complaint webhooks from supported providers are received and processed. Suppressed addresses are tracked per site to prevent sending to known-bad recipients.
Fleet-wide deliverability view
A fleet-wide deliverability summary shows which sites have unconfigured email, recent bounce rates, and sites with suppressed address lists that need attention.
Credentials encrypted at rest
SMTP passwords and API keys are encrypted at rest in the control plane. Plain-text credentials are never stored in the database.
Questions answered
Common questions about this feature.
Self-host it, read the code, and run your whole fleet.
Free and open source. No per-site fee. The full release is on GitHub.