On 16 Dec 96 at 9:09, Dave Wolfe wrote:
> > we could instead do:
> > approve password
> > subscribe mylist user1@address1
> > subscribe mylist user2@address2
> > which jsmith
> This apparently presumes a global password, otherwise the password may
> only apply to one list for 'which'.
I wasn't presuming that. Password applicability to the "which"
command is a separate issue. My point was simply that "approve
password" before a command should do exactly the same thing as
"approve password" on the same line as the command, for any value of
> Alan's idea of a persistent 'approve password' could be extended to
> 'approve password list', making the password *and* list (which are
> implicitly tied together anyway) persist until the next 'approve'
That is an interesting idea, but that gets into a parsing problem.
That would then require that no lists be named the same as a
majordomo command which can be approved. (Though why someone would
want to name a list the same as a majordomo command is beyond me, but
I worry about these unexpected interactions)
Perhaps another word besides "approve" should be used for this new
> approve password mylist
> configset strip=yes
> configset message_footer << END
> - To unsubscribe from this list...
> subscribe user1@address1
> subscribe user2@address2
Yes, this is a great example.
Alan Millar email@example.com
Owner, System Admin http://www.bolis.com
Ask me about Internet mailing list services at Bolis.com
The skill of accurate perception is called cynicism by those who
don't possess it.