HDTenEightyP/NetNews huggingface dataset:
Return-Path: <ERIC@SEARN.SUNET.SE>
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 01:56:02 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Listserv intro message
              6 Jan 1993 16:35:27 PST from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Wed, 6 Jan 1993 16:35:27 PST Yossie Silverman <YOSSIE@UCSFVM.UCSF.EDU>
said:

>I got this from one of my list owners:

But you're still the one who posted it.

>I've noticed that the standard  listserv introductory message for a list
>that archives messages tells the new client  how to ask for an index and
>how to get individual files.  unfortunately, the retrieval part is wrong
>in telling  you to use  "GET LISTNAME  filetype" instead of  what works,
>which is "GET filename filetype".

And what do you  think is the filename of list archive  logs? Could it by
any chance be the list name?

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Arnold Consulting
X-Vms-To: IN%"LSTSRV-L@uga.cc.uga.edu"
X-Vms-Cc: ARNOLD
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 22:31:51 -0600
From:         "Stephen L. Arnold" <ARNOLD@ARNOLD.COM>
Subject:      Re: Clarifications about the digest support
Comments: To: LSTSRV-L@uga.cc.uga.edu

Hi, Eric.  Nice new feature, and thanks for responding to all the
suggestions.

One suggestion occurred to me that I didn't see mentioned.  If a list
is changed back to Digest=No, it seems friendlier to change any
digest subscriptions to Mail rather than Nomail.  At least the user will
get the information, if not in the preferred format (since the preferred
format is being withdrawn!).

Another route you could take would be to allow lists to be marked
Digest=Mail, =Nomail, or =digestparameters.  "Mail" and "Nomail" mean
digests are not available for the list, and people requesting digests
will get Mail or Nomail, respectively, (and a warning!) instead.

Keep up the good work!

Steve
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <@SEARN.SUNET.SE,@FERRIS.BITNET:$EMP@FERRIS.BITNET>
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 12 Jan 1993 10:26:20 EST
Comments:     Warning -- original Sender: tag was A000@FERRIS
From:         Postmaster <$EMP@FERRIS.BITNET>
Subject:      Middle Tenn ?

