In message <9505171017.ZM10237@hpcvusm.cv.hp.com>,
"Sangeeta Agarwal" writes:
>I had a curious question.
>
>If a list owner owns several lists would he have to create different
>listname.passwd files?
>
>If thats the case it seems like an impossible thing to remember all
>the passwds for all the lists.
>
>I would appreciate if I could get a suggestion as to how things are really
>done.
The way I set it up is with three passwords:
1) A password for the majordomo owner. This is what is
contained in the listname.password file. It is not
known to the list managers. It is used with
writeconfig when a new version of majordomo is
installed, or if a list manager isn't bouncing people
fast enough, and the majordomo-owner is getting tired
of seeing the postmaster bounces for one of the lists
etc. It handles both functions 2 and 3 below.
2) A password for list maintainance issues. This is set with
the admin_password keyword in the per list config
file. It is known to the list maintainer for approving
subscriptions/unsubscriptions etc. It can also be used
for approving bounced messages. 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.
-- 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:
|
|
