HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.lstsrv-l
Date:         Wed, 7 Oct 1992 09:51:25 EDT
From:         Christine Shih <SHIH@KENTVM.BITNET>
Subject:      Error messages for remote lists

Is it  true that error  messages for list  that has an  errors-to field
pointing to  a remote site  got forwarded to the  postmaster's account?
Does the  errors-to person  also get  a copy? I  tried to  contact this
person but got no reply yet.

This is the only guess I could make about the delivery error messages I
am getting for a  list hosted here. I don't get  error messages for any
other list but this one.  The header is enclosed.  Is there something I
didn't setup correctly for the list?  Thanks for any suggestions.

*  Review= owner                  Subscription= Open
*  Send= Editor                   Notify= No
*  Confidential= no
*  Reply-to= xxxxxx@djohn-sun.kent.edu
*  Files= No                      Validate= Store only
*  X-tags= Comment                Ack= No
*  Stats= Normal,Private          Prime=No
*  Errors-to= xxxxxxx@sun-robot.nuceng.ufl.edu
*  Notebook= Yes,E,Weekly,Public
*  Mail-via= DIST2
*
*  Editor= xxxxxx@djohn-sun.kent.edu
*


Christine Shih
SHIH@KENTVM
Postmaster at KENTVM
From: GRZ046@vm.gmd.de (Richard Rodriguez)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: LMON/RSCS v3
Date: 15 Oct 92 14:47:05 GMT
Organization: GMD St. Augustin, Germany

Yes, we use LMON and RSCS V3, but only to gather statistics about
link availability. Automatic link restarts are now either handled
by RSCS internal retries or by VMNET. File size limits are enforced
by the optional shift-based file limiting package. I like this much
more than polling the link.

rr
From: WEAVER@OHSTVMA.BITNET (Duane D. Weaver)
Newsgroups: bit.listserv.lstsrv-l
Subject: LMON/RSCS v3
Date: 13 Oct 92 19:53:55 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

I have searched the archives for updates to LMON so it will work
with RSCS v3.   I found a reply to a request from Eric for a RSCS v3
site to test some changes to LMON and that is all.

Eric, are there changes to LMON that is available.
A look at LSOFT FILELIST on LISTSERV@SEARN revealed no recent updates
to the files for LMON.

Thanks,
Duane
From: ERIC@SEARN.SUNET.SE (Eric Thomas)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: Draft Internet requirement for mail based servers
Date: 16 Oct 92 23:05:22 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Comments: To: Greg Vaudreuil <gvaudre@NRI.Reston.VA.US>,
              cargille@cs.wisc.edu, houttuin@amiga.physik.unizh.ch,
              neufrode%neuvm1.BITNET@searn.sunet.se,
              jbc%bitnic.BITNET@searn.sunet.se, lstsrv-l@searn.sunet.se
              16 Oct 92 13:16:58 -0400 from Greg Vaudreuil
              <gvaudre@NRI.Reston.VA.US>

On Fri, 16 Oct 92 13:16:58 -0400 Greg Vaudreuil <gvaudre@NRI.Reston.VA.US>
said:

>Thank  you  for  reading  the document  and  submitting  comments.  This
>document is an Internet Draft  submitted independently for review by the
>IETF  community. The  intent of  posting  such documents  is to  solicit
>comments like  yours. The posting does  not lend any official  status to
>the document.

Thanks for  your prompt answer. I  understand that the document  is not a
standard and not even about to  be reviewed for standard status. However,
I learnt about  this through sheer luck.  I was about to  hit the discard
key after  having done the  same for a rather  long series of  new RFC's,
when I  suddenly realized it  could apply  to LISTSERV. My  comments were
*not* solicited,  and the same is  true for the cooperating  networks the
proposal  would  like to  apply  to.  The issue  was  not  brought to  my
knowledge, nor so  much as mentioned on any of  the mailing lists devoted
to  LISTSERV, in  spite of  the fact  that LISTSERV  is mentioned  in the
proposal.

