Mailcow Clustering

[deleted]

Hi there,

I recently started using Mailcow for both my email my clients’ email, and was wondering whether anybody had any advice with regards to making this setup redundant?

I’m assuming that Mailcow doesn’t have this functionality built-in, so would my only option be to make a contribution to Mailcow to add this functioanlity, or do some magic with Postfix / Dovecot on a separate node?

Has anybody managed to do this?

Thanks,

diekuh

We will publicate docs for that soon and sell support for it.

They will be releasd under the premise that we will not provide support for these setups in the community. 🙂

markus

diekuh Any news on this? Would really be nice to hear how far you came in the last months 🙂

annedouwe_mox

diekuh, I’m also interested in the progress of this. Can you share an update?

[deleted]

Perfect! Thanks for the update.

Very much looking forward to seeing what you come up with!

diekuh

We just need to rework it a bit and translate the text. :o Are you german?

[deleted]

diekuh Sorry for the delayed response!
Unfortunately I’m not German, but this is sounding great.

If I can help with anything, let me know!

Knubbl

I’m also interested in this topic, how the solution would look like 🙂
@diekuh I’m speaking German.

diekuh

I will probably release a doc for it in the next few days/weeks.

We decided to create new support packages for clustered setups, too. That will be the only way to get support for these kind of setups. The community is open for discussion of course, but we will not provide any kind of support here. I hope you understand.

[deleted]

Hi diekuh,

Do you have an ETA for this (i.e. an approximate due date)? We are wanting to move to a clustered mail setup ASAP (as we are coming to the end of the contract with our current MX provider), and would love to know when we can expect to be able to implement this. I know you’ve said a “couple days/weeks”, but it’d be great to know whether we are talking ‘a couple of days’ or ‘several weeks’. 😃

Also, could you give a little more info on these support packages, please? I presume these would just be for Mailcow-provided assistance with any problems on an instance, rather than putting clustering behind a paywall (as is done with some other platforms, like Axigen)?

Thanks in advance for all your hard work on putting this (and the entire solution) together! It’s truly amazing…

diekuh

Thanks. 🙂

We offer them currently hosted in Willich and FFM (active/active).

Docs are not available at the moment.

I don’t have any more information as of today. A “paywall” sounds strange. You don’t go in the supermarket and call the product price a paywall, do you? 🙂

[deleted]

diekuh Can you please clarify - will we be able to setup clustering without having to pay, or will this be a ‘premium’ (paid) feature?

I of course understand that you guys need to make money somehow, but putting features behind a paywall (and yes, I would call this a paywall) doesn’t seem to follow the ‘FOSS philosophy’.

TheDoctor

Sooooo, what is the status of this topic? Can you give us a sneak peak of the documentation? @diekuh

diekuh

@[deleted] FOSS does not mean that other people work for you for free. 🙂 The whole stack is free to use, open source and already able to run as active/active. Your comment is pretty presumptuous in that regard. :/

It is not a feature that is hidden behind a paywall. You can figure it out by yourself any time. Just check the code.

Please write a mail to info@tinc.gmbh if you are interested in such a setup.

TheDoctor

@diekuh I am sorry my post sounded presumptuous. I am a fan of your work and 😃 thought that you have more expertise in this field than me. I was just very exited about a good way to do this with an existing setup without too much interfering.

diekuh

Not yours, TheDoctor 🙂

Niklas is working on translating it already. 🙂

Elysweyr

diekuh Hi, is this something where you would appreciate support from German native speakers?

BusterB

Thanks for your hard work and support with mailcow, diekuh.

Please consider me as a +1 requester for instructions on how to properly cluster two or more mailcow servers in an HA config.

After my host server crashed the other day and mail was unavailble for 6 hours as the primary NAS was rebuilding, my wife switched over to gmail. 😢 I’m hopeful a better setup on my end will prevent or reduce (eliminate?) outages like this in the future. I figured out “cold” and “warm” (manual) standbys and have those working great – I just haven’t been able to figure out how to set up an HA config just yet and I don’t feel like messing with my PROD servers or tinkering too much with the default mailcow settings or compose files without knowing what I’m doing. Mailcow’s working AMAZING right now, so I’m happy!

Unfortunately, during the outage my (warm) stanby server database got corrupted somehow – I’m guessing it might have been doing a sync when the primary mailserver crashed. It took me hours to find out all I had to do was delete a single log file in the MySQL volume on the backup server and then MOOHOO! Everything came back up!

I don’t know German, but if I can help with some of the documentation (validation), feedback or testing, please let me know.

gVes

Hi, I am also very interested in being to create a mailcow server cluster. Please keep us posted!

dia_moos

@diekuh gibt es Neuigkeiten bezüglich der Cluster Doku? Kann die Community irgendwie helfen?