To start LISTSERV for debugging/testing purposes, first open a CMD.EXE "Command Prompt" (otherwise known as a "DOS box" to us old-timers) in "Run as administrator" mode.  (You will have to right-click the Command Prompt icon and choose that option.)  Next, change to the drive where you have installed LISTSERV, enter CD LISTSERV\MAIN at the prompt, and hit return.

You should now be able to start LISTSERV interactively by entering "LSV START" at the prompt and hitting return.  You will see various startup messages go by and then you will be prompted to enter commands if you wish.  For instance, a SHOW LICENSE command issued from the interactive command line looks like this:

30 Nov 2024 15:19:36 Initialization complete
30 Nov 2024 15:19:36 You can enter commands via the keyboard at any time

Paused - enter a command:
show lic
30 Nov 2024 15:19:40 From LISTSERV@LISTSERV.EXAMPLE.COM: show lic
* License type:      Evaluation
* Expiration date:   31 Dec 2024
* Maintenance until: 31 Dec 2024 (graduated license)
* Capacity:          4 points (0 in use)
* Version:           17.5
* Serial number:     EVAL-NT
* Build date:        20 Nov 2024


You may start the SMTPL.EXE SMTP "listener" service interactively in the same way.

You can run only one copy of LISTSERV at any given time. That is, you cannot start LISTSERV interactively if it is already running as a service, or vice-versa, nor can you start LISTSERV in multiple CMD windows. The same applies to the SMTP listener.

When LISTSERV is installed, it is registered in the Services Manager to start automatically as a system service at boot time.  Thus if you have rebooted your machine after installing LISTSERV, it may already be running.  If it is already running when you attempt to start it in a DOS box, you will get the following error:

C:\LISTSERV\MAIN>lsv start

>>> Unable to create SMTP synchronization events <<<


abnormal program termination


Similarly, if the SMTPL "listener" is already running as a service, you will get something like:

C:\LISTSERV\MAIN>smtpl start

LISTSERV SMTP listener, version 1.1e

Copyright Eric Thomas 1994-2019

>>> Cannot bind to 0.0.0.0, port 25: error 10048

Statistics for this session:

 Physical memory: 8132M (3222M available)

 Paging file:     16260M (10648M free)

 Process memory:  47364k in use

 Connections:     0 (max 0, total 0 in this session)

 Messages:        0 (0 recipients)

 SMTPL uptime:    0 00:00:00 (98.1% CPU utilization)


If the services are running, simply stop them from the Control Panel/Services applet, or just issue the commands

NET STOP LISTSERV

NET STOP LISTSERV-SMTP


in your DOS box before proceeding.

If there are no problems, LISTSERV will start up with messages similar to the following:

C:\LISTSERV\MAIN>lsv start

30 Nov 2024 16:53:18 LISTSERV(R) for Windows version 17.0 starting...

30 Nov 2024 16:53:18  Copyright Eric Thomas 1986-2024

30 Nov 2024 16:53:18 Build date: 20 Nov 2024

30 Nov 2024 16:53:18

30 Nov 2024 16:53:18 SIGNUP files are being compressed...

30 Nov 2024 16:53:18 -> No entry removed.

30 Nov 2024 16:53:18 The network tables are outdated and must be rebuilt.

* Network tables generation process started - be patient...

* Step 1 complete - DBINDEX file generated.

*                   198 NJE nodes, 64 dummy nodes, total 262.

* Step 2 complete - NODESUM3 file generated (7840 bytes).

*                   10 countries, 3 networks, 59 ':internet.' tags,

*                   73 hostnames, total 2411 bytes of Internet<->NJE data.

* Step 3 complete - LINKDEF2 file generated (236 links).

* Step 4 complete - no list/AFD/FUI entry updated for changed node names.

* Step 5 complete - SIGNUP files have been compressed, no entry removed.

30 Nov 2024 16:53:18 The peers tables are being rebuilt...

30 Nov 2024 16:53:19 ->>> No entry for LISTSERV.EXAMPLE.COM in PEERS NAMES.

30 Nov 2024 16:53:19 ->>> Dummy entry generated pending official registration:

30 Nov 2024 16:53:19 ->>> LISTSERV@LISTSERV.EXAMPLE.COM - Backbone=NO, License

number=9999.

30 Nov 2024 16:53:19 -> There are 300 known servers.

30 Nov 2024 16:53:19 File PEERS.DBNAMES has been rebuilt.

30 Nov 2024 16:53:19 File PEERS.DBINDEX has been rebuilt.

30 Nov 2024 16:53:19 File PEERS.NAMESUM has been rebuilt.

30 Nov 2024 16:53:19 File PEERS.DISTSUM2 has been rebuilt.

* Peers tables rebuilt successfully.

30 Nov 2024 16:53:19 Nearest backbone host is LISTSERV@PLUM.EASE.LSOFT.COM

30 Nov 2024 16:53:19 Nearest NJE host is LISTSERV@CUNYVM

* Step 6 complete - link weights file successfully compiled.

*

* Network tables generation completed successfully.

30 Nov 2024 16:53:19 Nearest backbone host is LISTSERV@PLUM.EASE.LSOFT.COM

30 Nov 2024 16:53:19 Nearest NJE host is LISTSERV@CUNYVM

30 Nov 2024 16:53:19 License merged successfully:

> LISTSERV-WINNT-*

>          UNITS=4

>          EXP=31-DEC-2024

>          REL=17.5

