docker-mailserver VS playbooks

I have used Roundcube docker-compose-fpm.yaml, which looks like it can be easily extended with docker-mailserver

However... For a live fire, in production setup I would push people to use a meta package like docker-mailserver, mailcow, mail-in-a-box or modoboa as it's better to have someone else set the sane defaults to prevent you from missing that one line in you config.

Se proprio vuoi farlo per il gusto di riprendere familiarità con i vari concetti, giocherei con dei set di container docker tipo https://github.com/tomav/docker-mailserver (su GitHub ne trovi molti altri, alcuni tipo mailcow anche con GUI per gestire il grosso delle opzioni).

Yes, spam learning is documented on the Wiki.

At work we deploy to VMs in VMware vCloud director, using Terraform and Ansible. I actually have the Ansible repo we use public, but it's a 3yo holy mess and I've made a new one that I use in my homelab so far, like that one much better.

It sure is, use at your own peril. This is my first attempt at setting up kubeadm with Ansible, also the repo we currently use at work. While it can be used for both on-prem and managed k8s, it's a holy mess and I would not suggest anyone use it.

I made some ansible playbooks to quickly setup one on Linode. But they're still missing the SPF+DKIM+DMARC setup in DNS I need to have a chance of sending mail.

Then I automated the setup of a Linode VPS+Route53 DNS to create a recipient email server at the press of a button using ansible, will add other hosts to it like Digitalocean and DO DNS in time.

Here's one example of me spinning up a MariaDB cluster using vagrant and ansible: https://gitlab.com/stemid-ansible/playbooks/ha-maxscale

If you're into that kind of stuff I make my ansible playbooks available on Gitlab.

Well then your goal now is to destroy the cluster and re-build it with automation. I use Ansible to do that in Vagrant CentOS 7 boxes.

My own Ansible+vagrant setup works only om CentOS.