More than 3 years ago I’ve written an article about self-hosting email. Throughout the years that setup was adjusted, migrated and changed in various ways. I’ve used it on the FreeBSD, Debian, Ubuntu since the original article which was based on CentOS. Now, I’m trying to set it up again on the CentOS, this time on the CentOS 8 and components to achieve the whole flow are changed a bit, and there are even some new ones....
Having wildcard SSL certificate can sometimes really help with streamlining vhost creation, where you don’t need to step extra step for issuing new SSL/TLS certificate. Although I attempt to automate every bit of the infrastructure I manage, and also have certificate issuance automated with my current configuration management system of choice - Ansible, it is still nice to have only one certificate to worry about as it streamlines the whole process of reloading the services after renewal and so on....
Recently I’ve been tasked to set up Confluence server installation. One of my friends was in need and I decided it would be nice to play a bit with the whole setup. As this is pro-bono and really not quite production install (meaning they use it, but it is not so downtime critical) there was a place to experiment with it a bit thus I decided to run Confluence in a Docker....
There are many reasons why would somebody want to host their own email server. There are many advantages for doing this but there are also many drawbacks. Setting up your own mail server can certainly be a great learning experience filled with discoveries about different set of technologies, protocols and how stuff works in general. Hosting your own email server can also be a huge pain in the ass, especially if you start to have problems with spamming but I won’t go too deep into pros or the cons since, if you’re already here, you probably read a thing or two and decided for yourself if you want to host your own email server or not....