Subject: IMAP and rsh

From: [email-masked] (Mark L. Chang)
Date: 1 Nov 1994 19:50:56 -0500

Currently, the machine that I want to access via the IMAPd daemon does not
allow rsh access (rlogin type) because the sysadmin sees it as a security
hole too big to justify.

Any way around this?

Also... I've got my own machine set up, but I didn't configure IMAPd for
it when installing pine... is there an easy way to do this and does the
archive contain sample imapd.conf files? 

Thanks.
-- 
---------------------------------------------------------------------------
Mark L. Chang | http://teal.ece.jhu.edu/~mchang | [email-masked]
---------------------------------------------------------------------------

---

From: Mark Crispin <[email-masked]>
Date: Tue, 1 Nov 1994 20:16:36 -0800

> allow rsh access (rlogin type) because the sysadmin sees it as a security

If you use an explicit port specification, Pine will not try rsh access. 
IMAP is normally on port 143.  If your server is called imap.foo.edu, try:
 {imap.foo.edu:143}inbox
              ^^^^ the :143 is the ``use port 143'' specifier

> archive contain sample imapd.conf files? 

The file imap/README documents how to set up an IMAP server, as does the 
Pine technical notes.

Do not use the imapd.conf capability.  This is evil, wicked, black magic, 
and sorcerer's apprentices who play with it will end up fighting a horde 
of water-bucket carrying brooms flooding the castle.  ;-)

In all seriousness, these files are used for special experimental purposes
at UW to override the normal behavior of imapd.  There are several highly
undocumented and bizarre side effects that occur when you change these
settings from their standard positions.  The form, and function, of any of
these is subject to change from version to version without notice.  It is
likely that if you depend upon anything done by this files you will be
very unhappy when you install the next version. 

imapd automatically configures itself for proper operation without any
configuration file.  If you use imapd.conf without having an intimate
understanding of what is going on in the source code, you're almost
certainly going to break both imapd and Pine on that system.  I've been
bit a few times myself (testing a particular experiment and forgetting to
delete it afterwards), and I wrote it! ;-)