Re: [Mailman-Users] Migrating and Upgrading

2008-01-04 Thread Dave Warchol
All: I apologize for "noise", I found the answer in the FAQ. % bin/withlist -l -r fix_url listname [options] Thanks again, -Dave >>> "Dave Warchol" <[EMAIL PROTECTED]> 1/4/2008 8:07 AM >>> Mark: First, thanks very much, your approach much easier and faster than mine. I setup a

Re: [Mailman-Users] Migrating and Upgrading

2008-01-04 Thread Dave Warchol
Mark: First, thanks very much, your approach much easier and faster than mine. I setup a testlist on the existing production server (call it server1) and was able to migrate the list and its archvies to a temporary box (call it server2) with a different hostname. However, when I acces

Re: [Mailman-Users] Migrating and Upgrading

2008-01-02 Thread Mark Sapiro
Dave Warchol wrote: > >One method I have considered would be "brute force" (a little labor intensive, >a little heavier on the downtime, but doable): >- dumping the metadata from the old lists (configuration, members, etc.) >- bring the old server down >- bring the new server up with the same nam

[Mailman-Users] Migrating and Upgrading

2008-01-02 Thread Dave Warchol
I need to migrate a very old Red Hat (7.3) mailman 2.0.13 (postfix MTA 1.1.7) installation to a SuSE SLES 10 box running mailman 2.1.7, postfix 2.2.9. I have the new box working in "test mode", temporary name/IP. My goal is to keep the SLES installation "turn key" using the standard packages t