Size: 862
Comment: remove obsolete gunk (verified it's not needed), add what i *think* it was we need to do to move to a new server again...
|
Size: 1185
Comment: to move all lists to a new server, just rsync /var/lib/mailman
|
Deletions are marked like this. | Additions are marked like this. |
Line 14: | Line 14: |
=== Individual Lists === | DomTool also needs some settings updated. === 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`. == Importing Individual Lists == |
1. Migrating Mailman Between Servers
Copy /etc/mailman to new server
Might just need mm_cfg.py and vhosts_cfg.py
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.