2016-06-25 08:57:46 +00:00
# docker-mailserver
2017-07-30 18:07:32 +00:00
[](https://travis-ci.org/tomav/docker-mailserver) [](https://hub.docker.com/r/tvial/docker-mailserver/) [](https://microbadger.com/images/tvial/docker-mailserver) [](https://github.com/tomav/docker-mailserver/) [](https://github.com/tomav/docker-mailserver/) [](https://github.com/tomav/docker-mailserver/) [](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
2016-10-30 13:11:36 +00:00
- postfix with smtp or ldap auth
- dovecot for sasl, imap (and optional pop3) with ssl support, with ldap auth
- saslauthd with ldap auth
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
- [amavis ](https://www.amavis.org/ )
- [spamassasin ](http://spamassassin.apache.org/ ) supporting custom rules
- [clamav ](https://www.clamav.net/ ) with automatic updates
2016-01-20 15:41:34 +00:00
- opendkim
2016-04-21 13:28:23 +00:00
- opendmarc
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
- [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/ )
2016-04-29 15:52:22 +00:00
- 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
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
- [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!)
2016-04-21 13:28:23 +00:00
- [integration tests ](https://travis-ci.org/tomav/docker-mailserver )
2016-02-01 14:05:29 +00:00
- [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:
curl -o setup.sh https://raw.githubusercontent.com/tomav/docker-mailserver/master/setup.sh; chmod a+x ./setup.sh
curl -o docker-compose.yml https://raw.githubusercontent.com/tomav/docker-mailserver/master/docker-compose.yml.dist
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
- Edit the `.env` to your liking. Adapt this file with your FQDN.
- Install [docker-compose ](https://docs.docker.com/compose/ ) in the version `1.6` or higher.
#### Create your mail accounts
./setup.sh email add < email > [< password > ]
#### 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.
#### Start the container
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
#### 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:
2016-12-25 21:54:37 +00:00
- "25:25"
- "143:143"
- "587:587"
- "993:993"
2016-04-24 15:37:10 +00:00
volumes:
2016-12-25 21:54:37 +00:00
- maildata:/var/mail
- mailstate:/var/mail-state
- ./config/:/tmp/docker-mailserver/
environment:
- ENABLE_SPAMASSASSIN=1
- ENABLE_CLAMAV=1
- ENABLE_FAIL2BAN=1
2017-02-06 09:21:18 +00:00
- ENABLE_POSTGREY=1
2016-12-25 21:54:37 +00:00
- ONE_DIR=1
- DMS_DEBUG=0
cap_add:
- NET_ADMIN
2017-10-10 06:15:18 +00:00
- 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
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
- ./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
- LDAP_QUERY_FILTER_USER="(& (mail=%s)(mailEnabled=TRUE))"
- LDAP_QUERY_FILTER_GROUP="(& (mailGroupMember=%s)(mailEnabled=TRUE))"
- LDAP_QUERY_FILTER_ALIAS="(& (mailAlias=%s)(mailEnabled=TRUE))"
- DOVECOT_PASS_FILTER="(& (objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))"
- DOVECOT_USER_FILTER="(& (objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))"
- 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
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
```
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.
##### 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
- manual => Let's you manually specify locations of your SSL certificates for non-standard cases
- self-signed => Enables self-signed certificates
Please read [the SSL page in the wiki ](https://github.com/tomav/docker-mailserver/wiki/Configure-SSL ) for more information.
##### PERMIT_DOCKER
Set different options for mynetworks option (can be overwrite in postfix-main.cf)
- **empty** => localhost only
- host => Add docker host (ipv4 only)
- network => Add all docker containers (ipv4 only)
##### 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.
##### 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
##### 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-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
Note: this spamassassin setting needs `ENABLE_SPAMASSASSIN=1`
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 ))
- For preparing the ldap server to use in combination with this continer [this ](http://acidx.net/wordpress/2014/06/installing-a-mailserver-with-postfix-dovecot-sasl-ldap-roundcube/ ) article may be helpful
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
- e.g. `"(&(mail=%s)(mailEnabled=TRUE))"`
- => Specify how ldap should be asked for users
##### LDAP_QUERY_FILTER_GROUP
- e.g. `"(&(mailGroupMember=%s)(mailEnabled=TRUE))"`
- => Specify how ldap should be asked for groups
##### LDAP_QUERY_FILTER_ALIAS
- e.g. `"(&(mailAlias=%s)(mailEnabled=TRUE))"`
- => Specify how ldap should be asked for aliases
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
2017-07-03 11:16:16 +00:00
##### DOVECOT_USER_FILTER
- e.g. `"(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))"`
##### DOVECOT_PASS_FILTER
- e.g. `"(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))"`
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`
##### 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
- specify an object with priviliges 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
##### 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
- provide comma seperated list of domains to exclude from rewriting
