Jason posted this to the users list, but I think that it raises a
question of concern to the workers. I share several lists, most based on
Majordomo, one run under LISTSERV. Because the owners are scientists
with erratic schedules (field work, etc.), the problem of multiple
approvals is a serious issue. LISTSERV uses just a token, it sends a
message with a header like
Subject: FISH-SCI: approval required (A879DA1A)
and all you have to do is reply with a message saying "OK". It will only
accept one approval for the token A879DA1A of course. But there is a
problem with this. On the lists I run the owner sometimes wants to make
changes before approving -- for example, it is common for someone to
include a long message, signatures and all, at the end of a short but
worthwhile posting. (Since these are my colleagues, I tend to be pretty
lenient abut these matters.) Complex MIME postings with vcards are a
particular bete noir.
I'm not sure what Jason means by "token-based approval", but rather than
the LISTSERV method it would be nice if the method could combine the
best of the two systems. I would suggest something like the following:
The bounce message includes a line like
and when the approval comes back, this token is checked. If this is the
first return, the message is posted as sent back, leaving scope for the
owner to modify it.
>Date: Wed, 28 Oct 1998 14:23:32 -0600
>From: Jason L Tibbitts III <email@example.com>
>Subject: Re: More than one moderator?
>In-reply-to: Thomas Gramstad's message of "Wed, 28 Oct 1998 19:52:33 +0100"
>>>>>> "TG" == Thomas Gramstad <firstname.lastname@example.org> writes:
>TG> Is it possible to have more than one moderator for a moderated
>TG> Majordomo list, and how does that work, technically?
>If works with 1.94.4, but not well. The problem is that there is no way to
>ensure that something is approved only once.
>You could use the MajorCool method; I think that it greatly reduces or
>possibly completely eliminates the possibility of double-approving a
>message. Of course, you then _have_ to do it through Majorcool.
>Majordomo 2 provides token-based approval, so you cannot double-approve a
>message. Mj2 also provides for distributing the workload by randomly
>choosing a set of moderators from a list and sending the approval message
>only to them. This, however, needs more work. (Probably not much more,
>since I already wrote most of it.) If someone is interested in using and
>testing it, then the work will get done much sooner.
>Majordomo2 info (needs updating) at http://www.hpc.uh.edu/majordomo/;
>discussion on email@example.com.
> - J<
Bill Silvert, Habitat Ecology Section, Bedford Institute of Oceanography,
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2, Tel. (902)426-1577