Go to file
Thomas VIAL e5719ceacb Begening configuration for Letsencrypt support 2015-12-05 16:44:13 +01:00
bin Improved documentation for #14 2015-08-18 20:49:49 +02:00
postfix Added integration testing - #28 2015-10-18 21:02:46 +02:00
spamassassin Fixes #8 - BC BREAK - User configuration is no longer in docker-compose.yml to make it easier to maintain 2015-07-16 19:35:11 +02:00
test Added IMAP connection integration test 2015-11-22 01:57:52 +01:00
.gitignore Begening configuration for Letsencrypt support 2015-12-05 16:44:13 +01:00
.travis.yml Added new line when needed and fixed a test 2015-10-18 21:30:53 +02:00
Dockerfile Fixes #38 (authdeamon pseudo-issue) 2015-11-22 01:48:19 +01:00
LICENCE Added Licence 2015-05-22 14:40:00 +02:00
Makefile Testing Travis config with nc commands 2015-10-19 19:37:49 +02:00
README.md Begening configuration for Letsencrypt support 2015-12-05 16:44:13 +01:00
SSL.md Begening configuration for Letsencrypt support 2015-12-05 16:44:13 +01:00
docker-compose.yml.dist Added a way to generate and configure a specific SSL certificate for postfix #14 2015-08-18 13:13:56 +02:00
start-mailserver.sh Begening configuration for Letsencrypt support 2015-12-05 16:44:13 +01:00

README.md

docker-mailserver

Build Status

A fullstack but simple mail server (smtp, imap, antispam, antivirus...).
Only configuration files, no SQL database. Keep it simple and versioned.
Easy to deploy and upgrade.

Includes:

  • postfix with smtp auth
  • courier-imap with ssl support
  • amavis
  • spamassasin
  • clamav with automatic updates

Why I created this image: Simple mail server with Docker

informations:

  • only config files, no *sql database required
  • mails are stored in /var/mail/${domain}/${username}
  • you should use a data volume container for /var/mail for data persistence
  • email login are full email address (username1@my-domain.com)
  • user accounts are managed in ./postfix/accounts.cf
  • aliases and fowards/redirects are managed in ./postfix/virtual
  • antispam rules are managed in ./spamassassin/rules.cf
  • files must be mounted to /tmp in your container (see docker-compose.yml template)
  • ssl is strongly recommended, you can provide a self-signed certificate, see below
  • includes integration tests
  • builds automated on docker hub

installation

docker pull tvial/docker-mailserver

build

docker build -t tvial/docker-mailserver .

run

docker run --name mail -v "$(pwd)/postfix":/tmp/postfix -v "$(pwd)/spamassassin":/tmp/spamassassin -p "25:25" -p "143:143" -p "587:587" -p "993:993" -h mail.my-domain.com -t tvial/docker-mailserver
mail:
  # image: tvial/docker-mailserver
  build: .
  hostname: mail
  domainname: my-domain.com
  ports:
  - "25:25"
  - "143:143"
  - "587:587"
  - "993:993"
  volumes:
  - ./spamassassin:/tmp/spamassassin/
  - ./postfix:/tmp/postfix/

Volumes allow to:

  • Insert custom antispam rules
  • Manage mail users, passwords and aliases
  • Manage SSL certificates

usage

docker-compose up -d mail

client configuration

imap

username: username1@my-domain.com password: server: imap port: 143 or 993 with ssl (recommended) imap path prefix: INBOX auth method: md5 challenge-response

smtp

smtp port: 25 or 587 with ssl (recommended) username: username1@my-domain.com password: auth method: md5 challenge-response

todo

Things to do or to improve are stored on Github, some open by myself. Feel free to improve this docker image.

wanna help?

Fork, improve, add tests and PR. ;-)