[nobody9999]

>Any tutorials/software you can recommend for this?

Not GP, but the process is pretty simple:

You'll need to be able to send, receive, store and forward emails. A variety of resources are required to do this. Note that pretty much all of the software suggestions are available through the default software trees of just about every Linux/BSD distribution.

1. You'll need a domain;

2. You'll need DNS services to publish your MX records with DMARC/DKIM/SPF[17] and/or DANE[18] support. If you can/want to host your own (not difficult), lots of folks like Unbound[0][1]. And while some folks hate on BIND[2][3], it's always a good choice. There are many others[4] as well;

3. You'll need a Mail Transfer Agent[5] (MTA) to send and receive emails. Postfix[6][7] is very popular. Some folks use Exim[8][9]. And others use the venerable sendmail[10][11];

4. You'll also need a Mail Delivery Agent[12] to store your mailboxes and serve them via a web interface and/or your mail client. Lots of folks like Dovecot[13][14]. Others use Cyrus[15][16].

[0] https://www.nlnetlabs.nl/projects/unbound/about/

[1] https://www.redhat.com/sysadmin/bound-dns

[2] https://www.isc.org/bind/

[3] https://www.firewall.cx/linux-knowledgebase-tutorials/system...

[4] https://en.wikipedia.org/wiki/Comparison_of_DNS_server_softw...

[5] https://en.wikipedia.org/wiki/Message_transfer_agent

[6] http://www.postfix.org/

[7] http://www.postfix.org/documentation.html

[8] https://www.exim.org/

[9] https://www.exim.org/exim-html-current/doc/html/spec_html/ch...

[10] ftp://ftp.sendmail.org/

[11] https://www.sendmail.org/~ca/email/doc8.12/op.html

[12] https://en.wikipedia.org/wiki/Message_delivery_agent

[13] https://www.dovecot.org/

[14] https://doc.dovecot.org/

[15] https://www.cyrusimap.org/

[16] https://www.cyrusimap.org/quickstart.html

[17] https://trendlineinteractive.com/resources/article/what-are-...

[18] https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Na...

Edit: Added link for DMARC/DKIM/SPF and reference/link for DANE.

[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.