Subject: Trying to Configure Pine

From: Aaron Herskowitz <[email-masked]>
Date: Wed, 10 Nov 93 00:59:52 -0500

Thanks to Mark for his comments and explanations.  I hope that everyone didn't  
interpret my enthusiasm for NeXTSTEP as a monogamous operating system stance -  
we have platforms running Ultrix, HP-UX, SunOS, MS-DOS, Mac.  We are realistic  
about other OSs, we just think that the NeXTSTEP environment currently suits  
*our* user's needs (in both software development and ease of use) even if it  
isn't anywhere near widely accepted.

I can understand the Pine programmers not supporting NeXTmail; I wouldn't  
expect that.  But I was wondering if any Pine users had taken it upon  
themselves to write something for Pine that can read/send in the NeXTmail  
proprietary format.  I guess I can assume that there aren't too many NeXT users  
on this list  :-)

I would still like to know if any of my problems that are not totally NeXT  
related can be solved:

1. if /usr/spool/mail/username doesn't exist, Pine complains and refuses to  
open the INBOX (understandable since it isn't there.)  Even if new mail arrives  
to /usr/spool/mail/username, the user will not be notified since the INBOX  
folder is not open.  I realize that the cause of this is created by the NeXT  
GUI mail application, but is there a simple work-around?

2. does a hostname need to contain the domain name to enable full name  
expansion in the addressable fields?  If I set "user-domain" in pine.conf, full  
name expansion doesn't work.

Thanks again,
Aaron
---
Aaron Herskowitz     [NeXTmail and MIME Welcomed]    E-Mail: [email-masked]
Academic Systems Manager, Technical and Network Services   Voice: (814)332-2755
Allegheny College, Meadville, Pennsylvania                   Fax: (814)333-9699

---

From: Mark Crispin <[email-masked]>
Date: Fri, 12 Nov 1993 03:12:50 -0800 (PST)

On Wed, 10 Nov 93 00:59:52 -0500, Aaron Herskowitz wrote:
> if /usr/spool/mail/username doesn't exist, Pine complains and refuses to

> GUI mail application, but is there a simple work-around?

If you set your INBOX-PATH variable to be INBOX, this should correct this
problem.