- Clarify host vs container paths in documentation
- Use loop for creating extra plugin files to reduce duplication
- Update example to show IMAP-specific plugin addition
Co-authored-by: DerLinkman <62480600+DerLinkman@users.noreply.github.com>
- Added documentation for using extra.conf with protocol blocks
- Clarified the recommended approach (extra files)
- Explained advantages and considerations of each method
Co-authored-by: DerLinkman <62480600+DerLinkman@users.noreply.github.com>
- Modified docker-entrypoint.sh to create empty mail_plugins_extra files
- Updated dovecot.conf to read from additional plugin files
- Added documentation on how to extend mail_plugins
Co-authored-by: DerLinkman <62480600+DerLinkman@users.noreply.github.com>
[Netfilter] add mailcow rule to docker-user chain
[Netfilter] add mailcow isolation rule to MAILCOW chain
[Netfilter] add mailcow isolation rule to MAILCOW chain
[Netfilter] set mailcow isolation rule before redis
[Netfilter] clear bans in redis after connecting
[Netfilter] simplify mailcow isolation rule for compatibility with iptables-nft
[Netfilter] stop container after mariadb, redis, dovecot, solr
[Netfilter] simplify mailcow isolation rule for compatibility with iptables-nft
[Netfilter] add exception for mailcow isolation rule for HA setups
[Netfilter] add exception for mailcow isolation rule for HA setups
[Netfilter] add DISABLE_NETFILTER_ISOLATION_RULE
[Netfilter] fix wrong var name
[Netfilter] add DISABLE_NETFILTER_ISOLATION_RULE to update and generate_config sh
When migrating from other Dovecot based installations it can be very
convenient to just copy over existing hashed passwords.
However, mailcow currently only supports a limited number of password
schemes.
This commit implements all password schemes that do not require
challenge/response or OTP mechanisms.
A convenient way to generate the regex with all supported schemas is
`docker-compose exec dovecot-mailcow doveadm pw -l | awk -F' ' '{printf
"/^{("; for(i=1;i<=NF-1;i++){printf "%s%s", sep, $i; sep="|"}; printf
")}/i\n"}'`
Note that this will also include unsupported challenge/response and OTP
schemas.
Furthermore this increases the vsz_limit for the dovecot auth service to
2G for the use of ARGON2I and ARGON2ID schemas.
Signed-off-by: Felix Kaechele <felix@kaechele.ca>
