This is reproducible when the server is up and running, and it applies
to two specific words he used against his list.  I've looked at the
Listserv, Purveyor (WWW) and Operator console logs during occurances of
the error and have seen nothing.  I'm guessing one of the participants
(possibly Purveyor) is hitting some kind of storage limit ONLY when it
gets the results back.  The same session can do (presumably less verbose)
requests normally immediately before and after getting the error.

                                                    -Kary

On 20 Jan 2002, at 13:25, Paul Russell wrote:

> The error had nothing to
>do with your search parms or the size of the archives. The LISTSERV server
>process (lsv) was not running. Consequently, the web interface (wa) could
>not establish a connection to lsv to execute your command. Notify the
>LISTSERV system administrator.
>
>On Fri, 18 Jan 2002 09:33:46 -0500, Tom Rawson <[log in to unmask]> wrote:
>
>>While trying to do an archive search just now I got this:
>>
>>    Error during command authentication
>>
>>    Error - unable to initiate communication with LISTSERV (errno=65535,
>>    phase=RECEIVE, target=149.68.45.24:2306). The server is probably not
>>    started.
>>