English | 简体中文

mailez — mail easy

Self-hosted email that scales with you: from a personal mailbox of one to ten-thousand-person organizations — teams, companies and public-sector agencies alike. Send and receive mail with your own domain, keep your data in your own hands, and enjoy a webmail that actually feels good to use. One command deploys the whole thing — mail delivery, spam filtering, authentication, admin console and webmail.

Who is it for?

• Individuals — a mailbox that is truly yours, not rented from a mail provider
• Businesses and organizations — domain mail for everyone, with data kept 100% in-house
• Public sector — strict data-sovereignty and privacy requirements, fully covered

What you get

Webmail that feels like a native app

• Live, not refreshed — new mail arrives over a real-time push channel, so

• Conversation view keeps threads readable — replies under one subject

• Three-pane layout — folders, list and reading pane side by side; the

• Search that just works — type naturally (from:, to:, has:attachment,

• Keyboard-first — press / to search, ⌘K for the command palette, ?

• Day-to-day mail tasks made easy — conversation threads, quick reply

• A workbench, not just an inbox — the home dashboard surfaces recent

• Privacy features built in — PGP sign and encrypt (distinct from your

• Works offline — installs as a PWA; light/dark themes and three list

Mail is just the start

• Calendar — events with reminders, shared calendars, and subscriptions

• Contacts — vCard import/export, duplicate merging, and CardDAV sync for

• Drive — upload and organize files, share by link, restore from trash;

Any device, any client

• Standard protocols — SMTP / IMAP / POP3 (implicit TLS available), plus

• Delta Chat — generate a login QR in settings and scan it with the

• App tokens — per-client tokens you can issue and revoke from settings

An admin console that doesn't feel like admin work

• Manage everything in one place — domains, mailboxes, aliases, relays,

• One-click DKIM — generate signing keys with a status hint, so your mail

• Domain health checks — the Health page live-verifies MX / SPF / DMARC /

• See who did what — audit log of admin actions and role-based access

• Backup or migrate easily — export and import your whole configuration

Trust and security under the hood

• Spam filtering that works — Rspamd learns from your reporting; DKIM /

• Transport security — MTA-STS and DANE protect mail in transit;

• Malware scanning & content controls — attachments are scanned for

Quick start

Two self-contained deployment tiers ship as compose files, managed by one entry point:

| Tier | Engine | Storage | |---|---|---| | dev (default) | mailezine | SQLite + Pebble + local FS | | production | mailezine | SQLite + Pebble + local FS (MySQL/PostgreSQL optional) |

Both tiers run the same mailezine engine — same protocols, same features at the mail layer, same upgrade path. They differ only in orientation (dev builds from source on the host; production is a fully containerized stack) and control-plane storage (SQLite by default, with MySQL/PostgreSQL available behind compose profiles). Existing deployments on the traditional multi-process mail architecture migrate in place with mailezine migrate.

./deploy/mailezctl.sh up              # dev tier
./deploy/mailezctl.sh up ce    # production tier (pull prebuilt images)

The dev tier expects the backend on the host at :8080 (build the images once with docker buildx bake from the repo root; details in docs/dev-setup.md). The production tier is fully containerized and publishes:

| Port | What's there | |---|---| | http://localhost:8082 | Admin console | | http://localhost:8083 | Webmail | | http://localhost:8081 | Backend API (for developers) | | 25/465/587/143/993/4190 … | Mail protocols (SMTP / IMAP / ManageSieve) |

Two prerequisites before the first up:

• Sibling checkout. The mailezine engine image builds from the sibling

• Linux hosts: data-directory ownership. The backend runs as uid 1000

Note that the mail ports above bind to loopback by default (safe for evaluations); a real deployment publishes them on the external interface via the compose port mappings.

mailezctl reads deploy/mailez.env (copy mailez.env.example, then set MAILEZ_SECRET_KEY and MAILEZ_STACK_SECRET). Raw docker compose invocations must pass --env-file mailez.env — the ${MAILEZ_STACK_SECRET:?} interpolation reads shell env and --env-file only, never the services' env_file. Host port mappings are overridable there too (MAILEZ_HTTP_PORT, MAILEZ_ADMIN_PORT, …) for machines where 80/443/8082 are already taken.

TLS is off by default for local testing. For production, follow deploy/certs/README.md to enable automatic certificates.

After the stack is up, provision the admin account inside the container (the backend image ships a one-shot seeder; no local Go required):

docker compose --env-file deploy/mailez.env -f deploy/docker-compose.ce.yml exec backend mailez-seed
default: admin@$MAILEZ_DOMAIN ([email protected] on the shipped example
domain) / MailezDemo2026! — override with
MAILEZ_ADMIN_EMAIL / MAILEZ_ADMIN_PASSWORD before seeding

Then verify the whole mail path end to end (requires Go on the host):

cd backend
go run ./cmd/e2e    # sends a test mail, checks delivery, DKIM and spam filtering

Tech stack (for developers)

• Backend: Go + Fiber, GORM, Redis
• Frontend: Next.js (React) — separate admin and webmail apps
• Mail engine: mailezine (a single Go binary) speaks

• More details: docs/dev-setup.md,

License

AGPL-3.0 — GNU Affero General Public License v3.0.

• Self-hosting is unencumbered — deploy, modify and run it for yourself

• Copyleft by design — anyone distributing mailez or serving a modified

• Commercial licensing — closed-source use, SaaS/managed offerings and