- Edited
- Best Answerset by scolastico
esackbauer Since I had planned to move mailcow to its own vm soon anyway, I have now done so. The previous system had grown historically and the plan is currently to move all services from there to new vms. After the move and a little bit of debugging because I still had 10.10.10.2 from the old vm in a config at one point, everything went wonderfully. So I think it was some kind of problem with the double ip setup. However, it’s strange because the duplicate ip has already existed for 2 years, and has only changed from 192.168.3.2 and 192.168.3.3 to 10.10.10.2 and 10.10.10.250. And the previous setup also worked with it without any problems.

