Open missytake opened 1 year ago
OTOH it closely ties mailadm to mailcow, and if we want to add different mail server backends in the future (e.g. mail-in-a-box) it could complicate that. So let's consider for a while before going down that path :)
We definitely want to support a simpler non-mailcow setup in the future. This does not prevent having a support for mailcow docker-compose integration, but this should not be the only option.
We don't have any other setup than mailcow at the moment, but I would say we should continue supporting setups where mailadm is running on a separate machine without docker at all.
We could simplify mailadm + mailcow setup and pin the mailcow version by making mailcow a mailadm submodule. This would best be combined by adding mailadm to mailcow's docker-compose setup by providing a docker-compose.override.yml, @brabo got that working already.
It's a bigger effort that would require changing installation documents both at https://mailadm.readthedocs.io/en/latest/ and delta.chat/serverguide, but will make the setup be a lot better integrated and simplified :)
OTOH it closely ties mailadm to mailcow, and if we want to add different mail server backends in the future (e.g. mail-in-a-box) it could complicate that. So let's consider for a while before going down that path :)