|
Size: 1185
Comment: to move all lists to a new server, just rsync /var/lib/mailman
|
Size: 1288
Comment: mention puppet
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Mailman packages and configuration are managed by Puppet class `hcoop::service::mail::mailman2` |
|
| Line 3: | Line 5: |
| 0. Copy `/etc/mailman` to new server * Might just need `mm_cfg.py` and `vhosts_cfg.py` |
0. Copy `/etc/mailman/{mm_cfg.py}` to new server * `vhost_cfg.py` is generated by DomTool. |
Mailman packages and configuration are managed by Puppet class hcoop::service::mail::mailman2
1. Migrating Mailman Between Servers
Copy /etc/mailman/{mm_cfg.py} to new server
vhost_cfg.py is generated by DomTool.
Copy /etc/exim4/mailmandb to new server
Stop mailman to prevent messages from being delivered while copying data: service mailman stop
Copy /var/lib/mailman to new server
In /etc/exim4/conf.d/main/01_exim4-config_listmacrosdef on:
the new mailman host: unset HCOOP_MAILMAN_RELAY_HOST
all other mail servers: set HCOOP_MAILMAN_RELAY_HOST to the new mailman host
Start mailman on new server: service mailman start
- Reload exim, and everything ought to work
DomTool also needs some settings updated.
1.1. Move All Lists
The entirety of /var/lib/mailman can just be rsynced between servers. This is assuming Debian configuration where system controlled content and data like locks are stored in external directories and just symlinked from /var/lib/mailman.
2. Importing Individual Lists
Not entirely sure, but an old post on mailman-users might have some insight.