Contribution guidelines
Checklist prior issue creation
Description
I'm running my mailcow UI at a different port. Therefore I've changed HTTPS_PORT in mailcow.conf. The connection for https://mta-sts.example.com/.well-known/mta-sts.txt on port 443 got refused. I switched the port to 443 for testing purposes and it worked as expected.
Unfortunately the error wasnโt fixed with #6739.
In my opinion mailcow should always serve the mta-sts at https://mta-sts.example.com/.well-known/mta-sts.txt at Port 443 if enabled. Connections to the mailcow domain for the Ul should only be served at the HTTPS_PORT (actual behavior).
Steps to reproduce:
- Setup MTA-STS in mailcow
- change HTTPS_PORT to something other than 443
- Connection for mta-sts.example.com is refused
- change HTTPS_PORT back to 443
- MTA-STS is working as expected
Logs:
Which branch are you using?
master (stable)
Which architecture are you using?
x86_64
Operating System:
Debian 13
Server/VM specifications:
4GB 4 Core
Is Apparmor, SELinux or similar active?
No
Virtualization technology:
KVM
Docker version:
docker-compose version or docker compose version:
mailcow version:
2025-12a
Reverse proxy:
Buildin mailcow Proxy
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
Contribution guidelines
Checklist prior issue creation
Description
I'm running my mailcow UI at a different port. Therefore I've changed HTTPS_PORT in mailcow.conf. The connection for https://mta-sts.example.com/.well-known/mta-sts.txt on port 443 got refused. I switched the port to 443 for testing purposes and it worked as expected.
Unfortunately the error wasnโt fixed with #6739.
In my opinion mailcow should always serve the mta-sts at https://mta-sts.example.com/.well-known/mta-sts.txt at Port 443 if enabled. Connections to the mailcow domain for the Ul should only be served at the HTTPS_PORT (actual behavior).
Steps to reproduce:
Logs:
Which branch are you using?
master (stable)
Which architecture are you using?
x86_64
Operating System:
Debian 13
Server/VM specifications:
4GB 4 Core
Is Apparmor, SELinux or similar active?
No
Virtualization technology:
KVM
Docker version:
docker-compose version or docker compose version:
mailcow version:
2025-12a
Reverse proxy:
Buildin mailcow Proxy
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: