Pagely is an enterprise managed WordPress host, acquired by GoDaddy in November 2021, co-founded by Joshua and Sally Strebel. Plans run from $199/month (VBURST-1) to $2,249/month and above for high-availability enterprise configurations; there are no introductory discounts. Pagely does not host email: no mailboxes, no IMAP or POP3, no forwarders. WordPress 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 → is delivered through a preconfigured MailChannels relay (a hosted outbound-mail filtering and delivery network) without any plugin configuration by the operator. High-volume senders are directed to add a dedicated ESP. At $199/month, Pagely operates in a tier where most operators already have dedicated email infrastructure.
Email on Pagely
How wp_mail works by default
A WordPress install on Pagely sends mail through wp_mail(), which routes through Pagely’s preconfigured MailChannels relay rather than a generic PHP mail() call to a local mail server. The operator does not need to install or configure a plugin for basic transactional delivery to work; this is a meaningful difference from shared cPanel hosts where the default path is raw PHP mail() on a shared IP with no spam filtering. Pagely’s MailChannels relay provides a cleaner delivery path out of the box.
The DNS requirement: the sending domain’s SPF record (the DNS entry that tells receiving servers which services are authorised to send mail on the domain’s behalf) must include include:relay.mailchannels.net. Pagely manages DNS for domains using Pagely’s nameservers; operators who have moved DNS to Cloudflare or another external provider need to add the MailChannels SPF include manually. Without it, MailChannels-routed mail may fail SPF at the recipient’s server and land in spam or be rejected.
DKIM (the per-message cryptographic signature that receiving servers use to confirm the message wasn’t altered in transit) is handled by MailChannels when the SPF configuration is in place. Pagely’s knowledge base documentation on email deliverability covers the SPF and DKIM requirements for the MailChannels path.
Because Pagely does not host domain email, the WordPress From address (wordpress@<domain> by default, or whatever the site’s admin email is set to) does not correspond to a real cPanel mailbox. This is fine for the MailChannels path — MailChannels signs outbound mail from the server regardless of whether the From address has a corresponding mailbox — but it means operators cannot receive replies to WordPress-generated emails unless they have configured domain email elsewhere (Google Workspace, Microsoft 365, or Fastmail with a custom domain).
Outbound SMTP port status
Pagely does not publish a comprehensive SMTP port policy. Port 25 outbound is blocked, which is standard for any managed hosting. For external SMTP relay connections from WordPress plugins, Pagely’s documentation routes operators toward dedicated sending services. Whether ports 465 and 587 are open for plugin-based SMTP credential connections is not documented publicly; Pagely’s support guidance favours API-based relay integrations over direct SMTP connections for external services.
The practical consequence: operators who need more than the default MailChannels transactional path should use a relay with a REST API or dedicated WordPress plugin (Postmark‘s official WordPress plugin, Mailgun‘s native integration) rather than assuming SMTP credential connections will work. API-based integrations bypass port availability as a variable and tend to be more reliable on managed WordPress infrastructure where network policy is tightly controlled.
Sending limits
Pagely does not publish a per-hour or per-day sending limit for the MailChannels transactional relay. The relay is described as covering "transactional email" and high-volume senders are directed to use a dedicated ESP.
For operators who need a documented ceiling to plan against: the MailChannels relay is not the right path for campaign or newsletter traffic regardless of any undocumented cap. Pagely’s own guidance singles out SendGrid, AWS SES, and Mailgun as the expected choices for high-volume transactional or bulk sends. At the price point Pagely operates ($199/month and up), most operators either have a Postmark or Mailgun account already or are running a dedicated infrastructure arrangement.
Mailboxes, forwarding, DNS
Pagely does not host email. There are no bundled mailboxes, no IMAP or POP3 servers, no email forwarders, and no catch-all addresses on Pagely. Domain email — branded addresses like [email protected] — requires a separate service. The common configurations at this price tier:
- Google Workspace (formerly G Suite): $6/user/month Business Starter. The most common choice for team email at organisations that are already in the Google ecosystem.
- Microsoft 365 Business Basic: $6/user/month. Exchange-based; standard for organisations on the Microsoft stack.
- Fastmail with custom domain: $5/user/month. Independent option for operators who prefer not to bring a hyperscaler into their email.
Pagely manages DNS for domains using Pagely’s nameservers, which is how the MailChannels SPF record gets applied. DNS delegation to Cloudflare or another provider is supported; any DNS provider can host the SPF record that MailChannels requires.
Authentication (SPF, DKIM, DMARC)
Pagely’s MailChannels relay requires one SPF change from the default:
Add
include:relay.mailchannels.netto the domain’s existing SPF record.Source: Pagely email deliverability documentation
DKIM is handled by MailChannels on the outbound path when the SPF include is present. Operators do not need to manage per-mailbox DKIM configuration (there are no mailboxes to configure it for); the relay-level DKIM signing is automatic.
DMARC is optional but recommended for operators who want to enforce policy on their sending domain. A starting policy of v=DMARC1; p=none; rua=mailto:reports@<domain> collects failure reports without rejecting mail, which is the appropriate starting point when the domain’s full sending inventory (MailChannels for transactional, a dedicated ESP for campaigns, potentially Google Workspace for employee email) hasn’t been fully audited for SPF/DKIM alignment.
The SPF record consideration: operators using both MailChannels (for wp_mail()) and a dedicated sending service (for campaigns or high-volume transactional) need both includes in the SPF record. A record that includes only relay.mailchannels.net will fail SPF for mail sent through Postmark, Mailgun, or any other service that isn’t MailChannels.
What Pagely does not provide
- Bundled mailboxes or email hosting. No addresses at the domain, no IMAP or POP3, no forwarders. Domain email is out of scope for the product; Pagely’s knowledge base says so directly.
- A published sending limit. The MailChannels relay is undocumented on throughput. Operators planning around volume need a dedicated ESP with documented quotas.
- Delivery events for wp_mail(). The MailChannels path does not expose per-message delivery, bounce, or rejection events to the WordPress admin. Any third-party relay with a dashboard or webhook does.
- External SMTP credential support (not confirmed). Pagely does not publish port-by-port SMTP access documentation. API-based integrations are the safer assumption for plugin-based relay connections.
When a third-party relay is needed
The Pagely default path (MailChannels relay, wp_mail() works out of the box) covers basic transactional delivery for sites whose WordPress-generated email is password resets, contact form acknowledgements, and WooCommerce order confirmations at modest volume. At the $199-and-up price point, most Pagely sites are beyond "modest volume." The triggers:
- You need delivery events. The MailChannels relay on Pagely produces no per-message log accessible to the operator. Postmark‘s dashboard and per-event webhook is the standard answer at this tier; Mailgun exposes a full API log.
- You need a documented throughput ceiling. Pagely publishes no sending limit for the default relay. Any site with a compliance requirement or an SLA around email delivery needs a service that publishes its quotas.
- You’re sending newsletters or campaigns. The MailChannels transactional relay is not designed for bulk sends; Pagely’s documentation says as much. Campaigns belong on a dedicated marketing platform.
- You need dedicated IP reputation. At the Pagely price point, sites with reputation-sensitive sending (financial services, healthcare, high-LTV e-commerce) typically want dedicated sending IPs. Postmark on the Dedicated IP add-on and Mailgun on Foundation are the standard options.
Because Pagely is enterprise managed WordPress, the practical reality is that many Pagely sites already have email infrastructure sorted: a Postmark account billed separately, a Mailgun key in the environment config, or Google Workspace handling both employee mail and transactional delivery through Workspace’s SMTP relay. For those that do not, installing WP Mail SMTP or Post SMTP and pointing it at Postmark or Mailgun via their API key is the standard configuration.
Verdict
Pagely is an enterprise managed WordPress host whose email story is defined by one fact: there is no bundled email. The preconfigured MailChannels relay handles transactional wp_mail() without configuration, which is a better default than the raw PHP mail() path on shared hosting, but it covers only a narrow use case. Operators bringing a Postmark or Mailgun account, or running Google Workspace for domain email, will find the relay path slots in cleanly. Operators who need bundled mailboxes or a published sending ceiling should look at the shared-hosting tier or a managed host that includes email hosting.
For the WordPress email setup that supplements Pagely’s default path, see how to configure WordPress email.