If you want to set up multiple mail servers then automation is your friend. Nowadays Ansible is commonly used for that purpose. If you are dealing with system administration you should have such a tool in your toolbox.
I have created an Ansible playbook on Github that you can download and use. Using it is pretty simple:
apt install ansible git
git clone https://github.com/Signum/ispmail-bookworm-ansible.git
cd ispmail-bookworm-ansible/ansible
ansible-playbook ispmail.yml -c localPlease follow the hints in the README.md within the repository.
cd ispmail-“bullseye”-ansible/ansible should “bookworm”.
(and I could also found references to “stretch” in Migrating and FAQ 🙂 )
And many thanks for your guides. I am using them for many years.
Regards, Thomas
No matter how hard I try – I always forget some old wording. Thanks for the hint and travelling with us. 🙂
Hi !
First of all, thanks a lot for your great work, I learned a lot already ^^
Yesterday I tried the ansible playbook :
certbot requested a certificate for “domain.com” instead of “mailserver.domaine.com”
I didn’t look further but ran certbot by hand and commented out the role “certbot” in the ansible playbook and everything seems fine.
Cheers
I clearly seem to have messed up somewhere with the ansible playbook because I keep getting the error:
[WARNING: Could not match supplied host pattern, ignoring: mx.[mydomain].com
ERROR! Specified inventory, host pattern and/or –limit leaves us with no hosts to target.
nevermind my comment, it was the result of a lack of sleep. realized after looking through ansible.cfg that the directory ispmail-bookworm-ansible expects to be located in /etc