> Obviously, I am misunderstanding this completely.  It sounds as though you
> (and others) are actually saying that, if I use the Netscape mailer included
> as a feature of the Netscape for sending listowner listserv commands to the
> listserv (TM) running my list, I will have to confirm those listowner listserv
> commands, whether or not I include a password?
 
My guess is that the confirmation requirement was added in LISTSERV
1.8c, which is still in beta testing.  We are running 1.8c beta and
when I sent our LISTSERV a "GET listname (NOLOCK PW=xxxx" command from
Netscape that normally does not require confirmation, I did have to
confirm it, just as others said.  Once I confirmed it, it was executed.
 
I also sent a test message to myself from Netscape on my Macintosh.
The X-Mailer header is what LISTSERV must be using to tell that the
message is from Netscape.  Here's the message.  I marked the X-mailer
header with an arrow.  Mozilla was a code name for Netscape.
 
Received: from CU.NIH.GOV by CU.NIH.GOV (Mailer) id 2634;
              Tue, 15 Oct 96  21:14:34 EDT
Received: from WEB.NIH.GOV by CU.NIH.GOV
    with TCP; Tue, 15 Oct 96 21:14:24 EDT
Received: from 156.40.112.234 by web.nih.gov (8.6.10/1.35(nsb-1.0))
       id VAA19264; Tue, 15 Oct 1996 21:12:37 -0400
Message-ID: <[log in to unmask]>
Date: Tue, 15 Oct 1996 21:13:55 -0400
From: Roger Fajman <[log in to unmask]>
X-Mailer: Mozilla 3.0 (Macintosh; U; PPC)  <----------------------------------
MIME-Version: 1.0
To: [log in to unmask]
Subject: Test 2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
 
test 2