Subject: Pcpine (Win95) in Lab environment

From: Jon Speer <[email-masked]>
Date: Tue, 23 Jul 1996 11:58:11 -0700

We would very much like to move PCPine into our campus Win95 labs. This of
course means that we can not store a login in the .pinerc file.  I would
appreciate feedback on dealing with any of the following issues:

1. After logging in initially, PCPine asks for a login and password again to
compose, and again for creating/editing folders.  This doesn't seem to be
the case if the login name is present in the .pinerc file.  How might we
avoid this?  We have considered writing a script to write this into .pinerc
each time they log into the Novell server (same login), but it seems this
could be done by PCPine itself by simply storing it into the .pinerc file
(we use revr dist between each user).

2. The .addressbook that our users have on Pine is in a format readable by
PCPine, but there doesn't seem to be a way to use it unless you copy it
over, which is of little use. 

3. Our users often rely on putting in another user's (on our system) login
on the TO: line and having pine do the user name translation and
automatically entering the user's first and last name.  This would be a
helpful option for PCPine to do the same translation there, and even moreso
to do this with the user's login so as to input the First and Last name in
the .pinerc file.  This would avoid asking the user to enter a FROM: value
every time they compose (which, here, is after they are asked to relogin again).

4. We are aware of the benefits of ACAP once finalized and in use, so I
wonder if this is in the works for PCPine.

Thanks,

Jon Speer
Information Technology
Lewis & Clark College
Portland, OR