LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Paul Hyland <[log in to unmask]>
Tue, 7 Dec 1993 16:41:52 EST
text/plain (33 lines)
Hi,
 
I am faced with the problem of transitioning my BITNET Listserv list to
another list technology on a Unix machine.  FYI, the new list maintenance
software is Unix Listserv, but as I understand it, this doesn't give it any
special status with BITNET listserv, nor make this process any easier.
(Correct me if I am wrong, please).
 
I hope to shut down the VM listserv list I maintain ([log in to unmask]) and
move its subscribers to another list on another machine,
[log in to unmask]  We have already manually moved current subscribers
over, and can change all public notices of the list to reflect the new
address (and any interface changes, etc.).  However, we cannot control files
that are already out there, nor printed lists that contain our soon-to-be old
address, and people will probably continue to subscribe to [log in to unmask]  Is
there any way to "automate" a transition of these users?
 
Two possibilities spring to mind.  1) Is there any way to forward a
subscription request to one list to become a subscription request to the
other list?  (seems exceedingly unlikely); or 2) Is there any way to send a
message to persons that try to subscribe to the former list containing all
the info they need about the new one, so that they will themselves subscribe
to it?
 
I guess the answer to 2) could  be a new welcome message that instead of
welcoming users tells them to go subscribe somewhere else; I guess I was
wondering if there was a way without adding them as subscribers, or even
after taking down (or closing?) the list.
 
Thanks for your help,
 
Paul

ATOM RSS1 RSS2