	      _  _ ____  _ ____ ____ ___  ____ _  _ ____
	      |\/| |__|  | |  | |__/ |  \ |  | |\/| |  |
	      |  | |  | _| |__| |  \ |__/ |__| |  | |__|

			     Release 1.94
			       INSTALL
  --------------------------------------------------------------------------

-> Current users of Majordomo whom are upgrading will want to    <--
-> read the Changelog for details on what has changed between    <--
-> versions of Majordomo.				         <--

-> In particular, NOTE THE CHANGES TO THE CONFIGURATION FILE.    <--
-> Several new variables have been added to sample.cf, so check  <--
-> it out and merge your existing majordomo.cf with the supplied <--
-> sample.cf							 <--

Steps to install Majordomo:

1) Pick a group and user ID for Majordomo to run under.  Usually this
   is "majordomo.daemon".  If you're this group, you can do all the
   majordomo management functions (creating new lists, etc.) without
   having to "su" to Majordomo.  You can create and use a group id
   other than "daemon" if you want, but if you do, that uid needs to
   be a "trusted" user as far as Sendmail is concerned (i.e., the user
   name needs to appear on a "T" line in your sendmail.cf file).

2) Choose a directory for Majordomo to install under.

3) Edit the Makefile, defining where Perl, the Majordomo home
   directory, and the user and group that Majordomo will run under.
   If running on a non-POSIX system, comment out the POSIX SECTION in
   the Makefile.  Under POSIX, wrapper must be setuid "root", even if
   the programs will be running as something other than "root" (i.e.,
   "daemon"), or it won't work.  The symptom of this is that Perl
   starts bitching about security violations and "unsafe usages".

4) Do a 'make wrapper' to verify that the wrapper program compiles
   cleanly.  

5) Do a 'make install' to install the Majordomo programs.  

6) Read and edit the Majordomo configuration file, 'majordomo.cf', in
   the Majordomo home directory (or as defined in the Makefile).
   The .cf file is "eval"ed into majordomo (so it needs to be valid
   PERL), and sets several things:

    $whereami		What machine am I on?
    $whoami		Who do users send requests to me as?
    $whoami_owner	Who is the owner of the above, for problems?
    $homedir		Where can I find my extra .pl files?
    $listdir		Where are the mailing lists?
    $digest_work_dir	Where does digest do its work?
    $log		Where do I write my log?
    $mailer		What program and args do I use to send mail?
    $filedir		Where should I look for files for "get" and "index"?
    $filedir_suffix	What suffix should I use for the file directory?
    $index_command	What command should I use for "index" requests?
    $sendmail_command   Where the sendmail program resides.



    If the following are set, Majordomo uses FTPMAIL to handle "get"
    and "index" requests, rather than processing those requests
    itself.  FTPMAIL will use the $filedir and $filedir_suffix
    settings to determine where to look for the files on the host
    specified by $ftpmail_location.

    $ftpmail_address	What FTPMAIL server should I send requests to?
    $ftpmail_location	What host should FTPMAIL look for my files on?

    See the "sample.cf" file for examples.

7) Chdir to the Majordomo home and run the configuration test script:
   # cd ~majordomo
   # ./wrapper config-test 

   This should check for the proper configuration of Majordomo. Fix
   any errors, and run again.

8) Add the majordomo-related aliases to your Sendmail alias file.
   This can either be /etc/aliases, or if you are using a more recent
   version of Sendmail (8.6 or above) a cleaner approach is to add an
   alias file specifically for Majordomo aliases by adding another
   "OA" line to /etc/sendmail.cf:

   OA/usr/test/majordomo-1.94/majordomo.aliases

   Whichever method chosen, add the following aliases for Majordomo
   itself:

    majordomo: "|/path/to/majordomo/wrapper majordomo"
    owner-majordomo: you,
    majordomo-owner: you

   Note the program name (majordomo) must not be a full path name.
   Also look at 'sample.aliases' for additional examples.

9) Test the configuration again by creating an empty file 'test' in
   $listdir, and issue a 'lists' command to Majordomo:

      % touch ~majordomo/lists/test
      % echo 'lists' | mail majordomo

   If everything is working correctly, you should get a message back
   from Majordomo, and not Mailer-Daemon.



That's it!  To create new lists, read the NEWLIST file.

