This query concerns something I don't understand about how the "OK" con-
firmation mechanism works.  The (possibly) relevant list keywords for
list THISLIST are:

*  Subscription= Open,confirm
*  Send= Editor,Hold
*  Validate= No
*  Default-Options= Repro,Shorthdr,NoMIME
*  Owner= [log in to unmask] (Dave at work)
*  Owner= quiet:
*  Owner= [log in to unmask] (Ben Chi)
*  Owner= [log in to unmask] (Dave at home)
*  Editor= [log in to unmask] (Dave at work)
*  Editor= [log in to unmask] (Dave at home)
*  Editor= [log in to unmask] (Ben Chi)
*  Editor= (THISLIST)
*
As a (quiet:) owner, I can issue list management commands without LIST-
SERV requiring an OK confirmation (this because VALIDATE= NO).  Dave at
work ([log in to unmask]) is similarly not required to confirm.  But Dave at
home ([log in to unmask]) is not exempt from this requirement -- viz. the
following:
------------------------------------------------------------------------
Date:         Thu, 22 May 1997 13:46:08 -0400
From:         "LISTSERV 1.8c" <[log in to unmask]>
Subject:      Output of your job "dave"
To:           "Dave at home" <[log in to unmask]>

> ok
Confirming:
> set thislist nomail for [log in to unmask]
THISLIST: subscription options updated for [log in to unmask]

One entry updated. One notification has been sent.
------------------------------------------------------------------------
What need I do to eliminate the need for commands from Dave at home to
be "OK"d?  And why does he need to OK but I don't, nor does he at work?
                                             /b