>Should this  document move  beyond the "Interesting  Idea" stage  and be
>submitted  as  a proposed  standard  to  the  IESG, the  community  will
>notified

I also  understand that, but  due to the  pretty loose definition  of the
word  "community",  especially when  it  comes  to networks  with  e-mail
connectivity, I  just want to  make sure that  my opposition to  both the
contents of the proposal and the way  it came to be developed is formally
registered  within the  IETF structure.  My goal  is not  to prevent  the
proposal from  ever turning into a  standard, but to make  sure that this
does not happen without explicit consultation of interested parties which
ought to have been involved from  day one. In particular, if the proposal
claims to apply to EARN and CREN, it should be formally approved by their
respective decision-making bodies  (which I trust not  to blindly approve
this  sort  of  proposal   without  consulting  software  developers  and
considering the interests of their users).

Thanks again for your time.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 13 Oct 1992 09:47:49 EDT
From:         "Noel P. Hart" <NHART@MITVMA.BITNET>
Subject:      Line continuation

How do I continue a line in a list header ?
From: ERIC@SEARN.BITNET (Eric Thomas)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: Owner cannot post to list
Date: 16 Oct 92 23:36:04 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
              16 Oct 1992 15:09:23 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Fri, 16 Oct 1992 15:09:23 EDT Gerrit Bos <SOFGBOS@VM.UOGUELPH.CA>
said:

>* Send= Open

You probably meant "Send= Public".

  Eric
From: DEVMTG12@SAKFU00.BITNET (MUSTAFA T. ALGHAZAL)
Newsgroups: bit.listserv.lstsrv-l
Subject: autolog error
Date: 7 Oct 92 10:48:21 GMT
Organization: KFU - KING FAISAL UNIVERSITY ,SAUDI ARABIA
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

Hi ...
       I discovered that the operator can't autolog the listserv machine
after IPLing the system,since release 1.7d has been installed.
I have to login the listserv and then run the lsvprof each time.However I
found that the exec is not running perfectly ,as I got the following msg.
(DMS ABN 150W 523 HEX 00020B Double Words of system storage were not recovered)

I tried to increase the storage capacity for the listserv machine ,but still
the error is there .
any help is much appricaited

____________________________________________________________________
|  MUSTAFA T. AL-GHAZAL          ||     DEVMTG12@SAKFU00.BITNET    |
|  KFU NODE ADMINSTRATOR         ||     OR : NAD@SAKFU00           |
|  ACADEMIC COMPUTING SERVICES   ||     VOICE: (966) 3-580-0219    |
|        M A N A G E R           ||     OR : (966)3-580-0000 X 1214|
|  KING FAISAL UNIVERSITY        ||     COMPUTER CENTER            |
|  HOFUF-SAUDI ARABIA            ||     P.O.BOX 380                |
|________________________________||________________________________|
From: ERIC@SEARN.BITNET (Eric Thomas)
Newsgroups: bit.listserv.lstsrv-l
Subject: Reformatting of PROFS notes under 1.7e
Date: 17 Oct 92 01:13:30 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

Unless someone  has a strong objection,  release 1.7e is going  to remove
the blank in  column 1 when reformatting PROFS notes,  as per the request
of a  PROFS site.  Just to  make sure no  useful information  is removed,
LISTSERV checks that there is a  blank there before removing it, and this
of course happens only for PROFS mail.

  Eric
From: TURGUT@FRORS12.BITNET (Turgut Kalfaoglu)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: LMON/RSCS v3
Date: 14 Oct 92 12:36:20 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Comments: To: WEAVER@OHSTVMA.BITNET

Fyi, There is a version of LMON that works with RSCS 3 that I stored
at LISTSERV@TREARN as a $PACKAGE a while ago. Probably it would work
for LISTSERV too. I think DEARN uses it on their RSCS 3..

