Urgent List Migration/Transfer - Need some help
All --
I need to move my existing Mailman system to a new AWS Server ASAP and could use some advice. The current server works just fine, the current problem is that the network it is on has been attacked, and the higher ups at IT have shut off all mail communication (in or out) to the internet.
So, someone not familiar with Mailman at all has this idea of moving the entire setup (lists, subscribers, any messages in the queues would be great) to a AWS instance. They have already gotten underway by .tar-ring var/lib/mailman/ and think they can simply unpack this. I'm sure that isn't going to work.
I know there is migration documentation in the Wiki & archives <http://wiki.list.org/pages/viewpage.action?pageId=4030682> <http://mail.python.org/pipermail/mailman-users/2007-January/055208.html> <http://mail.python.org/pipermail/mailman-users/2007-January/055211.html>
But would like to clarify that this information is up-to-date for our install (Mailman 2.1.9 --> ?? presumably the same or even a newer and better version).
I don't even have access tot he new server yet, so I can't comment on it's specs....sorry to be in a bit of a panic, it's really just other folks making this into an emergency.
Thanks for any help offered (including those who would like to get paid to do the work).,
Drew Tenenholz
On 04/23/2014 03:37 PM, Drew Tenenholz wrote:
But would like to clarify that this information is up-to-date for our install (Mailman 2.1.9 --> ?? presumably the same or even a newer and better version).
It's probably fine, but assuming the new server has a Mailman 2.1.9 or newer actually installed and working, here's the procedure I would follow:
On the new server, untar your tarball somewhere aside. 'cp -a' all of the directories in the tarball's var/lib/mailman/lists/ directory to the corresponding Mailman list's directory which may have a different path.
likewise all the var/lib/mailman/archives/private/*.mbox/ directories. Each of these LISTNAME.mbox directories should contain a single LISTNAME.mbox file which is the cumulative archive mbox for the list.
You can rebuild the a list's archive with 'bin/arch --wipe LISTNAME'. This may be preferable to copying all of archives/private because there are URLs in the HTML archive that may have the wrong host name. If not, you can copy the whole archives/private directory and skip the rebuild.
If some lists are very old, it's a good idea to check the mbox files with bin/cleanarch before running bin/arch.
It is not necessary or advisable to copy archives/public as this contains only symlinks and Mailman continuously (each time the list is saved) sets or removes those as appropriate for public/private archive settings. Its better not to try to copy archives/public/* because it's not necessary and if your tar followed symlinks you will be restoring files and your public archive will forever more consist of only those files.
You also have to deal with aliases for mail delivery. Depending on the new installation, bin/genaliases may be needed or nothing or some manual updates, but bin/genaliases will tell you about those.
Also, be sure to run bin/check_perms. This is usually needed.
The above will move the lists and archives. If you're concerned about held messages, shunted messages, etc. you could look at the data/ and qfiles/shunt directories, although they may not even be in your tarball depending on paths in the installation you're coming from.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 04/23/2014 03:37 PM, Drew Tenenholz wrote:
But would like to clarify that this information is up-to-date for our install (Mailman 2.1.9 --> ?? presumably the same or even a newer and better version).
It's probably fine, but assuming the new server has a Mailman 2.1.9 or newer actually installed and working, here's the procedure I would follow:
On the new server, untar your tarball somewhere aside. 'cp -a' all of the directories in the tarball's var/lib/mailman/lists/ directory to the corresponding Mailman list's directory which may have a different path.
likewise all the var/lib/mailman/archives/private/*.mbox/ directories. Each of these LISTNAME.mbox directories should contain a single LISTNAME.mbox file which is the cumulative archive mbox for the list.
You can rebuild the a list's archive with 'bin/arch --wipe LISTNAME'. This may be preferable to copying all of archives/private because there are URLs in the HTML archive that may have the wrong host name. If not, you can copy the whole archives/private directory and skip the rebuild.
If some lists are very old, it's a good idea to check the mbox files with bin/cleanarch before running bin/arch.
It is not necessary or advisable to copy archives/public as this contains only symlinks and Mailman continuously (each time the list is saved) sets or removes those as appropriate for public/private archive settings. Its better not to try to copy archives/public/* because it's not necessary and if your tar followed symlinks you will be restoring files and your public archive will forever more consist of only those files.
You also have to deal with aliases for mail delivery. Depending on the new installation, bin/genaliases may be needed or nothing or some manual updates, but bin/genaliases will tell you about those.
Also, be sure to run bin/check_perms. This is usually needed.
The above will move the lists and archives. If you're concerned about held messages, shunted messages, etc. you could look at the data/ and qfiles/shunt directories, although they may not even be in your tarball depending on paths in the installation you're coming from.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Drew Tenenholz -
Mark Sapiro