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 relay that covers basic wp_mail() sends under a fair-use policy, 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.
The relay is covered under fair-use terms; Presslabs does not publish the name of the relay provider in its current documentation, nor does it publish a per-hour or per-day sending ceiling. For sites where transactional email volume is predictable and modest, the default relay path is adequate. For sites that need documented throughput limits, 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 a comprehensive SMTP port policy. Port 25 outbound is blocked, which is standard for any managed host. For external SMTP relay connections from WordPress plugins, Presslabs’ own documentation routes operators toward configuring external email providers via MX records rather than SMTP credential connections.
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
No sending limit is published for the default transactional relay. The fair-use framing implies a cap exists but Presslabs does not document it, which makes the default path unsuitable for operators who need to plan around throughput.
For reference: InMotion Hosting publishes 250/hour per domain, 6,000/day; GreenGeeks publishes 100-500/hour by plan. The absence of a documented limit at Presslabs is the tell that the default relay is not the intended path for anything beyond basic transactional volume. Sites with a known email load — daily digest emails, high-LTV transactional confirmations, large member bases — should budget a dedicated sending service from the start.
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: $6/user/month Business Starter. 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 available for single domains up to 5 users; paid plans from $1/user/month. 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 or verify via the dashboard’s email deliverability guidance. 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. DKIM for WordPress’s wp_mail() default relay path is handled by the relay infrastructure; the operator does not configure per-mailbox DKIM (there are no mailboxes).
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.
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 published sending limit. Fair-use framing without documented caps. Operators planning around throughput need a relay with published quotas.
- Delivery events for wp_mail(). The default relay does not expose per-message delivery, bounce, or rejection events to the operator.
- 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. Fair-use is for transactional flows; campaigns belong on a dedicated platform.
When a third-party relay is needed
The default relay path covers modest transactional volume for sites where delivery events don’t matter and the sending ceiling is never approached. 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 need a documented throughput ceiling. Presslabs publishes no limit. Any site with a compliance requirement or SLA around email delivery needs a service with published quotas.
- You’re sending newsletters or campaigns. Fair-use transactional relay is not designed for bulk sends; 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 on the Dedicated IP add-on, Mailgun on Foundation.
Because Presslabs’ documentation routes operators to API-based relay plugins rather than SMTP credential connections, Postmark‘s official WordPress plugin and Mailgun‘s native integration are the natural fit — no SMTP port uncertainty, clean API key configuration.
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.