Logo: RAIDBOXES Emails

RAIDBOXES Emails

German domain email hosting from Raidboxes GmbH (Münster): Mail Hosting 2.0 with IMAP/SMTP, multi-mailbox plans, optional PGP, and dashboard fit for WordPress agencies—domain must be hosted at RAIDBOXES.

RAIDBOXES Emails is the business mailbox product of Raidboxes GmbH, a managed WordPress host based in Munster, Germany. It provides paid, ad-free email hosting for custom domains with IMAP and SMTP, webmail, aliases, forwarding, optional PGP, and backups.

It exists for WordPress agencies and sites already hosted at RAIDBOXES that want domain mail in the same dashboard. The domain must be hosted at RAIDBOXES. Mailboxes now run on RAIDBOXES' own infrastructure rather than the earlier mailbox.org cooperation.

The concrete differentiator is that Mail Hosting 2.0 fit for RAIDBOXES customers, with a hard limit of one connected domain per plan.

German operatorIMAP / SMTPMail Hosting 2.0Online DPAWordPress-adjacentOptional PGP

Shortlist when you already (or will) host the domain and WordPress stack at RAIDBOXES and need practical multi-mailbox domain email under a German operator with an online DPA. Skip when you need multi-domain density, default E2EE, or email fully independent of a hoster—consider Migadu, Tuta, Posteo, or mailbox.org instead.

Key capabilities

IMAP/SMTP mailboxes on dedicated hostnames (mail-rb.securemail.pro / smtp-rb.securemail.pro) after the move off the prior mailbox.org cooperation. Vendor claims German data-centre locations and triple-redundant mail servers. Best for teams that want domain mail under the same German WordPress host rather than a separate privacy-mail brand.

Tiered plans allocate a fixed number of mailboxes and a shared storage pool, plus per-mailbox alias and forwarding quotas, autoresponders, and catch-all (requires a dedicated catch-all mailbox). One connected domain per plan—confirm multi-domain needs before shortlisting.

All plans include spam and virus filtering, SSL/TLS for transfer, a blacklist checker, webmail, and ad-free inboxes. PGP is optional rather than default end-to-end encryption for every message—teams that need mandatory E2EE workflows should evaluate Tuta or a full mailbox.org stack instead.

Mailboxes are ordered from the RAIDBOXES dashboard and are intended to sit next to WordPress hosting and domain management. New RAIDBOXES mailboxes require the domain to be hosted with RAIDBOXES; legacy mailbox.org-linked domains follow a separate migration path documented in the help centre.

Raidboxes GmbH (Münster) offers an online data processing agreement (AV contract) with technical-organisational measures. Useful for agencies that already sign a DPA for WordPress hosting and want the same counterparty for domain email—still review TOMs and subprocessor scope for mailbox vs platform tooling.

At a glance

HQ
Münster, Germany
Legal entity
Raidboxes GmbH (HRB 16184)
Group
team.blue (Belgium) since 2022
Product
Mail Hosting 2.0 domain email
Access
IMAP / SMTP + webmail
Domain constraint
Domain hosted at RAIDBOXES for new mailboxes
Open source
No
Self-hosted
No

Best fit when

  • WordPress agencies and freelancers standardising on RAIDBOXES for sites, domains, and mail admin
  • SMEs wanting professional multi-mailbox domain email with standard IMAP clients—not a full Google/Microsoft suite
  • Teams that need catch-all, aliases, forwards, autoresponders, and ad-free inboxes on one domain
  • Buyers who require a German legal counterparty and an online B2B DPA for processor agreements
  • Operators migrating off legacy mailbox.org-linked RAIDBOXES mail toward first-party Mail Hosting 2.0

Poor fit when

  • Multi-domain mail estates that need many domains under one contract (one connected domain per plan)
  • Policies requiring default end-to-end encryption for all mail (PGP is optional only)
  • Buyers who refuse any coupling between mailbox service and domain/WordPress hosting
  • Teams seeking a full office suite (Drive, collaborative docs, built-in video) rather than domain mail
  • Procurement that demands public ISO 27001/SOC 2 or independent no-logs audit reports for the mail product

Consider instead when

  • When: You need multi-domain, usage-based professional mail without WordPress host lock-in

    Consider: Migadu

    Swiss-operated, standards-based hosting priced by quotas rather than per-domain WordPress adjacency

  • When: You need default E2EE and a privacy-first client model

    Consider: Tuta

    Different threat model; less IMAP flexibility than RAIDBOXES

  • When: You want privacy-oriented German personal/business mail without hosting coupling

    Consider: Posteo or mailbox (formerly mailbox.org)

    mailbox is also the former RAIDBOXES mail partner and a deeper digital-workplace option

  • When: You need Google/Microsoft suite collaboration, not just domain mailboxes

    Consider: Google Workspace or Microsoft 365

    US Big Tech residency and CLOUD Act profile differ sharply—use only if suite features dominate

