move mail lists from Solaris to redhat
Currently we have mailman running on an old Sun sparc with Solaris 8. I installed mailman on a new linux server with Redhat 4. I did some tests and mailman seems to work fine on the new system with newly created lists. The next step is to move the mail lists from the Solaris system to the Redat system. Does someone has done this before? Can I just move the content of the lists, archive/public and archive/private folders? I noticed that Linux is using sometimes a different file extension than on Sun. As an example config.pck is found on linux and config.db is found on Solaris
Greetings, Dany
We are also migrating our mailing lists from solaris (Majordomo) to Red Hat Linux (Mailman). I am planning to use the mailing list web admin "mass subscription" upload file feature to load the mailing list to the new server.
UR.
At 08:47 AM 6/28/2006, you wrote:
Currently we have mailman running on an old Sun sparc with Solaris 8. I installed mailman on a new linux server with Redhat 4. I did some tests and mailman seems to work fine on the new system with newly created lists. The next step is to move the mail lists from the Solaris system to the Redat system. Does someone has done this before? Can I just move the content of the lists, archive/public and archive/private folders? I noticed that Linux is using sometimes a different file extension than on Sun. As an example config.pck is found on linux and config.db is found on Solaris
Greetings, Dany
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/urao%40pop200.gsfc.nasa...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
This entry from the Mailman-Users archive helped me lot
http://www.mail-archive.com/mailman-users@python.org/msg35691.html
The config.db is indeed converted to a config.pck at first access. I also copied the files in the archive folders and ran
bin/withlist -l -r fix_url mylist
Uthra Rao wrote:
We are also migrating our mailing lists from solaris (Majordomo) to Red Hat Linux (Mailman). I am planning to use the mailing list web admin "mass subscription" upload file feature to load the mailing list to the new server.
UR.
At 08:47 AM 6/28/2006, you wrote:
Currently we have mailman running on an old Sun sparc with Solaris 8. I installed mailman on a new linux server with Redhat 4. I did some tests and mailman seems to work fine on the new system with newly created lists. The next step is to move the mail lists from the Solaris system to the Redat system. Does someone has done this before? Can I just move the content of the lists, archive/public and archive/private folders? I noticed that Linux is using sometimes a different file extension than on Sun. As an example config.pck is found on linux and config.db is found on Solaris
Greetings, Dany
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/urao%40pop200.gsfc.nasa...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
--
Dany Cuyt DEPARTMENT OF PLANT SYSTEMS BIOLOGY Fax:32 (0)9 3313809 GHENT UNIVERSITY/VIB, Technology Park 927, B-9052 Gent, Belgium Vlaams Interuniversitair Instituut voor Biotechnologie VIB mailto:dacuy@psb.ugent.be http://www.psb.ugent.be
Dany Cuyt wrote:
Currently we have mailman running on an old Sun sparc with Solaris 8. I installed mailman on a new linux server with Redhat 4. I did some tests and mailman seems to work fine on the new system with newly created lists. The next step is to move the mail lists from the Solaris system to the Redat system. Does someone has done this before? Can I just move the content of the lists, archive/public and archive/private folders? I noticed that Linux is using sometimes a different file extension than on Sun. As an example config.pck is found on linux and config.db is found on Solaris
Generally, you can just move the archives/private/* and lists/* directories except maybe not for the 'mailman' list if there is one on the old server, because there already is one on the new server since Mailman is running there. The symlinks in archives/public/ will be regenerated by Mailman as the lists are accessed, but you can move them if you want if the paths are correct.
The config.db->config.pck and maybe requests.db->requests.pck is not a Solaris->RedHat difference. It is a Mailman version difference 2.0->2.1 in the case of config.db->config.pck and 2.1.4->2.1.5 in the case of requests.db->requests.pck. Mailman will convert these for you the first time the list is accessed on the new server, as long as you have not already created the lists there. I.e. if Mailman finds only a config.db and maybe config.db.last, it will convert it to the proper config.pck, but if there is already a config.pck there, it will ignore the config.db.
Do not try to rename config.db to config.pck. The formats are entirely different.
There may still be issues after you move the lists if the new server has a different domain name. In this case, you have to run fix_url on all the moved lists in order to fix the names and you may want to rebuild the archives with bin/arch in order to fix the 'more information about this list' links to the 'listinfo' page. If you are going to do this step, then you only need to move the archives/private/*.mbox directories as the rest will be rebuilt from the archives/private/*.mbox/*.mbox files.
Run
bin/fix_url.py
and
bin/arch --help
for more info in these tools. There is also info on this in the FAQ <http://www.python.org/cgi-bin/faqw-mm.py>, but the specific info in FAQ 3.4 is somewhat out of date.
I see this post may be 'too late' but I'll send it anyway. (I hope I'm not contradicting myself).
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
What about archives/public directory? Does that have to be moved?
Originally, I thought of just tarballing/gzipping the entire mailman directory and moving the whole thing to the new server. There would be no URL change, so possibly would just require some tweaking of the GIDs and paths. Would that be a good way to approach a migration or is it unnecessary?
On 6/28/06, Mark Sapiro <msapiro@value.net> wrote:
Dany Cuyt wrote:
Currently we have mailman running on an old Sun sparc with Solaris 8. I installed mailman on a new linux server with Redhat 4. I did some tests and mailman seems to work fine on the new system with newly created lists. The next step is to move the mail lists from the Solaris system to the Redat system. Does someone has done this before? Can I just move the content of the lists, archive/public and archive/private folders? I noticed that Linux is using sometimes a different file extension than on Sun. As an example config.pck is found on linux and config.db is found on Solaris
Generally, you can just move the archives/private/* and lists/* directories except maybe not for the 'mailman' list if there is one on the old server, because there already is one on the new server since Mailman is running there. The symlinks in archives/public/ will be regenerated by Mailman as the lists are accessed, but you can move them if you want if the paths are correct.
The config.db->config.pck and maybe requests.db->requests.pck is not a Solaris->RedHat difference. It is a Mailman version difference 2.0->2.1 in the case of config.db->config.pck and 2.1.4->2.1.5 in the case of requests.db->requests.pck. Mailman will convert these for you the first time the list is accessed on the new server, as long as you have not already created the lists there. I.e. if Mailman finds only a config.db and maybe config.db.last, it will convert it to the proper config.pck, but if there is already a config.pck there, it will ignore the config.db.
Do not try to rename config.db to config.pck. The formats are entirely different.
There may still be issues after you move the lists if the new server has a different domain name. In this case, you have to run fix_url on all the moved lists in order to fix the names and you may want to rebuild the archives with bin/arch in order to fix the 'more information about this list' links to the 'listinfo' page. If you are going to do this step, then you only need to move the archives/private/*.mbox directories as the rest will be rebuilt from the archives/private/*.mbox/*.mbox files.
Run
bin/fix_url.py
and
bin/arch --help
for more info in these tools. There is also info on this in the FAQ <http://www.python.org/cgi-bin/faqw-mm.py>, but the specific info in FAQ 3.4 is somewhat out of date.
I see this post may be 'too late' but I'll send it anyway. (I hope I'm not contradicting myself).
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/adamsca%40gmail.com
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
-- Christopher Adams adamsca@gmail.com
Christopher Adams wrote:
What about archives/public directory? Does that have to be moved?
There needs to be an archives/public/ directory on the new host, but since Mailman is already installed there, one would have been created during the install process. WRT the actual archives/public/<list> symlinks, these are checked and added or deleted as necessary each time the list is accessed, because you might have changed the list from public to private or vice versa. What I said in my post was:
The symlinks in archives/public/ will be regenerated by Mailman as the lists are accessed, but you can move them if you want if the paths are correct.
Originally, I thought of just tarballing/gzipping the entire mailman directory and moving the whole thing to the new server. There would be no URL change, so possibly would just require some tweaking of the GIDs and paths. Would that be a good way to approach a migration or is it unnecessary?
This is a way to do it if you want the same Mailman version on the new box and if the hardware/OS is similar enough that the compiled and linked, C source wrappers (cgi-bin/* and mail/mailman) will work. The advantage of this approach, assuming you stop Mailman and incoming mail and the web server before making the tarball, is you get everything including held messages and pending requests.
If you don't shut everything down, you run the risk of the tarball not being self consistent. Stopping Mailman is not enough as incoming mail will still invoke the wrapper and be queued in Mailman and web changes can still be made. Plus, if you shut off the incoming MTA, any incoming posts or other mail will just be queued in the sending MTAs until you're back online.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Christopher Adams -
Dany Cuyt -
Mark Sapiro -
Uthra Rao