MailCow in Production Datacenter
-
@scottalanmiller said in MailCow in Production Datacenter:
@stacksofplates said in MailCow in Production Datacenter:
@Curtis said in MailCow in Production Datacenter:
@stacksofplates @scottalanmiller
https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml
Yeah I know there's a default, I didn't know if he had changed it at all.
I had not, the default didn't work so I wasn't looking to modify it yet.
ok. Let me spin up a system with docker and compose. I've been using podman so I don't have the tools on my laptop.
-
I was able to proxy through NGINX after running
docker-compose up -d. I didn't use HTTPS because I'm lazy but it passed HTTP fine. -
It's just a simple config to test (again because I'm lazy):
-
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
-
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Let me know if you have issues and I'll make a video for you
-
I have been running Mailcow for a little while, been testing and playing about with it. I'm quite impressed how it's all been put together. I would love to hear how many mailboxes people are running this in production.
Not using a reverse proxy on mine though.
-
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
-
@scottalanmiller said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
Using Docker?
-
@FATeknollogee said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
Using Docker?
Is there any other way? MailCow appears to be 100% dependent on Docker.
-
@scottalanmiller said in MailCow in Production Datacenter:
@FATeknollogee said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
Using Docker?
Is there any other way? MailCow appears to be 100% dependent on Docker.
I don't know of any other way which is why I asked!
Previously, we had that forum discussion & I thought the general consensus was Docker for this use case wasn't a great idea? -
@scottalanmiller said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
Did you have any issues using Nginx at all to start with?
-
@StuartJordan said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
Did you have any issues using Nginx at all to start with?
I did last time I tried like six months ago. This time, no issues.
-
@FATeknollogee said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
@FATeknollogee said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got
Been a while, and now it is a different project. This time for a customer. But we have MailCow up and running now and behind an Nginx proxy in a datacenter. Working great so far.
Using Docker?
Is there any other way? MailCow appears to be 100% dependent on Docker.
I don't know of any other way which is why I asked!
Previously, we had that forum discussion & I thought the general consensus was Docker for this use case wasn't a great idea?Docker is truly terrible here, IMHO. So much unnecessary complexity. But at least it is working.
-
@scottalanmiller said in MailCow in Production Datacenter:
Docker is truly terrible here, IMHO. So much unnecessary complexity. But at least it is working.
Basically, no other choice bit to "accept" Docker! (in this use case).
Is it good enough for you guys to ditch Zimbra & switch?
-
@FATeknollogee said in MailCow in Production Datacenter:
@scottalanmiller said in MailCow in Production Datacenter:
Docker is truly terrible here, IMHO. So much unnecessary complexity. But at least it is working.
Basically, no other choice bit to "accept" Docker! (in this use case).
Is it good enough for you guys to ditch Zimbra & switch?
We already ditched Zimbra and moved to Zoho, which we love. MailCow is rockin', though. But this is for a customer, not for us internally. But if we were still on Zimbra, this would be far better for us from what I've seen so far. The interface is da bomb.
-
Was there a consensus on the "best" distro to use for MailCow? @scottalanmiller what are you running it on?
-
Question for Scott - the customer wanted self hosted email? why?
Why is NTG on self-hosted email solution? I thought that today that was just generally not the way to go? Is it because you're an IT company?
-
@Dashrender said in MailCow in Production Datacenter:
Question for Scott - the customer wanted self hosted email? why?
Because the business needs or wants it. This isn’t a discussion on why.
Why is NTG on self-hosted email solution? I thought that today that was just generally not the way to go? Is it because you're an IT company?
NTG isn’t on self hosted.
-
@bnrstnr said in MailCow in Production Datacenter:
Was there a consensus on the "best" distro to use for MailCow? @scottalanmiller what are you running it on?
That'a good question (the first part, I know the second part.) I could not find anywhere that MailCow recommended one thing or another. What they do recommend is installing Docker from the Docker repos and not from any distro's own repos.
So from what I can tell, Debian, Ubuntu, RHEL, CentOS, Fedora, Suse Leap, Suse Tumbleweed and loads of others will all work just fine. Essentially anyone that supports Docker, in theory. But of course, Docker isn't universally compatible, so without MailCow documentation we just take our chances.
I know that Docker users almost universally use Ubuntu. So that's what we went with to minimize issues. Ubuntu 19.04.
-
@Dashrender said in MailCow in Production Datacenter:
Why is NTG on self-hosted email solution? I thought that today that was just generally not the way to go? Is it because you're an IT company?
NTG is on Zoho. But we could be on self hosted, our cost to do so is vastly lower than a normal company's cost to do so. But at $1/user, Zoho is pretty unbeatable.
