[Mailman-Users] Migrating Mailman to New Server (Same Domain)

Jewel Brueggeman-Makda jewel.brueggeman-makda at washburn.edu
Mon Oct 24 09:41:09 EDT 2016

Would it be best to copy the entire mailman directory to the new server or just the lists and archives?  
Command issued on new server to copy data from old.
rsync -avr root at serverip:/usr/local/mailman /usr/local/mailman

-----Original Message-----
From: Mailman-Users [mailto:mailman-users-bounces+jewel.makda=washburn.edu at python.org] On Behalf Of Mark Sapiro
Sent: Saturday, September 24, 2016 11:36 AM
To: mailman-users at python.org
Subject: Re: [Mailman-Users] Migrating Mailman to New Server (Same Domain)

On 09/23/2016 02:50 PM, Jewel Brueggeman-Makda wrote:
> TGIF Mailman Gurus,
> My current Mailman 2.1.12 server is lists.washlaw.edu and is running on a RedHat vm.  I need to move it onto a new server which already has a new instance of Mailman 2.1.22 also on a RedHat vm. I already ran the ./configure command to be the same setup as the OLD server.  I have searched the discussion list archives on the steps and am not fully understanding what needs to be done. Below are the steps I do know I need to take but then I am at a loss.
> 1.       Post Postfix, Apache and Mialman on OLD server and NEW servers
> 2.       Tar up the lists and archives from the mailman directory and copy the tar files to the new server
> a.       tar xvfx /usr/local/mailman/lists

should be  'tar cpvzf lists.tgz /usr/local/mailman/lists'

> b.      tar xvfz /usr/local/mailman/archives

should be 'tar cpvzf archives.tgz /usr/local/mailman/archives'

caveat: do not use the -h/--dereference option because archives/public contains only symlinks, and if it winds up with actual files, they don't get updated.

> 3.       Untar the lists and archives onto NEW server
> a.       tar -xvf lists.tgz
> b.      tar -xvf archives.tgz

Or instead of 2 and 3, if the two servers can talk to each other, use 'rsync -a'.

> c.       Run from /usr/local/mailman/bin ./check_perms -f
> 4.       Run newaliases

You don't need to run newaliases, but you do need to run Mailman's bin/genaliases.

Assuming the new server will ultimately be accessed via the old servers mail and web domain names, that's all you need.

If domain names will change, you will need to run fix_url after moving the lists. See <https://wiki.list.org/x/4030616>.

And, for the archives, in order to fix URLs to listinfo pages in the archives, the easiest thing is to just move the /usr/local/mailman/archives/private/LIST.mbox/LIST.mbox files and rebuild the pipermail archives with 'bin/arch --wipe'

Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-users/jewel.makda%40washburn.edu

More information about the Mailman-Users mailing list