Still in hope in receiving an complete answer here.
I am running a debian 8 server with several services and pulled the most recent mailcow-dockerized. During the setup I encountered the following errors:
ERROR: for postfix-mailcow Cannot start service postfix-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_postfix-mailcow_1: Error starting userland proxy: listen tcp 0.0.0.0:25: bind: address already in use
ERROR: for nginx-mailcow Cannot start service nginx-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_nginx-mailcow_1: Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
Obviously exim4 is installed on the server blocking port 25. Easy to fix if I simply remove it (but what to use for internal mails then?)
For 443 nginx is installed on my server which I need as the reverse proxy for my services... What should I do now? I was hoping I could use the dockerized mailcow without having to mess with my existing system.
These are the answers received via ticket system. Wasn't able to get it working
For Postfix you can either open mailcow-postfix to accept your "internal" mails or use exim4 to relay the mails via mailcow. I use a normal postfix installation on my hostsystem without port binding (comment smtp in master.cf) and forward the mails to mailcow.
For Nginx, just dont use the mailcow nginx container and configure your nginx to directly use the fpm container.
I simply don't know what I have to change in master.cf ...
In mailcow.conf change HTTPS_PORT=443 to HTTPS_PORT=127.0.0.1:4443 and now setup proxy in "natvie" nginx. Mailcow listen now on localhost:4443.
I think I have to remove the nginx part from the docker-compose.yml else I would receive the same error for the nginx container, because it's trying to bind 443 ... Am I right? But it is somehow needed for the network I guess.
I am looking forward to hearing from you.