Re: [Mailman-Users] Moving lists with large archives to new server
On 01/30/2015 03:09 PM, Andrew Hodgson wrote: My question revolves around the list archives. If I start Mailman up before they are copied across, it is likely there will be waiting messages and these will get archived to a new mbox file. I want to reduce downtime in moving the lists, but the mbox files are around 25GB, and there are a couple of lists which take the majority of that. I was going to index the messages once the mbox files are copied over, but what is the smartest way to get these moved without downing Mailman for too long? It seems like you are planning to just move the archives/private/LIST.mbox/LIST.mbox files and rebuild the archives with bin/arch --wipe after the .mbox files are moved. This in fact is the recommended procedure. One consideration is whether you want to preserve the message numbers in the new archive. If you don't do this, and someone has a saved URL to an archived message, that URL will return a different message from the new archive. So let's assume you do want to do this. The second consideration is whether your .mbox files are good. They probably are, but if they go back several years and you haven't previously checked, they may contain unescaped From lines in message bodies. bin/arch is very lax about validating From separators. Any line that begins with those 5 characters is considered a message separator and can result in trailing parts of messages being in the archive without headers and separately from the leading parts. This is normally not an issue with .mbox files written only by 2.1.x versions of Mailman. Mailman's bin/cleanarch script can help detect and fix such problems. OK. Now we'll assume you have a bunch of good LIST.mbox files on the old server which you just stopped. I think there are two ways to proceed. You'll have to decide which works better for you. While typing, I decided Way 2. is better. Way 1. Bring up the new server and start Mailman. Let the lists operate and messages archive. These messages will ultimately be renumbered, but this is a relatively short window so it may not be an issue. Bring the LIST.mbox files as say LIST.mbox/List.mbox.old After you have the files moved, find the PID of ArchRunner via something like ps -fwwC python and kill it with SIGTERM OR SIGINT. Do not use SIGKILL or the master will just restart it. Then do something to the effect of cat LIST.mbox/List.mbox LIST.mbox/List.mbox.old mv LIST.mbox/List.mbox LIST.mbox/List.mbox.new mv LIST.mbox/List.mbox.old LIST.mbox/List.mbox And verify the ownership and permissions on LIST.mbox/List.mbox which now should have all the messages with the new ones at the end. Then copy the ArchRunner command from the previous ps command output and issue that command with sudo -u mailman's_uid and a trailing to restart ArchRunner. If You don't start in in the background, it will remain attached to your terminal and breaking out will SIGINT it and it will die again. Command is like sudo -u mailman /usr/bin/python /var/MM/21/bin/qrunner \ --runner=ArchRunner:0:1 -s Now your mbox is good and new messages are being archived and you can run bin/arch --wipe LIST to build the pipermail archive. This should be OK as bin/arch will lock the archive to prevent conflicts with incoming messages. Way 2. I think this is better. Bring up the new server, start Mailman and immediately stop ArchRunner as above before any new messages arrive, perhaps before starting the MTA. Now you can just bring the LIST.mbox/List.mbox files over and check permissions and rebuild the archives with bin/arch with --wipe or not as the pipermail archive should be empty anyway. Meanwhile lists are running and messages for the archive are queued. Then when the pipermail archives have been rebuilt, start ArchRunner as above. Now there are potentially some cleanup things to do. It is possible, depending on how many posts arrived while ArchRunner was not running, the qfiles/archive directory grew large. This can be a performance issue. See the last paragraph in the FAQ at http://wiki.list.org/x/4030638. You can shrink the queue directory by waiting until it's empty, stopping Mailman, moving the directory aside and recreating it with the same ownership and permissions and restarting Mailman. and if by chance, one or two entries snuck in to the old, moved aside directory, move them individually back to the new directory. Finally, see the script at http://www.msapiro.net/scripts/update_archive_mtime (mirrored at http://fog.ccsf.edu/~msapiro/scripts/update_archive_mtime) if you care about the modification times of the archived message files. Caveat: I just typed this out. I'm *sure* it will work, but I've been wrong before. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org
Re: [Mailman-Users] Moving lists to new server - question on specific files
On 07/18/2014 01:27 PM, Alfred Pope wrote: 1) I'm moving the lists from version 2.1.9 on Solaris 10 to version 2.1.18-1 on Ubuntu. In an older post from Barry (which I cannot find now) he seems to indicate the list configuration files under mailman/lists/listname/ have not changed in these minor releases. He didn't come right out and say it directly but that's what I got from the post. I just wanted to clarify this. Does the format or contents of the list config files change among these minor releases? Yes, there are changes in the list config.pck files, mostly the addition of new attributes, but this is not something you need to worry about when moving a config.pck from an older to a newer MM. Each Mailman installation has an attribute Mailman.Version.DATA_FILE_VERSION and each list has an attribute data_version. Every time a list is instantiated, the list's data_version is compared to the installation's DATA_FILE_VERSION and if it is less, a process is run which knows how to update the list to match the installation, and the list is updated. Thus you don't have to worry when dropping a 2.1.9 config.pck into a 2.1.18-1 installation. The config.pck will be updated as needed automatically. There are possible issues with dropping a newer config.pck into an older installation. In most cases this will result in 'unused' list attributes which does no harm, but if an attribute has been renamed between the older and newer releases, the old name will be missing in this case. This is rare. The only recent case is from_is_list which was called author_is_list only in 2.1.16rc2, so dropping a newer config.pck into a 2.1.16rc2 installation would be a problem. 2) Also concerning the files under mailman/lists/listname/: several different posters say to copy over the entire contents of mailman/lists/listname/ but other posters say the only necessary files to copy are the list config.pck files. It makes sense that if you only copy over these minimal config files, you will loose the pending requests and subscription requests for each list. Loosing the data in pending.pck and request.pck is OK with me as long as it doesn't break the list. The list managers will be alerted in advance to clean up their lists. Also, the current (old) list server contains config.db files for each list in addition to the config.pck files. This is probably due to a previous migration in 2007. I would rather not copy everything under these list directories. I just need the list configuration and membership data. Is copying the minimal config files a safe plan? Copying only the config.pck is a safe plan. The config.db files are left over from Mailman 2.0.x and should not be copied in any case. In fact, they should be removed from the 2.1.9 installation. The reason for this is the data therein is very old, and it is possible that the config.pck files could become corrupted in some way and Mailman would fall back to the extremely outdated config.db. It's better if the config.pck corruption is discovered soon after it occurs. 3) I don't plan on copying over the heldmsg and bounce files under mailman/data/ If the list managers don't clean up their lists before the move they will loose this data. That's OK. I just want to make sure not including those files won't break something down the road. That too is fine. WRT the bounce-events-p.pck files, there normally should be at most one of these (or a few if BounceRunner is sliced) with p equal to the PID of BounceRunner. If there are any with PIDs of non-existent process, they are left behind from some anomalous event, possibly https://bugs.launchpad.net/mailman/+bug/1161610. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org
Re: [Mailman-Users] Moving lists
On Thu, 15 Apr 2010, Mark Sapiro wrote: The steps I sent the other day are OK as is, but some uncertainty is removed. Just to report that, so far as I can tell, everything went as expected. There was no reference to the domain in the config.pck file, so I could just run the withlist command as given. No commands generated any errors or warnings that I could see, and all seems to work just fine (at least on the web interface). Thanks so much for your help with this. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists
Geoff Shang wrote: See attached. I've not yet tried the procedure, so hopefully you'll have looked at it if I run into trouble. Either way I'll give you a blow-by-blow account of how it goes. I have looked at the cPanel 2.1.12cp3 code and made a diff to the 2.1.12 base, and it is surprisingly small. Basically cPanel Mailman is Mailman. In particular, config.pck files are the same (there are no additional list attributes) and the file structure within the /usr/local/cpanel/3rdparty/mailman PREFIX directory seems completely unchanged. As far as I can see, the only significant cPanel changes have to do with listname munging so that lists of the same name can exist in different domains, and most of this appears to be accomplished with their own list creation process and their own Exim router and transport for Mailman lists. I don't have the code for either of these, but it is easy to see how they work. Basically, when cPanel creates a list named listname in the example.com domain, it actually creates a Mailman list named listname_example.com in the example.com domain. The web interface reflects this in that every web URL is of the form http://example.com/mailman/XXX/listname_example.com. Other than that, the web interface is completely standard. Also, with the exception of a minor mod to newlist, and the addition of a --noarchives option to check_perms, the bin/ commands are unchanged and should all work provided the listname_example.com form of the listname is used. The only really significant changes to Mailman itself are mods to the getListAddress() and HasExplicitDest() list methods to account for the fact that the email addresses exposed and used for the listname_example.com list are listn...@example.com, etc. rather than listname_example@example.com. A similar mod is missing from the CalcRecips handler which is why sibling lists have do be defined using the listname_example@example.com address form and work only in a limited way because addresses in To: or Cc: are not of that form. The above, together with some Exim stuff so that mail to the listn...@example.com, etc. addresses is delivered to the listname_example.com list is apparently all there is. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists
On Thu, 15 Apr 2010, Mark Sapiro wrote: Basically cPanel Mailman is Mailman. In particular, config.pck files are the same (there are no additional list attributes) and the file structure within the /usr/local/cpanel/3rdparty/mailman PREFIX directory seems completely unchanged. So does this mean any changes to the instructions you send the other day? Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists
On 4/15/2010 1:35 PM, Geoff Shang wrote: So does this mean any changes to the instructions you send the other day? The steps I sent the other day are OK as is, but some uncertainty is removed. Here are some notes. 1) Create a list the cPanel way on cPanel. it should have the same name as the existing list which I'll call listname, and create it in the appropriate domain which I'll call example.com. This will result in cPanel creating a directory named (I think) /usr/local/cpanel/3rdparty/mailman/lists/listname_example.com/ This directory will contain at least a file named config.pck OK 2) Move the config.pck in step 1) aside and replace it with the lists/listname/config.pck from your server. OK 3) Step 1 should also have created a directory named (I think) /usr/local/cpanel/3rdparty/mailman/archives/private/listname_example.com.mbox/ which I think will be empty. Put the /archives/private/listname.mbox/listname.mbox file from your server in this directory. I'm not sure whether it's name should be listname_example.com.mbox or listname.mbox. In fact I'm not sure of any of the names, but you should be able to adjust them as required by looking at other lists. Also, make sure ownership and permissions are consistent with other lists. The file name will be listname_example.com.mbox, the same as the directory. 4) Here's where it gets tricky. I'm assuming that the command line tools will be in /usr/local/cpanel/3rdparty/mailman/bin/ and that they will work. This assumption may be overly optimistic. Perhaps these next steps should be tested before you begin. They are there and they should work. cd to /usr/local/cpanel/3rdparty/mailman and do bin/dumpdb on the config.pck you moved aside in step 2. Look at the values for the following attributes: host_name real_name web_page_url I expect these will be 'example.com', 'Listname', and 'http://example.com/mailman/' respectively. The real question will be if there is some other list attribute whose value is 'listname_example.com'. I suspect not, but if there is, for discussion let's say its name is xxx. Now we hope withlist works. Do bin/withlist -l listname_example.com Hopefully this will respond Loading list listname_example.com (locked) The variable `m' is the test MailList instance Then at the prompts type m.hostname = 'example.com' m.web_page_url = 'http://example.com/mailman/' or what ever the actual values were from dumpdb. If the value of real_name differed from 'listname' only in case, you don't need to change it. You can change it later if desired in the web UI. If you want to be sure, type m.real_name which will respond with what this was on your host which is probably what is wanted, i.e. something which differs only in case from 'listname'. If there was some xxx attribute with a value 'listname_example.com', type m.xxx = 'listname_example.com' or whatever is appropriate to match the cPanel config.pck. Finally type m.Save() and then control-D at the succeeding prompt and withlist should respond Unlocking (but not saving) list: listname_example.com Finalizing Note that if the only changes required are host_name and web_page_url, you should be able to replace the entire withlist interaction with bin/withlist -l -r fix_url listname -u example.com but that adds another unknown, potentially buggy piece to the process. This entire step should be OK to just do bin/withlist -l -r fix_url listname_example.com -u example.com without worrying about the dumpdb or the interactive withlist. 5) For the archives, you should be able to do bin/arch --wipe listname_example.com Which should work without having to specify the path to the .mbox. but here again we have the problem that cPanel's patches are incomplete and only address those things they expect to be used so the above command may not work. If it fails, you could try bin/arch --wipe listname_example.com path/to/listname.mbox where path/to/listname.mbox is an absolute or relative path to the file you created at step 3. Basically, the whole process is the same as the non cPanel case. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists
On Mon, 12 Apr 2010, Stephen J. Turnbull wrote: It's actually not as bad as it looks. Mark wrote an assembler language level description of where to get the data you'll need, and what to do with it. Oh I'm not particularly daunted by it, especially after rereading it a couple of times. But it's probably daunting for the owner of the small-time hosting company involved. Anyway, the customer has put me in direct contact with him so I'll see what we can get done. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists
Geoff Shang wrote: I have someone moving their lists off our server which runs regular Mailman to a server running Mailman under CPanel. Since it's a Mailman variant, I'm a bit reluctant to just copy stuff en mass over there, not that I'd be installing it anyway. On the other hand, the list has 679 members, 37 of whom are on digest and 46 of whom have delivery disabled (10 by bounce). Also, the configuration is a bit complicated. So I'm not exactly sure how or if I can do anything to aid migration of the list, particularly since there's no way from the web to subscribe a batch of people to digest or to nomail. Any thoughts? This needs to happen in a few days and I need to start telling peple how I'm going to manage this. I will assume the people on the cPanel side have shell access to the server. If not, there's not much that can be done. Based on my limited knowledge of how cPanel does things, I would do the following. Note that I have never done this and it may or may not work. 1) Create a list the cPanel way on cPanel. it should have the same name as the existing list which I'll call listname, and create it in the appropriate domain which I'll call example.com. This will result in cPanel creating a directory named (I think) /usr/local/cpanel/3rdparty/mailman/lists/listname_example.com/ This directory will contain at least a file named config.pck 2) Move the config.pck in step 1) aside and replace it with the lists/listname/config.pck from your server. 3) Step 1 should also have created a directory named (I think) /usr/local/cpanel/3rdparty/mailman/archives/private/listname_example.com.mbox/ which I think will be empty. Put the /archives/private/listname.mbox/listname.mbox file from your server in this directory. I'm not sure whether it's name should be listname_example.com.mbox or listname.mbox. In fact I'm not sure of any of the names, but you should be able to adjust them as required by looking at other lists. Also, make sure ownership and permissions are consistent with other lists. 4) Here's where it gets tricky. I'm assuming that the command line tools will be in /usr/local/cpanel/3rdparty/mailman/bin/ and that they will work. This assumption may be overly optimistic. Perhaps these next steps should be tested before you begin. cd to /usr/local/cpanel/3rdparty/mailman and do bin/dumpdb on the config.pck you moved aside in step 2. Look at the values for the following attributes: host_name real_name web_page_url I expect these will be 'example.com', 'Listname', and 'http://example.com/mailman/' respectively. The real question will be if there is some other list attribute whose value is 'listname_example.com'. I suspect not, but if there is, for discussion let's say its name is xxx. Now we hope withlist works. Do bin/withlist -l listname_example.com Hopefully this will respond Loading list listname_example.com (locked) The variable `m' is the test MailList instance Then at the prompts type m.hostname = 'example.com' m.web_page_url = 'http://example.com/mailman/' or what ever the actual values were from dumpdb. If the value of real_name differed from 'listname' only in case, you don't need to change it. You can change it later if desired in the web UI. If you want to be sure, type m.real_name which will respond with what this was on your host which is probably what is wanted, i.e. something which differs only in case from 'listname'. If there was some xxx attribute with a value 'listname_example.com', type m.xxx = 'listname_example.com' or whatever is appropriate to match the cPanel config.pck. Finally type m.Save() and then control-D at the succeeding prompt and withlist should respond Unlocking (but not saving) list: listname_example.com Finalizing Note that if the only changes required are host_name and web_page_url, you should be able to replace the entire withlist interaction with bin/withlist -l -r fix_url listname -u example.com but that adds another unknown, potentially buggy piece to the process. 5) For the archives, you should be able to do bin/arch --wipe listname_example.com but here again we have the problem that cPanel's patches are incomplete and only address those things they expect to be used so the above command may not work. If it fails, you could try bin/arch --wipe listname_example.com path/to/listname.mbox where path/to/listname.mbox is an absolute or relative path to the file you created at step 3. If possible please report or get a report on how this all goes. Inquiring minds want to know. If you have problems, or if you just want to do the cPanel Mailman user community a favor, get a tarball containing the Mailman/, bin/, cron/ and scripts/ directories from /usr/local/cpanel/3rdparty/mailman/ and send it to me. This contains only code and generic Mailman information except perhaps for Mailman/mm_cfg.py which I would like to see, but which can be anonymized. The purpose of this is to see cPanel's mods to be
Re: [Mailman-Users] Moving lists
On Sun, 11 Apr 2010, Mark Sapiro wrote: I will assume the people on the cPanel side have shell access to the server. If not, there's not much that can be done. Wow, that's quite a daunting list of things to do. I'm not sure the admin at the hosting provider will be game to try this, but I will ask. The amount of work it will save *if* it works will be considerable, particularly given that there are also some members on moderation and some not (which I forgot to mention in my previous message). Thanks for this. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists
Geoff Shang writes: On Sun, 11 Apr 2010, Mark Sapiro wrote: I will assume the people on the cPanel side have shell access to the server. If not, there's not much that can be done. Wow, that's quite a daunting list of things to do. It's actually not as bad as it looks. Mark wrote an assembler language level description of where to get the data you'll need, and what to do with it. I'm not saying it's easy; it will be painstaking work. But a relatively small amount of it! Definitely I encourage you and the new provider to cooperate on this; it is much more likely to get everything right than the obvious alternative manual procedure. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving lists on one box with several virtual hosts
Paul Kleeberg wrote: I have several Mailman lists on one box that has several virtual sites. I need to move them to a new box and I want to change the web address for users to manage their addresses from virtual1.tld to www.virtual1.tld. Looking at both config_list and with_list, I do not see a way to do that. I see how I may assign a domain for the list, but not one that assigns a domain for the web address to the list. What you are missing is the list's hidden web_page_url attribute. See the FAQ at http://wiki.list.org/x/mIA9. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Moving Lists... my final challenge
Jeff Bernier wrote: Is it possible to take these older archives and move them over to be added to the archives of the current lists on the new system? It is not a must-have, but would be nice. Get the archives/private/LISTNAME.mbox/LISTNAME.mbox files from the old server. Stop Mailman on the new server. Combine the old archives/private/LISTNAME.mbox/LISTNAME.mbox files with the new archives/private/LISTNAME.mbox/LISTNAME.mbox files, e.g. cat old.mbox new.mbox tmpfile cp tmpfile new.mbox where old.mbox is the archives/private/LISTNAME.mbox/LISTNAME.mbox from the old server and new.mbox is archives/private/LISTNAME.mbox/LISTNAME.mbox on the current server. Then run bin/arch --wipe LISTNAME to rebuild the pipermail archive on the new server from the archives/private/LISTNAME.mbox/LISTNAME.mbox file. After doing this for each moved list, start Mailman. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving Lists... my final challenge
Thank you Mark, That worked flawlessly. The list members will appreciate seeing all the archive history. Regards, Jeff Mark Sapiro m...@msapiro.net 2/11/2009 12:34 PM Jeff Bernier wrote: Is it possible to take these older archives and move them over to be added to the archives of the current lists on the new system? It is not a must-have, but would be nice. Get the archives/private/LISTNAME.mbox/LISTNAME.mbox files from the old server. Stop Mailman on the new server. Combine the old archives/private/LISTNAME.mbox/LISTNAME.mbox files with the new archives/private/LISTNAME.mbox/LISTNAME.mbox files, e.g. cat old.mbox new.mbox tmpfile cp tmpfile new.mbox where old.mbox is the archives/private/LISTNAME.mbox/LISTNAME.mbox from the old server and new.mbox is archives/private/LISTNAME.mbox/LISTNAME.mbox on the current server. Then run bin/arch --wipe LISTNAME to rebuild the pipermail archive on the new server from the archives/private/LISTNAME.mbox/LISTNAME.mbox file. After doing this for each moved list, start Mailman. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving Lists to New Host
Don McGregor wrote: I'm moving a list manager to a new box, and at the same time bumping up the version of mailman. I copied archives and the lists directory over, installed the 2.1.12rc1 version on top of the old 2.1.9 version. bin/list_lists shows all the old lists when run on the new box. The cgi script listinfo returns no lists for the web page at host/ mailman/listinfo--I get the default welcome page for mailman, no error message, but no mailing lists displayed. Any idea what could cause this? See the FAQ at http://wiki.list.org/x/6oA9 and others linked from it for information about why this is happening. Also see http://wiki.list.org/x/gIA9. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving lists without shell access
Brad Knowles wrote: on 11/18/08 6:36 PM, Scott Race said: Is there a way to move lists from one server to another without shell access? I am able to download the archives from the admin interface, but don't have ssh access Thanks! There's no way to import the archives without using the command-line interface. Not unless you want to re-send those messages to the new mailing list from an external system. Right. Also, if you are retrieving archives via the web, you want to try to retrieve the archival .mbox file (if there is one) rather than the individual, periodic .txt or .txt.gz files. The .mbox has a lot of information (headers) that isn't in the .txt files. Try a url like http://www.example.com/mailman/private/LISTNAME.mbox/LISTNAME.mbox. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving lists without shell access
on 11/18/08 6:36 PM, Scott Race said: Is there a way to move lists from one server to another without shell access? I am able to download the archives from the admin interface, but don't have ssh access Thanks! There's no way to import the archives without using the command-line interface. Not unless you want to re-send those messages to the new mailing list from an external system. The rest of the mailing list configuration may be something you can replicate by putting up one web admin page right next to the other and then doing some cutting and pasting, but it may be a pain-in-the-butt. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving Lists
Jeff Bernier wrote: I have a new server running our new Mailman Lists. I also have an older system containing Mailman lists that I want to migrate to the new server. Is this possible? If so... how is it done? The Mailman FAQ Wizard at http://wiki.list.org/display/DOC/Frequently+Asked+Questions has a wealth of information. In particular, there is one entry entitled How do I move a list to a different server-Mailman installation, which is located at http://wiki.list.org/x/2oA9. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moving Lists
On 5/24/07, carconni wrote: I'm moving postfix's /var/spool to /mounted_file_share/mail/var/spool and I've changed the path in the main.cf file to point to it. Postfix is not designed to be used on a shared filesystem. In fact, most shared filesystems violate some rules that most local filesystems follow, and even if you've only got the one machine that is accessing the data, the simple fact that it's on a shared filesystem will cause problems. In short, I'd avoid this kind of solution like the plague, as far as postfix is concerned. It may be okay to store certain types of user mailboxes out on NFS (or other shared filesystem type), but not the mail queues themselves. Is there anyway to do this with mailman? Can I move /var/mailman to /mounted_file_share/var/mailman and is there a configuration file in /usr/share/mailman that I should modify? In contrast, Mailman is designed to be as NFS-compatible as possible, and so long as the underlying filesystem either operates as a normal local filesystem, or at least follows the same rules that NFS does, then you should be okay. You should be able to move the entire /usr/local/mailman hierarchy out onto NFS, and Mailman should just work -- more or less. There will be certain types of filesystem problems that even Mailman can't solve for you in those kinds of situations, but it will do as much as can be done. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving Lists
On 5/24/07, Brad Knowles wrote: In short, I'd avoid this kind of solution like the plague, as far as postfix is concerned. It may be okay to store certain types of user mailboxes out on NFS (or other shared filesystem type), but not the mail queues themselves. I should also say that most mailbox formats are not safe to store on NFS, or any other kind of typical shared filesystem. If you spend the really big bucks and you get Veritas VxFS (plus all their cluster-aware software) on big honking Sun Solaris servers, then you may be able to store them on a shared filesystem (if you do it right), but at that point I imagine you'd have enough money that you wouldn't need to be coming to us with questions. There are some mailbox formats that are supposedly safe to store on NFS, but even they have some issues and extra baggage that they bring to the table, and which I imagine you are probably not aware of. Of course, most NFS implementations would still leave you with a single-point-of-failure (SPOF), that being your NFS server. The only way to resolve that one is to go with a clustered NFS server solution, such as sold by the folks at Network Appliance. But those things are pretty damn bloody expensive, too. Even so, they're still a lot less expensive than solutions from the likes of EMC or Hitachi Data Systems. Now, if you're talking about a shared filesystem type that is anything but NFS, then you've got a whole 'nother Universe of problems. Yes, I know about GFS from what used to be Sistina (since bought by Red Hat), and I know one of their former senior architects -- he's been my co-author on some of the invited talks I've done, and I've been a technical reviewer of his book. I also know about things like Coda (or AFS), and a wide variety of other distributed filesystem solutions. No, I'm not going to buy any sales pitch regarding how they're the perfect solution for problems like this. If you want a real distributed cluster-aware filesystem for use with mail servers, then you're going to have to pay some real money. It's that simple. Veritas VxFS isn't necessarily the only solution here, but it is one of the best known. There are other alternatives in this space, but they are equally expensive. And no, Veritas VxFS on Linux is not the same as Veritas VxFS on Solaris. Since you're using Mailman on Mac OS X, I should also point out FAQ 1.21 and 1.29 at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.021.htp and http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.029.htp. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving Lists
Brad, Thank you! It sounds like you've saved me a lot of heartache. We have a Netapps that I was hoping to mount on the mail server and was hoping I could avoid losing mail when the mail server ran into problems. It's my understanding that the next version on Leopard will support mail clustering so the solution I was looking for was somewhat temporary. I'll have to give this a lot more thought. On May 24, 2007, at 9:46 PM, Brad Knowles wrote: On 5/24/07, Brad Knowles wrote: In short, I'd avoid this kind of solution like the plague, as far as postfix is concerned. It may be okay to store certain types of user mailboxes out on NFS (or other shared filesystem type), but not the mail queues themselves. I should also say that most mailbox formats are not safe to store on NFS, or any other kind of typical shared filesystem. If you spend the really big bucks and you get Veritas VxFS (plus all their cluster-aware software) on big honking Sun Solaris servers, then you may be able to store them on a shared filesystem (if you do it right), but at that point I imagine you'd have enough money that you wouldn't need to be coming to us with questions. There are some mailbox formats that are supposedly safe to store on NFS, but even they have some issues and extra baggage that they bring to the table, and which I imagine you are probably not aware of. Of course, most NFS implementations would still leave you with a single-point-of-failure (SPOF), that being your NFS server. The only way to resolve that one is to go with a clustered NFS server solution, such as sold by the folks at Network Appliance. But those things are pretty damn bloody expensive, too. Even so, they're still a lot less expensive than solutions from the likes of EMC or Hitachi Data Systems. Now, if you're talking about a shared filesystem type that is anything but NFS, then you've got a whole 'nother Universe of problems. Yes, I know about GFS from what used to be Sistina (since bought by Red Hat), and I know one of their former senior architects -- he's been my co-author on some of the invited talks I've done, and I've been a technical reviewer of his book. I also know about things like Coda (or AFS), and a wide variety of other distributed filesystem solutions. No, I'm not going to buy any sales pitch regarding how they're the perfect solution for problems like this. If you want a real distributed cluster-aware filesystem for use with mail servers, then you're going to have to pay some real money. It's that simple. Veritas VxFS isn't necessarily the only solution here, but it is one of the best known. There are other alternatives in this space, but they are equally expensive. And no, Veritas VxFS on Linux is not the same as Veritas VxFS on Solaris. Since you're using Mailman on Mac OS X, I should also point out FAQ 1.21 and 1.29 at http://www.python.org/cgi-bin/faqw-mm.py? req=showfile=faq01.021.htp and http://www.python.org/cgi-bin/ faqw-mm.py?req=showfile=faq01.029.htp. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving Lists
On 5/24/07, carconni wrote: Thank you! It sounds like you've saved me a lot of heartache. We have a Netapps that I was hoping to mount on the mail server and was hoping I could avoid losing mail when the mail server ran into problems. You can copy stuff up there, as a periodic backup process. I did that kind of thing when I was the Sr. Internet Mail Administrator for Global Network Navigator, which was a joint venture between AOL and O'Reilly Associates, and while it started out as the first major Internet portal, it later became the first nationwide ISP. But don't try to use a mail spool on top of NFS as a live filesystem. It's my understanding that the next version on Leopard will support mail clustering so the solution I was looking for was somewhat temporary. I'll have to give this a lot more thought. Yeah, I don't think I'd really buy that. At best, that's a version 1.0 product from a company that doesn't really understand Enterprise requirements. If you want to know how to properly build or operate a mail cluster, I can point you to slides from invited talks that I've presented at various conferences (see http://www.shub-internet.org/brad/papers/), and consulting work that I've done for large corporations. I'm not currently in a position to officially do more of that kind of consulting now, but I can at least give you some guidance, and may be able to help you find someone who could help you implement that sort of thing. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists
On 1/29/07, G. Armour Van Horn [EMAIL PROTECTED] wrote: So, where do I dig up the membership list, and how do I deal with all the old URLs? FAQ 3.4 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp should help with this. Let us know if you still have issues. -- - Patrick Bogen -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists between virtual domains.
Orlando Reis wrote:
Hi all, athough this question as been posted in the past and I have searched
and searched the mailing list I haven't found a simple a and clear solution
to the problem.
I have my default mailman URL at www.mainhost.com
And have several other vhosts added
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['vhost1.org', vhost1.eu' ,'vhost2.org', '
vhost2.eu','vhost3.eu']
#add virtual hosts
VIRTUAL_HOSTS.clear()
add_virtualhost('www.vhost1.org', 'vhost1.org')
add_virtualhost('www.vhost1.eu','vhost1.eu')
add_virtualhost('www.vhost2.org', 'vhost2.org')
add_virtualhost('www.vhost2.eu','vhost2.eu')
add_virtualhost('www.vhost3.eu','vhost3.eu')
add_virtualhost('www.mainhost.com','mainhost.com')
I have lists on all domains
What I wan't to do is move a list from vhost1.org to vhost1.eu. Is there any
howto on how to do this.
You've answered your own question.
image that i have the following lists: list_all, list_member,
list_workproj1, list_workproj2
If I issue the fix_url command
bin/withlist -l -r fix_url list_all --urlhost=http://www.vhost1.eu
Actually, it should be
bin/withlist -l -r fix_url list_all --urlhost=www.vhost1.eu
That will change the url for the list configuration, but I will also have to
rebuild the archives?
Yes, but the only thing in the archives that is 'wrong' is the link to
the listinfo page from the table of contents page and the periodic
index pages. The table of contents will fix itself when a message is
archived and current and new index pages will too.
You can fix old index pages manually if it's important, or create some
kind of script to do it, or rebuild the entire archive with 'bin/arch
--wipe'.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter 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/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists between virtual domains.
Thanks for you reply mark.
I had little time to do it and that was what I did, after doing that for
each of the lists I wanted to move, I got several errors.
I then remembered, I don't know if that is mandatory, to regenerate
virtual-mailman.db using genaliases commmand.
so the steps I took per mailing list where:
withlist -l -r fix_url listname --urlhost=www.vhost1.eu
bin/arch --wipe listname
and at the end i did genaliases command and did /etc/init.d/mailman restart
And it worked, thanks Mark
On 1/29/07, Mark Sapiro [EMAIL PROTECTED] wrote:
Orlando Reis wrote:
Hi all, athough this question as been posted in the past and I have
searched
and searched the mailing list I haven't found a simple a and clear
solution
to the problem.
I have my default mailman URL at www.mainhost.com
And have several other vhosts added
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['vhost1.org', vhost1.eu' ,'vhost2.org',
'
vhost2.eu','vhost3.eu']
#add virtual hosts
VIRTUAL_HOSTS.clear()
add_virtualhost('www.vhost1.org', 'vhost1.org')
add_virtualhost('www.vhost1.eu','vhost1.eu')
add_virtualhost('www.vhost2.org', 'vhost2.org')
add_virtualhost('www.vhost2.eu','vhost2.eu')
add_virtualhost('www.vhost3.eu','vhost3.eu')
add_virtualhost('www.mainhost.com','mainhost.com')
I have lists on all domains
What I wan't to do is move a list from vhost1.org to vhost1.eu. Is there
any
howto on how to do this.
You've answered your own question.
image that i have the following lists: list_all, list_member,
list_workproj1, list_workproj2
If I issue the fix_url command
bin/withlist -l -r fix_url list_all --urlhost=http://www.vhost1.eu
Actually, it should be
bin/withlist -l -r fix_url list_all --urlhost=www.vhost1.eu
That will change the url for the list configuration, but I will also have
to
rebuild the archives?
Yes, but the only thing in the archives that is 'wrong' is the link to
the listinfo page from the table of contents page and the periodic
index pages. The table of contents will fix itself when a message is
archived and current and new index pages will too.
You can fix old index pages manually if it's important, or create some
kind of script to do it, or rebuild the entire archive with 'bin/arch
--wipe'.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter 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/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists
Patrick, The problem with the old server is that it won't accept mail for Mailman. Something about my last attempt to upgrade Mailman there broke it. I'm putting this function on a new server because I just don't have time to figure out the problem on the old one, and the new one has enough horsepower to run the lists along with its other tasks, thus letting me run one less server. However, the same reason I want to move the list means that I can't use the who password command via mail to get the list. Certainly the data is in a file somewhere. Van Patrick Bogen wrote: On 1/29/07, G. Armour Van Horn [EMAIL PROTECTED] wrote: So, where do I dig up the membership list, and how do I deal with all the old URLs? FAQ 3.4 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp should help with this. Let us know if you still have issues. -- -- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:[EMAIL PROTECTED] For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ --- -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists
A little more digging suggests it may be possible to extract the data with the dumpdb command run against the config.pck. That provides a lot of stuff that isn't needed, like the bounce status of the members which is hardly of interest after the time the server has been offline, but the users and other data seems to all be there. It looks like I could extract the information from that and use the add_members command to add the digest and regular members in two operations, but I probably lose their names and I certainly would lose their passwords. But is there a way to get everything back easily from this data? Van Patrick Bogen wrote: On 1/29/07, G. Armour Van Horn [EMAIL PROTECTED] wrote: So, where do I dig up the membership list, and how do I deal with all the old URLs? FAQ 3.4 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp should help with this. Let us know if you still have issues. -- -- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:[EMAIL PROTECTED] For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ --- -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists
G. Armour Van Horn wrote: The problem with the old server is that it won't accept mail for Mailman. Something about my last attempt to upgrade Mailman there broke it. I'm putting this function on a new server because I just don't have time to figure out the problem on the old one, and the new one has enough horsepower to run the lists along with its other tasks, thus letting me run one less server. However, the same reason I want to move the list means that I can't use the who password command via mail to get the list. Certainly the data is in a file somewhere. FAQ 3.4 is a hodge podge of obsolete and newer stuff. See the two archive posts linked from the second paragraph of the FAQ. Also see http://mail.python.org/pipermail/mailman-users/2007-January/055595.html. Basically, if your old list's are down, all you need to do for lists is move the lists/listname/config.pck files and run fix_url if any domain names changed. For archives, you can move the entire archives/private/ structure, or if you want to rebuild the archives, see the post linked above. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving lists
Mark, Thanks. ../../bin/withlist -l -r fix_url listname worked like a charm. I'm sure there's some cleanup to do, but I'll bet that took care of most of it. Van Mark Sapiro wrote: G. Armour Van Horn wrote: The problem with the old server is that it won't accept mail for Mailman. Something about my last attempt to upgrade Mailman there broke it. I'm putting this function on a new server because I just don't have time to figure out the problem on the old one, and the new one has enough horsepower to run the lists along with its other tasks, thus letting me run one less server. However, the same reason I want to move the list means that I can't use the who password command via mail to get the list. Certainly the data is in a file somewhere. FAQ 3.4 is a hodge podge of obsolete and newer stuff. See the two archive posts linked from the second paragraph of the FAQ. Also see http://mail.python.org/pipermail/mailman-users/2007-January/055595.html. Basically, if your old list's are down, all you need to do for lists is move the lists/listname/config.pck files and run fix_url if any domain names changed. For archives, you can move the entire archives/private/ structure, or if you want to rebuild the archives, see the post linked above. -- -- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:[EMAIL PROTECTED] For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ --- -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] moving lists from one server to another
On Mon, 2005-04-11 at 13:59 -0400, Dave Pisarek wrote: Hello all, I am new to mailman and need to move around 200 lists from one server to another. I am looking for an easy way and fast way to do so. If someone could explain how or point me to good docs on how to do this I would greatly appreciate. You left out some information that would help answer your question: * Do you have shell access to both servers? If so you can copy the files in the mailman var directory. * Will both servers be running the same basic version of mailman? E.g. 2.1 vs. 2.0? If you're upgrading versions at the same time you may need to run bin/update after the data files have been copied. * Will the new server have a new domain? If so, and you have shell access then you'll also have have to run bin/fix_url to change the domain. * You almost certainly have to check the values mm_cfg.py so they match the new server. * If you don't have shell access then I think its going to be very difficult. Don't forget to stop mailman from running before taking a snapshot of the files to copy and give yourself time to test the new installation before you turn your lists back on. -- John Dennis [EMAIL PROTECTED] -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] moving lists from one server to another
On Apr 11, 2005 2:54 PM, John Dennis [EMAIL PROTECTED] wrote: On Mon, 2005-04-11 at 13:59 -0400, Dave Pisarek wrote: Hello all, I am new to mailman and need to move around 200 lists from one server to another. I am looking for an easy way and fast way to do so. If someone could explain how or point me to good docs on how to do this I would greatly appreciate. You left out some information that would help answer your question: * Do you have shell access to both servers? If so you can copy the files in the mailman var directory. * Will both servers be running the same basic version of mailman? E.g. 2.1 vs. 2.0? If you're upgrading versions at the same time you may need to run bin/update after the data files have been copied. * Will the new server have a new domain? If so, and you have shell access then you'll also have have to run bin/fix_url to change the domain. * You almost certainly have to check the values mm_cfg.py so they match the new server. * If you don't have shell access then I think its going to be very difficult. Don't forget to stop mailman from running before taking a snapshot of the files to copy and give yourself time to test the new installation before you turn your lists back on. -- John Dennis [EMAIL PROTECTED] I do have root access to both servers and the new server is 2.1 vs the old 2.0 so you information is very helpful. Thank you very much John -- -- Dave -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] moving lists from one server to another
On Apr 11, 2005 3:19 PM, Dave Pisarek [EMAIL PROTECTED] wrote: On Apr 11, 2005 2:54 PM, John Dennis [EMAIL PROTECTED] wrote: On Mon, 2005-04-11 at 13:59 -0400, Dave Pisarek wrote: Hello all, I am new to mailman and need to move around 200 lists from one server to another. I am looking for an easy way and fast way to do so. If someone could explain how or point me to good docs on how to do this I would greatly appreciate. You left out some information that would help answer your question: * Do you have shell access to both servers? If so you can copy the files in the mailman var directory. * Will both servers be running the same basic version of mailman? E.g. 2.1 vs. 2.0? If you're upgrading versions at the same time you may need to run bin/update after the data files have been copied. * Will the new server have a new domain? If so, and you have shell access then you'll also have have to run bin/fix_url to change the domain. * You almost certainly have to check the values mm_cfg.py so they match the new server. * If you don't have shell access then I think its going to be very difficult. Don't forget to stop mailman from running before taking a snapshot of the files to copy and give yourself time to test the new installation before you turn your lists back on. -- John Dennis [EMAIL PROTECTED] I do have root access to both servers and the new server is 2.1 vs the old 2.0 so you information is very helpful. Thank you very much John -- -- Dave One thing that I do not have is a var directory in mailman. Below is the what I have after I su - mailman bash-2.05$ pwd /usr/mailman bash-2.05$ ls Mailmanarchives cgi-bindata icons locks mail pythonlib scriptstemplates TM bincron htdocs lists logs messages qfiles spam tests Not sure if this helps you but i am a little confused by the var -- -- Dave -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] moving lists from one server to another
On Mon, 2005-04-11 at 15:23 -0400, Dave Pisarek wrote: One thing that I do not have is a var directory in mailman. Below is the what I have after I su - mailman bash-2.05$ pwd /usr/mailman bash-2.05$ ls Mailmanarchives cgi-bindata icons locks mail pythonlib scriptstemplates TM bincron htdocs lists logs messages qfiles spam tests Not sure if this helps you but i am a little confused by the var As typically shipped and installed mailman has two root directories it can install into, prefix and var_prefix. In this instance var mean variable, or where mailman will place its variable data as opposed to its static run time files. Use of var_prefix is optional and depends on how the installation was done initially. Typically what is in var_prefix is archives, data, lists, logs, spam (off the top of my head and thats from a 2.1 perspective, 2.0 is fuzzy these days). It looks like your previous installation didn't separate static runtime files from varible data files. There are two files in the root of the tarball you'll want to read carefully, one is INSTALL, it explains many things and the steps involved. You will also want to read UPGRADING, it will help you go from 2.0 to 2.1. -- John Dennis [EMAIL PROTECTED] -- 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moving Lists between Systems/versions of Mailman
Ken, I recently upgraded and migrated at the same time. However, this was from 2.1.2 to 2.1.3. I turned off external mail/web access to Mailman, confirmed I had no mail left to be processed and then tar'd n' zipped the 2.1.2 installation. I moved and unpacked it on the new box and then ran the 2.1.3 installation process overwriting the 2.1.2 files. All of my lists, subscribers, etc. remained intact and I was able to start using the lists immediately. I would suggest a dry run, but suspect that a similar approach would work from 2.0.13 to 2.1.3. Cheers, n. On Tue, Nov 04, 2003 at 11:08:15PM -0600, Ken Scott wrote: We presently have Mailman v2.0.13 installed, with several lists created. We're going to be moving shortly to a new system, on which I have installed v2.1.3. Can I: (a) copy all appropriate files and aliases, etc., to the new system and have the lists run successfully, without actually having to re-create them? (b) re-create the lists, then copy all appropriate files and aliases, etc., and have them run successfully? If the answer is no to both, what then would be the proper procedure to follow in such a situation? One of these lists alone has several thousand subscribers, so I'd hate for my list owners to have to start over from scratch. Thanks in advance for any help. -- Ken, [EMAIL PROTECTED] -- Nate Perry-Thistle Director of Technology Performance Learning Systems, Inc.http://www.plsweb.com/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
