[rootsudo]

Great reply, I would say this is the way to go to learn and then if you get lazy, mailinabox https://mailinabox.email/ it combines everything above into a few hours to deploy.

But you still need to know everything above.

Then once you done this a few times, you have your own niche in tech - email is old and going no where and job security is ensured, it's funny, tech really is a circle.

[nobody9999]

>Great reply, I would say this is the way to go to learn and then if you get lazy, mailinabox https://mailinabox.email/ it combines everything above into a few hours to deploy.

Thanks!

A fair point. Although the bulk of that deployment time is, regardless of platform, going to be the configuration.

And since pretty much all the tools needed can be installed via 'apt-get'/'dnf install', etc. through default software repositories, is there any real advantage for more technical folks (as we generally see here)to use mailinabox over someone's preferred *nix configuration?

I'm not being snarky here, I'm not familiar with mailinabox and genuinely curious.

[rootsudo]

The people that run mailinabox and the subscription list/slack/chat are nice. If you know exactly what you're doing, and can put it all together in a bash script, then it's no different. Especially the later configuration part.

But having a place where to exchange (haha get it) info and see whats targeting/affecting most self hosted email users is really a time savings vs having to scope through your own logs and wonder what broke, or what's wrong.