bf04fb8a1a
before, we used heuristics to decide when to train/untrain a message as junk or nonjunk: the message had to be seen, be in certain mailboxes. then if a message was marked as junk, it was junk. and otherwise it was nonjunk. this wasn't good enough: you may want to keep some messages around as neither junk or nonjunk. and that wasn't possible. ideally, we would just look at the imap $Junk and $NotJunk flags. the problem is that mail clients don't set these flags, or don't make it easy. thunderbird can set the flags based on its own bayesian filter. it has a shortcut for marking Junk and moving it to the junk folder (good), but the counterpart of notjunk only marks a message as notjunk without showing in the UI that it was marked as notjunk. there is also no "move and mark as notjunk" mechanism. e.g. "archive" does not mark a message as notjunk. ios mail and mutt don't appear to have any way to see or change the $Junk and $NotJunk flags. what email clients do have is the ability to move messages to other mailboxes/folders. so mox now has a mechanism that allows you to configure mailboxes that automatically set $Junk or $NotJunk (or clear both) when a message is moved/copied/delivered to that folder. e.g. a mailbox called junk or spam or rejects marks its messags as junk. inbox, postmaster, dmarc, tlsrpt, neutral* mark their messages as neither junk or notjunk. other folders mark their messages as notjunk. e.g. list/*, archive. this functionality is optional, but enabled with the quickstart and for new accounts. also, mox now keeps track of the previous training of a message and will only untrain/train if needed. before, there probably have been duplicate or missing (un)trainings. this also includes a new subcommand "retrain" to recreate the junkfilter for an account. you should run it after updating to this version. and you should probably also modify your account config to include the AutomaticJunkFlags. |
||
|---|---|---|
| .go | ||
| autotls | ||
| config | ||
| dkim | ||
| dmarc | ||
| dmarcdb | ||
| dmarcrpt | ||
| dns | ||
| dnsbl | ||
| dsn | ||
| http | ||
| imapclient | ||
| imapserver | ||
| iprev | ||
| junk | ||
| message | ||
| metrics | ||
| mlog | ||
| mox- | ||
| moxio | ||
| moxvar | ||
| mtasts | ||
| mtastsdb | ||
| publicsuffix | ||
| queue | ||
| ratelimit | ||
| rfc | ||
| scram | ||
| smtp | ||
| smtpclient | ||
| smtpserver | ||
| spf | ||
| store | ||
| subjectpass | ||
| testdata | ||
| tlsrpt | ||
| tlsrptdb | ||
| updates | ||
| vendor | ||
| .dockerignore | ||
| .gitignore | ||
| .jshintrc | ||
| checkhtmljs | ||
| compatibility.txt | ||
| ctl.go | ||
| doc.go | ||
| docker-compose-imaptest.yml | ||
| docker-compose-integration.yml | ||
| Dockerfile | ||
| Dockerfile.imaptest | ||
| export.go | ||
| gendoc.sh | ||
| go.mod | ||
| go.sum | ||
| import.go | ||
| import_test.go | ||
| integration_test.go | ||
| junk.go | ||
| LICENSE.MIT | ||
| LICENSE.MPLv2.0 | ||
| main.go | ||
| main_test.go | ||
| Makefile | ||
| mox.service | ||
| quickstart.go | ||
| README.md | ||
| serve.go | ||
| start.go | ||
| tools.go | ||
| updates.go | ||
Mox is a modern full-featured open source secure mail server for low-maintenance self-hosted email.
See Quickstart below to get started.
Mox features:
- Quick and easy to start/maintain mail server, for your own domain(s).
- SMTP for receiving and submitting email.
- IMAP4 for giving email clients access to email.
- Automatic TLS with ACME, for use with Let's Encrypt and other CA's.
- SPF, verifying that a remote host is allowed to sent email for a domain.
- DKIM, verifying that a message is signed by the claimed sender domain, and for signing emails sent by mox for others to verify.
- DMARC, for enforcing SPF/DKIM policies set by domains. Incoming DMARC aggregate reports are analyzed.
- Reputation tracking, learning (per user) host- and domain-based reputation from (Non-)Junk email.
- 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, with unicode names in domains and usernames ("localparts").
- TLSRPT, parsing reports about TLS usage and issues.
- MTA-STS, for ensuring TLS is used whenever it is required. Both serving of policies, and tracking and applying policies of remote servers.
- Web admin interface that helps you set up your domains and accounts (instructions to create DNS records, configure SPF/DKIM/DMARC/TLSRPT/MTA-STS), for status information, managing accounts/domains, and modifying the configuration file.
- Autodiscovery (with SRV records, Microsoft-style and Thunderbird-style) for easy account setup (though not many clients support it).
- Prometheus metrics and structured logging for operational insight.
Not supported (but perhaps in the future):
- Webmail
- Functioning as SMTP relay
- HTTP-based API for sending messages and receiving delivery feedback
- Forwarding (to an external address)
- Autoresponders
- POP3
- Delivery to (unix) OS system users
- Sieve for filtering
- PGP or S/MIME
- Mailing list manager
- Calendaring
- Support for pluggable delivery mechanisms.
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.
Mox is implemented in Go, a modern safe programming language, and has a focus on security.
Mox is available under the MIT-license. Mox includes the Public Suffix List by Mozilla, under Mozilla Public License, v. 2.0.
Mox was created by Mechiel Lukkien, mechiel@ueber.net.
For discussions/talk, join #mox on irc.oftc.net, or #mox on the "Gopher slack".
Download
You can easily (cross) compile mox if you have a recent Go toolchain installed (see "go version", it must be >= 1.19; otherwise, see https://go.dev/dl/ or https://go.dev/doc/manage-install and $HOME/go/bin):
GOBIN=$PWD go install github.com/mjl-/mox@latest
Or you can download a binary built with the latest Go toolchain from https://beta.gobuilds.org/github.com/mjl-/mox, and symlink or rename it to "mox".
Verify you have a working mox binary:
./mox version
Note: Mox only compiles/works on unix systems, not on Plan 9 or Windows.
Quickstart
The easiest way to get started with serving email for your domain is to get a vm/machine dedicated to serving email, name it [host].[domain], login as an admin user, e.g. /home/service, download mox, and generate a configuration for your desired email address at your domain:
./mox quickstart you@example.com
This creates an account, generates a password and configuration files, prints the DNS records you need to manually create and prints commands to set permissions and install mox as a service.
If you already have email configured for your domain, or if you are already sending email for your domain from other machines/services, you should modify the suggested configuration and/or DNS records.
A dedicated machine is highly recommended because modern email requires HTTPS, also for automatic TLS. You can combine mox with an existing webserver, but it requires more configuration.
After starting, you can access the admin web interface on internal IPs.
FAQ - Frequently Asked Questions
Why a new mail server implementation?
Mox aims to make "running a mail server" easy and nearly effortless. Excellent quality mail server software exists, but getting a working setup typically requires you configure half a dozen services (SMTP, IMAP, SPF/DKIM/DMARC, spam filtering). 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?
See all commands and help text at https://pkg.go.dev/github.com/mjl-/mox/, and example config files at https://pkg.go.dev/github.com/mjl-/mox/config/.
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".
Mox is still in early stages, and documentation is still limited. Please create an issue describing what is unclear or confusing, and we'll try to improve the documentation.
How do I import/export email?
Use the "mox import maildir" or "mox import mbox" subcommands. You could also use your IMAP email client, add your mox account, and copy or move messages from one account to the other.
Similarly, see the "mox export maildir" and "mox export mbox" subcommands to export email.
How can I help?
Mox needs users and testing in real-life setups! So just give it a try, send and receive emails through it with your favourite email clients, and file an issue if you encounter a problem or would like to see a feature/functionality implemented.
Instead of switching your email for your domain over to mox, you could simply configure mox for a subdomain, e.g. [you]@moxtest.[yourdomain].
If you have experience with how the email protocols are used in the wild, e.g. compatibility issues, limitations, anti-spam measures, specification violations, that would be interesting to hear about.
Pull requests for bug fixes and new code are welcome too. If the changes are large, it helps to start a discussion (create a ticket) before doing all the work.
How do I change my password?
Regular users (doing IMAP/SMTP with authentication) can change their password at the account page, e.g. http://127.0.0.1/account/. Or you can set a password with "mox setaccountpassword".
The admin password can be changed with "mox setadminpassword".
How do I configure a second mox instance as a backup MX?
Unfortunately, mox does not yet provide an option for that. Mox does spam filtering based on reputation of received messages. It will take a good amount of work to share that information with a backup MX. Without that information, spammer could use a backup MX to get their spam accepted. Until mox has a proper solution, you can simply run a single SMTP server.
How secure is mox?
Security is high on the priority list for mox. Mox is young, so don't expect no bugs at all. Mox does have automated tests for some security aspects, e.g. for login, and uses fuzzing. Mox is written in Go, so some classes of bugs such as buffer mishandling do not typically result in privilege escalation. Of course logic bugs will still exist. If you find any security issues, please email them to mechiel@ueber.net.