Regards, -turgut
From: USTS034@UABDPO.BITNET (Landy Manderson)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: X-DEL JOBs accumulated
Date: 16 Oct 92 19:10:23 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Comments: To: "Forum on LISTSERV release 1.7" <LSTSRV-L@UGA.BITNET>,
              tramng@acadvm1.uottawa.ca
              16 Oct 1992 14:45:08 EDT from <TRAMNG@ACADVM1.UOTTAWA.CA>

On Fri, 16 Oct 1992 14:45:08 EDT Tram Nguyen said:
>All the X-DEL JOBs (with Prime=QuietNo) that arrived to our LISTSERV
>during prime time (MON-FRI: 8:00-17:00) seem to be forgotten in the
>reader.  {...}

I believe you have encountered the bug which I reported on 9/20, and Eric
fixed with patch 17D-003o on 9/21.  Our notes should be in the archives.
If you need more details, please let me know.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Marist College
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 8 Oct 1992 12:55:17 EDT
From:         "A. Harry Williams" <HARRY@VM.MARIST.EDU>
Subject:      AFD question

I'm playing with some AFD things, and have hit a few questions.
I'd like to be able to add an AFD subscription with a wildcard.
I cannot get this to work from the command line.  AFD ADD XYZ XYZ*
says file XYZ XYZ* is not known.  However, if I manually add
XYZ XYZ* to the AFDLIST FILE(in the proper format), it works.

Is
  a) wildcarding not supported and I'm just lucky with the manual add?
  b) Wildcarding supported, but I'm not doing the add correctly?
  c) neither

For reasons that are not relative to the discussion, I don't want
the message that is associated with the AFD sending of a file
to be sent.  There doesn't seem to be a way to suppressing this
message.  True or False?

/ahw
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 13 Oct 1992 10:05:04 EDT
Comments:     Converted from PROFS to RFC822 format by PUMP V2.2
From:         "Mignon Erixon-Stanford,
              Academic Systems Head" <IRMSS907@SIVM.BITNET>
Subject:      PROFS site needed to beta-test 1.7e

From:    Mignon Erixon-Stanford, Academic Systems Head

Eric - We're a PROFS site, running PUMP.  We'll beta 1.7e.

=-=-=-=-=-=-=-=-=-=-=-IRMSS907@SIVM-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Research Systems Division     Smithsonian Institution, A&I 2310
Washington, DC 20560          Internet: IRMSS907@SIVM.SI.EDU
From: ERIC@SEARN.BITNET (Eric Thomas)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: LMON/RSCS v3
Date: 13 Oct 92 20:56:45 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
              13 Oct 1992 15:53:55 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

Well testing was successful but I had not updated the distribution
version on LISTSERV@SEARN. This is now done.

  Eric
From: SOFGBOS@VM.UOGUELPH.CA (Gerrit Bos)
Newsgroups: bit.listserv.lstsrv-l
Subject: Owner cannot post to list
Date: 16 Oct 92 19:09:23 GMT
Organization: University of Guelph; Guelph, Ont., Canada; N1G 2W1
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

This is probably another one of these simple problems. but it is
baffling me.  The owner of a local list cannot post to the list.
I've checked all things I could think of:  He is subscribed, not
disabled, can send mail to other lists, but he always gets
rejected when he tries to post to his own list.
Here is one of the sample returned messages.  Am I in blindness
overlooking something?
------------------------------------------------------------------------------
Received: by UOGUELPH (Mailer R2.08 R208004) id 0426;
          Wed, 23 Sep 92 16:13:05 EDT
Date:         Wed, 23 Sep 1992 16:13:05 -0400
From:         Revised List Processor (1.7d) <LISTSERV@UOGUELPH.BITNET>
Subject:      Rejected posting to LARCHNET@UOGUELPH
To:           Paul Graham <CCSGRIMM@VM.UOGUELPH.CA>

