I walked through the mailserver.env file and made a few changes I’m going a slightly different path than the recommended one which uses docker-compose, and will build out a basic docker deployment. Once you think you’re ready to start installing thing the ReadMe is the right path to follow. Every stat is in pre-fail or old age, it is definitely time to move my email off that drive.īefore starting, take the time to read through the documentation. The SMART information says that the Power Cycle Count is only 502, but the Power On Hours is an astounding 130442 (that is 14.89 years). It is a Seagate Barracuda 40GB ( ST340014A). The hard drive that stores my email is very old. The SSD rebuild disrupted how I was doing things, and changing email is a little scary. I started doing this way back in 2017, but never really finished the work. The docker-mailserver project stands out for me as they have avoided database based configuration and have stuck with ‘files on disk’ as the model. I will mention there are many alternatives: mailu, iredmail, etc. Using the docker-mailserver solves all of the email problems with a single container. I’ve run my own email for a long time, mostly following the Ubuntu setup. If you are still thinking of running your own mail server, then grab your tinfoil hat and let’s look at the best way to operate a mail server in the age of containers. Alternatives are offered by Google, and Microsoft if you want to go that route, both provide support for custom domains. ProtonMail would be a good choice, you can even bring your own custom domain and still use ProtonMail. There are lots of providers out there that run email services and allow you to bring your own domain. Almost no one should run their own email server, it’s complicated and makes you responsible for all of the problems. Having a website on your domain is easy and a sensible use of that domain name. Everyone should have their own domain name (or several).

Makemkv how to get segment map