Mox is a modern full-featured open source secure mail server for low-maintenance self-hosted email.

For more details, see the mox website, https://www.xmox.nl.

See Quickstart below to get started.

Features

Quick and easy to start/maintain mail server, for your own domain(s).
SMTP (with extensions) for receiving, submitting and delivering email.
IMAP4 (with extensions) for giving email clients access to email.
Webmail for reading/sending email from the browser.
SPF/DKIM/DMARC for authenticating messages/delivery, also DMARC aggregate reports.
Reputation tracking, learning (per user) host-, domain- and sender address-based reputation from (Non-)Junk email classification.
Bayesian spam filtering that learns (per user) from (Non-)Junk email.
Slowing down senders with no/low reputation or questionable email content (similar to greylisting). Rejected emails are stored in a mailbox called Rejects for a short period, helping with misclassified legitimate synchronous signup/login/transactional emails.
Internationalized email (EIA), with unicode in email address usernames ("localparts"), and in domain names (IDNA).
Automatic TLS with ACME, for use with Let's Encrypt and other CA's.
DANE and MTA-STS for inbound and outbound delivery over SMTP with STARTTLS, including REQUIRETLS and with incoming/outgoing TLSRPT reporting.
Web admin interface that helps you set up your domains, accounts and list aliases (instructions to create DNS records, configure SPF/DKIM/DMARC/TLSRPT/MTA-STS), for status information, and modifying the configuration file.
Account autodiscovery (with SRV records, Microsoft-style, Thunderbird-style, and Apple device management profiles) for easy account setup (though client support is limited).
Webserver with serving static files and forwarding requests (reverse proxy), so port 443 can also be used to serve websites.
Simple HTTP/JSON API for sending transaction email and receiving delivery events and incoming messages (webapi and webhooks).
Prometheus metrics and structured logging for operational insight.
"mox localserve" subcommand for running mox locally for email-related testing/developing, including pedantic mode.
Most non-server Go packages mox consists of are written to be reusable.

Mox is available under the MIT-license and was created by Mechiel Lukkien, mechiel@ueber.net. Mox includes BSD-3-claused code from the Go Authors, and the Public Suffix List by Mozilla under Mozilla Public License, v2.0.

Mox has automated tests, including for interoperability with Postfix for SMTP. Mox is manually tested with email clients: Mozilla Thunderbird, mutt, iOS Mail, macOS Mail, Android Mail, Microsoft Outlook. Mox is also manually tested to interoperate with popular cloud providers: gmail.com, outlook.com, yahoo.com, proton.me.

The code is heavily cross-referenced with the RFCs for readability/maintainability.

Quickstart

The easiest way to get started with serving email for your domain is to get a (virtual) machine dedicated to serving email, name it [host].[domain] (e.g. mail.example.com). Having a DNSSEC-verifying resolver installed, such as unbound, is highly recommended. Run as root:

# Create mox user and homedir (or pick another name or homedir):
useradd -m -d /home/mox mox

cd /home/mox
... compile or download mox to this directory, see below ...

# Generate config files for your address/domain:
./mox quickstart you@example.com

The quickstart:

Creates configuration files mox.conf and domains.conf.
Adds the domain and an account for the email address to domains.conf
Generates an admin and account password.
Prints the DNS records you need to add, for the machine and domain.
Prints commands to start mox, and optionally install mox as a service.

A machine that doesn't already run a webserver is highly recommended because modern email requires HTTPS, and mox currently needs to run a webserver for automatic TLS with ACME. You could combine mox with an existing webserver, but it requires a lot more configuration. If you want to serve websites on the same machine, consider using the webserver built into mox. It's pretty good! If you want to run an existing webserver on port 443/80, see mox help quickstart.

After starting, you can access the admin web interface on internal IPs.

Download

Download a mox binary from https://beta.gobuilds.org/github.com/mjl-/mox@latest/linux-amd64-latest/.

Symlink or rename it to "mox".

The URL above always resolves to the latest release for linux/amd64 built with the latest Go toolchain. See the links at the bottom of that page for binaries for other platforms.

Compiling

You can easily (cross) compile mox yourself. You need a recent Go toolchain installed. Run go version, it must be >= 1.24. Download the latest version from https://go.dev/dl/ or see https://go.dev/doc/manage-install.