You   are   not    authorized   to   mail   to   list    LARCHNET   from   your
CCSGRIMM@VM.UOGUELPH.CA account.  You might be  authorized to post to  the list
from  another of  your  accounts or  under a  slightly  different address,  but
LISTSERV has no way to associate this  other account or address with you and is
thus rejecting your message. Your message is being returned to you unprocessed.
If you  have any  question regarding  authorization to  use the  LARCHNET list,
please contact  one of the  list owners, whose  names and addresses  are listed
below:

 Paul Graham <CCSGRIMM@UOGUELPH.BITNET>
 Paul Graham <CCSGRIMM@VM.UOGUELPH.CA>

------------------------- Rejected message (25 lines) -------------------------
Received: from VM.UoGuelph.CA (CCSGRIMM) by VM.UOGUELPH.CA (Mailer R2.08
 R208004) with BSMTP id 0416; Wed, 23 Sep 92 16:11:59 EDT
Date:         Wed, 23 Sep 92 16:05:18 EDT
From:         Paul Graham <CCSGRIMM@VM.UoGuelph.CA>
Subject:      Local Trouble
To:           Landscape Architecture E-newslist <larchnet@VM.UoGuelph.CA>

Hi, It's me.. your fearless Listowner .. had some troubles locally with
LISTSERV (a new version was installed, that might have been it) and so the
first few postings may have been lost.. hard to say.. anyway, I did post

...some lines deleted.... Gerrit

Paul Graham
University of Guelph
Landscape Architecture.
Canada

--------And the list header-----------

*    Landscape Architecture List
*
* Confidential= No
* review= public
* Subscription= Open
* Send= Open
* Notify= Yes
* Reply-to= List,Respect
* Files=No
* Validate= All Commands
* Stats= Normal,Private
* Ack= Yes
* Notebook= Yes,F,Monthly,Private
* Formcheck= No
* SizeLim= 5000
* Errors-to= Owner
*
*   OWNER= CCSGRIMM@UOGUELPH (Paul Graham)
*   OWNER= CCSGRIMM@VM.UOGUELPH.CA (Paul Graham)
*

Gerrit Bos   Systems Analyst, Data Comm., Comp. & Comm. Services, U. of Guelph
             Guelph ON Canada N1G 2W1 Ph:(519)824-4120 x3489 Fax:(519)763-1620
   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
Modesty is an ornament, but you go further without it... German Proverb
From: NU021172@NDSUVM1.BITNET (Marty Hoag)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: X-DEL JOBs accumulated
Date: 16 Oct 92 20:09:14 GMT
Organization: North Dakota Higher Education Computer Network
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
              16 Oct 1992 14:45:08 EDT from <TRAMNG@ACADVM1.UOTTAWA.CA>

On Fri, 16 Oct 1992 14:45:08 EDT Tram Nguyen said:
>All the X-DEL JOBs (with Prime=QuietNo) that arrived to our LISTSERV
>during prime time (MON-FRI: 8:00-17:00) seem to be forgotten in the
>reader.  However, LSVPRIME, executed every half hour during prime time,
>recognized that the jobs are there but suspended them due to the option
>Prime=QuietNo.
>
   I think fix 17D-003O fixed that here.  Here is the description.  It is
