Oh come on, it's not that hard to understand....
1. Majordomo has 2 addresses per list - listname@ and listname-request@
(and also the generic 'majordomo@' if you use it).
2. In a perfect world, users would know that list commands should go to
listname-request@ and postings go to listname@, but they forget in the
merest inkling of time;
3. Consequently, many users send commands to the listname@ address. If
Majordomo just let this through, the list would be full of spurious
postings and the world would be a worse place.
4. So Majordomo has the 'administrivia' filter, which traps things that
*look like* list commands sent to the posting address and bounces tham
to the owner.
5. The owner then inspects the posting; if it's a real admin command
mis-directed, he/she can either carry out the command on the user's
behalf, or write to them pointing out the error of their ways (or just
bin the whole thing :-). If it's a false-positive (ie the word H*lp or
zubscribe in the middle of a paragraph of text) the owner follows the
'ap*rove' procedure to release the posting to the list.
Recent versions of Majordomo allow the administrivia and taboo filters
to be tuned per-list in the list config file, so you have plenty of
opportunity to take out things that are there or add additional regexps
for your own circumstances. And you can turn it off altogether per-list.
This matching is a little crude of course, which may be what you're
objecting to - but on a busy list with lots of inexperienced
zubscribers, it's worth its weight in gold. The ratio of fase positives
to genuine hits is very low in my experience.
You may see a more intelligent mechanism in a future version of
> From: James D. Stallings[SMTP:email@example.com]
> Reply To: firstname.lastname@example.org
> Sent: 17 August 1997 23:27
> To: Jason L Tibbitts III
> Cc: email@example.com
> Subject: Re: Bouncing Messages.
> > Sure. Just read the config file; the option is 'administrivia'.
> > then
> > your list will see all of those annoying misdirected list commands.
> I found what you were talking about, and have set it to NO, but I do
> understand your message about annoying misdirected list commands. OK,
> understand what you mean. I guess you are in a catch 22 since with
> this. I mean you can not have messages with get, index, subscribe,
> unsubscribe, etc unless you have it set to no, yet misdirected
> will show up.