Jurisdiction & ownership

Legal entity
Raidboxes GmbH, Hafenstraße 32, 48153 Münster (Amtsgericht Münster HRB 16184)
Governing law
German law (company domicile Münster)
US parent / control
No known US parent
CLOUD Act exposure (indicative)
Medium
Hosting / residency
Email: vendor claims exclusive German data centres and first-party Mail Hosting 2.0 infrastructure (IMAP/SMTP on securemail.pro hostnames); privacy policy still names Heinlein Hosting/mailbox.org under paid email boxes (possible legacy lag). Platform/website: AWS EMEA SARL and DigitalOcean listed for web hosting of the online offer; US-group SaaS includes Intercom, Calendly, Chargebee, Sentry, Google analytics/ads, Mailgun, and others for support, billing, and marketing.

No known US parent; parent group team.blue N.V. is European (Belgium). CLOUD Act score is indicative medium due to US-group cloud/SaaS subprocessors on the commercial platform, not ownership. Separate mailbox content residency claims (Germany) from account/support telemetry paths. Not legal advice.

  • Independent security / no-logs auditNot found
  • ISO 27001Not found
  • SOC 2 / SOC 3Not found
  • GDPR / EU data protectionVendor claimed
  • +4

Considerations & known limitations

  • MediumDomain must be hosted at RAIDBOXES

    New mailboxes require the domain on RAIDBOXES. That is convenient for WP customers and a lock-in factor if you only wanted independent mail.

  • MediumOne connected domain per plan

    Multi-domain operators need multiple plans or another provider; not a Migadu-style multi-domain account model.

  • MediumPGP optional, not default E2EE

    Threat models that assume provider-side unreadability by default are a better fit for Tuta or similar products.

  • MediumUS-group platform subprocessors

    Privacy policy discloses AWS EMEA, DigitalOcean, Intercom, Chargebee, Google tools, Mailgun, and others for website/support/billing/marketing—even while email marketing claims German mail servers. Scope diligence to mailbox vs platform data paths.

  • LowPrivacy policy may lag Mail Hosting 2.0

    §Email box still lists mailbox.org/Heinlein while marketing claims first-party hosting—confirm live stack and subprocessor annex for your contract.

  • MediumNo public ISO/SOC/mail audit

    B Corp is not a security certification. Enterprise security questionnaires may need NDA materials or alternative providers with published audits.

Open questions for due diligence

  • For a new Mail Hosting 2.0 mailbox, is mailbox.org/Heinlein still a subprocessor for mailbox content, or only a legacy path?
  • Which German data-centre operators and exact regions host mail storage and backups (primary + DR)?
  • Does the standard DPA/TOM annex explicitly cover email hosting subprocessors separately from WordPress hosting?
  • What are published RPO/RTO and restore procedures for mailbox backups?
  • Are there any upcoming multi-domain plan options or reseller mail SKUs?

Frequently Asked Questions

Yes for new RAIDBOXES mailboxes: the help centre states that creating a mailbox is only possible if the domain is already hosted with RAIDBOXES. Domains can be transferred to the platform first. Domains still linked to mailbox.org mailboxes continue on that path until migrated to Mail Hosting 2.0.

Product marketing for Mail Hosting 2.0 says mailboxes are now hosted by RAIDBOXES on its own infrastructure, not through the previous mailbox.org cooperation. Legacy customers may still have mailbox.org-linked domains; migration documentation is published in the RAIDBOXES help centre. The public privacy policy may still name Heinlein Hosting / mailbox.org under paid email boxes—confirm the active stack for your account during procurement.

Yes for standard clients: IMAP (e.g. port 993 SSL/TLS) and SMTP (e.g. port 587 STARTTLS) plus webmail. PGP encryption is optional, not a mandatory zero-knowledge default. If your policy requires default E2EE for all messages or open-source clients only, shortlist Tuta or evaluate mailbox.org's encryption tooling instead.

Plans bundle a total mailbox count and storage pool (e.g. Mini/Starter/Pro tiers on the pricing page). Storage can be allocated per mailbox with a documented minimum allocation; more mailboxes means less headroom each. One connected domain per plan is a hard product limit—multi-domain mail estates usually need multiple plans or a different provider such as Migadu.

RAIDBOXES claims email server hosting exclusively in German data centres with GDPR-aligned deletion practices. A B2B DPA (AV contract) can be signed online. Separately, the privacy policy discloses US-group vendors (e.g. AWS EMEA, DigitalOcean, Intercom, Chargebee, analytics tools) for website, support, and billing paths—scope the DPA and TOMs to mailbox content vs platform subprocessors.