available from LISTSERV@SEARN with  GET 17D-003O FIX   (you may want to
GET V17D FIXLIST etc.  These should come from your official NAD address
as defined in the :contact. of PEERS NAMES on LISTSERV's 191 disk.

     Marty

17D-003O - Installed on 22 Sep 1992 13:22:46, affected files:
* LSVPRIME EXEC     - saved as LSVPRIME BK17D003
> This fix  corrects a  bug in the  WAKEPARM-driven exit  that releases
> jobs held for processing outside  prime time. Servers running without
> prime time  are not  affected. Note  that this  fix does  not replace
> LSWPLIB and thus does not include any of the other fixes.
From: gvaudre@NRI.RESTON.VA.US (Greg Vaudreuil)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: Draft Internet requirement for mail based servers
Date: 16 Oct 92 17:16:58 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Comments: To: Eric Thomas <ERIC@searn.sunet.se>
Comments: cc: "Forum on LISTSERV release 1.7" <LSTSRV-L@searn.sunet.se>,
              cargille@cs.wisc.edu, houttuin@amiga.physik.unizh.ch,
              neufrode%neuvm1.BITNET@searn.sunet.se,
              jbc%bitnic.BITNET@searn.sunet.se
              16 Oct 92 16:58:57 BST." <9210161305.aa13280@NRI.Reston.VA.US>

Erik,

Thank you for reading the document and submitting comments.  This
document is an Internet Draft submitted independently for review by the
IETF community.  The intent of posting such documents is to solicit
comments like yours.  The posting does not lend any official status to
the document.  Should this document move beyond the "Interesting Idea"
stage and be submitted as a proposed standard to the IESG, the
community will notified and a working group will likely be formed or an
existing working group will be tasked to review the proposal. Only
after this review will the document be considered by the IESG/IAB for
standardization.

Greg Vaudreuil
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Fri, 9 Oct 1992 16:47:33 EDT
From:         Bill Gruber <BIGCU@CUNYVM.BITNET>
Subject:      Subscription= (listname)?

We wish to create some sublists with the restriction that you must already be
subscribed to a "main" list in order to be allowed to subscribe to the sublist.
In other words, you can subscribe to list B only if you are already subscribed
to list A.

I tried Subscription= (listname) but this was not recognized so it defaulted
to Subscription= By_owner.  Anyone have any ideas about this?  Perhaps
Service= (listname)?... not sure that is looking for an access-level either.

Oh well... thanks for any suggestions.

Bill Gruber
City University of New York Computer Center
bigcu@cunyvm.cuny.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Sun, 11 Oct 1992 01:05:51 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      PROFS site needed to beta-test 1.7e

Some of  the mail processing  code has  been totally rewritten  for 1.7e.
This  includes  header processing.  A  RFC822  header is  now  internally
generated for PROFS, IBM NOTE et al  so that only one place would have to
be changed to  support long lines (previously, the  header routines would
set up a bunch of internal variables to get the desired results, and this
ended up being a mess as the code grew).

I need a PROFS site to test the new code, since I do not run PROFS.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 8 Oct 1992 18:07:13 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: AFD question
              8 Oct 1992 12:55:17 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Thu, 8 Oct 1992 12:55:17 EDT "A. Harry Williams" <HARRY@VM.MARIST.EDU>
said:

>  a) wildcarding not  supported and I'm just lucky with  the manual add?
>  b)  Wildcarding supported,  but I'm  not doing  the add  correctly? c)
>  neither

b. Wildcards are supported, but only  when they match a generic entry, or
a subset of  a generic entry. For  instance, if you have  a generic entry
for '* MINUTES',  you can subscribe to '* MINUTES',  '92* MINUTES' and so
on, but not  to '* MIN*'. The  reasons is that '* MINUTES'  have the same
access control  levels, and any new  file will inherit this.  There is no
telling what the next file which happens  to match '* MIN*' will have for
a GET code.

>For reasons  that are not relative  to the discussion, I  don't want the
>message that is  associated with the AFD  sending of a file  to be sent.
>There doesn't  seem to  be a  way to suppressing  this message.  True or
>False?

You  can't  suppress  the  messages.  In principle  they  should  not  be
generated when the file is sent via mail, well at least not with 1.7e.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
From: JIMJ@JHUVM.BITNET (Jim Jones)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: Owner cannot post to list
Date: 17 Oct 92 03:44:58 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
              16 Oct 1992 15:09:23 EDT from <SOFGBOS@VM.UOGUELPH.CA>

