At 10:45 AM 7/6/95, Brian Hartsfield wrote:
>On Fri, 7 Jul 1995, Mats Wichmann wrote:
>
>> Is there a graceful way to do this? Certainly, mail to the list itself
>> in the form of <listname@oldhost.com> can just be forwarded in the
>> alias file on oldhost, but is there a way to deal with admin stuff
>> gracefully as well? sub/unsub requests, who, etc., which are likely to
>> be occasionally sent to oldhost instead of newhost? It would be nice
>> to do something other than reply that the list is unknown - like give a
>> canned reply that the list has moved to a new location.
>
>Just take each of the alises on the old server and change them to
>
>list:list@newhost
>list-request:list-request@newhost
>list-approval:list-approval@newhost
>
>and so on. That would send all requests to newhost.
Only if the users are sending their requests to "list-request@oldhost", not
if they're sending them to "majordomo@oldhost", as many probably are.
You'd need to hack Majordomo itself to forward those messages pertaining to
the moved list to "majordomo@newhost". But what do you do about
multi-command messages that include stuff relevant to both current lists
and moved lists? It gets messy.
-Brent
----------------------------------------------------------------------
For info about the Internet Security Firewalls Tutorial and a schedule
of upcoming dates, please send email to Tutorial-Info@GreatCircle.COM
----------------------------------------------------------------------
Brent Chapman Great Circle Associates
Brent@GreatCircle.COM 1057 West Dana Street
+1 415 962 0841 Mountain View, CA 94041
Follow-Ups:
-
Re: moving lists
From: "Mats Wichmann (mipsABI Consultant)" <mats@questa.engr.sgi.com>
|
|