Problems with mailman migration
Hi!
I run into problems migrating an old installation of mailman into a current one.
I've got the old installation of mailman (2.0.13) residing at /home/mailman. The mails should be moved to /var/lib/mailman where I installed the current package (2.1.4, debian testing/unstable).
I already tried the method explained in http://www.mail-archive.com/mailman-users%40python.org/msg11052.html but the script described in this mail threw lots of errors and the result didn't work. A newer method I found wasn't practicable because the new mailman version doesn't provide a move_list script.
At the moment, I'm using the current binaries and config.db's in /var/lib/mailman but the configurations point to /home/mailman (where the archives grow). My setup is really messed up, I know. :(
Could someone point me in the right direction where to find documentation for moving/upgrading my lists?
Thanks in advance, Martin Öhler
Martin Oehler wrote on Mon, 3 May 2004 23:03:41 +0200:
Could someone point me in the right direction where to find documentation for moving/upgrading my lists?
There isn't much to do when you want to move/upgrade lists. I upgraded from the standard mailman which came with my Suse distribution (residing in /var/lib/mailman or /usr/lib/mailman) and also was something like 2.0.x by just installing 2.0.14 to /usr/local/mailman and then moving over the content of the lists directory if I recall it right. I fiddled a bit around in the mm_cfg.py and I think I replaced all aliases. There's also a start script for starting the seven (or so) runner programs and you have to change that, too, if you change the installation path. In Suse systems this is a rcmailman symlink pointing at /etc/init.d/mailman. So I simply replaced that with a symlink to the new mailmanctl file in the new location. You can also copy that file over the old one at /etc/init.d, so that it starts correctly after a reboot. I then moved the list to another machine almost the same way, I only had to do some extra steps using the withlist command for correcting the url and mail hosts. (I also clone my lists this way.) The mailman lists are almost completely building upon their own information, so even if you don't change anything you get some results, f.i. the web interface will work but all the links in it will point to the old location. It's then very easy to resolve this step by step. If I understand you correctly, you didn't change the host, so it should even be easier.
Kai
--
Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org
Hi!
On Tue, May 04, 2004 at 02:32:04PM +0200, Kai Schaetzl wrote:
Martin Oehler wrote on Mon, 3 May 2004 23:03:41 +0200:
Could someone point me in the right direction where to find documentation for moving/upgrading my lists?
There isn't much to do when you want to move/upgrade lists. I upgraded from the standard mailman which came with my Suse distribution (residing in /var/lib/mailman or /usr/lib/mailman) and also was something like 2.0.x by just installing 2.0.14 to /usr/local/mailman and then moving over the content of the lists directory if I recall it right. I fiddled a bit around in the mm_cfg.py and I think I replaced all aliases. There's also a start script for starting the seven (or so) runner programs and you have to change that, too, if you change the installation path. In Suse systems this is a rcmailman symlink pointing at /etc/init.d/mailman. So I simply replaced that with a symlink to the new mailmanctl file in the new location. You can also copy that file over the old one at /etc/init.d, so that it starts correctly after a reboot. I then moved the list to another machine almost the same way, I only had to do some extra steps using the withlist command for correcting the url and mail hosts. (I also clone my lists this way.) The mailman lists are almost completely building upon their own information, so even if you don't change anything you get some results, f.i. the web interface will work but all the links in it will point to the old location. It's then very easy to resolve this step by step. If I understand you correctly, you didn't change the host, so it should even be easier.
Thanks for your migration guide, I'll try this and report whether I was successful.
Regards, Martin Öhler
participants (2)
-
Kai Schaetzl -
Martin Oehler