In message <199505181203.NAA24252@mserv1.dl.ac.uk>,
J.F.L.Hopkinson@dl.ac.uk writes:
>"John P. Rouillard" <rouilj@cs.umb.edu> writes:
>> The way I set it up is with three passwords:
>>
>> 2) A password for list maintainance issues. This is set with
>> the admin_password keyword in the per list config
>> file.
>> ... As has been
>> mentioned before this password can be kept in the
>> .majordomo file for automatic use by the approve
>> script.
>>
>> 3) A password for list submission functions (approving bounced
>> messages). This is set in the per list config file
>> with the approve_password keyword. This can also be
>> put in a .majordomo file for use by approve.
>>
>
>If 2 and 3 both exist, how do you distinguish them in ~/.majordomo ?
You don't. You put the highest numbered password you have access to in
.majordomo. I.E. password 2 works for all password 3 functions.
-- John
John Rouillard
Senior Systems Administrator IDD Information Services
rouilj@dstar.iddis.com Waltham, MA (617) 890-7227 x337
(617) 487-3937 (Direct)
Senior Systems Consultant (SERL Project) University of Massachusetts at Boston
rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480
===============================================================================
My employers don't acknowledge my existence much less my opinions.
References:
|
|
