Presslabs is a Kubernetes-based managed WordPress host built in Timisoara, Romania, targeting publishers, agencies, and enterprise customers. Plans span from $33/month (Personal 1) to $6,000/month for Enterprise configurations, a wider range than most managed WordPress hosts. Presslabs does not host email: no mailboxes, no IMAP or POP3, no forwarding. 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 → (password resets, contact form notifications, WooCommerce order confirmations) is handled by a preconfigured SendGrid relay that Presslabs says it does not cap, without requiring plugin configuration. Operators who need domain email for their team must bring a separate provider; the Presslabs dashboard offers one-click MX record setup for Google Workspace and Zoho.
Email on Presslabs
How wp_mail works by default
A WordPress install on Presslabs routes wp_mail() through a preconfigured outbound relay rather than a raw PHP mail() call to a local server. Basic transactional sends (password resets, WooCommerce order confirmations, contact form notifications) work out of the box without installing an SMTP plugin, which is the more convenient default compared to shared cPanel hosts where the operator must configure authentication to avoid unsigned mail on a shared IP.
Presslabs’ 
Service Specifications page names the relay: WordPress system email (password recovery, new account creation, comment notifications) goes out through SendGrid. Presslabs says it does not cap these emails, and asks sites that send newsletters or other mass mail to install their own SMTP gateway service. For sites where transactional email volume is predictable and modest, the default relay path is adequate. For sites that need delivery events or dedicated IP reputation, a third-party sending service is the expected next step.
Authentication on the default path: Presslabs’ DNS documentation describes configuring SPF (the DNS record that specifies which mail servers are permitted to send on the domain’s behalf), DKIM (the per-message cryptographic signature that receiving servers use to verify the sender), and DMARC through the managed DNS panel. Operators using Presslabs-managed DNS can add these records directly; those who have moved DNS to Cloudflare or another provider configure them at the DNS host.
Outbound SMTP port status
Presslabs does not publish an outbound SMTP port policy, and nanoPost has not tested which ports are open. The Service Specifications page asks mass senders to install their own SMTP gateway service, which implies a WordPress site can reach one, but it does not say on which port.
The practical path for operators who need more than the default relay: use a relay with a REST API or dedicated WordPress plugin (Postmark‘s official plugin, Mailgun‘s native integration, SMTP2GO‘s plugin). API-based integrations bypass port availability as a variable, which is the safer choice on managed infrastructure where SMTP port policy is not publicly documented.
Sending limits
Presslabs says it does not cap WordPress system email on the default relay. The limit it sets is on the kind of mail, not the count: newsletters and other mass mail belong on the site’s own SMTP gateway service. Presslabs gives no figure for when a site starts to count as a mass sender.
That is looser than most hosts. InMotion Hosting publishes 250/hour; GreenGeeks publishes 100-500/hour by plan. Sites with a known email load (daily digest emails, large member bases) should still budget a dedicated sending service from the start, because Presslabs’ own documentation sends mass mail there and the default path gives the operator no delivery events.
Mailboxes, forwarding, DNS
Presslabs does not host email. There are no bundled mailboxes, no IMAP or POP3 servers, no email forwarders, and no catch-all addresses. Domain email for the team requires a separate provider. The Presslabs managed hosting dashboard offers one-click MX record configuration for two common options:
- Google Workspace: Business Starter at $7/user/month on an annual commitment. The Presslabs dashboard simplifies the MX record step; operator still needs to create a Google Workspace account and verify domain ownership through Google’s admin console.
- Zoho Mail: Free tier for one domain and up to 5 users, in some of Zoho’s data centres only and without IMAP, POP or ActiveSync; Mail Lite starts at $1/user/month, billed annually (yearly subscriptions only). The dashboard offers a one-click path here too.
For other providers (Microsoft 365, Fastmail, Proton Business), operators configure the MX records manually through the Presslabs DNS panel using the values from the email provider’s setup documentation.
Presslabs manages DNS for domains pointed through the account. SPF and DKIM records for the domain email provider are added through the same DNS panel. If DNS has been moved to Cloudflare, records go there.
Authentication (SPF, DKIM, DMARC)
Presslabs’ DNS documentation covers SPF, DKIM, and DMARC as standard DNS records configurable through the managed hosting dashboard.
SPF for the default transactional relay path: Presslabs does not publish the SPF include for its relay infrastructure in current documentation. Operators should confirm the correct include with Presslabs support. If both the default relay and a third-party sending service (Postmark, Mailgun) are in use, both SPF includes must appear in the record.
DKIM for domain email (Google Workspace, Zoho, etc.) is provided by the email provider and added as a TXT record through the DNS panel. For the default relay, Presslabs’ DNS Specifications page lists a mandrill._domainkeys TXT record in Presslabs-managed zones as the record WordPress system email needs. That page names Mandrill and the Service Specifications page names SendGrid, so check which DKIM record your zone carries, and ask Presslabs support which one is current, before relying on it.
DMARC is manual, added as a _dmarc TXT record. The standard starting point is a monitoring-only policy (v=DMARC1; p=none; rua=mailto:reports@<domain>) before advancing to enforcement once the sending inventory is fully documented and authenticated.
When the Presslabs relay’s include has to sit alongside a mailbox provider or a third-party sender in one SPF record, the SPF merger folds the includes together 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, DKIM selector, and DMARC resolve from the receiver’s perspective, so a stale nameserver or a missed record shows up before real traffic does.
What Presslabs does not provide
- Bundled mailboxes or email hosting. No addresses at the domain, no IMAP, no POP3, no forwarders. Domain email is out of scope; the documentation says as much by routing operators to Google and Zoho.
- A line between system mail and mass mail. System email is uncapped, mass mail must leave, and Presslabs gives no figure for where one becomes the other.
- Delivery events for wp_mail(). Presslabs’ documentation describes no per-message delivery, bounce, or rejection log for the default relay.
- Documented SPF infrastructure for the relay. The specific SPF include for Presslabs’ transactional relay is not published in current documentation, which complicates accurate SPF configuration.
- Marketing or bulk email allowance. Presslabs asks sites that send newsletters or other mass mail to install their own SMTP gateway service.
When a third-party relay is needed
The default relay path covers transactional volume for sites where delivery events don’t matter. The triggers for adding a relay:
- You need delivery events. The default relay produces no per-message log. Postmark is the cleanest option for transactional sites under 100,000 messages per month; Mailgun exposes a full log API; SMTP2GO is the cheapest credible entry point.
- You’re sending newsletters or campaigns. Presslabs’ Service Specifications page asks mass senders to bring their own SMTP gateway service; campaigns belong on a dedicated marketing platform.
- You need dedicated IP reputation. Sites in regulated industries or with deliverability-sensitive lists need dedicated IPs. Postmark offers them once sending reaches 300,000 emails a month, and Mailgun on its 100,000-a-month plans and up.
Because Presslabs does not publish which outbound SMTP ports are open, Postmark‘s official WordPress plugin and Mailgun‘s native integration are the natural fit: they send over HTTPS, so there is no port question, and configuration is one API key.
Verdict
Presslabs is a focused Kubernetes-based managed WordPress host for publishers and higher-tier operators. The email story is simple: no bundled email hosting, a preconfigured relay for basic wp_mail() transactional sends, and an expectation that operators bring their own domain email and dedicated ESP for anything beyond simple transactional volume. The pricing range (Personal 1 at $33/month through Enterprise at $6,000/month) puts it within reach of smaller publishers while still serving enterprise workloads, wider than Pagely’s pure-enterprise positioning.
For the WordPress email setup that supplements Presslabs’ default path, see how to configure WordPress email.
Corrections
- 2026-11-04: an earlier version gave InMotion Hosting a daily sending cap of 6,000 emails. InMotion publishes an hourly limit of 250; we found no InMotion source for a daily figure.
- 2026-11-01: an earlier version gave Google Workspace Business Starter as $6 per user per month. Google lists it at $7 per user per month on an annual commitment.
- 2026-10-29: earlier versions said Presslabs does not name its relay provider, that its fair-use terms imply an unpublished sending cap, that outbound port 25 is blocked, and that its documentation steers operators to API plugins rather than SMTP. Presslabs names SendGrid, says it does not cap WordPress system email, publishes no port policy, and asks mass senders to install their own SMTP gateway service.