By now you have already downloaded the QPopper source code, as described in section A.2. You can unpack this code by using the command zcat qpop.version.tar.gz | tar xvf -
Make sure that you are using the /usr/ccs/bin/make version of make. To make QPopper, cd into the qpopper directory and type make solaris2 Once finished, you should have an executable called popper.solaris2
To install QPopper, you will need to decide where to put the resulting executable and man pages. For the sake of argument, assume that you are installing into /usr/local Copy the popper into the library directory, using cp popper.solaris2 /usr/local/lib/popper Copy the man page into the man directory, using cp popper.8 /usr/local/man/man8/popper.8
To configure QPopper, you need to make it available as a service. Since the popper is only used occasionally, it makes sense to have it start up when someone wants to connect to it.
Solaris does not come with the POP3 service listed in its services file. If you have not already done so, you should add the following line to the /etc/services file:
pop-3 110/tcp # Post Office
Since the popper is a service that is started on demand, rather than running in background, the inetd daemon needs to be informed of its existence. Add the following line to the /etc/inetd.conf file:
# # QPopper POP3 Server # pop-3 stream tcp nowait root /usr/local/lib/popper popper -s
Once you have done this, you will need to make the inetd daemon re-read its configuration file. You do this, by sending a HUP signal to the inetd daemon.
The easiest test for QPopper is to connect up to it via a telnet session and see if you can get a response. Figure 17 shows a sample session.
doug@solaris 12 % telnet localhost pop-3 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK QPOP (version 2.2) at solaris starting. <630.897723195@solaris> USER doug +OK Password required for doug. PASS PPPPPPPP +OK doug has 0 messages (0 octets). QUIT +OK Pop server at solaris signing off. Connection closed by foreign host. |
If you are unable to connect up to the +OK response,
then the popper is not starting for some reason.
Check the /etc/inetd.conf file and
the /etc/services file, then see if killing
and restarting the inetd daemon will improve anything.
Once you have connected successfully, send yourself some mail using the /usr/bin/mail program and see if you can get your mail from the machine, using Netscape or some other POP client.