Starting Lyris List Manager
To run Lyris List Manger, you simply type "lyris start" on the command line.
Just plain "lyris" with no command line parameters will display the available options and then exit: it will not run the program.
The "start" action can be modified with a number of options. The options can be anywhere on the command line, in any order. The options are:
Run Lyris List Manager and display debugging information while running.
If you are running Lyris List Manager 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.
On Unix, you can do this by sending a USR1 signal to the Lyris List Manager process, which you can do with the command: kill -USR1 `cat /etc/lyris.pid`
Run Lyris List Manager but do not send any mail.
For example, to start Lyris List Manager in "debug" mode with no outgoing mail, you would use the command:
Run Lyris List Manager with no screen output
Run Lyris List Manager with no Command Protocol service (which runs on port 2020). The web interface will not be able to communicate with the server.
Run Lyris List Manager with Command Protocol tracing on. This feature displays all incoming and outgoing TCP/IP communications on the LCP port. This is very useful for
debugging your LCP scripts.
Run Lyris List Manager but do not run the incoming mail processing service. Incoming mail will not be processed.
Run Lyris List Manager, but do not run the full text indexing service. Messages waiting to be full text indexed will not be indexed.
Run Lyris List Manager, 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 Lyris List Manager installation.
Run Lyris List Manager, but do not run the smtp server which receives mail. No incoming mail will be accepted.
Run Lyris List Manager, but do not run the nntp server which allows Newsgroup access to the mailing lists.
Run Lyris List Manager, but do not run the scheduled task manager. Tasks such as digests will not be run.
Run Lyris List Manager, 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
Lyris List Manager will need to use. Lyris List Manager does this by trying to connect to port 25 (SMTP mail) and port 2020 (LCP) on all TCP/IP addresses of the machine, or just the TCP/IP addresses
Lyris List Manager 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, Lyris List Manager 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.
When you start Lyris List Manager 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
Lyris List Manager SMTP delivery engine is doing.