"SfR Fresh" - the SfR Freeware/Shareware Archive

Member "tulp-4.2.1/INSTALL" of archive tulp-4.2.1.tar.gz:

    1 INSTALL,v 1.4 2000/03/07 22:16:46 kim Exp
    2 
    3 
    4                      The Unix Listserv Program
    5                           Version 4.1.0
    6                  Installation and Operations Guide
    7 
    8      Copyright (C) 1991-2000  Kimmo Suominen, Christophe Wolfhugel
    9 
   10 1) Installation / Customization
   11 
   12 - Create a user named "listserv" on your system, preferably in its own
   13   group (this makes it easier to give access to maintenance users).
   14   You may of course choose another user if you wish.
   15 
   16   The user should *not* have any special privileges. It is *not* an
   17   administrative user.
   18 
   19   You may wish to disable logins on that account, and allow access
   20   only with rlogin (to avoid having a shared password).
   21 
   22   It is also a nice idea to put listserv's home directory on a stable
   23   file system, ie. where there are few risks of running out of space.
   24   In the current release, TULP gives an undefined (which could be
   25   mail loops, but we did not test this) behavior if the file system it's
   26   running on is full. Do not put the directory on a file system
   27   which is vital for the system.
   28 
   29   Create the directory expl in listserv's home directory. If you
   30   prefer using another organization, you'll have to change the
   31   adequate defines in conf.h and Makefile.
   32   
   33   Create the queue dir, relative to TULPDIR (see conf.h).
   34 
   35   TULP's binaries and scripts will be put in /usr/local/etc, all
   36   service files will be in ~/expl and we suggest that you put
   37   the sources in ~/src.
   38 
   39 - Login as root and create some mail aliases (described method
   40   is for sendmail). Aliases are generally stored in /usr/lib/aliases
   41   or /etc/aliases, some sites may have another location, anyway the
   42   system administrator should know about it.
   43 
   44   You must create 3 service aliases:
   45      listman:          address of the listserv manager (you!)
   46      listserv-request: listman
   47      list-errors:      where errors should be reported (generally also you).
   48   These two aliases must of course *not* point to Listserv otherwise you'll
   49   create a deadly loop.
   50 
   51   If you have decided not to use the -request facility in conf.h then
   52   you do not need the listserv-request alias. It is strongly
   53   discouraged not to use the -request facility.
   54 
   55   Ask your system administrator to add "listserv" to the list of
   56   trusted users in the sendmail configuration file (/etc/sendmail.cf).
   57   In order to modify the sendmail configuration file, the system
   58   administrator will need to do the following in most UNIX systems:
   59 
   60   1. Kill the sendmail daemon.
   61   2. edit sendmail.cf adding  the command Tlistserv in the trusted users
   62      section of the file.
   63   3. recompile the sendmail configuration file:  sendmail -bz
   64   4. restart the sendmail daemon:                sendmail -bd -q31m
   65   
   66   This will allow listserv to send mail while defining the appropriate From
   67   envelope.
   68 
   69   NOTE:  Recent versions of sendmail don't use a frozen configuration file
   70          anymore.  Neither do they have the notion of trusted users.
   71 
   72   If you wish to use the test list, also add an alias:
   73      test:          "|/usr/local/etc/deliver test"
   74 
   75   And finally alias listserv to the deliver package:
   76      listserv:      "|/usr/local/etc/deliver listserv"
   77 
   78   Note: if you have Perl installed on your system, use deliver.pl instead. 
   79   You will get more functions, particularly trapping of administrative
   80   requests sent to lists.
   81 
   82 - Issue a newaliases in order to refresh the database. Also rebuild
   83   your frozen Sendmail configuration file if any. The Sendmail
   84   daemon should be restarted in order to be sure that all modifications
   85   have been taken into account.
   86 
   87 - You'll now have to edit the configuration file conf.h in order to
   88   set the parameters according to your system and to your wishes.
   89 
   90   Parse this file carefully in order not to miss anything.
   91 
   92 - Edit helpfile in order to fill it in with your local adresses.
   93   You can also add whatever you'd like to. For example, on my
   94   production version on grasp.insa-lyon.fr I have explanations
   95   on how to retrieve the FAQ archives via the listserv.
   96 
   97 - Check and modify Makefile according to your system. On AIX 3.1,
   98   -D_BSD does not need to be added (if you have compilation errors,
   99   then it's that you have wrong options).
  100 
  101   Don't forget to put the proper directories.
  102 
  103 - Edit and customize 'deliver' and 'rc.tulp' according to your
  104   system.
  105 
  106 - Issue 'make all' in order to compile all the stuff.
  107 
  108 - Once compiled and linked successfully, issue a make 'install'.
  109   That will copy the executables and scripts to the right place.
  110 
  111   Verify that 'queue' is setuid to listserv (no danger, check the source
  112   to get the confirmation) or delivery of messages in the queue will fail.
  113 
  114 - Copy helpfile, lists and test.* to ~/expl. If you wish to
  115   create new lists, refer to the latter comments and also to tulp(5).
  116 
  117 - After copying the files  helpfile, lists and test.* to ~/expl make sure
  118   the protection mode masks, owner and group for the files in the expl
  119   directory are setup for the listserv owner and group.
  120 
  121 The installation of TULP in now ready, you can now create your lists
  122 and start the application.
  123 
  124 
  125 2) Running TULP
  126 
  127 TULP should be started preferably with the /usr/local/etc/rc.tulp
  128 script. 
  129 
  130 NEVER NEVER NEVER run Tulp as root.
  131 
  132 The daemon should immediately go into background (except if DEBUG was
  133 defined in the Makefile). You should now have the 'test' list ready
  134 for use with one subscriber: the list-manager (listman).
  135 
  136 Important events are filed to the syslog or to the fakesyslog you have
  137 defined.
  138 
  139 You may wish to create a file listname.n in order to enable the
  140 usage of the X-Sequence: field in the header of the resent messages.
  141 
  142 
  143 3) Listserv shutdown
  144 
  145 Normal shutdown is obtained when sending kill -15 to the listserv pid.
  146 shutdown generally does not take more than a few seconds, but when
  147 relaying a message it can be much longer.
  148 
  149 Shutdown may also be done by mail by sending the adequate string to the
  150 listserver. Change it in conf.h !
  151 
  152 
  153 4) Creating a list (delete is reverse operation)
  154 
  155 Creating a list is easy.
  156 
  157 - Choose the list name in order to be at most MAX_FILE-2 long (this name
  158   if called 'listname' for the following text).
  159 
  160   In fact it should not be longer than 12 characters as, too bad,
  161   Posix only requires 14 characters long filenames. If the names
  162   are longer, you'll be system specific.
  163 
  164 - Go to ~/expl and create 'listname.w' containing the welcome
  165   message that will be sent to every new subscriber.
  166   Create 'listname.u' and put in it any user you wish to subscribe
  167   immediately (see test.u format), otherwise just 'touch listname.u'.
  168   The file *must* exist. Create the file listname.n if you wish
  169   to have Sequence numbers.
  170   If you wish to have archiving, issue 'mkdir listname'.
  171   Verify that these files are mode 700.
  172 
  173   Customize the header of list.u (see file tulp(5)) according to your
  174   needs.
  175 
  176 - The file list.n, if existing contains the number (in text) of the next
  177   message. If present, the X-Sequence: field will be added to every
  178   forwarded message.
  179 
  180 - Edit the file lists and add the new list if you wish to have that list
  181   appear in the catalog.
  182 
  183 - Edit (as root) /usr/lib/aliases and alias the new list name to the
  184   deliver script and refresh the aliases database.
  185   Also put the -request alias (to a human) if you have choosen
  186   the adequate compilation option in conf.h.
  187   Exemple:
  188         tulp:           "|/usr/local/etc/deliver tulp"
  189         tulp-request:   listman
  190   (or use deliver.pl preferably if you have Perl).
  191 
  192 The new list is ready, you don't need to restart the listserv.
  193 
  194 Don't forget to subscribe to the new list, specifying address 'listname@host'
  195 as subscriber email.
  196 
  197 
  198 5) Miscellaneous
  199 
  200 This listserv is used successfully in coordination with INN  in order
  201 to establish a full bi-directionnal gateway between mailing lists and
  202 Usenet newsgroups.  This works fine only if listserv if the 'head' of
  203 the gatewayed list/group.