Community · AGPL-3.0-or-later

The whole server, free to self-host. One Rust binary, apt install away.

OxiMail Community is the complete server under AGPL-3.0-or-later. Mail, calendar, contacts, tasks, server-side filtering, a three-stage spam pipeline, encryption at rest, passkeys — JMAP-native, SQLite-backed, one process you run yourself. The same engine the Pro deployments run, minus the proprietary client apps and enterprise scaling modules.

GitHub repository Why ownership beats “sovereign cloud”

The warmest audience: you already left

Already self-hosting? OxiMail is built to take your mailboxes.

If you run Stalwart, Zimbra, Dovecot or any generic IMAP server, you are exactly who Community is for. The migration tooling pulls your mailboxes, folders and flags across — phased, domain by domain, validated against your real clients before you cut over. You are not rebuilding your mail estate from scratch; you are moving it to a JMAP-native engine that is one binary instead of a stack of six.

From Stalwart

Direct migration path — accounts, mailboxes, folders and message flags carried over.

From Zimbra

Leave the JVM stack behind. Mailbox import with folder and flag mapping.

From Dovecot

IMAP-side migration from the most common self-hosted mail store.

From generic IMAP

Any RFC 3501 source — Courier, Cyrus, a managed host you are leaving.

What ships in Community

A real mail and collaboration server. Not a demo, not a teaser.

Everything below is shipped today and runs in the single AGPL binary.

Mail

JMAP Mail (RFC 8621) plus IMAP4rev2 over TLS. SMTP inbound and outbound. Server-side Sieve filtering with a from-scratch interpreter, managed over ManageSieve.

Calendar, contacts, tasks

JMAP Calendar, Contacts (RFC 9610) and Tasks, with CalDAV and CardDAV for legacy clients — Thunderbird, Apple Mail, eM Client. ICS import and export.

Three-stage spam pipeline

A scored network → content → model pipeline: SPF/DKIM/DMARC/ARC, DNSBL, greylisting, then per-tenant Bayesian classification and URL analysis — built in. No rspamd, no SpamAssassin, no third-party API keys.

Encryption at rest + passkeys

A per-tenant key hierarchy — keys stay on your infrastructure. Phishing-resistant passkey sign-in over WebAuthn.

Legacy protocol support

IMAP, CalDAV and CardDAV translation so existing desktop and mobile clients connect unchanged while you move to JMAP at your own pace.

Fail-loud integrity

No silently dropped mail, no swallowed errors. Any message accepted with a 250 is delivered or quarantined — never to /dev/null.

How it runs

One binary. SQLite. Up to about 2000 accounts.

Community is SQLite-backed and has been validated to around 2000 accounts per instance — enough for a cooperative, an association, a small institution or a personal estate of domains. Install it on Debian or Ubuntu, point your DNS, and you have a full mail and collaboration server in one process, one config, one login. No JVM, no orchestration, no specialist on call to keep a six-service stack standing.

# add the OxiMail apt repository (instructions on GitHub)
curl -fsSL https://get.oximail.ch | sudo bash
sudo apt install oximail

Or grab a release binary from the GitHub releases page and put it anywhere on $PATH. For deployments past Community’s envelope — PostgreSQL, object storage, clustering — those live in the Pro edition.

The licence, plainly

AGPL-3.0-or-later — and what that actually means for you.

Self-hosters run OxiMail for internal use freely. The AGPL’s network-use clause only bites when you operate a modified OxiMail as a service to outside users — then you must offer those users the source of your modifications. If you run it for your own organisation, your family or yourself and don’t expose your fork as a public service, the clause never triggers and you owe nobody anything. The full source is on GitHub, today.

See how Community and Pro divide →

Not in Community

Pro and roadmap, labelled honestly.

Community is the complete mail-and-groupware server. The proprietary client applications (the web Workspace, desktop Sync) and the enterprise scaling layer (PostgreSQL, object storage, clustering, directory integration) are Pro. Drive, Meet, Comms and Shield are roadmap, not shipped — we lead with what runs today and label the future as future. None of it is required to run a complete, sovereign mail server from the AGPL binary.

Pull the source, or read the thesis behind it.

Community lives in the open. Issues, discussions and the JMAP Internet-Drafts we are extending the standard with are all on GitHub.

GitHub organisation See pricing & Pro