I posted this once before for backing up archives, dbs, and keeping all user info, but it had one small bug. The files in archives/private/* had the wrong permissions set. A small change took care of that. Also, the $person_to_nag_with_700_emails variable doesn't matter if you use the --output argument to bin/newlist. If you are moving to a new machine name, you will also want to set things with config_list - I cannot stress how powerful a tool this can be!
I think this will work for what you want, but of course this didn't fix my mailman woes :(
terminator.sh
Description: Binary data
On Tuesday, November 27, 2001, at 10:28 AM, Phydeaux wrote: > At 07:34 PM 11/26/2001 -0800, you wrote: >> At 21:49 -0500 11/26/2001, Phydeaux wrote: >>> Using bin/list_lists I can get a list of the lists. I can then easily >>> cycle >>> through each list and (for each one) do the following: >>> >>> - Run bin/config_list >>> - Run bin/list_members (once for digested, once for regular members) >>> - Copy the complete archive or at least the mbox file of the archive. >>> >>> I can then tar the whole mess up and copy it to tape, etc. for a >>> portable backup of my mailman installation. >>> >>> I have several questions. First, am I forgetting to copy anything? >>> Will the above approach get me all the data I need to restore the >>> system? >> >> I don't think the above has captured various user flags other than >> digest >> vs regular. >> >> I believe a restore will not restore subscriber choices like not-me-to, >> no-mail, hidden, and some others. > > True... so what is the best way to back things up? I'm loathe to just > back up > the db files, as they can easily be modified while a tar is taking > place. Is that > what everyone else is doing? Is there any facility for dumping user > config > info? I must be missing something... > > reb > > > ------------------------------------------------------ > Mailman-Users maillist - [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users
