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

View file

@ -4,8 +4,8 @@ title: 'FAQ'
### What kind of database are you using?
None! No database is required. Filesystem is the database.
This image is based on config files that can be persisted using Docker volumes, and as such versioned, backed up and so forth.
None! No database is required. Filesystem is the database.
This image is based on config files that can be persisted using Docker volumes, and as such versioned, backed up and so forth.
### Where are emails stored?
@ -30,7 +30,7 @@ See [supervisorctl's documentation](http://supervisord.org/running.html#running-
### How can I sync container with host date/time? Timezone?
Share the host's [`/etc/localtime`](https://www.freedesktop.org/software/systemd/man/localtime.html) with the `docker-mailserver` container, using a Docker volume:
Share the host's [`/etc/localtime`](https://www.freedesktop.org/software/systemd/man/localtime.html) with the `docker-mailserver` container, using a Docker volume:
```yaml
volumes:
@ -322,13 +322,13 @@ If we're blind, we won't be able to do anything.
### What system requirements are required to run `docker-mailserver` effectively?
1 core and 1GB of RAM + swap partition is recommended to run `docker-mailserver` with clamav.
1 core and 1GB of RAM + swap partition is recommended to run `docker-mailserver` with ClamAV.
Otherwise, it could work with 512M of RAM.
!!! warning
Clamav can consume a lot of memory, as it reads the entire signature database into RAM.
ClamAV can consume a lot of memory, as it reads the entire signature database into RAM.
Current figure is about 850M and growing. If you get errors about clamav or amavis failing to allocate memory you need more RAM or more swap and of course docker must be allowed to use swap (not always the case). If you can't use swap at all you may need 3G RAM.
Current figure is about 850M and growing. If you get errors about ClamAV or amavis failing to allocate memory you need more RAM or more swap and of course docker must be allowed to use swap (not always the case). If you can't use swap at all you may need 3G RAM.
### Can `docker-mailserver` run in a Rancher Environment?