SUCCESS! Finally got mailcow-dockerized installed

tblancher

I had posted here nearly five months ago, asking questions about things I didn’t understand about the documentation, and how to get started with mailcow-dockerized. I was only working on it on weekends, with plenty of other stuff to keep me busy (I’m a father of a 17-month old boy, I’m active in my community, and I have a day job that doesn’t let me play with this stuff).

Suffice to say, after I was sure I had the right configuration set up, setting up my first domain was relatively painless. No issues launching the mailcow-dockerized stack with docker compose; and it does seem integrated quite well with my other Docker Compose stack. I have my other nginx pointing to the nginx-mailcow service, and I’m managing Let’s Encrypt/certbot from my Arch Linux host. I’m monitoring everything with New Relic (which is what I’d been working on for the past month), and I feel I have everything set up and ready to go! I can send and receive email at the one address I created, and I’m already checking it in GMail.

My next steps are to add some other domains I control to this new installation. If that is successful I’m planning on migrating my father’s email domains to a new VPS (this time probably running Rocky 9, for maintainability by someone other than myself). One of his domains is what I use for my main personal email address, and I’m eager to fully control it.

DocFraggle

Congratz 😃

My 5 pennies regarding Rocky 9: I don’t know if you heard about the latest move (ok, it’s been a few months now) of RedHat to maybe close their upstream sources. If they do that, Rocky Linux can’t use them anymore to update their packages, and Rocky still doesn’t have a real answer about what they will do then.

https://rockylinux.org/news/keeping-open-source-open/

Just keep that in mind and maybe switch to another supported distro 🙂

tblancher

DocFraggle

Yes, I’ve read plenty about the ire from the wider Linux community Red Hat brought on by only providing source RPMs to paying customers. However, the article you linked to indicated that Rocky has two viable, legal methods to obtain the SRPMs. There’s at least one level of indirection for both methods, and it’s possible Red Hat tries to close this “loophole” (for lack of a better term), but Rocky will continue as best it can.

[unknown]

I used to run Debian on all my personal devices, even my DIY home router. I ultimately got tired of the Debian way once I started using Arch Linux in earnest. Granted, I’ve maintained the Debian ways that I still think are good ideas, but dropped a lot of the things Debian does as a matter of principle. Arch Linux gives you the flexibility to do that, without compromising functionality or purpose.

I’m going with a modern Red Hat based distro mainly to keep my skills in that area as current as possible. Most of my recent Red Hat experience has been on RHEL7, which is end of life on July 1, 2024. My dad’s VPS is running CentOS 7, which is EOL on the same day. I’m mainly going with Rocky (or perhaps Alma, if they navigate the Red Hat drama better than Rocky) so it’s maintainable by someone other than me, since my father will also be using the new VPS.

esackbauer

Debian FTW 😉