Subject: imap installation doc?

From: Dan Mandell <[email-masked]>
Date: Mon, 8 Mar 1993 22:50:28 +0500 ()

We have been using NFS to mount the mail directory on HP systems, but
we are finding that if the arrangement is susceptible to any failure of
mail server or network.  The login procedure checks a NFS directory for
new mail and never completes the login process.

So I have been attempting to install the IMAP demon received with the Pine
3.03 distribution. Without benefit of installation instructions, I'm not
sure where we stand.  I have made an entry in our inetd.conf, and
inetd.sec and services files, but imap seems dysfunctional: I can neither
telnet to the port assigned this service, nor execute the imapd demon as a
background task.  When invoking imapd, it displays the following
* OK jade.saintmarys.edu IMAP2+ Service 6.6(43) at ...date 
but then seems to die.  

Dan 

--
=====================================
Dan Mandell, Academic Computing       
Saint Mary's College                
Internet: [email-masked]

---

From: Mark Crispin <[email-masked]>
Date: Mon, 8 Mar 1993 22:29:41 -0800 (PST)

Dan -

     It doesn't sound like you have done anything wrong.  More specifically,
it seems that you've done everything necessary.  It sounds to me as if it is
starting up and then crashing.  There should be installation instructions in
the c-client README file.  Here's an extract:

----------------------------------------------------------------------------

     The Unix servers ipop2d, ipop3d, and imapd should be installed in
a system daemon directory, and invoked by your /etc/inetd.conf file
with lines such as:
	pop	stream	tcp	nowait	root	/usr/local/etc/ipop2d	ipop2d
	pop3	stream	tcp	nowait	root	/usr/local/etc/ipop3d	ipop3d
	imap	stream	tcp	nowait	root	/usr/local/etc/imapd	imapd
You may also have to edit your /etc/services (or Yellow Pages,
Netinfo, etc. equivalent) to register these services, e.g.
	pop		109/tcp		postoffice
	pop3		110/tcp
	imap		143/tcp

     If you want to enable the rimap capability, which allows users with a
suitable client and .rhosts file on the server to access IMAP services
without transmitting her password in the clear over the network, you need
to have /etc/rimapd as a link to the real copy of imapd.  Assuming you have
imapd installed on /usr/local/etc as above:
	% ln -s /usr/local/etc/imapd /etc/rimapd

     Technical note: rimap works by having the client routine tcp_aopen()
invoke `rsh _host_ exec /etc/rimapd' in an child process, and then
returning pipes to that process' standard I/O instead of a TCP socket.  You
can set up `e-mail only accounts' by making the shell be something which
accepts only that string and not ordinary Unix shell commands.

----------------------------------------------------------------------------

     I assume you also know that you have to send a HUP signal to inetd (or
reboot your system) before any changes to /etc/inetd.conf take effect?

     Try running imapd on your terminal, perhaps under gdb, and see if it
crashes in any obvious way.  If you run it on your terminal, you'll get a
	* PREAUTH jade.saintmarys.edu IMAP2+ Service 6.6(43) at ...date
instead of
	* OK jade.saintmarys.edu IMAP2+ Service 6.6(43) at ...date
that just means it's meaningless to log in (since you're already logged in).

     I don't have any HP systems here, and the HP port was supplied by a user.
So I can't advise you much further at this point.  But, if you can't figure it
out (that is, if the cause of the problem isn't obvious when you run it on
your terminal), contact me again.  Perhaps if you can let me on your system
I'll be able to figure it out and give you a fix/instructions on what to do.

-- Mark --