Subject: PINE on the sun

From: Arthur Snoke <[email-masked]>
Date: Wed, 27 May 1998 16:38:48 -0400 (EDT)

I have been using PINE on a Unix system (sun) for about a month, but I
still need to use two other mailers to handle all my incoming mail:
sun's mailtool to handle sun attachments, and netscape to handle messages
in which the text has been encoded using ISO-8859-1 character set.

I posted messages to the list regarding these two points on May 11, and
the only response I got was a pointer to a c program and perl script that
should be able to translate sun attachments into base64 encoding.
Unfortunately, the referencing in the documentation accompanying those
programs was specific to metamail and I could not figure out how to change
my mailcap file.  My mailcap.unx file had some lines related to my second
problem (character sets), but I must be leaving something out.  The fact
that I can view ISO-8859-1 encoded files (and print them) using netscape
tells me my operating system has the capability for this.  (More and more
messages seem to be using the ISO encoding. It seems to be the default for
netscape.)

There must be someone out there who has encountered and solved these
problems.  Please share.

Arthur Snoke

-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Jim Sander <[email-masked]>
Date: Wed, 27 May 1998 17:02:16 -0400 (EDT)

Just thought I'd let you all know I found my problem The solution came
to me in that state between waking and sleep... but it worked.

   What had happened is that I was locking things down to prevent users
from arbitrarily executing commands by setting the shell and speller
variables in pine.conf.fixed - and that much worked. However, when you
actually tried to use the editor or speller, you'd erase your message.

   I found that the culprit was actually the setting operating-dir=~ which
aparently prevented temporary files from being created by the external
programs. (that's my guess anyway) Allowing users to access files outside
their own directory root is OK with me- that's what chmod is for. So,
problem solved- just remove this restriction.

   Hope this helps someone else...
-=Jim=-