Been having stuff go awry with this site over the last couple of days.
So far no response from the contact person.
I don't have any problem with "regular" listserv. Anyone know about
middle Tennessee ?
Trevor C Poole
Ferris State University
>
> The following errors occurred while attempting to send this mail file.
>
> Sender is: listserv@knuth.mtsu.edu
>
> MAIL NOT SENT TO => FERRIS.BITNET!@MUSIC.BITNET
> REASON
> *** This userid is not a valid user on our system.
> ------------------------------------------------------------------------------
>
> -----------------------------  ORIGINAL MESSAGE  -----------------------------
>
> HELO FERRIS.BITNET
> MAIL FROM:<@FERRIS.BITNET,@CMUVM.CSV.CMICH.EDU:listserv@knuth.mtsu.edu>
> RCPT TO:<FERRIS.BITNET!@MUSIC.BITNET>
> DATA
> Received: from CMUVM.BITNET (NJE origin MAILER@CMUVM) by FERRIS.BITNET (LMail
> Received: from CMUVM by CMUVM.BITNET (Mailer R2.10 ptf000) with BSMTP id 6709;
>  Mon, 11 Jan 93 20:49:41 EST
> Received: from CMUVM by CMUVM.BITNET (Mailer R2.10 ptf000) with BSMTP id 6708;
>  Mon, 11 Jan 93 20:49:40 EST
> Received: from knuth.mtsu.edu by CMUVM.CSV.CMICH.EDU (IBM VM SMTP V2R1)
>    with TCP; Mon, 11 Jan 93 20:49:38 EST
> Received: by knuth.mtsu.edu (Smail3.1.28.1 #6)
>         id m0nBalh-000d6YC; Mon, 11 Jan 93 19:50 CST
> Date: Mon, 11 Jan 93 19:50 CST
> Sender: listserv@knuth.mtsu.edu (ListServ@KNUTH.MTSU.EDU)
> Message-Id:  <11JAN93.20433949.0002.MUSIC@FERRIS>
> Comment: Middle TN State Univ ListServer Version 5.31
> Errors-To: csmjb@knuth.mtsu.edu
> Reply-To: <listserv@knuth.mtsu.edu>
> Sender: listserv@knuth.mtsu.edu
> Version: 5.4 -- Copyright (c) 1991/92, Anastasios Kotsikonas
> From: listserv@knuth.mtsu.edu
> To: cmuvm.csv.cmich.edu!ferris.bitnet!ferris.bitnet!$emd
> Subject: Invalid request
>
> >The following errors occurred while attempting to send this mail file.
>
> Unrecognized request THE
>
> Report any problems to 'csmjb@knuth.mtsu.edu'.
> For a list of the available requests send a message to listserv@knuth.mtsu.edu
> with the word 'help' in the body of the message.
>
> PS: Any subsequent requests that you might have submitted have been ignored.
> .
> QUIT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Mon, 11 Jan 1993 12:18:37 PST
From:         john riehl <RIEHL@USCVM.BITNET>
Subject:      serving off users

I have several users who subscribe from systems.  Since the hostname is
incorrect (smtp says host is unknown), the mail bounces.  I have served
the userid off and removed him from the list, but he keeps resubscribing,
and he is somehow no longer served out.

1.  Who can serve the user on?

2.  How can I absolutely prevent the user from being served on?

one user in particular is on austen.notis.com

jr
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-pmrqc:      1
Priority: normal
X-mailer:     Pegasus Mail v2.3 (R5).
Newsgroups: bit.listserv.lstsrv-l
Date:         Fri, 8 Jan 1993 12:08:02 CST
Reply-To:     JSimon@TUCCmail.Trinity.Edu
From:         Jonathon Simon <JSIMON@TUCCMAIL.TRINITY.EDU>
Subject:      Rev 5 of 17E-002D
Comments: To: Eric Thomas <ERIC%SEARN.bitnet@VM1.TUCC.TRINITY.EDU>,
          LSTSRV-L%UGA.bitnet@VM1.TUCC.TRINITY.EDU

> Rev 5 fixes  a serious register corruption bug in  a library routine that
> had never been used before rev 4  (the program I used to test the routine
> when I  wrote it was much  simpler and apparently didn't  mind). It fixes
> problems  with the  dates reported  in the  subject field  if the  digest
> couldn't be sent at the expected  time, and adds support for "Size(nnnn)"
> after the frequency parameter. You can  put it either after or before the
> day of week/time of day parameter. Example:

Is installation of rev 5 (on top of rev 4) as simple as running LFIX
17e- 002D, or are there some files that must first be saved (backup
copies made) since I have applied rev 4 already.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <ERIC@SEARN.SUNET.SE>
Newsgroups: bit.listserv.lstsrv-l
Date:         Fri, 8 Jan 1993 16:25:18 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Clarifications about the digest support
              7 Jan 1993 22:31:51 -0600 from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Thu, 7 Jan 1993 22:31:51 -0600 "Stephen L. Arnold" <ARNOLD@ARNOLD.COM>
said:

>One suggestion occurred to me that I  didn't see mentioned. If a list is
>changed  back to  Digest=No, it  seems friendlier  to change  any digest
>subscriptions to Mail rather than Nomail.

The problem is  that LISTSERV just does  not do this sort  of things when
you  edit the  header. Many  people (especially  sites with  large lists)
update lists  by logging on  to LISTSERV and  just editing the  LIST file
directly.  Some day  I'll change  the format  of lists  and this  will no
longer  be possible,  but  for now  I  am very  reluctant  to spend  time
implementing things  which would  work only  if you  don't edit  the list
manually - especially if I end up having  to change it a lot with the new
list  format. The  new  format will  be  needed at  some  time to  handle
addresses longer than 80 bytes in the lists.

>Another  route you  could take  would  be to  allow lists  to be  marked
>Digest=Mail,  =Nomail, or  =digestparameters. "Mail"  and "Nomail"  mean
>digests are  not available for  the list, and people  requesting digests
>will get Mail or Nomail, respectively, (and a warning!) instead.

If you requests  a digest and they  are not available, you  get a warning
and your  options are set  to MAIL. The only  "problem" case is  when you
request and get the digests option, and the list owner subsequently turns
off digests.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <@SEARN.SUNET.SE:Christian.J.Reichetzeder
             @AWIIMC12.IMC.UNIVIE.AC.AT>
Organization: Institut fuer Medizinische Computerwissenschaften
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 16:36:05 CET
From:         Christian.J.Reichetzeder@AWIIMC12.IMC.UNIVIE.AC.AT
Subject:      Re: PD Unix Listserv ListServer?
              7 Jan 1993 14:47:30 GMT from <combstm@LESTER.APPSTATE.EDU>

On Thu, 7 Jan 1993 14:47:30 GMT Terry M. Combs said:
>There is UN*X Listserv software available from cs.bu.edu via anonymous ftp.

Gads, I thought  n-zillions of postings and the recent  flame wars should have
been sufficient prevent this kind of  half-sense [I'm trying to be polite] for
at least a few months.
If ppl.  HAVE TO speak of/ask  for/ask about *Listservers*, well  they perhaps
don't know better.  I don't understand someone claiming  knowledge of LISTSERV
(calling  it  VM listserv  is  redundant)  being  so  ignorant of  the  recent
discussion -  apart from  the fact  the the information  about LISTSERV  is at
least partially incorrect.
'nuff of that, PLEASE
Christian
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Mon, 4 Jan 1993 18:27:37 EST
From:         Kent Fiala <SNOKLF@VM.SAS.COM>
Subject:      CARD abends
Comments: To: "Forum on LISTSERV release 1.7" <LSTSRV-L@uga.cc.uga.edu>

We have an application that makes very heavy use of the CARD command,
and we use the LISTSERV version of CARD.  Very rarely (probably once in
10's or 100's of thousands of executions) it abends with

DMSITS140T CARD routine called from 005A4F9E did DMSKEY with no reset

All of the CARD commands are localized to two places, one for LOAD and
one for DUMP, and the only option that ever varys is NEWDATE/OLDDATE,
so it can't be that some infrequent unusual way of invoking CARD causes
the abend.

The problem is fairly recent, and may be roughly correlated with
conversion to CMS Release 8.

Has anyone else seen this, or anything similar?

------------------------------------------------------------------------
Kent Fiala <snoklf@vm.sas.com>
SAS Institute Inc., Cary NC 27513 USA                 919-677-8000 x6646
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Samford University Computer Services
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 16:10:19 CST
From:         THE GAR <GLWARNER@SAMFORD.BITNET>
Subject:      Average Disk Consumption (?)
Comments: To: lstsrv-l@uga.BITNET, Harold Pritchet <harold@uga.BITNET>
Comments: cc: Galen Tillery <RGTILLER@SAMFORD.BITNET>

My director has finally agreed to let us open up our listserv to
hosting lists (besides computer-service-owned lists) around campus.

BUT, he first wants:

   "rules"     for list owners about what kind of lists can be hosted
               and what kind of things are their job and what are my job.
               (I installed the listserv, and serve as techrep and postmast).

   "class"     An outline of what sort of training will be required for
               list owners, and an estimate of how much time we will
               need to support and train a list owner.

   "resources" An estimate of how much disk space, etc these lists will
               require.

Rules aren't a great problem, but if someone has a set drawn up, I'd
love to see them.

Training is sort of a problem, because we have some VERY experienced
bitnet users who I would love to have as list owners despite the fact
they have NO training, and I have some highly trained people who are
begging to host lists, and would be absolute nightmares to support
because they just simply don't know what they are doing.  We need a
formal way of classifying who is a bumbling idiot and who would catch on
quick and be a great list owner with a little training.  I can't just
say "no, you can't have a list because you're impossible to train".

Resources are a major problem.  The boss wants an estimate, which is
absolutely impossible to do since I don't know yet whether the lists are
going to be STREK-L (150+ messages a day) monsters, or CRYPTO-L (I think
I've got 1 message a month there) crawlers.  And yet I can understand
him wanting to know how much traffic the "average" list has.  Any ideas?


 /++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\
!  Later        +   Systems Programmer                                 !
!  Gary Warner  +   Samford University Computer Services               !
!               +   II TIMOTHY 2:15                                    !
 \+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++/
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <ERIC@SEARN.SUNET.SE>
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 17:02:18 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: New feature in 1.7f - automatic digests
              7 Jan 1993 09:22:15 HNE from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Thu, 7 Jan 1993 09:22:15 HNE Jean Bedard <ADMIN@VM1.ULAVAL.CA> said:

>>Users sign up for digestified  rather than immediate delivery with 'SET
>>listname DIGests',  which is  an alternative to  MAIL and  NOMAIL. This
>>command is rejected if digests are  not available for the list, however
>>if the option is accepted and the list owner subsequently turns digests
>>off, it will be treated like NOMAIL.
>
>May I suggest that, instead of rejecting SET listname DIGEST, it behaves
>like SET listname  MAIL, so that it becomes effective  when/if the owner
>decides to make it operational?

The only  difference is in  the very rare case  where a list  owner first
enables digests,  and then decides to  disable them after all.  In such a
case, I  would expect the owner  to warn the users  abundantly and/or fix
their subscriptions. Furthermore I wanted  to avoid complaints from users
with the  following scenario: Joe  is subscribed to  a bunch of  lists in
their digested form, and goes on vacations for 2 weeks. Before going away
he sets NOMAIL on all lists. When he comes back he finds out that:

1. He did  not get partial digests  for the period of time  before he set
   NOMAIL. Joe  thinks he should have  got the messages posted  before he
   sent the SET NOMAIL.

2. After sending  a SET MAIL command, he got  long digests which included
   messages posted while he had SET NOMAIL!

A  set of  2 options  would  make it  legitimate  for Joe  to think  that
MAIL/NOMAIL controls which messages are shown to him, and DIGEST/NODIGEST
controls  how  they are  sent.  With  a  single  option, digests  are  an
alternative to MAIL and NOMAIL - a  means of getting the messages to you,
and not a means of deciding which messages to show. Joe issues SET NOMAIL
before going on  vacations, and SET DIGESTS (not SET  MAIL) when he comes
back.  At this  point  he  starts getting  the  digests  again, which  is
logical.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: North Dakota Higher Education Computer Network
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 12:29:20 CST
From:         Marty Hoag <NU021172@NDSUVM1.BITNET>
Subject:      Re: Clarifications about the digest support

   Eric - I like the idea of regularly scheduled digests with a cap on the
size of the digest which would force a digest out before the time elapses.
Kicking out a digest at that point would have the benefit of spreading the
network load out and keeping people informed sooner of a high traffic
discussion (as opposed to waiting the entire time period then chopping up
the digest).  Thanks for adding the digest capability...

   Would the addition of a "cap" change the scheduling of the regular
digest in any way?  For example, if I have a weekly list that kicks off
every Sunday but hits its limit on Tuesday, would the next digest still
be scheduled for the next Sunday?  This may depend on implementation details
but I think I like that approach.  It keeps a regular schedule "framework"
with additional digests interspersed as needed due to the load.

   Finally, if some list editors are interested, I wrote a very
simple-minded REXX EXEC which creates digests from note or Rice Mail
NOTEBOOKS (it would probably work from archives too but I don't think
I've tried that).  For example, I save list searches sent to our
new-list list in a notebook and create a digest every few weeks.
Since the DIGEST EXEC just creates a file you can edit the digest as
you wish before sending it (in fact I've wrapped a local exec around
the process to generate mail to the list with the digest imbedded).

   While my DIGEST EXEC isn't totally RFC1153 compliant, it should
allow any reasonable "bursters" to pick it appart ok (it worked with
the RFC1153 author's software anyway).  And it provides a starting
point to you could make it more compliant if you wish.  I'm sure there
are other programs that do this same thing (I know someone was working
on a CMS PIPEs version).

   If you'd like a copy of "DIGEST EXEC" you can get it from LISTSERV
on NDSUVM1 (eg. tell listserv at ndsuvm1 get digest exec ) or via
anonymous FTP to vm1.nodak.edu after  CD LOCSOFT   then  GET DIGEST.EXEC .

     Marty
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <ERIC@SEARN.SUNET.SE>
Newsgroups: bit.listserv.lstsrv-l
Date:         Mon, 11 Jan 1993 23:53:49 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: serving off users
              11 Jan 1993 12:18:37 PST from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Mon, 11 Jan 1993 12:18:37 PST john riehl <RIEHL@USCVM> said:

>1. Who can serve the user on?

If you (not LISTSERV) served him off, only a postmaster can serve him on.

>2. How can I absolutely prevent the user from being served on?

SERVE OFF should do it, but mind the case.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Instituto Tecnologico de Monterrey, Campus Queretaro
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 08:50:16 CST
From:         "Juan M. Courcoul" <COURCOUL@VMTECQRO.BITNET>
Subject:      Re: New feature in 1.7f - automatic digests

On Wed, 6 Jan 1993 21:58:15 +0100 Eric Thomas said:
>Release  1.7f  will  introduce   an  automatic  digestification  function
>allowing subscribers  who do not have  the time to read  large numbers of
>messages as they arrive to subscribe to a digestified version of the list
>instead...
>                                                     ...........The third
>parameter is  either "Daily"  (the default),  "Weekly" or  "Monthly". The
>last  parameter is  optional  and  specifies when  the  digest  is to  be
>actually distributed.

I really like this idea, but just when I was going to suggest a further
improvement....

On Thu, 7 Jan 1993 01:19:34 EST Larry Rondot said:
....
>Will it be possible to place a size limit on the digest?  What I would like
>too see is the ability to cut a digest once a week into as many volumes
>required to keep each volume under a given limit (200k).

I definitely have to side with Larry on this. One of the main criteria I would
have for establishing the cutoff limit would be the size of the individual
digest, even if this means having to send out more than one digest a day
(as in the case of extremely active lists, such as INFO-IBMPC or INFO-MAC).
Note that I would prefer to ship out a digest as soon as the limit is reached,
whereas Larry would wait till a specified time limit and then split up the
thing into as many bits as needed.

This may also alleviate the problem of overflowing the A-disk (or wherever
the digest is being accumulated).

Thanks, Eric, for your continued interest in improving an already great
product !

Juan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
From: combstm@lester.appstate.edu (Terry M. Combs)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: PD Unix Listserv ListServer?
Date: 7 Jan 93 14:47:30 GMT
Organization: Appalachian State University
NNTP-Posting-Host: lester.appstate.edu
X-Newsreader: TIN [version 1.1 PL7]

Douglas M. MacFarlane (madmac@ils.nwu.edu) wrote:
: We are interested in putting-up a listserver here at ILS.  Is there a
: public-domain or inexpensively licensed listserver for Unix, either SunOS,
: AIX, or Ultrix?
:
There is UN*X Listserv software available from cs.bu.edu via anonymous ftp.
Do a cd pub/listserv to get to the area it is stored in.  There is also
an alpha version of a new release of the software which has loads of
features in it that make it a good tool for managing lists. We are using
the 6.0 alpha stuff on ULTRIX 4.2. 

The biggest problem presently is the interfacing of VM Listserv list output
to the UNIX Listserv server.  Peered lists used to be the
method used by the VM listserv but this method generated too much traffic
so a method of "Distribute Jobs" was developed where backbone Listservs 
receive the traffic for an area and distribute that traffic and forward the 
received messages to the next backbone site.  Good idea. 

You could subscribe the listserv to the appropriate VM lists but this
gets messy when users want to post, since many lists require the poster
to also be subscribed.  

I hope this helps.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 7 Jan 1993 11:20:17 EST
From:         Paul Goodwin <CC100PG@GITVM1.BITNET>
Subject:      Re: PD Unix Listserv ListServer?
              7 Jan 1993 14:47:30 GMT from <combstm@LESTER.APPSTATE.EDU>

    On  7 Jan 1993 14:47:30 GMT Terry M. Combs said:
>Douglas M. MacFarlane (madmac@ils.nwu.edu) wrote:
>: We are interested in putting-up a listserver here at ILS.  Is there a
>: public-domain or inexpensively licensed listserver for Unix, either SunOS,
>: AIX, or Ultrix?
>:
>There is UN*X Listserv software available from cs.bu.edu via anonymous ftp.


Is this Un*x Listserv really Listserv, or is it a list server for Un*x?  I know
that there are a number of list servers for Un*x available, but haven't heard
about one which is compatable with LISTSERV yet...


Paul Goodwin
IBM System Support
Georgia Institute of Technology
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Resent-Organization: Temple University Computer Services -- Listserv Postmaster
Return-Path: <@VM.TEMPLE.EDU:LISTSERV@TEMPLEVM.BITNET>
X-Acknowledge-To: <OASIS@TEMPLEVM.BITNET>
Newsgroups: bit.listserv.lstsrv-l
Date:         Wed, 6 Jan 1993 22:08:54 EST
Comments:     Resent-From: Stan Horwitz <OASIS@TEMPLEVM.BITNET>
Comments:     Originally-From: Revised List Processor (1.7e)
              <LISTSERV@TEMPLEVM.BITNET>
From:         Stan Horwitz <OASIS@TEMPLEVM.BITNET>
Subject:      Message

Oops, a  Rexx error seems  to have presented itself  upon attempting to  do a
netwide  delete. Is  this something  which requires  a fix  or should  I just
consider  it an  annomaly. My  listserv machine  has 5  M of  virtual memory.

Stan Horwitz
Listserv Postmaster
Temple University
Acknowledge to: OASIS@TEMPLEVM (or VM.TEMPLE.EDU)

----------------------------Original message----------------------------
A  REXX  error occurred  while  processing  the following  command  from
SYSTEM@GMUVAX: "QUIET DELETE * DD=Names ( NETWIDE FWDED=2". See enclosed
traceback and/or console log for more details.
-------------------------------------------------------------------------------
4 Jan 1993 15:47:48 To   SYSTEM@GMUVAX: You are not a registered NAD (Node Admin
istrator) for node GMUVAX. The NAD (...)
   155 +++       errors = errors'15'x'>>> You are not authorized to act on behal
f of' u@n
   369 +++  Call Process listname
DMSREX450E Error 5 running LSVDEL EXEC, line 155: Machine storage exhausted
-------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU