Email-server: Installation directly on the server vs docker-containers. Does anyone here have positive/negative experiences with any of them?

It all feels like banging rocks together, when mailgun and Sendgrid are available.

@bahua yup. Unfortunately though we are required to either host everything ourselves, or host some kind of layer 4 proxy to redirect the messages.

The corporate policy is that our domain have to point to one of our own IP addresses.

@not-sure

We have the same policy. I am overjoyed not to have to deal with it. Best of luck to you.

@bahua thanks. I really don’t get it though

Someone recently told me mailcow seems to be awesome, and its docker based?
Since i have my personal vendetta against docker after working with it once i opted against it and choose iRedMail, but that requires a fresh system or it will fuck with existing configurations and not even your grandchildren will be able to find the problems.

There would be no value in containerizing email.

@justin-tamblyn I love docker for things like APIs and backends where it:
1. makes sense to be able to move things around easily
2. is nice to have multiple instances like production, staging, development and
3. is easy to run on local computer, or spin up a new temporary version on a server etc.
The email server is fairly static. What I don’t like with docker is the inability to easily change configuration and such.

I just found this docker-compose script which I think was quite cool: https://github.com/hardware/... though I’m not too comfortable going that direction, which is why I wanted to see if anyone had experience with it.

keep it as simple as it can, if docker is not a necessity for you then why?

@KorDarei mostly because it is easy and fast to setup with what I found.
I was hesitant to go that direction, but wanted to see if anyone had any positive experiences with it

I'm using MailCow (with docker) and I'm really happy with it