Subject: | |
From: | Eric Thomas <ERIC@FRECP11> |
Reply To: | The Revised LISTSERV Distribution List <LSTSRV-L@EB0UB011> |
Date: | Tue, 12 May 1987 23:47 SET |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Alan: I'm posting my reply directly to LSTSRV-L since I'll go home soon. It
will probably reach the list before your question so I'm using
REPLY TEXT.
> Does AFD use distribute?
No.
> Can it be made to?
Not yet, but I'm considering doing something in this direction (only if there
is no prolog of course).
> Can distribute be given a TO which specifies a list?
No problem, or more simply, just SENDFILE the stuff to the list userid (and
set Files=Yes and FormCheck=No or something like that). It will go
automatically via DISTRIBUTE without your having to build a job header.
>
> Basically, I want to:
>
> - Accept subscriptions for mailer distributions from authorized users
> such as :contact for himself or for a designated user (e.g. similar
> to FOR command).
Note that you can use LSVNAD(userid@node) (returns a boolean) to do that.
It also checks for alternate contacts, etc.
> - Periodically cause an updated distribution to be sent out via
> DISTRIBUTE to the users in the subscription list.
That's no problem
> - Do something similar for KERMIT files more along the lines of
> an AFD since those files get updated at different intervals and
> are not really a single package like mailer updates are.
Sounds great, but I must change the code then. Maybe an AFD=DISTRIBUTE
in the filelist header or something like that?
> For
> KERMIT too I would like to restrict who can subscribe to prevent
> multiple subscriptions at the same site.
That's a little more difficult to check (you have to look into AFDLIST FILE)
but it's feasible.
> Also, maybe KERMIT
> could be distributed out to several listserv sites?
I'll let the list answer this one. Not me -- not enough DASD space.
> Am I making sense?
Sure. The network would bless you if all KERMIT traffic could be lowered by
just a mere little small 30%... :-)
Eric
|
|
|