There does not need to be such a file and the variables are read just fine in a default installation.
Yes, I think so, that’s was why I posted this discussion, in case there’s a bug in the update process.
If you change things in mailcow, expect errors to happen. We cannot support that.
The change was a workaround to be able to connect to the admin UI. I’m planning to migrate mailcow to a fresh server, because I think that something broke mailcow.
And yes, it works absolutly fine in mailcow. Don’t you think someone would have noticed if the variables were ignored?
Of course I know that this should work. Anyway, I don’t see the point of your question. I wrote this post because I had some problem, and after investigating some time, I wasn’t able to fix it. Do you think I was bored at home and decided to write this post to spend some spare time?
As I told previously, I’m going to migrate mailcow to a new server, because I’m also having another issue, and I think that something else (firewalld? ) broke my system.
Thanks for your attention and your time.