chore: disable F2B postfix-sasl jail (#4535)
Some checks failed
Build, Test & Deploy / Build AMD64 Image (push) Has been cancelled
Documentation / Deploy Docs (push) Has been cancelled
Lint / lint (push) Has been cancelled
Build, Test & Deploy / Test AMD64 Image (push) Has been cancelled
Build, Test & Deploy / Publish AMD64 and ARM64 Image (push) Has been cancelled
Documentation / Update `versions.json` if necessary (push) Has been cancelled
Documentation / update `latest` symlink if neccessary (push) Has been cancelled

Signed-off-by: Georg Lauterbach <44545919+georglauterbach@users.noreply.github.com>
This commit is contained in:
Georg Lauterbach 2025-08-03 10:37:41 +02:00 committed by GitHub
parent b6e5d34cd4
commit e448b5e53e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 22 additions and 20 deletions

View file

@ -78,6 +78,15 @@ This following configuration files inside the `docker-data/dms/config/` volume w
[github-file-f2bjail]: https://github.com/docker-mailserver/docker-mailserver/blob/master/config-examples/fail2ban-jail.cf
[github-file-f2bconfig]: https://github.com/docker-mailserver/docker-mailserver/blob/master/config-examples/fail2ban-fail2ban.cf
### SASL
The `postfix` jail comes with `mode=extra` by default, which covers SASL login errors for our default SASL provider. Hence, the `postfix-sasl` jail has been disabled. If you switch to another SASL provider (e.g., SASLauthd), you may want to turn the `postfix-sasl` jail back on:
```ini title="docker-data/dms/config/fail2ban-jail.cf"
[postfix-sasl]
enabled = true
```
### Viewing All Bans
When just running