Notebook= No

Notebook= Yes,where,interval|Single|Separate,access-level[,access-level,...]

Indicates whether or not an automatic log of every piece of mail sent to the list is to be kept, and defines at which interval of time its file name must be changed and who is allowed to retrieve it from the server. The default values are "Notebook= No,A,Single,Private".


is the filemode of the minidisk (z/VM) or the disk and directory (non-z/VM) on which the notebook is to be kept. The default value of "A" is equivalent to LISTSERV's main working directory. On z/VM servers, this is LISTSERV's A disk; on Windows servers, this is LISTSERV's MAIN directory, and on Unix servers it is ~listserv/home (or whatever value has been used in the Makefile for $LSVROOT/home). Naturally, you may change this value to any directory you wish, provided that a) the directory exists (for security reasons, LISTSERV will not make it for you) and b) LISTSERV has read-write access to that directory. Rather than use the "A" directory, L-Soft strongly recommends that you create a separate directory structure with subdirectories for each list and use a full path spec for this parameter. This is important for security purposes related to the file server functions (see the Site Manager's Manual for details).

Note that under unix this parameter MUST IMPERATIVELY point to a directory specification that is all lower-case. LISTSERV for unix cannot write archives to directories named in upper- or mixed-case.

If your server is running the Web Archive Interface, L-Soft does not recommend that this parameter be pointed to the web archive index directory.  Doing so can potentially expose your notebook archives to the public, regardless of the access-level you may have set for them within LISTSERV.  Best practice is always that list archive notebooks should be kept in a separate directory tree from the web interface's index files and not be directly accessible from the web.


Defines the filetype or extension of the "notebook" file for the list, as indicated below (the filename will always be the same as the list name):

Single:        A single file with the extension "NOTEBOOK" is created.  (Note: Single

       notebooks are not compatible with the LISTSERV web interface.)

Yearly:        A new file is started each yearly, extension is "LOGyy"

Monthly:        The extension is "LOGyymm"

Weekly:        The extension is "LOGyymmw" (w in "A"-"E")

Separate:        A separate file is kept for each mailing (e.g. announcements,
       newsletters). The extension is "yy-nnnnn" (sequential counter). (Note:

       Separate notebooks are not compatible with the LISTSERV web interface.)

While you may change the notebook interval at any time, LISTSERV will not convert existing notebooks into the new interval format. For instance, if you convert from Monthly to Weekly notebooks, LISTSERV will continue to maintain your original notebooks in their monthly format, while writing any new postings into weekly notebooks. This is perfectly normal and does not affect the proper operation of your list (in particular it does not cause any breakage to the archive search feature).  Moreover (for lists with "Weekly", "Monthly", or "Yearly" archives) the "seamless" archive threading introduced in LISTSERV 17.0 renders the interval distinction effectively moot, at least so far as the display of messages in the interface is concerned.

Note: Lists configured with "Single" or "Separate" archives are not supported in the web archive interface, and no messages will be displayed for lists so configured.

For servers with the web archive interface interface installed, please note that in order for archives to appear in the interface, the following requirements must be met:

    1. Notebooks can be "Public" or "Private" (or any other access-level)
    2. The notebook interval must be "Weekly", "Monthly", or "Yearly" ("Yearly" is not recommended, as the archive files often tend to grow too large).
    3. The "Confidential=" keyword must be set either to "No" or "Service"
    4. The LISTSERV maintainer must create an index directory for your list per the instructions in the Site Manager’s Operations Manual.

See the Site Manager’s Operations Manual for further details.

Note: Notebooks may be retrieved by means of the GET command. On z/VM only, a list of all available notebooks can be obtained with a GET NOTEBOOK FILELIST command.

The first two parameters of the "Notebook=" keyword may only be changed by the LISTSERV postmaster.

If necessary, you may break the "Notebook=" keyword into multiple lines in order to avoid running up against the 100-character header line limit. For instance

* Notebook= Yes,/home/listserv/lists/mylist-l,Monthly,Private

is strictly equivalent to

* Notebook= Yes
* Notebook= /home/listserv/lists/mylist-l
* Notebook= Monthly,Private

This can be particularly important if it is necessary to specify multiple access-levels for the notebooks (for instance if you have many sub-lists and want the subscribers to the sub-lists to be able to access the super-list's notebooks), for example,

* Notebook= Yes,C:\LISTS\SUPER,Monthly,Private,(SUB-A),(SUB-B)
* Notebook= (SUB-C),(SUB-D),(SUB-E),(SUB-F)