2016-06-25 08:57:46 +00:00
# docker-mailserver
2020-09-05 14:19:12 +00:00
[![Build Status][build_status]][build_status::travis] [![Docker Pulls][docker_pulls]][docker_hub_pulls::hub] [![Docker layers][layers]][layers_outer::badger] [![Github Stars][gh_stars]][repo] [![Contributors][contributors]][repo] [![Github Forks][forks]][repo] [![Gitter][shields::gitter]][gitter]
[build_status]: https://travis-ci.org/tomav/docker-mailserver.svg?branch=master
[build_status::travis]: https://travis-ci.org/tomav/docker-mailserver
[docker_pulls]: https://img.shields.io/docker/pulls/tvial/docker-mailserver.svg
[docker_hub_pulls::hub]: https://hub.docker.com/r/tvial/docker-mailserver/
[layers]: https://images.microbadger.com/badges/image/tvial/docker-mailserver.svg
[layers_outer::badger]: https://microbadger.com/images/tvial/docker-mailserver
[gh_stars]: https://img.shields.io/github/stars/tomav/docker-mailserver.svg?label=github%20%E2%98%85
[repo]: https://github.com/tomav/docker-mailserver/
[contributors]: https://img.shields.io/github/contributors/tomav/docker-mailserver.svg
[forks]: https://img.shields.io/github/forks/tomav/docker-mailserver.svg?label=github%20forks
[shields::gitter]: https://img.shields.io/gitter/room/tomav/docker-mailserver.svg
[gitter]: https://gitter.im/tomav/docker-mailserver
2017-02-23 10:48:52 +00:00
2020-09-24 12:54:21 +00:00
A fullstack but simple mail server (SMTP, IMAP, Antispam, Antivirus...).
2016-04-21 13:28:23 +00:00
Only configuration files, no SQL database. Keep it simple and versioned.
Easy to deploy and upgrade.
2015-03-28 15:44:40 +00:00
2020-09-09 15:19:48 +00:00
Why I created this image: [Simple Mail Server with Docker ](http://tvi.al/simple-mail-server-with-docker/ )
2020-09-24 12:54:21 +00:00
1. [Announcements ](#announcements )
2020-09-09 15:19:48 +00:00
2. [Includes ](#includes )
3. [Issues & Contributing ](#issues--contributing )
4. [Requirements ](#requirements )
5. [Usage ](#usage )
6. [Examples ](#examples )
7. [Environment Variables ](#environment-variables )
2020-09-05 14:19:12 +00:00
2020-09-24 12:54:21 +00:00
## Announcements
2020-03-16 17:38:28 +00:00
2020-09-24 12:54:21 +00:00
1. Debian Buster is now Docker base image
- Filebeat was removed
- Dovecot was downgraded
2. ELK was removed
3. New contributing guidelines were added
2020-09-26 13:11:52 +00:00
4. Added option to use non-default network interface
2020-03-16 17:38:28 +00:00
2020-09-05 14:19:12 +00:00
## Includes
2015-03-29 12:07:56 +00:00
2020-09-24 12:54:21 +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, sieve and [quotas ](https://github.com/tomav/docker-mailserver/wiki/Configure-Accounts#mailbox-quota )
- 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/ )
2019-12-03 13:52:26 +00:00
- Plus addressing (a.k.a. [extension delimiters ](http://www.postfix.org/postconf.5.html#recipient_delimiter ))
works out of the box: email for `you+extension@example.com` go to `you@example.com`
2015-03-28 15:44:40 +00:00
2020-09-05 14:19:12 +00:00
## Issues & Contributing
2015-08-26 08:05:40 +00:00
2020-09-05 14:19:12 +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. If you'd like to contribute, read [`CONTRIBUTING.md` ](./CONTRIBUTING.md ) thoroughly.
2016-04-20 08:15:51 +00:00
2018-01-09 07:31:15 +00:00
## Requirements
Recommended:
2020-09-04 06:42:12 +00:00
2020-09-26 13:11:52 +00:00
- 1 Core
2019-10-28 12:55:18 +00:00
- 1-2GB RAM
- Swap enabled for the container
2018-01-09 07:31:15 +00:00
Minimum:
2020-09-04 06:42:12 +00:00
2020-09-26 13:11:52 +00:00
- 1 vCore
2018-01-09 07:31:15 +00:00
- 512MB RAM
2019-11-02 05:46:35 +00:00
**Note:** You'll need to deactivate some services like ClamAV to be able to run on a host with 512MB of RAM. Even with 1G RAM you may run into problems without swap, see [FAQ ](https://github.com/tomav/docker-mailserver/wiki/FAQ-and-Tips ).
2018-01-09 07:31:15 +00:00
2016-04-24 15:37:10 +00:00
## Usage
2015-03-31 15:28:13 +00:00
2020-09-04 06:42:12 +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
2020-09-05 14:19:12 +00:00
``` BASH
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
curl -o .env https://raw.githubusercontent.com/tomav/docker-mailserver/master/.env.dist
2020-01-13 13:36:58 +00:00
2020-09-04 06:42:12 +00:00
curl -o env-mailserver https://raw.githubusercontent.com/tomav/docker-mailserver/master/env-mailserver.dist
```
2016-02-01 14:05:29 +00:00
2020-09-04 06:42:12 +00:00
### Create a docker-compose environment
2018-02-07 18:37:26 +00:00
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` ).
2020-09-26 13:11:52 +00:00
- [Install the latest docker-compose ](https://docs.docker.com/compose/install/ )
**Note:**: Variables in `.env` are expanded in the `docker-compose.yml` file **only** and **not** in the container. The file `env-mailserver` serves this case where environment variables are used in the container.
2018-02-07 18:37:26 +00:00
2020-01-18 10:42:23 +00:00
**Note:** If you want to use a bare domain (host name equals domain name) see [FAQ ](https://github.com/tomav/docker-mailserver/wiki/FAQ-and-Tips#can-i-use-nakedbare-domains-no-host-name ).
2020-09-24 12:54:21 +00:00
### Get up and running
2018-10-14 19:41:52 +00:00
2020-09-04 06:42:12 +00:00
``` BASH
docker-compose up -d mail
./setup.sh email add < user @ domain > [< password > ]
./setup.sh config dkim
```
2018-02-07 18:37:26 +00:00
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.
2020-09-04 06:42:12 +00:00
### Miscellaneous
2019-07-24 12:06:31 +00:00
#### Restart and update the container
2018-02-07 18:37:26 +00:00
2020-09-04 06:42:12 +00:00
``` BASH
docker-compose down
docker pull tvial/docker-mailserver:latest
docker-compose up -d mail
```
2018-02-07 18:37:26 +00:00
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-18 12:12:39 +00:00
#### Exposed ports
2020-04-27 06:23:32 +00:00
2020-09-04 06:42:12 +00:00
| Protocol | Opt-in Encryption ¹ | Enforced Encryption | Purpose |
| :------: | :----------------------: | :-----------------: | :------------: |
| SMTP | 25 | N/A | Transfer² |
| ESMTP | 587 | 465³ | Submission |
| POP3 | 110 | 995 | Retrieval |
| IMAP4 | 143 | 993 | Retrieval |
2020-04-27 06:23:32 +00:00
1. A connection *may* be secured over TLS when both ends support `STARTTLS` . On ports 110, 143 and 587, `docker-mailserver` will reject a connection that cannot be secured. Port 25 is [required ](https://serverfault.com/questions/623692/is-it-still-wrong-to-require-starttls-on-incoming-smtp-messages ) to support insecure connections.
2. Receives email and filters for spam and viruses. For submitting outgoing mail you should prefer the submission ports(465, 587), which require authentication. Unless a relay host is configured, outgoing email will leave the server via port 25(thus outbound traffic must not be blocked by your provider or firewall).
3. A submission port since 2018, [RFC 8314 ](https://tools.ietf.org/html/rfc8314 ). Originally a secure variant of port 25.
See the [wiki ](https://github.com/tomav/docker-mailserver/wiki ) for further details and best practice advice, especially regarding security concerns.
2018-02-18 12:12:39 +00:00
2020-09-09 15:19:48 +00:00
## Examples
2020-09-04 06:42:12 +00:00
2020-09-09 15:19:48 +00:00
### With Relevant Environmental Variables
2018-02-07 18:37:26 +00:00
2020-09-09 15:19:48 +00:00
``` YAML
version: '3.8'
2016-09-07 17:39:27 +00:00
services:
mail:
2017-04-27 16:01:26 +00:00
image: tvial/docker-mailserver:latest
2020-09-26 13:11:52 +00:00
hostname: mail # ${HOSTNAME}
domainname: domain.com # ${DOMAINNAME}
container_name: mail # ${CONTAINER_NAME}
2016-09-07 17:39:27 +00:00
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
2020-05-02 17:10:36 +00:00
- SPAMASSASSIN_SPAM_TO_INBOX=1
2019-05-05 18:22:51 +00:00
- 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
2020-09-21 11:54:31 +00:00
restart: always
2016-09-07 17:39:27 +00:00
volumes:
maildata:
2016-12-25 21:54:37 +00:00
mailstate:
2019-09-15 13:40:05 +00:00
maillogs:
2016-09-07 17:39:27 +00:00
```
2016-02-01 14:05:29 +00:00
2020-09-04 06:42:12 +00:00
#### LDAP setup
2017-07-03 11:16:16 +00:00
2020-09-04 06:42:12 +00:00
``` YAML
2020-09-09 15:19:48 +00:00
version: '3.8'
2017-07-03 11:16:16 +00:00
services:
mail:
image: tvial/docker-mailserver:latest
2020-09-26 13:11:52 +00:00
hostname: mail # ${HOSTNAME}
domainname: domain.com # ${DOMAINNAME}
container_name: mail # ${CONTAINER_NAME}
2017-07-03 11:16:16 +00:00
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
2020-05-02 17:10:36 +00:00
- SPAMASSASSIN_SPAM_TO_INBOX=1
2017-07-03 11:16:16 +00:00
- 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
2020-07-23 05:14:54 +00:00
- SASLAUTHD_LDAP_FILTER=(& (objectClass=PostfixBookMailAccount)(uniqueIdentifier=%U))
2017-07-03 11:16:16 +00:00
- 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
2020-09-21 11:54:31 +00:00
restart: always
2017-07-03 11:16:16 +00:00
volumes:
maildata:
mailstate:
2019-09-15 13:40:05 +00:00
maillogs:
2017-07-03 11:16:16 +00:00
```
2020-09-04 06:42:12 +00:00
## Environment variables
2016-04-07 12:20:51 +00:00
2020-09-21 11:54:31 +00:00
If an option doesn't work as documented here, check if you are running the latest image! Values in **bold** are the default values.
2020-09-04 06:42:12 +00:00
### Assignments
#### 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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
``` BASH
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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
- **empty** => SSL disabled
- letsencrypt => Enables Let's Encrypt certificates
- custom => Enables custom certificates
- 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
2020-09-04 06:42:12 +00:00
- **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-02-22 07:36:12 +00:00
2018-03-07 18:33:43 +00:00
##### SPOOF_PROTECTION
2020-09-04 06:42:12 +00:00
2018-03-07 18:33:43 +00:00
Configures the handling of creating mails with forged sender addresses.
2020-09-04 06:42:12 +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)
- 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-07 18:33:43 +00:00
2018-03-18 19:15:06 +00:00
##### ENABLE_SRS
2020-09-04 06:42:12 +00:00
2018-03-18 19:15:06 +00:00
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.
2020-09-04 06:42:12 +00:00
- **0** => Disabled
- 1 => Enabled
2018-03-18 19:15:06 +00:00
2018-02-07 18:37:26 +00:00
##### PERMIT_DOCKER
2020-03-01 18:40:50 +00:00
Set different options for mynetworks option (can be overwrite in postfix-main.cf) **WARNING** : Adding the docker network's gateway to the list of trusted hosts, e.g. using the `network` or `connected-networks` option, can create an [**open relay** ](https://en.wikipedia.org/wiki/Open_mail_relay ), [for instance ](https://github.com/tomav/docker-mailserver/issues/1405#issuecomment-590106498 ) if IPv6 is enabled on the host machine but not in Docker.
2020-09-04 06:42:12 +00:00
- **empty** => localhost only
- host => Add docker host (ipv4 only)
- 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
2020-03-19 08:35:25 +00:00
Note: you probably want to [set `POSTFIX_INET_PROTOCOLS=ipv4` ](#postfix_inet_protocols ) to make it work fine with Docker.
2020-09-26 13:11:52 +00:00
##### NETWORK_INTERFACE
In case your network interface differs from `eth0` , e.g. when you are using HostNetworking in Kubernetes, you can set this to whatever interface you want. This interface will then be used.
- **empty** => `eth0`
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
2020-09-04 06:42:12 +00:00
- **empty** => 7 days
2018-02-07 18:37:26 +00:00
##### 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)
2020-09-04 06:42:12 +00:00
- `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 /> )
2018-02-07 18:37:26 +00:00
- `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)
2020-05-01 21:42:21 +00:00
##### ENABLE_QUOTAS
- **1** => Dovecot quota is enabled
- 0 => Dovecot quota is disabled
See [mailbox quota ](https://github.com/tomav/docker-mailserver/wiki/Configure-Accounts#mailbox-quota ).
2018-10-15 19:17:45 +00:00
##### 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
2020-09-04 06:42:12 +00:00
- **empty** => Managesieve service disabled
- 1 => Enables Managesieve on port 4190
2018-02-07 18:37:26 +00:00
##### OVERRIDE_HOSTNAME
2020-09-04 06:42:12 +00:00
- **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.
2018-02-07 18:37:26 +00:00
##### POSTMASTER_ADDRESS
2020-09-04 06:42:12 +00:00
- **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
2020-09-04 06:42:12 +00:00
- **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
2019-10-17 13:26:44 +00:00
##### DOVECOT_MAILBOX_FORMAT
2020-09-04 06:42:12 +00:00
- **maildir** => uses very common Maildir format, one file contains one message
- sdbox => (experimental) uses Dovecot high-performance mailbox format, one file contains one message
- mdbox ==> (experimental) uses Dovecot high-performance mailbox format, multiple messages per file and multiple files per box
2019-10-17 13:26:44 +00:00
This option has been added in November 2019. Using other format than Maildir is considered as experimental in docker-mailserver and should only be used for testing purpose. For more details, please refer to [Dovecot Documentation ](https://wiki2.dovecot.org/MailboxFormat ).
2018-05-01 17:57:31 +00:00
2020-03-19 08:35:25 +00:00
##### POSTFIX_INET_PROTOCOLS
- **all** => All possible protocols.
- ipv4 => Use only IPv4 traffic. Most likely you want this behind Docker.
- ipv6 => Use only IPv6 traffic.
2020-09-04 06:42:12 +00:00
Note: More details in < http: / / www . postfix . org / postconf . 5 . html # inet_protocols >
2020-03-19 08:35:25 +00:00
2020-09-04 06:42:12 +00:00
#### Reports
2019-09-15 13:40:05 +00:00
##### PFLOGSUMM_TRIGGER
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
Recipient address for pflogsumm reports.
- **not set** => Use REPORT_RECIPIENT or POSTMASTER_ADDRESS
- => Specify the recipient address(es)
2019-09-15 13:40:05 +00:00
##### PFLOGSUMM_SENDER
2020-09-04 06:42:12 +00:00
From address for pflogsumm reports.
- **not set** => Use REPORT_SENDER or POSTMASTER_ADDRESS
- => Specify the sender address
2019-09-15 13:40:05 +00:00
##### LOGWATCH_INTERVAL
2020-09-04 06:42:12 +00:00
Interval for logwatch report.
- **none** => No report is generated
- daily => Send a daily report
- weekly => Send a report every week
2019-09-15 13:40:05 +00:00
##### LOGWATCH_RECIPIENT
2020-09-04 06:42:12 +00:00
Recipient address for logwatch reports if they are enabled.
- **not set** => Use REPORT_RECIPIENT or POSTMASTER_ADDRESS
- => Specify the recipient address(es)
2019-09-15 13:40:05 +00:00
##### REPORT_RECIPIENT (deprecated)
2018-03-18 18:52:28 +00:00
2020-09-04 06:42:12 +00:00
Enables a report being sent (created by pflogsumm) on a regular basis.
- **0** => Report emails are disabled unless enabled by other options
- 1 => Using POSTMASTER_ADDRESS as the recipient
- => Specify the recipient address
2018-03-18 18:52:28 +00:00
2019-09-15 13:40:05 +00:00
##### REPORT_SENDER (deprecated)
2018-05-01 17:57:31 +00:00
2020-09-04 06:42:12 +00:00
Change the sending address for mail report
- **empty** => mailserver-report@hostname
- => Specify the report sender (From) address
2018-05-01 17:57:31 +00:00
2019-09-15 13:40:05 +00:00
##### REPORT_INTERVAL (deprecated)
2018-05-01 17:57:31 +00:00
2020-09-04 06:42:12 +00:00
Changes the interval in which logs are rotated and a report is being sent (deprecated).
- **daily** => Send a daily report
- weekly => Send a report every week
- monthly => Send a report every month
2018-03-18 18:52:28 +00:00
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
2020-01-13 13:36:58 +00:00
the logs.
2019-09-15 13:40:05 +00:00
2020-01-13 13:36:58 +00:00
##### LOGROTATE_INTERVAL
2019-09-15 13:40:05 +00:00
2020-09-04 06:42:12 +00:00
Defines the interval in which the mail log is being rotated.
- **daily** => Rotate daily.
- weekly => Rotate weekly.
- monthly => Rotate monthly.
2019-09-15 13:40:05 +00:00
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
2020-09-04 06:42:12 +00:00
#### Spamassassin
2018-02-07 18:37:26 +00:00
##### ENABLE_SPAMASSASSIN
2016-12-25 21:54:37 +00:00
2020-09-04 06:42:12 +00:00
- **0** => Spamassassin is disabled
- 1 => Spamassassin is enabled
2020-05-02 17:10:36 +00:00
2020-09-04 06:42:12 +00:00
**/!\\ Spam delivery:** when Spamassassin is enabled, messages marked as spam WILL NOT BE DELIVERED.
2020-05-02 17:10:36 +00:00
Use `SPAMASSASSIN_SPAM_TO_INBOX=1` for receiving spam messages.
##### SPAMASSASSIN_SPAM_TO_INBOX
2020-09-04 06:42:12 +00:00
- **0** => Spam messages will be bounced (_rejected_) without any notification (_dangerous_).
- 1 => Spam messages will be delivered to the inbox and tagged as spam using `SA_SPAM_SUBJECT` .
2020-05-02 17:10:36 +00:00
##### MOVE_SPAM_TO_JUNK
2020-09-04 06:42:12 +00:00
- **1** => Spam messages will be delivered in the `Junk` folder.
- 0 => Spam messages will be delivered in the mailbox.
2020-05-02 17:10:36 +00:00
Note: this setting needs `SPAMASSASSIN_SPAM_TO_INBOX=1`
2016-12-25 21:54:37 +00:00
##### SA_TAG
2020-09-04 06:42:12 +00:00
- **2.0** => add spam info headers if at, or above that level
2016-12-25 21:54:37 +00:00
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1`
##### SA_TAG2
2020-09-04 06:42:12 +00:00
- **6.31** => add 'spam detected' headers at that level
2016-12-25 21:54:37 +00:00
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1`
##### SA_KILL
2020-09-04 06:42:12 +00:00
- **6.31** => triggers spam evasive actions
2016-12-25 21:54:37 +00:00
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
2020-09-04 06:42:12 +00:00
- **\*\*\*SPAM\*\*\*** => add tag to subject if spam detected
2017-06-23 19:50:01 +00:00
2020-05-31 20:06:31 +00:00
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1` . Add the spamassassin score to the subject line by inserting the keyword _SCORE_ : ** \*\*\*SPAM(_SCORE_)\*\*\***.
2017-06-23 19:50:01 +00:00
2019-01-29 14:48:42 +00:00
##### SA_SHORTCIRCUIT_BAYES_SPAM
2020-09-04 06:42:12 +00:00
- **1** => will activate spamassassin short circuiting for bayes spam detection.
2019-01-29 14:48:42 +00:00
2020-01-13 13:36:58 +00:00
This will uncomment the respective line in ```/etc/spamassasin/local.cf```
2019-01-29 14:48:42 +00:00
Note: activate this only if you are confident in your bayes database for identifying spam.
##### SA_SHORTCIRCUIT_BAYES_HAM
2020-09-04 06:42:12 +00:00
- **1** => will activate spamassassin short circuiting for bayes ham detection
2019-01-29 14:48:42 +00:00
2020-01-13 13:36:58 +00:00
This will uncomment the respective line in ```/etc/spamassasin/local.cf```
2019-01-29 14:48:42 +00:00
Note: activate this only if you are confident in your bayes database for identifying ham.
2020-09-04 06:42:12 +00:00
#### Fetchmail
2016-04-22 22:31:15 +00:00
2018-02-07 18:37:26 +00:00
##### ENABLE_FETCHMAIL
2020-09-04 06:42:12 +00:00
- **0** => `fetchmail` disabled
- 1 => `fetchmail` enabled
2016-08-21 20:13:13 +00:00
2017-10-05 06:25:29 +00:00
##### FETCHMAIL_POLL
2020-09-04 06:42:12 +00:00
- **300** => `fetchmail` The number of seconds for the interval
#### LDAP
2018-02-07 18:37:26 +00:00
2016-10-30 13:11:36 +00:00
##### ENABLE_LDAP
2020-09-04 06:42:12 +00:00
- **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 ))
- 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
2020-09-04 06:42:12 +00:00
- **empty** => no
- yes => LDAP over TLS enabled for Postfix
2018-01-25 21:38:41 +00:00
2016-10-30 13:11:36 +00:00
##### LDAP_SERVER_HOST
2020-09-04 06:42:12 +00:00
- **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
2016-10-30 13:11:36 +00:00
##### LDAP_SEARCH_BASE
2020-09-04 06:42:12 +00:00
- **empty** => ou=people,dc=domain,dc=com
- => e.g. LDAP_SEARCH_BASE=dc=mydomain,dc=local
2016-10-30 13:11:36 +00:00
##### LDAP_BIND_DN
2020-09-04 06:42:12 +00:00
- **empty** => cn=admin,dc=domain,dc=com
- => take a look at examples of SASL_LDAP_BIND_DN
2016-10-30 13:11:36 +00:00
##### LDAP_BIND_PW
2020-09-04 06:42:12 +00:00
- **empty** => admin
- => Specify the password to bind against ldap
2016-10-30 13:11:36 +00:00
2017-07-03 11:16:16 +00:00
##### LDAP_QUERY_FILTER_USER
2020-09-04 06:42:12 +00:00
- e.g. `(&(mail=%s)(mailEnabled=TRUE))`
- => Specify how ldap should be asked for users
2017-07-03 11:16:16 +00:00
##### LDAP_QUERY_FILTER_GROUP
2020-09-04 06:42:12 +00:00
- e.g. `(&(mailGroupMember=%s)(mailEnabled=TRUE))`
- => Specify how ldap should be asked for groups
2017-07-03 11:16:16 +00:00
##### LDAP_QUERY_FILTER_ALIAS
2020-09-04 06:42:12 +00:00
- e.g. `(&(mailAlias=%s)(mailEnabled=TRUE))`
- => 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
2020-09-04 06:42:12 +00:00
- **empty** => no
- yes => LDAP over TLS enabled for Dovecot
2018-01-25 21:38:41 +00:00
2020-09-04 06:42:12 +00:00
#### Dovecot
2018-02-07 18:37:26 +00:00
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
2020-09-04 06:42:12 +00:00
- e.g. `(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))`
2019-01-20 10:15:26 +00:00
2019-08-21 10:53:53 +00:00
##### DOVECOT_USER_ATTRS
2019-01-20 10:15:26 +00:00
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
- e.g. `(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))`
2019-01-20 10:15:26 +00:00
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
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
- **0** => `postgrey` is disabled
- 1 => `postgrey` is enabled
2017-02-06 09:21:18 +00:00
##### POSTGREY_DELAY
2020-09-04 06:42:12 +00:00
- **300** => greylist for N seconds
2017-02-06 09:21:18 +00:00
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
##### POSTGREY_MAX_AGE
2017-07-03 11:16:16 +00:00
2020-09-04 06:42:12 +00:00
- **35** => delete entries older than N days since the last time that they have been seen
2017-02-06 09:21:18 +00:00
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
2018-11-01 18:32:36 +00:00
##### POSTGREY_AUTO_WHITELIST_CLIENTS
2020-09-04 06:42:12 +00:00
- **5** => whitelist host after N successful deliveries (N=0 to disable whitelisting)
2018-11-01 18:32:36 +00:00
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
2020-09-04 06:42:12 +00:00
- **Delayed by postgrey** => response when a mail is greylisted
2017-02-06 09:21:18 +00:00
Note: This postgrey setting needs `ENABLE_POSTGREY=1`
2020-09-04 06:42:12 +00:00
#### SASL Auth
2018-02-07 18:37:26 +00:00
2016-10-30 13:11:36 +00:00
##### ENABLE_SASLAUTHD
2020-09-04 06:42:12 +00:00
- **0** => `saslauthd` is disabled
- 1 => `saslauthd` is enabled
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_MECHANISMS
2020-09-04 06:42:12 +00:00
- empty => pam
- `ldap` => authenticate against ldap server
- `shadow` => authenticate against local user db
- `mysql` => authenticate against mysql db
- `rimap` => authenticate against imap server
- NOTE: can be a list of mechanisms like pam ldap shadow
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_MECH_OPTIONS
2020-09-04 06:42:12 +00:00
- empty => None
- e.g. with SASLAUTHD_MECHANISMS rimap you need to specify the ip-address/servername of the imap server ==> xxx.xxx.xxx.xxx
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_LDAP_SERVER
2020-09-04 06:42:12 +00:00
- empty => localhost
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_LDAP_SSL
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
- empty => anonymous bind
- specify an object with privileges to search the directory tree
- 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
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_LDAP_PASSWORD
2020-09-04 06:42:12 +00:00
- empty => anonymous bind
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_LDAP_SEARCH_BASE
2020-09-04 06:42:12 +00:00
- empty => Reverting to SASLAUTHD_MECHANISMS pam
- specify the search base
2016-10-30 13:11:36 +00:00
##### SASLAUTHD_LDAP_FILTER
2020-09-04 06:42:12 +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
2020-09-04 06:42:12 +00:00
- **empty** => No sasl_passwd will be created
- string => `/etc/postfix/sasl_passwd` will be created with the string as password
2016-04-22 22:31:15 +00:00
2020-09-04 06:42:12 +00:00
#### SRS (Sender Rewriting Scheme)
2018-02-18 19:53:13 +00:00
2019-12-03 13:33:51 +00:00
##### SRS_SENDER_CLASSES
An email has an "envelope" sender (indicating the sending server) and a
"header" sender (indicating who sent it). More strict SPF policies may require
you to replace both instead of just the envelope sender.
[More info ](https://www.mybluelinux.com/what-is-email-envelope-and-email-header/ ).
2020-09-04 06:42:12 +00:00
- **envelope_sender** => Rewrite only envelope sender address
- header_sender => Rewrite only header sender (not recommended)
- envelope_sender,header_sender => Rewrite both senders
2019-12-03 13:33:51 +00:00
2018-02-18 19:53:13 +00:00
##### SRS_EXCLUDE_DOMAINS
2020-09-04 06:42:12 +00:00
- **empty** => Envelope sender will be rewritten for all domains
- provide comma separated list of domains to exclude from rewriting
2018-03-08 21:51:10 +00:00
##### SRS_SECRET
2020-09-04 06:42:12 +00:00
- **empty** => generated when the container is started for the first time
- provide a secret to use in base64
- 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
2020-09-04 06:42:12 +00:00
- **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
2018-06-19 06:17:32 +00:00
2020-09-04 06:42:12 +00:00
#### Default Relay Host
2019-01-19 10:10:31 +00:00
2020-09-05 14:19:12 +00:00
##### DEFAULT_RELAY_HOST
2019-01-19 10:10:31 +00:00
2020-09-04 06:42:12 +00:00
- **empty** => don't set default relayhost setting in main.cf
- default host and port to relay all mail through.
2019-12-03 13:52:26 +00:00
Format: `[example.com]:587` (don't forget the brackets if you need this to
be compatible with `$RELAY_USER` and `$RELAY_PASSWORD` , explained below).
2019-01-19 10:10:31 +00:00
2020-09-04 06:42:12 +00:00
#### Multi-domain Relay Hosts
2018-04-02 08:45:58 +00:00
2020-09-05 14:19:12 +00:00
##### RELAY_HOST
2018-04-02 08:45:58 +00:00
2020-09-04 06:42:12 +00:00
- **empty** => don't configure relay host
- default host to relay mail through
2018-04-02 08:45:58 +00:00
2020-09-05 14:19:12 +00:00
##### RELAY_PORT
2018-04-02 08:45:58 +00:00
2020-09-04 06:42:12 +00:00
- **empty** => 25
- default port to relay mail through
2018-04-02 08:45:58 +00:00
2020-09-05 14:19:12 +00:00
##### RELAY_USER
2018-04-02 08:45:58 +00:00
2020-09-04 06:42:12 +00:00
- **empty** => no default
- default relay username (if no specific entry exists in postfix-sasl-password.cf)
2018-04-02 08:45:58 +00:00
2020-09-05 14:19:12 +00:00
##### RELAY_PASSWORD
2018-04-02 08:45:58 +00:00
2020-09-04 06:42:12 +00:00
- **empty** => no default
- password for default relay user