2016-06-25 08:57:46 +00:00
# docker-mailserver
2017-07-30 18:07:32 +00:00
[![Build Status ](https://travis-ci.org/tomav/docker-mailserver.svg?branch=master )](https://travis-ci.org/tomav/docker-mailserver) [![Docker Pulls ](https://img.shields.io/docker/pulls/tvial/docker-mailserver.svg )](https://hub.docker.com/r/tvial/docker-mailserver/) [![Docker layers ](https://images.microbadger.com/badges/image/tvial/docker-mailserver.svg )](https://microbadger.com/images/tvial/docker-mailserver) [![Github Stars ](https://img.shields.io/github/stars/tomav/docker-mailserver.svg?label=github%20%E2%98%85 )](https://github.com/tomav/docker-mailserver/) [![Github Stars ](https://img.shields.io/github/contributors/tomav/docker-mailserver.svg )](https://github.com/tomav/docker-mailserver/) [![Github Forks ](https://img.shields.io/github/forks/tomav/docker-mailserver.svg?label=github%20forks )](https://github.com/tomav/docker-mailserver/) [![Gitter ](https://img.shields.io/gitter/room/tomav/docker-mailserver.svg )](https://gitter.im/tomav/docker-mailserver)
2017-02-23 10:48:52 +00:00
2016-04-24 15:37:10 +00:00
2016-04-21 13:28:23 +00:00
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.
2015-03-28 15:44:40 +00:00
Includes:
2015-03-29 12:07:56 +00:00
2019-08-31 07:15:42 +00:00
- [Postfix ](http://www.postfix.org ) with smtp or ldap auth
- [Dovecot ](https://www.dovecot.org ) for sasl, imap (and optional pop3) with ssl support, with ldap auth
- Dovecot is installed from the [Dovecot Community Repo ](https://wiki2.dovecot.org/PrebuiltBinaries )
2016-10-30 13:11:36 +00:00
- saslauthd with ldap auth
2019-08-31 07:15:42 +00:00
- [Amavis ](https://www.amavis.org/ )
- [Spamassasin ](http://spamassassin.apache.org/ ) supporting custom rules
- [ClamAV ](https://www.clamav.net/ ) with automatic updates
- [OpenDKIM ](http://www.opendkim.org )
- [OpenDMARC ](https://github.com/trusteddomainproject/OpenDMARC )
- [Fail2ban ](https://www.fail2ban.org/wiki/index.php/Main_Page )
- [Fetchmail ](http://www.fetchmail.info/fetchmail-man.html )
- [Postscreen ](http://www.postfix.org/POSTSCREEN_README.html )
- [Postgrey ](https://postgrey.schweikert.ch/ )
- basic [Sieve support ](https://github.com/tomav/docker-mailserver/wiki/Configure-Sieve-filters ) using dovecot
2016-01-26 11:56:26 +00:00
- [LetsEncrypt ](https://letsencrypt.org/ ) and self-signed certificates
2019-08-31 07:15:42 +00:00
- [Setup script ](https://github.com/tomav/docker-mailserver/wiki/Setup-docker-mailserver-using-the-script-setup.sh ) to easily configure and maintain your mailserver
2016-12-25 21:54:37 +00:00
- persistent data and state (but think about backups!)
2019-08-31 07:15:42 +00:00
- [Integration tests ](https://travis-ci.org/tomav/docker-mailserver )
- [Automated builds on docker hub ](https://hub.docker.com/r/tvial/docker-mailserver/ )
2015-03-28 15:44:40 +00:00
2015-09-12 08:53:59 +00:00
Why I created this image: [Simple mail server with Docker ](http://tvi.al/simple-mail-server-with-docker/ )
2015-08-26 08:05:40 +00:00
2016-04-24 15:37:10 +00:00
Before you open an issue, please have a look this `README` , the [Wiki ](https://github.com/tomav/docker-mailserver/wiki/ ) and Postfix/Dovecot documentation.
2016-04-20 08:15:51 +00:00
2018-01-09 07:31:15 +00:00
## Requirements
Recommended:
- 1 CPU
- 1GB RAM
Minimum:
- 1 CPU
- 512MB RAM
**Note:** You'll need to deactivate some services like ClamAV to be able to run on a host with 512MB of RAM.
2016-04-24 15:37:10 +00:00
## Usage
2015-03-31 15:28:13 +00:00
2016-05-08 18:10:38 +00:00
#### Get latest image
2016-08-31 13:15:39 +00:00
2016-05-08 18:10:38 +00:00
docker pull tvial/docker-mailserver:latest
2015-03-28 15:04:09 +00:00
2018-02-07 18:37:26 +00:00
#### Get the tools
2016-04-20 08:15:51 +00:00
2018-02-07 18:37:26 +00:00
Download the docker-compose.yml, the .env and the setup.sh files:
2018-03-07 18:33:43 +00:00
2018-02-07 18:37:26 +00:00
curl -o setup.sh https://raw.githubusercontent.com/tomav/docker-mailserver/master/setup.sh; chmod a+x ./setup.sh
2018-03-07 18:33:43 +00:00
2018-02-07 18:37:26 +00:00
curl -o docker-compose.yml https://raw.githubusercontent.com/tomav/docker-mailserver/master/docker-compose.yml.dist
2018-03-07 18:33:43 +00:00
2018-02-07 18:37:26 +00:00
curl -o .env https://raw.githubusercontent.com/tomav/docker-mailserver/master/.env.dist
2016-02-01 14:05:29 +00:00
2018-02-07 18:37:26 +00:00
#### Create a docker-compose environment
2019-09-29 18:17:09 +00:00
- Edit the files `.env` and `env-mailserver` to your liking:
2019-09-20 19:38:13 +00:00
- `.env` contains the configuration for docker-compose
- `env-mailserver` contains the configuration for the mailserver container
2019-09-20 16:40:37 +00:00
- These files supports only simple `VAR=VAL` lines (see [Documentation ](https://docs.docker.com/compose/env-file/ )).
2018-11-11 19:46:53 +00:00
- Don't quote your values.
- Variable substitution is *not* supported (e.g. `OVERRIDE_HOSTNAME=$HOSTNAME.$DOMAINNAME` ).
2019-01-20 10:16:19 +00:00
- Install [docker-compose ](https://docs.docker.com/compose/ ) in the version `1.7` or higher.
2018-02-07 18:37:26 +00:00
2018-10-14 19:41:52 +00:00
#### Start Container
docker-compose up -d mail
2018-02-07 18:37:26 +00:00
#### Create your mail accounts
2018-04-04 16:59:28 +00:00
./setup.sh email add < user @ domain > [< password > ]
2018-02-07 18:37:26 +00:00
#### Generate DKIM keys
./setup.sh config dkim
Now the keys are generated, you can configure your DNS server by just pasting the content of `config/opendkim/keys/domain.tld/mail.txt` in your `domain.tld.hosts` zone.
2019-07-24 12:06:31 +00:00
#### Restart and update the container
2018-02-07 18:37:26 +00:00
2018-10-14 19:41:52 +00:00
docker-compose down
2019-07-24 12:06:31 +00:00
docker pull tvial/docker-mailserver:latest
2018-02-07 18:37:26 +00:00
docker-compose up -d mail
You're done!
And don't forget to have a look at the remaining functions of the `setup.sh` script
2018-03-18 19:15:06 +00:00
#### SPF/Forwarding Problems
If you got any problems with SPF and/or forwarding mails, give [SRS ](https://github.com/roehling/postsrsd/blob/master/README.md ) a try. You enable SRS by setting `ENABLE_SRS=1` . See the variable description for further information.
2018-02-07 18:37:26 +00:00
#### For informational purposes:
Your config folder will be mounted in `/tmp/docker-mailserver/` . To understand how things work on boot, please have a look at [start-mailserver.sh ](https://github.com/tomav/docker-mailserver/blob/master/target/start-mailserver.sh )
2017-01-04 09:05:02 +00:00
2017-03-16 15:45:47 +00:00
`restart: always` ensures that the mail server container (and ELK container when using the mail server together with ELK stack) is automatically restarted by Docker in cases like a Docker service or host restart or container exit.
2018-02-18 12:12:39 +00:00
#### Exposed ports
* 25 receiving email from other mailservers
* 465 SSL Client email submission
* 587 TLS Client email submission
* 143 StartTLS IMAP client
* 993 TLS/SSL IMAP client
* 110 POP3 client
* 995 TLS/SSL POP3 client
`Note: Port 25 is only for receiving email from other mailservers and not for submitting email. You need to use port 465 or 587 for this.`
2018-02-07 18:37:26 +00:00
##### Examples with just the relevant environmental variables:
2017-07-03 11:16:16 +00:00
```yaml
2016-09-07 17:39:27 +00:00
version: '2'
services:
mail:
2017-04-27 16:01:26 +00:00
image: tvial/docker-mailserver:latest
2016-09-07 17:39:27 +00:00
hostname: mail
domainname: domain.com
container_name: mail
ports:
2019-05-05 18:22:51 +00:00
- "25:25"
- "143:143"
- "587:587"
- "993:993"
2016-04-24 15:37:10 +00:00
volumes:
2019-05-05 18:22:51 +00:00
- maildata:/var/mail
- mailstate:/var/mail-state
2019-09-15 13:40:05 +00:00
- maillogs:/var/log/mail
2019-05-05 18:22:51 +00:00
- ./config/:/tmp/docker-mailserver/
2016-12-25 21:54:37 +00:00
environment:
2019-05-05 18:22:51 +00:00
- ENABLE_SPAMASSASSIN=1
- ENABLE_CLAMAV=1
- ENABLE_FAIL2BAN=1
- ENABLE_POSTGREY=1
- ONE_DIR=1
- DMS_DEBUG=0
2016-12-25 21:54:37 +00:00
cap_add:
2019-05-05 18:22:51 +00:00
- NET_ADMIN
- SYS_PTRACE
2016-09-07 17:39:27 +00:00
volumes:
maildata:
driver: local
2016-12-25 21:54:37 +00:00
mailstate:
driver: local
2019-09-15 13:40:05 +00:00
maillogs:
driver: local
2016-09-07 17:39:27 +00:00
```
2016-02-01 14:05:29 +00:00
2017-07-03 11:16:16 +00:00
__for ldap setup__:
```yaml
version: '2'
services:
mail:
image: tvial/docker-mailserver:latest
hostname: mail
domainname: domain.com
container_name: mail
ports:
- "25:25"
- "143:143"
- "587:587"
- "993:993"
volumes:
- maildata:/var/mail
- mailstate:/var/mail-state
2019-09-15 13:40:05 +00:00
- maillogs:/var/log/mail
2017-07-03 11:16:16 +00:00
- ./config/:/tmp/docker-mailserver/
environment:
- ENABLE_SPAMASSASSIN=1
- ENABLE_CLAMAV=1
- ENABLE_FAIL2BAN=1
- ENABLE_POSTGREY=1
- ONE_DIR=1
- DMS_DEBUG=0
- ENABLE_LDAP=1
- LDAP_SERVER_HOST=ldap # your ldap container/IP/ServerName
- LDAP_SEARCH_BASE=ou=people,dc=localhost,dc=localdomain
- LDAP_BIND_DN=cn=admin,dc=localhost,dc=localdomain
- LDAP_BIND_PW=admin
2018-11-03 20:52:17 +00:00
- LDAP_QUERY_FILTER_USER=(& (mail=%s)(mailEnabled=TRUE))
- LDAP_QUERY_FILTER_GROUP=(& (mailGroupMember=%s)(mailEnabled=TRUE))
2019-02-02 10:02:31 +00:00
- LDAP_QUERY_FILTER_ALIAS=(|(& (mailAlias=%s)(objectClass=PostfixBookMailForward))(& (mailAlias=%s)(objectClass=PostfixBookMailAccount)(mailEnabled=TRUE)))
- LDAP_QUERY_FILTER_DOMAIN=(|(& (mail=*@%s)(objectClass=PostfixBookMailAccount)(mailEnabled=TRUE))(& (mailGroupMember=*@%s)(objectClass=PostfixBookMailAccount)(mailEnabled=TRUE))(& (mailalias=*@%s)(objectClass=PostfixBookMailForward)))
2018-11-03 20:52:17 +00:00
- DOVECOT_PASS_FILTER=(& (objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))
- DOVECOT_USER_FILTER=(& (objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))
2017-07-03 11:16:16 +00:00
- ENABLE_SASLAUTHD=1
- SASLAUTHD_MECHANISMS=ldap
- SASLAUTHD_LDAP_SERVER=ldap
- SASLAUTHD_LDAP_BIND_DN=cn=admin,dc=localhost,dc=localdomain
- SASLAUTHD_LDAP_PASSWORD=admin
- SASLAUTHD_LDAP_SEARCH_BASE=ou=people,dc=localhost,dc=localdomain
- POSTMASTER_ADDRESS=postmaster@localhost.localdomain
2018-10-15 19:17:45 +00:00
- POSTFIX_MESSAGE_SIZE_LIMIT=100000000
2017-07-03 11:16:16 +00:00
cap_add:
- NET_ADMIN
2017-10-10 06:15:18 +00:00
- SYS_PTRACE
2017-07-03 11:16:16 +00:00
volumes:
maildata:
driver: local
mailstate:
driver: local
2019-09-15 13:40:05 +00:00
maillogs:
driver: local
2017-07-03 11:16:16 +00:00
```
2018-02-07 18:37:26 +00:00
# Environment variables
2016-04-07 12:20:51 +00:00
2018-02-07 18:37:26 +00:00
Please check [how the container starts ](https://github.com/tomav/docker-mailserver/blob/master/target/start-mailserver.sh ) to understand what's expected. Also if an option doesn't work as documented here, check if you are running the latest image!
2016-04-07 12:20:51 +00:00
2018-02-07 18:37:26 +00:00
Value in **bold** is the default value.
2016-02-01 14:05:29 +00:00
2018-02-07 18:37:26 +00:00
## General
2015-07-16 17:35:11 +00:00
2018-02-07 18:37:26 +00:00
##### DMS_DEBUG
2015-07-16 17:35:11 +00:00
2018-02-07 18:37:26 +00:00
- **0** => Debug disabled
- 1 => Enables debug on startup
2017-08-12 16:09:11 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_CLAMAV
2017-08-12 16:09:11 +00:00
2018-02-07 18:37:26 +00:00
- **0** => Clamav is disabled
- 1 => Clamav is enabled
2015-08-10 10:20:50 +00:00
2018-02-07 18:37:26 +00:00
##### ONE_DIR
2017-01-04 09:09:03 +00:00
2018-02-07 18:37:26 +00:00
- **0** => state in default directories
- 1 => consolidate all states into a single directory (`/var/mail-state`) to allow persistence using docker volumes
2015-06-29 12:55:54 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_POP3
2015-06-29 12:55:54 +00:00
2018-02-07 18:37:26 +00:00
- **empty** => POP3 service disabled
- 1 => Enables POP3 service
2015-12-05 16:32:33 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_FAIL2BAN
2015-06-29 12:55:54 +00:00
2018-02-07 18:37:26 +00:00
- **0** => fail2ban service disabled
- 1 => Enables fail2ban service
2016-04-22 22:31:15 +00:00
2018-02-07 18:37:26 +00:00
If you enable Fail2Ban, don't forget to add the following lines to your `docker-compose.yml` :
2016-04-22 22:31:15 +00:00
2018-02-07 18:37:26 +00:00
cap_add:
- NET_ADMIN
2016-12-23 22:56:39 +00:00
2018-02-07 18:37:26 +00:00
Otherwise, `iptables` won't be able to ban IPs.
2018-03-07 18:33:43 +00:00
2018-02-07 18:37:26 +00:00
##### SMTP_ONLY
2016-12-23 22:56:39 +00:00
2018-02-07 18:37:26 +00:00
- **empty** => all daemons start
- 1 => only launch postfix smtp
2016-12-25 21:54:37 +00:00
2018-02-07 18:37:26 +00:00
##### SSL_TYPE
- **empty** => SSL disabled
- letsencrypt => Enables Let's Encrypt certificates
- custom => Enables custom certificates
2018-12-02 11:59:16 +00:00
- manual => Let you manually specify locations of your SSL certificates for non-standard cases
2018-02-07 18:37:26 +00:00
- self-signed => Enables self-signed certificates
2018-12-02 11:59:16 +00:00
- _any other value_ => SSL required, settings by default
2018-02-07 18:37:26 +00:00
Please read [the SSL page in the wiki ](https://github.com/tomav/docker-mailserver/wiki/Configure-SSL ) for more information.
2018-02-22 07:36:12 +00:00
##### TLS_LEVEL
- **empty** => modern
- modern => Enables TLSv1.2 and modern ciphers only. (default)
- intermediate => Enables TLSv1, TLSv1.1 and TLSv1.2 and broad compatibility ciphers.
- old => NOT implemented. If you really need it, then customize the TLS ciphers overriding postfix and dovecot settings [ wiki](https://github.com/tomav/docker-mailserver/wiki/
2018-03-07 18:33:43 +00:00
##### SPOOF_PROTECTION
Configures the handling of creating mails with forged sender addresses.
2018-03-07 21:14:52 +00:00
- **empty** => Mail address spoofing allowed. Any logged in user may create email messages with a forged sender address. See also [Wikipedia ](https://en.wikipedia.org/wiki/Email_spoofing )(not recommended, but default for backwards compatibility reasons)
2018-03-07 18:33:43 +00:00
- 1 => (recommended) Mail spoofing denied. Each user may only send with his own or his alias addresses. Addresses with [extension delimiters ](http://www.postfix.org/postconf.5.html#recipient_delimiter ) are not able to send messages.
2018-03-18 19:15:06 +00:00
##### ENABLE_SRS
Enables the Sender Rewriting Scheme. SRS is needed if your mail server acts as forwarder. See [postsrsd ](https://github.com/roehling/postsrsd/blob/master/README.md#sender-rewriting-scheme-crash-course ) for further explanation.
- **0** => Disabled
- 1 => Enabled
2018-02-07 18:37:26 +00:00
##### PERMIT_DOCKER
Set different options for mynetworks option (can be overwrite in postfix-main.cf)
- **empty** => localhost only
- host => Add docker host (ipv4 only)
2019-08-02 13:05:00 +00:00
- network => Add the docker default bridge network (172.16.0.0/12); **WARNING** : `docker-compose` might use others (e.g. 192.168.0.0/16) use `PERMIT_DOCKER=connected-networks` in this case
- connected-networks => Add all connected docker networks (ipv4 only)
2018-02-07 18:37:26 +00:00
##### VIRUSMAILS_DELETE_DELAY
Set how many days a virusmail will stay on the server before being deleted
- **empty** => 7 days
##### ENABLE_POSTFIX_VIRTUAL_TRANSPORT
This Option is activating the Usage of POSTFIX_DAGENT to specify a ltmp client different from default dovecot socket.
- **empty** => disabled
- 1 => enabled
##### POSTFIX_DAGENT
Enabled by ENABLE_POSTFIX_VIRTUAL_TRANSPORT. Specify the final delivery of postfix
- **empty**: fail
- `lmtp:unix:private/dovecot-lmtp` (use socket)
- `lmtps:inet:<host>:<port>` (secure lmtp with starttls, take a look at https://sys4.de/en/blog/2014/11/17/sicheres-lmtp-mit-starttls-in-dovecot/)
- `lmtp:<kopano-host>:2003` (use kopano as mailstore)
- etc.
2018-10-15 19:17:45 +00:00
##### POSTFIX\_MAILBOX\_SIZE\_LIMIT
Set the mailbox size limit for all users. If set to zero, the size will be unlimited (default).
- **empty** => 0 (no limit)
##### POSTFIX\_MESSAGE\_SIZE\_LIMIT
Set the message size limit for all users. If set to zero, the size will be unlimited (not recommended!)
2018-10-20 18:10:30 +00:00
- **empty** => 10240000 (~10 MB)
2018-10-15 19:17:45 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_MANAGESIEVE
- **empty** => Managesieve service disabled
- 1 => Enables Managesieve on port 4190
##### OVERRIDE_HOSTNAME
- **empty** => uses the `hostname` command to get the mail server's canonical hostname
- => Specify a fully-qualified domainname to serve mail for. This is used for many of the config features so if you can't set your hostname (e.g. you're in a container platform that doesn't let you) specify it in this environment variable.
##### POSTMASTER_ADDRESS
- **empty** => postmaster@domain.com
- => Specify the postmaster address
2018-05-01 17:57:31 +00:00
2018-02-07 18:37:26 +00:00
##### POSTSCREEN_ACTION
- **enforce** => Allow other tests to complete. Reject attempts to deliver mail with a 550 SMTP reply, and log the helo/sender/recipient information. Repeat this test the next time the client connects.
- drop => Drop the connection immediately with a 521 SMTP reply. Repeat this test the next time the client connects.
- ignore => Ignore the failure of this test. Allow other tests to complete. Repeat this test the next time the client connects. This option is useful for testing and collecting statistics without blocking mail.
2016-12-25 21:54:37 +00:00
2018-05-01 17:57:31 +00:00
2019-09-15 13:40:05 +00:00
## Reports
##### PFLOGSUMM_TRIGGER
2019-09-16 06:05:18 +00:00
Enables regular pflogsumm mail reports.
- **not set** => No report
- daily_cron => Daily report for the previous day
- logrotate => Full report based on the mail log when it is rotated
2019-09-15 13:40:05 +00:00
This is a new option. The old REPORT options are still supported for backwards compatibility.
If this is not set and reports are enabled with the old options, logrotate will be used.
##### PFLOGSUMM_RECIPIENT
2019-09-16 06:05:18 +00:00
Recipient address for pflogsumm reports.
2019-09-15 13:40:05 +00:00
- **not set** => Use REPORT_RECIPIENT or POSTMASTER_ADDRESS
- => Specify the recipient address(es)
##### PFLOGSUMM_SENDER
2019-09-16 06:05:18 +00:00
From address for pflogsumm reports.
2019-09-15 13:40:05 +00:00
- **not set** => Use REPORT_SENDER or POSTMASTER_ADDRESS
- => Specify the sender address
##### LOGWATCH_INTERVAL
Interval for logwatch report.
- **none** => No report is generated
- daily => Send a daily report
- weekly => Send a report every week
##### LOGWATCH_RECIPIENT
Recipient address for logwatch reports if they are enabled.
- **not set** => Use REPORT_RECIPIENT or POSTMASTER_ADDRESS
- => Specify the recipient address(es)
##### REPORT_RECIPIENT (deprecated)
2018-03-18 18:52:28 +00:00
Enables a report being sent (created by pflogsumm) on a regular basis.
2019-09-15 13:40:05 +00:00
- **0** => Report emails are disabled unless enabled by other options
2018-03-18 18:52:28 +00:00
- 1 => Using POSTMASTER_ADDRESS as the recipient
- => Specify the recipient address
2019-09-15 13:40:05 +00:00
##### REPORT_SENDER (deprecated)
2018-05-01 17:57:31 +00:00
Change the sending address for mail report
- **empty** => mailserver-report@hostname
- => Specify the report sender (From) address
2019-09-15 13:40:05 +00:00
##### REPORT_INTERVAL (deprecated)
2018-05-01 17:57:31 +00:00
2019-09-15 13:40:05 +00:00
changes the interval in which logs are rotated and a report is being sent (deprecated).
2018-03-18 18:52:28 +00:00
- **daily** => Send a daily report
- weekly => Send a report every week
- monthly => Send a report every month
2019-09-15 13:40:05 +00:00
Note: This variable used to control logrotate inside the container and sent the pflogsumm report when the logs were rotated.
It is still supported for backwards compatibility, but the new option LOGROTATE_INTERVAL has been added that only rotates
the logs.
##### LOGROTATE_INTERVAL
Defines the interval in which the mail log is being rotated.
- **daily** => Rotate daily.
- weekly => Rotate weekly.
- monthly => Rotate monthly.
Note that only the log inside the container is affected.
The full log output is still available via `docker logs mail` (or your respective container name).
If you want to control logrotation for the docker generated logfile see: [Docker Logging Drivers ](https://docs.docker.com/config/containers/logging/configure/ ).
Also note that by default the logs are lost when the container is recycled. To keep the logs, mount a volume.
Finally the logrotate interval **may** affect the period for generated reports. That is the case when the reports are triggered by log rotation.
2018-03-18 18:52:28 +00:00
2018-02-07 18:37:26 +00:00
## Spamassassin
##### ENABLE_SPAMASSASSIN
2016-12-25 21:54:37 +00:00
- **0** => Spamassassin is disabled
- 1 => Spamassassin is enabled
##### SA_TAG
- **2.0** => add spam info headers if at, or above that level
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1`
##### SA_TAG2
- **6.31** => add 'spam detected' headers at that level
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1`
##### SA_KILL
- **6.31** => triggers spam evasive actions
2019-08-21 10:25:10 +00:00
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1` . By default, the mailserver is configured to quarantine spam emails. If emails are quarantined, they are compressed and stored in a location dependent on the ONE_DIR setting above. If `ONE_DIR=1` the location is /var/mail-state/lib-amavis/virusmails/. If `ONE_DIR=0` it is /var/lib/amavis/virusmails/. These paths are inside the docker container. To inhibit this behaviour and deliver spam emails, set this to a very high value e.g. 100.0.
2016-12-25 21:54:37 +00:00
2017-06-23 19:50:01 +00:00
##### SA_SPAM_SUBJECT
- **\*\*\*SPAM\*\*\*** => add tag to subject if spam detected
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1`
2018-02-07 18:37:26 +00:00
## Fetchmail
2016-04-22 22:31:15 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_FETCHMAIL
2016-12-25 21:54:37 +00:00
- **0** => `fetchmail` disabled
2016-08-21 20:13:13 +00:00
- 1 => `fetchmail` enabled
2017-10-05 06:25:29 +00:00
##### FETCHMAIL_POLL
- **300** => `fetchmail` The number of seconds for the interval
2018-02-07 18:37:26 +00:00
## LDAP
2016-10-30 13:11:36 +00:00
##### ENABLE_LDAP
- **empty** => LDAP authentification is disabled
- 1 => LDAP authentification is enabled
- NOTE:
- A second container for the ldap service is necessary (e.g. [docker-openldap ](https://github.com/osixia/docker-openldap ))
2019-01-22 13:00:53 +00:00
- For preparing the ldap server to use in combination with this container [this ](http://acidx.net/wordpress/2014/06/installing-a-mailserver-with-postfix-dovecot-sasl-ldap-roundcube/ ) article may be helpful
2016-10-30 13:11:36 +00:00
2018-01-25 21:38:41 +00:00
##### LDAP_START_TLS
- **empty** => no
- yes => LDAP over TLS enabled for Postfix
2016-10-30 13:11:36 +00:00
##### LDAP_SERVER_HOST
- **empty** => mail.domain.com
- => Specify the dns-name/ip-address where the ldap-server
- NOTE: If you going to use the mailserver in combination with docker-compose you can set the service name here
##### LDAP_SEARCH_BASE
- **empty** => ou=people,dc=domain,dc=com
- => e.g. LDAP_SEARCH_BASE=dc=mydomain,dc=local
##### LDAP_BIND_DN
- **empty** => cn=admin,dc=domain,dc=com
- => take a look at examples of SASL_LDAP_BIND_DN
##### LDAP_BIND_PW
- **empty** => admin
- => Specify the password to bind against ldap
2017-07-03 11:16:16 +00:00
##### LDAP_QUERY_FILTER_USER
2019-01-20 10:15:26 +00:00
- e.g. `(&(mail=%s)(mailEnabled=TRUE))`
2017-07-03 11:16:16 +00:00
- => Specify how ldap should be asked for users
##### LDAP_QUERY_FILTER_GROUP
2019-01-20 10:15:26 +00:00
- e.g. `(&(mailGroupMember=%s)(mailEnabled=TRUE))`
2017-07-03 11:16:16 +00:00
- => Specify how ldap should be asked for groups
##### LDAP_QUERY_FILTER_ALIAS
2019-01-20 10:15:26 +00:00
- e.g. `(&(mailAlias=%s)(mailEnabled=TRUE))`
2017-07-03 11:16:16 +00:00
- => Specify how ldap should be asked for aliases
2019-01-20 10:15:26 +00:00
2018-11-03 20:52:17 +00:00
##### LDAP_QUERY_FILTER_DOMAIN
2019-01-20 10:15:26 +00:00
- e.g. `(&(|(mail=*@%s)(mailalias=*@%s)(mailGroupMember=*@%s))(mailEnabled=TRUE))`
2018-11-03 20:52:17 +00:00
- => Specify how ldap should be asked for domains
2017-07-03 11:16:16 +00:00
2018-01-25 21:38:41 +00:00
##### DOVECOT_TLS
- **empty** => no
- yes => LDAP over TLS enabled for Dovecot
2018-02-07 18:37:26 +00:00
## Dovecot
2019-01-20 10:15:26 +00:00
The following variables overwrite the default values for ```/etc/dovecot/dovecot-ldap.conf.ext```.
2017-07-03 11:16:16 +00:00
##### DOVECOT_USER_FILTER
2019-01-20 10:15:26 +00:00
- e.g. `(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))`
2019-08-21 10:53:53 +00:00
##### DOVECOT_USER_ATTRS
2019-01-20 10:15:26 +00:00
- e.g. `homeDirectory=home,qmailUID=uid,qmailGID=gid,mailMessageStore=mail`
- => Specify the directory to dovecot attribute mapping that fits your directory structure.
- Note: This is necessary for directories that do not use the [Postfix Book Schema ](test/docker-openldap/bootstrap/schema/mmc/postfix-book.schema ).
- Note: The left-hand value is the directory attribute, the right hand value is the dovecot variable.
- More details on the [Dovecot Wiki ](https://wiki.dovecot.org/AuthDatabase/LDAP/Userdb )
2017-07-03 11:16:16 +00:00
##### DOVECOT_PASS_FILTER
2019-01-20 10:15:26 +00:00
- e.g. `(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))`
2019-08-21 10:53:53 +00:00
##### DOVECOT_PASS_ATTRS
2019-01-20 10:15:26 +00:00
- e.g. `uid=user,userPassword=password`
- => Specify the directory to dovecot variable mapping that fits your directory structure.
- Note: This is necessary for directories that do not use the [Postfix Book Schema ](test/docker-openldap/bootstrap/schema/mmc/postfix-book.schema ).
- Note: The left-hand value is the directory attribute, the right hand value is the dovecot variable.
- More details on the [Dovecot Wiki ](https://wiki.dovecot.org/AuthDatabase/LDAP/PasswordLookups )
2017-07-03 11:16:16 +00:00
2018-02-07 18:37:26 +00:00
## Postgrey
Introducing Postscreen (#799)
* Introduced Postscreen
cheaper, earlier and simpler blocking of zombies/spambots.
From http://postfix.cs.utah.edu/POSTSCREEN_README.html :
As a first layer, postscreen(8) blocks connections from zombies and other spambots that are responsible for about 90% of all spam. It is implemented as a single process to make this defense as cheap as possible.
Things we need to consider:
- Do we need a whitelist/backlist file? (http://postfix.cs.utah.edu/postconf.5.html#postscreen_access_list)
- Via introducing an optional config/postfix-access.cidr
- The only permanent whitelisting I could imagine are monitoring services(which might (still?) behave weird/hastely) or blacklisting backup servers(since no traffic should be coming from them anyway)
- Do we need deep inspections? They are desireable, but these tests are expensive: a good client must disconnect after it passes the test, before it can talk to a real Postfix SMTP server. Considered tests are:
- postscreen_bare_newline_enable (http://postfix.cs.utah.edu/postconf.5.html#postscreen_bare_newline_action)
- postscreen_non_smtp_command_enable (http://postfix.cs.utah.edu/postconf.5.html#postscreen_non_smtp_command_action)
- postscreen_pipelining_enable (http://postfix.cs.utah.edu/postconf.5.html#postscreen_pipelining_action)
- Do we need to make the blacklisting via dnsblocking configurable? It's currently set and weighted as follows, where a score of 3 results in blocking, a score of -1 results in whitelisting:
(*: adds the specified weight to the SMTP client's DNSBL score. Specify a negative number for whitelisting.)
(http://postfix.cs.utah.edu/postconf.5.html#postscreen_dnsbl_sites)
- zen.spamhaus.org*3
- bl.mailspike.net
- b.barracudacentral.org*2
- bl.spameatingmonkey.net
- bl.spamcop.net
- dnsbl.sorbs.net
- psbl.surriel.com
- list.dnswl.org=127.0.[0..255].0*-2
- list.dnswl.org=127.0.[0..255].1*-3
- list.dnswl.org=127.0.[0..255].[2..3]*-4
- What to do when blacklisting? I currently set it to drop. We could
- ignore: Ignore the failure of this test. Allow other tests to complete. Repeat this test the next time the client connects. This option is useful for testing and collecting statistics without blocking mail.
- enforce: Allow other tests to complete. Reject attempts to deliver mail with a 550 SMTP reply, and log the helo/sender/recipient information. Repeat this test the next time the client connects.
- drop: Drop the connection immediately with a 521 SMTP reply. Repeat this test the next time the client connects.
In the end I think we could drop postgrey support. Postscreen replaces postgrey in its entirety, while being more selective and not delaying mail. Especially if we consider using the deep inspection options of postscreen.
Hope that wasn't too much to read! ;)
* main.cf got misformatted..
Don't know how, should be ok now.
* fixed malformatted main.cf & repaired master.cf
* reenabled rbl stuff.. It's cached, therefore doesn't hurt
* fixed tests
* added tests, repaired tests, added info, introduced new Variable POSTSCREEN_ACTION, fixes
2018-02-04 20:31:08 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_POSTGREY
2017-02-06 09:21:18 +00:00
- **0** => `postgrey` is disabled
- 1 => `postgrey` is enabled
##### POSTGREY_DELAY
- **300** => greylist for N seconds
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
##### POSTGREY_MAX_AGE
2017-07-03 11:16:16 +00:00
2017-02-06 09:21:18 +00:00
- **35** => delete entries older than N days since the last time that they have been seen
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
2018-11-01 18:32:36 +00:00
##### POSTGREY_AUTO_WHITELIST_CLIENTS
- **5** => whitelist host after N successful deliveries (N=0 to disable whitelisting)
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
2017-02-06 09:21:18 +00:00
##### POSTGREY_TEXT
2017-07-03 11:16:16 +00:00
2017-02-06 09:21:18 +00:00
- **Delayed by postgrey** => response when a mail is greylisted
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
2018-02-07 18:37:26 +00:00
## SASL Auth
2016-10-30 13:11:36 +00:00
##### ENABLE_SASLAUTHD
2016-12-25 21:54:37 +00:00
- **0** => `saslauthd` is disabled
2016-10-30 13:11:36 +00:00
- 1 => `saslauthd` is enabled
##### SASLAUTHD_MECHANISMS
- empty => pam
2017-07-03 11:16:16 +00:00
- `ldap` => authenticate against ldap server
- `shadow` => authenticate against local user db
- `mysql` => authenticate against mysql db
- `rimap` => authenticate against imap server
2016-10-30 13:11:36 +00:00
- NOTE: can be a list of mechanisms like pam ldap shadow
##### SASLAUTHD_MECH_OPTIONS
- empty => None
- e.g. with SASLAUTHD_MECHANISMS rimap you need to specify the ip-address/servername of the imap server ==> xxx.xxx.xxx.xxx
##### SASLAUTHD_LDAP_SERVER
- empty => localhost
##### SASLAUTHD_LDAP_SSL
2017-07-03 11:16:16 +00:00
- empty or 0 => `ldap://` will be used
- 1 => `ldaps://` will be used
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_LDAP_BIND_DN
- empty => anonymous bind
2019-05-14 19:40:02 +00:00
- specify an object with privileges to search the directory tree
2016-10-30 13:11:36 +00:00
- e.g. active directory: SASLAUTHD_LDAP_BIND_DN=cn=Administrator,cn=Users,dc=mydomain,dc=net
- e.g. openldap: SASLAUTHD_LDAP_BIND_DN=cn=admin,dc=mydomain,dc=net
##### SASLAUTHD_LDAP_PASSWORD
- empty => anonymous bind
##### SASLAUTHD_LDAP_SEARCH_BASE
- empty => Reverting to SASLAUTHD_MECHANISMS pam
- specify the search base
##### SASLAUTHD_LDAP_FILTER
2017-07-03 11:16:16 +00:00
- empty => default filter `(&(uniqueIdentifier=%u)(mailEnabled=TRUE))`
- e.g. for active directory: `(&(sAMAccountName=%U)(objectClass=person))`
- e.g. for openldap: `(&(uid=%U)(objectClass=person))`
2016-10-30 13:11:36 +00:00
2016-04-22 22:31:15 +00:00
##### SASL_PASSWD
- **empty** => No sasl_passwd will be created
2016-04-22 22:35:40 +00:00
- string => `/etc/postfix/sasl_passwd` will be created with the string as password
2016-04-22 22:31:15 +00:00
2018-02-18 19:53:13 +00:00
## SRS (Sender Rewriting Scheme)
##### SRS_EXCLUDE_DOMAINS
- **empty** => Envelope sender will be rewritten for all domains
2019-01-22 13:00:53 +00:00
- provide comma separated list of domains to exclude from rewriting
2018-03-08 21:51:10 +00:00
##### SRS_SECRET
2018-03-10 12:41:20 +00:00
- **empty** => generated when the container is started for the first time
- provide a secret to use in base64
2018-03-08 21:51:10 +00:00
- you may specify multiple keys, comma separated. the first one is used for signing and the remaining will be used for verification. this is how you rotate and expire keys
- if you have a cluster/swarm make sure the same keys are on all nodes
- example command to generate a key: `dd if=/dev/urandom bs=24 count=1 2>/dev/null | base64`
2018-04-02 08:45:58 +00:00
2018-06-19 06:17:32 +00:00
##### SRS_DOMAINNAME
- **empty** => Derived from OVERRIDE_HOSTNAME, DOMAINNAME, or the container's hostname
- Set this if auto-detection fails, isn't what you want, or you wish to have a separate container handle DSNs
2019-01-19 10:10:31 +00:00
## Default Relay Host
#### DEFAULT_RELAY_HOST
- **empty** => don't set default relayhost setting in main.cf
- default host and port to relay all mail through
2018-04-02 08:45:58 +00:00
## Multi-domain Relay Hosts
#### RELAY_HOST
- **empty** => don't configure relay host
- default host to relay mail through
#### RELAY_PORT
- **empty** => 25
- default port to relay mail through
#### RELAY_USER
- **empty** => no default
- default relay username (if no specific entry exists in postfix-sasl-password.cf)
#### RELAY_PASSWORD
- **empty** => no default
- password for default relay user