
MAKE:
        To install the popper you need to determine which OS is supported
    and run the appropriate make command.  Just run make for the list of
    available builds.

        There are a few options to consider when doing a build.

        1) KERBEROS - Define this value if you want to build a kerberos IV
                      server.
        2) AUTHFILE - Define this value to the file you want which only
                      allows users listed in the file to have popper access.
                      Ex: -DAUTHFILE=\"/etc/authfile\"
        
	3) AUTH - Means that your system supports special authorization
		  mechanisms like shadow passwords or special crypt
		  programs.  The make files have been setup for this
		  as best as I can tell.  SunOS4.x is the only one which
		  does not support this by default since it requires the
		  C2 code to be loaded which is not done by default.  If
		  you support shadow passwords on SunOS4.x then define
		  SUNOS4 and AUTH in the make.sunos makefile.

	4) RPOP - This feature allows the pop client to use the hosts.equiv
		  and .rhosts files for system/user validation.  This feature
		  is not recommened since it is far to easy to spoof a system
		  on a PC or a Mac.

	4) Temporary pop files are placed in the mail spool directory by
	   default.  /tmp is consider this to be a security risk and a
	   system reboot will probably clear the temporary .user.pop files.
	   You may want to change the value of POP_DROP, POP_TMPDROP, and
	   POP_TMPXMIT in the popper.h file.  Many sysadmins who have may
	   user (say 200 or more) create a separate spool directory for
	   popper files.  /usr/spool/poptemp would be a good choice.
	   Permissions should be 1777 (drwxrwxrwt) on the directory.

	5) Mail spool directory.  Some systems have symbolic links from
	   /usr/mail to /usr/spool/mail.  Some don't.  I've tried to guess
	   at which OS uses /usr/man and which uses /usr/spool/mail.  Some
	   times I guess wrong.  Make sure you check this before

	Notes:

	SCO - some versions of SCO use the crypt_d library, others the
	      crypt_i library.  This distribution assumes crypt_d.

	IRIX - The default spool directory is /usr/mail, some systems
	       use /usr/spool/mail.

INSTALL:
	After running make on the appropriate OS, you need to move the
    popper to a known location.  There is no one correct place.  Many
    sysadmins prefer /usr/lib, but /usr/etc, /local/lib, /local/etc, or
    /usr/sbin are all good choices.

	Modify your inetd.conf file to contain the following line.  You
    may have to modify it to support your version of the file:

pop3    stream  tcp     nowait  root    /usr/local/etc/popper   popper -s

	Modify your services file to include the following line.

pop3            110/tcp                         # Post Office

	Restart inetd with a kill -HUP <inetdpid> and you should be all
    set.

DEBUGGING:
	Telnet to the popper port.  If you receive an error message

    "connect: Connection refused"
	    check your services file and make sure the port name "pop3" is
	spelt the same way.  This message is telling you that inetd is not
	servicing that port.
    
    or 

    "connect: Connection closed"
	    or similar messages indicate that inetd has the correct port
	assigned to the popper, but that either the program cannot be
	located or it is failing on startup.


	What you are looking for is the startup banner.  If you see the
    following line then you have correctly installed the popper as far
    as inetd is concerned.

	"+OK UCB Pop server (version 2.1.3-R1) at <system name> starting."

	Now you need to run two commands to authorize yourself.  You
    should make sure you have a message or two queued up so you can
    make sure the popper is pointed at the correct mail spool file.
    Don't be alarmed, the password is echoed back, that's the way it
    is suppose to work:

    user <your user name here>
    +OK Password required for <your user name hsers>
    pass <your password>
    +OK mark has 2 message(s) (4123 octets).

	You have successfully authorized yourself.  You have two messages.
    At this point you can enter "quit" to exit.  list and uidl are two
    commands to list out each message by size and unique ID respectively.
    If you get this far Eudora or any other pop client will not have a
    problem communicating with your popper.