To download the source code of the latest release, and compile it to binary "mox":

GOBIN=$PWD CGO_ENABLED=0 go install github.com/mjl-/mox@latest

Mox only compiles for and fully works on unix systems. Mox also compiles for Windows, but "mox serve" does not yet work, though "mox localserve" (for a local test instance) and most other subcommands do. Mox does not compile for Plan 9.

Docker

Although not recommended, you can also run mox with docker image r.xmox.nl/mox, with tags like v0.0.1 and v0.0.1-go1.20.1-alpine3.17.2, see https://r.xmox.nl/r/mox/. See https://github.com/mjl-/mox/blob/main/docker-compose.yml to get started.

New docker images aren't (automatically) generated for new Go runtime/compile releases.

It is important to run with docker host networking, so mox can use the public IPs and has correct remote IP information for incoming connections (important for junk filtering and rate-limiting).

Development

See develop.txt for instructions/tips for developing on mox.

Roadmap

"mox setup" command, using admin web interface for interactive setup
Automate DNS management, for setup and maintenance, such as DANE/DKIM key rotation
Config options for "transactional email domains", for which mox will only send messages
Encrypted storage of files (email messages, TLS keys), also with per account keys
Recognize common deliverability issues and help postmasters solve them
JMAP, IMAP OBJECTID extension, IMAP JMAPACCESS extension
Calendaring with CalDAV/iCal
Introbox, to which first-time senders are delivered
Add special IMAP mailbox ("Queue?") that contains queued but undelivered messages, updated with IMAP flags/keywords/tags and message headers.
External addresses in aliases/lists.
Autoresponder (out of office/vacation)
Mailing list manager
IMAP extensions for "online"/non-syncing/webmail clients (SORT (including DISPLAYFROM, DISPLAYTO), THREAD, PARTIAL, CONTEXT=SEARCH CONTEXT=SORT ESORT, FILTERS)
IMAP ACL support, for account sharing (interacts with many extensions and code)
Improve support for mobile clients with extensions: IMAP URLAUTH, SMTP CHUNKING and BINARYMIME, IMAP CATENATE
Privilege separation, isolating parts of the application to more restricted sandbox (e.g. new unauthenticated connections)
Using mox as backup MX
Sieve for filtering (for now see Rulesets in the account config)
ARC, with forwarded email from trusted source
Milter support, for integration with external tools
SMTP DSN extension
IMAP Sieve extension, to run Sieve scripts after message changes (not only new deliveries)
OAUTH2 support, for single sign on
Forwarding (to an external address)

There are many smaller improvements to make as well, search for "todo" in the code.

Not supported/planned

There is currently no plan to implement the following. Though this may change in the future.

Functioning as an SMTP relay without authentication
POP3
Delivery to (unix) OS system users (mbox/Maildir)
Support for pluggable delivery mechanisms

FAQ - Frequently Asked Questions

Why a new mail server implementation?

Mox aims to make "running a mail server" easy and nearly effortless. Excellent quality (open source) mail server software exists, but getting a working setup typically requires you configure half a dozen services (SMTP, IMAP, SPF/DKIM/DMARC, spam filtering), which are often written in C (where small bugs often have large consequences). That seems to lead to people no longer running their own mail servers, instead switching to one of the few centralized email providers. Email with SMTP is a long-time decentralized messaging protocol. To keep it decentralized, people need to run their own mail server. Mox aims to make that easy.

Where is the documentation?

To keep mox as a project maintainable, documentation is integrated into, and generated from the code.

A list of mox commands, and their help output, are at https://www.xmox.nl/commands/.

Mox is configured through configuration files, and each field comes with documentation. See https://www.xmox.nl/config/ for config files containing all fields and their documentation.

You can get the same information by running "mox" without arguments to list its subcommands and usage, and "mox help [subcommand]" for more details.

The example config files are printed by "mox config describe-static" and "mox config describe-dynamic".

If you're missing some documentation, please create an issue describing what is unclear or confusing, and we'll try to improve the documentation.

Is Mox affected by SMTP smuggling?

Mox itself is not affected: it only treats "\r\n.\r\n" as SMTP end-of-message. Bu

Mox

Install / Use

README