While checking on the status of FRULM11, whose mailer turned out to be dead
(among other problems), I discovered the cause of the messages you're seeing
below. This is what happens when the mailer delivers something to LISTSERV
without setting the filetype to "MAIL". LISTSERV then processes it as a
non-mail file, executing each command in turn; since LSVCMD is programmed to
ignore any "command" from the mailer (before 1.24, there was no asterisk on
the "Mail sent" messages, so the mailer was indeed sending a lot of
"commands"), you don't get the "Invalid command" messages. Although this is
not a LISTSERV bug, I will add a test in 1.6b to process anything coming from
the local mailer as mail.
 
  Eric
----------------------------Original message----------------------------
Here's another of those strange error messages from LISTSERV.
This is the first I've seen in a long time.
 
== Forwarded Mail ==
 
Received: from UBVM(MAILER@UBVM) by NIHCU (Mailer) id 2525;
              Wed, 15 Feb 89  07:55:35 EST
Received: by UBVM (Mailer R2.02A) id 9460; Wed, 15 Feb 89 07:57:12 EST
Date:         Wed, 15 Feb 89 07:57:11 EST
From:         Revised List Processor (1.5o) <LISTSERV@UBVM>
Subject:      Output of your job "MAILER"
To:           MAILER@NIHCU
 
> To:       listserv@ubvm
 
> From:     "Norman C. Saunders" <NYS@NIHCU>
 
> Date:     Wed, 15 Feb 89  07:54:18 EST
 
> signoff pascal-l
 
 
Summary of resource utilization
-------------------------------
 CPU time:        0.49 sec                 Device I/O:     0
 Overhead CPU:    0.03 sec                 Paging I/O:     1
 CPU model:       3081                     DASD model:  3380