Independent review
Assessment — OpenShip Mail is a feature inside the broader Openship deployment platform, not a standalone repository or isolated mail appliance. A self-hosted Openship control plane connects to a clean Ubuntu or Debian server, transfers a bundled iRedMail engine, and orchestrates Postfix, Dovecot, antispam components, TLS, DKIM, domains, mailboxes, backups, and health checks. It can then deploy a Zero-derived browser inbox that connects over IMAP and SMTP.
The wizard meaningfully shortens a difficult installation, but the operator still runs Internet-facing mail. Before setup, you need a controlled domain, DNS editing, SSH access to a target host, outbound port 25, and access to the VPS provider's PTR controls. During setup, DNS and reverse DNS require deliberate confirmation. Afterward, SPF, DKIM, DMARC, certificates, abuse controls, software updates, backups, blocklists, reputation, and warm-up remain operational responsibilities.
Setup difficulty — advanced even with automation. The control plane itself uses PostgreSQL and Redis, while each mail setup occupies a server. The installer can warn and continue when port 25 is blocked, but delivery cannot succeed until the provider permits it. New domains may initially land in spam. The webmail deploy path is dashboard-only at review time, and mail functions are hidden from the managed Openship Cloud interface.
This is a compelling fit for experienced self-hosters or infrastructure teams that want a guided, inspectable path to domain mail and are prepared to monitor deliverability. It is a poor fit for teams that expect Gmail-like operations without mail expertise. Google Workspace and Microsoft 365 replace the hosted mailbox category; Mailgun, SES, and SendGrid overlap more with outbound transactional delivery, so none is a perfect one-to-one comparison.
GitHub reports main active, enabled, unarchived, and Apache-2.0 at repository level. The current reviewed HEAD, ae1e2c04 from 2026-07-22, is newer than the research dossier's earlier commit and retains the verified Mail architecture and guide. The bundled iRedMail engine separately carries GPLv3, so a one-line Apache label is incomplete for the Mail feature and exact component scope needs review without drawing legal conclusions. The latest release was v0.1.11 and its email artifact was named for linux-amd64; ARM operators should verify current assets or build support.
Practical fit
Best for experienced operators who value automated self-hosted mail provisioning and can own DNS, PTR, deliverability, abuse response, upgrades, and sensitive backups.
Useful for
Provision and administer domain email on an operator-controlled server Manage domains, mailboxes, quotas, DNS checks, health, tests, and backups Deploy a Zero-based webmail client over the provisioned IMAP and SMTP services
Dependencies
Self-hosted Openship control plane with PostgreSQL and Redis A clean Ubuntu or Debian target reachable over SSH Postfix, Dovecot, iRedMail components, OpenResty, Certbot, and antispam services Bun-based webmail runtime connecting through IMAPS and SMTP
External services
Domain DNS provider and VPS reverse-DNS controls VPS provider that permits outbound SMTP on port 25 Certificate authority access for Let's Encrypt
Deployment notes
Run only from self-hosted Openship, dedicate a suitable target host, confirm port 25 before installation, publish and verify MX/SPF/DKIM/DMARC plus PTR, secure SSH and backups, monitor daemon health and reputation, and verify architecture support for the selected webmail release artifact.
Limitations
The Mail feature is unavailable in managed Openship Cloud. Each mail setup occupies its own server and only one installation runs per Openship instance at a time. Port 25, DNS, PTR, deliverability, reputation, and abuse handling remain operator responsibilities. Backups can contain messages, password hashes, DKIM private keys, and other sensitive material. The parent repository and bundled mail engine have different license declarations.
Project media
