*******************************************************************************
 
OMICRON ECHO 3                                                   9 . dubna 1993
 
*******************************************************************************
 
OBSAH:   1. STUDIJNI PRIRUCKA
         2. PRIKAZ DIGEST/INDEX
 
*******************************************************************************
 
                      S T U D I J N I  P R I R U C K A
                      --------------------------------
   Vazeni pratele!
 
   Prave vysla prva studijni prirucka pro kurs "Sluzby celosvetove pocitacove
site Internet a zpusoby jejiho vyuzivani". Prirucka se nazyva "Elektronicka
posta a elektronicke konference v siti Internet". Autori jsou
 
            Vladimir Vrabec (vrabec@vax.felk.cvut.cs),
            Martin Bily (bily@vax.felk.cvut.cs), tel. 297841 l. 323.
 
   Prirucka zahrnuje 70 stan textu vysazenych v systemu LaTeX a obsahuje tyto
kapitoly:
 
    1. Co to je Internet ?
        2. Internetovska adresace
    3. Elektronicka posta
    4. Internet Resource Guide
    5. Archie
    6. FTPMAIL
        7. BITFTP
    8. Service
    9. Trickle
       10. Elektronicke diskusni skupiny a konference.
 
   Prirucka je urcena pro posluchace kursu, v mensim mnozstvi je u autoru
k disposici i ostatnim zajemcum.
 
                                                  Vladimir Vrabec
                                                  Martin Bily
 
*******************************************************************************
 
               P R I K A Z   D I G E S T / I N D E X
               -------------------------------------
 
   "Listserv" Erica Thomase verze 1.7f poskytuje mezi jinym uzivateli
alternativni volby
        SET listname DIGESTS,
        SET listname INDEX.
Tyto volby jsou alternativni navic s volbami
        SET listname MAIL,
        SET listname NOMAIL
(viz pripojeny vypis z LISTSERV REFCARD).
 
   Pokud spravce vhodne nastavi e-konferenci, tak volba DIGESTS zpusobi, ze
tok jednotlivych prispevku z konference k uzivateli je zamenen za posilani
zprav zahrnujici souhrn prispevku za urcene obdobi (treba za den). Volba
INDEX znamena, ze se zasilaji pouze jednoradkove informace o prispevcich.
Dle techto informaci lze pomoci napr. prostredku vyberu z databazoveho archivu
zajimave prispevky vyzadat.
 
   Podrobnosti lze najit v prilozenych prispevcich Erika
Thomase do e-konference LSTOWN-L. Upozornujeme, ze ne kazdy "listserv" je
Thomasuv. Jeho typ snadno overite zaslanim libovolneho prikazu dotycnemu
"listservu" a prohlednutim odpovedi, ktera by mela v nasem pripade obsahovat
v hlavicce zadanou identifikaci "listservru" napr.
        "BITNET list server at XXXXX (1.7f)".
 
 
--------
Subject: File: "LISTSERV REFCARD"
......
         Revised LISTSERV System Reference Library, release 1.7f
         -------------------------------------------------------
         (c) Eric Thomas 1986,1987,1988,1989,1990,1991,1992,1993
......
 
SET          listname options                  Alter your subscription options:
......
 
             Mail/NOMail                       -> Toggle receipt of mail
             DIGests/INDex                     -> Ask for digests or message
                                                  indexes rather than getting
                                                  messages as they are posted
......
 
--------
 
>>> Item number 1215, dated 93/01/06 21:58:15 -- ALL
> Date:         Wed, 6 Jan 1993 21:58:15 +0100
> Reply-To:     ListServ list owners 
> Sender:       ListServ list owners 
> From:         Eric Thomas 
> Subject:      New feature in 1.7f - automatic digests
 
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 list owner decides whether digests are available or not, the
frequency at  which they are issued  and the day  of week or time  of day
when the  digest should  be distributed. The  digests conform  to RFC1153
with an  accepted deviation from  the recommended subject  line (verified
with the RFC author).
 
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.
 
The list owner controls the availability and frequency of digests through
the new "Digest=" list header keyword, which defaults to "Digest= No" for
lists without an archive and "Digest= Yes,Same,Daily" for archived lists.
It  is not  necessary for  the  list to  be  archived to  keep a  digest,
LISTSERV simply attempts to enable digests (by default) for as many lists
as  possible, but  without ending  up having  to store  large amounts  of
digest data  on its A-disk. Because  the default frequency is  daily, the
additional cost in disk  space is very low (but might  still not have fit
on the A-disk once multiplied by 100 lists).
 
