Great Circle Associates Majordomo-Workers
(November 1994)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: more on approval vs owner
From: Dan Simoes <dans @ ans . net>
Date: Wed, 9 Nov 1994 10:59:34 -0500 (EST)
To: majordomo-workers @ greatcircle . com (majordomo-workers)

I've been parsing through majordomo and doing some test runs.
Here's what I've found.  My goal is to have subs/unsubs go to 
user1, and list content approved by user2.

The initial aliases file:

testmod-outgoing:       :include:/home/majordom/lists/testmod
testmod-owner: user1
owner-testmod: user1
testmod-approval: user2
testmod-request: "| /home/majordom/wrapper request-answer testmod"
testmod: "| /home/majordom/wrapper resend -l testmod -h iss.ans.net -f testmod-owner -r testmod -a /home/majordom/lists/testmod.passwd -A -R testmod-outgoing"
Note that resend is being called with a -f flag.

We send a note to the list, and it gets bounced to testmod-owner
for approval.  user1 receives the message and approves it, and off it
goes.

Next test: remove the -f part of resend, rebuild the aliases database,
and send another message.  You would expect that the message gets 
bounced to testmod-approval, right?  Wrong.  testmod-approval (user2)
gets a recording from request-answer, and the message to be 
approved goes off into the bit bucket.

OK, we remove the recording and point testmod-request to testmod-owner.
Next test message...  user1 now receives a bounce message
and can approve it for distribution.  But my original goal of having
user2 approve the messages is lost.

The only functional solution appears to be this:  continue to use
the -f testmod-owner part of resend, and add the moderators to 
the testmod-owner alias.  As I mentioned before, this is not always
desirable, as you will have people who want to manage content but
not sub/unsubs, etc.

I guess I could point testmod-request to testmod-approval.  Then
the approvers would have to deal with other types of sub/unsub
message from people not used to using majordomo.  Sort of 
defeats the purpose.

It therefore does not appear to be possible to separate the two
different functions of a list *owner* and a list *approver*.

Hope this clarifies a bit the problem I'm having.  Comments, 
suggestions are welcome.  After using majordomo for some time, I'd
be tickled if I've stumbled upon something that can make it better
in future versions.

| Dan |
-- 
Dan Simoes			          dans@ans.net
Advanced Network & Services	         (914) 789-5378
100 Clearbrook Road  			Elmsford, NY 10523


Follow-Ups:
Indexed By Date Previous: Re: list-owner and list-approval aliases
From: Dan Simoes <dans@ans.net>
Next: resend && administravia
From: Chan Wilson <cwilson@snarf.engr.sgi.com>
Indexed By Thread Previous: using 'advertise' for more than 'lists' restrictions
From: Chan Wilson <cwilson@snarf.engr.sgi.com>
Next: Re: more on approval vs owner
From: pdc@lunch.engr.sgi.com (Paul Close)

Google
 
Search Internet Search www.greatcircle.com