In message <199505181203.NAA24252@mserv1.dl.ac.uk>,
>"John P. Rouillard" <email@example.com> 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
>> ... As has been
>> mentioned before this password can be kept in the
>> .majordomo file for automatic use by the approve
>> 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.
Senior Systems Administrator IDD Information Services
firstname.lastname@example.org Waltham, MA (617) 890-7227 x337
(617) 487-3937 (Direct)
Senior Systems Consultant (SERL Project) University of Massachusetts at Boston
email@example.com (preferred) Boston, MA, (617) 287-6480
My employers don't acknowledge my existence much less my opinions.