how to update docker-compose.yml

FriendlyUser

Hi all,

I figured out, that my docker-compose.yml does not correspond to the mailcow/mailcow-dockerizedblob/master/docker-compose.yml

is my docker-compose.yml supposed to be automatically updated or
do I have to manually update the file
should I not touch the docker-compose.yml file in any case?
Is there a problem, because I touched it (disabled ipv6 at some point in the past) ?
Is there a documentation for my case?

Thanks for your help.

D4niel

FriendlyUser is my docker-compose.yml supposed to be automatically updated

Yes

FriendlyUser do I have to manually update the file

FriendlyUser should I not touch the docker-compose.yml file in any case?

Usually you don’t need to modify it at all. Most settings can be changed in config files or through a docker-compose override file. Some examples are in the docs.

FriendlyUser Is there a problem, because I touched it (disabled ipv6 at some point in the past) ?

Not necessarily. If there is an update the changes usually get merged. This should be verified however.

FriendlyUser Is there a documentation for my case?

https://docs.mailcow.email/post_installation/firststeps-disable_ipv6/

FriendlyUser

Thank you @D4niel ,

I see clearer now. Just the ipv6nat-mailcow content was not merged.

Since I am seeing myself being an open relay, although I have disabled ipv6 as the docs say,
I need to investigate further.
In german, see the other Thread: https://community.mailcow.email/d/5013-massenhaft-bounces-durch-spam/6

But it seems to me at the moment:

As soon as I disable IPv6 as the docs say, the docker stack still creates docker-proxy with IPv6, forwarding/natting everything from IPv6 to the postfix, which identifies the request coming from 172.11.1.1 thus automatically accepting mails that are forged to be from my server. -> Open relay 👿