WP Engine does not bundle mailboxes. WordPress’s outbound mail leaves through a MailChannels (the outbound relay WP Engine funnels wp_mail() through) relay by default, signed with DKIM (the cryptographic signature receiving servers use to confirm a message came from your domain) automatically, but the platform enforces an hourly send cap that it deliberately does not publish. Port 25 is blocked outbound; 465, 587, and 2525 are open, so an SMTP plugin connects to an external relay directly. The headline trade-off is editorial as much as it is technical: WP Engine’s own documentation states the bundled relay is built for password resets and “will not support a full email campaign,” and the platform itself recommends a third-party provider for anything past incidental volume.
Plans renew at $25/month (Startup, annual billing) and step up through $50, $96, and $242 for Professional, Growth, and Scale. WP Engine sits at the premium end of managed WordPress hosting and is the largest host in the category by install count, alongside Kinsta and well above shared hosts like SiteGround and Bluehost.
Email on WP Engine
How wp_mail works by default
A fresh WordPress install on WP Engine sends mail through MailChannels rather than the local server, with no SMTP plugin to install and no relay credentials to add. WordPress core hands the message to wp_mail(), which on this host is wired to ship outbound through WP Engine’s MailChannels integration. Password resets, user-registration notifications, and comment-moderation alerts leave through this path without configuration.
The detail to plan around is the hourly send cap. WP Engine’s 
own documentation states that “to ensure server stability we impose a hard limit on the amount of emails that can be sent in an hour” and that “in order to prevent abuse of this limit, we will not share the exact amount.” The same page calls the bundled mail “limited” and steers any operator with non-incidental traffic toward a third-party relay. That is unusual phrasing for a host’s marketing surface: WP Engine is the platform that most clearly tells customers its bundled email is not the answer, and most clearly leaves the SMTP ports open so the answer is a plugin install.
Outbound SMTP port status
| Port | Status | Protocol |
|---|---|---|
| 25 | Blocked | SMTP (legacy) — WP Engine blocks outbound 25 for spam prevention |
| 465 | Open | SMTPS (implicit TLS) |
| 587 | Open | SMTP with STARTTLS — the standard submission port for external relays; required for Microsoft 365 |
| 2525 | Open | SMTP (alternate) — WP Engine’s own documentation calls this the recommended choice |
| 993 | Blocked | IMAPS (incoming) — no relevance without bundled mailboxes |
| 995 | Blocked | POP3S (incoming) — no relevance without bundled mailboxes |
Outbound port 25 is closed; the three modern submission ports (465, 587, 2525) are all open. WP Engine’s own documentation calls out port 2525 as the recommended choice and port 587 specifically for Microsoft 365. Any WordPress SMTP plugin that supports authenticated submission (WP Mail SMTP, FluentSMTP, Post SMTP) connects to external services like Postmark and SMTP2GO without trouble. The IMAP/POP3 ports being blocked is consistent with WP Engine not bundling mailboxes: there is no inbound mail to read.
Sending limits
WP Engine enforces an hourly outbound cap on the MailChannels relay and does not publish the figure. The policy phrasing is: enough headroom for routine transactional output (password resets, registration notifications, the occasional WooCommerce order on a low-traffic site), explicitly not enough headroom for “a full email campaign” or notification-heavy plugins firing on every user interaction. The result is that an operator with any meaningful volume has no number to plan against, which is by design.
The limit is enough to send a functional amount of emails such as password resets, but will not support a full email campaign.
The practical consequence: any site that fits one of the “relay is needed” conditions below is also a site that should not try to discover the limit empirically. SiteGround publishes 400-or-800-per-hour numbers; Kinsta publishes 150-or-1,000-or-3,000-per-day numbers; WP Engine’s choice not to publish is itself a recommendation to route mail off the bundled relay before traffic matters.
Mailboxes, forwarding, DNS
WP Engine does not bundle email hosting. There are no mailboxes at [email protected], no IMAP or POP3, no webmail interface, and no forwarding rules. Domain email at WP Engine is always an external arrangement. Practical options: 
Google Workspace at $7/user/month or Microsoft 365 at similar pricing for full mailboxes; Fastmail from $5/user/month for an independent mailbox provider; or a forwarding service (ImprovMX, Forward Email) when the domain only needs to receive at a few addresses without full inboxes.
WP Engine manages DNS for any domain pointed at the platform through the User Portal, with the standard A, CNAME, MX, and TXT record types editable in the dashboard. SPF, DKIM, and DMARC records are added there for any domain WP Engine is authoritative for. If DNS lives elsewhere (Cloudflare is the common one), the records are added at that provider instead.
Authentication (SPF, DKIM, DMARC)
WP Engine’s MailChannels integration handles DKIM signing automatically on the default path. There is no DKIM record for the operator to publish for the bundled relay; the signature is applied at the MailChannels layer. A third-party relay layered on top brings its own DKIM, which the operator does publish at the DNS host.
SPF (the DNS record listing which servers are authorised to send mail under the domain) is not auto-published. WP Engine recommends adding an SPF include for relay.mailchannels.net so that mail leaving through the bundled path passes SPF alignment, and updating the record again once a third-party relay is added. A site running both the bundled path and a third-party relay needs both includes; a site moving entirely off the bundled path can drop the MailChannels include and replace it with the third-party’s.
DMARC is the operator’s call. WP Engine publishes guidance on adding _dmarc records but does not auto-publish a policy. p=none with a rua= reporting address is the conservative starting position; tightening to p=quarantine or p=reject belongs after aggregate reports confirm clean alignment across whatever mix of relays the site uses.
What WP Engine does not provide
- A disclosed hourly limit. The cap exists but is not published. Sites planning around the bundled path have no number to plan against. The policy answer is to plan around a third-party relay instead.
- Mailboxes at the hosted domain. No inboxes, no webmail, no IMAP or POP3. Fastmail, Google Workspace, or a forwarding service (ImprovMX, Forward Email) fills the gap.
- Per-message delivery logs and bounce tracking. WP Engine surfaces nothing about what was sent, what bounced, or what hit spam on the bundled path. A relay with webhook delivery events (Postmark, Mailgun) is the way to get that visibility.
- Marketing or bulk email allowance. The bundled mail is explicitly transactional only. A dedicated marketing platform (Mailchimp, MailerLite, ConvertKit) is the route for broadcast traffic.
- A dedicated sending IP on the default path. MailChannels’ relay shares IP reputation across many tenants. Sites where deliverability isolation matters need a relay with a dedicated-IP add-on (Postmark on Dedicated IP; Mailgun on Foundation).
When a third-party relay is needed
WP Engine answers this in its own documentation: the relay is the default expectation, not an optional add-on for edge cases. Sites that send only the occasional password reset can sit on the bundled MailChannels path; everything else moves up to a relay before traffic does.
The specific conditions that argue for a dedicated relay:
- Anything beyond incidental transactional volume. Any site sending more than a handful of A transactional email is the automated message a WordPress site sends in response to a single user action – a password reset, an order confirmation, a form receipt – addressed to the user who triggered it. Read full reference → an hour. The bundled cap is undisclosed; the editorial recommendation is to move off the relay before discovering it. Postmark is the cleanest fit for transactional under 100,000 a month; SMTP2GO is the cheapest credible option at low volumes; Mailgun is where higher volumes make economic sense.
- A missed email has a real cost. Password resets that arrive late, order confirmations that vanish into spam, registration notifications that the new user never sees, all roll up to churn. A dedicated relay is the only path that exposes the data needed to confirm those messages landed.
- Delivery visibility is required. Per-message delivery, bounce, and complaint events arrive as webhooks from Postmark, Mailgun, and SMTP2GO, with searchable logs and aggregate dashboards. The bundled WP Engine path produces none of this.
- The site needs marketing or newsletter sending. The bundled policy excludes broadcast traffic. A marketing platform (Mailchimp, ConvertKit, MailerLite) handles the campaign side; a dedicated transactional relay handles the transactional side.
Because WP Engine keeps 465, 587, and 2525 open, an SMTP plugin connects to any of the providers above without an API-only constraint. SMTP is simpler to set up; the providers’ HTTP APIs hold up better when DNS or network changes shift things around. Both work.
Verdict
WP Engine is the right pick for managed WordPress sites whose operators already plan to run a third-party SMTP relay from day one, and who want a host whose policy assumes that. The MailChannels-backed default mail covers password resets, the open submission ports keep the relay swap path clean, and WP Engine’s own documentation steers any operator past incidental volume to a relay rather than dressing the bundled mail up as something it is not. The trade-off is candor doubled with the no-mailbox stance: a brand that needs full domain email and a reliable transactional path will end up paying for a relay and a mailbox provider on top of the hosting bill, and that bill is at the premium end of the category. For the WordPress email setup that supplements WP Engine’s default path, see how to configure WordPress email.