Subject: pine with Sun's xterm

From: Lucio Chiappetti <[email-masked]>
Date: Wed, 16 Mar 1994 17:26:38 +0100 (MET)

I have been using for a long time Pine on my DECstation.
We are now starting to use Pine (3.89) as mail agent in our institute,
both on DECs and on Suns (we are running OpenWindows 3 under SunOS 4.1.3).

We have an arrangement by which workstation users (as opposed to terminal
users) invoke a command which opens an additional window in which pine
runs. When the user exits pine, the window disappears.

This is essentially an  xterm -e pine (or dxterm -e pine).

Now, what is happening on our Suns using the /usr/openwin/bin/xterm
bundled with OpenWindows, is that a "core" file is left around after
pine exits.
This does not occur with DEC's xterm nor with dxterm.

Apparently, if we insert a "sleep" command,  creating a script like

    pine
    sleep 1

and invoke such script as xterm -e script

there is no core dump. 
However this is not a very elegant solution. 

What is the reason of the core dump (who is dumping core ? pine or
Sun's xterm ?) ? 
Are there any more elegant solution that a sleepy wrapper script ?

---------------------------------------------------------------------------- 
       A member of  G.ASS : Group for Astronomical Software Support          
---------------------------------------------------------------------------- 
Lucio Chiappetti - IFCTR/CNR     | Ma te' vugl' da' quost avis a ti' Orsign  
via Bassini 15 - I-20133 Milano  | Buttet rabios intant te se' pisnign       
Internet: [email-masked]  |                                           
Decnet:   IFCTR::LUCIO           |             (Rabisch, II 46, 119-120)     
----------------------------------------------------------------------------

---

From: David L Miller <[email-masked]>
Date: Wed, 16 Mar 1994 09:30:24 -0800 (PST)

Lucio,

We have not yet completely isolated the cause of the core files.  Until we
get a fix in place, the sleepy wrapper is the recommended work-around. 

Thanks for the report!

--DLM

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Lucio Chiappetti <[email-masked]>
Date: Mon, 21 Mar 1994 19:31:38 +0100 (MET)

Hello,
       I have been PERSONALLY using Pine very happily since 3.05, and
now we are going to have Pine as DEFAULT MAILER for Unix and DOS here
at IFCTR (this is motivated by the fact we are dropping a Vax used by
a good deal of my colleagues here). We have 3.89 happily running on Unix
(Ultrix and SunOS).

In order to use PC-Pine we need to install and configure imapd, using
the distributed binaries. The documentation in Pine Technical Notes (pag. 
13) are quite terse, and in particular at pag. 14 there is a mention of 
two files (/etc/imapdrc and .imapdrc) which are NOT explained ANYWHERE.

We have also retrieved the imap-3.2.tar file and I have extracted a few
files :

  imap-3.2/ANSI/c-client/Internal.DOC
  imap-3.2/ANSI/imapd/imapd.8c
  imap-3.2/RFC1176.TXT
* imap-3.2/README
  imap-3.2/Updates.DOC

but none of them look an installation AND configuration guide.
Where should I look (in the tar file or in the cac.washington.edu
archives) ?

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

Our arrangement will be like the following (there are strangeness
for historical reasons). Please confirm my understanding of how pine,
pc-pine and imapd interact is correct.

There are here two "privileged" machines :

   [A] is a DECstation which is domain nameserver, mail exchanger for
       the domain, and Internet-Decnet gateway

   [B] is a Sun which is NIS server and our main disk file server

Then there are a number of "personal" workstations [X] and PCs [x].  

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

   All workstations [X,A,B] send their internet mail directly. Decnet and
   Bitnet mail is gatewayed to machine [A]
   Mail exits as from "[email-masked]"

   All incoming mail for the domain comes to machine [A], which knows the
   netwide aliases file (kept on [B]), and is delivered currently as :

     - to workstations [X] for their owners
     - to the Vax for most of the others (this will be dropped)
     - to workstation [B] for the "general" unix users

   machine [A] is the only one to have a "special" sendmail.cf

----------

   What we would like now is to have 4 classes of users :

   a) owners of [X], which should continue sending and receiving mail
      from their workstation
   b) generic unix users, which should continue sending and receiving
      mail on [B] 
   c) local users with a PC [x]. They should receive mail in an inbox
      on machine [B] (or [A] ?), read it via pc-pine/imapd and keep it
      on their PC via auto-save feature, and set it from [x].

      - to allow them sending mail we should designate [A] as smtp-server,
        shouldn't we ? 
      - is there any special arrangement needed in sendmail.cf on [A] ?
      - do they need to have an account on [B], or can imapd work 
        without an account ?  

   d) local users with PC [x] which however need access to their mail
      via remote login. In this case we plan to provide them an account
      on [B], and they should be able to use either pine or pc-pine via
      imapd to read all of their mail (new and old).

      - for an imapd user, can|must the inbox be the usual
        /var/spool/mail/user ?
      - can an imapd user also access a set of folders on a private
        directory (we would like to have read mail stored under the
        user login directory, and not on /var, for quota reasons.

      - is there any preference to have imapd on [A] or [B] ? 

-----------

Is all of this sensible and what are the steps to configure imapd (pointers
to documentation files to read will be appreciated) ?

---

From: David L Miller <[email-masked]>
Date: Mon, 21 Mar 1994 14:59:59 -0800 (PST)

Lucio,

It sounds like you have found most of the documentation we have.  Basically,
you copy the imapd binary to the appropriate directory and add a line to the
services and inetd.conf files.  Then send a SIGHUP to the inetd process and
you should be ready to go.  The imapdrc and .imapdrc files are only used 
in very unusual configurations that you probably will not be using.  

Your configuration looks pretty good.  One caution is that if the [X] 
workstations are NFS mounting any of their folders, you should use IMAP 
to access them directly from the system that physically stores them.  
Pine and imapd have trouble trying to lock files on an NFS mounted 
filesystem.

The IMAP only clients need accounts on the server, but they do not
necessarily need a login shell.  The INBOX is usually in the usual system
location, but can be moved with appropriate /usr/local/lib/pine.conf or
~/.pinerc entries. 

Thanks for the request!

--DLM

---

From: Pierre Roy <[email-masked]>
Date: Tue, 22 Mar 1994 00:18:46 -0500 (EST)

Hi,
is imapd compatible with pop readers, Can i say to the pop readers to 
use impad at port 117 ( ithink)???

Thanks

Pierre Roy Porretta                         
Ecole de technologie superieure (ETS)          Tel:(514) 289-8883
AEETS                                          Fax:(514) 289-9480
e-mail:[email-masked]
       [email-masked]

---

From: David L Miller <[email-masked]>
Date: Tue, 22 Mar 1994 08:44:04 -0800 (PST)

Pierre,

No, but the UW IMAP distribution contains ipop2d and ipop3d servers.  Get 
mail/imap.tar.Z from ftp.cac.washington.edu.

Thanks for the request!

--DLM

---

From: Terry Gray <[email-masked]>
Date: Tue, 22 Mar 1994 09:01:40 -0800 (PST)

Pierre,
Alas, no.

IMAP is a functional superset of POP, but not a syntactic superset.
In other words, the two protocols are not compatible.

I know of one POP client (POPmail from U Minnesota, I think) that can be
configured to use either POP or IMAP servers.  (But, in POP tradition, it
will delete messages from the server after retrieving them.)

-teg

p.s. IMAP's default port is 143.