LISTSERV keeps logs of all of its activity. On VM systems, this information is kept in the LISTSERV console log. On unix systems, it is kept in
$LSVROOT/listserv.log by default. Note that unix systems create the log by redirection of standard output to a file; see the 'go' script if you are interested in this process.
On VMS and Windows systems, there may be several different logs depending on the configuration of the system. For instance, in addition to the LISTSERV log itself, there will be logs for the SMTP "workers" if this feature is enabled. On Windows systems, there will also be a log for the SMTP "listener" if it is in service. By default, logs under VMS are kept in
LISTSERV_ROOT:[LOG] and logs under Windows are kept in
\LISTSERV\LOG.
While LISTSERV for VM (via WAKEPARM FILE) and Windows "turns" the log at midnight each day, automatically creating daily logs, LISTSERV for VMS and unix does not.
LISTSERV for VMS can "turn" the log via the revision control system if you simply stop and restart LISTSERV once a day (note that you must stop LISTSERV completely and restart it in a new process). This will create files like
LSV_machinename.LOG;1 and
LSV_machinename.LOG;2 in
LISTSERV_ROOT:[LOG] (by default).
LISTSERV for unix creates a single file in the $LSVROOT directory called listserv.log. As this file can get quite long, it will probably be most productive to create a shell script called by a cron job to stop LISTSERV, rename the existing listserv.log and move it to another location (e.g., $LSVROOT/oldlogs), and then restart LISTSERV. L-Soft does not provide shell scripts for this purpose.
On all systems, you will probably want to clean out your old logs on a regular basis. To do this, you will want to write a script that executes automatically (e.g., via WAKEPARM on VM, as a cron job on unix, or as an AT job on Windows). A sample REXXette for use with Windows that keeps the last 5 days' worth of compressed logs and deletes anything older than that follows:
Note: While it is of course possible to simply delete the log file on a daily basis, for the purpose of debugging potential problems this is not recommended.
|
•
|
OpenVMS: LISTSERV_ROOT:[LOG]LSV_machine.LOG;x
|
|
•
|
Unix: ~$LSVROOT/listserv.log
|
|
•
|
Windows: LISTSERV\LOG\LISTSERV-yyyymmdd.LOG
|
Under VM, the console log can be "turned" by placing the appropriate command in the WAKEPARM file. Under Windows NT and 95, LISTSERV automatically "turns" the log at midnight. For OpenVMS, if you reboot daily as explained in Section 10.2
Managing the Logs, the logs are numbered using the revision tracking system, e.g.,
LSV_PEAR.LOG;1,
LSV_PEAR.LOG;2, etc. (if you don't do the daily reboot, LISTSERV just keeps a single log file). For Windows, "
yyyymmdd" is the year, month and day of the log, for example, LISTSERV-19980104.LOG is the log for 4 January 1998. Unix logs are simply the output of the program written to standard output and shell scripts (not provided by L-Soft) can be written to "turn" the logs daily via cron.
25 May 1996 00:00:00 Expiring cookie from xxxxx@ICOM.CA:
> SIGNOFF TECHLINK
25 May 1996 00:00:00 Sent information mail to xxxxx@ICOM.CA
25 May 1996 00:00:00 Expiring cookie from xxxxxxxx@LIGHTSIDE.COM:
> SUBSCRIBE WINNT-L Sxxxx Bxxxxx
25 May 1996 00:00:00 Sent information mail to xxxxxxxx@LIGHTSIDE.COM
25 May 1996 00:00:00 Virtual disk slot E(E:\LISTSERV\ARCHIVES\NISTEP-L) released
.
25 May 1996 00:00:00 Directory E:\EASE\PEACH\LISTS\IATN accessed as virtual disk
slot E.
LISTSERV uses "disk slots" in rotation to minimize the overhead involved in opening a file, performing an operation, closing the file, and then possibly having to reopen the file immediately to perform another operation. A given "disk slot" stays open until it is needed for another file.
25 May 1996 00:00:35 Virtual disk slot E(E:\LISTSERV\ARCHIVES\HONYAKU) released.
25 May 1996 00:00:35 Directory E:\LISTSERV\ARCHIVES\SPAM-L accessed as virtual disk slot E.
25 May 1996 00:00:37 Reindexing SPAM-L LOG9605...
25 May 1996 00:00:37 SPAM-L digest is being distributed...
25 May 1996 00:00:37 Distributing mail ("SPAM-L") from owner-SPAM-L@PEACH.EASE.LSOFT.COM...
25 May 1996 00:00:38 Mail forwarded to H-NET.MSU.EDU for 2 recipients.
25 May 1996 00:00:38 Mail forwarded to UAFSYSB.UARK.EDU for 2 recipients.
25 May 1996 00:00:38 Mail forwarded to LISTMAIL.SUNET.SE for 2 recipients.
The preceding 3 jobs were forwarded to LISTSERV servers on the DISTRIBUTE backbone. The following mail is posted to 45 users who are not served by the DISTRIBUTE backbone in a single BSMTP "envelope".
25 May 1996 00:00:38 Mail posted via SMTP to xxx@AMERICAN.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxx@AOL.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@AOL.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@BCVMS.BC.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@BMACADM.BITNET.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@CLEMSON.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxxxxx@COMPUSERVE.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxx@EMAIL.GC.CUNY.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@ERE.UMONTREAL.CA.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@ETERNA.COM.AU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@GOL.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxx@GPU.SRV.UALBERTA.CA.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@HAWAII.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@IBM.NET.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxx@IDIR.NET.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@INET.UNI-C.DK.
25 May 1996 00:00:38 Mail posted via SMTP to xxx@KSUVM.KSU.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxx@LOC.GOV.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@LOONY-TOONS.TAMU.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@LTRR.ARIZONA.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@MAILBOX.SYR.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxx@MO.NET.
25 May 1996 00:00:38 Mail posted via SMTP to xxxx@MUSICA.MCGILL.CA.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@NANDO.NET.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@NETCOM.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@NYIQ.NET.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@PAMELA.INT.MED.UNIPI.IT.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@PIONEER.STATE.ND.US.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@PSC.LSA.UMICH.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxx@PSUVM.PSU.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@PUCC.PRINCETON.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@SCS.UNR.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@SILVERPLATTER.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@SJUVM.STJOHNS.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@SPCVXA.SPC.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@TELERAMA.LM.COM.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@UA1VM.UA.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@UABDPO.DPO.UAB.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxxx@UCONNVM.UCONN.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@UTARLVM1.UTA.EDU.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@UVVM.UVIC.CA.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxxx@VM1.HQADMIN.DOE.GOV.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxx@VM1.MCGILL.CA.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@VM3090.EGE.EDU.TR.
25 May 1996 00:00:38 Mail posted via SMTP to xxxxxx@WATSON.IBM.COM.
25 May 1996 00:00:44 Sent information mail to xxxxxxxx@CARIARI.UCR.AC.CR
25 May 1996 00:00:45 Sent information mail to xxxxxx@LINUS.DC.LSOFT.COM
25 May 1996 00:00:46 Sent information mail to xxxxx@AF.PENTAGON.MIL
25 May 1996 00:00:46 Sent information mail to xxxxx@ESA.MHS.COMPUSERVE.COM
25 May 1996 00:05:43 Automatic nondelivery report processing for WIN95-L:
25 May 1996 00:05:43 -> All errors temporary, no action taken.
25 May 1996 00:07:34 Automatic nondelivery report processing for EXCEL-G:
25 May 1996 00:07:34 -> 1 monitoring entry updated.
25 May 1996 00:39:23 Processing file 8209289 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:39:25 Processing mail from xxxxxx@PRIMENET.COM for ACCESS-L
25 May 1996 00:39:25 Virtual disk slot E(E:\EASE\PEACH\FTP\EXCEL-L) released.
25 May 1996 00:39:25 Directory E:\EASE\PEACH\FTP\ACCESS-L accessed as virtual disk slot E.
25 May 1996 00:39:26 Distributing mail ("ACCESS-L") from owner-access-l@PEACH.EASE.LSOFT.COM...
25 May 1996 00:39:26 Mail posted via SMTP to xxxxxxxxxxxxxx@NR-COMMS.RADIO.BBC.C
O.UK.
25 May 1996 00:39:26 Mail posted via SMTP to xxxxxxxx@OHS.ORG.
25 May 1996 00:39:26 Mail posted via SMTP to xxxxx@POBOX.COM.
25 May 1996 00:39:26 Done - 1 outbound file (3 rcpts).
25 May 1996 00:39:26 Distributing mail ("ACCESS-L") from owner-access-l@PEACH.EASE.LSOFT.COM...
25 May 1996 00:39:26 Mail forwarded to LISTSERV@HEARN for 4 recipients.
25 May 1996 00:39:27 Mail forwarded to LISTMAIL.SUNET.SE for 11 recipients.
25 May 1996 00:39:27 Mail forwarded to LISTSERV@ICINECA for 4 recipients.
25 May 1996 00:39:27 Mail forwarded to LISTSERV.GMD.DE for 3 recipients.
25 May 1996 00:39:27 Mail forwarded to LISTSERV@AEARN for 2 recipients.
25 May 1996 00:39:27 Processed 192 recipients...
25 May 1996 00:39:27 Done - 5 jobs (24 rcpts), 1 outbound file (192 rcpts).
25 May 1996 00:39:27 Distributing mail ("ACCESS-L") from owner-accessl@PEACH.EASE.LSOFT.COM...
25 May 1996 00:39:27 Mail posted via SMTP to xxxxx@ADC.COM.
25 May 1996 00:39:27 Mail posted via SMTP to xxxxxxx@MSMEL.PRAXA.COM.AU.
25 May 1996 00:39:27 Mail posted via SMTP to xxxxxxx@SPRYNET.COM.
25 May 1996 00:39:27 Done - 1 outbound file (3 rcpts).
25 May 1996 00:39:27 Message DISTRIBUTEd to 222 recipients.
25 May 1996 00:39:28 Sent information mail to xxxxxx@PRIMENET.COM
25 May 1996 00:01:16 From MAILER@PEACH.EASE.LSOFT.COM: X-ADMMAIL OWNER-AFNS
25 May 1996 00:01:16 Processing file 8206153 from MAILER@PEACH.EASE.LSOFT.COM
6 Jun 2000 09:12:42 Automatic nondelivery report processing for AFNS:
6 Jun 2000 09:12:42 -> All errors temporary, no action taken.
This particular type of mail, when sent to the OWNER-listname address, is a delivery error being returned to the RFC 821 MAIL FROM: address. The last two lines of this log excerpt entry simply indicate that auto-deletion is enabled for the list and that in this case the error received was not a permanent one.
26 Jun 2000 09:12:38 From MAILER@PEACH.EASE.LSOFT.COM: X-ADMMAIL TEST-REQUEST JOE.USER@EXAMPLE.COM
26 Jun 2000 09:12:39 Sent information mail to JOE.USER@EXAMPLE.COM
25 May 1996 00:01:16 Processing file 8206155 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:01:16 From LISTSERV@PSUVM.PSU.EDU: X-B64 ID=PANL.MAILDIST CLASS=A
25 May 1996 00:01:16 Rescheduled as: 8206156
25 May 1996 00:01:16 Processing file 8206156 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:01:16 From LISTSERV@PSUVM: DIST2 MAIL I=Y FROM=owner-pan-l@BINGVMB.CC.BINGHAMTON.EDU FORW(CRC) HOST(626 626 (...)
25 May 1996 00:01:17 Distributing mail ("PAN-L") from owner-pan-l@BINGVMB.CC.BINGHAMTON.EDU...
25 May 1996 00:01:17 Mail posted via SMTP to xxxxxxxx@ACS.RYERSON.CA.
25 May 1996 00:01:17 Mail posted via SMTP to xxxxx@AMAIL.AMDAHL.COM.
25 May 1996 00:01:17 Mail posted via SMTP to xxxxxxx@AOL.COM.
25 May 1996 00:01:17 Processing file 8206160 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:01:17 From xxxxxxx@AUSCONSULT.COM.AU: UNSUB EXCEL-L
25 May 1996 00:01:17 Requesting confirmation, cookie=3EB4F2
25 May 1996 00:01:17 Sent information mail to xxxxxxx@AUSCONSULT.COM.AU
25 May 1996 00:04:54 Processing file 8206401 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:54 From LISTSERV@INTERNET.COM: X-B64 ID=X-SUPD.JOB ASCII CLASS=J
25 May 1996 00:04:54 Rescheduled as: 8206402
25 May 1996 00:04:54 Processing file 8206402 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:54 From LISTSERV@INTERNET.COM: DIST2 I=Y FROM=LISTSERV@INTERNET.COM FORW(CRC) HOST(626 626 626 626 626 691 686 (...)
25 May 1996 00:04:54 Distributing file "X-SUPD JOB" from LISTSERV@INTERNET.COM...
25 May 1996 00:04:54 File forwarded to LIME.EASE.LSOFT.COM for 1 recipient.
25 May 1996 00:04:54 File forwarded to WIN95.DC.LSOFT.COM for 1 recipient.
25 May 1996 00:04:54 File forwarded to SPIDER.EASE.LSOFT.COM for 1 recipient.
25 May 1996 00:04:54 File forwarded to HOME.EASE.LSOFT.COM for 1 recipient.
25 May 1996 00:04:54 File forwarded to LISTSERV.GEORGETOWN.EDU for 1 recipient.
25 May 1996 00:04:54 File forwarded to CC1.KULEUVEN.AC.BE for 1 recipient.
25 May 1996 00:04:54 File forwarded to LISTSERV.USHMM.ORG for 1 recipient.
25 May 1996 00:04:54 File forwarded to LISTSERV.CLARK.NET for 1 recipient.
25 May 1996 00:04:54 File "X-SUPD JOB" distributed to LISTSERV@PEACH.EASE.LSOFT.COM.
25 May 1996 00:04:54 Done - 8 jobs (8 rcpts), 1 outbound file (1 rcpt).
25 May 1996 00:04:54 Processing file 8206411 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:54 From LISTSERV@INTERNET.COM: X-SUPD FWD=NO DATE=1996052500:00:04 DATA=5 56 PHOTOPRO 465 PHOTOTECH 268 PHOTOAS (...)
25 May 1996 00:04:08 Processing file 8206361 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:08 From LISTSERV@LISTSERV.UIC.EDU: X-B64 ID=X-LUPD.JOB ASCII CLASS=J
25 May 1996 00:04:08 Rescheduled as: 8206362
25 May 1996 00:04:08 Processing file 8206362 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:08 From LISTSERV@LISTSERV.UIC.EDU: DIST2 I=Y FROM=LISTSERV@LIS
TSERV.UIC.EDU FORW(CRC) HOST(626 626 626 626 626 691 (...)
25 May 1996 00:04:08 Distributing file "X-LUPD JOB" from LISTSERV@LISTSERV.UIC.EDU...
25 May 1996 00:04:08 File forwarded to LIME.EASE.LSOFT.COM for 1 recipient.
25 May 1996 00:04:08 File forwarded to WIN95.DC.LSOFT.COM for 1 recipient.
25 May 1996 00:04:08 File forwarded to SPIDER.EASE.LSOFT.COM for 1 recipient.
25 May 1996 00:04:08 File forwarded to HOME.EASE.LSOFT.COM for 1 recipient.
25 May 1996 00:04:08 File forwarded to LISTSERV.GEORGETOWN.EDU for 1 recipient.
25 May 1996 00:04:08 File forwarded to CC1.KULEUVEN.AC.BE for 1 recipient.
25 May 1996 00:04:08 File forwarded to LISTSERV.USHMM.ORG for 1 recipient.
25 May 1996 00:04:08 File forwarded to LISTSERV.CLARK.NET for 1 recipient.
25 May 1996 00:04:08 File "X-LUPD JOB" distributed to LISTSERV@PEACH.EASE.LSOFT.COM.
25 May 1996 00:04:08 Done - 8 jobs (8 rcpts), 1 outbound file (1 rcpt).
25 May 1996 00:04:08 Processing file 8206371 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:08 From LISTSERV@LISTSERV.UIC.EDU: X-LUPD FWD=NO DATE=1996052423:00:02 HDR=YES
> REP NEWIO-L NEWIO-L /Info about replacing ILLINET Online hardware and software/2616677089
> CKS 3881006631
25 May 1996 00:04:10 GLOBLIST FILE has been successfully updated.
25 May 1996 00:24:11 Processing file 8207550 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:24:11 From LISTSERV@VM1.NODAK.EDU: X-LUPD FWD=NO DATE=1996052423:00:04 HDR=YES
> DEL WLREHAB
> DEL WDAMAGE
> DEL POWER-L
> DEL QUEST
> DEL RS1-L
> DEL SANGEET
> DEL SPRINT-L
> DEL STAFFGOV
> DEL TAG-L
> DEL TELUGU
> DEL THEORY-A
> DEL THEORY-B
> DEL THEORY-C
> DEL THEORYNT
> DEL TOW
> DEL TWSGIS-L
> DEL UND-SEMI
> CKS 3794276653
25 May 1996 00:24:13 GLOBLIST FILE has been successfully updated.
Note: If the "CKS" checksum does not check out, the job is discarded without being processed.
Here is a set of typical log entries for the receipt of a valid "OK" confirmation. Notice that LISTSERV accepts the OK and then issues itself the command that required confirmation. Other than the "OK", this behavior (at least in the log) is identical to how LISTSERV handles commands that do not require confirmation.
225 May 1996 00:04:58 Processing file 8206418 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:04:58 From xxxxxxxxx@SOL.KISS.DE: OK
25 May 1996 00:04:58 From xxxxxxxxx@SOL.KISS.DE: SIGNOFF AFWEEKLY
25 May 1996 00:04:58 To xxxxxxxxx@SOL.KISS.DE: You have been removed from the AFWEEKLY list.
25 May 1996 00:04:58 Sending FAREWELL message to xxxxxxxxx@SOL.KISS.DE
25 May 1996 00:04:58 Sent information mail to xxxxxxxxx@SOL.KISS.DE
25 May 1996 00:04:58 Sent information mail to:
> xxxxxxx@AFSYNC.HQ.AF.MIL xxxxxxx@AFSYNC.HQ.AF.MIL
> xxxxx@AFNEWS.PA.AF.MIL xxxxxx@MASTER.PA.AF.MIL
25 May 1996 00:04:58 Sent information mail to xxxxxxxxx@SOL.KISS.DE
25 May 1996 00:08:50 Processing file 8206772 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:08:50 From xxxxxxxxxx@GENIE.COM: OK 71365E
25 May 1996 00:08:50 From xxxxxxxxxx@GENIE.COM: SUBSCRIBE AFNS Mxxxx Exxx Kxxxxxer
25 May 1996 00:08:51 To xxxxxxxxxx@GENIE.COM: You have been added to the AFNS list.
25 May 1996 00:08:51 Sent information mail to xxxxxxxxxx@GENIE.COM
25 May 1996 00:08:51 Sending WELCOME message to xxxxxxxxxx@GENIE.COM
25 May 1996 00:08:51 Sent information mail to xxxxxxxxxx@GENIE.COM
25 May 1996 00:08:51 Sent information mail to:
> xxxxxxx@AFSYNC.HQ.AF.MIL xxxxxxx@AFSYNC.HQ.AF.MIL
> xxxxx@AFNEWS.PA.AF.MIL xxxxxx@MASTER.PA.AF.MIL
25 May 1996 00:08:51 Sent information mail to xxxxxxxxxx@GENIE.COM
"OK" confirmation codes relate to specific userids. For instance, if you try to execute a command as "someuser@someplace.com" and reply to the "OK" from "someuser@unix1.someplace.com", LISTSERV will not perform so-called "fuzzy matching" or do a DNS lookup to determine whether or not "unix1.someplace.com" maps to "someplace.com". Therefore, since the code and the userid don't match, LISTSERV will respond that the confirmation code does not match any pending job.
25 May 1996 01:16:28 Processing file 8211043 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 01:16:29 From xxxxxx@MSN.COM: ok
25 May 1996 01:16:29 To xxxxxx@MSN.COM: The confirmation code you gave (78B484) does not correspond to any pending (...)
25 May 1996 00:11:42 Processing file 8206935 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:11:42 From xxxxxxxx@NS.NET: SUBSCRIBE IN-TOUCH Txxxxx Hxxxxxx
25 May 1996 00:11:42 To xxxxxxxx@NS.NET: You are already subscribed to the IN-TOUCH list as "Txxxxx Hxxxxxx.
25 May 1996 00:11:42 Sent information mail to therrera@NS.NET
25 May 1996 00:16:18 Processing file 8207278 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:16:18 From xxxxxxx@EROLS.COM: SUBSCRIBE IN-TOUCH Rxxxxxx Sxxx
25 May 1996 00:16:18 To xxxxxxx@EROLS.COM: The name associated with your xxxxxxx@EROLS.COM subscription has been (...)
25 May 1996 00:16:18 Sent information mail to xxxxxxx@EROLS.COM
25 May 1996 00:32:07 Processing file 8207703 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:32:07 From MAILER@PEACH.EASE.LSOFT.COM: X-ADMMAIL OWNER-EXCEL-L Mailer-Daemon@inf.com
25 May 1996 00:32:15 Processing file 8207705 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:32:15 From xxxxxxxx@IX.NETCOM.COM: ok
25 May 1996 00:32:15 From xxxxxxxx@IX.NETCOM.COM: sub WINNT-L Txxxx D.Sxxxx
25 May 1996 00:32:15 To xxxxxxxx@IX.NETCOM.COM: You have been added to the WINNT-L list.
25 May 1996 00:32:15 Sent information mail to xxxxxxxx@IX.NETCOM.COM
25 May 1996 00:32:15 From xxxxxxxx@IX.NETCOM.COM: Txxxx Sxxxx
25 May 1996 00:32:15 To xxxxxxxx@IX.NETCOM.COM: Unknown command - "TXXXX". Try HELP.
25 May 1996 00:32:15 From xxxxxxxx@IX.NETCOM.COM: xxxxxxxx@ix.netcom.com
25 May 1996 00:32:15 To xxxxxxxx@IX.NETCOM.COM: Unknown command - "XXXXXXXX@IX
.NETCOM.COM". Try HELP.
25 May 1996 00:32:15 From xxxxxxxx@IX.NETCOM.COM: http://www.netcom.com/~xxxxxxxx/
25 May 1996 00:32:15 To xxxxxxxx@IX.NETCOM.COM: Unknown command - "HTTP:". Try HELP.
25 May 1996 00:32:15 Sent information mail to xxxxxxxx@IX.NETCOM.COM
25 May 1996 00:36:08 From xxxxxxx@WEBCOM.COM: quiet delete iatnxxxxxx@po.pacific.net.sq pw=xxxxx
25 May 1996 00:36:08 To xxxxxxx@WEBCOM.COM: xxxxxx@PO.PACIFIC.NET.SQ is not subscribed to the IATN list.
25 May 1996 00:36:08 Sent information mail to xxxxxx@WEBCOM.COM
25 May 1996 00:36:42 Processing file 8208564 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:36:43 To xxxxx@IQUEST.NET: The distribution of your message dated Fri, 24 May 1996 23:32:59 -0500 with (...)
25 May 1996 00:36:43 Sent information mail to xxxxx@IQUEST.NET
25 May 1996 00:48:56 Processing file 8210093 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 00:48:57 From LISTSERV@SEARN.SUNET.SE: X-B64 ID=X-FOR.JOB CLASS=M
25 May 1996 00:48:57 Rescheduled as: 8210094
25 May 1996 00:48:57 Processing file 8210094 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 00:48:57 From LISTSERV@SEARN: X-FOR FWDED=2xxxxxxxx@CS.SFU.CA SUBSCRIBE WINNT-L Pxxxxxxxxx Pxxxxxxxx
25 May 1996 00:48:57 Requesting confirmation, cookie=4E79B8
25 May 1996 00:48:57 Sent information mail to xxxxxxxx@CS.SFU.CA
25 May 1996 00:48:57 Sent information mail to xxxxxxxx@CS.SFU.CA
25 May 1996 01:13:25 Processing file 8210957 from MAILER@PEACH.EASE.LSOFT.COM
25 May 1996 01:13:25 From LISTSERV@PSUVM.PSU.EDU: X-B64 ID=X-DEL.JOB CLASS=A
25 May 1996 01:13:25 Rescheduled as: 8210958
25 May 1996 01:13:25 Processing file 8210958 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 01:13:25 From LISTSERV@PSUVM: DIST2 I=Y FROM=LISTSERV@VM1.NODAK.EDU
FORW(CRC) HOST(626 626 626 626 626 626 691 (...)
25 May 1996 01:13:25 Distributing file "X-DEL JOB" from LISTSERV@VM1.NODAK.EDU...
25 May 1996 01:13:25 File forwarded to HOME.EASE.LSOFT.COM for 1 recipient.
25 May 1996 01:13:25 File forwarded to SPIDER.EASE.LSOFT.COM for 1 recipient.
25 May 1996 01:13:25 File forwarded to WIN95.DC.LSOFT.COM for 1 recipient.
25 May 1996 01:13:25 File forwarded to INDIAN.DC.LSOFT.COM for 1 recipient.
25 May 1996 01:13:25 File forwarded to LIME.EASE.LSOFT.COM for 1 recipient.
25 May 1996 01:13:25 File forwarded to LISTSERV.GEORGETOWN.EDU for 1 recipient.
25 May 1996 01:13:25 File forwarded to CC1.KULEUVEN.AC.BE for 1 recipient.
25 May 1996 01:13:26 File forwarded to LISTSERV.USHMM.ORG for 1 recipient.
25 May 1996 01:13:26 File forwarded to LISTSERV.CLARK.NET for 1 recipient.
25 May 1996 01:13:26 File "X-DEL JOB" distributed to LISTSERV@PEACH.EASE.LSOFT.COM.
25 May 1996 01:13:26 Done - 9 jobs (9 rcpts), 1 outbound file (1 rcpt).
25 May 1996 01:13:26 Processing file 8210968 from LISTSERV@PEACH.EASE.LSOFT.COM
25 May 1996 01:13:26 From LISTSERV@VM1.NODAK.EDU: X-FOR xxxx@SDSUMUS.SDSTATE.EDU
SIGNOFF * FWDED=2 (NETWIDE
LISTSERV caches files that it uses for efficiency. Occasionally, you may see a warning that the FIO cache has reached a preset limit (FIOC_WARNING in the site configuration file). See the FIOC_CACHE, FIOC_TRIM, and FIOC_WARNING site configuration variables in the
Site Configuration Keyword Reference document for more information. If you get a lot of these warnings, you may want to consider adjusting the cache values.
25 May 1996 01:24:06 Virtual disk slot E(E:\EASE\PEACH\FTP\VBDATA-L) released.
25 May 1996 01:24:06 Directory E:\LISTSERV\ARCHIVES\SPAM-L accessed as virtual disk slot E.
When LISTSERV receives a request from the 'wa' interface, it logs the activity as below. Note that LISTSERV receives an X-LOGIN command from 'wa' and issues a validation code if the password and the user's e-mail address match. Note also that LISTSERV logs the IP address of the machine making the request via 'wa'.
5 Aug 1997 10:51:08 From IUSR_XXX@PEACH.EASE.LSOFT.COM: X-LOGIN xxxxxx@lsoft.com 206.241.13.58 PW=YYYYYYYY
5 Aug 1997 10:51:08 To IUSR_XXX@PEACH.EASE.LSOFT.COM: ***OK*** 6093C01B81CF68D42B
5 Aug 1997 10:51:09 From IUSR_XXX@PEACH.EASE.LSOFT.COM: X-LOGCK 6093C01B81CF68D42B AUTHINFO(206.241.13.58) WM: LIST OWNED
5 Aug 1997 10:51:21 From IUSR_XXX@PEACH.EASE.LSOFT.COM: X-LOGCK 6093C01B81CF68D42B AUTHINFO(206.241.13.58) OWNER(TEST) WM: GET TEST (HDR NOL (...)
4 Feb 1998 10:26:53 From IUSR_XXX@PEACH.EASE.LSOFT.COM: X-LOGCK 3EA2D501187014BB04 AUTHINFO(204.149.110.125) NOTEBOOK(spam-l) DBS: SEARC (...)
4 Feb 1998 10:26:56 Reindexing SPAM-L LOG9802A...
4 Feb 1998 10:27:08 To IUSR_PEACH@LSOFT.COM: -> 23 matches.
4 Feb 1998 10:27:08 From IUSR_PEACH@LSOFT.COM: X-LOGCK 37BA2700C7AA3AE9EE AUTHINFO(208.141.38.1) WM: SUBSCRIBE WINNT-L Kevin Mc (...)
4 Feb 1998 10:27:08 Requesting confirmation, cookie=1723C284
From time to time a server receives X-SPAM jobs from other LISTSERV hosts. These jobs are "spam alerts" which tell the server that spam has been detected at another site and a user has been put under 48 hour quarantine.
14 Jun 1999 06:48:52 Processing file 41256617 from MAILER@PEACH.EASE.LSOFT.COM
14 Jun 1999 06:48:52 From LISTSERV@PLUM.EASE.LSOFT.COM: X-B64 ID=X-SPAM.JOB ASCII CLASS=J
14 Jun 1999 06:48:52 Rescheduled as: 41256618
14 Jun 1999 06:48:52 Processing file 41256618 from LISTSERV@PEACH.EASE.LSOFT.COM
14 Jun 1999 06:48:52 From LISTSERV@PLUM.EASE.LSOFT.COM: DIST2 I=Y FROM=LISTSERV@LISTSERV.AOL.COM FORW(CRC) HOST(626)
14 Jun 1999 06:48:52 Distributing file "X-SPAM JOB" from LISTSERV@LISTSERV.AOL.COM...
14 Jun 1999 06:48:52 File "X-SPAM JOB" distributed to LISTSERV@PEACH.EASE.LSOFT.COM.
14 Jun 1999 06:48:52 Done - 1 outbound file (1 rcpt).
14 Jun 1999 06:48:52 Processing file 41256619 from LISTSERV@PEACH.EASE.LSOFT.COM
14 Jun 1999 06:48:52 From LISTSERV@LISTSERV.AOL.COM: X-SPAM exxxx_xxxxxxxxx@YAHOO.COM 4214CE9E
14 Jun 1999 06:48:52 -> Registered.
X-TBREG jobs are sent out by all LISTSERV Lite Free Edition servers and any other servers that are set to TABLELESS runmode (see "RUNMODE" in the
Site Configuration Keyword Reference document). These jobs register your server with a central L-Soft server, and are important for two reasons: first, so that your server and lists can show up in the L-Soft-maintained CataList service; and second, so that your server can participate correctly in the LISTSERV distributed server model without needing to update LISTSERV's networking tables on a regular basis.
Non-Free Edition servers set to NETWORKED or STANDALONE runmode do not generate X-TBREG jobs, although they may receive them from remote hosts to be cached for DISTRIBUTE purposes.
Note: LISTSERV Lite Free Edition servers cannot change their runmode and therefore will always self-register this way.
13 Mar 2000 16:45:13 From LVMON@VM.SE.LSOFT.COM: RELEASE
13 Mar 2000 16:45:13 To LVMON@VM.SE.LSOFT.COM: LISTSERV(R) High Performance for Windows NT version 1.8d, managed by:
13 Mar 2000 16:45:13 From LVMON@VM.SE.LSOFT.COM: SHOW
13 Mar 2000 16:45:13 From LVMON@VM.SE.LSOFT.COM: SHOW WWW_ARCHIVE_URL
13 Mar 2000 16:45:13 To LVMON@VM.SE.LSOFT.COM: WWW_ARCHIVE_URL = http://peach.ease.lsoft.com/scripts/wa.exe
13 Mar 2000 16:45:13 From LVMON@VM.SE.LSOFT.COM: SHOW CTR 200003
13 Mar 2000 16:45:13 From LVMON@VM.SE.LSOFT.COM: SHOW CTR 200002
13 Mar 2000 16:45:13 Sent information mail to LVMON@VM.SE.LSOFT.COM
VM.SE.LSOFT.COM is a central L-Soft server that collects publicly-available statistics and other information for the CataList service and for L-Soft's use in developing usage metrics. All of the commands sent by LVMON are documented and can be issued by any user. See also
5.7 of this manual for more information on inter-server information sharing.
In 1.8e, LISTSERV's MIME parser was completely rewritten to address a number of issues, not the least of which were to add uuencoded binary filtering support and anti-virus support. When a MIME message is received by LISTSERV, information about the makeup of the message is logged; for example, here is a message with an RTF file attached which has been sent to a list:
9 Nov 2001 10:26:52 Processing file 0118 from MAILER@LISTSERV.EXAMPLE.COM
Part 1 [1-243]: MULTIPART/MIXED; parent=0; boundary="--=====================_480
189806==_"
Part 2 [1-6]: TEXT/PLAIN; parent=1; boundary=""
Part 3 [7-235]: APPLICATION/RTF; parent=1; boundary=""
Parts: 3 skipped: 0
9 Nov 2001 10:31:44 Processing file 0121 from MAILER@LISTSERV.EXAMPLE.COM
Part 1 [1-235]: MULTIPART/MIXED; parent=0; boundary="--=====================_480
480784==_"
Part 2 [1-5]: TEXT/PLAIN; parent=1; boundary=""
Part 3 [6-234]: APPLICATION/RTF; parent=1; boundary=""
Parts: 3 skipped: 0
Rewriting part 2
9 Nov 2001 10:31:44 -> Decoding MIME message parts...
9 Nov 2001 10:31:44 Rescheduled as: 0122
9 Nov 2001 10:31:44 Processing file 0122 from LISTSERV@LISTSERV.EXAMPLE.COM
Part 1 [1-1]: TEXT/PLAIN; parent=0; boundary=""
Parts: 1 skipped: 0
9 Nov 2001 10:31:44 From ncb@EXAMPLE.COM: show lic
9 Nov 2001 10:31:44 Sent information mail to ncb@EXAMPLE.COM
In this latter message, LISTSERV sees the three MIME parts of the message and skips them all, passing the message to the MIME parser. LISTSERV then rewrites the second MIME part (the TEXT/PLAIN attachment that actually contains the command(s) to be executed) and places a new job containing only the TEXT/PLAIN attachment in the spool, which is then executed by the command processor. The APPLICATION/RTF attachment is simply discarded.
Finally, here is an example of a subscription request received from a site running an InterScan VirusWall gateway, which wraps the original message in a special MIME wrapper. The actual "raw" message as received by LISTSERV looks like this:
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="------------InterScan_NT_MIME_Boundary"
Subject:
Date: Mon, 26 Nov 2001 14:51:18 -0800
Message-ID: <66C896FC5FA3EB4E9BC85569962F378403BCC430@example.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Index: AcF2zNx1xlGA3wa1RES/vvt+eFWNGw==
From: "Joe User" <joe@example.com>
To: <LISTSERV@LISTSERV.EXAMPLE.COM>
Return-Path: joe@example.com
X-OriginalArrivalTime: 26 Nov 2001 22:51:19.0067 (UTC)
FILETIME=[DCAAC6B0:01C176CC]
--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C176CC.DC8A9762"
------_=_NextPart_001_01C176CC.DC8A9762
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_001_01C176CC.DC8A9762
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
SUBSCRIBE TEST Joe = User
=00
------_=_NextPart_001_01C176CC.DC8A9762--
Versions of LISTSERV previous to 1.8e were unable to parse any text out of this type of message, but from version 1.8e forward the MIME parser is able to find the plain text attachment and execute it:
27 Nov 2001 10:13:01 Processing file 0083 from MAILER@LISTSERV.EXAMPLE.COM
Part 1 [1-24]: MULTIPART/MIXED; parent=0; boundary="--------------InterScan_NT_MIME_Boundary"
Part 2 [3-0]: MULTIPART/ALTERNATIVE; parent=1; boundary="------_=_NextPart_001_01C176CC.DC8A9762"
Part 3 [7-14]: TEXT/PLAIN; parent=2; boundary=""
Part 4 [15-21]: TEXT/HTML; parent=2; boundary=""
Parts: 4 skipped: 0
Rewriting part 3
27 Nov 2001 10:13:01 -> Decoding MIME message parts...
27 Nov 2001 10:13:01 Rescheduled as: 0084
XMV.finalrc: 3
27 Nov 2001 10:13:01 Processing file 0084 from LISTSERV@LISTSERV.EXAMPLE.COM
Part 1 [1-1]: TEXT/PLAIN; parent=0; boundary=""
Parts: 1 skipped: 0
27 Nov 2001 10:13:01 From joe@EXAMPLE.COM: SUBSCRIBE TEST Joe User
27 Nov 2001 10:13:01 Sent information mail to joe@EXAMPLE.COM
27 Nov 2001 10:13:01 Sending WELCOME message to joe@EXAMPLE.COM
27 Nov 2001 10:13:01 Sent information mail to joe@EXAMPLE.COM
5 Dec 2001 17:31:07 -> Rejected:
* Your posting to the TEST list has been rejected by the content filter. OOO
* messages are not allowed on this list.
5 Dec 2001 17:31:07 Sent information mail to ncb@EXAMPLE.COM
These logs are for the SMTPL.EXE "listener" service, and are called SMTP-yyyymmdd.LOG.
1 They are found in the /LISTSERV/LOG directory with the other LISTSERV system logs. A typical "listener" log looks like this:
This log simply keeps track of incoming SMTP connections to your server. It adds an entry for each new connection as it opens and closes. Additionally, if a connection is closed abnormally (e.g., by the remote host before any data is sent), the condition is logged. The SMTP log is generally useful only for debugging the SMTP listener, although it may also be of use in debugging problems with specific remote hosts.
|
•
|
OpenVMS: LISTSERV_ROOT:[LOG]SMTPSn-yyyymmdd.LOG
|
|
•
|
Windows: LISTSERV\LOG\SMTPSn-yyyymmdd.LOG
|
(LISTSERV automatically "turns" the OpenVMS and Windows SMTPS logs at midnight. "
yyyymmdd" is the year, month and day of the log, for example,
LISTSERV-19980104.LOG is the log for 4 January 1998; "
n" refers to the worker that is generating the log. Each worker generates a log, so if you have 10 workers running, you will have logs for
SMTPS1 through
SMTPS10.)
The SMTP worker logs keep track of events that occur while the SMTP workers are delivering mail to the external mail host(s) defined in the SMTP_FORWARD_n variables in the site configuration file. In general, the events logged will be errors of one kind or another. For instance, the first error in the example above indicates an SMTP error, and the second indicates that a file that caused an error has been renamed so that it can be examined for debugging.
The last three errors are normal and can generally be ignored. They refer to the fact that two workers have noticed a .MAIL file that exists in the queue, and that one of them grabbed it before the other one did. The first worker locks the file and the second worker is denied permission to open it. Sometimes the first worker may process the mail so quickly that the error will read "File not found" rather than "Permission denied"; either way, this should not be considered alarming unless mail is actually not being delivered.
This feature is available to track certain operations on lists with "Change-Log= Yes" coded into their headers. As noted elsewhere in this manual, setting the keyword to "Yes" causes LISTSERV to write a file called
listname.CHANGELOG (or
listname CHANGELG for VM) into LISTSERV's A directory or A disk. CHANGELOG files are automatically available for list owners and site maintainers to
GET and
PUT (
PUT normally being used to delete them) like any other file. It is not necessary to make catalog entries for CHANGELOG files.
It is also possible to define change-logs for regular mailing lists that rotate on a regular basis, either DAILY, WEEKLY, MONTHLY, or YEARLY. (The option SINGLE is provided for backward compatibility and is still the default, that is, LISTSERV does not ever rotate the change-log). The rotation periods are specified as a second parameter to the Change-Log= list header keyword, for example:
(the latter being equivalent to "Change-Log= Yes" as noted above). Rotated change-logs are renamed with the format
listname.CHANGELOG-yyyy[mm[dd|w]] (depending on the rotation period selected) and may be retrieved with the GET command as usual.
Documented Restriction: NOLIST-* change-logs are always SINGLE. In addition, Change-Log rotation is not available under VM.
The operations monitored are ADD,
AUTODEL,
BOUNCE,
CHANGE,
DELETE,
POST,
READD,
RESUBSCRIBE,
SET,
SIGNOFF, and
SUBSCRIBE. All abbreviations and synonyms are translated to their "official" forms, i.e.,
SUB,
JOIN, and
SIGNON are all translated to
SUBSCRIBE for the purposes of the changelog. This makes it easy to write scripts to come up with statistics for a given list--you don't have to take variations of the commands into account.
20011025100330 ADD xxxxxxx@JPS.NET Lxxxx Pxxxxxxxx
20011025120049 AUTODEL xxxxxxxx@EISA.NET.AU
20011025131221 BOUNCE xxxxxxxx@NONEXIST.COM
20011025214433 CHANGE xxxx@MCS.COM txxx@MCS.NET
20011025214434 DELETE xxxxx@SINGNET.COM.SG
20011025060052 EXPIRE joe@EXAMPLE.COM
20011025232441 POST xxxxxxxx@M4.SPRYNET.COM Printer Drivers
20011025000400 RESUBSCRIBE xxxx@MAIL.MECHWART.MUMSZKI.HU MxxxxxZxxxxx
20011025113947 SET xxxxxx.xxxxxxx@WDC.COM REPRO
20011025082712 SIGNOFF xxxxxxxx@STARNET.NET.AR
20011025085642 SUBSCRIBE xxxxxxxx@LYCOSMAIL.COM Kxx Wxxxxxx
As you see, the SET entry tells you what options were set, and the
POST entry tells you what the subject of the posting was.
RESUBSCRIBE is a
SUBSCRIBE operation that takes place when the user is already subscribed to the list, for example, to change the real name field in the user's subscription.
BOUNCE is a special operation that takes place when using the "no-list" bounce-processing mechanism (described in the
Advanced Topics Guide for LISTSERV).
EXPIRE indicates that the renewal "grace period" for the subscriber in question has expired without the user sending a
CONFIRM command and the user has been deleted from the list. Otherwise these entries are fairly self-explanatory.
This type of record shows the basic results of an ADD IMPORT job. The numbers following the
IMPORT recordtype stand for (1) recipients added, (2) entries changed, and (3) recipients forwarded to another host, in other words, the same results that are sent back to the
ADD IMPORT invoker on completion of the job.
This tells you how many subscribers existed on the list before this particular change-log was started. It is handy to know if you are trying to track historical subscription count trends.
Note: Even with the changelog rotation feature active, changelog files can get very large. It may be necessary to monitor the size of the changelogs on your server and delete them as disk space fills up. If a list owner wants the changelog information for his list, he should be instructed that it is his responsibility to
GET old changelog files regularly and delete them himself each time. There is no facility in LISTSERV to delete the rotated changelog files automatically.
While LISTSERV does not provide a native method to display statistics, it is entirely possible to use scripts to post-process the LISTSERV console logs and changelogs to provide a wide range of statistics. Additionally, the native SHOW CTR command provides a breakdown of current and past LISTSERV traffic.
There are two unsupported REXX scripts available from L-Soft which can be used to extract various statistics from the LISTSERV console log and from changelogs. See
Note: These scripts are completely unsupported. Neither the script author nor the L-Soft support department is able to field support requests for unsupported scripts.
The second script is designed to be run against a listname.CHANGELOG file and produces a report similar to the old VM STATS command output (addresses have been changed to protect the innocent). There are two options--TOP (which produces posting information for only the top x number of posters--by default this is 20, the value can be raised or lowered by changing the variable setting in the code), and NOP (which suppresses the individual posting data altogether). If neither the TOP or NOP options are specified, individual posting data are produced for each and every address that posted to the list during the period represented by the changelog, which has the potential to produce very long reports. It is probably best to run this script with redirection to a file.
C:\rexx>rexx stats.rexx access-l top
Statistics for ACCESS-L from 25 Jun 1998 through 10 Mar 2000 (625 days)
Total lines processed: 27495
Total subscribers on list at start of period: 1465
Total subscribers on list at end of period: 2623
Increase: +1158
Total units Units/day
=========== =========
ADD operations: 0 0.0000
AUTODEL operations: 1147 1.8352
BOUNCE operations: 0 0.0000
CHANGE operations: 153 0.2448
DELETE operations: 182 0.2912
IMPORT operations: 2 0.0013
Recipients added: 0 0.0000
Entries changed: 2 0.0013
Forwarded: 0 0.0000
POST operations: 16758 26.8128
READD operations: 0 0.0000
RESUBSCRIBE operations: 45 0.0720
SET operations (total): 2733 4.3728
ACK: 29 0.0464
NOACK: 240 0.3840
MSGACK: 0 0.0000
CONCEAL: 108 0.1728
NOCONCEAL: 4 0.0064
FILES: 2 0.0032
NOFILES: 1 0.0016
MAIL: 344 0.5504
NOMAIL: 688 1.1008
DIGESTS: 1162 1.8592
NODIGESTS: 160 0.2560
INDEX: 114 0.1824
NOINDEX: 5 0.0080
REPRO: 207 0.3312
NOREPRO: 97 0.1552
MIME: 78 0.1248
NOMIME: 274 0.4384
HTML: 213 0.3408
NOHTML: 79 0.1264
TOPICS: 0 0.0000
FULLHDR: 13 0.0208
SHORTHDR: 31 0.0496
DUALHDR: 5 0.0080
IETFHDR: 4 0.0064
SUBJECTHDR: 69 0.1104
FULL822: 0 0.0000
SHORT822: 0 0.0000
SIGNOFF operations: 2568 4.1088
SUBSCRIBE operations: 3908 6.2528
Ratio of SIGNOFF operations to SUBSCRIBE operations: 0.6571:1
Total
Top 20 posters Units Units/day Units/mon(*)
================================================ ===== ========= =========
Gxxxxx.Wxxxxx@xxxxxxxxxxx.xx.xx 19 3.1667 0.6333
dxxxxxx@xxx.xxx.xx 18 3.0000 0.6000
dxx.exxxxxx@xx.xxxxxxx.xx.xx 11 1.8333 0.3667
fxxxxxxx@xx.xxx 11 1.8333 0.3667
mxxxxx@xxxxxxxxx.xxx 8 1.3333 0.2667
cxxxxxxx@xxxxxx.xxx 8 1.3333 0.2667
Hxxxxxxx@xxxxxx.xxx 7 1.1667 0.2333
mxx@xxxxxxxxxxxxxx.xxx 7 1.1667 0.2333
dxxxxx.xxxxxxx@xxx-xxx.xx 7 1.1667 0.2333
dxxxxxx@xxxxxxxxxxxx.xxx 7 1.1667 0.2333
jxxxx@xxxxxxxxx.xxx 7 1.1667 0.2333
kxxxxxxxx@xxxxx.xxx 6 1.0000 0.2000
nxxxx_x@xxx.xxx 6 1.0000 0.2000
Pxxxxxx@xxxx.xxx 5 0.8333 0.1667
G.F.G.Wxxxxxxxx@xx.xxxxxxxx.xx 4 0.6667 0.1333
Nxxxxxxx.Vxx@xxx.xxxxx.xx.xx 4 0.6667 0.1333
axxxxxxx@xxxxxxxx.xxx.xxx 4 0.6667 0.1333
kxxxxxx@xxxxxxx.xx.xx 4 0.6667 0.1333
txxxx.x.x@xx.xxx 4 0.6667 0.1333
xxxxxx@xxxxxxx.xxx.xx 3 0.5000 0.1000
Top 20 posters Last posted
================================================ ===========
Gxxxxx.Wxxxxx@xxxxxxxxxxx.xx.xx 13-Jan-1999
dxxxxxx@xxx.xxx.xx 12-Jan-1999
dxx.exxxxxx@xx.xxxxxxx.xx.xx 12-Jan-1999
fxxxxxxx@xx.xxx 13-Jan-1999
mxxxxx@xxxxxxxxx.xxx 09-Jan-1999
cxxxxxxx@xxxxxx.xxx 13-Jan-1999
Hxxxxxxx@xxxxxx.xxx 13-Jan-1999
mxx@xxxxxxxxxxxxxx.xxx 12-Jan-1999
dxxxxx.xxxxxxx@xxx-xxx.xx 13-Jan-1999
dxxxxxx@xxxxxxxxxxxx.xxx 13-Jan-1999
jxxxx@xxxxxxxxx.xxx 13-Jan-1999
kxxxxxxxx@xxxxx.xxx 12-Jan-1999
nxxxx_x@xxx.xxx 09-Jan-1999
Pxxxxxx@xxxx.xxx 11-Jan-1999
G.F.G.Wxxxxxxxx@xx.xxxxxxxx.xx 13-Jan-1999
Nxxxxxxx.Vxx@xxx.xxxxx.xx.xx 13-Jan-1999
axxxxxxx@xxxxxxxx.xxx.xxx 10-Jan-1999
kxxxxxx@xxxxxxx.xx.xx 13-Jan-1999
txxxx.x.x@xx.xxx 13-Jan-1999
xxxxxx@xxxxxxx.xxx.xx 11-Jan-1999
Note: These scripts are not supported in any way by L-Soft, and your use of them is strictly at your own risk.
LISTSERV provides certain raw statistics in response to the command SHOW CTR yyyymm (where "
yyyymm" is the year and month for which you are requesting statistics). For instance,
SHOW CTR 200110 sent to one of L-Soft's hosting servers produces the following:
>SHOW CTR 200110
200110 1 0 102276 14829079 9414 351624 1686 5525 218474 189356 125315 29161
245922 59850 11234881 0 1654503 21893 40050348 302198 112853 63348 4373
291703 134 73552 END EOD
Unfortunately this is fairly obscure (it was originally intended to be used only by LISTSERV to compile network-wide statistics) and requires a certain amount of interpretation. The fields signify, in order:
|
•
|
END (tells LISTSERV that this is the end of the regular data)
|
|
•
|
EOD (tells LISTSERV that this is the end of the report)
|
XPOL
integer_value
integer_value
>SHOW CTR 200508
200508 1 0 6151 6704302 1300 223483 704 9003 34593 17229 23136 17628 74524
64977 348776 0 266059 60477 26257717 302407 68659 24196 97223 754088 2614
39464990 0 0 0 0 0 END XPOL 744 227 EOD
If enabled (see the Site Configuration Keyword Reference document, SYSTEM_CHANGELOG) a file called
system.changelog (
SYSTEM CHANGELG under VM) is generated in LISTSERV's A directory (A disk under VM), containing records of the following sort:
20000605014426 MAIL-MERGE 1 0 1,MM1,owner-XYZ@GUAVA.EASE.LSOFT.COM,Re: Whatever
20000803010016 MAIL 22544 8304 21,MYLIST-L,LISTSERV@GUAVA.EASE.LSOFT.COM,owner-
mylist-l@GUAVA.EASE.LSOFT.COM,How now brown cow?
20000804134805 DIST-NJE 1 0 1,X-SPAM.JOB,LISTSERV@PLUM.EASE.LSOFT.COM,LISTSERV@
LISTSERV.EXAMPLE.COM
20000804190101 DIST-NJE 1 0 1,Netwide_SIGNOFF,LISTSERV@PLUM.EASE.LSOFT.COM,LIST
SERV@LISTSERV.EXAMPLE.COM
20000804230002 DIST-NJE 0 119 1,SUPD,LISTSERV@GUAVA.EASE.LSOFT.COM,LISTSERV@GUA
VA.EASE.LSOFT.COM
A VIRUS job type is also available to track intercepted viruses. Assuming that 1) the system.changelog is enabled and 2) LISTSERV's anti-virus scanning facility is enabled, LISTSERV will write records like the following to the system.changelog file for each virus encountered:
20020110152955 VIRUS TEST 6 EICAR-Test-File
20020128144949 VIRUS *LSWAVDD* 1 EICAR-Test-File
A copy of changelog information may be stored in a DBMS. This requires a pre-existing DBMS connection configured in the usual way (see the
Advanced Topics Guide for LISTSERV if you need guidance), and is controlled by three new site configuration parameters, and a table that must be created manually. The parameters, which are defined in LISTSERV's site configuration file, are
CHANGELOG_DBMS,
CHANGELOG_DBMS_TABLE, and
CHANGELOG_DBMS_CONNECTION . The first two are mandatory while the third is optional.
Note: It is not possible for LISTSERV to write the changelog in multiple different tables based on various combinations of parameters. This can be accomplished on the DBMS side with a stored procedure if required.
Important: The DBMS copy is just that, a copy. The disk files (*.changelog) are still generated. Naturally if they are not needed they may periodically be erased with a script.
As an example, let us say that you have created a table called CHANGELOG in the database to which LISTSERV is connected. The CHANGELOG table has four columns, which are called TIMESTAMP, LISTNAME, RECORDTYPE, and PARAMETERS. So you would open your system configuration file in a text editor and add the following entries:
|
•
|
Unix: CHANGELOG_DBMS="ALL"
|
|
•
|
Unix: CHANGELOG_DBMS="SYSTEM NOLIST"
|
