mirror of
https://gitlab.archlinux.org/archlinux/infrastructure.git
synced 2024-05-23 10:26:03 +02:00
893a95f329
With the final lists migrated to mailman3[1], the mailman2 server can finally be killed. When the mailman3 server was initially setup[2], it was done on a separate server because the mailman and mailman3 packages conflicted, and the traffic was routed over wireguard (HTTP, LMTP and SMTP). Instead of installing mailman3 on the original lists.al.org server and transferring the data, it was easier just to install the missing pieces (basically Postfix and adjusting the Nginx configuration) on the ml3 server and move the IPs (to keep the IP mail reputation). So basically the following was done: - The IPs for the original lists.al.org was moved to the mailman3.al.org server - The mailman2 datadir was transferred to mailman3.al.org server, so we can keep the pipermail links alive, and import missing mails if needed - The original lists.al.org server was decommissioned - The mailman3.al.org server was renamed to lists.al.org - The missing pieces was added to the mailman3 role (basically Postfix + Nginx adjustments) - The mailman role was deleted and the mailman3 role renamed to mailman [1]75ac7d09("mailman: Fourth and final batch of mailman3 migrated lists") [2]9294828f("Setup mailman3 server") Fix #59
17 lines
422 B
Django/Jinja
17 lines
422 B
Django/Jinja
[mailman]
|
|
site_owner: root@{{ lists_domain }}
|
|
layout: fhs
|
|
|
|
[database]
|
|
class: mailman.database.postgresql.PostgreSQLDatabase
|
|
url: postgres://{{ vault_mailman_db_user }}:{{ vault_mailman_db_password }}@/mailman
|
|
|
|
[webservice]
|
|
admin_user: {{ vault_mailman_admin_user }}
|
|
admin_pass: {{ vault_mailman_admin_pass }}
|
|
|
|
[archiver.hyperkitty]
|
|
class: mailman_hyperkitty.Archiver
|
|
enable: yes
|
|
configuration: /etc/mailman-hyperkitty.cfg
|