I have a couple of other docker-compose based services running on the same host as mailcow and occasionally it happens that another service already has created a subnet on 172.22.1 and then mailcow fails to start. I would like to specify another subnet that is outside of the range of 172.1.1 - 172.50.1.
I have tried to set
mailcow.conf and run
./update.sh however this resulted in the mail server not reachable and/or emails not being received.
I assume it is related to https://community.mailcow.email/d/85-cant-send-or-receive-email though I am not sure.
a) What is a valid network here?
b) Is updating
mailcow.conf and running
./update.sh the proper way to switch the network?
Thanks + best regards!