Pagely is an enterprise managed WordPress host, co-founded by Joshua and Sally Strebel; GoDaddy announced its acquisition in November 2021. Plans start at StartPress, listed at $199/month and shown at $99/month on Pagely’s pricing page in October 2026; the top published tier, ScalePress, runs $2,500/month, or $3,600 in a high-availability configuration. 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 → goes out through PHP mail(), which Pagely relays through MailChannels (a hosted outbound-mail filtering and delivery network), so it sends with no plugin installed. Pagely’s own knowledge base ranks that path below an SMTP plugin or a third-party email service, and documents an SPF record for it but no DKIM on the site’s domain, so DMARC alignment on the default path is unverified. At these prices, many operators will already have email infrastructure of their own.
Email on Pagely
How wp_mail works by default
A WordPress install on Pagely sends mail through wp_mail(), which by default calls PHP’s mail() function. Pagely hands that mail to MailChannels, a third-party service that filters it for spam before delivery, so mail leaves the server with no plugin installed. Pagely’s
deliverability article is blunt about how far to trust this path: “we recommend you utilize a third party and NOT rely on the server’s mail() function to deliver email,” and for a site whose receipts or download links depend on email, it “STRONGLY” advises a third-party service. The article ranks the default path “Good”, an SMTP plugin “Better” and a dedicated email service “Best”.
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 where the documentation stops. Pagely’s article covers the SPF record and nothing else: it gives no DKIM record to publish and does not say whether MailChannels signs the mail, or under whose domain. Without a DKIM signature on the site’s own domain, DMARC can pass only through SPF alignment, which depends on the envelope sender the relay uses, and Pagely does not document that either.
Because Pagely does not host domain email, the WordPress From address (wordpress@<domain> by default unless a plugin or the wp_mail_from filter changes it) does not correspond to a real mailbox. This is fine for the MailChannels path (Pagely’s article says the SPF include is what lets [email protected] work as a From address) 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 publishes no outbound port policy, for port 25 or for 465/587. For external SMTP relay connections from WordPress plugins, Pagely’s documentation routes operators toward dedicated sending services, without saying which ports those connections may use. Pagely’s deliverability article lists an SMTP plugin pointed at SendGrid, SparkPost or Mailgun as an option, but does not say which outbound ports that connection uses.
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 integrations take port policy out of the question, which matters on a host that documents none.
Sending limits
Pagely does not publish a per-hour or per-day sending limit for the MailChannels relay. Its article says only: “Our policy is to restrict the volume and velocity of outbound email from our servers,” and that it does “not allow any bulk sending of any kind, such as for email marketing, newsletters, etc.”
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 article names SendGrid, SparkPost, Mailgun and Mailjet as the third-party services to use. At Pagely’s prices, many operators will already have a Postmark or Mailgun account or a sending arrangement of their own.
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 usual options:
- Google Workspace, for organisations already in the Google ecosystem.
- Microsoft 365, Exchange-based, for organisations on the Microsoft stack.
- Fastmail with a custom domain, an independent option for operators who prefer not to bring a hyperscaler into their email.
Pagely’s article asks the operator to have the DNS provider append the include, which is Pagely itself for domains on its nameservers. 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
Pagely documents no DKIM record for this path. Whether MailChannels adds a signature, and under which domain, is not stated, so treat the site’s mail as unsigned for DMARC purposes until a test send shows otherwise: send a wp_mail() to a Gmail address and read the Authentication-Results header for dkim=pass with header.d= set to the site’s own domain.
DMARC is the operator’s call, and on this path the safe position is v=DMARC1; p=none; rua=mailto:reports@<domain>, which collects reports without rejecting mail. Tightening to p=quarantine or p=reject belongs only after aggregate reports show the relayed WordPress mail passing aligned SPF or DKIM for the site’s domain. Pagely documents neither, so only the reports can show it. A domain that already enforces DMARC should send WordPress mail through a mailer plugin and a relay that signs as the domain.
The SPF record consideration: if the second sender uses the root domain as its envelope sender, its include goes in the same SPF record as MailChannels’. Postmark uses its own Return-Path and needs no include; Mailgun’s lives on the sending subdomain. The SPF merger folds include:relay.mailchannels.net alongside the second sender’s include and counts the DNS lookups against RFC 7208’s ten-lookup ceiling before publish. Once the record is live, the DNS auth checker reads how the domain’s SPF, any DKIM signature, and DMARC resolve from the receiver’s perspective, so a stale nameserver or a missed include shows up before real traffic does.
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.
- Documented DKIM or DMARC alignment. The default path has an SPF record and nothing else in Pagely’s documentation. Nothing says the mail is signed as the site’s domain.
- 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(). Pagely documents no mail log for the relay. Any third-party relay with a dashboard or webhook provides one.
- 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 Pagely’s prices, many sites will be past modest volume. The triggers:
- Your domain enforces DMARC. At
p=quarantineorp=reject, mail that does not pass aligned SPF or DKIM goes to spam or is refused, and Pagely documents neither for the default path. A relay that signs as the domain passes DMARC on DKIM alone. - You need delivery events. Pagely documents no mail log for the relay. 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 (once sending reaches 300,000 emails a month) and Mailgun (on its 100,000-a-month plans and up) are the standard options.
Because Pagely sells enterprise managed WordPress, many of its sites will already have email infrastructure in place: 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 MailChannels relay lets wp_mail() send without configuration, but Pagely’s own documentation tells operators not to rely on it, and it documents an SPF record with no DKIM on the site’s domain, so a domain that enforces DMARC cannot count on it. 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.
Corrections
- 2026-10-29: an earlier version said MailChannels DKIM-signs Pagely’s default-path mail and that Pagely’s documentation covers DKIM for it. Pagely’s documentation covers only an SPF record; it also tells operators not to rely on the server’s
mail()path, which an earlier version omitted. - 2026-10-29: an earlier version said Pagely blocks outbound port 25. Pagely publishes no outbound port policy, so the block is unconfirmed.

