
The configuration presented here is intended to be that used by a
"normal" internet site. This means that the site  should  have  a
direct IP connection to the Internet and make use of the DNS.

This is intended to be a first step that will get messages deliv-
ered to a few selected people and make very  little  use  of  the
more advanced features.

To configure this version for use, do the following.

1.   Run  make  install  in this directory. This will install the
     files in the correct places.

        % ./make install


2.   Edit the installed tailor file (/usr/lib/pp/tailor) to  con-
     figure  the  site  specific parameters near the beginning of
     this file.

        % vi /usr/lib/pp/tailor


3.   Add the contents of the file isoentities.add to your  system
     wide isoentities file (usually either in /usr/etc). You will
     probably need to be root to do this step.

        % su
        Password:
        # vi /usr/etc/isoentities

     This step is useful as a backup anyway, but if you have  all
     your  applications  registered  in  the X.500 directory, you
     should add such an entry to that too. A sample entry is giv-
     en  in  x500.sample. This should be added (after editing) at
     the same position as your other local applications.

        % dish -u <manager>
        Welcome to Dish (DIrectory SHell)
        Enter password for "<manager>":
        Dish -> moveto cn=<machine>
        Dish -> add "cn=pp qmgr" -objectclass "applicationEntity & quipuObject"


4.   Change     directory     to     the     tables     directory
     (/usr/lib/pp/tables).

        % cd /usr/lib/pp/tables


5.   Edit the users file and add a few local users using the for-
     mat given in that file.

        % vi users


6.   Edit the ch.local file and add the same users to that  file.

        % vi ch.local


7.   Run dbmbuild (found in directory /usr/lib/pp/cmds).

        % /usr/lib/pp/cmds/dbmbuild -v


8.   Run  ckconfig  (found in the directory /usr/lib/pp/cmds) and
     see if everything looks reasonable.

        % /usr/lib/pp/cmds/ckconfig


9.   Start the pptsapd and the qmgr

        % /usr/lib/pp/cmds/pptsapd >& /dev/null
        % /usr/lib/pp/cmds/qmgr >& /dev/null


10.  Add an appropriate line to the /etc/inetd.conf file to allow
     smtp incoming connections. An example might be

        smtp stream tcp nowait pp /usr/pp/cmds/chans/smtpsrvr smtpsrvr smtp

     After this you will need to do a kill -HUP on the inetd pro-
     cess to get it to reread the configuration file.  If you are
     running  another smtp service (e.g sendmail), make sure this
     is no longer running.

        % su
        Password:
        # vi /etc/inetd.conf
        # ps -x
        # kill -HUP <pid>


PP should now be ready for use. At this point it is worth testing
out a few things. Some simple tests are as follows:

Submit a message to local user you configured in and see if it is
delivered. This is easiest done by using  the  PP  supplied  mail
program.   This is normally installed in the /usr/lib/pp/cmds di-
rectory. A command such as

   % /usr/lib/pp/cmds/mail -s test pp < /etc/motd

is a good start.

Submit a message to some other local machine using the same  syn-
tax as above.

If  that  works too, try a message to someone further afield. Use
the same method, just pick a remote address for testing.

This configuration is meant only to get you started. Once this is
running  you will almost certainly want to do some of the follow-
ing.

o    Add all your users to the users and ch.local table by  means
     of some shell/awk script from local databases.

o    Create some lists to be expanded by the list channel.

o    Rebuild the domain and channel tables to take account of lo-
     cal knowledge.

o    Add in the ability to use X.400. This is at  present  rather
     too complicated to automate.

Full details for all these procedures are laid out in Volume 1 of
the PP manual.

