Miscellaneous first checks

• I checked that all ports are open and not blocked by my ISP / hosting provider.
• I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

Affected Component(s)

setup.sh fail2ban ignores IPv6 bans

What happened and when does this occur?

So I was troubleshooting connection issues and couldn’t for the life of me connect to either postfix or dovecot over IPv6. Meanwhile I could happily see someone else log in via v6.

I _had_ checked `setup.sh fail2ban` prior, and double checked again. It reported “No IPs have been banned” both times. `exec`ing a shell later, I could see & remove the ban using the regular `fail2ban` command inside the container.

What did you expect to happen?

I expected `setup.sh fail2ban` to list IPv6 bans in addition to IPv4 bans. I also expected a `setup.sh fail2ban unban <IPv6 address>` that I tried anyway to work.

How do we replicate the issue?

1. Enable fail2ban.
2. Get your local IPv6 address banned by e.g. using the wrong password enough times.
3. Observe connection issues.
4. Run `setup.sh fail2ban`.
5. Observe “No IPs have been banned”.
6. Look at fail2bans actual database.
7. Observe your local IPv6 address having been banned.

DMS version

11.1.0

What operating system is DMS running on?

Linux

What instruction set architecture is DMS running on?

x86_64 / AMD64

What container orchestration tool are you using?

Podman (not officially supported)

docker-compose.yml

No response

Relevant log output

No response

Other relevant information

No response

What level of experience do you have with Docker and mail servers?

• I am inexperienced with docker
• I am inexperienced with mail servers
• I am uncomfortable with the CLI

Code of conduct

• I have read this project's Code of Conduct and I agree
• I have read the README and the documentation and I searched the issue tracker but could not find a solution

Improvements to this form?

No response