Subject: 2 pine/imap questions - shared folders; remote authentication

From: [email-masked] (Michael Fox)
Date: Thu, 29 Jul 93 23:08:29 EST

Background:

We are running pine3.07 (hacked, see below), imapd 3.0, and testing
ECSmail 1.0, in the process of converting from a home grown mail system
on a Prime.  We have a Sun 670 (thumper) as a mailbox server running imapd
with the /etc/rimapd link for remote pre-authentication.  We also have
a Sun Sparc 2 as an nntp server, running INN, and use trn as the client
news reader.  A number of other Suns and PCs access these services, and all 
the Suns run Sunos 4.1.3.

The Pine hack is to emulate "noticeboards" as we new them on the 
Prime system, which are really shared folders.  To make them 
visible to users in the normal folder menu, 2 extra entries are
displayed, <notices> and <parcels> which in reality point to
{thumper}/var/spool/mail/postnotices and {thumper}/var/spool/mail/
postparcels.  This works OK for pine, but not for ECSmail.

Question 1: We have noticed extended BBOARD functionality in imapd,
will this be used in Pine 3.85, and how?  Is it just for NNTP type
services, or can it be used like we are trying to do, pointing to
shared folders somewhere?

Question 2: Remote authentication works for some users but not others,
who seem to us to have identical configurations - same home system,
same unix groups and netgroups, same .pinerc, and all can use rlogin
and rsh OK.  We cannot pick the problem - anyone have any pointers
or procedures we could follow to try and solve this ( the same 
problem existed with imap 2 as imap 3, and with the original
unhacked pine)

Thanks - Michael Fox, Department of Conservation and Natural Resources
         Victoria, Australia

---

From: Mark Crispin <[email-masked]>
Date: Thu, 29 Jul 1993 11:30:41 -0700 (PDT)

On Thu, 29 Jul 93 23:08:29 EST, Michael Fox wrote:
> will this be used in Pine 3.85, and how?

Yes.

>  Is it just for NNTP type

Shared folder such as you describe are also under development.  We're doing it
a bit differently, but I think that the new stuff in 3.85 will lay down a lot
of the groundwork to make noticeboards a lot easier to do.

> problem existed with imap 2 as imap 3, and with the original

Check their .cshrc, etc. file to make sure that no extraneous output is coming
out when an rsh is done.  Such output would confuse the rimap opening code in
c-client/imap2.c and make it conclude that it can't use rimap.  Remember,
rimap is simply an exec() of ``rsh serverhost /etc/rimapd''; the IMAP client
runs with no privileges.