On Thu, 10 May 2001, Dan Liston wrote:
> Date: Thu, 10 May 2001 18:46:55 -0500
> From: Dan Liston <dliston@netscape.com>
> To: GARGIULO Eduardo INGDESI <YAPEDU@SIDERAR.COM>
> Cc: majordomo-users@GreatCircle.COM
> Subject: Re: password
>
> The filename needs to be list.passwd.
>
> Check out the list-owner-info file for additional info.
>
> Dan Liston
>
> GARGIULO Eduardo INGDESI wrote:
> >
> > How can I make the password for administrative tasks
> > in a list, like approval subscriptions or something else.
> >
> > I've created a file list.admin and writed a password to
> > that file, but it didn't work.
Here is an edited excerpt from a four year old message:
_________________________________________________________________________
From: Bill.Houle@SanDiegoCA.NCR.COM (Bill Houle)
Date: Sat, 15 Nov 1997 17:34:34 -0800
list.passwd is the old version of where the per-list passwd was kept
before it was added to the config file. It's use is deprecated in favor of
the admin_passwd in the config file. It remains purely for legacy and
migration reasons.
Since "officially" the password is in the config, and there is currently
no way to alter just a single config file keyword, the "passwd" command
itself is bogus and should also be considered legacy. Having both a
list.passwd and the admin_passwd can be a mess. You may just want to
disable (comment out) the support for the command (and alter the docs as
you suggested).
What some site admins have taken to doing out of convenience is to make
the list.passwd file be a site passwd, linking all files together, and
setting it read-only. Thus, a passwd change attempt by a list-owner will
fail.
_________________________________________________________________________
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us
References:
|
|