On Fri, 16 Oct 1992 15:09:23 EDT Gerrit Bos said:
>This is probably another one of these simple problems. but it is
>baffling me.  The owner of a local list cannot post to the list.
>I've checked all things I could think of:  He is subscribed, not
>disabled, can send mail to other lists, but he always gets
>rejected when he tries to post to his own list.
>Here is one of the sample returned messages.  Am I in blindness
>overlooking something?

 The code that parses the list headers was changed in a recent release of
 LISTSERV (1.7d I believe).  One side effect is that unrecognized values
 for list variables produce different results.  That is, "Send= Owners" used
 do the same thing that "Send= Owner" did, by accident.  You've coded your
 list with "Send= Open" which is an unrecognized value.  The proper setting
 is "Send= Public".  I ran into a similar problem earlier this week with a
 secondary distribution list (it had "Send= Owners" so the posts were bounced).
 After the list owner changed it, everything worked just fine again.

 -jj

 PS - The short answer is, change the list header to "Send= Public". :)
From: TRAMNG@ACADVM1.UOTTAWA.CA (Tram Nguyen)
Newsgroups: bit.listserv.lstsrv-l
Subject: X-DEL JOBs accumulated
Date: 16 Oct 92 18:45:08 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.

All the X-DEL JOBs (with Prime=QuietNo) that arrived to our LISTSERV
during prime time (MON-FRI: 8:00-17:00) seem to be forgotten in the
reader.  However, LSVPRIME, executed every half hour during prime time,
recognized that the jobs are there but suspended them due to the option
Prime=QuietNo.

How do I get them to be processed again ?  And what caused LISTSERV
to behave like that ?  Does it have anything to do with the fact
that the server was placed offline a few days ago as the number of
spool files go past the limit ?  Any pointers are greatly appreciated.
We are running release 1.7d.

Thanks in advance.

Tram Nguyen
University of Ottawa.
From: SYSMAINT@PCCVM.BITNET (Russell N. Hathhorn, VM Systems Support)
Newsgroups: bit.listserv.lstsrv-l
Subject: VM based bulletin board software
Date: 14 Oct 92 20:04:23 GMT
Organization: Portland Community College
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

I know that I have seen this stuff mentioned somewhere - but I forgot where

Information please

+---------------------------------------------+-------------------------------+
|   Russell N. Hathhorn                       |  Bitnet: SYSMAINT@PCCVM       |
|   VM Systems Programmer/Analyst             |  Compu$erve: 76636,1036       |
|   Portland Community College                |  Voice: (503) 244-6111 x 4705 |
|   12000 S. W. 49th Avenue                   |  Fax:   (503) 324-7010        |
|   Portland, Oregon  97219-0990              |  "     Just say NO to OCO   " |
+---------------------------------------------+-------------------------------+
| "No free man shall ever be debarred the use of arms... The strongest reason |
|  for people to retain the right to keep and bear arms is, as a last         |
|  resort, to protect themselves against tyranny in government."              |
|  Thomas Jefferson - Proposal Virginia Constitution, June 1776               |
|  Thomas Jefferson Papers, 334 (C. J. Boyd, Ed., 1950).                      |
+-----------------------------------------------------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 13 Oct 1992 14:55:27 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Line continuation
              13 Oct 1992 09:47:49 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

You can't,  the maximum length  is 98  characters. Keywords which  have a
series  of values  separated by  commas  can be  repeated. For  instance,
"Owner= X,Y" is the same as coding "Owner= X" and then "Owner= Y".

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Sat, 10 Oct 1992 01:12:32 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Subscription= (listname)?
              9 Oct 1992 16:47:33 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Fri, 9 Oct 1992 16:47:33 EDT Bill Gruber <BIGCU@CUNYVM> said:

>I  tried Subscription=  (listname) but  this  was not  recognized so  it
>defaulted to Subscription=  By_owner. Anyone have any  ideas about this?
>Perhaps  Service=  (listname)?...  not  sure  that  is  looking  for  an
>access-level either.

No,  "Service=" expects  a list  of hostnames,  countries, administrative
networks, and so on. It was never meant to cover anything but topological
or administrative areas. I'm afraid there is currently no way to do that,
beyond  an   external  server  that   would  process  the   requests  for
subscriptions on its own and issue the ADD command.

  Eric