WP Engine is a managed WordPress hosting provider with a deliberate stance on email: it works out of the box for basic transactional messages, but the platform openly recommends using a third-party email provider for anything beyond password resets. Default outbound email routes through MailChannels with an undisclosed hourly sending cap. SMTP ports 465, 587, and 2525 are open (port 25 is blocked), so SMTP plugins can connect directly to external relay services without needing API-based workarounds.
Plans start at $25/month (Startup, annual billing). WP Engine is the largest managed WordPress host by install count.
Email on WP Engine
What works out of the box
WordPress core’s wp_mail() sends through WP Engine’s MailChannels relay. Password resets, user registration notifications, and comment moderation alerts will typically send without additional configuration. WP Engine’s documentation is explicit about the limitations: "The limit is enough to send a functional amount of emails such as password resets, but will not support a full email campaign."
The exact hourly sending limit is not disclosed. WP Engine enforces it to protect shared IP reputation across the platform; a single site sending spam could get the relay IP blocklisted for thousands of other sites.
SMTP port access
| Port | Status | Protocol |
|---|---|---|
| 25 | Blocked | SMTP (legacy) |
| 465 | Open | SMTPS (implicit TLS) |
| 587 | Open | SMTP with STARTTLS |
| 2525 | Open | SMTP (alternate) |
| 993 | Blocked | IMAP |
| 995 | Blocked | POP3 |
This is a meaningful difference from Kinsta, which blocks all SMTP ports and requires API-based plugin integration. On WP Engine, an SMTP plugin configured with smtp.postmarkapp.com:587 or smtp.sendgrid.net:465 works directly. Microsoft 365 requires port 587 specifically.
DNS and authentication
WP Engine does not provide MX records, DKIM records, or email hosting. SPF and DMARC records for outbound email must be configured at the DNS host. WP Engine recommends adding an SPF include for MailChannels to allowlist the default relay, and adding the third-party provider’s SPF include when using an external service.
What WP Engine does not provide
Disclosed sending limits. The hourly cap exists but is not published. This makes it impossible to plan around. If email volume is anything beyond incidental, a third-party relay is not optional; it is WP Engine’s own recommendation.
Email hosting (mailboxes). No email accounts, no IMAP/POP3, no forwarding. Domain email requires a separate provider: Google Workspace ($7/month per user), Fastmail (from €5/month), or a forwarding service (ImprovMX, Forward Email).
Email monitoring. No delivery logs, no bounce tracking, no open/click metrics. The default relay is a black box. Third-party services provide the observability that WP Engine’s infrastructure does not.
Marketing/bulk email. Prohibited. Use a dedicated email marketing platform.
When to add a third-party relay
WP Engine’s own documentation answers this: always, unless the site sends only a handful of transactional emails per day. The platform is designed around the assumption that serious WordPress email goes through a dedicated provider.
Recommended setup: install an SMTP plugin (WP Mail SMTP, FluentSMTP, Post SMTP) and configure it with Postmark, SMTP2GO, or Mailgun. Since ports 465/587/2525 are open, both SMTP-based and API-based connections work. SMTP is simpler to configure; API is more resilient to network restrictions.