Introduce CLAMAV_MESSAGE_SIZE_LIMIT env (#2453)

This commit is contained in:
Casper 2022-03-03 16:17:01 +01:00 committed by GitHub
parent 1911f9a4b4
commit b9fdb1e7b5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
9 changed files with 57 additions and 30 deletions

View file

@ -75,8 +75,8 @@ Note: Emails will be rejected, if they don't pass the block list checks!
##### ENABLE_CLAMAV
- **0** => Clamav is disabled
- 1 => Clamav is enabled
- **0** => ClamAV is disabled
- 1 => ClamAV is enabled
##### ENABLE_POP3
@ -192,6 +192,13 @@ Set the message size limit for all users. If set to zero, the size will be unlim
- **empty** => 10240000 (~10 MB)
##### CLAMAV_MESSAGE_SIZE_LIMIT
Mails larger than this limit won't be scanned.
ClamAV must be enabled (ENABLE_CLAMAV=1) for this.
- **empty** => 25M (25 MB)
##### ENABLE_MANAGESIEVE
- **empty** => Managesieve service disabled
@ -319,9 +326,9 @@ Changes the interval in which a report is being sent.
!!! note
`LOGROTATE_INTERVAL` only manages `logrotate` within the container for services we manage internally.
The entire log output for the container is still available via `docker logs mailserver` (or your respective container name). If you want to configure external log rotation for that container output as well, : [Docker Logging Drivers](https://docs.docker.com/config/containers/logging/configure/).
By default, the logs are lost when the container is destroyed (eg: re-creating via `docker-compose down && docker-compose up -d`). To keep the logs, mount a volume (to `/var/log/mail/`).
!!! note