Starting ListManager

To run Lyris ListManger, change to the directory where you have installed ListManager. Then, run

lm start

or

./lm start

if running Unix.

Just plain "lm" with no command line parameters will display the available options and then exit: it will not run the program.

To save the output to a file, run

lm start 1>lm.log 2>lm2.log

This command will redirect the standard output and the error log to files in your ListManager directory, which may be examined later.

The "start" command can be modified with a number of options. The options can be anywhere on the command line, in any order. The options are:

cfgfile

Run ListManager and specify which configuration file to use. By default, ListManager uses lmcfg.txt to connect to the database.

You can use an alternate configuration file using the cfgfile command-line option. The file to load is specified after the "cfgfile" command-line argument. For example:

lm.exe start cfgfile mycfg.txt

The cfgfile arg can appear anywhere in the command line.

debug

Run ListManager and display debugging information while running.

If you are running ListManager in the foreground, you can toggle debug mode on or off without restarting the server.

On Windows, you can do this by pressing the ctrl-break key.

displaysmtp

Run ListManager, and display all SMTP transactions. This command is run with the debug command:

lm start debug displaysmtp

mailtest

Run ListManager, do not actually deliver any email. It will run completely as normal, but during the SMTP transaction will send a RESET and QUIT command right before it is supposed to send the DATA command. This option can be useful to test the load-capacity and stability of a ListManager installation.

morestats

Running ListManager in morestats mode gives additional information in the Server Statistics page.

nocheck

Run ListManager, but do not check for any TCP/IP conflicts. When it starts up, it first checks to see if any other programs are using the TCP/IP addresses and ports that ListManager will need to use. ListManager does this by trying to connect to port 25 (SMTP mail) and port 2021 (Tclport) on all TCP/IP addresses of the machine, or just the TCP/IP addresses ListManager has been configured to use, if the "Multiple TCP/IP Addresses" setting has been used. If one of the ports it needs is being used, ListManager will display an error message and not load. If you prefer, you can bypass this test with the nocheck option, and it will start a few seconds faster.

noincoming

Run ListManager but do not run the incoming mail processing service. Incoming mail will not be processed.

noindexer

Run ListManager, but do not run the full text indexing service. Messages waiting to be full text indexed will not be indexed.

nomail

Run ListManager but do not send any mail.

For example, to start ListManager in "debug" mode with no outgoing mail, you would use the command:

lm start debug nomail

nonntpserver

Run ListManager, but do not run the nntp server which allows Newsgroup access to the mailing lists.

noscheduler

Run ListManager, but do not run the scheduled task manager. Tasks such as digests will not be run.

noscreen

Run ListManager with no screen output

nosmtpserver

Run ListManager, but do not run the SMTP server which receives mail. No incoming mail will be accepted.

notclport

Run ListManager with no TCLPORT service (which runs on port 2021, by default). The web interface will not be able to communicate with the server.

tclporttrace

Run ListManager so it keeps track of the current state of every tclport thread.

threadtrack

When you start ListManager in the foreground with the "threadtrack" option on the command line, it will keep track of the current state of every SMTP mail thread. You can view the instant status of all mail sending threads from the server statistics page, where this additional information is appended. This can be informative and useful in determining what the ListManager SMTP delivery engine is doing.