LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Peter Rauch <[log in to unmask]>
Thu, 26 Sep 1996 14:14:06 PDT
text/plain (76 lines)
Now that I have your attention, please help me with a listserv configuration
question. Consider it as a volunteer contribution to the Sierra Club....
 
We wish to sometimes set up discussion lists that are moderated/unmoderated
pairs. The moderated list will be for those who "trust" the moderator
to approve all the messages relevant to the topical area of the list
and the unmoderated version will be where _all_ messages get posted,
even those that the moderate rejected on the moderated list, for those
subscribers who do not trust or agree with the Editor's judgement.
 
PROBLEM: How do we configure such list-pairs so as to reduce the work
of the subscriber, of the moderator, and get LISTSERV to do as much of
the dirty work of message management/distribution as possible?
 
SCENARIO:
 
1. Two lists, called: MOD-L and UNMOD-L. The moderator's role on MOD-L
is only to approve or not approve of submitted postings; he is not
permitted to edit the message before posting it to MOD-L.
 
2. A subscriber can subscribe to either (and normally would subscribe
to only one, but that is not a requirement).
 
3. All subscribers to MOD-L are able to send to UNMOD-L by way of the
UNMOD-L keywords SEND= Editor,(MOD-L) and Default-options= Editor
(effectively making all subscribers into self-editors and making
the list unmoderated).
 
4. Subscribers to either list must submit their messages only to
the UNMOD-L list (this is an "ease of use" issue; the subscribers
need only remember one list address).
 
5. The subscriber's message is immediately posted to the UNMOD-L list,
and a copy is sent to MOD-L, as it is proposed to be one of the
subscribers of the UNMOD-L list.  The message "should" go to the
Editor of MOD-L, who will either approve or ignore it. Since the
Editor is not allowed to edit the message, the "OK" style of
approval is desirable (rather than having to deal with "resend-ing"
the message itself.
 
QUESTION:
 
How must these two lists be configured, in detail, related to this goal?
 
The obvious issues are to avoid potential for loops, and to minimize
the work/knowhow of the Editor and subscribers. Obviously, it would be
easy to set these lists up in a way that would force the subscribers to
subscribe to both lists, to send messages to both, or send to the
editor's personal address (!not!) and for the editor to manually
distribute all messages to UNMOD-L and selectively to MOD-L, etc. We
want LISTERV's wide-ranging configurability to work more for us.  But,
the solution has eluded us on "little" points here and there. The
messages approved for MOD-L should appear to be coming from the
original author, not from the other list, nor from the Editor.
Error/informational messages from LISTSERV or form either list should not
initiate a loop by being sent to the other list. Etc. It would be nice
if the informational message from LISTSERV to a subscriber of the
MOD-L list, should a subscriber forget and send a message to MOD-L
instead of to UNMOD-L, says "Please send your message to UNMOD-L"
rather then "You are not allowed to post to the MOD-L list" (remember,
we don't want to create additional work for the Editor of MOD-L by
sending him messages misdirected to MOD-L; MOD-L subscribers can be SET
to NOPOST to accomplish this [I assume that the Editor can approve a
message for a NOPOST subscriber and that the message would get
posted?); that message is not a mailtpl file template, so it appears
that we can't tailor it.
 
I hope the above is a sufficient description. That remains to be seen,
as you submit your suggested solutions and they work but my problem
definition starts to squirm our from under you, as I try to get it
complete and right in the light of your discussion... :>(
 
Got a headache yet? Well, thanks for reading this far. You're on your
way to being a Club volunteer (headaches not required)!
Peter R

ATOM RSS1 RSS2