The syntax of the keyword  is "Digest= Yes,where,frequency,when", or then
"Digest= No". The second parameter  is a disk or directory specification,
just as  with the "Notebook="  keyword, or  "Same", which means  that the
digest must be  stored on the same  disk as the list  archives. 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.  For daily  digests, specify  'hh:ss' or  just 'hh'
(with the  understanding that  distribution will not  occur at  the exact
time  you  specified).   For  weekly  digests,  specify   a  weekday  (eg
"Tuesday"). For  monthly digests, you may  specify a number from  1 to 31
corresponding  to  the  day  of  the   month  when  the  digest  will  be
distributed, although  this is  not recommended. The  purpose here  is to
make it possible  for digests to be  issued at mid-month - if  you code a
number larger than 28, you may not get a digest every month.
 
You can  already start coding "Digest="  keywords for the lists  you own.
The code will be made available shortly for beta-testing.
 
  Eric
 
>>> Item number 1251, dated 93/01/09 03:19:25 -- ALL
> Date:         Sat, 9 Jan 1993 03:19:25 +0100
> Reply-To:     ListServ list owners 
> Sender:       ListServ list owners 
> From:         Eric Thomas 
> Subject:      Support for "digest indexes"
 
Support for digest indexes has been added to release 1.7f. A digest index
is a kind of table of contents - a digest without the actual messages. It
gives the name  of the poster, the  subject, the number of  lines and the
date of each posting, along with a  reference number which you can use to
order  the actual  message (through  the database  functions) if  you are
interested. See the example below.
 
Indexes are  automatically available if  the list offers digests  AND the
postings are archived. An index is  sent to users who have requested this
type of subscription (via SET listname  INDEX, an alternative to MAIL and
DIGEST)  whenever a  digest is  issued.  Thus, there  is no  need for  an
"Index=" option - indexes are an integral part of the digest system.
 
I am  not going to  consider an option allowing  indexes to be  turned on
when the list is not archived, with LISTSERV keeping the last 50 messages
or 500k for a week so that people have time to order them, except that if
there were  more than 50  messages or 500k in  the digest it  should keep
everything for 3 days, and then the last  50 for a week. I know there are
many list owners who can't get disk space to archive their list, but this
sort of system simply doesn't work, it costs more in wasted manpower than
you'd save in disk space costs. With a bit of effort you can usually find
a site with the disk space to host your list.
 
The code is being made available for  beta-testing as 17E-002D rev 6. The
first index  issued for any given  list will contain question  marks in a
number of places if you were running 17E-002D rev 4 or 5 before - this is
normal and can be ignored.
 
  Eric
-------------------------------------------------------------------------
> Date:     Sat, 9 Jan 1993 03:16:34 +0100
> Reply-To: Revised List Processor (1.7e) 
> Sender:   "L201: SEARN 201 list" 
> From:     Automatic digest processor 
> Subject:  L201 Index - 9 Jan 1993 - Special issue
> To:       Recipients of L201 indexes 
 
Index Date  Size Poster and subject
----- ----  ---- ------------------
00014 01/09   15 From:    Eric Thomas 
                 Subject: PIPE statistics
 
00015 01/09  140 From:    Eric Thomas 
                 Subject: Mailer statistics
 
The sizes shown are the number of lines in the messages, not counting mail
headers. For your convenience, this message has been specially formatted to
make it easier to order the messages you are interested in. Just forward this
message back to L@SEARN (or L@SEARN.SUNET.SE) and fill in the line starting
with "Print" (if there is not enough space, you can add more lines as long as
you type "Print" on each new line). Make sure to use the forward command of
your mail program, not the normal reply function. There is a lot more the
LISTSERV database functions can do for you - for instance, you can select all
the messages with a particular subject in a single command rather than retyping
all the index numbers. For more information, send an INFO DATABASE command to
LISTSERV (you could add it before the line that says "Database search" the next
time you order messages from the LISTSERV archive).
 
//       JOB
Database search DD=Orders
//Orders DD *
Select * in L201.14-15
Print 
/*
//       EOJ
 
*******************************************************************************