From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?
Status: RO
X-Status: 

                                       
Not yet, but Kerberos support is planned for a future release of Pine. If
you have access to Kerberos or AFS compatible IMAP clients already, the
following information may be useful. 
  
The current version of imapd does not support AFS or Kerberos
authentication.  However, the routine which validates authentication is
designed as a drop-in module, to allow you to replace with alternative
authentication schemes such as AFS, Kerberos, S/Key, etc. 
   
This routine is server_login(). Depending upon which version of c-client
you have, it is either in the os__xxx_.c (where _xxx_ is the name of your
port) or it is in a file named log__yyy_.c which is included by the
os_xxx.c file. 
   
The log__yyy_.c is usually log_std.c (std for "standard UNIX"), but it may
be log_sv4.c (SVR4) or a couple of other variants. This file only contains
that one routine, so it should be a simple matter to modify that file and
rebuild imapd. 

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?
Status: RO
X-Status: 

                                       

No.  Neither Pine nor PC-Pine currently support POP's offline mail model
(wherein pending mail is pulled from the mail server to the local machine
and deleted from the server).  However, it is likely that this model will
be supported, with a choice of either IMAP or POP as the access protocol,
in a future release. 

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?
Status: RO
X-Status: 



Using the Tenex format for INBOXes allows multiple sessions (or mulitple
users, subject to the usual access controls) to have *almost* full
Read-Write access to the INBOX. The only limitation on full RW access is
that if there are multiple sessions at a given moment, no one can do an
Expunge. However, message state changes (e.g. marking a msg as deleted)
*can* be done, and this state is preserved across sessions. 
   
If an explicit Expunge command fails, it will say so and tell you that the
mailbox is in use by another process. When there is only one session left
using that mailbox, expunge will resume working again. 
   
In contrast: the normal Berkeley style folders can have only one RW client
at a time, so _given the current software_ the latest session steals the
RW lock away from any previous session, with the earlier session becoming
RO. 

NOTE:  Mailbox format for INBOX is a function of the mail transfer agent
(sendmail, tmail), not the mail user agent (Pine), so this is a decision
for sys/mail admins, not for regular Pine users. 

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?
Status: RO
X-Status: 

                                     
In Unix and PC Pine 3.90 and higher, the Release Notes (Press "R" on the 
Main Menu) contain a section on Configuration, including default file names 
and environment variables.  Almost all personal configuration can be
accomplished through the Setup (S) command on the main menu. 

Unix Pine uses three configuration files:  a system-wide defaults file, 
a system-wide non-overridable settings file and a personal coniguration file.
If you need to generate a "blank" copy of the system wide configuration
files, run "pine -conf > /usr/local/lib".  If, for some reason, you need to 
generate a blank personal configuration file, run "pine -P pinerc.blank".
   

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?
Status: RO
X-Status: 

                                       

Pine does not support some older terminals (e.g. tvi925, WYSE-60) very
well. Some problems can be overcome with a proper termcap entry, but
others, such as handling cursor keys, do not have a good solution. 

From dlm@shivafs.cac.washington.edu Wed Aug 24 09:26:18 1994
Date: Tue, 10 Feb 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I configure Pine to not leave mail in /usr/spool/mail?
Status: RO
X-Status: 

You have several options:
   
    1. Leave inbox in /usr/spool/mail, but turn on the Pine option to
       prompt users to move read messages to a folder in their home
       directory upon exiting Pine. 
    2. Modify your mail delivery program to deliver mail directly into
       the user's home directory, and specify that inbox-path in your
       global pine.conf (See the "tmail" program on
       ftp.cac.washington.edu for an example.) 
    3. "touch mail.txt" in each home directory, which will cause Pine
       (upon startup) to pull mail from /usr/spool/mail into ~/mail.txt
       -- however, mail.txt will be a Tenex-format, rather than Berkeley
       mail format folder (faster, but non-standard). 
    4. Link in the "mbox" driver when you build Pine. This driver will
       (upon Pine startup) pull mail from /usr/spool/mail into ~/mbox,
       which will be a Bky-format folder. 
       
   
