[Mailman-Users] 2nd request: migrating a list from 1.1 to 2.1 hosts?
matthew.davis at dogpound.vnet.net
Tue Jan 28 23:44:24 CET 2003
* Tom Neff (tneff at grassyhill.org) wrote:
> There seem to be some other threads capturing people's attention, but Barry
> has logged in and sent mail a couple of times :), so I'm assuming this fell
> through the cracks.
> I have some lists on a host running MM1.1, and a new host running MM2.1. I
> need to move the 1.1 lists over to the new host. Is there a robust way to
> do this?
-[ From mailman-2.1/UPGRADING ]-
UPGRADING FROM 1.x to 2.x
In addition to the instructions above, I highly recommend that you
make sure your Mailman queue is cleared /before/ upgrading.
Mailman version 1.x had a cron script called run_queue which was
part of its bulk mailer. With Mailman 2.x there is no default
bulk mailer (it lets the MTA handle this), and it is currently
unknown what the effects of upgrading are on the run_queue script,
but I'll bet it's not good. :)
The way to make sure that your Mailman queue is empty is to look
in your $prefix/data directory. If you see any files that start
with "mm_q." you've still got messages waiting on the queue. You
can run $prefix/cron/run_queue by hand until the queue is cleared.
Multiple invocations of this script won't help though; they lock
each other out. Also, be warned that clearing the queue can take
a while and may cause a large load on your system (two reasons why
all this stuff has been redesigned in 2.x :).
You do not need to run "make update" if you are upgrading from
version 1.0 or 1.1 to version 2.0, since this is now run
automatically when you do a "make install". However you should
modify your crontab entries to execute cron/qrunner instead of
cron/run_queue. You can also safely remove the file
If you are upgrading from a pre-1.0 beta, you need to follow the
-[ End Section ]-
The rest of the doc is a good read. It's not there just to make the tarball
Where would we be without rhetorical questions?
More information about the Mailman-Users