Subject: Step-by-step SCO, imapd and PC-PINE

From: Steve Inners <[email-masked]>
Date: Tue, 14 Mar 1995 11:54:58 -0800 (PST)

Thanks to:

Vladimir Solnicky <[email-masked]>
Ramon J Hontanon <[email-masked]>

for their instrumental advice (name used in /etc/services must match name 
used in /etc/inetd.conf).  The initial stage of reading UNIX inboxes from 
PC-PINE at my site was a success!

To those who requested the "Big Secret" if and when I got it all together 
.... here is what I learned:

=========================================================================

Setting up PC-PINE to allow reading an INBOX located on an SCO
machine

This step-by-step assumes:

Proper installation of winsock.
tcpman.exe as the PC-tcp element.
The user has an account on the SCO machine.
The email system on the SCO machine is functional.
You are using the pre-compiled SCO code for Pine3.91.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

1)   Place imapd (found in the pine3.91/bin directory on the pre-
     compiled SCO distribution) in the /etc directory with the
     mode and ownership as follows.

-rwx--x--x  1 bin  bin    427500 Mar 08 09:41 /etc/impad

2)   Edit /etc/inetd.conf to include the following line:

imap   stream  tcp    nowait   root   /etc/imapd    imapd

3)   Edit /etc/services to include the following line:

imap   143/tcp

4)   Issue a SIGHUP (kill -1) to inetd's PID in the process table. 
     This will cause inetd to re-read the inetd.conf file (no need to
     reboot).

5)   Edit your PINERC file (related to the PC-PINE installation). 
     Note: PINERC will not exist until you have attempted to run
     PC-PINE the first time.  Required fields for remote access of
     your INBOX are:

user-id=
smtp-server= <------ Needed to COMPOSE mail
inbox-path=<------ Needed for accessing INBOX
incoming-folders=
default-fcc=
postponed-folder=

The user-id field needs to contain the logname of the individual
who's INBOX we are accessing.

The smtp-server field is the name of the server that has an smtp
channel setup for email.

The inbox-path is how you latch onto the imapd server.  The
syntax is: inbox-path={machine}/usr/spool/mail/logname
where machine is substituted for the hostname of the server you
configured imapd on and logname is the users login name.

The incoming-folders, default-fcc and postponed-folder are
optional.  If you plan on maintaining one set of folders, you will
have to use syntax similar to the syntax used in the inbox-path parameter.

This method of configuration will require the user to supply his
UNIX password to gain access to his inbox.  In my particular
scenario, this is OK.  You may try the rimapd concept to alleviate
the need for password provision (?).  The rimapd concept is
discussed in the distribution documentation.

-Steve				[email-masked]
###################################################
Perspective: No matter where you go, there you are.
###################################################
Yea yea yea .. been there .. done that.