Core Announcement: Mailez 1.0.0 Official Release
Mailez 1.0.0 has been officially released, marking a significant advancement in open-source infrastructure for self-hosted email. Key facts:
- Release date: September 14, 2026 (per OSC source)
- Version: 1.0.0 General Availability
- Deployment: Single binary, one-command setup
- Protocols: SMTP, IMAP, POP3, ManageSieve
- Language: Go
- License: AGPL-3.0 (community edition)
Mailez delivers Webmail, admin console, spam filtering, and integrated collaboration tools (calendar, contacts, cloud storage) without assembling existing Postfix/Dovecot-style components. Instead, it relies on the proprietary Mailezine engine implementing each protocol directly.
Fully Proprietary Engine: The Contrasting Architecture
Mailez’s technical approach challenges conventional wisdom. Most self-hosted email stacks (e.g., iRedMail) combine Postfix, Dovecot, and SpamAssassin—resulting in complex configuration and version-mismatch risks. Mailez packages everything into a single binary, with its Mailezine engine handling protocol logic natively.
This yields clear trade-offs:
- Operational upside: Eliminates inter-service compatibility issues; simplified maintenance;
- Risk factor: Protocol stack lacks years of production hardening that mature projects possess.
Core functionality spans Webmail, admin interface, anti-spam, and collaboration modules. Compatibility with Outlook, Mutt, and other standard clients is maintained despite the unconventional architecture.
Capability Comparison
| Dimension | Traditional (Postfix+Dovecot) | Mailez 1.0.0 |
|---|---|---|
| Architecture | Multi-component assembly | Single-binary engine |
| Deployment | Steep configuration curve | One-command setup |
| Protocol support | Requires external plugins | Native implementation |
| Collaboration features | Requires additional software (e.g., Nextcloud) | Built-in calendar/cloud/contacts |
| License | Mixed (MIT/BSD/commercial) | AGPL-3.0 open source |
Note: No performance benchmarks are disclosed (e.g., mail throughput, max users), critical data for production evaluation.
Practical Guidance
Adopt early if you:
- Need simplified email operations without dedicated sysadmin staff;
- Demand full data sovereignty and reject SaaS email;
- Operate small-to-medium teams comfortable with Go ecosystem.
Wait and observe if you:
- Plan large-scale deployment (1,000+ mailboxes): No scaling documentation yet;
- Require mission-critical email reliability: Durability mechanisms unverified;
- Already maintain stable Postfix infrastructure: Migration TCO unclear.
Final Thoughts
Mailez demonstrates that foundational email infrastructure remains open to reinvention. Its success hinges less on architectural novelty and more on community-driven validation of real-world production scenarios.