How does this scale up?

[titansmc]

Hi,
We are an organization of roughly 2000 heavily mail users and we plan to migrate to some other solution, but I am not sure if this setup will be able to scale, currently we have 8 VM's handling IMAP, 2 of them SMTP, 2 for webmail an IronPorts for doing SPAM filtering. Do you guys think this solution is able to scale horizontally ?

Thanks.

[kaiyou]

Sorry for the delay, I have been more than overwhelmed lately and focusing on replacing SQLite, specifically for some performance issues.

Currently Mailu will probably not scale up horizontally. It could in theory, with very little adjustments, but it would require some work that I personally won't have time to take upon until the end of the year.

[muhlemmer]

Horizontal scaling using Docker Swarm should possible soon. See issue #530 and PR's #563, #560 and #551(outdated). If kubernetes is more your cup of coffee, see PR #559. With a bit of luck it should be supported in master soon and probably in the next release.

If you are a mail admin, you might be able to convince you employer to spend some hours helping out here, in order to implement it in your company 😉

[titansmc]

That sounds really cool! Thanks for the efforts. So far we are using qmail and fixing some issues we have, but the next step is to convince the boss we should move to a postfix solution docker based and ideally Mailu :) But maybe I can get involved in the project in my spare time. I have an off topic question...for us to implement this I guess we would need commercial support, are you planning to provide it? Cheers. Missatge de Tim Möhlmann <notifications@github.com> del dia dj., 9 d’ag. 2018 a les 13:32:

…

Horizontal scaling using Docker Swarm should possible soon. See issue #530 <#530> and PR's #563 <#563>, #560 <#560> and #551 <#551>(outdated). If kubernetes is more your cup of coffee, see PR #559 <#559>. With a bit of luck it should be supported in master soon and probably in the next release. If you are a mail admin, you might be able to convince you employer to spend some hours helping out here, in order to implement in you company 😉 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#520 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH0AYEBDoX1qS5jSKmyL-Xh8WYeXawVZks5uPB3OgaJpZM4VJGUn> .

-- ------------------------------------------------ http://www.arruixaqueplou.org http://www.terradelfoc.blogspot.com -------------------------------------------------

[muhlemmer]

I'm not part of this organization, just a contributor which wants Swarm support for his own infrastructure. But I've seen the author (Kaiyou) denying donation before since he can't be at it full time. (#508)

But, once you have Docker up and running it is really user-friendly to set up. Using the classic docker-compose way, you'd be done in half hour (if you already have a server running Docker)

Docker swarm will take a bit more, since you have to set up some kind shared network storage between Nodes and what not. This is outside the Mailu scope, but it does take some extra time to administer the servers.

You could always get a managed platform for Docker swarm or Kubernetes, like Google, CoreOS, Red Hat etc. At least you can get commercial support from there for the Docker infrastructure. Network filesystems, configuration distribution etc.

[titansmc]

Thanks ! I've tested it on docker-compose and I found it really cool. But now I would like to go further (once this is ready for Kubernetes) and convince my company to move to it, for the docker platform is fine, we have experience and it doesn't worry, but for the mail software would be nice to have commercial support since we are maintaining more than 1k mailboxes through several domains and we aren't that much people in the team, so it would be nice to have enterprise grade support. But I understand what author say...let see if we find a formula that fits all of us! Cheers. Missatge de Tim Möhlmann <notifications@github.com> del dia dj., 9 d’ag. 2018 a les 14:18:

…

I'm not part of this organization, just a contributor which wants Swarm support for his own infrastructure. But I've seen the author (Kaiyou) denying donation before since he can't be at it full time. (#508 <#508>) But, once you have Docker up and running it is really user-friendly to set up. Using the classic docker-compose way, you'd be done in half hour (if you already have a server running Docker) Docker swarm will take a bit more, since you have to set up some kind shared network storage between Nodes and what not. This is outside the Mailu scope, but it does take some extra time to administer the servers. You could always get a managed platform for Docker swarm or Kubernetes, like Google, CoreOS, Red Hat etc. At least you can get commercial support from there for the Docker infrastructure. Network filesystems, configuration distribution etc. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#520 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH0AYGmOrp5hZTt7oq3k7_1y-juFzw7tks5uPCimgaJpZM4VJGUn> .

-- ------------------------------------------------ http://www.arruixaqueplou.org http://www.terradelfoc.blogspot.com -------------------------------------------------

[rakshith-ravi]

@muhlemmer @kaiyou I'm looking for a similar solution. I'm looking to abstract away the database part into a separate server (if only it was on MySQL or something similar), move all the email files into a shared volume so that we can have 2-3 separate "app servers" that all share the same data for the sake of horizontal scaling. I would love to have something like that for my company.

That being said, I'm more than willing to help with the project. I'm not sure where to start yet. I'm okayish in terms of knowledge about these fields, but pretty well versed with infrastructure scalability. So I'd love it if you could point out some resources that I could read up that'd help me contribute to the project. I could also test scalability out on actual instances and help in that sense too. Please do let me know what I can read up and what the important files I need to focus on are, in order to implement this.

[muhlemmer]

Let's include a summary of this conversation in the FAQ. #564