On 21 Aug 1998, Rich Pieri wrote:
> jim barchuk writes:
> > My concern is making it happen as painlessly as possible for the users.
> Believe it or not, the least painful way of doing it is to require all
> subscribers to unsubscribe from the old list and subscribe to the new
There is merit to that, but let me explain what I did about a year ago
with a move of a list of about 400 not very sophisiticated users from
a majordomo system at a remote site to a my local site. While I had the
list password at the remote site, I had no ability to edit passwords at
the other site and had to work with the sysadm there.
(1) Inform users that a move would be happening and that there might be
some disruption, and that they would get more details later on.
(2) Set up the new list locally.
Then in a short space of time
(3) close subscription and unsubscription requests at the old list. All
such requests get passed on to LIST-approval in the ordinary way.
(4) use "who" on old list to duplicate subscribers at new site. And make
sure that the new site list is up and running.
(5) get the postmaster at the remote site set up the following aliases
owner-LIST -> owner-LIST@new.site
LIST-approvel -> LISTfirstname.lastname@example.org
LIST-request -> LISTemail@example.com
LIST -> LIST@new.site
(6) Inform users of the change.
(7) After about 6 months, I put To: and Cc: LIST@old.site in taboo_headers
just so that I would be forced to notice if anyone were still mailing to
the old address.
It should be noted that LIST@old.site was widely publicized, and there are
still some pointers to it left. The combination of the forwarding and
having a list.config at the old site with closed subscription and
unsubscription seems to do the job.
Jeffrey Goldberg +44 (0)1234 750 111 x 2826
Cranfield Computer Centre FAX 751 814
Relativism is the triumph of authority over truth, convention over justice.