|POP3 (starttls needed)||127.0.0.1:110|
|IMAP (starttls needed)||127.0.0.1:143|
|SMTP (starttls needed)||127.0.0.1:25|
You can create or edit accounts via the management interface (see above).
Passwords can also be edited via webmail.
By default, spam is filtered by rspamd.
|Block attachments by type (bat, com, exe, dll, vbs, docm, doc, dzip)||FILTER_MIME|
- Clone this repository at first. The command
bin/production.shis a wrapper for docker-compose.
It loads the needed configuration files for using the mailserver in production mode.
- Copy the file
.envand change the variables in it to fit your needs.
They're described in this file later.
bin/production.sh pullto obtain the images.
bin/production.sh up -dcreates and starts the containers.
Volume Management (Where are my files?)
Docker manages the data volumes. The first startup creates four volumes, named data-db, -mail, -tls and -filter.
docker volume inspect <name> to get their real path in the filesystem.
The TLS certificate is stored in the data-tls volume. Obtain its path by running
docker volume inspect
and replace the autogenerated certificate with a real one.
.env file (Configuration)
|MAILNAME||Should match your reverse DNS record|
|POSTMASTER||Mail address of the system's administrator|
|FILTER_MIME||Discard mails with suspicious files attached (see above)|
|ENABLE_IMAP||Enable IMAP4 support|
|ENABLE_POP3||Enable POP3 support|
|ADMIN_USERS||Mail addresses of users that are allowed to use the manager|
Override container configuration
Container configurations can be overridden by creating the file
docker-compose.override.yml in the root folder.
The startup script will load it automatically.
If you need further assistance, check the docker-compose manual.