MajorCool takes into account the fact that the list.passwd file is both
deprecated and still useful:
1) If the file is non-existent (in the "modern" scenario), then the
list.config password is updated.
2) If the file is read-only (as in Roger's delegated "override"
scenario), then the list.config password is updated.
3) If the file exists and is writable (the deprecated scenario), then
the list.passwd file is updated. In this case, Majordomo gives
precedence to the list.passwd file, not the list.config file.
So back to Sujit... if you want the list.config password to always be
updated, either stop using list.passwd files altogether, or follow the
convention and make them linked/read-only. For MajorCool to do what you
are logically expecting is to break the deprecated Majordomo behavior.
--bill
On Friday, March 5, 2004, at 12:59 PM, Roger B.A. Klorese wrote:
>> ftp://ftp.ccsf.org/majordomo-patches/1.94.5/passwd.1
>
> Bear in mind that this "long deprecated behavior" is a great boon to
> people
> running list servers with delegated administration.
>
> If you maintain the central password in a read-only common file that's
> linked to all of the LISTNAME.passwd files, you can have an "override"
> password that will work no matter what each list owner changes the
> list's
> admin_passwd to.
>
References:
|
|
