In message <199607181728.KAA05521@pau-amma.filoli.com>, David Wolfskill writes:
> (Then again, as of 1.93, I recently found that it's
>possible for a list admin to modify the config to specify "yes" for
>restrict_post... and the degree to which 1.93 tolerates the
>specification of a non-existent file for restrict_post (or, (nearly)
>equivalently, for the -I argument to resend) is rather lower than I
>thought optimal.... I whacked resend to ignore the specification if the
>file specified doesn't exist. I may whack it further to whimper to the
>list-owner that the specification is broken, and is thus being ignored.
In general we do find it a general problem, in providing lists to several
hundred list owners who are mostly not especially computer-literate, that they
find it difficult to work by editing their list config and sending it back to
Majordomo; and they make errors. Hell, they even make errors in the simple
"approve <password> subscribe username@hostname" syntax and then don't even
do anything, when they get an error bounced back for every message going out
to their list.....
A while ago I had proposed the notion of two different tiers, or layers, of
per-list config commands, maybe it's time to mention it again?
Maybe there would be a small file of simple list config options for the
typical novice list owner.... but then there'd be a second config file of
mailto: email@example.com (permanent mailto:firstname.lastname@example.org)
permanent <URL: http://www.pobox.com/~ckk>
*moving to email@example.com, Siemens Corporate Research,
Princeton NJ, in August 1996