Time to update new mail server configuration to production hostnames ?

Sandro Santilli strk at kbt.io
Thu Sep 18 23:51:12 PDT 2025


Following the SPF change (which should now be already propagated),
I suggest we deploy the mail-servers playbook to production,
which would have the effect of updating the configurations on the osgeo9-mail container
to use the production URLs ( mail.osgeo.org and lists.osgeo.org ) instead of the staging ones.

What do you think ?


This is how you can see what would change:

  ANSIBLE_CONFIG=ansible.osgeo.prod.cfg \
  ansible-playbook -v deployment/deploy-mail-servers.yml
	-l osgeo9_mail \
  --check --diff

Most notable changes are:


	TASK [list-server : Install /etc/mailman/mm_cfg.py] ****
		--- before: /etc/mailman/mm_cfg.py
		+++ after: ...
		-DEFAULT_EMAIL_HOST = 'lists.staging.osgeo.org'
		+DEFAULT_EMAIL_HOST = 'lists.osgeo.org'
		-DEFAULT_URL_HOST   = 'lists.staging.osgeo.org'
		+DEFAULT_URL_HOST   = 'lists.osgeo.org'


	TASK [mail-server : Install postfix main.cf configuration] *****
		--- before: /etc/postfix/main.cf
		+++ after: ...
		-myhostname = lists.staging.osgeo.org
		+myhostname = lists.osgeo.org
		-myorigin = mail2.osgeo.osuosl.org
		+myorigin = osgeo.org
		-smtpd_tls_cert_file = /etc/letsencrypt/live/lists.staging.osgeo.org/fullchain.pem
		-smtpd_tls_CAfile = /etc/letsencrypt/live/lists.staging.osgeo.org/fullchain.pem
		-smtpd_tls_key_file = /etc/letsencrypt/live/lists.staging.osgeo.org/privkey.pem
		+smtpd_tls_cert_file = /etc/letsencrypt/live/lists.osgeo.org/fullchain.pem
		+smtpd_tls_CAfile = /etc/letsencrypt/live/lists.osgeo.org/fullchain.pem
		+smtpd_tls_key_file = /etc/letsencrypt/live/lists.osgeo.org/privkey.pem
		-mydomain = staging.osgeo.org
		+mydomain = osgeo.org

--strk;

  Libre GIS consultant/developer 🎺
  https://strk.kbt.io/services.html


More information about the Sac mailing list