>          OPT=EVAL

>          SERIAL=EVAL-NT

>          CKS=1-BFBC2F88-23E6788A

*******************************************************************************

******************************* Evaluation copy *******************************

*******************************************************************************

*                                                                             *

* This  software is  an evaluation  copy,  provided to  you at  no charge  to *

* demonstrate the capabilities  of our product(s). You are  granted a license *

* to use this  evaluation copy until 31  Dec 2024, at which  time the program *

* will automatically  exit with an  error message  every time you  attempt to *

* start it. The reason for this restriction is that we want to make sure that *

* you evaluate the  latest version of the software, and  not an obsolete copy *

* obtained from an outdated distribution.                                     *

*                                                                             *

* LICENSE: Subject  to the  restrictions set  forth below,  you may  use this *

* evaluation copy as you  see fit (and until 31 Dec 2024), as  long as you do *

* not derive a profit from such use.                                          *

*                                                                             *

* RIGHT TO COPY:  You may copy the  software as necessary to use  it, and for *

* backup purposes.  In addition, you  can copy and distribute  the evaluation *

* kit, IN ITS  ENTIRETY, provided that you  do not alter or modify  it in any *

* way, and that  you do not derive  a profit from such  copy or distribution. *

* Our copyright notice  must remain on the original copy  of the software and *

* be included on any copy you make.                                           *

*                                                                             *

* NO RIGHT TO MODIFY: You are not  allowed to modify the software in any way, *

* except for the  interfaces provided with source code, which  you may modify *

* and/or  recompile  for your  own  use.  Any  modified version  remains  our *

* property and subject to the present terms and conditions.                   *

*                                                                             *

* USE AT YOUR OWN RISK: THE SOFTWARE  IS PROVIDED ON AN 'AS IS' BASIS. L-SOFT *

* DOES NOT MAKE  ANY EXPRESS OR IMPLIED WARRANTY OF  ANY KIND WHATSOEVER WITH *

* RESPECT TO  THE SOFTWARE,  INCLUDING, WITHOUT  LIMITATION, ANY  WARRANTY OF *

* MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Neither L-Soft nor any *

* of  its employees,  officers  or  agents will  be  liable  for any  direct, *

* indirect or consequential  damages, even if L-Soft had been  advised of the *

* possibility of such damage.                                                 *

*                                                                             *

* FOR ASSISTANCE  CONTACT: SUPPORT@LSOFT.COM, or  call +1 (301)  731-0440 (or *

* 1-800-399-5449 from the US or Canada).                                      *

*                                                                             *

*******************************************************************************

30 Nov 2024 16:53:19 Sent information mail to LSTMAINT@EXAMPLE.COM

30 Nov 2024 16:53:19 Initialization complete.

30 Nov 2024 16:53:19 You can enter commands via the keyboard at any time.


SMTPL isn't as verbose.  It will start up with only a few messages:

C:\LISTSERV\MAIN>smtpl start

30 Nov 2024 14:39:31 LISTSERV SMTP listener, version 1.1e

30 Nov 2024 14:39:31 Copyright Eric Thomas 1994-2019

30 Nov 2024 14:39:31 Now listening to 0.0.0.0, port 25.

30 Nov 2024 14:39:31 Initialization complete - 200 concurrent threads.


To test the server, send Internet mail to the LISTSERV address with some random command, such as HELP, to check that the SMTP listener and outgoing mail interface are working correctly. Please note that the "LISTSERV address" is the address formed by "LISTSERV@" + the value you defined in the site configuration file for NODE=. For instance, if you defined NODE=LISTSERV.XYZ.COM, the LISTSERV address would be LISTSERV@LISTSERV.XYZ.COM.

DO NOT attempt to create lists or use the WWW interface until the basic email functions (i.e., sending commands to LISTSERV by email and getting a response) are tested and working correctly.

Note that LISTSERV will not see any mail you send it via MAPI unless you have a MAPI/SMTP gateway for your LAN. LISTSERV does not include a MAPI gateway and thus does not support MAPI.

When running as services, LISTSERV and SMTPL both create log files in the \LISTSERV\LOG directory but, for performance reasons, the file buffers are not flushed with each and every write. If you attempt to TYPE the log file, it may appear to be empty. If you wait a few minutes, the buffers will be flushed and you will be able to examine the files. LISTSERV generates "crash reports" when it terminates abnormally, which are sent to the LISTSERV postmasters by default. These "crash reports" normally include a traceback of the error along with the last 100 LISTSERV log entries prior to the crash, and should be sent to L-Soft support for problem resolution. 

In interactive mode, the log files are also created but the file buffers are flushed continuously. Flushing the logs continuously ensures that, in the event of a severe program failure, the logs will always contain information about the cause of the failure. 

(Due to the fact that writing to command windows can significantly slow down an application, interactive mode should be used only when you are trying to troubleshoot a problem.)

Note: While critical errors are reported to the Windows System Event Log and can be examined with Event Viewer (select the Application log), the Windows error codes are almost never useful for debugging problems with LISTSERV.  The LISTSERV console log should be consulted in favor of the event log when a problem arises.

When running as services, both LISTSERV and SMTPL may be stopped from the Control Panel/Services applet, or by issuing the commands NET STOP LISTSERV and NET STOP LISTSERV-SMTP from a DOS prompt.

When running in interactive mode, to stop LISTSERV, simply type STOP. To stop SMTPL, wait until there is no more activity and type Ctrl-C.