From owner-pine-info@cac.washington.edu  Sun Jan  1 00:35:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28396;
	Sun, 1 Jan 95 00:35:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26427;
	Sun, 1 Jan 95 00:32:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26421;
	Sun, 1 Jan 95 00:32:49 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA25820; Sun, 1 Jan 1995 03:32:03 +0500
Date: Sun, 1 Jan 1995 03:32:03 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: Ava Mckittrick <CYBRNURS@ix.netcom.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Updating Pine
In-Reply-To: <3e2sql$s67@ixnews2.ix.netcom.com>
Message-Id: <Pine.SOL.3.90.950101032814.25703H-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 746

On 31 Dec 1994, Ava Mckittrick wrote:

> Unix shell account using bin/bash
> I telnet to my account from ix.netcom.com
> using pine 3.89 heard update/grade new and improved.
> Pine menu gives me opportunity to select an upgrade and
> then dl me a big mondo Pine.zip file to my shell account.
> Do i need to bring this pine.zip back to my pc and unzip
> and then do the installation by ftp the files/files back?
> Any help would be appreciated..
 
The upgrade option in Pine is for PC-Pine, not for the Unix version you
use on your dial-up shell account.  You need to badger your system
administrator to upgrade to Pine 3.91.  It isn't something you can do
yourself. 
 
-------------------------------------
Chip Old   <fold@mail.bcpl.lib.md.us>



From owner-pine-info@cac.washington.edu  Sun Jan  1 05:19:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04724;
	Sun, 1 Jan 95 05:19:05 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29848;
	Sun, 1 Jan 95 05:12:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29842;
	Sun, 1 Jan 95 05:12:34 -0800
Received: by hobbes.twntpe.cdc.com; Sun, 1 Jan 95 21:11:09 -0800
Date: Sun, 1 Jan 1995 21:11:07 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Marty Brenneis <droid@nbn.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Still can't open INBOX
In-Reply-To: <D1p1IC.82A@nbn.com>
Message-Id: <Pine.SOL.3.91.950101210817.29909B-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 31 Dec 1994, Marty Brenneis wrote:

> So I still can't get pine to find my host.
> I set the inbox to match that shown in the manual (yes, I did
> insert my host's name). No matter how I format the name of the host
> I get an error #11004 that states it can't find the host. I can
> ping the host with no problem. I can access my mail with the Netmanage
> mail program (bleah). I am using Netmanage Chamelon Sampler for the
> TCP/IP winsock stuff. Other clues, I can read news from the news site
> here.
> 
> Anyone got more hints?
	
	The info-pine<--->comp.mail.pine gateway has been down....and
maybe I missed some discussion on this.....but...

	What do you get when you do:

telnet hostname 143

	
Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Sun Jan  1 18:52:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16368;
	Sun, 1 Jan 95 18:52:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10922;
	Sun, 1 Jan 95 18:38:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10914;
	Sun, 1 Jan 95 18:38:11 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOcUu-00038CC; Sun, 1 Jan 95 18:27 PST
To: pine-info@cac.washington.edu
From: mfrisch@io.org
Subject: OS/2 version of Pine?
Date: 2 Jan 1995 00:45:19 GMT
Message-Id: <3e7iav$n31@ionews.io.org>

	Is there an OS/2 version of Pine available that works with a POP mail
server?  If this is a FAQ, please direct me to the source of the FAQ.

	Thank you very much in advance!

Mike - Team OS/2



From owner-pine-info@cac.washington.edu  Sun Jan  1 19:45:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17262;
	Sun, 1 Jan 95 19:45:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09120;
	Sun, 1 Jan 95 19:24:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09114;
	Sun, 1 Jan 95 19:24:48 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOdIt-00038CC; Sun, 1 Jan 95 19:19 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Pine Pipe to Zmodem
Date: 1 Jan 1995 22:07:56 -0500
Message-Id: <3e7qmc$rod@little-miami.iac.net>

I'm doing terminal emulation to my ISP. The default mailer is Pine. The
pipe command IS configured but I can't get piping to: sz - to work. When
I try it, the screen does display the zmodem init string, i.e *B00000....
But I can't get it to connect up to my terminal emulation program's
zmodem requestor. Piping from Elm and from Tin work just fine. The sysadmin
gave me some non-understanable explaination about why the Pine pipe command
doesn't work with 'sz'. Is the pipe command in Pine _that_ different from
that of Elm (and Tin)?

 
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Mon Jan  2 03:04:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25720;
	Mon, 2 Jan 95 03:04:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17005;
	Mon, 2 Jan 95 03:00:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16999;
	Mon, 2 Jan 95 03:00:14 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOkQQ-00038CC; Mon, 2 Jan 95 02:55 PST
To: pine-info@cac.washington.edu
From: lucio@ifctr.mi.cnr.it (Lucio Chiappetti)
Subject: Re: WANTED: Way to add delimiter to exported msgs
Date: 2 Jan 1995 04:52:49 -0600
Message-Id: <9601021101.AA07964@poseidon.ifctr.mi.cnr.it>
References: <3e2hrv$4g6@cronkite.ocis.temple.edu>

In article <3e2hrv$4g6@cronkite.ocis.temple.edu>, shrim@astro.ocis.temple.edu (Wet-Sprocket) write:
|> Comes here Mr. John Moran with this opinion in the"comp.mail.pine" group in this article on 30 Dec 1994 01:10:26 GMT:
|> 
|>  +       I regularly use Pine's export feature to save e-mail messages to 
|>  +   several different subject files. I would like to then import these files 
|>  +   into a database. But I need to find a way to add a delimiter character or 
|>  +   string to the exported messages so that can be separated from each other. 
|>  +   Is there a way to do this in Pine?
|> 
|> Hmmm...when you export a set of e-mail to a same file using the append feature
|> each mail is separated from one another by the From: header info for that mail.

   NO !
   The separator line is not the "From:" (From-colon) header line (part
   of the mail header, in any order, and even duplicated sometimes),
   but the "Unix From" line  (From starting in column one and followed
   by a blank space).

   There is a single From line at the beginning of each message (this
   is guaranteed by a device in the mailig s/w  such that any line
   starting with From-blank is changed to >From ), followed by the
   mail header, a blank line, the mail body ... then another Unix From
   line starts the next message

-- 
---------------------------------------------------------------------------- 
       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: LUCIO@IFCTR.MI.CNR.IT  |                                           
Decnet:   IFCTR::LUCIO           |             (Rabisch, II 46, 119-120)     
---------------------------------------------------------------------------- 


From owner-pine-info@cac.washington.edu  Mon Jan  2 03:36:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26539;
	Mon, 2 Jan 95 03:36:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15047;
	Mon, 2 Jan 95 03:30:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15041;
	Mon, 2 Jan 95 03:30:14 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOkpz-00038CC; Mon, 2 Jan 95 03:22 PST
To: pine-info@cac.washington.edu
From: viljanen@cc.Helsinki.FI (Lea Viljanen)
Subject: Re: 8BIT or QUOTED-PRINTABLE in Pine Usenet News articles
Date: 2 Jan 1995 11:19:44 -0000
Message-Id: <3e8ngg$6nd@kantti.Helsinki.FI>
References: <Pine.SUN.3.91.941230135751.17730B-100000@ester>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Jacob Palme <jpalme@dsv.su.se> wrote:
>When I write articles to Usenet News, using Pine set on the ISO 8859-1
>character set, then PINE uses the Quoted-Printable encoding. Very
>few newsreaders can read Quoted-Printable, so this makes my articles
>very difficult to read if they contain many characters with the 8th
>bit set.

Apply the following patch to Pine sources and read news by
using "pine -use_qp 0".

---------- 8< ------------- 8< ------------------ 8< ---------------

(pine-3.90-patch-8bit.txt A 940905 PSv)

Patches to pine 3.90
====================

These are patches to get the following:

* Correction to the when-to-QP-encode code: The 30% limit must be
  paired with a lower length limit, or else very short letters could
  mysteriously sometimes be BASE64-encoded, because of a too high
  non-ASCII character ratio. (For getting just this correction, see
  the changes to line 3263-3266 in send.c.)

* New command line parameters:

  -use qp [0 or 1]	Use MIME encoding quoted printable for text,
			not 8-bit. (Default XX, 0=no, 1 or [none]=yes.)
  -mime_8 [0 or 1]	If text contains 8-bit text, use
			MIME. (Default YY, 0=no, 1 or [none]=yes.)

* New config parameters (on which the XX and YY defaults above
  depends): 

	DEFAULT_NOT_USE_QUOTED_PRINTABLE - Corresponds to "-use_qp 0"

  Enable this *only* if your sending software have the ESMTP 8BITMIME
  extension avaliable and enabled. (See RFC 1425 and RFC 1426.)

	DEFAULT_USE_NON_MIME_8BIT_LOCALLY - Corresponds to "-mime_8 0"

  Enable this *only* if your sending software transforms messages to
  7-bit before sending them outside your domain, or if it transforms
  it to MIME and uses ESMTP 8BITMIME (see above).

(I do *not* take any responsibility for the functionality of Pine 3.90
after applying this patch!)

---
Peter Svanberg,				    Email: psv@nada.kth.se
Dept of Num An & CS,
Royal Inst of Tech			    Phone: +46 8 790 71 40
S-100 44  Stockholm, SWEDEN		    Fax:   +46 8 790 09 30


-----------------------------------------------------------------------
*** pine.h.DIST	Thu Aug 25 04:55:22 1994
--- pine.h	Wed Aug 31 17:04:59 1994
***************
*** 1048,1049 ****
--- 1048,1052 ----
  
+     unsigned	 mime_encode_8bit_text:1;
+     unsigned	 mime_use_qp_encoding:1;
+ 
      unsigned     noshow_error:1;
*** args.c.DIST	Thu Aug 18 19:19:47 1994
--- args.c	Mon Sep  5 22:12:13 1994
***************
*** 111,112 ****
--- 111,124 ----
  
+ #ifdef	DEFAULT_USE_NON_MIME_8BIT_LOCALLY
+     pine_state->mime_encode_8bit_text = 0;
+ #else
+     pine_state->mime_encode_8bit_text = 1;
+ #endif
+ 
+ #ifdef	DEFAULT_NOT_USE_QUOTED_PRINTABLE
+     pine_state->mime_use_qp_encoding = 0;
+ #else
+     pine_state->mime_use_qp_encoding = 1;
+ #endif
+ 
        /* while more arguments with leading - */
***************
*** 147,148 ****
--- 159,174 ----
  	       goto Loop;
+ 	    }else if(strcmp(*av, "mime_8") == 0) { /* PSv */
+ 	       if(--ac){
+ 		   pine_state->mime_encode_8bit_text = atoi(*++av);
+ 	       }else{
+ 		   pine_state->mime_encode_8bit_text = 1;
+ 	       }
+ 	       goto Loop;
+ 	    }else if(strcmp(*av, "use_qp") == 0) { /* PSv */
+ 	       if(--ac){
+ 		   pine_state->mime_use_qp_encoding = atoi(*++av);
+ 	       }else{
+ 		   pine_state->mime_use_qp_encoding = 1;
+ 	       }
+ 	       goto Loop;
  	    }else if(strcmp(*av, "sort") == 0){
***************
*** 367,368 ****
--- 393,404 ----
  {
+ 	int mime_encode_8bit_text = 1;
+ 	int mime_use_qp_encoding = 1;
+ 
+ #ifdef	DEFAULT_USE_NON_MIME_8BIT_LOCALLY
+ 	mime_encode_8bit_text = 0;
+ #endif
+ #ifdef	DEFAULT_NOT_USE_QUOTED_PRINTABLE
+ 	mime_use_qp_encoding = 0;
+ #endif
+ 
  	/**  print out possible starting arguments... **/
***************
*** 396,397 ****
--- 432,439 ----
          printf("\t -a\t\tSpecial anonymous mode for UWIN\n");
+ 
+         printf("\t -use_qp [0 or 1]\n\t\t\tUse MIME encoding quoted printable for text, not 8-bit.\n\t\t\t(Default %s, 0=no, 1 or [none]=yes.)\n",
+ 	       mime_use_qp_encoding ? "yes" : "no");
+         printf("\t -mime_8 [0 or 1]\n\t\t\tIf text contains 8-bit text, use MIME.\n\t\t\t(Default %s, 0=no, 1 or [none]=yes.)\n",
+ 	       mime_encode_8bit_text ? "yes" : "no");
+ 
  /* WHILE TESTING FOLDERS */
*** send.c.DIST	Fri Aug 26 20:36:55 1994
--- send.c	Mon Sep  5 22:11:11 1994
***************
*** 3078,3079 ****
--- 3078,3081 ----
  
+     body->mime_allowed = 1;
+ 
  #ifndef DOS
***************
*** 3263,3266 ****
  	}
! 	else if ((eight_bit_chars * 100L)/len < 30L) {
  	    /*
  	     * The 30% threshold is based on qp encoded readability
--- 3265,3269 ----
  	}
! 	else if ((eight_bit_chars * 100L)/len < 30L || len < 100) {
  	    /*
+ 	     * Less than 30% 8-bit or shorter than 100 chars.
  	     * The 30% threshold is based on qp encoded readability
***************
*** 3273,3275 ****
  	    if (new_encoding != ENCBINARY)
! 		new_encoding = ENC8BIT;  /* short lines, < 30% 8 bit chars */
  	}else {
--- 3276,3281 ----
  	    if (new_encoding != ENCBINARY)
! 		new_encoding = ENC8BIT;  /* short lines, few 8 bit chars */
! 	    if (!ps_global->mime_encode_8bit_text) {
! 		body->mime_allowed = 0;
! 	    }
  	}else {
***************
*** 3589,3591 ****
  
!     if (body && !header->env->remail) {	/* not if remail or no body */
  	if((f && !(*f)(s, MIME_VER))
--- 3595,3598 ----
  
!     if (body && !header->env->remail && body->mime_allowed) { /* PSv */
! 	/* not [if remail or no body structure or !mime_allowed] */
  	if((f && !(*f)(s, MIME_VER))
***************
*** 3803,3805 ****
  	  case ENC8BIT:			/* encode 8BIT into QUOTED-PRINTABLE */
! 	    gf_link_filter(gf_8bit_qp);
  	    break;
--- 3810,3813 ----
  	  case ENC8BIT:			/* encode 8BIT into QUOTED-PRINTABLE */
! 	    if (body->mime_allowed && ps_global->mime_use_qp_encoding)
! 		gf_link_filter(gf_8bit_qp);
  	    break;
***************
*** 3859,3861 ****
  	       body_encodings[body->encoding == ENCBINARY ? ENCBASE64 :
! 			      body->encoding == ENC8BIT ? ENCQUOTEDPRINTABLE :
  			      body->encoding <= ENCMAX ? body->encoding :
--- 3867,3872 ----
  	       body_encodings[body->encoding == ENCBINARY ? ENCBASE64 :
! 			      (body->encoding == ENC8BIT
! 			       && body->mime_allowed
! 			       && ps_global->mime_use_qp_encoding) ?
! 			      ENCQUOTEDPRINTABLE :
  			      body->encoding <= ENCMAX ? body->encoding :
*** makefile.???.DIST	Tue Jul 26 00:21:59 1994
--- makefile.???	Mon Sep  5 02:27:17 1994
***************
  
If desired add

 	-DDEFAULT_NOT_USE_QUOTED_PRINTABLE
or
	-DDEFAULT_USE_NON_MIME_8BIT_LOCALLY

to the line starting 

CFLAGS= ...
  
  
*** ../c-client/mail.h.DIST	Thu Aug 18 07:25:15 1994
--- ../c-client/mail.h	Mon Sep  5 21:53:03 1994
***************
*** 238,239 ****
--- 238,240 ----
    } size;
+   unsigned short mime_allowed;	/* (PSv) MIME allowed? (internal status) */
  };


(pine-3.90-patch-8bit.txt END)

-- 
Lea 'LadyBug' Viljanen        University of Helsinki      Lea doesn't
Lea.Viljanen@Helsinki.FI      Computing Centre            rhyme with tea.


From owner-pine-info@cac.washington.edu  Mon Jan  2 07:32:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02491;
	Mon, 2 Jan 95 07:32:31 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20540;
	Mon, 2 Jan 95 07:25:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ees1a0.engr.ccny.cuny.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20534;
	Mon, 2 Jan 95 07:25:41 -0800
Received: by ees1a0.engr.ccny.cuny.edu (4.1/SMI-4.1-940815-1)
	id AA08159; Mon, 2 Jan 95 10:25:03 EST
Date: Mon, 2 Jan 1995 10:25:02 -0500 (EST)
From: Dan Schlitt <dan@ees1a0.engr.ccny.cuny.edu>
To: Lucio Chiappetti <lucio@ifctr.mi.cnr.it>
Cc: pine-info@cac.washington.edu
Subject: Re: WANTED: Way to add delimiter to exported msgs
In-Reply-To: <9601021101.AA07964@poseidon.ifctr.mi.cnr.it>
Message-Id: <Pine.SUN.3.91.950102101833.7003B-100000@ees1a0.engr.ccny.cuny.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


As was corresectly pointed out to me by others, the export command does 
not use the Berkley mail separator.  Unless Pine reorders the headers 
when it exports a message, the From: method will also not work reliably. 
The best method might be to pipe the message to a script which appends 
the message to the file and inserts the separator.  

The alternative may be having the program which imports the messages into 
the database parse all the headers in the file with exported messages.  
This is not a very nice solution.

/dan

-- 

Dan Schlitt                           School of Engineering Computer Systems
dan@ee-mail.engr.ccny.cuny.edu        City College of New York
(212)650-6760                         New York, NY 10031

On 2 Jan 1995, Lucio Chiappetti wrote:

> In article <3e2hrv$4g6@cronkite.ocis.temple.edu>, shrim@astro.ocis.temple.edu (Wet-Sprocket) write:
> |> Comes here Mr. John Moran with this opinion in the"comp.mail.pine" group in this article on 30 Dec 1994 01:10:26 GMT:
> |> 
> |>  +       I regularly use Pine's export feature to save e-mail messages to 
> |>  +   several different subject files. I would like to then import these files 
> |>  +   into a database. But I need to find a way to add a delimiter character or 
> |>  +   string to the exported messages so that can be separated from each other. 
> |>  +   Is there a way to do this in Pine?
> |> 
> |> Hmmm...when you export a set of e-mail to a same file using the append feature
> |> each mail is separated from one another by the From: header info for that mail.
> 
>    NO !
>    The separator line is not the "From:" (From-colon) header line (part
>    of the mail header, in any order, and even duplicated sometimes),
>    but the "Unix From" line  (From starting in column one and followed
>    by a blank space).
> 
>    There is a single From line at the beginning of each message (this
>    is guaranteed by a device in the mailig s/w  such that any line
>    starting with From-blank is changed to >From ), followed by the
>    mail header, a blank line, the mail body ... then another Unix From
>    line starts the next message
> 
> -- 
> ---------------------------------------------------------------------------- 
>        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: LUCIO@IFCTR.MI.CNR.IT  |                                           
> Decnet:   IFCTR::LUCIO           |             (Rabisch, II 46, 119-120)     
> ---------------------------------------------------------------------------- 
> 



From owner-pine-info@cac.washington.edu  Mon Jan  2 08:03:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02987;
	Mon, 2 Jan 95 08:03:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20862;
	Mon, 2 Jan 95 07:57:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from poseidon.ifctr.mi.cnr.it by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20856;
	Mon, 2 Jan 95 07:57:39 -0800
Received: by poseidon.ifctr.mi.cnr.it (5.65/1.34)
	id AA09030; Tue, 2 Jan 1996 17:05:09 +0100
Organization: Istituto di Fisica Cosmica e Tecnologie Relative
Date: Tue, 2 Jan 1996 17:05:07 +0100 (MET)
From: Lucio Chiappetti <lucio@ifctr.mi.cnr.it>
Subject: Re: WANTED: Way to add delimiter to exported msgs
To: Dan Schlitt <dan@ees1a0.engr.ccny.cuny.edu>
Cc: pine-info@cac.washington.edu
In-Reply-To: <Pine.SUN.3.91.950102101833.7003B-100000@ees1a0.engr.ccny.cuny.edu>
Message-Id: <Pine.3.89.9601021727.A8822-0100000@poseidon.ifctr.mi.cnr.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 2 Jan 1995, Dan Schlitt wrote:

> As was corresectly pointed out to me by others, the export command does 
> not use the Berkley mail separator.  Unless Pine reorders the headers 
> when it exports a message, the From: method will also not work reliably. 
> The best method might be [...omissis...]

  When I was mentioning the use of the "Unix From" line (see below), I 
  was NOT referring to the Pine "export" command (which exports a single 
  mail) but to the Pine "save" command !

  The "Unix From" line can be used as delimiter when parsing FOLDERS !!

> On 2 Jan 1995, Lucio Chiappetti wrote:
> 
> >    NO !
> >    The separator line is not the "From:" (From-colon) header line (part
> >    of the mail header, in any order, and even duplicated sometimes),
> >    but the "Unix From" line  (From starting in column one and followed
> >    by a blank space).


From owner-pine-info@cac.washington.edu  Mon Jan  2 08:35:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03517;
	Mon, 2 Jan 95 08:35:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21213;
	Mon, 2 Jan 95 08:30:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21207;
	Mon, 2 Jan 95 08:30:32 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOpWX-00038CC; Mon, 2 Jan 95 08:22 PST
To: pine-info@cac.washington.edu
From: alexrs@world.std.com (Alex R Stevenson)
Subject: creating quotes
Message-Id: <D1sDGr.Duy@world.std.com>
Date: Mon, 2 Jan 1995 16:22:03 GMT

I cannot figure out how to create quotes - single or double - in pine (or 
in Unix for that matter) on my Mac. Any suggestions?


From owner-pine-info@cac.washington.edu  Mon Jan  2 10:52:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06241;
	Mon, 2 Jan 95 10:52:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22986;
	Mon, 2 Jan 95 10:48:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from Krypton.Mankato.MSUS.EDU by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22980;
	Mon, 2 Jan 95 10:48:01 -0800
Received: from localhost (hayden@localhost) by krypton.mankato.msus.edu (8.6.4/8.6.4) id MAA06552; Mon, 2 Jan 1995 12:47:40 -0600
Date: Mon, 2 Jan 1995 12:47:39 -0600 (CST)
From: "Robert A. Hayden" <hayden@krypton.mankato.msus.edu>
To: Pine Info <pine-info@cac.washington.edu>
Subject: Turning off news
Message-Id: <Pine.ULT.3.91.950102124453.6479B-100000@krypton.mankato.msus.edu>
X-Geek_2.1: GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++
X-Geek_2.1: P+>++ L++ 3- E---- N+++ K+++ W M+ V-- -po+(---)> Y++ t+ 5+++ j
X-Geek_2.1: R+++ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++**
X-Pgp-Fingerprint: D1 0B 53 C9 9A 2F 29 A5  76 2A 5A F6 EC 27 AB B9
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there a way to COMPLETELY shut off the reading of news in 3.91?  We 
have to read news via NNTP from another machine and if there is some lag 
or something on that machine, it can take several minutes to start.  
Rather annoying.

What I'd like is for it NOT to build the folders, but still allow me to 
post to a newsgroup.

Can this be done?

____        Robert A. Hayden       <=> hayden@krypton.mankato.msus.edu
\  /__          -=-=-=-=-          <=>          -=-=-=-=-
 \/  /  Finger for Geek Code Info  <=> All I want is a cure...  
   \/   Finger for PGP Public Key  <=>      And all my friends back!



From owner-pine-info@cac.washington.edu  Mon Jan  2 12:15:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07720;
	Mon, 2 Jan 95 12:15:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21670;
	Mon, 2 Jan 95 12:09:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21664;
	Mon, 2 Jan 95 12:09:33 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOssO-00038FC; Mon, 2 Jan 95 11:57 PST
To: pine-info@cac.washington.edu
From: emartin@ibm.net
Subject: pop3d for Solaris2.3?
Date: 2 Jan 1995 19:42:10 GMT
Message-Id: <3e9kui$2as0@news-s01.ny.us.ibm.net>

Can anyone tell me where I can get pine for Solaris2.3.
I understand It comes with a pop3 server, which is what Im really looking 
for.

		Thanks
		Ernie


From owner-pine-info@cac.washington.edu  Mon Jan  2 14:34:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10776;
	Mon, 2 Jan 95 14:34:07 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23648;
	Mon, 2 Jan 95 14:31:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23642;
	Mon, 2 Jan 95 14:30:59 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOvAV-00038FC; Mon, 2 Jan 95 14:23 PST
To: pine-info@cac.washington.edu
From: arwhead@tyrell.net (Bill Murray)
Subject: Somthng other than vt100
Message-Id: <D1n07w.40B@tyrell.net>
Date: Fri, 30 Dec 1994 18:47:55 GMT

I can't get my compiled version of PINE3.91 to work with a terminal emulation
other than vt100.  When I run pine-bin.solaris for solaris2.x it comes up
with an error message and never runs pine.  The error is:

Your terminal, of type "vp", is lacking functions needed to run pine.  And
it's not just vp but many other emulations.  I've tried pine on another
solaris machine and it works with the emulations I'm trying but my
compiled version does not.

WHAT's WRONG?

Bill Murray
arwhead@tyrell.net


From owner-pine-info@cac.washington.edu  Mon Jan  2 14:34:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10805;
	Mon, 2 Jan 95 14:34:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26154;
	Mon, 2 Jan 95 14:30:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26148;
	Mon, 2 Jan 95 14:30:57 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOvAU-00038CC; Mon, 2 Jan 95 14:23 PST
To: pine-info@cac.washington.edu
From: arwhead@tyrell.net (Bill Murray)
Subject: Terminal Emulations
Message-Id: <D1Mv1s.3I7@tyrell.net>
Date: Fri, 30 Dec 1994 16:56:16 GMT

How do you set up other terminal emulations for PINE besides vt100.  
SPECIFICALLY, vp or ADDS VIEWPOINT.  Pine says that it does not support
pine.  Isn't there something I can change in the configuration file of
pine without changing my terminal emulation to something other than vt100
or vt220 or whatever.  I want to use vp.  Any ideas?

Bill Murray
arwhead@tyrell.net


From owner-pine-info@cac.washington.edu  Mon Jan  2 15:20:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12185;
	Mon, 2 Jan 95 15:20:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26981;
	Mon, 2 Jan 95 15:18:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26975;
	Mon, 2 Jan 95 15:18:01 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOvsX-00038bC; Mon, 2 Jan 95 15:09 PST
To: pine-info@cac.washington.edu
From: re36648@deere.com (Dave Smart)
Subject: Can't find 'aliases' equiv for pine
Message-Id: <D1st6z.L8s@deere.com>
Date: Mon, 2 Jan 1995 20:55:19 GMT

Apologies in advance if this is completely obvious...
I'm new to pine, and involved with installing it (sound fun?)

I want to setup aliases like firstname.lastname, and have found that the
file 'aliases' does this for the sendmail utility, but pine does not read this
file. Documentation is minimal, so I've been browsing for that as well.

Thanks


Dave Smart
voice:  319/292-8776
fax:    319/292-8032
e-mail: re36648@deere.com
s-mail: John Deere PEC
        P.O. Box 8000 M/S-81A
        Waterloo, IA 50704-8000


From owner-pine-info@cac.washington.edu  Mon Jan  2 15:26:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12311;
	Mon, 2 Jan 95 15:26:07 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24579;
	Mon, 2 Jan 95 15:23:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24573;
	Mon, 2 Jan 95 15:23:43 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOvvZ-00038cC; Mon, 2 Jan 95 15:12 PST
To: pine-info@cac.washington.edu
From: scottc@online.dct.com (Scott Chapman)
Subject: Pine on SCO 3.2v4.2 w mmdf
Date: 2 Jan 1995 22:14:18 GMT
Message-Id: <3e9trq$fkd@fullfeed.fullfeed.com>

If anyone has gotten Pine 3.91 and associated programs going on the
latest release of SCO 3.2v4.2 please send me a little mail if you have any
helpful hints.

I would prefer to clean up some of the warning messages,
and short of telling the compiler to shut up, maybe there are a few
other #defines, etc that I could set to clean up some of them before I 
start to track them down and fix them.

Once that is done, I would then
like to start doing some MINIMAL site specific changes also, in the easiest
to update method I can find.

If there is a SCO/Pine place to look, please point me in the right direction.

Thanks in advance for any help!

schapman@acm.org


From owner-pine-info@cac.washington.edu  Mon Jan  2 15:59:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13007;
	Mon, 2 Jan 95 15:59:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27488;
	Mon, 2 Jan 95 15:56:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from astro.ocis.temple.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27482;
	Mon, 2 Jan 95 15:56:35 -0800
Received: by astro.ocis.temple.edu (5.61/25)
	id AA00588; Mon, 2 Jan 95 18:56:33 -0500
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Message-Id: <9501022356.AA00588@astro.ocis.temple.edu>
To: Andrew Sweger <absweger@u.washington.edu>
Cc: Dan Schlitt <dan@ees1a0.engr.ccny.cuny.edu>,
        Wet-Sprocket <shrim@astro.ocis.temple.edu>,
        pine-info@cac.washington.edu, shrim@astro.ocis.temple.edu
Subject: Re: WANTED: Way to add delimiter to exported msgs 
In-Reply-To: Your message of Sat, 31 Dec 94 13:14:02 -0800.
             <Pine.OSF.3.91a.941231131056.3925A-100000@saul1.u.washington.edu> 
Date: Mon, 02 Jan 95 18:56:32 EST




From owner-pine-info@cac.washington.edu  Mon Jan  2 17:19:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14982;
	Mon, 2 Jan 95 17:19:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28698;
	Mon, 2 Jan 95 17:16:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28692;
	Mon, 2 Jan 95 17:16:11 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOxiU-00038CC; Mon, 2 Jan 95 17:07 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: cmsg cancel <9501022356.AA00588@astro.ocis.temple.edu>
Control: cancel <9501022356.AA00588@astro.ocis.temple.edu>
Date: 3 Jan 1995 00:56:58 GMT
Message-Id: <3ea7cq$kb0@cronkite.ocis.temple.edu>

Article cancelled from within tin [v1.2 PL2]


From owner-pine-info@cac.washington.edu  Mon Jan  2 17:59:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15654;
	Mon, 2 Jan 95 17:59:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26596;
	Mon, 2 Jan 95 17:55:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26590;
	Mon, 2 Jan 95 17:55:02 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOyHt-00038CC; Mon, 2 Jan 95 17:43 PST
To: pine-info@cac.washington.edu
From: gc617952@netserv.chula.ac.th (Charn Ariyakul)
Subject: [Q] PC-PINE Source Code
Date: 25 Dec 1994 01:36:44 GMT
Message-Id: <3diibc$n92@enterprise.netserv.chula.ac.th>




From owner-pine-info@cac.washington.edu  Mon Jan  2 18:22:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16110;
	Mon, 2 Jan 95 18:22:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29488;
	Mon, 2 Jan 95 18:16:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29482;
	Mon, 2 Jan 95 18:16:17 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOyhz-00038CC; Mon, 2 Jan 95 18:10 PST
To: pine-info@cac.washington.edu
From: pjh@tigger.jvnc.net (Prof. Peter J. Holsberg)
Subject: Re: Can't Find .newsrc
Message-Id: <D1t49M.8tu@tigger.jvnc.net>
References: <3e2kou$4g6@cronkite.ocis.temple.edu>
Date: Tue, 3 Jan 1995 02:00:58 GMT

shrim@astro.ocis.temple.edu (Wet-Sprocket) writes:

>Comes here Mr. Pete Holsberg with this opinion in the "comp.mail.pine" group in this article on Thu, 22 Dec 1994 17:47:03 GMT:

> +   =	News *{tecoma.mccc.edu}[]
> +   =	can't connect to tecoma, 143
> +   =	conenction refused
> +   =Is that an imapd problem???

>On the other hand it could be a /etc/hosts problem on the tecoma.mccc.edu
>machine. Would it be possible that that nntp-server is denying news-reading
>access to the Unix-ware machine?

No.


From owner-pine-info@cac.washington.edu  Mon Jan  2 19:21:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17191;
	Mon, 2 Jan 95 19:21:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00273;
	Mon, 2 Jan 95 19:16:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00267;
	Mon, 2 Jan 95 19:16:21 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rOzdi-00038CC; Mon, 2 Jan 95 19:10 PST
To: pine-info@cac.washington.edu
From: gurupubl@crl.com (Brian Goss)
Subject: Problem posting UUencoded files with PINE?
Date: 2 Jan 1995 19:06:04 -0800
Message-Id: <3eaeus$g4q@crl4.crl.com>

I am having problems using the Read File option in pine to read in a 
uuencoded file.  When I read in the file, pine says LINE TOO LONG and 
automatically wraps all the text.  This, in turn, basically corruptes the 
uuencoded data.  Can anyone help me with this problem?

BG



From owner-pine-info@cac.washington.edu  Mon Jan  2 22:49:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20823;
	Mon, 2 Jan 95 22:49:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00279;
	Mon, 2 Jan 95 22:40:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00273;
	Mon, 2 Jan 95 22:40:13 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA29226; Tue, 3 Jan 1995 01:38:54 +0500
Date: Tue, 3 Jan 1995 01:38:54 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: Alex R Stevenson <alexrs@world.std.com>
Cc: pine-info@cac.washington.edu
Subject: Re: creating quotes
In-Reply-To: <D1sDGr.Duy@world.std.com>
Message-Id: <Pine.SOL.3.90.950103012934.29188C-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 912

On Mon, 2 Jan 1995, Alex R Stevenson wrote:

> I cannot figure out how to create quotes - single or double - in pine (or 
> in Unix for that matter) on my Mac. Any suggestions?
 
???  I must be missing something obvious here.  Do you mean quotation
marks like "this" and 'this'?  If so, then you just type them, just as 
you would in anything else.  What happens when you try to type quotation 
marks?  If they are not echoed back from the Unix box, then either your 
telecomm software is doing something strange to your Mac's keyboard 
mapping (see your telecomm software's documentation), or the Unix box is 
rejecting those characters for some reason (ask your System Administrator).
 
I use a Mac too, and use Microphone Pro (or occasionally ZTerm) telecomm 
software. I have no trouble sending quote characters to Pine and Unix.

-------------------------------------
Chip Old   <fold@mail.bcpl.lib.md.us>



From owner-pine-info@cac.washington.edu  Mon Jan  2 23:15:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21363;
	Mon, 2 Jan 95 23:15:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00583;
	Mon, 2 Jan 95 23:10:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from linknet.kitsap.lib.wa.us by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00577;
	Mon, 2 Jan 95 23:10:34 -0800
Received: (from michael@localhost) by linknet.kitsap.lib.wa.us (8.6.9/8.6.9) id XAA07259; Mon, 2 Jan 1995 23:08:26 -0800
Date: Mon, 2 Jan 1995 23:08:25 -0800 (PST)
From: Michael Schuyler <michael@linknet.kitsap.lib.wa.us>
To: pine-info@cac.washington.edu
Subject: Pico
Message-Id: <Pine.SUN.3.91.950102230701.7234B-100000@linknet.kitsap.lib.wa.us>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there an OVERTYPE mode in Pico?


  :::::;     . ,             Michael Schuyler               ..,     `::::::
  :::;' /)  - * -    michael@linknet.kitsap.lib.wa.us      - + -  (\ `:::::
  ::'  / )   ':`  Kitsap Regional Library, 1301 Sylvan Way  ':`   ( \_ `  :
  :' _( (_    _     Bremerton, WA  98310 (360) 405-9139       _    ) )\ />:




From owner-pine-info@cac.washington.edu  Tue Jan  3 06:02:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29961;
	Tue, 3 Jan 95 06:02:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05534;
	Tue, 3 Jan 95 05:57:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05528;
	Tue, 3 Jan 95 05:57:44 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rP9XZ-00038KC; Tue, 3 Jan 95 05:44 PST
To: pine-info@cac.washington.edu
From: Jeff Morris <jbmorris@indiana.edu>
Subject: View Message screen constantly redraws?
Date: Tue, 3 Jan 1995 08:35:10 -0500
Message-Id: <Pine.HPP.3.91.950103083001.1288A-100000@ezmail.ucs.indiana.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

If I am viewing a message, every minute or half minute or so the screen 
either redraws itself or makes some minor change.  With my telnet 
program, if I'm on another connection, it tells me when something changes 
on the connections I'm not looking at right now.  If I leave pine 3.91 in 
the view message screen and flip to another connection, it will soon tell 
me that something has changed on the pine connection, but it really 
hasn't.  Does anyone know what is going on and why?

- Jeff

P.S. In 3.91, is there a way to specify how often you want it to check 
for new mail?


From owner-pine-info@cac.washington.edu  Tue Jan  3 06:10:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00215;
	Tue, 3 Jan 95 06:10:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08296;
	Tue, 3 Jan 95 06:05:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08290;
	Tue, 3 Jan 95 06:05:35 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rP9gW-00038OC; Tue, 3 Jan 95 05:54 PST
To: pine-info@cac.washington.edu
From: berliner@netcom.com (Guy Berliner)
Subject: Dumb Question: Why Does My Terminal Lock Up?
Message-Id: <berlinerD1tI1J.B51@netcom.com>
Date: Tue, 3 Jan 1995 06:58:30 GMT

I just started using PINE 3.89, and everything goes swimmingly
until I try to read news. I enter the folder list, go into
the news collection, punch return when I see the words
[ Select Here to See Expanded List ] in inverse video. And
then my terminal locks up. Can't suspend, can't kill, can't
do anything.

What foolish thing am I doing to cause the program to hang 
this way? When I set 
news-collections=News *{foo.bar.edu/nntp}[*]
where foo.bar.edu is a news server to which I have access, I
have no problems. But when I try to use my local host at
Netcom by changing the .pinerc entry to
news-collection=News *[*]
then my terminal locks up when I try to read news, like I 
said. I'm sure I'm doing something dense. I'm sure I must
have to specify the news directory, /var/spool/news, or 
something. But where? Should I be setting an environment 
variable in my .profile or something? Please forgive me for 
asking this newby question, but though I've rtfm'ed it, I'm 
honestly at a loss now. Thanks in advance.

BTW: If possible, please mail me a response, as I don't 
regularly read this newsgroup. Thanks.

Guy Berliner

-- 
Finger berliner@netcom18.netcom.com for pgp key. 
Please send me encrypted mail! Everyone else will see gibberish,
but I'll only see plaintext, cause I just push the "Decrypt"
button in my copy of Windows Z-mail! (Ask me for more info.)


From owner-pine-info@cac.washington.edu  Tue Jan  3 07:50:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02211;
	Tue, 3 Jan 95 07:50:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07000;
	Tue, 3 Jan 95 07:42:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06994;
	Tue, 3 Jan 95 07:42:19 -0800
Received: by hobbes.twntpe.cdc.com; Tue, 3 Jan 95 23:40:52 -0800
Date: Tue, 3 Jan 1995 23:40:51 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Jeff Morris <jbmorris@indiana.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: View Message screen constantly redraws?
In-Reply-To: <Pine.HPP.3.91.950103083001.1288A-100000@ezmail.ucs.indiana.edu>
Message-Id: <Pine.SOL.3.91.950103233548.1322D-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 3 Jan 1995, Jeff Morris wrote:

> If I am viewing a message, every minute or half minute or so the screen 
> either redraws itself or makes some minor change.  With my telnet 
> program, if I'm on another connection, it tells me when something changes 
> on the connections I'm not looking at right now.  If I leave pine 3.91 in 
> the view message screen and flip to another connection, it will soon tell 
> me that something has changed on the pine connection, but it really 
> hasn't.  Does anyone know what is going on and why?

	Hummm...you are using pine 3.91.  I believe the default interval
for checking for new mail was changed to 2.5 minutes or so...  In any
event, when pine 3.91 checks for new mail it will put an * in the upper
left corner.  This is maybe what you are seeing.

	You can disable the * cue in the configuration with:

	[X]  enable-mail-check-cue

> P.S. In 3.91, is there a way to specify how often you want it to check 
> for new mail?

	Yes, but I for got what .h file it is...   :-( ;-(


Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Tue Jan  3 08:04:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02700;
	Tue, 3 Jan 95 08:04:48 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07258;
	Tue, 3 Jan 95 07:57:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07252;
	Tue, 3 Jan 95 07:57:42 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPBRx-00038CC; Tue, 3 Jan 95 07:47 PST
To: pine-info@cac.washington.edu
From: peter-wa@dsv.su.se (Peter Wastholm)
Subject: Re: Inverse Video - change it
Date: 3 Jan 1995 15:16:34 GMT
Message-Id: <3ebpoi$f6d@erinews.ericsson.se>
References: <D1Hxs3.6zK@iglou.com>
Mime-Version: 1.0

In article <D1Hxs3.6zK@iglou.com>, karenoel@iglou.iglou.com wrote:
>
>I used to have a -> to show which letter was chosen. Now it is highlighted
>with what I think is called Inverse Video. 
>
>How do I get the -> back?
>

I read somewhere in the docs that Pine tries to detect if you're sitting on 
a slow modem line. If it thinks that you are, selection is marked with a -> 
instead of the usual reverse video. Have you changed modems recently or 
something? Anyway, maybe you can force Pine to display selected letters the 
way you want, but I can't help you there.

/Peter Wastholm



From owner-pine-info@cac.washington.edu  Tue Jan  3 08:24:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03428;
	Tue, 3 Jan 95 08:24:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10323;
	Tue, 3 Jan 95 08:20:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10308;
	Tue, 3 Jan 95 08:20:54 -0800
Received: from localhost by shiva2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01338;
	Tue, 3 Jan 95 08:20:53 -0800
Newsgroups: comp.mail.pine
Date: Tue, 3 Jan 1995 10:02:04 -0600 (GMT-0600)
From: Nick Boris <nmboris@artsci.wustl.edu>
X-Sender: nmboris@mulberry
To: "David L. Miller" <dlm@cac.washington.edu>
Subject: PC-PINE & X.400
Message-Id: <Pine.NXT.3.91.950103095147.24321C-100000@mulberry>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-Date: Tue, 3 Jan 1995 08:20:47 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950103082047.1265A@shiva2.cac.washington.edu>


Happy New Year to all!

Anyway one of these questions may have already been answered here 
(several times) but I have (repetadly) missed it. The other question may 
not be appropriate for this gorup (and you are free to tell me so) but I 
figured that I might as well try.

1) I had been trying to set up PC-Pine about a month ago (before romping
off to CERN for HTML goo and vacation) and was told my my MIS bud that he
had not installed IMAP systme-wide. When I returned he said that IMAP is
not up and running so that we sould try to figure out how to get it 
running now that we are starting to dissimnate a SLIP/PPP package to any 
of our users who want it.

Specifically we want (I want) to set it up so that it leaves all the 
mailboxes on the server machine and leaves all the dial-up clients alone. 
Can this be done so that it reads & writes to the multiple folders in the 
~/mail directory? 

What is the syntax for this and for readin from the inbox {artsci.wustl.edu}.

I also remember something about not being able to share a .newsrc between 
Client and Server. Is this true?

2) How do you communicate with someone on an X.400 gateway? (Yes you can 
scream at me about how stupid I am for not knowing this. Hey I don't do 
Sendmail just httpd! Besides two degress in english doth not a guru make)

Thanks in advance,

Nick

nmboris@artsci.wustl.edu
http://www.artsci.wustl.edu/~nmboris/




From owner-pine-info@cac.washington.edu  Tue Jan  3 09:18:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05911;
	Tue, 3 Jan 95 09:18:13 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09108;
	Tue, 3 Jan 95 09:12:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09102;
	Tue, 3 Jan 95 09:12:21 -0800
Received: from linda.teleport.com (bsherman@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id JAA25213 for <pine-info@cac.washington.edu>; Tue, 3 Jan 1995 09:12:21 -0800
Date: Tue, 3 Jan 1995 09:12:54 -0800 (PST)
From: "Brian E. Sherman" <bsherman@teleport.com>
To: Peter Wastholm <peter-wa@dsv.su.se>
Cc: pine-info@cac.washington.edu
Subject: Re: Inverse Video - change it
In-Reply-To: <3ebpoi$f6d@erinews.ericsson.se>
Message-Id: <Pine.SUN.3.91.950103090836.28596B@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 3 Jan 1995, Peter Wastholm wrote:

> Subject: Re: Inverse Video - change it
> 
> In article <D1Hxs3.6zK@iglou.com>, karenoel@iglou.iglou.com wrote:
> >
> >I used to have a -> to show which letter was chosen. Now it is highlighted
> >with what I think is called Inverse Video. 
> >
> >How do I get the -> back?
> >
> 

Under the Pine 3.91 Config options find the option:
 
show-selected-in-boldface 

and unselect it.  

 *-------------------------------------------------------------------------*
 |        _---_  "You can make a program fool-proof but then someone comes |
 |        (o o)        along and makes a better fool"  Murphy's Law        |
 *-----ooO--~--Ooo-------------------------------------*-------------------* 
 | Newport/Layton Home Fashions,Inc. - MIS/EDI Manager |
 |    E-Mail: Brian E. Sherman <bsherman@teleport.com> |
 | snailMail: 1420 NW Lovejoy St.      *---------------*
 |            Portland, OR  USA  97209 |  Opinions Expressed Here Are All Mine.
 |     Voice: 503-222-3847  Ext. 234   |  No-One Else Will Claim Them.
 |       Fax: 503-222-7465             |  
 *-------------------------------------* 
       (oo)   (oo) 





From owner-pine-info@cac.washington.edu  Tue Jan  3 10:32:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10307;
	Tue, 3 Jan 95 10:32:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13624;
	Tue, 3 Jan 95 10:26:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13610;
	Tue, 3 Jan 95 10:26:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPDkQ-00038CC; Tue, 3 Jan 95 10:14 PST
To: pine-info@cac.washington.edu
From: bparker@interaccess.com (Ben Parker)
Subject: Time zone mvar PC-Pine
Date: Tue, 3 Jan 1995 10:10:34 CST
Message-Id: <bparker.73.0DD32032@interaccess.com>

The instructions in the tech notes for Pine are not really clear about the 
proper use and format of the TZ environment variable for setting the correct 
local Time Zone time in msgs created by PC-Pine.

It says the TZ variable is xxxnnyyy where xxx is the abbreviation for the 
Standard (non-daylight-savings) Time Zone, nn is the offset from GMT, and yyy 
is the Daylight savings time zone abbreviation.

In my case (Illinois, USA) this should be CST-6CDT (since we are 6hrs behind 
or later than GMT)  However when I do this, PC-Pine sets the msg time to GMT+6 
which is really the correct time for India or SE Asia, not the USA.  When I 
set TZ to  CST6CDT I get the correct time setting.

I guess it is not necessary to use 2 numerals (such as 06) but what is the 
correct setting for number greater than 1 digit (e.g. 11 hrs)?

What is the correct setting for (New Zealand or Fiji) which is on the Int'l 
Date Line and +12 hrs from GMT.

What is the correct setting for Newfoundland (Canada) which is -3.5 hrs GMT?

Also, will PC-Pine automatically adjust for Daylight Savings Time periods 
(April to October) or does the TZ Variable need to be reset manually during 
that time?

Thanks.


 Ben Parker (IL)  bparker@interaccess.com   71450.2735@compuserve.com


From owner-pine-info@cac.washington.edu  Tue Jan  3 11:28:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14038;
	Tue, 3 Jan 95 11:28:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14899;
	Tue, 3 Jan 95 11:12:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from micronet.wcu.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14890;
	Tue, 3 Jan 95 11:12:52 -0800
Received: by micronet.wcu.edu (5.0/SMI-SVR4)
	id AA01865; Tue, 3 Jan 1995 14:12:15 +0500
Date: Tue, 3 Jan 1995 14:12:14 -0500 (EST)
From: Patti Johnson <johnson@micronet.wcu.edu>
X-Sender: johnson@micronet
To: pine-info@cac.washington.edu
Subject: trouble with the return address
Message-Id: <Pine.SOL.3.91.950103140941.1857A-100000@micronet>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 654

Hello all!  I've got both pine and mailx in use on my Solaris 2.3 system 
- with one major problem:

While mailx correctly addresses the "From" field, pine omits the machine 
name.  That is, here's the From from the two mailers:

mailx:	johnson@micronet.wcu.edu
pine:	johnson@wcu.edu

I NEED pine to return address my outgoing mail by the full method: 
johnson@micronet.wcu.edu and have piddled with sendmail.cf - only to 
screw up the working mailx.  Any ideas?  I've looked into the custom 
headers but find little help on doing a system-wide customize-able header 
for the return address.

Thanks for ANY help!
patti johnson
johnson@micronet.wcu.edu



From owner-pine-info@cac.washington.edu  Tue Jan  3 13:34:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20509;
	Tue, 3 Jan 95 13:34:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15744;
	Tue, 3 Jan 95 13:27:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15738;
	Tue, 3 Jan 95 13:27:11 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPGYX-00038CC; Tue, 3 Jan 95 13:14 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs
Date: Tue, 3 Jan 1995 12:23:07 -0800
Message-Id: <Pine.ULT.3.92.950103122152.27331e-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.92.950103122043.27331d-100000@shiva1.cac.washington.edu>


P.S.  If you do this, please make sure to make the behavior very clear to 
your users.  If you don't, we get flooded with bug reports ;)

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Tue, 3 Jan 1995, David L Miller wrote:

> Date: Tue, 3 Jan 1995 12:21:18 -0800
> From: David L Miller <dlm@cac.washington.edu>
> To: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> Subject: Re: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs 
> 
> 
> Set the read-msg-folder variable and the auto-move-read-msgs feature.
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On 31 Dec 1994, Wet-Sprocket wrote:
> 
> > Date: 31 DEC 1994 16:33:22 GMT 
> > From: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> > Newgroups: comp.mail.pine
> > Subject: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs 
> > 
> > Pi(o)ne(e)rs,
> > 
> > Is there a way to rig pine.conf.fixed so that when a user leaves read mail in
> > the INBOX to the tune of 1.5+ Mgs all the excessive mail be moved to a folder
> > within the users' home dir. in order to conserve diskspace on /usr/spool disk?
> > 
> > --
> > .---.                                ,    ,
> > \___                                ("\''/").___..--''"`-._
> >     \                                `9_ 9  )   `-.  (     ).`-.__.`)
> > `___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
> > Computer Svcs                      _..`--'_..-_/  /--'_.' .
> > Temple Univ.                      (il).-''  ((i).'  ((!.-'
> > __________________________________________________________________________
> > Talk about me doing the talking for others...esp. My Employers!
> > 
> > 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 13:58:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21617;
	Tue, 3 Jan 95 13:58:18 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16520;
	Tue, 3 Jan 95 13:52:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16514;
	Tue, 3 Jan 95 13:52:51 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPGyw-00038CC; Tue, 3 Jan 95 13:41 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: aggregate select in Newsgroups
Date: Tue, 3 Jan 1995 13:04:32 -0800
Message-Id: <Pine.ULT.3.92.950103130330.27331g-100000@shiva1.cac.washington.edu>
References: <Pine.ULT.3.91.941230164733.24657B-100000@halcyon.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.91.941230164733.24657B-100000@halcyon.com> 


An option to set the margins is on the (endless?) requested enhancements
list, but I have no idea how soon it might get to the top... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 30 Dec 1994, Charles W. Cooper II wrote:

> Date: Fri, 30 DEC 1994 16:48:58 -0800 
> From: Charles W. Cooper II <ccooper@halcyon.halcyon.com>
> Newgroups: comp.mail.pine
> Subject: aggregate select in Newsgroups 
> 
> 
> Hi there,
> 
> I'm not sure if this has been covered but I would like to see the ability 
> to select multiple newsgroups to subscribe in an aggregate fashion rather 
> than having to search, select and subscribe one by one...
> 
> Any possibilities here?
> 
> Thanks!
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 14:15:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22445;
	Tue, 3 Jan 95 14:15:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16891;
	Tue, 3 Jan 95 14:06:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16885;
	Tue, 3 Jan 95 14:06:36 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPHF6-00038CC; Tue, 3 Jan 95 13:58 PST
To: pine-info@cac.washington.edu
From: hollis@nadn.navy.mil (David T Hollis)
Subject: IMAP Daemon on Solaris 2.3
Message-Id: <D1uL6s.GCp@usna.navy.mil>
Date: Tue, 3 Jan 1995 21:04:04 GMT

Anyone have some info on setting up an IMAP daemon on a Solaris 2.3 
workstation?  I checked the documentation (albeit somewhat quickly) and 
found no mention of IMAP, nor POP.  If there is a FAQ with this info, 
please point me to it.  The purpose is to allow PC-Pine (Winsock) to 
access email of the workstation.

--
------------------------------
David Hollis
U.S. Naval Academy



From owner-pine-info@cac.washington.edu  Tue Jan  3 14:32:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23358;
	Tue, 3 Jan 95 14:32:20 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20211;
	Tue, 3 Jan 95 14:28:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20205;
	Tue, 3 Jan 95 14:28:30 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPHbN-00038KC; Tue, 3 Jan 95 14:21 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: Pine on SCO 3.2v4.2 w mmdf
Date: Tue, 3 Jan 1995 18:57:46 GMT
Message-Id: <D1uFCC.JE2@ssi.edc.org>
References: <3e9trq$fkd@fullfeed.fullfeed.com>

Scott Chapman (scottc@online.dct.com) wrote:
: I would prefer to clean up some of the warning messages,
: and short of telling the compiler to shut up, maybe there are a few
: other #defines, etc that I could set to clean up some of them before I 
: start to track them down and fix them.

I ignored them.  I have never had any troubles with the resulting 
binaries.  The int conversions it complains about are fine, since as it 
complains, it fixes them.  It's the difference in the way SCO handles 
signals, which is really only a semantic problem with which sort of error 
it returns.  Anyway, I wouldn't bang my head against it.

: Once that is done, I would then
: like to start doing some MINIMAL site specific changes also, in the easiest
: to update method I can find.

: If there is a SCO/Pine place to look, please point me in the right direction.

Not sure what you're looking for here - there aren't any site-specific 
compile-time options you can tweak - it's all done through the .pinerc, 
pine.conf and pine.conf.fixed.  I found everything I needed in the source 
tree.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Tue Jan  3 16:04:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27715;
	Tue, 3 Jan 95 16:04:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19533;
	Tue, 3 Jan 95 15:57:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19527;
	Tue, 3 Jan 95 15:57:26 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPIuY-00038CC; Tue, 3 Jan 95 15:45 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs
Date: Tue, 3 Jan 1995 12:21:18 -0800
Message-Id: <Pine.ULT.3.92.950103122043.27331d-100000@shiva1.cac.washington.edu>
References: <3e414i$o00@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3e414i$o00@cronkite.ocis.temple.edu> 


Set the read-msg-folder variable and the auto-move-read-msgs feature.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 31 Dec 1994, Wet-Sprocket wrote:

> Date: 31 DEC 1994 16:33:22 GMT 
> From: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs 
> 
> Pi(o)ne(e)rs,
> 
> Is there a way to rig pine.conf.fixed so that when a user leaves read mail in
> the INBOX to the tune of 1.5+ Mgs all the excessive mail be moved to a folder
> within the users' home dir. in order to conserve diskspace on /usr/spool disk?
> 
> --
> .---.                                ,    ,
> \___                                ("\''/").___..--''"`-._
>     \                                `9_ 9  )   `-.  (     ).`-.__.`)
> `___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
> Computer Svcs                      _..`--'_..-_/  /--'_.' .
> Temple Univ.                      (il).-''  ((i).'  ((!.-'
> __________________________________________________________________________
> Talk about me doing the talking for others...esp. My Employers!
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 16:24:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28767;
	Tue, 3 Jan 95 16:24:23 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20393;
	Tue, 3 Jan 95 16:21:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20357;
	Tue, 3 Jan 95 16:20:57 -0800
Received: by hobbes.twntpe.cdc.com; Wed, 4 Jan 95 08:19:15 -0800
Date: Wed, 4 Jan 1995 08:19:14 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Peter Wastholm <peter-wa@dsv.su.se>
Cc: pine-info@cac.washington.edu
Subject: Re: Inverse Video - change it
In-Reply-To: <3ebpoi$f6d@erinews.ericsson.se>
Message-Id: <Pine.SOL.3.91.950104081738.9470B-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 3 Jan 1995, Peter Wastholm wrote:

> In article <D1Hxs3.6zK@iglou.com>, karenoel@iglou.iglou.com wrote:
> >
> >I used to have a -> to show which letter was chosen. Now it is highlighted
> >with what I think is called Inverse Video. 
> >
> >How do I get the -> back?
> >
> 
> I read somewhere in the docs that Pine tries to detect if you're sitting on 
> a slow modem line. If it thinks that you are, selection is marked with a -> 
> instead of the usual reverse video. Have you changed modems recently or 
> something? Anyway, maybe you can force Pine to display selected letters the 
> way you want, but I can't help you there.
> 

	If you are running pine 3.9x then go to the setup/config menu
and set:

	    [ ]  assume-slow-link  

	That will help....

				Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Tue Jan  3 16:41:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29423;
	Tue, 3 Jan 95 16:41:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20773;
	Tue, 3 Jan 95 16:38:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20753;
	Tue, 3 Jan 95 16:37:55 -0800
Received: by hobbes.twntpe.cdc.com; Wed, 4 Jan 95 08:36:14 -0800
Date: Wed, 4 Jan 1995 08:36:13 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: David T Hollis <hollis@nadn.navy.mil>
Cc: pine-info@cac.washington.edu
Subject: Re: IMAP Daemon on Solaris 2.3
In-Reply-To: <D1uL6s.GCp@usna.navy.mil>
Message-Id: <Pine.SOL.3.91.950104083231.9470C-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 3 Jan 1995, David T Hollis wrote:

> Anyone have some info on setting up an IMAP daemon on a Solaris 2.3 
> workstation?  I checked the documentation (albeit somewhat quickly) and 
> found no mention of IMAP, nor POP.  If there is a FAQ with this info, 
> please point me to it.  The purpose is to allow PC-Pine (Winsock) to 
> access email of the workstation.

In your /etc/services file add a line like:

imap              143/tcp                         # IMAP

In your /etc/inetd.conf file add a line like:

imap    stream  tcp     nowait  root    /usr/local/bin/imapd   imapd

(the whitespace between fields in the inetd.conf file should be tabs)

Then find the PID of the inetd process and give it a kill -1...or
simply bounce the system.

				Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Tue Jan  3 16:47:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29723;
	Tue, 3 Jan 95 16:47:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20956;
	Tue, 3 Jan 95 16:43:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20950;
	Tue, 3 Jan 95 16:43:50 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPJf9-00038JC; Tue, 3 Jan 95 16:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Turning off news
Date: Tue, 3 Jan 1995 15:06:15 -0800
Message-Id: <Pine.ULT.3.92.950103150516.27331y-100000@shiva1.cac.washington.edu>
References: <Pine.ULT.3.91.950102124453.6479B-100000@krypton.mankato.msus.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.91.950102124453.6479B-100000@krypton.mankato.msus.edu> 


It sounds like what you want is to set nntp-server, to allow posting, and
clear news-collections by setting it to "". 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Mon, 2 Jan 1995, Robert A. Hayden wrote:

> Date: Mon, 2 JAN 1995 18:47:39 GMT 
> From: Robert A. Hayden <hayden@krypton.mankato.msus.edu>
> Newgroups: comp.mail.pine
> Subject: Turning off news 
> 
> Is there a way to COMPLETELY shut off the reading of news in 3.91?  We 
> have to read news via NNTP from another machine and if there is some lag 
> or something on that machine, it can take several minutes to start.  
> Rather annoying.
> 
> What I'd like is for it NOT to build the folders, but still allow me to 
> post to a newsgroup.
> 
> Can this be done?
> 
> ____        Robert A. Hayden       <=> hayden@krypton.mankato.msus.edu
> \  /__          -=-=-=-=-          <=>          -=-=-=-=-
>  \/  /  Finger for Geek Code Info  <=> All I want is a cure...  
>    \/   Finger for PGP Public Key  <=>      And all my friends back!
> 
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 16:47:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29744;
	Tue, 3 Jan 95 16:47:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23762;
	Tue, 3 Jan 95 16:43:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23756;
	Tue, 3 Jan 95 16:43:48 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPJez-00038CC; Tue, 3 Jan 95 16:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: News reading problem
Date: Tue, 3 Jan 1995 15:01:24 -0800
Message-Id: <Pine.ULT.3.92.950103150038.27331v-100000@shiva1.cac.washington.edu>
References: <d93ted.788635919@txfs1.hfb.se>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <d93ted.788635919@txfs1.hfb.se> 


Neither option is currently available, but the latter is on our list for 
consideration.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Wed, 28 Dec 1994, Thomas D. Eklund HFB T d93 wrote:

> Date: Wed, 28 DEC 1994 17:31:59 GMT 
> From: Thomas D. Eklund HFB T d93 <d93ted@t.hfb.se>
> Newgroups: comp.mail.pine
> Subject: News reading problem 
> 
> 
> 
> Hi.
> 
>    Can someone tell me how to read more than one newsgroup from one place?
>    
>    Something like:
>    
> news-collections = Solace *{news.solace.se/nntp}[comp.mail.pine && alt.binaries.supermodels
> 		   Sunet *{news.sunet.se/nntp}[comp.lang.visualbasic && rec.autos
> 
>    or can i have "Solace" news-collection read a specific .newsrc file 
>    and "Sunet" another like in emacs gnus?
>    
>    
> 
> Thanks in advance.
> -- 
> -------------------------------------------------------------------------------
>     ___    _    ____    _    ___         ,---------------------------------,
>    /   \__/ \__/    \__/ \__/   \        | Thomas '3kk3' Eklund-Dahlborg   |
>    |          _|@ @ __          |        | tel: +46 - 243 83238            |
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 17:01:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00378;
	Tue, 3 Jan 95 17:01:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21323;
	Tue, 3 Jan 95 16:58:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21317;
	Tue, 3 Jan 95 16:58:19 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPJu0-00038JC; Tue, 3 Jan 95 16:48 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: several messages
Date: Tue, 3 Jan 1995 15:12:48 -0800
Message-Id: <Pine.ULT.3.92.950103150959.27331A-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D1n07w.40B@tyrell.net> 


Check the termcap/terminfo database on your system to make sure that the 
"vp" terminal type is included.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 30 Dec 1994, Bill Murray wrote:

> Date: Fri, 30 DEC 1994 16:56:16 GMT 
> From: Bill Murray <arwhead@tyrell.net>
> Newgroups: comp.mail.pine
> Subject: Terminal Emulations 
> 
> How do you set up other terminal emulations for PINE besides vt100.  
> SPECIFICALLY, vp or ADDS VIEWPOINT.  Pine says that it does not support
> pine.  Isn't there something I can change in the configuration file of
> pine without changing my terminal emulation to something other than vt100
> or vt220 or whatever.  I want to use vp.  Any ideas?
> 
> Bill Murray
> arwhead@tyrell.net
> 
> 

On Fri, 30 Dec 1994, Bill Murray wrote:

> Date: Fri, 30 DEC 1994 18:47:55 GMT 
> From: Bill Murray <arwhead@tyrell.net>
> Newgroups: comp.mail.pine
> Subject: Somthng other than vt100 
> 
> I can't get my compiled version of PINE3.91 to work with a terminal emulation
> other than vt100.  When I run pine-bin.solaris for solaris2.x it comes up
> with an error message and never runs pine.  The error is:
> 
> Your terminal, of type "vp", is lacking functions needed to run pine.  And
> it's not just vp but many other emulations.  I've tried pine on another
> solaris machine and it works with the emulations I'm trying but my
> compiled version does not.
> 
> WHAT's WRONG?
> 
> Bill Murray
> arwhead@tyrell.net
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 17:02:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00399;
	Tue, 3 Jan 95 17:02:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24099;
	Tue, 3 Jan 95 16:58:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24093;
	Tue, 3 Jan 95 16:58:17 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPJtq-00038CC; Tue, 3 Jan 95 16:48 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: pop3d for Solaris2.3?
Date: Tue, 3 Jan 1995 15:08:33 -0800
Message-Id: <Pine.ULT.3.92.950103150643.27331z-100000@shiva1.cac.washington.edu>
References: <3e9kui$2as0@news-s01.ny.us.ibm.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3e9kui$2as0@news-s01.ny.us.ibm.net> 


Pine is available from ftp.cac.washington.edu in the pine directory.  The 
ipop3d server is included in the source distribution, pine.tar.Z.  For 
Solaris 2.3, add "-Dconst=" to the CFLAGS line in pine/makefile.sol 
before building.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 2 Jan 1995 emartin@ibm.net wrote:

> Date: 2 JAN 1995 19:42:10 GMT 
> From: emartin@ibm.net
> Newgroups: comp.mail.pine
> Subject: pop3d for Solaris2.3? 
> 
> Can anyone tell me where I can get pine for Solaris2.3.
> I understand It comes with a pop3 server, which is what Im really looking 
> for.
> 
> 		Thanks
> 		Ernie
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan  3 18:10:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03229;
	Tue, 3 Jan 95 18:10:58 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25555;
	Tue, 3 Jan 95 18:07:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.fast.net by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25549;
	Tue, 3 Jan 95 18:07:24 -0800
Received: from roland.fast.net by fast.net with smtp
	(Smail3.1.28.1 #13) id m0rPL8k-0002DmC; Tue, 3 Jan 95 21:07 EST
Date: Tue, 3 Jan 1995 21:03:23 -0800 (PST)
From: Roland Zuk <roland@fast.net>
To: pine-info@cac.washington.edu
Subject: SMTP Lost connections
X-Sender: roland@ns.fast.net
Message-Id: <Pine.PCW.3.91.950103205227.8015C-100000@roland.fast.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I'm having some trouble with PC-Pine Windows and would welcome any 
suggestions.  When I attempt to send a message, the system often hangs 
and comes back with a "Waiting for response from server" message, then 
eventually times out, giving the "Break connection?" prompt.

The Pinedebug log shows "Transfer protocol error: 421 SMTP connection 
went away."

I can usually recover and send mail by exiting and restarting Pine, then 
immediately sending the postponed message.

I'm running PC-Pine Win with the Trumpet Winsock via a dialup PPP 
connection.  Any suggestions?  Is the SMTP timeout a local problem or 
something on my service provider's end?

Thanks
Roland



P.S.  Kudos to the CAC Pine Team on continuing excellent work with Pine!
I'm a long time Unix Pine user and have installed the Windows port version 
for personal use at home for compatibility and because it beats the H^&#! 
out of any commercial package available.  Nice work!


From owner-pine-info@cac.washington.edu  Tue Jan  3 18:32:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03939;
	Tue, 3 Jan 95 18:32:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22927;
	Tue, 3 Jan 95 18:28:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from linknet.kitsap.lib.wa.us by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22921;
	Tue, 3 Jan 95 18:28:17 -0800
Received: (from michael@localhost) by linknet.kitsap.lib.wa.us (8.6.9/8.6.9) id SAA01008; Tue, 3 Jan 1995 18:26:10 -0800
Date: Tue, 3 Jan 1995 18:26:10 -0800 (PST)
From: Michael Schuyler <michael@linknet.kitsap.lib.wa.us>
To: pine-info@cac.washington.edu
Subject: Refusing  Export
In-Reply-To: <Pine.ULT.3.92.950103150038.27331v-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950103182308.808B-100000@linknet.kitsap.lib.wa.us>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there any wayto set up pine to refuse exports to the hme directory? I 
run a system where we offer e-mail, but not disk space-related services 
such as ftp, etc. I was able to prevent a suspen (ctrl-Z) with an option, 
but haven't found anything for export. 

  :::::;     . ,             Michael Schuyler               ..,     `::::::
  :::;' /)  - * -    michael@linknet.kitsap.lib.wa.us      - + -  (\ `:::::
  ::'  / )   ':`  Kitsap Regional Library, 1301 Sylvan Way  ':`   ( \_ `  :
  :' _( (_    _     Bremerton, WA  98310 (360) 405-9139       _    ) )\ />:




From owner-pine-info@cac.washington.edu  Tue Jan  3 18:36:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04065;
	Tue, 3 Jan 95 18:36:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25953;
	Tue, 3 Jan 95 18:32:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25947;
	Tue, 3 Jan 95 18:32:50 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPLKJ-00038CC; Tue, 3 Jan 95 18:19 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs
Date: 4 Jan 1995 00:48:50 GMT
Message-Id: <3ecr9i$2v2@cronkite.ocis.temple.edu>

Regarding:

 +  Set the read-msg-folder variable and the auto-move-read-msgs feature.

 +  P.S.  If you do this, please make sure to make the behavior very clear to 
 +  your users.  If you don't, we get flooded with bug reports ;)

Right, but that will affect each and every user. Perhaps I should have better
phrased my question which is: I want to penalise only *such* users who tend
to keep more than 1.5 Mgs worth of *read* mail in INBOX(system's mailspool)

Any user who is following proper diskspace-ettiquette by moving read mail from
INBOX to folders in his personal account space should not have that
read-msg-folder/auto-move-read-msgs p.i.b option by default IMHO.

Something like "if INBOX>1.5 Mgs move INBOX to $HOME/mail/movedmailfolder"...
Right now I have a csh script running to check that...but anyway....

Your headers indicate:

Message-ID: <Pine.ULT.3.92.950103122152.2731e-10000@shiva1.cac.washington.edu>

3.92? Any possibility of a scoop as to what's in 3.92? :))

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan  3 18:51:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04546;
	Tue, 3 Jan 95 18:51:57 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23217;
	Tue, 3 Jan 95 18:48:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23211;
	Tue, 3 Jan 95 18:47:58 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPLdc-00038KC; Tue, 3 Jan 95 18:39 PST
To: pine-info@cac.washington.edu
From: calfeld@ceslab03 (Chris Alfeld)
Subject: Re: Pico
Date: Wed, 4 Jan 1995 00:55:52 GMT
Message-Id: <1995Jan4.005552.10610@math.utah.edu>
References: <Pine.SUN.3.91.950102230701.7234B-100000@linknet.kitsap.lib.wa.us>

Michael Schuyler (michael@linknet.kitsap.lib.wa.us) wrote:
: Is there an OVERTYPE mode in Pico?

Nope, control-d is forward delete though.

--
-Chris 	(calfeld@math.utah.edu calfeld@east.east-slc.edu)
	Home Page: http://www.math.utah.edu/~calfeld/


From owner-pine-info@cac.washington.edu  Tue Jan  3 18:52:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04575;
	Tue, 3 Jan 95 18:52:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23209;
	Tue, 3 Jan 95 18:47:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23203;
	Tue, 3 Jan 95 18:47:50 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPLZz-00038CC; Tue, 3 Jan 95 18:36 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: trouble with the return address
Date: 4 Jan 1995 00:58:44 GMT
Message-Id: <3ecrs4$2v2@cronkite.ocis.temple.edu>

Comes here Mz. Patti Johnson with this opinion in the "comp.mail.pine" group in this article on Tue, 3 Jan 1995 19:12:14 GMT:

 +   While mailx correctly addresses the "From" field, pine omits the machine 
 +   name.  That is, here's the From from the two mailers:

 +   mailx:	johnson@micronet.wcu.edu
 +   pine:	johnson@wcu.edu

We had the same problem, which got fixed by setting this option in Setup/Config:

user-domain = <No Value Set>

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan  3 18:56:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04672;
	Tue, 3 Jan 95 18:56:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26157;
	Tue, 3 Jan 95 18:47:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26151;
	Tue, 3 Jan 95 18:47:56 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPLdb-00038JC; Tue, 3 Jan 95 18:39 PST
To: pine-info@cac.washington.edu
From: calfeld@ceslab03 (Chris Alfeld)
Subject: Re: Pine Pipe to Zmodem
Date: Wed, 4 Jan 1995 00:52:56 GMT
Message-Id: <1995Jan4.005256.10505@math.utah.edu>
References: <3e7qmc$rod@little-miami.iac.net>

Carl Jolley (cjolley@iac.net) wrote:
: I'm doing terminal emulation to my ISP. The default mailer is Pine. The
: pipe command IS configured but I can't get piping to: sz - to work. When
: I try it, the screen does display the zmodem init string, i.e *B00000....
: But I can't get it to connect up to my terminal emulation program's
: zmodem requestor. Piping from Elm and from Tin work just fine. The sysadmin
: gave me some non-understanable explaination about why the Pine pipe command
: doesn't work with 'sz'. Is the pipe command in Pine _that_ different from
: that of Elm (and Tin)?

I've never tried piping into sz but you might try this:

	| (cat > tmpfile;sz tmpfile;rm -f tmpfile)

--
-Chris 	(calfeld@math.utah.edu calfeld@east.east-slc.edu)
	Home Page: http://www.math.utah.edu/~calfeld/


From owner-pine-info@cac.washington.edu  Tue Jan  3 19:25:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05147;
	Tue, 3 Jan 95 19:25:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26539;
	Tue, 3 Jan 95 19:19:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26533;
	Tue, 3 Jan 95 19:19:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPM95-00038CC; Tue, 3 Jan 95 19:12 PST
To: pine-info@cac.washington.edu
From: The Mac*CHAT List Moderator <shrim@astro.ocis.temple.edu>
Subject: Re: Problem posting UUencoded files with PINE?
Date: Tue, 3 Jan 1995 20:32:05 -0500 (EST)
Message-Id: <Pine.BSD.3.90.950103202529.15018A-100000@astro.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3eaeus$g4q@crl4.crl.com> 

Comes here Mr. Brian Goss with this opinion in the"comp.mail.pine" group in this
article on 2 Jan 1995 19:06:04 -0800:

 +   I am having problems using the Read File option in pine to read in a 
 +   uuencoded file.  When I read in the file, pine says LINE TOO LONG and 
 +   automatically wraps all the text.  This, in turn, basically corruptes the 
 +   uuencoded data.  Can anyone help me with this problem?

Hmm....looks like the problem is with the way your uuencoder works.
I uuencoded your post and copied here, check and see if your uudecoder
can decode it and the uuencoder encodes the same way.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.

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

begin 600 yourpost.uu
M1G)O;3H@9W5R=7!U8FQ`8W)L+F-O;2`H0G)I86X@1V]S<RD*3F5W<V=R;W5P
M<SH@8V]M<"YM86EL+G!I;F4*4W5B:F5C=#H@4')O8FQE;2!P;W-T:6YG(%55
M96YC;V1E9"!F:6QE<R!W:71H(%!)3D4_"D1A=&4Z(#(@2F%N(#$Y.34@,3DZ
M,#8Z,#0@+3`X,#`*3W)G86YI>F%T:6]N.B!#4DP@1&EA;'5P($EN=&5R;F5T
M($%C8V5S<PDH-#$U*2`W,#4M-C`V,"`@6TQO9VEN.B!G=65S=%T*3&EN97,Z
M(#<*365S<V%G92U)1#H@/#-E865U<R1G-'%`8W)L-"YC<FPN8V]M/@I.3E10
M+5!O<W1I;F<M2&]S=#H@8W)L-"YC<FPN8V]M"E@M3F5W<W)E861E<CH@5$E.
M(%MV97)S:6]N(#$N,B!03#)="@I)(&%M(&AA=FEN9R!P<F]B;&5M<R!U<VEN
M9R!T:&4@4F5A9"!&:6QE(&]P=&EO;B!I;B!P:6YE('1O(')E860@:6X@82`*
M=75E;F-O9&5D(&9I;&4N("!7:&5N($D@<F5A9"!I;B!T:&4@9FEL92P@<&EN
M92!S87ES($Q)3D4@5$]/($Q/3D<@86YD(`IA=71O;6%T:6-A;&QY('=R87!S
M(&%L;"!T:&4@=&5X="X@(%1H:7,L(&EN('1U<FXL(&)A<VEC86QL>2!C;W)R
M=7!T97,@=&AE(`IU=65N8V]D960@9&%T82X@($-A;B!A;GEO;F4@:&5L<"!M
992!W:71H('1H:7,@<')O8FQE;3\*"D)'"BX@
`
end



From owner-pine-info@cac.washington.edu  Tue Jan  3 20:00:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05839;
	Tue, 3 Jan 95 20:00:11 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24203;
	Tue, 3 Jan 95 19:56:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24197;
	Tue, 3 Jan 95 19:56:44 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPMex-00038CC; Tue, 3 Jan 95 19:45 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: View Message screen constantly redraws?
Date: 4 Jan 1995 01:54:26 GMT
Message-Id: <3ecv4i$2v2@cronkite.ocis.temple.edu>

Comes here Mr. Ed Greshko with this opinion in the"comp.mail.pine" group in this
article on Wed, 4 Jan 1995 07:40:51 GMT:

 +   > P.S. In 3.91, is there a way to specify how often you want it to check 
 +   > for new mail?

 +   	Yes, but I for got what .h file it is...   :-( ;-(

Hmm...that could be pine/osdep/os-machine.h (os-hpp.h in your case?), change
150(=60*2.5) to whatever you feel is appropriate for your situation.

Here's the relevant portion of the os-sun.h (for Sun systems).....

/*----------------------------------------------------------------------
  $Id: os-sun.h,v 5.19 1994/10/10 22:29:35 mikes Exp $

  ----------------------------------------------------------------------*/

#define NEW_MAIL_TIME      (150) /* How often to check for new mail. There's 
                                   some expense in doing this so it shouldn't
                                   be done too frequently.  */

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan  3 20:22:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06249;
	Tue, 3 Jan 95 20:22:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27499;
	Tue, 3 Jan 95 20:19:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27493;
	Tue, 3 Jan 95 20:19:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPN4U-00038CC; Tue, 3 Jan 95 20:11 PST
To: pine-info@cac.washington.edu
From: jdavis@CS.Arizona.EDU (Jim Davis)
Subject: Re: Refusing  Export
Date: 3 Jan 1995 20:46:13 -0700
Message-Id: <3ed5m5$iig@wolf.CS.Arizona.EDU>
References: <Pine.ULT.3.92.950103150038.27331v-100000@shiva1.cac.washington.edu> <Pine.SUN.3.91.950103182308.808B-100000@linknet.kitsap.lib.wa.us>

In article <Pine.SUN.3.91.950103182308.808B-100000@linknet.kitsap.lib.wa.us>,
Michael Schuyler <michael@linknet.kitsap.lib.wa.us> wrote:
:Is there any wayto set up pine to refuse exports to the hme directory?

According to the man page, running pine with the '-r' flag will
prevent exports (among other things).

If that won't suffice then you'll probably have to hack the source.
The quickest thing I could spot would be to modify the first
if-statement in the cmd_export function in mailcmd.c in the obvious
way.



From owner-pine-info@cac.washington.edu  Tue Jan  3 22:16:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08291;
	Tue, 3 Jan 95 22:16:08 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26050;
	Tue, 3 Jan 95 22:11:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26044;
	Tue, 3 Jan 95 22:11:58 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPOlL-00038CC; Tue, 3 Jan 95 21:59 PST
To: pine-info@cac.washington.edu
From: Neil Steffen <nsteffen@cyberport.net>
Subject: How Can I POST Pretyped Documents in NEWS??
Date: 4 Jan 1995 06:00:12 GMT
Message-Id: <3eddhc$5mc@cpmt.cyberport.net>

       I have MOZILLA 1.0N and  Chameleon. I have typed many documents
 that I cannot export into NEWS via "newspost:comp.mail.pine"  with
my  Mail Document Button. 
	What is the command or do I need to use a GATEWAY to transfer
 Documents?     Thanks for your support.
  


From owner-pine-info@cac.washington.edu  Tue Jan  3 22:17:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08326;
	Tue, 3 Jan 95 22:17:02 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28961;
	Tue, 3 Jan 95 22:13:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28955;
	Tue, 3 Jan 95 22:13:12 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPOsW-00038JC; Tue, 3 Jan 95 22:07 PST
To: pine-info@cac.washington.edu
From: Marty Brenneis <droid@nbn.com>
Subject: Re: Still can't open INBOX
Message-Id: <D1v9yC.6zD@nbn.com>
References: <D1p1IC.82A@nbn.com> <Pine.SOL.3.91.950101210817.29909B-100000@hobbes>
Date: Wed, 4 Jan 1995 05:58:59 GMT

egreshko@hobbes.twntpe.cdc.com (Ed Greshko) wrote:
>
> On Sat, 31 Dec 1994, Marty Brenneis wrote:
> 
> > So I still can't get pine to find my host.
> > I set the inbox to match that shown in the manual (yes, I did
> > insert my host's name). No matter how I format the name of the host
> > I get an error #11004 that states it can't find the host. I can
> > ping the host with no problem. I can access my mail with the Netmanage
> > mail program (bleah). I am using Netmanage Chamelon Sampler for the
> > TCP/IP winsock stuff. Other clues, I can read news from the news site
> > here.
> > 
> > Anyone got more hints?
> 	What do you get when you do:
> 
> telnet hostname 143
> 
I get the login for the IMAP server.

When I load pine it still complains about how it can't find the host.

I dinked around with it more this evening and find that I can go to
'L' list folders menu and ask it to open the INBOX. It then connects
to the server and asks for my password. Then is complains that
the SELECT command can't find /usr/spool/mail/droid. This is what I
was told was the name of my inbox on that system.

Any more hints?

Marty Brenneis
Industrial Magician
droid@nbn.com



From owner-pine-info@cac.washington.edu  Tue Jan  3 22:36:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08740;
	Tue, 3 Jan 95 22:36:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26297;
	Tue, 3 Jan 95 22:32:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26291;
	Tue, 3 Jan 95 22:32:13 -0800
Received: from ip-pdx3-29.teleport.com (ip-pdx3-29.teleport.com [204.119.60.157]) by desiree.teleport.com (8.6.9/8.6.9) with SMTP id WAA03024 for <pine-info@cac.washington.edu>; Tue, 3 Jan 1995 22:32:10 -0800
Date: Tue, 3 Jan 1995 22:32:10 -0800
Message-Id: <199501040632.WAA03024@desiree.teleport.com>
X-Sender: knute@mail.teleport.com
X-Mailer: Windows Eudora Version 1.4.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: pine-info@cac.washington.edu
From: knute@teleport.com (Knute Snortum)
Subject: Pine binaries

I work for a VAR and we are looking at Pine to be the mail reader we
distribute with our systems, as well as use in house.  We have clients with
several versions of Unix, including a "tweeked" version of System VII by Altos.

I just discovered (and can someone comfirm?) that Pine cannot be compiled
without a developer's version of TCP/IP.  No problem for us internally; it
works fine.  But what about our other clients?  Specifically, this weirdo
Altos Unix refuses to execute the standard Unix binary.  Do you have to tell
our client to buy the developer's version of TCP/IP?

What I'd really like is a wayy to get Pine binaries for different flavors of
Unix.  Any hints?

---Knute (knute@msi.masi.com, knute@teleport.com)



From owner-pine-info@cac.washington.edu  Tue Jan  3 23:16:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09861;
	Tue, 3 Jan 95 23:16:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26875;
	Tue, 3 Jan 95 23:12:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26863;
	Tue, 3 Jan 95 23:12:04 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPPjY-00038CC; Tue, 3 Jan 95 23:02 PST
To: pine-info@cac.washington.edu
From: mlk68@imap1.asu.edu
Subject: Where are my TIN saved files?
Date: 4 Jan 1995 06:54:24 GMT
Message-Id: <3edgn0$f42@news.asu.edu>

	I am working with a TIN newsreader and can not locate my saved 
article files. I go through the process of saving files that I find in 
the Internet newsgroups and giving them a name. When I go to the FTP 
saved files directory, they aren't there. Please, please help.

--
Michael Leshowitz
mlk68@imap1.asu.edu


From owner-pine-info@cac.washington.edu  Wed Jan  4 05:28:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18881;
	Wed, 4 Jan 95 05:28:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04666;
	Wed, 4 Jan 95 05:19:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04660;
	Wed, 4 Jan 95 05:18:58 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPVVr-00038CC; Wed, 4 Jan 95 05:12 PST
To: pine-info@cac.washington.edu
From: kkeyte%esoc.BITNET@arizvm1.ccit.arizona.edu (Karl Keyte)
Message-Id: <19950104.113544.069884.NETNEWS@ESOC>
Date: Wed, 4 Jan 1995 11:35:43 +0100
Subject: Adding mail header lines

I'm running pine 3.91 on a Linux system.  I want to be able to add mail header
lines as I compose a message. Typically I send mail from one system but want
replies to go elsewhere, so I want to insert a 'Reply-To:' entry in the header.

Does anyone know how I can do this? I must be just missing something.

Karl

-------------------------------------------------------------------------
Vitrociset S.p.A.				Tel   : +(49) 6151 902041
European Space Agency				Fax   : +(49) 6151 904041
64293 Darmstadt, Germany			e-Mail: KKEYTE@ESOC.BITNET


From owner-pine-info@cac.washington.edu  Wed Jan  4 06:03:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19816;
	Wed, 4 Jan 95 06:03:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02217;
	Wed, 4 Jan 95 05:57:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02211;
	Wed, 4 Jan 95 05:57:32 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPWAf-00038CC; Wed, 4 Jan 95 05:54 PST
To: pine-info@cac.washington.edu
From: paul_haring@jhuapl.edu (Paul S. Haring)
Subject: Re: Where are my TIN saved files?
Message-Id: <paul_haring.5.0008E30D@jhuapl.edu>
References: <3edgn0$f42@news.asu.edu>
Date: Wed, 4 Jan 1995 13:53:09 GMT

In article <3edgn0$f42@news.asu.edu> mlk68@imap1.asu.edu writes:
>From: mlk68@imap1.asu.edu
>Subject: Where are my TIN saved files?
>Date: 4 Jan 1995 06:54:24 GMT

>        I am working with a TIN newsreader and can not locate my saved 
>article files. I go through the process of saving files that I find in 
>the Internet newsgroups and giving them a name. When I go to the FTP 
>saved files directory, they aren't there. Please, please help.

>--
>Michael Leshowitz
>mlk68@imap1.asu.edu

Read your .tinrc file, in it is a line specifing the "save" directory.  
It's usually ~/News.  There's lots of good stuff in .tinrc, look it over 
carefully.						-- Paul --


From owner-pine-info@cac.washington.edu  Wed Jan  4 08:09:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23936;
	Wed, 4 Jan 95 08:09:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07420;
	Wed, 4 Jan 95 08:04:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07414;
	Wed, 4 Jan 95 08:04:14 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPY4p-00038CC; Wed, 4 Jan 95 07:56 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: Pine binaries
Date: Wed, 4 Jan 1995 15:46:55 GMT
Message-Id: <D1w168.CCD@ssi.edc.org>
References: <199501040632.WAA03024@desiree.teleport.com>

Knute Snortum (knute@teleport.com) wrote:
: I just discovered (and can someone comfirm?) that Pine cannot be compiled
: without a developer's version of TCP/IP.  No problem for us internally; it
: works fine.  But what about our other clients?  Specifically, this weirdo
: Altos Unix refuses to execute the standard Unix binary.  Do you have to tell
: our client to buy the developer's version of TCP/IP?

The Developer's Version of TCP/IP applies only to SCO Unix.  You're 
likely to have to port Pine yourself to any platforms it doesn't already 
support.  But it supports so many so well, that you should be able to 
find a good place to start.  It sounds like you're expecting binary 
compatibility between youre various flavors of Unix - you won't get it.  
You'll pretty much need to recompile Pine for each separate OS, unless 
you know for sure beforehand it will work.

: What I'd really like is a wayy to get Pine binaries for different flavors of
: Unix.  Any hints?

Several can be found at ftp.cac.washington.edu.  For the others, try 
crossposting here and in the system-specific newsgroup for anyone who 
might have already solved your difficulties.  But cross-platform 
development is a hard problem, and it sounds like you're going to get in 
thick.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Wed Jan  4 08:17:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24250;
	Wed, 4 Jan 95 08:17:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04463;
	Wed, 4 Jan 95 08:12:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04457;
	Wed, 4 Jan 95 08:12:33 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPYHI-00038CC; Wed, 4 Jan 95 08:09 PST
To: pine-info@cac.washington.edu
From: hcn@sysdeco.no (Hans Chr. Nielsen)
Subject: HP/UX NFS locking problem
Date: 4 Jan 1995 15:29:19 GMT
Message-Id: <3eeesf$ce2@lion>

Our system supervisor has added some patches to our HP/UX workstations.
We use HP/UX 9.01; I have not been able to find any description of the
patches. Everything except pine works OK.

After these patches pine keeps locking up. It happens when it tries
to open a folder in my folder directory. It creates a <folder>.lock file
and nothing happens after this. It may also lock up when opening the
sent-mail folder to save a copy of outgoing mail. The same lock file
is created. The hanging process may not be killed.
 
This only happens on a workstation where my home-directory (and folder
directory) is nfs-mounted. The server is the patched hp.
The problem occurs on hps running pine 3.07 but not on suns running 3.07.
I compiled 3.91 for hp,rs6000 and sun. The problem occurs on hps and rs6000s.
Sun is still OK. Running pine on the nfs server is also OK.

Any suggestions will be greatly appreciated. I don't think I will get any
help from HP as pine is the only program that has problems.
-- 
  hans chr n

  Hans Chr Nielsen, Sysdeco Innovation A/S
  Chr. Michelsens gt 65, N-0474 OSLO
  Tel +47 22383090  Fax +47 22382555
  Email: hcn@sysdeco.no


From owner-pine-info@cac.washington.edu  Wed Jan  4 08:58:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26124;
	Wed, 4 Jan 95 08:58:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08493;
	Wed, 4 Jan 95 08:53:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08487;
	Wed, 4 Jan 95 08:53:23 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPYrK-00038LC; Wed, 4 Jan 95 08:46 PST
To: pine-info@cac.washington.edu
From: Edward Vielmetti <emv@recepsen.aa.msen.com>
Subject: Address book tools
Date: Wed, 4 Jan 1995 11:38:47 -0500
Message-Id: <Pine.BSI.3.91.950104113141.27761B-100000@recepsen.aa.msen.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'm adding a ton of new entries to my address book these days, and can 
think of a few tools that would make the process easier.  (The objective 
is to minimize wrong or stale entries).  A few come to mind right away:

- a way to exercise the SMTP "VRFY" command from the address book, so 
  that you can tell whether an address is deliverable
- an interface to finger, whois, or some other directory service
  so that you can look people up
- a more visible "comments" screen
- and of course some support for shared or remote address books.

thanks

  Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
Msen Inc., 320 Miller, Ann Arbor MI  48103 +1 313 998 4562 (fax: 998 4563)




From owner-pine-info@cac.washington.edu  Wed Jan  4 08:58:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26161;
	Wed, 4 Jan 95 08:58:53 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08369;
	Wed, 4 Jan 95 08:48:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08363;
	Wed, 4 Jan 95 08:48:44 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPYcx-00038CC; Wed, 4 Jan 95 08:31 PST
To: pine-info@cac.washington.edu
From: lucio@ifctr.mi.cnr.it (Lucio Chiappetti)
Subject: Re: trouble with the return address
Date: 4 Jan 1995 10:29:41 -0600
Message-Id: <9601041638.AA18276@poseidon.ifctr.mi.cnr.it>
References: <3ecrs4$2v2@cronkite.ocis.temple.edu>

In article <3ecrs4$2v2@cronkite.ocis.temple.edu>, shrim@astro.ocis.temple.edu (Wet-Sprocket) write:
|> Comes here Mz. Patti Johnson with this opinion in the "comp.mail.pine" group in this article on Tue, 3 Jan 1995 19:12:14 GMT:
|> 
|>  +   While mailx correctly addresses the "From" field, pine omits the machine 
|>  +   name.  That is, here's the From from the two mailers:
|>  +   mailx:	johnson@micronet.wcu.edu
|>  +   pine:	johnson@wcu.edu
|> 
|> We had the same problem, which got fixed by setting this option in Setup/Config:
|> user-domain = <No Value Set>

   In fact pine is trying to enforce (but escapes are possible as shown
   above) a very reasonable thing, that is, mail is sent to somebody
   at some domain. Nobody cares about which machine is used for receiving
   the mail, and this information should not go out.

   The mail exchanger for the receiving domain should take care of
   forwarding the mail to the user machine in a way transparent and
   invisible to the sender of the mail.
   Here as in most places we receive all mails as user@ifctr.mi.cnr.it
   and the mail exchanger knows that my mail goes to poseidon, another
   guy's goes to helios and so on.
   If tomorrow I would move to another machine, or even on leave to
   another place, I'd just have to change the local alias and the rest
   of the world wouldn't even note.

   Having the machine name in the address is more or less as 
   sending somebody a letter not as

       Mr. Pinco Pallino
       Broad Street 24

   but

       Mr. Pinco Pallino
       Broad Street 24
       the second mailbox in the third row on the shelf
       in staircase E

   Don't you agree that this information should be known only to
   the porter of Broad Street 24, or the postman ?

-- 
---------------------------------------------------------------------------- 
       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: LUCIO@IFCTR.MI.CNR.IT  |                                           
Decnet:   IFCTR::LUCIO           |             (Rabisch, II 46, 119-120)     
---------------------------------------------------------------------------- 


From owner-pine-info@cac.washington.edu  Wed Jan  4 09:01:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26331;
	Wed, 4 Jan 95 09:01:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05271;
	Wed, 4 Jan 95 08:53:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05265;
	Wed, 4 Jan 95 08:53:21 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPYjk-00038KC; Wed, 4 Jan 95 08:39 PST
To: pine-info@cac.washington.edu
From: kira@fohnix.metronet.com (Jacqueline Hamilton)
Subject: can I post news from pine?
Date: 4 Jan 1995 10:37:36 -0600
Message-Id: <3eeisg$3vb@fohnix.metronet.com>


I've got a mail message that I'd like to redirect as a post to a newsgroup.
Is this doable from pine?  I'm digging through the builtin help but haven't
found much about news features.

(I dont want to reply to the message either - just basically bounce it to 
news)

Any info appreciated!

-j.


-- 
-Jackie Hamilton
kira@metronet.com
http://fohnix.metronet.com/HomePages/kira/newhome.html


From owner-pine-info@cac.washington.edu  Wed Jan  4 09:29:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28026;
	Wed, 4 Jan 95 09:29:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06161;
	Wed, 4 Jan 95 09:25:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06155;
	Wed, 4 Jan 95 09:25:42 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPZNL-00038CC; Wed, 4 Jan 95 09:19 PST
To: pine-info@cac.washington.edu
From: calfeld@ceslab01 (Chris Alfeld)
Subject: Re: Adding mail header lines
Date: Wed, 4 Jan 1995 16:57:02 GMT
Message-Id: <1995Jan4.165702.25666@math.utah.edu>
References: <19950104.113544.069884.NETNEWS@ESOC>

Karl Keyte (kkeyte@esoc.bitnet) wrote:
: I'm running pine 3.91 on a Linux system.  I want to be able to add mail header
: lines as I compose a message. Typically I send mail from one system but want
: replies to go elsewhere, so I want to insert a 'Reply-To:' entry in the header.

: Does anyone know how I can do this? I must be just missing something.

Go to Setup/Config from the menu menu.  Go down to custom-headers
and add any headers you want.

--
-Chris 	(calfeld@math.utah.edu calfeld@east.east-slc.edu)
	Home Page: http://www.math.utah.edu/~calfeld/


From owner-pine-info@cac.washington.edu  Wed Jan  4 10:33:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00790;
	Wed, 4 Jan 95 10:33:05 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10866;
	Wed, 4 Jan 95 10:23:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10860;
	Wed, 4 Jan 95 10:23:34 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPaGH-00038CC; Wed, 4 Jan 95 10:16 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: Pine Pipe to Zmodem
Date: 4 Jan 1995 12:57:25 -0500
Message-Id: <3eeni5$t36@wabash.iac.net>
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu>

Chris Alfeld (calfeld@ceslab03) wrote:
: Carl Jolley (cjolley@iac.net) wrote:
: : I'm doing terminal emulation to my ISP. The default mailer is Pine. The
: : pipe command IS configured but I can't get piping to: sz - to work. When
: : I try it, the screen does display the zmodem init string, i.e *B00000....
: : But I can't get it to connect up to my terminal emulation program's
: : zmodem requestor. Piping from Elm and from Tin work just fine. The sysadmin
: : gave me some non-understanable explaination about why the Pine pipe command
: : doesn't work with 'sz'. Is the pipe command in Pine _that_ different from
: : that of Elm (and Tin)?

: I've never tried piping into sz but you might try this:

: 	| (cat > tmpfile;sz tmpfile;rm -f tmpfile)

I tried this and it works identically to just doing : sz -
i.e. it doesn't work. In both cases it does fire up the host system zmodem
and it displays the init string , i.e. **B0000000000000 but then on the
next line it displays ten or so question marks. Oh, also when I do get
back to Pine it it presents me with a screen as though I had Replied to
the message and then entered ^X, i.e. the screen has quoted the message I
was trying to d/l, and at the top there is a skeleton reply message, complete
with my signature and Pine is asking if I want to send the reply. Oh, one
small detail I forgot, when the host system's zmodem fires up, prior to
display of the init sting it sends a response that the zmodem has been
initiated in batch mode. No big deal but it does appear that everything up
until that point and enen through the sending of the init string is exactly
what one would expect. Invariably if I then manually initiate the zmodem
recieve from my end, it times out. The host system's zmodem is not talking
to my end. It appears possibly that the stuff that zmodem would normally
be sending to me is somehow being sent back to Pine.
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Wed Jan  4 10:50:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01486;
	Wed, 4 Jan 95 10:50:45 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08101;
	Wed, 4 Jan 95 10:45:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08095;
	Wed, 4 Jan 95 10:45:50 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPaeC-00038CC; Wed, 4 Jan 95 10:41 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs
Date: Wed, 4 Jan 1995 10:03:07 -0800
Message-Id: <Pine.ULT.3.92.950104094406.8935P-100000@shiva1.cac.washington.edu>
References: <3ecr9i$2v2@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3ecr9i$2v2@cronkite.ocis.temple.edu> 


On 4 Jan 1995, Wet-Sprocket wrote:

> Date: 4 JAN 1995 00:48:50 GMT 
> From: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: Re: [Q] Move to Read-Msg Folder/pine.conf.fixed/INBOX > 1.5 Mgs 
> 
> Regarding:
> 
>  +  Set the read-msg-folder variable and the auto-move-read-msgs feature.
> 
>  +  P.S.  If you do this, please make sure to make the behavior very clear to 
>  +  your users.  If you don't, we get flooded with bug reports ;)
> 
> Right, but that will affect each and every user. Perhaps I should have better
> phrased my question which is: I want to penalise only *such* users who tend
> to keep more than 1.5 Mgs worth of *read* mail in INBOX(system's mailspool)
> 
> Any user who is following proper diskspace-ettiquette by moving read mail from
> INBOX to folders in his personal account space should not have that
> read-msg-folder/auto-move-read-msgs p.i.b option by default IMHO.
> 
> Something like "if INBOX>1.5 Mgs move INBOX to $HOME/mail/movedmailfolder"...
> Right now I have a csh script running to check that...but anyway....
> 

Ahhh, Pine doesn't have any capability like that.  Offhand, I would
probably put a csh/perl wrapper around Pine that made the check and did
the dirty work before invoking the real Pine.  Some small utilities that 
may be useful for copying remote folders or converting formats are:

	ftp://ftp.cac.washington.edu/mail/imapcopy.tar.Z
	ftp://ftp.cac.washington.edu/mail/mbxcopy.tar.Z
	ftp://ftp.cac.washington.edu/mail/mbxcvt.tar.Z

> Your headers indicate:
> 
> Message-ID: <Pine.ULT.3.92.950103122152.2731e-10000@shiva1.cac.washington.edu>
> 
> 3.92? Any possibility of a scoop as to what's in 3.92? :))
> 

Pine 3.92 will be mostly bug fixes and optimization, though a few new
features have been added, like ESMTP 8BITMIME support, mime.types support,
a default-saved-msg-folder variable, etc.  Over the holiday we have been
experimenting with primitive xterm mouse support... 

To answer the next question, no, we do not have an expected release date 
for Pine 3.92 yet...

--DLM

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Wed Jan  4 11:05:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02052;
	Wed, 4 Jan 95 11:05:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11621;
	Wed, 4 Jan 95 11:00:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11615;
	Wed, 4 Jan 95 11:00:51 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPapN-00038KC; Wed, 4 Jan 95 10:52 PST
To: pine-info@cac.washington.edu
From: Frank Gallant <fgallant@anselm.edu>
Subject: Pine bug address problem. HELP!
Date: Wed, 4 Jan 1995 13:22:58 -0500
Message-Id: <Pine.OSF.3.91.950104132155.16499E-100000@hawk.anselm.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


	I have just set up pine for an OSF1 system. Most of it is working 
fine EXCEPT:
	I want the users on the system to report bugs directly to me 
instead of the standard bug address.  I've changed the bug-fullname and 
the bug-address in pine.conf file, but it never sees it.  The pine-degug 
file still shows the original address being read.  Where should i change 
this information?
	Any assistance would be greatly appreciated.


Happy Computing

Frank




From owner-pine-info@cac.washington.edu  Wed Jan  4 11:33:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03234;
	Wed, 4 Jan 95 11:33:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12335;
	Wed, 4 Jan 95 11:28:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12329;
	Wed, 4 Jan 95 11:28:30 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPbFR-00038JC; Wed, 4 Jan 95 11:19 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Pine binaries
Date: Wed, 4 Jan 1995 10:45:25 -0800
Message-Id: <Pine.ULT.3.92.950104104129.8935Q-100000@shiva1.cac.washington.edu>
References: <199501040632.WAA03024@desiree.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <199501040632.WAA03024@desiree.teleport.com> 

On Wed, 4 Jan 1995, Knute Snortum wrote:

> I just discovered (and can someone comfirm?) that Pine cannot be compiled
> without a developer's version of TCP/IP.  No problem for us internally; it
> works fine.  But what about our other clients?  Specifically, this weirdo
> Altos Unix refuses to execute the standard Unix binary.  Do you have to tell
> our client to buy the developer's version of TCP/IP?
> 

You could compile the distribution on your in-house systems and distribute
those binaries.  That is assuming you have a system in-house that is
compatible with your client's system... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Wed Jan  4 11:34:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03272;
	Wed, 4 Jan 95 11:34:18 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09052;
	Wed, 4 Jan 95 11:28:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09046;
	Wed, 4 Jan 95 11:28:27 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPbFl-00038KC; Wed, 4 Jan 95 11:20 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Address book tools
Date: Wed, 4 Jan 1995 10:50:14 -0800
Message-Id: <Pine.ULT.3.92.950104104723.8935R-100000@shiva1.cac.washington.edu>
References: <Pine.BSI.3.91.950104113141.27761B-100000@recepsen.aa.msen.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.BSI.3.91.950104113141.27761B-100000@recepsen.aa.msen.com> 

On Wed, 4 Jan 1995, Edward Vielmetti wrote:

> Date: Wed, 4 JAN 1995 11:38:47 -0500 
> From: Edward Vielmetti <emv@recepsen.aa.msen.com>
> Newgroups: comp.mail.pine
> Subject: Address book tools 
> 
> I'm adding a ton of new entries to my address book these days, and can 
> think of a few tools that would make the process easier.  (The objective 
> is to minimize wrong or stale entries).  A few come to mind right away:
> 
> - a way to exercise the SMTP "VRFY" command from the address book, so 
>   that you can tell whether an address is deliverable

Interesting suggestion...

> - an interface to finger, whois, or some other directory service
>   so that you can look people up

This is planned....

> - a more visible "comments" screen

We have not yet figured out how best to do this, but we are looking into
it... 

> - and of course some support for shared or remote address books.

Shared addressbooks are available now, remote will come later...

--DLM

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Wed Jan  4 12:03:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04565;
	Wed, 4 Jan 95 12:03:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09865;
	Wed, 4 Jan 95 11:58:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09859;
	Wed, 4 Jan 95 11:58:33 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPbk5-00038KC; Wed, 4 Jan 95 11:51 PST
To: pine-info@cac.washington.edu
From: eggert@twinsun.com (Paul Eggert)
Subject: Re: Time zone mvar PC-Pine
Date: 4 Jan 1995 10:58:41 -0800
Message-Id: <3eer51$mro@tattoo.twinsun.com>
References: <bparker.73.0DD32032@interaccess.com>

bparker@interaccess.com (Ben Parker) writes:

> The instructions in the tech notes for Pine are not really clear about the 
> proper use and format of the TZ environment variable ...  In my case
> (Illinois, USA) this should be CST-6CDT (since we are 6hrs behind or later
> than GMT)  However when I do this, PC-Pine sets the msg time to GMT+6 ...

The instructions in the Pine tech-notes are incorrect with respect to sign.
TZ offsets are west of GMT, not east; thus your TZ should be "CST6CDT".

> What is the correct setting for Newfoundland (Canada) which is -3.5 hrs GMT?

"NST3:30NDT".  The tech notes don't explain this, unfortunately.

> what is the correct setting for number greater than 1 digit (e.g. 11 hrs)?

The offset can be more than one digit, e.g. "NZST-12" for Fiji.

>Also, will PC-Pine automatically adjust for Daylight Savings Time periods 
>(April to October) or does the TZ Variable need to be reset manually during 
>that time?

It should figure it out automatically.

One tricky thing is what to do when the daylight savings time
switchover rules are different from the default US rules.  For New
Zealand, for example, you'll need a TZ value that is something like
"NZST-12NZDT,M10.1.0/2,M3.3.0/3", since NZ switches to summer time the
first Sunday in October at 02:00 and switch back the third Sunday in
March at 03:00.  This is all explained in the Posix 1003.1 standard,
section 8.1.1, ``Extensions to the Time Functions''.  This should
probably be covered in the Pine tech notes too.


From owner-pine-info@cac.washington.edu  Wed Jan  4 13:28:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08242;
	Wed, 4 Jan 95 13:28:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15095;
	Wed, 4 Jan 95 13:13:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15089;
	Wed, 4 Jan 95 13:13:43 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPcs3-00038JC; Wed, 4 Jan 95 13:03 PST
To: pine-info@cac.washington.edu
From: derda@dogwood.botany.uga.edu (Greg Derda)
Subject: Insert Mode in Pico?
Date: 4 Jan 1995 20:37:20 GMT
Message-Id: <3ef0u0$ppb@hobbes.cc.uga.edu>


Does anyone know if there is a way to put 'pico' in the insert (typeover)
mode?  

Thank you,
Greg
----

###########################################################################
# GREG DERDA                              Network Administrator           #
# 2502 Plant Sciences                     derda@dogwood.botany.uga.edu    #
# Department of Botany                    (706) 542-1804                  #
# University of Georgia                   (706)-542-1805 FAX              #
# Athens, GA, USA 30602    dogWWWood -->  http://dogwood.botany.uga.edu/  #
###########################################################################




From owner-pine-info@cac.washington.edu  Wed Jan  4 16:14:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14346;
	Wed, 4 Jan 95 16:14:35 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18739;
	Wed, 4 Jan 95 16:05:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from aurore.umd.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18733;
	Wed, 4 Jan 95 16:05:21 -0800
Received: from localhost.umd.edu (localhost.umd.edu [127.0.0.1]) by aurore.umd.edu (8.6.9/8.6.6) with SMTP id TAA21444 for <pine-info@cac.washington.edu>; Wed, 4 Jan 1995 19:01:38 -0500
Message-Id: <199501050001.TAA21444@aurore.umd.edu>
X-Authentication-Warning: aurore.umd.edu: Host localhost.umd.edu didn't use HELO protocol
To: pine-info@cac.washington.edu
Subject: Problems with PCPINE 3.91 and SunOS
Date: Wed, 04 Jan 1995 19:01:35 -0500
From: Larry Lentner <larry@aurore.umd.edu>

I have the packet driver version of PCPINE 3.91 that I'm using
to communicate with a Sun Sparcstation 5 running the imapd
included in the pine 3.91 distribution and sendmail 8.6.9. It's
also functioning as a nameserver, running BIND 4.9.2.

When I finish composing a message and go to send the message,
there's a 30-second delay between the time I hit send and the
time pcpine drops me back to a prompt. I had a DECstation 5000/25
running Ultrix 4.3 and BIND 4.9.2 before I replaced it with the
Sun and I didn't have this problem with the DEC.

This is causing my impatient users some major headaches. Has
anyone else experienced this as well or have any suggestions
on how I might go about fixing it?

Thanks,

Larry Lentner
UMCEES/CBL Computer Center


From owner-pine-info@cac.washington.edu  Wed Jan  4 16:27:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14813;
	Wed, 4 Jan 95 16:27:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15955;
	Wed, 4 Jan 95 16:22:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15949;
	Wed, 4 Jan 95 16:22:31 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 5 Jan 95 08:20:55 -0800
Date: Thu, 5 Jan 1995 08:20:54 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: David L Miller <dlm@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Address book tools
In-Reply-To: <Pine.ULT.3.92.950104104723.8935R-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SOL.3.91.950105081234.21226A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 4 Jan 1995, David L Miller wrote:
 
> > - a way to exercise the SMTP "VRFY" command from the address book, so 
> >   that you can tell whether an address is deliverable
> 
> Interesting suggestion...

	Interesting....yes.  Useful?  Maybe.  Many SMTP servers do not
allow "VRFY".  Many addresses are on the other side of Gateways and the
Gateway itself doesn't give an indication that the address is deliverable.
This goes for many addresses that are being taken care of by an MX record.
I believe that there would be too many cases of addresses being declaired
as "deliverable" when in fact they may not be deliverable.  

					Ed

P.S.	I like the rest of the suggestions....

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan  4 17:21:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17409;
	Wed, 4 Jan 95 17:21:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17446;
	Wed, 4 Jan 95 17:16:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17440;
	Wed, 4 Jan 95 17:16:37 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPgho-00038JC; Wed, 4 Jan 95 17:09 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Where are my TIN saved files?
Date: 5 Jan 1995 00:33:38 GMT
Message-Id: <3efep2$dl0@cronkite.ocis.temple.edu>

Comes here Mr. mlk68@imap1.asu.edu with this opinion in  "comp.mail.pine" group in this article on 4 Jan 1995 06:54:24 GMT:

 +   	I am working with a TIN newsreader and can not locate my saved 
 +   article files. I go through the process of saving files that I find in 
 +   the Internet newsgroups and giving them a name. When I go to the FTP 
 +   saved files directory, they aren't there. Please, please help.

You can view/change the options set by hitting M at the Group Index Screen.
You can also manually change those by editing the .tin/tinrc file.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Wed Jan  4 17:33:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17770;
	Wed, 4 Jan 95 17:33:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20796;
	Wed, 4 Jan 95 17:29:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20790;
	Wed, 4 Jan 95 17:29:09 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPgrH-00038CC; Wed, 4 Jan 95 17:19 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: trouble with the return address
Date: 5 Jan 1995 00:49:01 GMT
Message-Id: <3efflt$dl0@cronkite.ocis.temple.edu>

Comes here Mr. Lucio Chiappetti with this opinion in the "comp.mail.pine" group in this article on 4 Jan 1995 10:29:41 -0600:

 +      In fact pine is trying to enforce (but escapes are possible as shown
 +      above) a very reasonable thing, that is, mail is sent to somebody
 +      at some domain. Nobody cares about which machine is used for receiving
 +      the mail, and this information should not go out.

 +      The mail exchanger for the receiving domain should take care of
 +      forwarding the mail to the user machine in a way transparent and
 +      invisible to the sender of the mail.

Good point, but then you do require a robust mail-server which keeps routing
off all the incoming mail to respective sub-domain hosts.

Not all do have access to this yet, some notable univ. here who support this
idea are umich.edu, uiuc.edu. It would be nice if this gets standardized.

Comments, anyone ?

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Wed Jan  4 21:07:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23464;
	Wed, 4 Jan 95 21:07:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20909;
	Wed, 4 Jan 95 20:59:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20903;
	Wed, 4 Jan 95 20:59:58 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPk9g-00038LC; Wed, 4 Jan 95 20:50 PST
To: pine-info@cac.washington.edu
From: Jeff Morris <jbmorris@indiana.edu>
Subject: Re: View Message screen constantly redraws?
Date: Wed, 4 Jan 1995 23:30:56 -0500
Message-Id: <Pine.HPP.3.91.950104232623.11244F-100000@ezmail.ucs.indiana.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SOL.3.91.950103233548.1322D-100000@hobbes> 

> when pine 3.91 checks for new mail it will put an * in the upper
> left corner.  This is maybe what you are seeing.
Nope, I disabled that as soon as I got it.  A nice thing to be able to 
disable, because with 3.89 that was happening to me every 30 seconds no 
matter where I was, and it was driving me crazy because it kept telling 
me something had changed in pine, when really nothing had.

Someone else suggested maybe it was a bad modem connection - no, I am 
using ethernet, and it doesn't only do it on my computer, but any I've tried.

I don't know what it does, but it only happens if I'm in the view message 
screen, not the index.

- Jeff


From owner-pine-info@cac.washington.edu  Wed Jan  4 21:36:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24441;
	Wed, 4 Jan 95 21:36:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24446;
	Wed, 4 Jan 95 21:29:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24440;
	Wed, 4 Jan 95 21:29:35 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPkd5-00038LC; Wed, 4 Jan 95 21:20 PST
To: pine-info@cac.washington.edu
From: lyna@netcom.com (L. Faucett)
Subject: Re: Adding mail header lines
Message-Id: <lynaD1x28I.Mnv@netcom.com>
References: <19950104.113544.069884.NETNEWS@ESOC> <1995Jan4.165702.25666@math.utah.edu>
Date: Thu, 5 Jan 1995 05:07:29 GMT

Chris Alfeld (calfeld@ceslab01) wrote:
: Karl Keyte (kkeyte@esoc.bitnet) wrote:
: : I'm running pine 3.91 on a Linux system.  I want to be able to add mail header
: : lines as I compose a message. Typically I send mail from one system but want
: : replies to go elsewhere, so I want to insert a 'Reply-To:' entry in the header.

: : Does anyone know how I can do this? I must be just missing something.

: Go to Setup/Config from the menu menu.  Go down to custom-headers
: and add any headers you want.

	I'm using Pine 3.89 provided by my service -- When I select 
Option [uunder Setup] I get a message that says "no option screen."  How 
else can i compose a new header?  TIA
-- 
-- --lyna@netcom.com


From owner-pine-info@cac.washington.edu  Wed Jan  4 22:31:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25509;
	Wed, 4 Jan 95 22:31:05 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22142;
	Wed, 4 Jan 95 22:23:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22136;
	Wed, 4 Jan 95 22:23:57 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPlSk-00038CC; Wed, 4 Jan 95 22:14 PST
To: pine-info@cac.washington.edu
From: oconnort@acf2.nyu.edu (Tim O'Connor)
Subject: Re: Address book tools
Date: 5 Jan 1995 05:40:02 GMT
Message-Id: <3eg0ni$frq@cmcl2.NYU.EDU>
References: <Pine.BSI.3.91.950104113141.27761B-100000@recepsen.aa.msen.com>

Edward Vielmetti (emv@recepsen.aa.msen.com) wrote:

> - an interface to finger, whois, or some other directory service
>   so that you can look people up

Yes, today we were talking about the possibility of doing ph lookups 
from within Pine 3.91, since we're running a ph server in production 
now.  

I said I'd browse through the archives at the uwashington ftp site to 
see if the topic had been raised, but (as often happens) I didn't need 
to look any further than this newsgroup.

Many thanks for the timely discussion!

--tim o'connor

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Tim O'Connor                                        tim.oconnor@nyu.edu
NYU Academic Computing Facility                   Phone: (212) 998-3024
251 Mercer St., New York, NY 10012                  Fax: (212) 995-4120


From owner-pine-info@cac.washington.edu  Wed Jan  4 22:36:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25619;
	Wed, 4 Jan 95 22:36:31 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25266;
	Wed, 4 Jan 95 22:29:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25254;
	Wed, 4 Jan 95 22:29:00 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 5 Jan 95 14:27:31 -0800
Date: Thu, 5 Jan 1995 14:27:31 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: "L. Faucett" <lyna@netcom.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Adding mail header lines
In-Reply-To: <lynaD1x28I.Mnv@netcom.com>
Message-Id: <Pine.SOL.3.91.950105142622.9706D-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 5 Jan 1995, L. Faucett wrote:

> 	I'm using Pine 3.89 provided by my service -- When I select 
> Option [uunder Setup] I get a message that says "no option screen."  How 
> else can i compose a new header?  TIA

	Oooopsss...there is your problem...that feature is not available
in 3.89.  Request that your service upgrade to 3.91

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Thu Jan  5 01:19:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29054;
	Thu, 5 Jan 95 01:19:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27608;
	Thu, 5 Jan 95 01:12:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27602;
	Thu, 5 Jan 95 01:12:24 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPo2C-00038JC; Thu, 5 Jan 95 00:59 PST
To: pine-info@cac.washington.edu
From: nntp-server <s599@hamster.hrz.uni-giessen.de>
Subject: test
Message-Id: <Pine.A32.3.91.950105093453.21569A-100000@smail.hrz.uni-giessen.de>
In-Reply-To: <3dt0gr$8b2@cronkite.ocis.temple.edu> 
Date: Thu, 5 Jan 1995 08:36:32 GMT
Content-Type: TEXT/PLAIN; charset=US-ASCII
References: <3dt0gr$8b2@cronkite.ocis.temple.edu> 
Mime-Version: 1.0

This is just a test.


From owner-pine-info@cac.washington.edu  Thu Jan  5 04:44:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03976;
	Thu, 5 Jan 95 04:44:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26822;
	Thu, 5 Jan 95 04:36:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26816;
	Thu, 5 Jan 95 04:36:28 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPrFZ-00038JC; Thu, 5 Jan 95 04:25 PST
To: pine-info@cac.washington.edu
From: Henrik Rasmussen <her@garm.adm.ku.dk>
Subject: prYnt from pine
Date: Thu, 5 Jan 1995 13:11:22 +0100
Message-Id: <Pine.HPP.3.91.950105125012.25467I-100000@garm.adm.ku.dk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE

I normally use one printer from pine but for some mails I want to use=20
another printer. When I press "Y" for prYnt I am asked if I want to use the=
=20
command

Print message 1 using command "lp -dmuslas1"?=20

and have the opportunity to enter "Y" for "Yes", "N" for "No" or "^C" for=
=20
"Cancel". It is obvious that "Y" and "^C" means but answering "N" have=20
the same effect as "^C". Why can't i change printer by answering "N",=20
backspace or just enter another command as elsewhere in pine?

Venlig hilsen / Regards
Henrik Rasmussen

  University of Copenhagen   ADB-kontoret
-------------------------------------------------------------------------
  N=F8rregade 10            Tel:   +45 35 32 26 26   Direct: +45 35 32 27 0=
4
  P.O.B. 2177             Fax:   +45 35 32 27 80
  DK 1017 K=F8benhavn K     Email: Henrik.Rasmussen@adm.ku.dk
-------------------------------------------------------------------------





From owner-pine-info@cac.washington.edu  Thu Jan  5 05:59:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05571;
	Thu, 5 Jan 95 05:59:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01269;
	Thu, 5 Jan 95 05:49:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01263;
	Thu, 5 Jan 95 05:49:15 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPsN8-00038JC; Thu, 5 Jan 95 05:36 PST
To: pine-info@cac.washington.edu
From: lucio@ifctr.mi.cnr.it (Lucio Chiappetti)
Subject: Re: trouble with the return address
Date: 5 Jan 1995 07:36:09 -0600
Message-Id: <9601051344.AA26314@poseidon.ifctr.mi.cnr.it>
References: <3efflt$dl0@cronkite.ocis.temple.edu>

In article <3efflt$dl0@cronkite.ocis.temple.edu>, shrim@astro.ocis.temple.edu (Wet-Sprocket) write:
|> Comes here Mr. Lucio Chiappetti with this opinion in the "comp.mail.pine" group in this article on 4 Jan 1995 10:29:41 -0600:
|> 
|>  +      In fact pine is trying to enforce (but escapes are possible as shown
|>  +      above) a very reasonable thing, that is, mail is sent to somebody
|>  +      at some domain. Nobody cares about which machine is used for receiving
|>  +      the mail, and this information should not go out.
|> 
|>  +      The mail exchanger for the receiving domain should take care of
|>  +      forwarding the mail to the user machine in a way transparent and
|>  +      invisible to the sender of the mail.
|> 
|> Good point, but then you do require a robust mail-server which keeps routing
|> off all the incoming mail to respective sub-domain hosts.
|> 
|> Not all do have access to this yet, some notable univ. here who support this
|> idea are umich.edu, uiuc.edu. It would be nice if this gets standardized.
|> 

   It is not clear to me from the above if the "notable universities"
   (which are presumably very large organizations with several depart-
   ments possibly each one with its own subdomain) "support" means
   "implementation".
   I suppose somebody at washington.edu, the home of Pine, can comment
   MUCH better than I do.

   However I was NOT saying that *subdomains* shall not appear in the
   address, but that *machine names* shall not appear in the address.

   For instance I am lucio@ifctr.mi.cnr.it, and the address is
   a subdomain : 
     ifctr is the Istituto di Fisica Cosmica e Tecnologie Relative
     mi    in the Milan Area of
     cnr      the National Research Council of
     it       Italy

   I do not want to appear as "lucio@poseidon.ifctr.mi.cnr.it"
   (the machine where I receive mail), nor as "lucio@anything.ifctr.mi.cnr.it"
   (if I'm sending the mail from another machine).

   I do not either want to appear as "lucio@mi.cnr.it" or as
   "lucio@cnr.it" !!!  In this case the effort will be quite big,
   since CNR is a large AND uncoordinated organization.

   Having things dealt with at the lower level domain is instead
   very SIMPLE.
   One does not need any terribly robust mail server.

   Even we (a 30-people institute) can deal with that, just using
   Digital stock sendmail. All what we need is to enter in /etc/aliases
   on our NIS server an alias " user: user@machine" for each new
   user.
   This is a bearable load even for a surrogate volunteer part-time
   sysadm, and the turnaround to implement it is 2 minutes.



-- 
---------------------------------------------------------------------------- 
       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: LUCIO@IFCTR.MI.CNR.IT  |                                           
Decnet:   IFCTR::LUCIO           |             (Rabisch, II 46, 119-120)     
---------------------------------------------------------------------------- 


From owner-pine-info@cac.washington.edu  Thu Jan  5 06:27:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06070;
	Thu, 5 Jan 95 06:27:52 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28091;
	Thu, 5 Jan 95 06:19:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28085;
	Thu, 5 Jan 95 06:19:16 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPspN-00038KC; Thu, 5 Jan 95 06:06 PST
To: pine-info@cac.washington.edu
From: nntp-server <s599@hamster.hrz.uni-giessen.de>
Subject: Test 
Message-Id: <Pine.A32.3.91.950105143600.35431A-100000@smail.hrz.uni-giessen.de>
Date: Thu, 5 Jan 1995 13:36:33 GMT
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0

Test


From owner-pine-info@cac.washington.edu  Thu Jan  5 07:31:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07518;
	Thu, 5 Jan 95 07:31:43 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02504;
	Thu, 5 Jan 95 07:21:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02498;
	Thu, 5 Jan 95 07:21:42 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPtp2-00038JC; Thu, 5 Jan 95 07:09 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Unable to view attachment - HELP
Date: 5 Jan 95 15:10:01 GMT
Message-Id: <ellis.789318601@gmi.edu>

I have received a message on a list I subscribe to that allegedly has an
attachment.  When I view the attachment I get:

  PINE 3.90 ATTACHED TEXT Folder: INBOX Message 12 of 7,957 TOP   

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1982785689-789276093:#6308
Content-Type: TEXT/PLAIN; charset=US-ASCII

You are all in my address list thanks to the first CONCOM News release
which listed EVERYBODY.  As a result, I can share with you the search
[...]
qualify and be interested, share the job description with that person.

UNM is taking applications until January 20.  So, please, let us hear
from you.

--0-1982785689-789276093:#6308
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="plnrjobd.txt"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.3.89.9501042033.E6308@hydra.unm.edu>
Content-Description:

DQpUSEUgVU5JVkVSU0lUWSBPRiBORVcgTUVYSUNPDQpWQUNBTkNZIEFOTk9V
TkNFTUVOVA0KDQoNCg0KUE9TSVRJT046CU5FVFdPUksgU0VSVklDRVMgT0ZG
SUNFUg0KUkVRVUlTSVRJT04gTlVNQkVSOgk5NDI1OTcqQQ0KREVQQVJUTUVO
[...]



I know almost nothing about MIME, and I don't know of anyone else locally
who knows as much as I do.  What is wrong with the attachment that it is not
being decoded?


-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Thu Jan  5 09:18:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12298;
	Thu, 5 Jan 95 09:18:28 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01347;
	Thu, 5 Jan 95 09:06:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01341;
	Thu, 5 Jan 95 09:06:50 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPvWJ-00038CC; Thu, 5 Jan 95 08:58 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Pine Pipe to Zmodem
Date: 5 Jan 95 16:57:11 GMT
Message-Id: <ellis.789325031@gmi.edu>
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu> <3eeni5$t36@wabash.iac.net>

cjolley@iac.net (Carl Jolley) writes:

 >Chris Alfeld (calfeld@ceslab03) wrote:
 >: Carl Jolley (cjolley@iac.net) wrote:
 >: : I'm doing terminal emulation to my ISP. The default mailer is Pine. The
 >: : pipe command IS configured but I can't get piping to: sz - to work. When
 >: : I try it, the screen does display the zmodem init string, i.e *B00000....
 >: : But I can't get it to connect up to my terminal emulation program's
 >: : zmodem requestor. Piping from Elm and from Tin work just fine. The sysadmin
 >: : gave me some non-understanable explaination about why the Pine pipe command
 >: : doesn't work with 'sz'. Is the pipe command in Pine _that_ different from
 >: : that of Elm (and Tin)?

 >: I've never tried piping into sz but you might try this:

 >: 	| (cat > tmpfile;sz tmpfile;rm -f tmpfile)

 >I tried this and it works identically to just doing : sz -
 >i.e. it doesn't work. In both cases it does fire up the host system zmodem
 >and it displays the init string , i.e. **B0000000000000 but then on the
 >next line it displays ten or so question marks. Oh, also when I do get
 >back to Pine it it presents me with a screen as though I had Replied to
 >the message and then entered ^X, i.e. the screen has quoted the message I
 >was trying to d/l, and at the top there is a skeleton reply message, complete
 >with my signature and Pine is asking if I want to send the reply. Oh, one
 >small detail I forgot, when the host system's zmodem fires up, prior to
 >display of the init sting it sends a response that the zmodem has been
 >initiated in batch mode. No big deal but it does appear that everything up
 >until that point and enen through the sending of the init string is exactly
 >what one would expect. Invariably if I then manually initiate the zmodem
 >recieve from my end, it times out. The host system's zmodem is not talking
 >to my end. It appears possibly that the stuff that zmodem would normally
 >be sending to me is somehow being sent back to Pine.

Just a thought:  about 1988-89 Chuck Forsberg (the developer of zmodem)
changed the licensing of the UNIX versions of sz/rz, etc., to say they could
only be used with licensed versions of the zmodem protocol.  Sometime after
that he recoded rz/sz to explicitly open /dev/tty rather than using stdin
and stdout the way it had in the past.  This could interfere with attempts
to pipe rz/sz.

It is better to have the older free versions that use stdio.

 >-- 
 >**** cjolley@iac.net <Carl Jolley>
 >**** All opinions are my own and not necessarily those of my employer ****

-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Thu Jan  5 09:42:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13274;
	Thu, 5 Jan 95 09:42:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05430;
	Thu, 5 Jan 95 09:31:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05424;
	Thu, 5 Jan 95 09:31:53 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rPvr8-00038JC; Thu, 5 Jan 95 09:20 PST
To: pine-info@cac.washington.edu
From: tim@pooh (Tim Bloomfield)
Subject: Re: trouble with the return address
Message-Id: <D1xzAx.Gpy@oci.utoronto.ca>
References: <3ecrs4$2v2@cronkite.ocis.temple.edu>
Date: Thu, 5 Jan 1995 17:01:45 GMT

Wet-Sprocket (shrim@astro.ocis.temple.edu) wrote:
: Comes here Mz. Patti Johnson with this opinion in the "comp.mail.pine" group in this article on Tue, 3 Jan 1995 19:12:14 GMT:

:  +   While mailx correctly addresses the "From" field, pine omits the machine 
:  +   name.  That is, here's the From from the two mailers:

:  +   mailx:	johnson@micronet.wcu.edu
:  +   pine:	johnson@wcu.edu

: We had the same problem, which got fixed by setting this option in Setup/Config:

: user-domain = <No Value Set>

This fix does not work for me. When I leave the user domain unset my 
email to outside sites does not include a domain name which is not very 
useful. I am using Solaris 2.3 and Pine 3.91.

The sendmail.cf is the standard one with the bug fix to stop it truncating
domain names in the From field. This works well with elm.

-Tim 



From owner-pine-info@cac.washington.edu  Thu Jan  5 10:17:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14721;
	Thu, 5 Jan 95 10:17:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02499;
	Thu, 5 Jan 95 09:58:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from micronet.wcu.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02493;
	Thu, 5 Jan 95 09:58:57 -0800
Received: by micronet (5.0/SMI-SVR4)
	id AA07791; Thu, 5 Jan 1995 12:58:30 +0500
Date: Thu, 5 Jan 1995 12:58:29 -0500 (EST)
From: Patti Johnson <johnson@micronet.wcu.edu>
To: pine-info@cac.washington.edu
Subject: (To: Tim) Re: trouble with the return address
Message-Id: <Pine.SOL.3.91.950105125712.7715B-100000@micronet>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 874

(sorry folks - I couldn't reply to Tim, due to his return address - so 
I'm posting to the group)

Tim, from your message below - I'm not sure if you were asking further 
how to fix the problem or stating how you fixed it.  I'm sorry.  At any 
rate, I did find a fix - very like what "wet sprocket" wrote - but not 
exactly.  If you'd like it, let me know.  If you've got a fix, I'd like 
to compare notes.  BTW - I'm using Solaris 2.3 + Pine 3.91 too - so our 
fixes should be the same???
pj

On Thu, 5 Jan 1995, Tim Bloomfield wrote:

> This fix does not work for me. When I leave the user domain unset my 
> email to outside sites does not include a domain name which is not very 
> useful. I am using Solaris 2.3 and Pine 3.91.
> 
> The sendmail.cf is the standard one with the bug fix to stop it truncating
> domain names in the From field. This works well with elm.




From owner-pine-info@cac.washington.edu  Thu Jan  5 12:19:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20577;
	Thu, 5 Jan 95 12:19:58 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09260;
	Thu, 5 Jan 95 12:01:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09254;
	Thu, 5 Jan 95 12:01:45 -0800
Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24414;
	Thu, 5 Jan 95 12:01:33 -0800
Date: Thu, 5 Jan 1995 12:01:31 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Lucio Chiappetti <lucio@ifctr.mi.cnr.it>
Cc: pine-info@cac.washington.edu
Subject: Re: trouble with the return address
In-Reply-To: <9601051344.AA26314@poseidon.ifctr.mi.cnr.it>
Message-Id: <Pine.ULT.3.92.950105113332.5215J-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

FYI, Pine does not try to enforce anything in this area; rather it provides
config options to accommodate whatever model is supported at your site.

There have been some subtle bugs/changes in this part of Pine's logic over
the past year or two, but the intent hasn't changed.  In current code
here's what I understand should be happening: 

If user-domain is set, then outgoing addresses will have that value on 
the right side of the @ sign in From: addresses (and when Pine completes 
a To: or Cc: address for you.)  Pine doesn't care whether the user-domain
value includes a machine name or not.  Your choice, but it must match
whatever your local MTAs will accept.

If user-domain is *not* set (in either the personal or global pine config
file), Pine uses a system call to get the host name, and will use whatever
it gets as the right-hand-side unless "use-only-domain-name" is set, in
which case it attempts to strip off the machine name. 

By the way, a common source of address config problems occurs when people
have entries in their /etc/hosts file backwards: the fully qualified name
should be first, and the short hostname second.  If these are reversed
(and user-domain is not set) then people will end up with return addresses
of the form "joe@frodo" which will cause no end of grief. 

-teg

On 5 Jan 1995, Lucio Chiappetti wrote:

> In article <3efflt$dl0@cronkite.ocis.temple.edu>, (Wet-Sprocket) writes:
> |> Comes here Mr. Lucio Chiappetti with this opinion in "comp.mail.pine":
> |> 
> |>  +  In fact pine is trying to enforce (but escapes are possible as shown
> |>  +  above) a very reasonable thing, that is, mail is sent to somebody
> |>  +  at some domain. Nobody cares about which machine is used for receiving
> |>  +  the mail, and this information should not go out.
> |> 
> |>  +  The mail exchanger for the receiving domain should take care of
> |>  +  forwarding the mail to the user machine in a way transparent and
> |>  +  invisible to the sender of the mail.
> |> 
> |> Good point, but then you do require a robust mail-server which keeps 
> |> routing off all the incoming mail to respective sub-domain hosts.
> |> 
> |> Not all do have access to this yet, some notable univ. here who support
> |> this idea are umich.edu, uiuc.edu. It would be nice if this gets 
> |> standardized. 
> 
>    It is not clear to me from the above if the "notable universities"
>    (which are presumably very large organizations with several depart-
>    ments possibly each one with its own subdomain) "support" means
>    "implementation".
>    I suppose somebody at washington.edu, the home of Pine, can comment
>    MUCH better than I do.
> 
>    However I was NOT saying that *subdomains* shall not appear in the
>    address, but that *machine names* shall not appear in the address.
> 
>    For instance I am lucio@ifctr.mi.cnr.it, and the address is
>    a subdomain : 
>      ifctr is the Istituto di Fisica Cosmica e Tecnologie Relative
>      mi    in the Milan Area of
>      cnr      the National Research Council of
>      it       Italy
> 
>    I do not want to appear as "lucio@poseidon.ifctr.mi.cnr.it"
>    (the machine where I receive mail), nor as "lucio@anything.ifctr.mi.cnr.it"
>    (if I'm sending the mail from another machine).
> 
>    I do not either want to appear as "lucio@mi.cnr.it" or as
>    "lucio@cnr.it" !!!  In this case the effort will be quite big,
>    since CNR is a large AND uncoordinated organization.
> 
>    Having things dealt with at the lower level domain is instead
>    very SIMPLE.
>    One does not need any terribly robust mail server.
> 
>    Even we (a 30-people institute) can deal with that, just using
>    Digital stock sendmail. All what we need is to enter in /etc/aliases
>    on our NIS server an alias " user: user@machine" for each new
>    user.
>    This is a bearable load even for a surrogate volunteer part-time
>    sysadm, and the turnaround to implement it is 2 minutes.
>
> -- 
> ---------------------------------------------------------------------------- 
>        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: LUCIO@IFCTR.MI.CNR.IT  |                                           
> Decnet:   IFCTR::LUCIO           |             (Rabisch, II 46, 119-120)     
> ---------------------------------------------------------------------------- 


From owner-pine-info@cac.washington.edu  Thu Jan  5 15:45:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29168;
	Thu, 5 Jan 95 15:45:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10671;
	Thu, 5 Jan 95 15:33:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from egate.citicorp.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10665;
	Thu, 5 Jan 95 15:33:33 -0800
Received: by egate.citicorp.com id AA11933
  (InterLock SMTP Gateway 1.1 for pine-info@cac.washington.edu);
  Thu, 5 Jan 1995 23:33:31 GMT
Received: by egate.citicorp.com (Internal Mail Agent-1);
  Thu, 5 Jan 1995 23:33:31 GMT
Date: Thu, 5 Jan 1995 18:33:30 -0500
Message-Id: <199501052333.SAA22988@maple.cgin.us-md.citicorp.com>
X-Sender: vgupta@cginnet
X-Mailer: Windows Eudora Version 1.4.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: pine-info@cac.washington.edu
From: Vic.Gupta@citicorp.com (Global LAN Design, CGIN, (703) 708-1256)
Subject: Does PINE supports Internet firewalls.

Hi:

I wanted to know if PINE supports Internet Firewalls.

Thanks.




From owner-pine-info@cac.washington.edu  Thu Jan  5 17:26:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03773;
	Thu, 5 Jan 95 17:26:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13092;
	Thu, 5 Jan 95 17:15:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13086;
	Thu, 5 Jan 95 17:15:31 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQ367-00038TC; Thu, 5 Jan 95 17:04 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: trouble with the return address
Date: 5 Jan 1995 23:51:31 GMT
Message-Id: <3ei0m3$h98@cronkite.ocis.temple.edu>

Comes here Mr. Lucio Chiappetti with this opinion in the "comp.mail.pine" group in this article on 5 Jan 1995 07:36:09 -0600:

 +      I do not either want to appear as "lucio@mi.cnr.it" or as
 +      "lucio@cnr.it" !!!  In this case the effort will be quite big,
 +      since CNR is a large AND uncoordinated organization.

 +      Even we (a 30-people institute) can deal with that, just using
 +      Digital stock sendmail. All what we need is to enter in /etc/aliases
 +      on our NIS server an alias " user: user@machine" for each new
 +      user.


Entries in /etc/aliases ???? You gotta be kidding....
6000+ entries on the system only for this???? and I'am not even talking
about the mainframe systems yet....

Nah! that would be a primitive approach....i would prefer shrim@temple.edu
anyday!

Just set up a mail-server, and then each user send an e-mail to this server
telling to which address mail sent to user@temple.edu should be redirected to.

Suppose the user wants to switch to another host to send/recieve mail then he
should be able to change it *himself* by sending another e-mail to the server
with the new address (a la Listserv) without requiring the intervention of a
full-time Mail-Admin to make the necessary changes manually, in matter of secs.

The keyword here is flexibility.

You would hate to be pulled over for speeding on the Information SuperHighway,
wouldn't you ? :) comments ?

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Thu Jan  5 17:53:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04851;
	Thu, 5 Jan 95 17:53:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17685;
	Thu, 5 Jan 95 17:48:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17679;
	Thu, 5 Jan 95 17:48:02 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQ3dg-00038CC; Thu, 5 Jan 95 17:38 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: trouble with the return address
Date: 6 Jan 1995 00:31:52 GMT
Message-Id: <3ei31o$h98@cronkite.ocis.temple.edu>

Comes here Mr. Tim Bloomfield with this opinion in the "comp.mail.pine" group in this article on Thu, 5 Jan 1995 17:01:45 GMT:

 +   This fix does not work for me. When I leave the user domain unset my 
 +   email to outside sites does not include a domain name which is not very 
 +   useful. I am using Solaris 2.3 and Pine 3.91.

Hmmm...your case seems to be inverted....how about this...

user-domain = your.hosts.complete.address (for ex: foo.bar.com)

and checking this option...

use-only-domain-name = Yes

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Thu Jan  5 18:38:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05965;
	Thu, 5 Jan 95 18:38:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14511;
	Thu, 5 Jan 95 18:33:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14505;
	Thu, 5 Jan 95 18:33:07 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQ4MZ-00038UC; Thu, 5 Jan 95 18:25 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: prYnt from pine
Date: 6 Jan 1995 01:16:44 GMT
Message-Id: <3ei5ls$h98@cronkite.ocis.temple.edu>

Comes here Mr. Henrik Rasmussen with this opinion in the "comp.mail.pine" group in this article on Thu, 5 Jan 1995 13:11:22 +0100:

 +   I normally use one printer from pine but for some mails I want to use
 +   another printer. When I press "Y" for prYnt I am asked if I want to

 +   Print message 1 using command "lp -dmuslas1"?=20

 +   and have the opportunity to enter "Y" for "Yes", "N" for "No" or "^C" for
 +   "Cancel". It is obvious that "Y" and "^C" means but answering "N" have
 +   the same effect as "^C". Why can't i change printer by answering "N",
 +   backspace or just enter another command as elsewhere in pine?

Good point!!
I use the Network LaserPrinter while at work, and the StyleWriter at home to
print and would love an option C instead of ^C to switch printers without
having to go and change the printers in the Setup.

Right now what I do is take advantage of the -p config-file flag of Pine.

pine -f .workpinerc   - while at work

pine -f .homepinerc   - while at home  

In ".workpinerc" I have printer setup to print to 'lpr -P printername'
and in ".homepinerc" I have set it to 'attached-to-ansi' printer setup.

Also in my .tcshrc I have setup aliases like
alias wp 'pine -f .workpinerc'
alias hp 'pine -f .homepinerc'

Hope this helps.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Thu Jan  5 19:07:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06524;
	Thu, 5 Jan 95 19:07:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18718;
	Thu, 5 Jan 95 19:00:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18712;
	Thu, 5 Jan 95 19:00:42 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQ4hB-00038UC; Thu, 5 Jan 95 18:46 PST
To: pine-info@cac.washington.edu
From: Phil Safier <psafier@rt66.com>
Subject: Need help in creating mailing list
Date: Thu, 5 Jan 1995 18:35:02 -0700
Message-Id: <Pine.SUN.3.91.950105183230.29807B-100000@mack>
References: <3e414i$o00@cronkite.ocis.temple.edu> <Pine.ULT.3.92.950103122043.27331d-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.92.950103122043.27331d-100000@shiva1.cac.washington.edu> 

Can someone point me to help files on working with mailing lists in the 
addressbook. I have about 19K worth of names and addresses but can't 
figure out how to put them into my addressbook at one shot.


From owner-pine-info@cac.washington.edu  Thu Jan  5 20:34:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08444;
	Thu, 5 Jan 95 20:34:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16136;
	Thu, 5 Jan 95 20:28:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16130;
	Thu, 5 Jan 95 20:28:17 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQ64d-00038OC; Thu, 5 Jan 95 20:14 PST
To: pine-info@cac.washington.edu
From: idjfc@imap1.asu.edu
Subject: printing problems
Date: 6 Jan 1995 02:48:17 GMT
Message-Id: <3eib1h$cd3@news.asu.edu>

I am using Pine 3.91 (a newby to the net) and am having problems getting 
my printer to work with it. The printer worked fine with the previous 
version of Pine.  I am using an IBM Compatable, 486DX, 8 meg of ram, 
TCP/IP, trumpet telnet.  The modem is a Practical Peripheral 28.8.  I use 
a PPP connection to a SPARCSERVER 1000 running Solaris 2.3.  While in 
Pine, when I type "y" for print, a message "Caption Onsing" appears in the 
lower right hand corner of the screen, and everything is dumped to my 
hard disk.  I have read through all the Pine FAQs and can't come up with 
anything that closely matches my problem.  The printer is a Panasonic 
KX-P2123 which emulates an IBM Proprinter X24E.  It is a 24-pin.  Of 
course after things are dumped into the hard disk, I can then print it 
out fine, but it is an inconvenience, and I'm not too pleased about 
something just dumping to the hard disk without my control.  Under the 
Pine printer options, I have selected the "ansi" selection.  Requesting 
help within the Pine program doesn't give me mush, just tells me to make 
a selection.  I work within both MS-DOS 6.22 and Windows 3.1 and the 
problem is the same under both platforms.  The printer works fine on-line 
with everything else; i.e., netscape, HGopher, etc.
     I would greatly appreciate any information.  Thank you. - JB    


From owner-pine-info@cac.washington.edu  Thu Jan  5 21:04:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09110;
	Thu, 5 Jan 95 21:04:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20298;
	Thu, 5 Jan 95 20:58:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20292;
	Thu, 5 Jan 95 20:58:20 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQ6Xu-00038OC; Thu, 5 Jan 95 20:45 PST
To: pine-info@cac.washington.edu
From: mcphail@garnet.msen.com (Michael McPhail)
Subject: Re: Where are my TIN saved files?
Date: 6 Jan 1995 02:47:36 GMT
Message-Id: <3eib08$qdm$2@heifetz.msen.com>
References: <3edgn0$f42@news.asu.edu>

mlk68@imap1.asu.edu wrote:
: 	I am working with a TIN newsreader and can not locate my saved 
: article files. I go through the process of saving files that I find in 
: the Internet newsgroups and giving them a name. When I go to the FTP 
: saved files directory, they aren't there. Please, please help.

: --
: Michael Leshowitz
: mlk68@imap1.asu.edu

You should have a directory in your home directory called Mail (or mail). 
Try that location.

 =======================================================================
[                                    |                                  ]
[       Mike McPhail                 |     My other computer            ]
[    mcphail@mail.msen.com           |     is a Cray.                   ]
[  aa351@detroit.freenet.org         |                                  ]
[                                    |                                  ]
 =======================================================================


From owner-pine-info@cac.washington.edu  Fri Jan  6 03:47:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17292;
	Fri, 6 Jan 95 03:47:12 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21683;
	Fri, 6 Jan 95 03:39:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21677;
	Fri, 6 Jan 95 03:39:29 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQCpm-00038PC; Fri, 6 Jan 95 03:27 PST
To: pine-info@cac.washington.edu
From: Nancy McGough <nancym@ii.com>
Subject: Using formail to solve private mail w/ Newsgroups header problem
Date: Thu, 5 Jan 1995 21:38:25 -0800
Message-Id: <Pine.ULT.3.91.950105211047.7915A-100000@halcyon.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Pine is both a newsreader and a mailer and whenever a message
sent by Pine contains a Newsgroups header, it means that the
message was posted to a newsgroup.  If a message is only
mailed it will not contain a Newsgroups header.  If you use
Pine as your mailer and you receive a message that has a
Newsgroups header, Pine will ask you if you want to reply
by posting.  Now, if everyone used Pine this would be fine.
But, since many people use NN, Tin, and TRN, which all include
a Newsgroups header in privately mailed messages, this is a
problem.  Often people answer yes to this question because
they think that they are responding to a message that was
posted, rather than just mailed.  And then someone's private
message gets posted to the world, causing all kinds of turmoil.
A future release of Pine will make it more clear to the user
about this danger, but until that happens you may want to
put something like this into your .procmailrc file:

# Useful if you use Pine as your mailer
:0 fhw
* ^Newsgroups:
* !^Message-Id:.*Pine
| formail -R Newsgroups: Originated-In-Newsgroups:


What this does is if an incoming mail message contains a
Newsgroups header and the Message-Id does not contain "Pine"
(i.e., it did get mailed by Pine) then it replaces (R) the
Newsgroups header with Originated-In-Newsgroups, followed by
the newsgroups.  Some questions:

* Any suggestion for a better header than Originated-In-Newsgroups?
* Any suggestions for improving this?
* What other newsreaders (other than nn, tin, and trn) include a
  Newsgroups header in privately mailed messages?
* Do you think this is a good example to put in the Procmail FAQ?
  If not, what's a better header munging example?

Thanks much,
Nancy

-- 
 /\_/\    Nancy McGough
( o.o )   Infinite Ink
 > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/


From owner-pine-info@cac.washington.edu  Fri Jan  6 03:54:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17500;
	Fri, 6 Jan 95 03:54:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25299;
	Fri, 6 Jan 95 03:48:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25293;
	Fri, 6 Jan 95 03:48:51 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQD1i-00038JC; Fri, 6 Jan 95 03:40 PST
To: pine-info@cac.washington.edu
From: hubbell@well.sf.ca.us (Charles H. Hubbell)
Subject: Using Pine to post to newsgroups
Date: 6 Jan 1995 05:36:28 GMT
Message-Id: <3eikss$73k@nkosi.well.com>

How does one perform that operation?

                          Chuck Hubbell





From owner-pine-info@cac.washington.edu  Fri Jan  6 04:25:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18551;
	Fri, 6 Jan 95 04:25:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22349;
	Fri, 6 Jan 95 04:18:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22343;
	Fri, 6 Jan 95 04:18:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQDTa-00038JC; Fri, 6 Jan 95 04:09 PST
To: pine-info@cac.washington.edu
From: pucho@netcom.com (Marcos Rubinstein)
Subject: Re: Anyway to tell the date/time mail came in????
Message-Id: <puchoD1zFFL.DL2@netcom.com>
References: <3dpvkm$n8a@news.cais.com>
Date: Fri, 6 Jan 1995 11:47:44 GMT

Jeffrey Fitzgerald (jlfitz@cais2.cais.com) decia:
: 	In Pine (or even TIN) is it possible to see when the message was 
: posted? I can't find anyway to see it...

in pine: while reading your mail hit the "h" key... that will put you in 
full headers... read them... you'll see when it was received by your 
sistem....

in pine... well... there is really no way... as much as you didn't 
receive the message... it was received by the news-server your host is 
using...
Pucho


From owner-pine-info@cac.washington.edu  Fri Jan  6 06:07:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20885;
	Fri, 6 Jan 95 06:07:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23661;
	Fri, 6 Jan 95 05:58:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from hopper.acs.ryerson.ca by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23655;
	Fri, 6 Jan 95 05:58:44 -0800
Received: by acs.ryerson.ca (5.0/SMI-SVR4)
	id AA02072; Fri, 6 Jan 1995 08:55:56 -0500
Date: Fri, 6 Jan 1995 08:55:55 -0500 (EST)
From: Paul Ribeiro <pribeiro@acs.ryerson.ca>
X-Sender: pribeiro@hopper
To: pine-info@cac.washington.edu
Subject: Headers under Solaris
In-Reply-To: <3ei5ls$h98@cronkite.ocis.temple.edu>
Message-Id: <Pine.SOL.3.91.950106085033.1992E-100000@hopper>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 599

Hi,
I'm having a strange problem, with
user-domain=acs.ryerson.ca
use-only-domain-name=yes

under AIX I get:

Date: Fri, 6 Jan 1995 00:19:59 -0500 (EST)
From: Paul Ribeiro <pribeiro@acs.ryerson.ca>
To: Paul Ribeiro <pribeiro@acs.ryerson.ca>
Subject: test
Message-ID: <Pine.A32.3.91.950106001954.41578A@hermes.acs.ryerson.ca>

under Solaris I get:

Date: Fri, 6 Jan 1995 00:14:35 -0500 (EST)
From: Paul Ribeiro <pribeiro@acs.ryerson.ca>
X-Sender: pribeiro@hopper  <---- why "hopper"?
To: Paul Ribeiro <pribeiro@acs.ryerson.ca>
Subject: test
Message-ID: <Pine.SOL.3.91.950106001423.721B@hopper>








From owner-pine-info@cac.washington.edu  Fri Jan  6 08:02:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23324;
	Fri, 6 Jan 95 08:02:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28691;
	Fri, 6 Jan 95 07:54:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28685;
	Fri, 6 Jan 95 07:54:09 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQGpE-00038KC; Fri, 6 Jan 95 07:43 PST
To: pine-info@cac.washington.edu
From: "J. Kelly Cunningham" <deviate@lipschitz>
Subject: Re: Pine Pipe to Zmodem 
Message-Id: <Pine.NXT.3.91.950106012216.22917A-100000@lipschitz>
Date: Fri, 6 Jan 1995 01:55:21 -0600
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu> <3eeni5$t36@wabash.iac.net> <ellis.789325031@gmi.edu> 
In-Reply-To: <ellis.789325031@gmi.edu> 
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

-----BEGIN PGP SIGNED MESSAGE-----

On 5 Jan 1995, R. Stewart Ellis wrote:

   cjolley@iac.net (Carl Jolley) writes:
   
    >Chris Alfeld (calfeld@ceslab03) wrote:
    >: Carl Jolley (cjolley@iac.net) wrote:
    >: : I'm doing terminal emulation to my ISP. The default mailer is Pine. The
    >: : pipe command IS configured but I can't get piping to: sz - to work. When
    >: : I try it, the screen does display the zmodem init string, i.e *B00000....
[...]   
    >: 	| (cat > tmpfile;sz tmpfile;rm -f tmpfile)
   
This isn't really what you want, but how 'bout this?

Run Pine from this:
#!/bin/csh -f
/path/to/pine3.91 -z -id0
if ( -e ~/articles.to.download ) then
	cd ~/articles.to.download
	if ( `ls | wc -l` ) d *  # d is sz, kermit, whatever...
endif
cd ~ ; rm -r ~/articles.to.download
#

h:
#! /bin/csh -f
# 
# Save articles for download.
# 
cat > ~/download.article.tmp
if ( -e ~/articles.to.download == 0 ) then
	cd ~ ; mkdir articles.to.download
endif
set i = 1
while ( -e articles.to.download/download.article.$i )
@ i++
end
mv ~/download.article.tmp ~/articles.to.download/download.article.$i
echo Article stored for later download...
#

Pipe each article you want to download to h.  When you quit Pine, the wrapper
starts sending the articles.




-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBLwyi8eBu0383Om6dAQEEDgQApRZOtRrhZyG1sfjiLPh+Vm6UGibspqBt
ZEappxIbBuq7qcxOoNSNt8Rf/keIO7aINoDA5MkeEfGqv9aI43LKbuKi3X/ao/YL
8yixChV3jGq374eUa0YWLWuyiYzTgTBPr9riyz0DJggpBYXiLDzd06YIw6AkZ+sR
WklPjIj7fgY=
=sDj1
-----END PGP SIGNATURE-----


-- kc       prudence dictates a low profile -- Sandy Sandfort
          finger deviate@lipschitz.sfasu.edu | pgp -fka +force
    finger slutsky@lipschitz.sfasu.edu | pgp -f | tee mkpgp.txt.uu | more


From owner-pine-info@cac.washington.edu  Fri Jan  6 10:28:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29946;
	Fri, 6 Jan 95 10:28:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29005;
	Fri, 6 Jan 95 10:20:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28999;
	Fri, 6 Jan 95 10:20:45 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQJ6T-00038JC; Fri, 6 Jan 95 10:09 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Setting up for news, upgrading pine systemwide.
Date: 6 Jan 95 17:32:37 GMT
Message-Id: <ellis.789413557@gmi.edu>

First of all, although I generally think pine is a great MUA, I am
distinctly uncomfortable with it as a newsreader, preferring nn.  However I
am the one who originally installed elm and nn on our site several years
ago, followed shortly by tin, and about a year ago, pine.  Currently the
systemwide pine is 3.89, but I want to upgrade to 3.91.  

Part of what prevented me was an error message I keep getting when running
3.91 about unbalanced {.  I posted on it in the past but got no real help.
Today I finally figured it out.  It had to do with the value of
news-collections in the systemwide pine.conf file.  It was set to:

news-collections=News/[] *{$NNTPSERVER/nntp}[]

which correctly pointed 3.89 at our nntpserver, set in a global cshrc file.
However this was not being instantiated properly by 3.9{0|1}.  I had to
experiment with brackets and parens until I finally got a version that would
work correctly with both 3.89 and 3.91:

news-collections=News/[] *{${NNTPSERVER}/nntp}[]


Now I am trying to make sense of the folders issue.  Although I would expect
the immediately preceding news-collection setting to look in ~/News then at
the nntpserver, I do not seem to see any folders from my ~/News directory.
I also experimented with setting the folder-collection to:

folder-collections=Mail/[] News/[]

This latter gave me a merged list of folders from ~/Mail and ~/News, but I
could not append to the folders that I knew were in News.  Part of this may
have been because they were saved by nn, which does not by default setup a
folder in completely proper UNIX mail format.  I also could not just save to
the folders by name, so I am quite confused about the relationship between
news and folders.

The model I want, because it is most compatible with our other newsreaders
and MUAs, is to have news saved in folders in ~/News, mail saved in ~/Mail.
Then I want users to be able to open the folders of saved news in a way
distinct from their mail folders.  I know this runs against the cognitive
model that the pine team seem to be pushing, but it is the one I am most
comfortable trying to support, as an unpaid volunteer, in addition to my 12
hrs/qtr teaching load, maintaining gopher and www, and serving on about a
dozen committees.

Does anyone have any advice?

In addition to the news issues, which are what make me the most
uncomfortable, should I anticipate any other major sources of confusion from
my users if I just upgrade them from 3.89 to 3.91 without warning?



-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Fri Jan  6 10:59:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01180;
	Fri, 6 Jan 95 10:59:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03128;
	Fri, 6 Jan 95 10:50:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03122;
	Fri, 6 Jan 95 10:50:47 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQJbV-00038CC; Fri, 6 Jan 95 10:41 PST
To: pine-info@cac.washington.edu
From: bsachett@alert.com (Bruce Sachetti)
Subject: Using Wyse50 (or any non-VTxxx) terminals w/Pine
Message-Id: <bsachett.3.0443F9EF@alert.com>
Date: Fri, 6 Jan 1995 11:01:21 GMT

If anyone has had any success making a Wyse 50 terminal work with Pine 
(especially arrow keys), please let me know.  I originally thought this was a 
termcap vs. terminfo issue.  

I am using Pine on an RS/6000 (3.2.3 and 3.2.5) and have tried Pine 3.89 and 
Pine 3.91.  Per David Miller's previous response, I did make sure that the 
pico and pine makefile.a32 had "-l curses" instead of "-l termcap".  

It seems that Pine isn't using terminfo.  

Any help would be appreciated...


Bruce G. Sachetti                    
Systems Administrator II         
Alert Centre Inc. Englewood, CO   
bsachett@alert.com (303)488-7719     



From owner-pine-info@cac.washington.edu  Fri Jan  6 11:03:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01375;
	Fri, 6 Jan 95 11:03:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29892;
	Fri, 6 Jan 95 10:54:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29886;
	Fri, 6 Jan 95 10:54:32 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQJeZ-00038JC; Fri, 6 Jan 95 10:44 PST
To: pine-info@cac.washington.edu
From: Garbi Schmidt <garbi@coco.ihi.ku.dk>
Subject: WANTED DESPERATELY: books on pine
Date: Fri, 6 Jan 1995 18:33:04 +0100 (MET)
Message-Id: <Pine.ULT.3.90.950106183019.27529A-100000@coco.ihi.ku.dk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hi there!

Does anybody out there have the ultimate solution to my quest for a good 
book on pine, or perhaps som FAQ or HELPsite for pine - especially setup 
and configuration questions??

Thanks a lot!
			Garbi
--------------------------------------------------------------------------
Garbi Schmidt | 'Tomorrow is the most important thing in life.' (John Wayne)
Copenhagen,DK | 'HALLELUJA -- there is still hope!' (G. Schmidt)
---------------------------------------------------------------------------

 


From owner-pine-info@cac.washington.edu  Fri Jan  6 11:05:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01469;
	Fri, 6 Jan 95 11:05:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03369;
	Fri, 6 Jan 95 10:59:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03363;
	Fri, 6 Jan 95 10:59:31 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQJlY-00038CC; Fri, 6 Jan 95 10:52 PST
To: pine-info@cac.washington.edu
From: rrogers@minnie.imd.nrc.ca (Rick Rogers)
Subject: FAQ?? or VMS PINE??
Date: 6 Jan 95 09:35:30 NDT
Message-Id: <1995Jan6.093530.1@minnie.imd.nrc.ca>

Hi all,

   Where is the FAQ for this group (assuming there is one), I can't
find it as far back as my feed has.

   If there isn't a FAQ I'm specifically looking for info on PINE
for VMS to work with SMTP.

Thanks,

Rick


From owner-pine-info@cac.washington.edu  Fri Jan  6 11:27:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02303;
	Fri, 6 Jan 95 11:27:54 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03966;
	Fri, 6 Jan 95 11:20:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03960;
	Fri, 6 Jan 95 11:20:53 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQK44-00038JC; Fri, 6 Jan 95 11:11 PST
To: pine-info@cac.washington.edu
From: peter-wa@dsv.su.se (Peter Wastholm)
Subject: Re-sort a folder *permanently*?
Date: 6 Jan 1995 13:31:49 GMT
Message-Id: <3ejgo5$jc9@erinews.ericsson.se>
Mime-Version: 1.0

I recently restructured my folder-collection. When moving letters to their 
appropriate folders, the order got messed up, so now most of my folders are 
sorted pretty randomly. Therefore, every time I enter a folder, I have to 
press $ d to sort the letters by date the way I want them. Isn't there a way 
to make that order permanent?

/Peter Wastholm



From owner-pine-info@cac.washington.edu  Fri Jan  6 11:29:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02342;
	Fri, 6 Jan 95 11:29:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00781;
	Fri, 6 Jan 95 11:20:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00775;
	Fri, 6 Jan 95 11:20:51 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQK0z-00038CC; Fri, 6 Jan 95 11:07 PST
To: pine-info@cac.washington.edu
From: Rahul Dhesi <dhesi@rahul.net>
Subject: Re: Using formail to solve private mail w/ Newsgroups header problem
Date: 6 Jan 1995 13:29:11 GMT
Message-Id: <3ejgj7$ahe@hustle.rahul.net>
References: <Pine.ULT.3.91.950105211047.7915A-100000@halcyon.com>

In <Pine.ULT.3.91.950105211047.7915A-100000@halcyon.com> Nancy McGough
<nancym@ii.com> writes:

>* ^Newsgroups:
>* !^Message-Id:.*Pine
>| formail -R Newsgroups: Originated-In-Newsgroups:

>What this does is if an incoming mail message contains a
>Newsgroups header and the Message-Id does not contain "Pine"
>(i.e., it did get mailed by Pine) then it replaces (R) the
>Newsgroups header with Originated-In-Newsgroups, followed by
>the newsgroups.

My first reaction was that this is an excellent idea.

However, in the long run, treating messages differently based on the
originating mail software will cause a lot of confusion.  I think it would be
better if pine users would unconditionally have procmail convert the
Newsgroups header.  I suggest that they transform it to X-Newsgroups --
short and simple.

(It would be ideal if a patch for pine could be developed that would do
this transformation automatically, without requiring a procmail
filter.)

By doing so we largely preserve the original semantics of the
Newsgroups header in email, i.e., that the sender of the reply saw
something on Usenet and sent email in response, and that the recipient
of the email is not expected to post a reply to Usenet.  The basic idea
is:

     - if you get it in email, send any reply in email
     - if you see it on Usenet, 
	  either post a follow-up to Usenet
	  or send a private email reply
	  but don't do both except in unusual circumstances

>* Do you think this is a good example to put in the Procmail FAQ?

Actually this really belongs in the pine FAQ, if/when there is one.

Procmail is baroque.  Its .procmailrc file syntax is quite hard to
understand.   It's not a good match for most pine users, who want a
simple menu-driven interface that they can use without reading a
cryptic manual.  That a pine user should need to add a .forward file
entry to enable procmail, and add some cryptic lines to a .procmailrc
file, just to use pine normally, is ironic.
-- 
Rahul Dhesi <dhesi@rahul.net>


From owner-pine-info@cac.washington.edu  Fri Jan  6 13:08:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07140;
	Fri, 6 Jan 95 13:08:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03178;
	Fri, 6 Jan 95 12:59:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03172;
	Fri, 6 Jan 95 12:59:47 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQLZL-00038JC; Fri, 6 Jan 95 12:47 PST
To: pine-info@cac.washington.edu
From: tim@pooh (Tim Bloomfield)
Subject: Environment variable for pine.conf?
Message-Id: <D1zzLI.5Mv@oci.utoronto.ca>
Date: Fri, 6 Jan 1995 19:03:18 GMT



--
-------------------------------------------------
Tim Bloomfield  (tim@srcl.sunnybrook.utoronto.ca)
Sunnybrook Health Science Ctr. 
North York, Ontario.


From owner-pine-info@cac.washington.edu  Fri Jan  6 13:20:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07801;
	Fri, 6 Jan 95 13:20:33 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06648;
	Fri, 6 Jan 95 13:06:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06642;
	Fri, 6 Jan 95 13:06:01 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQLeG-00038KC; Fri, 6 Jan 95 12:52 PST
To: pine-info@cac.washington.edu
From: anil@unix1.sncc.lsu.edu (Anil Dedhia)
Subject: How to disable Alternate editor command system wide ?
Date: 6 Jan 1995 18:20:11 GMT
Message-Id: <3ek1kr$1nd4@unix1.sncc.lsu.edu>

Hi,

I would like to know about how to disable alternate editor command
system wide. We want all the people accessing pine on a particular machine 
to use only pico for editing. For this purpose, I created pine.conf.fixed 
file in /usr/local/lib directory on the RS/6000 machine running AIX
with the following options :

editor=/usr/local/bin/pico
feature-list=no-enable-alternate-editor-cmd

This still does not work. The documentation says that feature-list is
additive. So users can bypass the setting and use some other editor
by creating appropriate .pinerc file. So how do I achieve the goal 
of disabling alternate editor command system wide ?

Thanks for help,
Anil

--
------------------------------------------------------------------------
|          Anil Dedhia            |  e-mail: anil@unix1.sncc.lsu.edu   |
|  Information Technology Support |  Phone:  (504) 388-1928            | 
|    Louisiana State University   |  http://bit.csc.lsu.edu/~dedhia    | 
------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Fri Jan  6 13:23:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08003;
	Fri, 6 Jan 95 13:23:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03540;
	Fri, 6 Jan 95 13:06:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03534;
	Fri, 6 Jan 95 13:06:03 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQLgR-00038LC; Fri, 6 Jan 95 12:54 PST
To: pine-info@cac.washington.edu
From: tim@pooh (Tim Bloomfield)
Subject: Re: Environment variable for pine.conf?
Message-Id: <D1zzzz.5wp@oci.utoronto.ca>
References: <D1zzLI.5Mv@oci.utoronto.ca>
Date: Fri, 6 Jan 1995 19:11:59 GMT

Sorry about the previous message. Tin crashed When I resized a window while 
editing.

Is there an environment variable that can be set to point to the location of 
pine.conf? The man page does not mention one. Thanks


-------------------------------------------------
Tim Bloomfield  (tim@srcl.sunnybrook.utoronto.ca)
Sunnybrook Health Science Ctr. 
North York, Ontario.


From owner-pine-info@cac.washington.edu  Fri Jan  6 14:09:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10078;
	Fri, 6 Jan 95 14:09:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07985;
	Fri, 6 Jan 95 13:59:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07979;
	Fri, 6 Jan 95 13:59:56 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQMVH-00038CC; Fri, 6 Jan 95 13:47 PST
To: pine-info@cac.washington.edu
From: erin@skivs.ski.org (Erin O'Neill)
Subject: Pine & Procomm/Prowin
Date: 6 Jan 1995 13:38:04 -0800
Message-Id: <3ekd7s$oj3@skivs.ski.org>


I have some users that are using both the shareware Procomm for DOS & using 
Prowin (Procomm for windows) and both are complaining about NOT being able 
to do the 2 following things:

1) print a mail message to their local printers 

2) capture a mail message to a procomm capture file.


Many of these users want to stop using mail & only use pine, but they find 
they can't live without these features.

Any Suggestions?

erin
erin@skivs.ski.org
-- 
erin
erin@skivs.ski.org


From owner-pine-info@cac.washington.edu  Fri Jan  6 14:19:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10591;
	Fri, 6 Jan 95 14:19:19 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05148;
	Fri, 6 Jan 95 14:09:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05142;
	Fri, 6 Jan 95 14:09:55 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQMf0-00038KC; Fri, 6 Jan 95 13:57 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Setting up for news, upgrading pine systemwide.
Date: Fri, 6 Jan 1995 13:37:11 -0800
Message-Id: <Pine.ULT.3.92.950106132601.2851P-100000@shiva1.cac.washington.edu>
References: <ellis.789413557@gmi.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ellis.789413557@gmi.edu> 

On 6 Jan 1995, R. Stewart Ellis wrote:

> Date: 6 JAN 95 17:32:37 GMT 
> From: R. Stewart Ellis <ellis@nova.gmi.edu>
> Newgroups: comp.mail.pine
> Subject: Setting up for news, upgrading pine systemwide. 
> 
> First of all, although I generally think pine is a great MUA, I am
> distinctly uncomfortable with it as a newsreader, preferring nn.  However I
> am the one who originally installed elm and nn on our site several years
> ago, followed shortly by tin, and about a year ago, pine.  Currently the
> systemwide pine is 3.89, but I want to upgrade to 3.91.  
> 
> Part of what prevented me was an error message I keep getting when running
> 3.91 about unbalanced {.  I posted on it in the past but got no real help.
> Today I finally figured it out.  It had to do with the value of
> news-collections in the systemwide pine.conf file.  It was set to:
> 
> news-collections=News/[] *{$NNTPSERVER/nntp}[]
> 
> which correctly pointed 3.89 at our nntpserver, set in a global cshrc file.
> However this was not being instantiated properly by 3.9{0|1}.  I had to
> experiment with brackets and parens until I finally got a version that would
> work correctly with both 3.89 and 3.91:
> 
> news-collections=News/[] *{${NNTPSERVER}/nntp}[]
> 

FWIW, if you set
	
	nntp-server=$NNTPSERVER

and leave news-collections blank, Pine 3.91 will assume a default
news-collection.  Note that the "News/[]" in your example above is only
the nickname for the collection and does not have any other significance. 
 
> 
> Now I am trying to make sense of the folders issue.  Although I would expect
> the immediately preceding news-collection setting to look in ~/News then at
> the nntpserver, I do not seem to see any folders from my ~/News directory.
> I also experimented with setting the folder-collection to:
> 
> folder-collections=Mail/[] News/[]
> 
> This latter gave me a merged list of folders from ~/Mail and ~/News, but I
> could not append to the folders that I knew were in News.  Part of this may
> have been because they were saved by nn, which does not by default setup a
> folder in completely proper UNIX mail format.  I also could not just save to
> the folders by name, so I am quite confused about the relationship between
> news and folders.
> 

"Mail/[]" in the above example is only specifying a nickname and does not
have anything to do with the ~/Mail directory.  You have specified a
folder collection called "Mail/[]" that resides in the ~/News directory... 

> The model I want, because it is most compatible with our other newsreaders
> and MUAs, is to have news saved in folders in ~/News, mail saved in ~/Mail.
> Then I want users to be able to open the folders of saved news in a way
> distinct from their mail folders.  I know this runs against the cognitive
> model that the pine team seem to be pushing, but it is the one I am most
> comfortable trying to support, as an unpaid volunteer, in addition to my 12
> hrs/qtr teaching load, maintaining gopher and www, and serving on about a
> dozen committees.
> 

You can have as many folder collections as you want in Pine, but the first
one listed is the default for saves from any collection. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Fri Jan  6 15:10:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12734;
	Fri, 6 Jan 95 15:10:20 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06435;
	Fri, 6 Jan 95 15:05:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.fast.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06429;
	Fri, 6 Jan 95 15:05:49 -0800
Received: from roland.fast.net by fast.net with smtp
	(Smail3.1.28.1 #13) id m0rQNjq-0002HzC; Fri, 6 Jan 95 18:06 EST
Date: Fri, 6 Jan 1995 18:01:37 -0800 (PST)
From: Roland Zuk <roland@fast.net>
Cc: pine-info@cac.washington.edu
Subject: Re: Re-sort a folder *permanently*?
X-Sender: roland@ns.fast.net
In-Reply-To: <3ejgo5$jc9@erinews.ericsson.se>
Message-Id: <Pine.PCW.3.91.950106175834.4759B-100000@roland.fast.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On 6 Jan 1995, Peter Wastholm wrote:

> press $ d to sort the letters by date the way I want them. Isn't there a way 
> to make that order permanent?


Sort the folder the way you want it, the Select All and Apply Save to a 
new folder to create a new folder in sorted order.  From then on, you can 
save a lot of time by just reading the folder in Arrival order (the order 
they occur in the file).

Regards
Roland



From owner-pine-info@cac.washington.edu  Fri Jan  6 15:54:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14413;
	Fri, 6 Jan 95 15:54:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07320;
	Fri, 6 Jan 95 15:44:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from uu4.psi.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07314;
	Fri, 6 Jan 95 15:44:23 -0800
Received: from msi.UUCP by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP;
        id AA27249 for ; Fri, 6 Jan 95 18:27:03 -0500
Date: Fri, 6 Jan 1995 14:39:50 -0800 (PST)
From: Knute Snortum <knute@masi.com>
To: Pine Information Discussion Group <pine-info@cac.washington.edu>
Subject: Pine "build" problems
Message-Id: <Pine.SCO.3.91.950106133650.18138A-300000@MSI.masi.COM>
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-16838-789431990=:20729"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-16838-789431990=:20729
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'm trying to get Pine to compile on a "tweeked" System V Unix box (it's 
old.)  Pine wants me to run the "build" script to make the files, but 
it's not finding some standard library stuff (I think.)  It's hard to 
follow the logic of the build script because a) I'm a novice and b) it's 
written to compile on several platforms, but it seems like the actual 
compile statements start with $(CC).

Here's the dumb question: where does C look for the standard libraries?  
In other words, when you have a statement like

  #include <stdlib.h>

where does C look for that?  I found a command line switch (-I) that 
allows me to specify additional paths to look in, but is there a global 
way to do this?

Maybe it has nothing to do with libraries (the errors look kinda like C 
errors.)  I have attatched two file for those who wish to take a look 
that I created thusly:

  ./build >build.out 2>build.err

I would appreciate any help.

--- Knute Snortum			Internet: knute@msi.masi.com
    MAS Inc.				Compuserve: 72144,1646


---559023410-16838-789431990=:20729
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="build.out"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SCO.3.91.950106143950.20729A@MSI.masi.COM>
Content-Description: 

bWFrZSBhcmdzIGFyZSAiQ0M9Y2MiDQoNCk1ha2luZyBjLWNsaWVudCBsaWJy
YXJ5LCBtdGVzdCBhbmQgaW1hcGQNCgltYWtlIGJ1aWxkIFNZU1RZUEU9QU5T
SSBPUz1zY28NCgllY2hvIHNjbyA+IE9TVFlQRQ0KCXJtIC1yZiBzeXN0eXBl
DQoJbG4gLXMgQU5TSSBzeXN0eXBlDQoJY2QgQU5TSS9jLWNsaWVudDsgbWFr
ZSBzY28NCgltYWtlIG10ZXN0IE9TPXNjbyBFWFRSQURSSVZFUlM9IiIgXA0K
CQlTVERQUk9UTz1tbWRmcHJvdG8gXA0KCQlDRkxBR1M9IExOPSJsbiIgUkFO
TElCPXRydWUgXA0KCQlMREZMQUdTPSItbHNvY2tldCAtbGNyeXB0IC1scHJv
dCAtbHgiDQoJLi9kcml2ZXJzICBpbWFwIG5udHAgcG9wMyBtaCBtdHggdGVu
ZXggbW1kZiBiZXplcmsgbmV3cyBwaGlsZSBkdW1teQ0KCXJtIC1mIE9TVFlQ
RSBDRkxBR1MgTERGTEFHUyBvc2RlcC5oDQoJZWNobyBzY28gPiBPU1RZUEUN
CgllY2hvICA+IENGTEFHUw0KCWVjaG8gLWxzb2NrZXQgLWxjcnlwdCAtbHBy
b3QgLWx4ICA+IExERkxBR1MNCglsbiBvc19zY28uaCBvc2RlcC5oDQoJY2Mg
IC1jIG1haWwuYw0KKioqIEVycm9yIGNvZGUgMTAyDQoqKiogRXJyb3IgY29k
ZSAxDQoqKiogRXJyb3IgY29kZSAxDQoqKiogRXJyb3IgY29kZSAxDQoNCk1h
a2luZyBQaWNvDQoJY2MgLWMgLURzY28gLURQT1NJWCAtREpPQl9DT05UUk9M
ICBvc2RlcC5jDQoqKiogRXJyb3IgY29kZSAxDQoNCk1ha2luZyBQaW5lLg0K
CWNjIC1EU0NPICAgLWcgLURERUJVRyAtRFNZU1RZUEU9XCJTQ09cIiAtYyBh
ZGRyYm9vay5jDQoqKiogRXJyb3IgY29kZSAxDQoNCkxpbmtzIHRvIGV4ZWN1
dGFibGVzIGFyZSBpbiBiaW4gZGlyZWN0b3J5Og0KRG9uZQ0K
---559023410-16838-789431990=:20729
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="build.err"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SCO.3.91.950106143950.20729B@MSI.masi.COM>
Content-Description: 

bWFpbC5jDQptYWlsLmgoMzQ2KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3Ig
OiBpZGVudGlmaWVyICdzJw0KbWFpbC5oKDM0OCkgOiBlcnJvciA2MTogc3lu
dGF4IGVycm9yIDogaWRlbnRpZmllciAncycNCm1haWwuaCgzNTApIDogZXJy
b3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3MnDQptYWlsLmgo
MzUxKSA6IGVycm9yIDU5OiBzeW50YXggZXJyb3IgOiAnfScNCm1haWwuaCg0
MTcpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ21h
aWxib3gnDQptYWlsLmgoNDE5KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3Ig
OiBpZGVudGlmaWVyICdmdW5jdGlvbicNCm1haWwuaCg0MjEpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0MjMpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0MjUpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0MjcpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0MjkpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0MzEpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0MzMpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0MzUpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0MzcpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0MzkpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NDEpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0NDQpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0NDYpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NDgpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0NTApIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0NTIpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NTQpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0NTYpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0NTgpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NjApIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0NjIpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0NjQpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NjYpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0NjgpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0NzApIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NzIpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0NzQpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg0NzYpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg0NzkpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg0ODApIDogZXJyb3IgNTk6IHN5bnRheCBlcnJv
ciA6ICd9Jw0KbWFpbC5oKDQ5OCkgOiBlcnJvciA1NDogZXhwZWN0ZWQgJygn
IHRvIGZvbGxvdyAnY29uc3QnDQptYWlsLmgoNDk4KSA6IGVycm9yIDg1OiAn
ZGF5cycgOiBpZ25vcmVkDQptYWlsLmgoNDk5KSA6IGVycm9yIDYyOiB0eXBl
ICdjaGFyJyB1bmV4cGVjdGVkDQptYWlsLmgoNTA0KSA6IGVycm9yIDYxOiBz
eW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdzdHJlYW0nDQptYWlsLmgoNTA1
KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdmJw0K
bWFpbC5oKDUwNikgOiBlcnJvciA2MTogc3ludGF4IGVycm9yIDogaWRlbnRp
ZmllciAnc3RyZWFtJw0KbWFpbC5oKDUwNykgOiBlcnJvciA2MTogc3ludGF4
IGVycm9yIDogaWRlbnRpZmllciAndGltZScNCmxpbmthZ2UuaCgxKSA6IHdh
cm5pbmcgMzg6ICdpbWFwZHJpdmVyJyA6IGZvcm1hbCBwYXJhbWV0ZXIgaGFz
IGJhZCBzdG9yYWdlIGNsYXNzDQpsaW5rYWdlLmgoMSkgOiBlcnJvciA4NTog
J2ltYXBkcml2ZXInIDogaWdub3JlZA0KbGlua2FnZS5oKDIpIDogd2Fybmlu
ZyAzODogJ25udHBkcml2ZXInIDogZm9ybWFsIHBhcmFtZXRlciBoYXMgYmFk
IHN0b3JhZ2UgY2xhc3MNCmxpbmthZ2UuaCgyKSA6IGVycm9yIDg1OiAnbm50
cGRyaXZlcicgOiBpZ25vcmVkDQpsaW5rYWdlLmgoMykgOiB3YXJuaW5nIDM4
OiAncG9wM2RyaXZlcicgOiBmb3JtYWwgcGFyYW1ldGVyIGhhcyBiYWQgc3Rv
cmFnZSBjbGFzcw0KbGlua2FnZS5oKDMpIDogZXJyb3IgODU6ICdwb3AzZHJp
dmVyJyA6IGlnbm9yZWQNCmxpbmthZ2UuaCg0KSA6IHdhcm5pbmcgMzg6ICdt
aGRyaXZlcicgOiBmb3JtYWwgcGFyYW1ldGVyIGhhcyBiYWQgc3RvcmFnZSBj
bGFzcw0KbGlua2FnZS5oKDQpIDogZXJyb3IgODU6ICdtaGRyaXZlcicgOiBp
Z25vcmVkDQpsaW5rYWdlLmgoNSkgOiB3YXJuaW5nIDM4OiAnbXR4ZHJpdmVy
JyA6IGZvcm1hbCBwYXJhbWV0ZXIgaGFzIGJhZCBzdG9yYWdlIGNsYXNzDQps
aW5rYWdlLmgoNSkgOiBlcnJvciA4NTogJ210eGRyaXZlcicgOiBpZ25vcmVk
DQpsaW5rYWdlLmgoNikgOiB3YXJuaW5nIDM4OiAndGVuZXhkcml2ZXInIDog
Zm9ybWFsIHBhcmFtZXRlciBoYXMgYmFkIHN0b3JhZ2UgY2xhc3MNCmxpbmth
Z2UuaCg2KSA6IGVycm9yIDg1OiAndGVuZXhkcml2ZXInIDogaWdub3JlZA0K
bGlua2FnZS5oKDcpIDogd2FybmluZyAzODogJ21tZGZkcml2ZXInIDogZm9y
bWFsIHBhcmFtZXRlciBoYXMgYmFkIHN0b3JhZ2UgY2xhc3MNCmxpbmthZ2Uu
aCg3KSA6IGVycm9yIDg1OiAnbW1kZmRyaXZlcicgOiBpZ25vcmVkDQpsaW5r
YWdlLmgoOCkgOiB3YXJuaW5nIDM4OiAnYmV6ZXJrZHJpdmVyJyA6IGZvcm1h
bCBwYXJhbWV0ZXIgaGFzIGJhZCBzdG9yYWdlIGNsYXNzDQpsaW5rYWdlLmgo
OCkgOiBlcnJvciA4NTogJ2JlemVya2RyaXZlcicgOiBpZ25vcmVkDQpsaW5r
YWdlLmgoOSkgOiB3YXJuaW5nIDM4OiAnbmV3c2RyaXZlcicgOiBmb3JtYWwg
cGFyYW1ldGVyIGhhcyBiYWQgc3RvcmFnZSBjbGFzcw0KbGlua2FnZS5oKDkp
IDogZXJyb3IgODU6ICduZXdzZHJpdmVyJyA6IGlnbm9yZWQNCmxpbmthZ2Uu
aCgxMCkgOiB3YXJuaW5nIDM4OiAncGhpbGVkcml2ZXInIDogZm9ybWFsIHBh
cmFtZXRlciBoYXMgYmFkIHN0b3JhZ2UgY2xhc3MNCmxpbmthZ2UuaCgxMCkg
OiBlcnJvciA4NTogJ3BoaWxlZHJpdmVyJyA6IGlnbm9yZWQNCmxpbmthZ2Uu
aCgxMSkgOiB3YXJuaW5nIDM4OiAnZHVtbXlkcml2ZXInIDogZm9ybWFsIHBh
cmFtZXRlciBoYXMgYmFkIHN0b3JhZ2UgY2xhc3MNCmxpbmthZ2UuaCgxMSkg
OiBlcnJvciA4NTogJ2R1bW15ZHJpdmVyJyA6IGlnbm9yZWQNCm1haWwuaCg2
MDcpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0
cmVhbScNCm1haWwuaCg2MDgpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6
IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2MDkpIDogZXJyb3IgNjE6
IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2
MTApIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0
cmVhbScNCm1haWwuaCg2MTEpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6
IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2MTIpIDogZXJyb3IgNjE6
IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmluZycNCm1haWwuaCg2
MTMpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0
cmluZycNCm1haWwuaCg2MTQpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6
IGlkZW50aWZpZXIgJ3N0cmluZycNCm1haWwuaCg2MTUpIDogZXJyb3IgNjE6
IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmluZycNCm1haWwuaCg2
MTYpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ2hv
c3QnDQptYWlsLmgoNjE3KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBp
ZGVudGlmaWVyICdzdHJlYW0nDQptYWlsLmgoNjE4KSA6IGVycm9yIDYxOiBz
eW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdzdHJlYW0nDQptYWlsLmgoNjE5
KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdzdHJl
YW0nDQptYWlsLmgoNjIwKSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBp
ZGVudGlmaWVyICdzdHJpbmcnDQptYWlsLmgoNjIxKSA6IGVycm9yIDYxOiBz
eW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdmJw0KbWFpbC5oKDYyMikgOiBl
cnJvciA2MTogc3ludGF4IGVycm9yIDogaWRlbnRpZmllciAnc3RyZWFtJw0K
bWFpbC5oKDYyNCkgOiB3YXJuaW5nIDM4OiAnbWFpbF9zdHJpbmcnIDogZm9y
bWFsIHBhcmFtZXRlciBoYXMgYmFkIHN0b3JhZ2UgY2xhc3MNCm1haWwuaCg2
MjQpIDogZXJyb3IgODU6ICdtYWlsX3N0cmluZycgOiBpZ25vcmVkDQptYWls
LmgoNjI1KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVy
ICdzJw0KbWFpbC5oKDYyNikgOiBlcnJvciA2MTogc3ludGF4IGVycm9yIDog
aWRlbnRpZmllciAncycNCm1haWwuaCg2MjcpIDogZXJyb3IgNjE6IHN5bnRh
eCBlcnJvciA6IGlkZW50aWZpZXIgJ3MnDQptYWlsLmgoNjI4KSA6IGVycm9y
IDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdkcml2ZXInDQptYWls
LmgoNjI5KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVy
ICdzdHJlYW0nDQptYWlsLmgoNjMwKSA6IGVycm9yIDYxOiBzeW50YXggZXJy
b3IgOiBpZGVudGlmaWVyICdzdHJlYW0nDQptYWlsLmgoNjMxKSA6IGVycm9y
IDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdzdHJlYW0nDQptYWls
LmgoNjMyKSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVy
ICdzdHJlYW0nDQptYWlsLmgoNjMzKSA6IGVycm9yIDYxOiBzeW50YXggZXJy
b3IgOiBpZGVudGlmaWVyICdzdHJlYW0nDQptYWlsLmgoNjM0KSA6IGVycm9y
IDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVyICdzdHJlYW0nDQptYWls
LmgoNjM1KSA6IGVycm9yIDYxOiBzeW50YXggZXJyb3IgOiBpZGVudGlmaWVy
ICduYW1lJw0KbWFpbC5oKDYzNikgOiBlcnJvciA2MTogc3ludGF4IGVycm9y
IDogaWRlbnRpZmllciAnbmFtZScNCm1haWwuaCg2MzcpIDogZXJyb3IgNjE6
IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2
MzgpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0
cmVhbScNCm1haWwuaCg2MzkpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6
IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2NDApIDogZXJyb3IgNjE6
IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2
NDEpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0
cmVhbScNCm1haWwuaCg2NDIpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6
IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2NDMpIDogZXJyb3IgNjE6
IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2
NDQpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ29s
ZHN0cmVhbScNCm1haWwuaCg2NDUpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2NDYpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg2NDcpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J2hhbmRsZScNCm1haWwuaCg2NDgpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ2hhbmRsZScNCm1haWwuaCg2NDkpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg2NTApIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg2NTEpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2NTIpIDogZXJyb3Ig
NjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwu
aCg2NTMpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJvciA6IGlkZW50aWZpZXIg
J3N0cmVhbScNCm1haWwuaCg2NTQpIDogZXJyb3IgNjE6IHN5bnRheCBlcnJv
ciA6IGlkZW50aWZpZXIgJ3N0cmVhbScNCm1haWwuaCg2NTQpIDogZmF0YWwg
ZXJyb3IgMzogZXJyb3IgY291bnQgZXhjZWVkcyAxMDA7IHN0b3BwaW5nIGNv
bXBpbGF0aW9uDQoNClN0b3AuDQoNClN0b3AuDQoNClN0b3AuDQoNClN0b3Au
DQpvc2RlcC5jDQpvc2RlcC5jKDcwKSA6IGZhdGFsIGVycm9yIDE1OiBjYW5u
b3QgZmluZCAndGVybWlvcy5oJw0KDQpTdG9wLg0KYWRkcmJvb2suYw0Kb3Mu
aCgyMTgpIDogZmF0YWwgZXJyb3IgMTU6IGNhbm5vdCBmaW5kICdzeXMvd2Fp
dC5oJw0KDQpTdG9wLg0Kc2l6ZTogIGJpbi9waW5lOiAgY2Fubm90IG9wZW4N
CnNpemU6ICBiaW4vbXRlc3Q6ICBjYW5ub3Qgb3Blbg0Kc2l6ZTogIGJpbi9p
bWFwZDogIGNhbm5vdCBvcGVuDQpzaXplOiAgYmluL3BpY286ICBjYW5ub3Qg
b3Blbg0K
---559023410-16838-789431990=:20729--


From owner-pine-info@cac.washington.edu  Fri Jan  6 17:37:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18817;
	Fri, 6 Jan 95 17:37:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12972;
	Fri, 6 Jan 95 17:30:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12966;
	Fri, 6 Jan 95 17:30:22 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQPn6-00038CC; Fri, 6 Jan 95 17:18 PST
To: pine-info@cac.washington.edu
From: kf7qz@bcstec.ca.boeing.com (Rick Scott)
Subject: FTP for Pine
Message-Id: <D205wq.L9z@bcstec.ca.boeing.com>
Date: Fri, 6 Jan 1995 21:19:38 GMT

I am sorry if I offend for asking for this on here. But where can I ftp 
pine and Pico from.  I just opened this area and did not see a FAQ to 
read on access.  I want to use it on Amateur Radio TCP/IP instead of the 
current elm and ed that I use. 

Thanks ahead of time

-- 
| Ricky Scott                     |        All Comments (unfortunately) |
| kf7qz@bectec.ca.boeing.com      |        are purely my own and do not |
| kf7qz@prostar.com               |        reflect the views nor are    |
|                                 |        supported by my employer     |


From owner-pine-info@cac.washington.edu  Fri Jan  6 17:59:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19762;
	Fri, 6 Jan 95 17:59:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13492;
	Fri, 6 Jan 95 17:51:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13486;
	Fri, 6 Jan 95 17:51:16 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id RAA24452 for <pine-info@cac.washington.edu>; Fri, 6 Jan 1995 17:51:14 -0800
Date: Fri, 6 Jan 1995 17:51:48 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Bruce Sachetti <bsachett@alert.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Using Wyse50 (or any non-VTxxx) terminals w/Pine
In-Reply-To: <bsachett.3.0443F9EF@alert.com>
Message-Id: <Pine.SUN.3.91.950106174651.24772A@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 6 Jan 1995, Bruce Sachetti wrote:

> If anyone has had any success making a Wyse 50 terminal work with Pine 
> (especially arrow keys), please let me know.  I originally thought this was a 
> termcap vs. terminfo issue.  
> 
> I am using Pine on an RS/6000 (3.2.3 and 3.2.5) and have tried Pine 3.89 and 
> Pine 3.91.  Per David Miller's previous response, I did make sure that the 
> pico and pine makefile.a32 had "-l curses" instead of "-l termcap".  
> 
> It seems that Pine isn't using terminfo.  
> 
> Any help would be appreciated...
>
> Bruce G. Sachetti                    
> Systems Administrator II         
> Alert Centre Inc. Englewood, CO   
> bsachett@alert.com (303)488-7719     
> 
>

For me it was discovering that we had non-ANSI keyboards.  The people in 
my office are just learning to use the control-key equivilents.  It's too 
much work to change ALL our applications now. 

knute@teleport.COM  Public Access User --- Not affiliated with Teleport
Public Access UNIX and Internet at (503) 220-1016 (2400-14400, N81)

or, e-mail me at work: knute@msi.masi.com


From owner-pine-info@cac.washington.edu  Fri Jan  6 18:02:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19869;
	Fri, 6 Jan 95 18:02:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10390;
	Fri, 6 Jan 95 17:55:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10384;
	Fri, 6 Jan 95 17:55:27 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQQBg-00038CC; Fri, 6 Jan 95 17:43 PST
To: pine-info@cac.washington.edu
From: martin@dorsai.dorsai.org (martin schildkret)
Subject: Turning Off Insert Mode In Pine
Message-Id: <D20FIG.JtC@dorsai.org>
Date: Sat, 7 Jan 1995 00:47:03 GMT

  Is there any way of turning off the insert mode in PINE. I would much 
prfer to be in typeover. Thanks for any help that I may receive.....

--
       -----------------------------------------------------------
       | <<<   Martin@Dorsai.Org  |  < Martin Schildkret >   >>> |
       -----------------------------------------------------------
                                


From owner-pine-info@cac.washington.edu  Fri Jan  6 18:05:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20157;
	Fri, 6 Jan 95 18:05:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13767;
	Fri, 6 Jan 95 18:01:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13761;
	Fri, 6 Jan 95 18:01:31 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id SAA25452 for <pine-info@cac.washington.edu>; Fri, 6 Jan 1995 18:01:30 -0800
Date: Fri, 6 Jan 1995 18:02:01 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Rick Scott <kf7qz@bcstec.ca.boeing.com>
Cc: pine-info@cac.washington.edu
Subject: Re: FTP for Pine
In-Reply-To: <D205wq.L9z@bcstec.ca.boeing.com>
Message-Id: <Pine.SUN.3.91.950106175715.24772B@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 6 Jan 1995, Rick Scott wrote:

> I am sorry if I offend for asking for this on here. But where can I ftp 
> pine and Pico from.  I just opened this area and did not see a FAQ to 
> read on access.  I want to use it on Amateur Radio TCP/IP instead of the 
> current elm and ed that I use. 
> 
> Thanks ahead of time
> 
> -- 
> | Ricky Scott                     |        All Comments (unfortunately) |
> | kf7qz@bectec.ca.boeing.com      |        are purely my own and do not |
> | kf7qz@prostar.com               |        reflect the views nor are    |
> |                                 |        supported by my employer     |
> 

Boy, people are really nervous about getting flamed these days.  It's 
okay; we're all friendly here.

I believe you can FPT right into cac.washington.edu and get the latest 
stuff.  Nancy, if you're listening, could you give him all the lastest?  I 
don't have it handy.

knute@teleport.COM  Public Access User --- Not affiliated with Teleport
Public Access UNIX and Internet at (503) 220-1016 (2400-14400, N81)



From owner-pine-info@cac.washington.edu  Fri Jan  6 19:34:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22378;
	Fri, 6 Jan 95 19:34:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15161;
	Fri, 6 Jan 95 19:30:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15155;
	Fri, 6 Jan 95 19:30:43 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQRj0-00038MC; Fri, 6 Jan 95 19:21 PST
To: pine-info@cac.washington.edu
From: UMABnet Help Account <help@umabnet.ab.umd.edu>
Subject: Limit on ratio of new to included text in news postings?
Date: Fri, 6 Jan 1995 18:33:16 -0500
Message-Id: <Pine.A32.3.91.950106181753.55663C-100000@umabnet.ab.umd.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Greetings.  I got this message from one of our users:

> Whenever I reply to a message in Usenet, and save the message, I get an
> error "441, more text than new" or something like that.  Do you know what
> that is and how to correct it?  I would like to be able to reply to these
> messages (by including parts of the original message for ease of reading).

I assume the software is checking for some appropriate ratio of new text
to included text in a follow-up to a newsgroup post.  I tested this out on
our system, incrementally adding to the new text and deleting from the 
included text.  I was still getting this error 441 quite a bit after 
I, a seasoned reader of news, felt that the ratio of new to included text 
was appropriate.

Can anyone tell me:

1. Is it Pine, or some other bit of software called by Pine, that is 
generating this message?

2. How does whatever-it-is calculate the appropriate ratio?

3. Is the some way to tweak the formula, or turn the checking off entirely?
(The latter might be preferable, as it would disallow "Ditto." posts, 
which would be fine by me.)

Thanks in advance.

Miriam 

-------------------------------------------------------------------------
Miriam Jaffe * Information Services * University of Maryland at Baltimore 
   100 North Greene Street, 2nd floor * Baltimore, MD * 21201 * U.S.A.
             +1 410 706 8166 * mjaffe@umabnet.ab.umd.edu






From owner-pine-info@cac.washington.edu  Fri Jan  6 20:42:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23819;
	Fri, 6 Jan 95 20:42:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12715;
	Fri, 6 Jan 95 20:38:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12709;
	Fri, 6 Jan 95 20:38:27 -0800
Date: Fri, 6 Jan 95 20:38:27 -0800
From: pine-list-owner@rain.psg.com
Message-Id: <9501070438.AA12709@mx1.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQSmi-00038CC; Fri, 6 Jan 95 20:29 PST


There is not currently a native OS/2 version of Pine, but PC-Pine for
Windows is reported to work if you have winsock on your machine.  The FAQ 
is in

	ftp://ftp.cac.washington.edu/pine/docs/faq

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 2 Jan 1995 mfrisch@io.org wrote:

> Date: 2 JAN 1995 00:45:19 GMT 
> From: mfrisch@io.org
> Newgroups: comp.mail.pine
> Subject: OS/2 version of Pine? 
> 
> 	Is there an OS/2 version of Pine available that works with a POP mail
> server?  If this is a FAQ, please direct me to the source of the FAQ.
> 
> 	Thank you very much in advance!
> 
> Mike - Team OS/2
> 
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan  6 20:53:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24074;
	Fri, 6 Jan 95 20:53:07 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16247;
	Fri, 6 Jan 95 20:49:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16241;
	Fri, 6 Jan 95 20:49:42 -0800
Date: Fri, 6 Jan 95 20:49:42 -0800
From: pine-list-owner@rain.psg.com
Message-Id: <9501070449.AA16241@mx2.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQSzO-00038CC; Fri, 6 Jan 95 20:42 PST

6. January 1995

To Whoever can answer...

I am looking for a GUI for Unix-based Pine, preferably something like 
Mosaic.  

If anyone could point me in the right direction, I would really 
appreciate it.

Craig


From owner-pine-info@cac.washington.edu  Fri Jan  6 21:07:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24377;
	Fri, 6 Jan 95 21:07:54 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16507;
	Fri, 6 Jan 95 21:04:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16501;
	Fri, 6 Jan 95 21:04:55 -0800
Date: Fri, 6 Jan 95 21:04:55 -0800
From: pine-list-owner@rain.psg.com
Message-Id: <9501070504.AA16501@mx2.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQTDS-00038JC; Fri, 6 Jan 95 20:57 PST


You can set "sort-key=by-date" in the Setup/Config screen.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 6 Jan 1995, Peter Wastholm wrote:

> Date: 6 JAN 1995 13:31:49 GMT 
> From: Peter Wastholm <peter-wa@dsv.su.se>
> Newgroups: comp.mail.pine
> Subject: Re-sort a folder *permanently*? 
> 
> I recently restructured my folder-collection. When moving letters to their 
> appropriate folders, the order got messed up, so now most of my folders are 
> sorted pretty randomly. Therefore, every time I enter a folder, I have to 
> press $ d to sort the letters by date the way I want them. Isn't there a way 
> to make that order permanent?
> 
> /Peter Wastholm
> 
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan  6 21:07:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24401;
	Fri, 6 Jan 95 21:07:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13125;
	Fri, 6 Jan 95 21:04:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13119;
	Fri, 6 Jan 95 21:04:43 -0800
Date: Fri, 6 Jan 95 21:04:43 -0800
From: pine-list-owner@rain.psg.com
Message-Id: <9501070504.AA13119@mx1.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQTDH-00038CC; Fri, 6 Jan 95 20:57 PST


The Pine FAQ is available from ftp.cac.washington.edu in the pine/docs
directory.  It has not been posted recently, since we have been working on
a new version that has taken longer than we expected... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 6 Jan 1995, Rick Rogers wrote:

> Date: 6 JAN 95 09:35:30 NDT 
> From: Rick Rogers <rrogers@minnie.imd.nrc.ca>
> Newgroups: comp.mail.pine
> Subject: FAQ?? or VMS PINE?? 
> 
> Hi all,
> 
>    Where is the FAQ for this group (assuming there is one), I can't
> find it as far back as my feed has.
> 
>    If there isn't a FAQ I'm specifically looking for info on PINE
> for VMS to work with SMTP.
> 
> Thanks,
> 
> Rick
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan  6 21:32:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24930;
	Fri, 6 Jan 95 21:32:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13415;
	Fri, 6 Jan 95 21:28:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13409;
	Fri, 6 Jan 95 21:28:31 -0800
Date: Fri, 6 Jan 95 21:28:31 -0800
From: pine-list-owner@rain.psg.com
Message-Id: <9501070528.AA13409@mx1.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQTYI-00038JC; Fri, 6 Jan 95 21:18 PST

How does one perform that operation?
                                         Chuck Hubbell

(P.S.  I've already tried to post this message here,
       so if this turns out to be a re-posting,
       it illustrates the very problem that perplexes me.)




From owner-pine-info@cac.washington.edu  Sat Jan  7 01:39:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29652;
	Sat, 7 Jan 95 01:39:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19905;
	Sat, 7 Jan 95 01:35:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19899;
	Sat, 7 Jan 95 01:35:13 -0800
Date: Sat, 7 Jan 95 01:35:13 -0800
From: pine-list-owner@psg.com
Message-Id: <9501070935.AA19899@mx2.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQXNW-00038CC; Sat, 7 Jan 95 01:24 PST

Hans Chr. Nielsen (hcn@sysdeco.no) wrote:
: After these patches pine keeps locking up. It happens when it tries
: to open a folder in my folder directory. It creates a <folder>.lock file
: and nothing happens after this. It may also lock up when opening the
: sent-mail folder to save a copy of outgoing mail. The same lock file
: is created. The hanging process may not be killed.

: Any suggestions will be greatly appreciated. I don't think I will get any
: help from HP as pine is the only program that has problems.

Try this:

1. Make sure you have ALL the patches for rpc.statd, rpc.lockd, and NFS
2. On both machines (server and client), do the following, in order:
   a. kill rpc.statd
   b. kill rpc.lockd
   DO a AND b ON BOTH MACHINES BEFORE GOING TO C
   c. rm -rf /etc/sm /etc/sm.bak
   d. start rpc.statd
   e. start rpc.lockd

I am working with HP to try to find out why the sm directories are being 
corrupted-- no luck so far.  Please post a followup and let us know if 
this helps.

--
* Noel Hunter,  Academic Systems Administrator,    Wake Forest University *
* email: noel@wfu.edu                            http://www.wfu.edu/~noel *


From owner-pine-info@cac.washington.edu  Sat Jan  7 03:47:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02177;
	Sat, 7 Jan 95 03:47:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17778;
	Sat, 7 Jan 95 03:44:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17772;
	Sat, 7 Jan 95 03:44:15 -0800
Date: Sat, 7 Jan 95 03:44:15 -0800
From: pine-list-owner@psg.com
Message-Id: <9501071144.AA17772@mx1.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQZQy-00038CC; Sat, 7 Jan 95 03:35 PST

  I find no way to export a marked block of text from Pine message to a 
file. Is there a way?

  Will there come a time when Pine exhibits two windows on receiving the 
Reply command?: Inbox mail in the top window; reply-being-composed in 
bottom window; marked block can be transferred from one to another.

                                -- Bill Smithers



From owner-pine-info@cac.washington.edu  Sat Jan  7 04:03:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02474;
	Sat, 7 Jan 95 04:03:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21486;
	Sat, 7 Jan 95 03:59:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21480;
	Sat, 7 Jan 95 03:59:19 -0800
Date: Sat, 7 Jan 95 03:59:19 -0800
From: pine-list-owner@psg.com
Message-Id: <9501071159.AA21480@mx2.cac.washington.edu>
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rQZe9-00038CC; Sat, 7 Jan 95 03:49 PST

I want to change the id  in pine. For ex.

                    007@school.edu  
          
               to   Al@school.edu 
                    (I want to change or remove 007 ,is this possible?)

So far I can do this only  Al 007@school.edu
                              ^^^ still here.             



(by configuring  the option menu)


Also, is there any way to change the IP (domain) address? That is ,from
@school.edu to @home.edu for ex.? I have already tried the  config
. values , I can modify this part but once the mail is sent it cannot
leave my mail system.  I guess to send out mail , the return address
must be identifiable before mail is to leave the local host? 


Thanks
Al




From owner-pine-info@cac.washington.edu  Sat Jan  7 08:36:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07516;
	Sat, 7 Jan 95 08:36:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21221;
	Sat, 7 Jan 95 08:32:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21215;
	Sat, 7 Jan 95 08:32:20 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQdtI-00038JC; Sat, 7 Jan 95 08:21 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: Pine Pipe to Zmodem
Date: 7 Jan 1995 11:19:44 -0500
Message-Id: <3emev0$o7a@wabash.iac.net>
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu> <3eeni5$t36@wabash.iac.net> <ellis.789325031@gmi.edu>  <Pine.NXT.3.91.950106012216.22917A-100000@lipschitz>

J. Kelly Cunningham (deviate@lipschitz) wrote:
: -----BEGIN PGP SIGNED MESSAGE-----

: On 5 Jan 1995, R. Stewart Ellis wrote:

:    cjolley@iac.net (Carl Jolley) writes:
:    
:     >Chris Alfeld (calfeld@ceslab03) wrote:
:     >: Carl Jolley (cjolley@iac.net) wrote:
:     >: : I'm doing terminal emulation to my ISP. The default mailer is Pine. The
:     >: : pipe command IS configured but I can't get piping to: sz - to work. When
:     >: : I try it, the screen does display the zmodem init string, i.e *B00000....
: [...]   
:     >: 	| (cat > tmpfile;sz tmpfile;rm -f tmpfile)
:    
: This isn't really what you want, but how 'bout this?
[rest deleted, but saved for later study]
 
You are correct, I could always just export the message I am interested in
and later download them after I quit Pine. I sounds like there is no way
to interactively download a Pine message ala Elm's pipe. The behavior of
Pine's pipe, i.e. pipe to a command and capture the output back into
a viewer, does not seem to be documented in either the man pages or in
Pine's help screens. I thought that something was broken, but now I
understand that the operation of Pine's pipe is a "feature". It would be
nice if in addition to the current operation of Pine's pipe there was an
option to do a pipe without capturing the command's stdout.
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Sat Jan  7 11:30:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11073;
	Sat, 7 Jan 95 11:30:05 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26825;
	Sat, 7 Jan 95 11:27:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26819;
	Sat, 7 Jan 95 11:27:36 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQgg7-00038CC; Sat, 7 Jan 95 11:19 PST
To: pine-info@cac.washington.edu
From: tgpt_ltd@uhura.cc.rochester.edu (Thomas Guptill)
Subject: repost: Pine/VMS FTP site in US
Message-Id: <1995Jan7.184624.17081@galileo.cc.rochester.edu>
Date: Sat, 7 Jan 95 18:46:24 GMT


	Since there has been a bit of traffic about it recently, I figured
I'd let people know again that VMS-Pine v3.91 is available for anonymous ftp
from lenin.cc.rochester.edu.  Extracting it requires a recent version of
UNZIP, and you MUST remember to transfer it as a binary.  This version
provides improved TCPIP support, but I've found that 3.89 seems to work
better under my installation of VMS (5.4-2).  (I'm not using TCPIP support,
since I only use it for local mail and I need to talk to PMDF anyway.) BTW: 
Congratulations to the development team; it's a great program.  

	Tom
-- 
| Tom Guptill            I don't speak for UCC from this account. |
| tgpt_ltd@UORDBV                                                 |
| Temporary LARVA-ED resident                                     |


From owner-pine-info@cac.washington.edu  Sat Jan  7 11:55:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11641;
	Sat, 7 Jan 95 11:55:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23792;
	Sat, 7 Jan 95 11:53:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23786;
	Sat, 7 Jan 95 11:53:55 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQh0O-00038QC; Sat, 7 Jan 95 11:40 PST
To: pine-info@cac.washington.edu
From: rross@lang1.langara.bc.ca (Ron Ross)
Subject: Re: trouble with the return address
Date: 6 Jan 1995 05:03:14 GMT
Message-Id: <3eiiui$8rq@vcc7.vcc.bc.ca>
References: <3ecrs4$2v2@cronkite.ocis.temple.edu> <D1xzAx.Gpy@oci.utoronto.ca>

There are a couple of things you could try.  #1 is setting the 
user-domain variable to "micronet.wcu.edu".  #2 would be to try
setting the use-domain-name-only switch to "NO".

Hope this helps.

           ___  Oo            .:/
          (___)o_o         ,,///;,   ,;/
     //====--//(_)        o:::::::;;///         Ron Ross           
             \\ ^        >::::::::;;\\\         <rross@langara.bc.ca>
                           ''\\\\\'" ';\        I'd rather be diving !!!


Tim Bloomfield (tim@pooh) wrote:
: Wet-Sprocket (shrim@astro.ocis.temple.edu) wrote:
: : Comes here Mz. Patti Johnson with this opinion in the "comp.mail.pine" group in this article on Tue, 3 Jan 1995 19:12:14 GMT:

: :  +   While mailx correctly addresses the "From" field, pine omits the machine 
: :  +   name.  That is, here's the From from the two mailers:

: :  +   mailx:	johnson@micronet.wcu.edu
: :  +   pine:	johnson@wcu.edu

: : We had the same problem, which got fixed by setting this option in Setup/Config:

: : user-domain = <No Value Set>

: This fix does not work for me. When I leave the user domain unset my 
: email to outside sites does not include a domain name which is not very 
: useful. I am using Solaris 2.3 and Pine 3.91.

: The sendmail.cf is the standard one with the bug fix to stop it truncating
: domain names in the From field. This works well with elm.

: -Tim 



From owner-pine-info@cac.washington.edu  Sat Jan  7 11:59:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11706;
	Sat, 7 Jan 95 11:59:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27228;
	Sat, 7 Jan 95 11:57:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27222;
	Sat, 7 Jan 95 11:57:39 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQh7S-00038CC; Sat, 7 Jan 95 11:48 PST
To: pine-info@cac.washington.edu
From: root@whacked.dorm.lsu.edu (Ben Curtis)
Subject: POP
Date: 7 Jan 1995 05:44:28 GMT
Message-Id: <3el9ns$nn@deathstar.cris.com>

	I tried using the POP capability of 3.91 by specifying my INBOX 
as the POP mailbox, but something is screwy.  Until today (one day of 
use) it worked fine, but when I read my mail today, one message had no 
text, and another message was mangled similarly.  I have no clue as to 
the problem, so any suggestions would be greatly appreciated.

--
   __                __  _      _____          _                      
  / /  ______ ______/ /_(_)___ / ___ \________(_)___    _______  __ _ 
 / _ \/ __/ // / __/ __/ /(_-</ / _ `/ __/ __/ /(_-< _ / __/ _ \/  ' \
/_.__/\__/\_,_/_/  \__/_//___/\ \_,_/\__/_/ /_//___/(_)\__/\___/_/_/_/
                               \___/                                  
Linux Lover ... Talker Coder ... Ultimate Player ... Animaniacs Watcher


From owner-pine-info@cac.washington.edu  Sat Jan  7 16:41:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17726;
	Sat, 7 Jan 95 16:41:48 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27391;
	Sat, 7 Jan 95 16:38:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27385;
	Sat, 7 Jan 95 16:38:27 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQlSA-00038KC; Sat, 7 Jan 95 16:25 PST
To: pine-info@cac.washington.edu
From: jhallen@world.std.com (Joseph H Allen)
Subject: JOE 2.4 - Now with SuperPico mode
Message-Id: <D224M0.HAo@world.std.com>
Date: Sat, 7 Jan 1995 22:46:48 GMT

Version 2.4 of my editor is ready.  You can get it by anonymous ftp from
ftp.std.com, file: src/editors/joe2.4.tar.Z.  It probably will not appear
until the sysop comes in on monday, however.

This upstart uEMACS hack of an editor has been stealing too many of my
customers, so I've decided to fight back.  This version of JOE includes
'JPICO'- a greatly enhanced version of Pico (perhaps I should have called it
Nano or Micro?).  It includes all of the missing functions from Pico (such
as go to beginning of file and overtype mode), and generally extends the
editor while keeping reasonably close to the simple model it provides.  It
should be especially useful for editing News and mail articles since the
paragraph formatter can properly format quoted news articles.  Also JOE
normally can display the line and column number on the status line, allows
you to set the right-margin and has many other user-friendly features.

Here are the two help screens for JPICO to give you an idea of what you get:

^[ means you hit Ctrl-[ or the ESC key

CURSOR           GO TO            BLOCK      DELETE    MISC         EXIT
^B left ^F right ^[Y top of file  ^@  mark   ^D  char  ^J   format  ^X save
^P up   ^N down  ^[V end of file  ^K  cut    ^K  line  ^T   spell   ^C abort
^Y prev. screen  ^A  beg. of line ^U  paste  ^[K >line ^[T  file    ^Z shell
^V next screen   ^E  end of line  ^[U select ^[H word< ^L   refresh FILE
^[B prev. word   ^[L line No.     ^O  save   ^[D >word ^[^[ options ^O save
^[F next word    ^W  find text    ^[/ filter ^[- undo  ^[=  redo    ^R insert

MACROS         WINDOW          WINDOW     SHELL         MISC
^[( 0-9 Record ^[O Split       ^[I Grow   ^[! Command   ^[X Execute command
^[)     Stop   ^[E Edit file   ^[J Shrink ^[W Window    ^[M Math
^[ 0-9  Play   ^[P Goto prev.  QUOTE      I-SEARCH      ^[C Center line
^[?     Query  ^[N Goto next   `  Ctrl-   ^[R Backwards ^[G to matching ( [ {
^[\     Repeat ^[Z Zoom in/out ^\ Meta-   ^[S Forwards  ^[< ^[> pan left/rght

This version of JOE also includes a number of improvements and bug fixes:

You can set the JOETERM environment variable to have JOE use a different
terminal type then that specified in the normal TERM environment variable.
You may want to do this since JOE can usually handle the terminal better
than other programs- for example 'rn' messes up my Xenix console if I let it
use inverse and underline, but joe doesn't.

If JOE can't find the specified termcap or terminfo entry it uses a default
extended ansi terminal type instead of giving up.  This should be useful
with the above option since many terminal emulators and PC UNIX consoles
are ansi with insert and delete line, but many terminfo and termcap
databases only provide primitive ansi or vt100.

If you compile joe for terminfo, it includes the termcap routines anyway,
and searches the termcap database (if it exists) if no terminfo entry can be
found.

JOE now starts out in read only mode if the specified file can not be
written to.

If JOE can't make a backup file, it now asks if it should save the file
anyway.

The IDLEOUT compile option is eliminated.  Instead, if the user specified
'-' on the command line, joe will use /dev/tty to open the terminal instead
of stdin/stdout.

More status line options are now available:
  The ASCII decimal and hex values of the character under the cursor
  The number of lines in the file
  What percent of the file the cursor is at
  The current byte offset into the file
  Whether rectangular block mode is enabled
  If the file is read only

A number of glitches in the 'jstar' keymap are fixed.

-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}


From owner-pine-info@cac.washington.edu  Sat Jan  7 23:33:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24764;
	Sat, 7 Jan 95 23:33:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05650;
	Sat, 7 Jan 95 23:27:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05644;
	Sat, 7 Jan 95 23:27:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQrqU-00038CC; Sat, 7 Jan 95 23:15 PST
To: pine-info@cac.washington.edu
From: Eric.Beaudoin@dmr.ca (Eric Beaudoin)
Subject: Re: Limit on ratio of new to included text in news postings?
Date: Sat, 07 Jan 1995 22:25:50 -0500
Message-Id: <Eric.Beaudoin-0701952225500001@slip140.mtl.dmr.ca>
References: <Pine.A32.3.91.950106181753.55663C-100000@umabnet.ab.umd.edu>

In article <Pine.A32.3.91.950106181753.55663C-100000@umabnet.ab.umd.edu>,
UMABnet Help Account <help@umabnet.ab.umd.edu> wrote:

> Greetings.  I got this message from one of our users:
> 
> > Whenever I reply to a message in Usenet, and save the message, I get an
> > error "441, more text than new" or something like that.  Do you know what
> > that is and how to correct it?  I would like to be able to reply to these
> > messages (by including parts of the original message for ease of reading).
> 
> I assume the software is checking for some appropriate ratio of new text
> to included text in a follow-up to a newsgroup post.  I tested this out on
> our system, incrementally adding to the new text and deleting from the 
> included text.  I was still getting this error 441 quite a bit after 
> I, a seasoned reader of news, felt that the ratio of new to included text 
> was appropriate.
> 
> Can anyone tell me:
> 
> 1. Is it Pine, or some other bit of software called by Pine, that is 
> generating this message?

It is usualy the transport program that check this. This means INN,
C-News, NNTP or wathever your site use.

> 2. How does whatever-it-is calculate the appropriate ratio?

With INN, it check the number of lines witch begin with a ">" (a) and the
number of lines witch doesn't (b). If a is greater than b, you got the
error. To avoid this you can change the ">" for another symbol, add empty
lines to your answer or have a very big .sig. Note that the last two
suggestions go far agains proper Netiquette ;-).
 
> 3. Is the some way to tweak the formula, or turn the checking off entirely?
> (The latter might be preferable, as it would disallow "Ditto." posts, 
> which would be fine by me.)

Again with INN (I presume it's the same thing with others) you can
recompile the program with this option off. You sould ask your news
administrator.

Best
______________________________________________________________________________
Eric Beaudoin   <mailto:Eric.Beaudoin@DMR.CA> |  Mes opignions sont miennes et
Groupe DMR Inc. (514) 877-3301                |   peuvent devenir les votres.


From owner-pine-info@cac.washington.edu  Sun Jan  8 05:32:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02006;
	Sun, 8 Jan 95 05:32:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06615;
	Sun, 8 Jan 95 05:19:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06609;
	Sun, 8 Jan 95 05:19:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQxMh-00038CC; Sun, 8 Jan 95 05:08 PST
To: pine-info@cac.washington.edu
From: jhallen@world.std.com (Joseph H Allen)
Subject: Re: JOE 2.4 - Now with SuperPico mode
Message-Id: <D238Is.8vG@world.std.com>
References: <D224M0.HAo@world.std.com>
Date: Sun, 8 Jan 1995 13:08:52 GMT

In article <D224M0.HAo@world.std.com>,
Joseph H Allen <jhallen@world.std.com> wrote:
>Version 2.4 of my editor is ready.  You can get it by anonymous ftp from
>ftp.std.com, file: src/editors/joe2.4.tar.Z.  It probably will not appear
>until the sysop comes in on monday, however.

Please wait for version 2.5 to appear.  Version 2.4 has a minor bug which
prevents you from creating new files.

-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}


From owner-pine-info@cac.washington.edu  Sun Jan  8 07:24:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03760;
	Sun, 8 Jan 95 07:24:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11202;
	Sun, 8 Jan 95 07:20:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11196;
	Sun, 8 Jan 95 07:20:05 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rQzFi-00038CC; Sun, 8 Jan 95 07:09 PST
To: pine-info@cac.washington.edu
From: tbear@calon.com (tbear)
Subject: printer 
Message-Id: <D23CtH.E76@nbn.com>
Date: Sun, 8 Jan 1995 14:41:41 GMT


Help I have a problem with my printer using pine. I have a IBM PS/2 Model 
30 with mcga screen. My printer is an Epson Action Printer 2250. When I 
tell the pine to use ansi to ansi and then ask it to print what is in my 
mail box I get nothing to print. I am not very good at computers but I do 
understand the basics. Could anyone help with my problem.

Thank you in advance,

Tbear


From owner-pine-info@cac.washington.edu  Sun Jan  8 08:41:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04912;
	Sun, 8 Jan 95 08:41:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12038;
	Sun, 8 Jan 95 08:35:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12032;
	Sun, 8 Jan 95 08:35:15 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR0PE-00038JC; Sun, 8 Jan 95 08:23 PST
To: pine-info@cac.washington.edu
From: The Shrim Dude! <shrim@astro.ocis.temple.edu>
Subject: Test Ignore
Date: Sun, 8 Jan 1995 10:49:50 -0500 (EST)
Message-Id: <Pine.BSD.3.90.950108104628.3280A-100000@astro.ocis.temple.edu>
References: <3ep130$l5a@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3ep130$l5a@cronkite.ocis.temple.edu> 

Million apologies to post a Test message to c.m.p
But this is a test to see if the Followup-To
header works.

PS: btw is there something wrong with Pine Mail-to-News gateway ?

--
.---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________



From owner-pine-info@cac.washington.edu  Sun Jan  8 08:41:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04914;
	Sun, 8 Jan 95 08:41:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08786;
	Sun, 8 Jan 95 08:35:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08780;
	Sun, 8 Jan 95 08:35:12 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR0P8-00038CC; Sun, 8 Jan 95 08:23 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Setting Followup-To header
Date: 8 Jan 1995 15:41:20 GMT
Message-Id: <3ep130$l5a@cronkite.ocis.temple.edu>

Piners,

I have added a "Followup-To" header in my customized-hdrs option.
When I post to a newsgroup, I can set the followups to go to another
newsgroup by simply typing that newsgroups name at the Followup-To:
header. It accepts the value, so far so good the article gets posted.

Then I want to Reply to this post to see if this actually works from
Pine. Nope, it takes the value in Newsgrps: header but not the other.

But when I use Tin to reply to this post, it warns me that the followups
are re-directed to another newsgroup and the newsgroup name.

Question is why does Pine ignore my Followup-To header while Tin doesn't?

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Sun Jan  8 10:20:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06722;
	Sun, 8 Jan 95 10:20:33 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13270;
	Sun, 8 Jan 95 10:17:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from opus.csd.uwm.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13264;
	Sun, 8 Jan 95 10:17:06 -0800
Received: from localhost (dave@localhost) by opus.csd.uwm.edu (8.6.4/8.6.4) id MAA04024 for pine-info@cac.washington.edu; Sun, 8 Jan 1995 12:17:05 -0600
Date: Sun, 8 Jan 1995 12:17:05 -0600
From: Dave Rasmussen <dave@opus.csd.uwm.edu>
Message-Id: <199501081817.MAA04024@opus.csd.uwm.edu>
To: pine-info@cac.washington.edu
Subject: pine on usl svr4

Does anyone have pine running on this platform and if so could you
send me diffs or let me know how to get the source? thx!


From owner-pine-info@cac.washington.edu  Sun Jan  8 10:52:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07433;
	Sun, 8 Jan 95 10:52:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10274;
	Sun, 8 Jan 95 10:44:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10268;
	Sun, 8 Jan 95 10:44:13 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR2Ro-00038CC; Sun, 8 Jan 95 10:34 PST
To: pine-info@cac.washington.edu
From: mmead@goof.com (matthew c. mead)
Subject: PGP mail with pine
Date: 8 Jan 1995 18:34:34 GMT
Message-Id: <3epb7q$o0v@solaris.cc.vt.edu>



	I've been using perl scripts for PGP mail in elm for a while, and I've
been told by a friend of mine that pine has PGP support built it.  Is this
true?  If not, what mechanism is used to achieve the encryption and decryption?
Also, where can I find it ... thanks for any help!




-matt


-- 
Matthew C. Mead -- System/Network Administration, User Support, Software Devel.
Virginia Tech Center for Transportation Research
Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com
WWW: http://www.goof.com:/~mmead


From owner-pine-info@cac.washington.edu  Sun Jan  8 11:04:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07643;
	Sun, 8 Jan 95 11:04:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13795;
	Sun, 8 Jan 95 10:59:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13789;
	Sun, 8 Jan 95 10:59:17 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR2gq-00038JC; Sun, 8 Jan 95 10:50 PST
To: pine-info@cac.washington.edu
From: poyner@primenet.com (Brandon Lee Poyner)
Subject: pine 3.90 eating CPU on exit
Date: 8 Jan 1995 18:49:05 GMT
Message-Id: <3epc31$d43@news.primenet.com>

My internet provider uses pine 3.90 running on BSDI.  Every time I exit  
pine, it just hangs.  It would hang as long as it could, except that i 
terminate it with a interupt (^C)

I have pine aliased to 'pine -d 0 -i -z' .. so that I don't get debug 
information (-d 0), initially i go into the incoming folder (-i) and I 
want it to respond to control-z (-z)

I just logged in twice (via PPP) to see what's happening, and did a 
'ps ugx' upon my attempt to exit pine.  Here's what I got...

USER       PID %CPU %MEM   VSZ  RSS TT  STAT STARTED       TIME COMMAND
poyner   29541 82.8  0.0  1196  584 pe  R+   11:09PM    0:56.21 pine 0
poyner   29458  0.0  0.0   572  460 q2  Ss   11:08PM    0:00.68 -bash (bash)
poyner   29430  0.0  0.0   572  468 pe  Is   11:08PM    0:00.52 -bash (bash)
poyner   29681  0.0  0.0   272  200 q2  R+   11:11PM    0:00.03 ps -ugx

I believe it's the -d 0 option that causes this, but to have one process 
eating 82% CPU really isn't good for the system.  

I've also used an older (i believe) version of pine and not had this problem 
with the same command line, but that was also on Ultrix.

Anybody know what causes this?  Thanks.

  ____________________________________________________________ ______________
 )_/~~~~~\____/~~~\___/~~~~~\___/~~\/~~\____/~~~~\___/~~~~\___| poyner@      (
(__/~\ /~~\__/~\ /~\__/~\   ___/~\/~~\/~\__/~\  /~\__/~\  /~\_|  primenet.com )
 )_/~\_/~~\__/~~~~~\__/~~~~~\__/~\____/~\__/~\__/~\__/~\__/~\_:--------------(
(__/~\_/~~\__/~\ /~\__/~\   ___/~\____/~\__/~\__/~\__/~\__/~\_| http://www.   )
 )_/~~~~~\___/~\_/~\__/~~~~~\__/~\____/~\___/~~~~\___/~\__/~\_| primenet.com (
(___------____-___-____-----____-______-_____----_____-____-__| /~poyner/     )
 )-----------------------------------------------------------~---------------(
( Price does not include tacks? TACKS? I don't want TACKS in my food! oh, tax )
 `---------------------------------------------------------------------------'


From owner-pine-info@cac.washington.edu  Sun Jan  8 13:26:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10260;
	Sun, 8 Jan 95 13:26:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12088;
	Sun, 8 Jan 95 13:20:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12076;
	Sun, 8 Jan 95 13:20:49 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR4rE-00038CC; Sun, 8 Jan 95 13:09 PST
To: pine-info@cac.washington.edu
From: guojin@iss.nus.sg (Guo Jin)
Subject: [?] pine & ispell
Date: 8 Jan 1995 03:48:52 GMT
Message-Id: <3ennb4$46s@holodeck.iss.nus.sg>

Hi, there,

Is there a way to use ispell together with pine/pico?

And, is there a "standard" API for spell checkers which can provide
candidate suggestions?

Thanks.

GuoJin



From owner-pine-info@cac.washington.edu  Sun Jan  8 13:31:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10347;
	Sun, 8 Jan 95 13:31:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15557;
	Sun, 8 Jan 95 13:24:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15551;
	Sun, 8 Jan 95 13:24:36 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR4yn-00038JC; Sun, 8 Jan 95 13:16 PST
To: pine-info@cac.washington.edu
From: "J. Kelly Cunningham" <deviate@lipschitz>
Subject: Re: Using Pine to post to newsgroups 
Message-Id: <Pine.NXT.3.91.950106215116.28245C-100000@lipschitz>
Date: Fri, 6 Jan 1995 21:54:05 -0600
References: <3eikss$73k@nkosi.well.com> 
In-Reply-To: <3eikss$73k@nkosi.well.com> 
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

-----BEGIN PGP SIGNED MESSAGE-----

On 6 Jan 1995, Charles H. Hubbell wrote:

   How does one perform that operation?
   
                             Chuck Hubbell
   
Hit "r" or "c".   
   


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBLw274eBu0383Om6dAQFD3AQAoZA4t4onwK7FVyQ3hK6ksKyNvNOr52KM
VsJ88WpXaciDqcA0lufd6ulLHuTLt2BzDgKgryL83/UVq1P+DmwyHJyO+W+v2ngP
PGzcJ+PWXVpwWIneIhaSuLdwbc9RVmKh0R1+4Ymz8twLn1EPz5KL+fX7UJI6pJnv
B1ebyuBLTdo=
=mxW2
-----END PGP SIGNATURE-----


-- kc       prudence dictates a low profile -- Sandy Sandfort
          finger deviate@lipschitz.sfasu.edu | pgp -fka +force
    finger slutsky@lipschitz.sfasu.edu | pgp -f | tee mkpgp.txt.uu | more


From owner-pine-info@cac.washington.edu  Sun Jan  8 15:37:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12873;
	Sun, 8 Jan 95 15:37:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13783;
	Sun, 8 Jan 95 15:33:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13777;
	Sun, 8 Jan 95 15:33:36 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id PAA13282 for <pine-info@cac.washington.edu>; Sun, 8 Jan 1995 15:33:34 -0800
Date: Sun, 8 Jan 1995 15:33:36 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Guo Jin <guojin@iss.nus.sg>
Cc: pine-info@cac.washington.edu
Subject: Re: [?] pine & ispell
In-Reply-To: <3ennb4$46s@holodeck.iss.nus.sg>
Message-Id: <Pine.SUN.3.91.950108152826.8660A-100000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 8 Jan 1995, Guo Jin wrote:

> Hi, there,
> 
> Is there a way to use ispell together with pine/pico?
> 
> And, is there a "standard" API for spell checkers which can provide
> candidate suggestions?
> 
> Thanks.
> 
> GuoJin
> 
> 

Can you FTP?  If so, you'll find a wealth of infomation (and an answer to 
your specific question) at

  ftp://ftp.cac.washington.edu/pine/docs

If you can www try

   http://www.cac.washington.edo/pine

If you can't, maybe I can dig up the old e-mail and send it to you.

---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646



From owner-pine-info@cac.washington.edu  Sun Jan  8 16:33:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13838;
	Sun, 8 Jan 95 16:33:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14615;
	Sun, 8 Jan 95 16:29:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14609;
	Sun, 8 Jan 95 16:29:54 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR7rt-00038CC; Sun, 8 Jan 95 16:21 PST
To: pine-info@cac.washington.edu
From: scocca@gibbs.oit.unc.edu (D. A. Scocca)
Subject: True Sort of a Mailbox?
Date: 9 Jan 1995 00:15:43 GMT
Message-Id: <3epv7f$19gq@bigblue.oit.unc.edu>

I have a problem in Pine 3.91 (Unix).  


I want to start downloading some of my mail folders.  Unfortunately, I
have not always moved mail into folders in the same order in which I 
received it, although I would like to download files with the messages
in that order.

The sort command seems to sort only the index on the screen, not the 
acutal order of the messages in the file.  Is there any way to change 
this so that it sorts the file itself?

I believe that one work-around is: 
Sort the index
Select all messages
Extract all selected messages into a new file
Download that new file

But I'm wondering if there's a more direct way....

Any hints?

(Please reply by email if possible...)

Thanks...

Dave Scocca
--
* The Minstrel in the Gallery                     "Heteroskedastic"  *
* D. A. Scocca                             scocca@gibbs.oit.unc.edu  *
* "My love does not, cannot _make_ her happy.  My love can only      *
*    release in her the capacity to be happy."     --J. Barnes       *


From owner-pine-info@cac.washington.edu  Sun Jan  8 17:23:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15167;
	Sun, 8 Jan 95 17:23:58 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18803;
	Sun, 8 Jan 95 17:21:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18797;
	Sun, 8 Jan 95 17:21:15 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rR8cy-00038CC; Sun, 8 Jan 95 17:10 PST
To: pine-info@cac.washington.edu
From: Grant Young <young@ucla.edu>
Subject: PC Pine & SLIP
Date: 9 Jan 1995 01:10:29 GMT
Message-Id: <3eq2e5$cqr@saba.info.ucla.edu>

Hello Pine Folks:

I'm truly in need of help.  I want to use the packet version of
PC Pine 3.91 to connect via a SLIP connection to my school's
mail/news system.  I am using the Univ. of Minnesota's UMSLIP.COM
Packet driver for SLIP, version 2.1 and PHONE.EXE to dial into
my school's slip server.  Gopher, Minuet and DosLynx are working
great.  Whenever I try to run Pine, I get an error message stating
that BOOTP failed.  When I manually enter my IP address, gateway,
nameserver, etc., Pine returns a message stating that my INBOX cannot
be opened because the [Host cannot be found].

I can successfully run the packet version of PC Pine with the Crynwr
Packet driver for a 3c509 NIC, version 11.2.  I do not use BOOTP
when I use the Crynwr 3c509 packet driver.

Any thoughts as to what the problem is?

Grant



From owner-pine-info@cac.washington.edu  Sun Jan  8 20:54:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20492;
	Sun, 8 Jan 95 20:54:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18774;
	Sun, 8 Jan 95 20:51:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18768;
	Sun, 8 Jan 95 20:51:35 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRBtm-00038CC; Sun, 8 Jan 95 20:40 PST
To: pine-info@cac.washington.edu
From: entropy@IntNet.net (Jonathan Cooper)
Subject: [ killfile ]
Date: 8 Jan 1995 23:14:25 -0500
Message-Id: <3eqd71$hgt@xcalibur.IntNet.net>

How would I kill all mail that comes from a certain address using
pine itself?  Does pine support killfiles?

Yes, I know I could just make a procmail recipe, but I'd like to
use just pine.

-jon
-- 
( --------[ Jonathan D. Cooper ]--------[ entropy@intnet.net ]-------- )
( PGP 2.6.2 keyprint: 31 50 8F 82 B9 79 ED C4  5B 12 A0 35 E0 9B C0 01 )
( home page: http://taz.hyperreal.com/~entropy/ ]---[ Key-ID: 4082CCB5 )


From owner-pine-info@cac.washington.edu  Sun Jan  8 22:18:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22000;
	Sun, 8 Jan 95 22:18:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22636;
	Sun, 8 Jan 95 22:15:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22630;
	Sun, 8 Jan 95 22:15:25 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRDEY-00038LC; Sun, 8 Jan 95 22:05 PST
To: pine-info@cac.washington.edu
From: dkraemer@crl.com (Dan Kraemer)
Subject: Filtering w/ Procmail Help
Date: 9 Jan 1995 06:03:15 GMT
Message-Id: <3eqjj3$s2h@nntp.crl.com>

I'm using procmail to filter e-mail from a few mailing lists into 
separate folders.  I've recently subscribed to a new mailing list in 
which the headers don't match exactly what I need to make my procmail 
recipes work.  Here's a header of one of the mails:

>From danorton@chsw.win.netSun Jan  8 21:59:55 1995
Date: Sun, 8 Jan 1995 11:53:09 -0600
From: "Daniel A. Norton" <danorton@chsw.win.net>
Reply to: familylaw-l@acc.wuacc.edu
To: dkraemer@crl.com
Subject: Re: Group Therapy, Evidentiar...

What recipe should I use to save this to INFAMILYLAW?   All of the other 
lists I'm on have the To: line which includes the list name... This list 
sends the email to my address with just the Reply to: line having 
familylaw in it...   Can anyone clue me in?

--

-Dan Kraemer
dkraemer@crl.com

"Bad movie?  You're soaking in it!"
	-Crow, _The Giant Gila Monster_, MST3K




From owner-pine-info@cac.washington.edu  Mon Jan  9 02:45:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27336;
	Mon, 9 Jan 95 02:45:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25997;
	Mon, 9 Jan 95 02:40:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25991;
	Mon, 9 Jan 95 02:40:48 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRHOa-00038JC; Mon, 9 Jan 95 02:32 PST
To: pine-info@cac.washington.edu
From: "Keith M. Rainey" <kmr@engr.latech.edu>
Subject: Adding to addressbook
Date: Fri, 6 Jan 1995 17:24:32 -0600
Message-Id: <Pine.SUN.3.91.950106165903.6579A-100000@antares>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


	I use a lot of lists in my addressbook and I am constantly
changing lists, and adding new lists.  Is there a way to append a
text file of addresses into the .addressbook file?  It would make 
my life a little easier (since I'm so lazy).  Also, is there a
way to send address lists to other users without them having to 
type in all of the names?

	Any help would be greatly appreciated.  Thank you.

Keith M. Rainey
Louisiana Tech University
Biomedical Engineering
kmr@engr.latech.edu



From owner-pine-info@cac.washington.edu  Mon Jan  9 02:48:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27381;
	Mon, 9 Jan 95 02:48:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22950;
	Mon, 9 Jan 95 02:40:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22944;
	Mon, 9 Jan 95 02:40:46 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRHM4-00038KC; Mon, 9 Jan 95 02:29 PST
To: pine-info@cac.washington.edu
From: harle@venus.usna.navy.mil (Mr. Jim Harle (CSERV STAFF))
Subject: Re: Address book tools
Message-Id: <D24txJ.7Ky@usna.navy.mil>
References: <Pine.BSI.3.91.950104113141.27761B-100000@recepsen.aa.msen.com> <3eg0ni$frq@cmcl2.NYU.EDU>
Date: Mon, 9 Jan 1995 09:48:54 GMT

We have been using a link to ph from pine for a while now.  Its useful as-is,
but I wanted to do some work on it before I sent it to the folks at Univ
of Washington.  There are a few bugs when names aren't found and more
than one submission on the "To:" line.  Feel free to Email me if you want
the code anyway.

Tim O'Connor (oconnort@acf2.nyu.edu) wrote:
: Edward Vielmetti (emv@recepsen.aa.msen.com) wrote:

: > - an interface to finger, whois, or some other directory service
: >   so that you can look people up

: Yes, today we were talking about the possibility of doing ph lookups 
: from within Pine 3.91, since we're running a ph server in production 
: now.  

: I said I'd browse through the archives at the uwashington ftp site to 
: see if the topic had been raised, but (as often happens) I didn't need 
: to look any further than this newsgroup.

: Many thanks for the timely discussion!

: --tim o'connor

: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
: Tim O'Connor                                        tim.oconnor@nyu.edu
: NYU Academic Computing Facility                   Phone: (212) 998-3024
: 251 Mercer St., New York, NY 10012                  Fax: (212) 995-4120


From owner-pine-info@cac.washington.edu  Mon Jan  9 07:50:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04537;
	Mon, 9 Jan 95 07:50:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27005;
	Mon, 9 Jan 95 07:41:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26999;
	Mon, 9 Jan 95 07:41:16 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRLzI-00038KC; Mon, 9 Jan 95 07:26 PST
To: pine-info@cac.washington.edu
From: Hank Burchard <burchard@twp.com>
Subject: ddoouubbllee lleetteerrss
Date: Mon, 9 Jan 1995 10:24:43 -0500
Message-Id: <Pine.SUN.3.91.950109102023.10086D-100000@twp.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


     Every once in a while, in the midst of composing a message, I start 
getting doubled letters on my screen (as in the subject line above). It 
seems to happen at random and often clears up in a moment or two, but 
sometimes I have to sign off and then dial up again to get it to stop. 
It's not an improper echo setting, which is all I get from the faq.  Any 
technowhizzes out there have a solution?
     Thanx in advance....

+ + + + +

Hank Burchard * Weekend Section * The Washington Post
1150 15th Street NW * Washington DC USA 20071-0001
VoiceMail (202) 334-7243 * Email: burchard@twp.com



From owner-pine-info@cac.washington.edu  Mon Jan  9 09:06:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07840;
	Mon, 9 Jan 95 09:06:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01592;
	Mon, 9 Jan 95 08:52:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01586;
	Mon, 9 Jan 95 08:52:39 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRNAv-00038KC; Mon, 9 Jan 95 08:42 PST
To: pine-info@cac.washington.edu
From: Philip Nelson <nelsonp@uwgb.edu>
Subject: Winsock Pine lockups
Date: 9 Jan 1995 16:35:23 GMT
Message-Id: <3erokb$er5@athena.athenet.net>

Has anyone else had problems with lockups in Winsock Pine 3.91?
It seems that when various network operations take place that
pine will not be able to finish it's current operation but will
not time out either.  Examples are selecting an invalid newsgroup 
or server.  Also if I leave Pine minimized for part of a day it
will alway be hung.  When it's hung the menus will still operate
though some will be grayed including exit, no keys will work and 
quitting windows gives the error saying that the network was in use
and windows tried to restore it to it's previous state but rebooting
may be required.  I am using Pathworks 5.1 for my TCP/IP and winsock.


From owner-pine-info@cac.washington.edu  Mon Jan  9 09:59:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10588;
	Mon, 9 Jan 95 09:59:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02913;
	Mon, 9 Jan 95 09:47:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from calafia.uabcs.mx by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02907;
	Mon, 9 Jan 95 09:47:21 -0800
Received: by calafia.uabcs.mx (AIX 3.2/UCB 5.64/4.03)
          id AA07817; Mon, 9 Jan 1995 09:46:23 -0600
Date: Mon, 9 Jan 1995 09:46:23 -0600 (CST)
From: Thomas Hucke <hucke@calafia.uabcs.mx>
Reply-To: Thomas Hucke <hucke@calafia.uabcs.mx>
Subject: Don't get pcpine_f running..HELP
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.88.9501061614.A9694-0100000@calafia.uabcs.mx>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

I need help from a PC-PINE specialist!! 

We are running PC-PINE 3.89 and FTP PCTCP 2.20 without problems. But after
installing PCPINE 3.91 over version 3.89 and trying to send mail I get
always the message: Error connecting to mail server.  Then I installed
PCPINE 3.91 from the scratch. I start PCPINE and I can send mail. I leave
the program and start again PCPINE. But I cannot send mail a second time,
always I receive the message: Error connecting to mail server:. I return
to PCPINE 3.89 and everything works fine. 

What's going on ? Has PC-PINE for FTP PCTCP a bug or do I have to upgrade
some files ? 

Somebody told me, I have to take ODIPKT 3.0. But why does v.89 work fine
and v.91 doesn't ? Several times I send a report to
pine@cac.washington.edu, but nothing. 

Can anybody help me ?
TIA, Thomas Hucke 

Universidad Autonoma de Baja California Sur / Mexico

hucke@calafia.uabcs.mx




From owner-pine-info@cac.washington.edu  Mon Jan  9 10:14:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11620;
	Mon, 9 Jan 95 10:14:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03349;
	Mon, 9 Jan 95 10:03:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from weber.ucsd.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03343;
	Mon, 9 Jan 95 10:03:33 -0800
Received: from localhost (corrigan@localhost [127.0.0.1]) by weber.ucsd.edu (8.6.9/8.6.9) with ESMTP id KAA27024; Mon, 9 Jan 1995 10:03:30 -0800
Message-Id: <199501091803.KAA27024@weber.ucsd.edu>
To: dkraemer@crl.com (Dan Kraemer)
Cc: pine-info@cac.washington.edu
Reply-To: pine-info@cac.washington.edu
Subject: Re: Filtering w/ Procmail Help 
In-Reply-To: Your message of "09 Jan 1995 06:03:15 +0000."
             <3eqjj3$s2h@nntp.crl.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Id: <27020.789674610.1@weber.ucsd.edu>
Date: Mon, 09 Jan 1995 10:03:30 -0800
From: "Michael J. Corrigan" <corrigan@ucsd.edu>

:0:
*^Reply to: familylaw-l@acc.wuacc.edu
INFAMILYLAW


> I'm using procmail to filter e-mail from a few mailing lists into 
> separate folders.  I've recently subscribed to a new mailing list in 
> which the headers don't match exactly what I need to make my procmail 
> recipes work.  Here's a header of one of the mails:
> 
> From danorton@chsw.win.netSun Jan  8 21:59:55 1995
> Date: Sun, 8 Jan 1995 11:53:09 -0600
> From: "Daniel A. Norton" <danorton@chsw.win.net>
> Reply to: familylaw-l@acc.wuacc.edu
> To: dkraemer@crl.com
> Subject: Re: Group Therapy, Evidentiar...
> 
> What recipe should I use to save this to INFAMILYLAW?   All of the other 
> lists I'm on have the To: line which includes the list name... This list 
> sends the email to my address with just the Reply to: line having 
> familylaw in it...   Can anyone clue me in?
> 
> --
> 
> -Dan Kraemer
> dkraemer@crl.com
> 
> "Bad movie?  You're soaking in it!"
> 	-Crow, _The Giant Gila Monster_, MST3K
> 
> 


From owner-pine-info@cac.washington.edu  Mon Jan  9 10:27:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12361;
	Mon, 9 Jan 95 10:27:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00869;
	Mon, 9 Jan 95 10:20:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from calafia.uabcs.mx by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00863;
	Mon, 9 Jan 95 10:20:41 -0800
Received: by calafia.uabcs.mx (AIX 3.2/UCB 5.64/4.03)
          id AA09655; Mon, 9 Jan 1995 10:19:53 -0600
Date: Mon, 9 Jan 1995 10:19:52 -0600 (CST)
From: Thomas Hucke <hucke@calafia.uabcs.mx>
Subject: 
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.88.9501091021.A9139-0100000@calafia.uabcs.mx>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

set pine-info mail




From owner-pine-info@cac.washington.edu  Mon Jan  9 10:44:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13783;
	Mon, 9 Jan 95 10:44:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01378;
	Mon, 9 Jan 95 10:38:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01372;
	Mon, 9 Jan 95 10:38:56 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14051;
	Mon, 9 Jan 95 10:38:55 -0800
Date: Wed, 28 Dec 1994 12:06:07 -0800 (PST)
From: rich hurley <rhurley@teleport.com>
To: pine@cac.washington.edu
Subject: Altos system 5 version
Message-Id: <Pine.SUN.3.91.941228120424.27074A-100000@elaine.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-Date: Mon, 9 Jan 1995 10:38:52 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950109103852.2851F@shiva1.cac.washington.edu>

I work at a UNIX Var and we are now using pine on sco based machines.  My 
question is do you have a version of pine that can be compiled and 
executed on an Altos 386 box, running Altos Unix System V?

Any help is appreciated...

rhurley@teleport.com
rah@masi.com


rhurley@teleport.COM  Public Access User --- Not affiliated with Teleport
Public Access UNIX and Internet at (503) 220-1016 (2400-14400, N81)



From owner-pine-info@cac.washington.edu  Mon Jan  9 11:07:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15684;
	Mon, 9 Jan 95 11:07:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04875;
	Mon, 9 Jan 95 11:01:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from cv4.chem.purdue.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04869;
	Mon, 9 Jan 95 11:01:19 -0800
Received: by cv4.chem.purdue.edu (931110.SGI.ANONFTP/931108.SGI.ANONFTP)
	for pine-info@cac.washington.edu id AA18795; Mon, 9 Jan 95 14:02:10 -0500
Date: Mon, 9 Jan 95 14:02:10 -0500
From: lev@cv4.chem.purdue.edu (Lev A. Gorenstein)
Message-Id: <9501091902.AA18795@cv4.chem.purdue.edu>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu

Guys, 

Shame on you!  I understand that you're busy because people are sending 
you bullshit questions (and the amount of bullshit is much more than the 
amount of gold in it).  But still, what you've done is, well, let's say
"impolite", though some other words are on the tip of my tongue.  I 
received the AUTOMATED answer from you A WEEK (!!!) after I sent you my 
bug report!  If you use the program to automatically fetch the standard 
text as a reply-acknoledgement of receiving a report, than it shouldn't 
take A WEEK to send acknoledgement!  And if I'm wrong and you read my 
report, and than sent me this formal crap that "people are asking us 
about IRC, talk chat, disk space..." (and there was nothing about it in
my mail)...  Well, if so, than I have no words...  This is not the 
civilized way of treating people:  first you ask "Please, send us bug 
reports, we will greatly appreciate it!", and than you just pee at those 
who did answer to your soliciting and send you a letter about improving 
YOUR server.   Damn, I expect apologees!

Hope that I won't get the same text about "no disk space on your host",
etc. again.


____________________________________________
  Lev A. Gorenstein
  Chemistry Department
  Purdue University
  W.Lafayette, IN 47907, USA
  (317)494-5289; Fax (317)494-0239
  lev@chem.purdue.edu



From owner-pine-info@cac.washington.edu  Mon Jan  9 11:21:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16799;
	Mon, 9 Jan 95 11:21:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02426;
	Mon, 9 Jan 95 11:17:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from atc.boeing.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02420;
	Mon, 9 Jan 95 11:17:33 -0800
Received: by atc.boeing.com (5.57) 
	id AA03286; Mon, 9 Jan 95 11:21:22 -0800
Received: from bcstec.ca.boeing.com by splinter.boeing.com with SMTP
	(1.37.109.14/16.2) id AA219529001; Mon, 9 Jan 1995 11:16:41 -0800
Received: by bcstec.ca.boeing.com (4.1/SMI-4.1)
	id AA01533; Mon, 9 Jan 95 11:17:08 PST
Date: Mon, 9 Jan 1995 11:17:07 -0800 (PST)
From: Rick Scott <kf7qz@bcstec.ca.boeing.com>
Subject: Re: FTP for Pine
To: Knute Snortum <knute@teleport.com>
Cc: pine-info@cac.washington.edu
In-Reply-To: <Pine.SUN.3.91.950106175715.24772B@linda.teleport.com>
Message-Id: <Pine.3.89.9501091130.B1242-0100000@bcstec>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Fri, 6 Jan 1995, Knute Snortum wrote:

> 
> Boy, people are really nervous about getting flamed these days.  It's 
> okay; we're all friendly here.

You got that right ... seems everybody who thinks thier and internet cop 
will drop a flame on you in a heartbeat.   

> I believe you can FPT right into cac.washington.edu and get the latest 

She just emailed me on it and gave me the full route ... thanks for the help


| Ricky Scott                     |        All Comments (unfortunately) |
| kf7qz@bectec.ca.boeing.com      |        are purely my own and do not |
| kf7qz@prostar.com               |        reflect the views nor are    |
|                                 |        supported by my employer     |



From owner-pine-info@cac.washington.edu  Mon Jan  9 11:35:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17847;
	Mon, 9 Jan 95 11:35:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02808;
	Mon, 9 Jan 95 11:31:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ds1.gl.umbc.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02802;
	Mon, 9 Jan 95 11:31:02 -0800
Received: from umbc8.umbc.edu (stoppe1@f-umbc8.umbc.edu [130.85.3.8]) by ds1.gl.umbc.edu (8.6.9/8.6.9) with ESMTP id OAA15309 for <pine-info@cac.washington.edu>; Mon, 9 Jan 1995 14:31:01 -0500
Received: (stoppe1@localhost) by umbc8.umbc.edu (8.6.9/8.6.9) id OAA24930; Mon, 9 Jan 1995 14:31:00 -0500
Date: Mon, 9 Jan 1995 14:31:00 -0500
From: Avi Golden <stoppe1@gl.umbc.edu>
X-Sender: stoppe1@umbc8.umbc.edu
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: not a bug report, a request
In-Reply-To: <Pine.ULT.3.92.950109112729.2851B-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SGI.3.90.950109143024.20682E-100000@umbc8.umbc.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

sure, FAQ me.

avi

   ******************** Can anyone say, "Oslo Accords"? ******************


Rule #76 of the Ferengi Rules of Acquisition:

  Every once in a while, declare peace. It confuses the hell out of your 
  enemies.
					- Quark



From owner-pine-info@cac.washington.edu  Mon Jan  9 12:09:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20757;
	Mon, 9 Jan 95 12:09:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03882;
	Mon, 9 Jan 95 12:05:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ssi.edc.org by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03858;
	Mon, 9 Jan 95 12:05:05 -0800
Received: from ssi.edc.org by ssi.edc.org id aa19433; 9 Jan 95 15:03 EST
Date: Mon, 9 Jan 1995 15:03:32 -0500 (EST)
From: Gunther Anderson <gunther@ssi.edc.org>
To: Pine Information List <pine-info@cac.washington.edu>
Cc: "Carol J. Fox" <cfox@sinnfree.sinnfree.org>,
        Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID JX1YQ): Trying to Solve a Two Problems
In-Reply-To: <Pine.ULT.3.92.950109114345.2851U-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SCO.3.91.950109145719.16852C-100000@ssi.edc.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> On Tue, 3 Jan 1995, Carol J. Fox wrote:
> 
> > Subject: Bug (ID JX1YQ): Trying to Solve a Two Problems
> > 
> > 
> > We have a user on our freenet who is telling us that the L (Folder) 
> > section locks up on her when she tries to use PINE.  She can get no 
> > further.  None of our other users have complained.  She thinks the 
> > problem is on our end because it happens whenever she logs in from any 
> > computer on her network but to noone else who logs in from her network.  
> > We think its on her end because no one else is having the same problem.  
> > Can you shed any light on this?

You might try, from the root account (so you don't have to know her 
password), logging into her account and checking this phenomenon from your 
own controlled environment.  However, my first thought is to check the 
filenames in her mail/ direcory for illegal characters.  If she managed 
to create a folder whose name involves a strategic set of illegal 
characters (^S comes to mind), it could stop her connection immediately 
upon an attempt to display it.

> > Another user has his main email account on Delphi and would like PINE on 
> > our system to automatically send his email on our system to his Delphi 
> > account.  Is this possible?

No, that's not what Pine does.  You will want to look into message 
forwarding at the transport level.  Look into .forward (or .maildelivery 
if you're using MMDF) files on your system, or talk to the administrator 
about putting an entry in the system aliases file to automatically 
redirect incoming messages.  But Pine only reads messages once they're in 
the mailbox, and it only does that when it's told to.  It won't do any 
automatic processing when no one's logged in, and it can't touch mail 
until its already been delivered.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Mon Jan  9 12:51:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22836;
	Mon, 9 Jan 95 12:51:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07872;
	Mon, 9 Jan 95 12:47:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from San-A.grbb.polymtl.ca by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07863;
	Mon, 9 Jan 95 12:47:36 -0800
Received: by grbb.polymtl.ca  (930420.SGI)
	for pine-info@cac.washington.edu id AA17978; Mon, 9 Jan 95 15:50:32 -0500
Date: Mon, 9 Jan 1995 15:50:31 -0500 (EST)
From: Gildas PERROT <perrot@grbb.polymtl.ca>
X-Sender: perrot@San-A
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Bug (ID J907O): New suggestion 
In-Reply-To: <Pine.ULT.3.92.950109124429.2851K-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SGI.3.91.950109155004.17652E-100000@San-A>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I would like the latest FAQ about Pine.

Thanks in advance.		Gildas.

# Gildas PERROT, Associe de recherche # Ecole Polytechnique          
# Institut de Genie Biomedical        # C.P. 6079, Succ. Centre-Ville    __o
# e-mail: perrot@grbb.polymtl.ca      # Montreal H3C3A7, Canada   ------ \<,
# Tel: (514) 340-4184                 # Fax: (514) 340-4611    ------ (*)/ (*)

             





From owner-pine-info@cac.washington.edu  Mon Jan  9 13:03:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23702;
	Mon, 9 Jan 95 13:03:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08087;
	Mon, 9 Jan 95 12:57:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from sun1.wwb.noaa.gov by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08081;
	Mon, 9 Jan 95 12:57:10 -0800
Received: Mon, 9 Jan 95 15:57:07 EST from sgi11.wwb.noaa.gov by sun1.wwb.noaa.gov (4.1/1.5)
Received: by sgi11.wwb.noaa.gov (920110.SGI/890607.SGI)
	(for @sun1.wwb.noaa.gov:pine-info@cac.washington.edu) id AA17546; Mon, 9 Jan 95 15:57:03 -0500
Date: Mon, 9 Jan 1995 15:46:00 -0500 (EST)
From: Richard Reynolds <wd01rr@sgi11.wwb.noaa.gov>
Subject: Re: New Version
To: Pine Information List <pine-info@cac.washington.edu>
In-Reply-To: <Pine.ULT.3.92.950109113120.2851I-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.3.07.9501091555.A17517-d100000@sgi11.wwb.noaa.gov>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am a disappointed in your response.  I have looked through your
ftp and www tools.  Other than wishing to give you a pat on the back for
pine, I really have just one request. 

IS THERE A MORE RECENT VERSION OF PINE THAT RUNS ON A SILICON GRAPHICS
MACHINE?   If so where is it in your anonymous ftp account.  


On Mon, 9 Jan 1995, David L Miller wrote:

> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Tue, 3 Jan 1995, Richard Reynolds wrote:
> 
> > Date: Tue, 3 Jan 1995 09:00:04 -0500 (EST)
> > From: Richard Reynolds <wd01rr@sgi11.wwb.noaa.gov>
> > To: pine@cac.washington.edu
> > Subject: New Version
> > 
> > I have just discovered pine is on our unix system. I am delighted 
> > with it.  However, as with all users, there are a few things I would
> > like to change.
> > 
> > 1)  When I paste into it with my mouse, the text is justifed.  This is
> > not done correctly and the blocking for the rest of the file is destroyed.
> > I would like to be able to turn the justify off!
> > 
> > 2)  I wish I could define some special keys.  For instance, I would define
> > page up and page down to be ^V and ^Y.
> > 
> > 3)  I wish the mouse worked!
> > 
> > I suspect some of thse problems might be fixed in your latest version. I
> > am using pine version 3.07 on a silicon graphics workstation.  I noticed
> > in you ftp server that version 3.90 is available.  However, from the
> > documentation, I am not sure which version to get.  The version for the
> > sun?  When I get the new version, can it be installed without being "root"?
> > 
> > Thanks again for your efforts.  Pine is so much better than unix mail!
> > 
> > Best regards, Dick Reynolds
> > ------------------------------------------------------------------------
> > Richard W. Reynolds                     Coupled Model Project W/NMCx3
> > INTERNET: wd01rr@sgi11.wwb.noaa.gov     National Meteorological Center
> >                                         World Weather Building, Room 807
> > PHONE:    (301) 763-8396                5200 Auth Road
> > FAX:      (301) 763-8125                Camp Springs, MD 20746 USA
> > Note: the two characters after "sgi" are two ones not two Ls.
> > 
> >  
> > 
> > 
> > 





From owner-pine-info@cac.washington.edu  Mon Jan  9 14:46:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01461;
	Mon, 9 Jan 95 14:46:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08429;
	Mon, 9 Jan 95 14:41:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from tyrell.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08423;
	Mon, 9 Jan 95 14:41:55 -0800
Received: from arrowhead.UUCP by tyrell.net with UUCP id AA13277
  (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 9 Jan 1995 16:39:28 -0600
Received: by arrowhead.com (5.0/SMI-SVR4)
	id AA04550; Mon, 9 Jan 95 16:36:54 CST
Date: Mon, 9 Jan 1995 16:36:54 -0600 (CST)
From: Bill Murray <wpm@arrowhead.com>
X-Sender: wpm@arrowhead
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Please send faq
In-Reply-To: <Pine.ULT.3.92.950109133818.2851q-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SOL.3.91.950109163613.4544A-100000@arrowhead>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 426

Please send me a copy of your faq

  ---------------------------------------------------------------------------
  |   Bill Murray                  |       email:  bmurray@arrowhead.com    |
  |   Systems Manager              |       voice:  816-861-1113 Ext 3119    |
  |   Arrowhead Distributors, Inc. |         fax:  816-861-4139             |
  ---------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Mon Jan  9 15:16:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03095;
	Mon, 9 Jan 95 15:16:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09289;
	Mon, 9 Jan 95 15:12:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rs8.loc.gov by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09281;
	Mon, 9 Jan 95 15:12:17 -0800
Received: by rs8.loc.gov (AIX 3.2/UCB 5.64/4.03)
          id AA48334; Mon, 9 Jan 1995 18:14:16 -0500
Date: Mon, 9 Jan 1995 18:14:16 -0500 (EST)
From: George Walser <gwal@loc.gov>
To: Pine Information List <pine-info@cac.washington.edu>
Cc: Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID XI7QJ): no mail
In-Reply-To: <Pine.ULT.3.92.950109124256.2851H-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.A32.3.91.950109181238.58730A-100000@rs8.loc.gov>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I got my E-mail working again, but Im not quite sure how. Thank you for 
responding, even if you couldnt help directly. I appreciate the thought.
George Walser
gwal@loc.gov (no need to reply to this)



From owner-pine-info@cac.washington.edu  Mon Jan  9 15:42:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04391;
	Mon, 9 Jan 95 15:42:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10003;
	Mon, 9 Jan 95 15:37:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09995;
	Mon, 9 Jan 95 15:37:16 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRTVR-00038KC; Mon, 9 Jan 95 15:28 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Pine-Bugs canned reply and FAQ requests
Date: Mon, 9 Jan 1995 14:14:24 -0800
Message-Id: <Pine.ULT.3.92.950109140656.2851x-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


In my zeal to clear out some of the backlog of messages to
pine-bugs@cac.washington.edu, I inadvertantly sent out a couple hundred
copies of a message that implied that a copy of the Pine FAQ could be
obtained simply by sending a message to pine-info@cac.washington.edu (via
a "Reply-To: pine-info@cac.washington.edu" header) This was done manually,
but the text of the message I am sending is a slightly modified version of
the text that will soon be sent out automatically when reports are filed
to pine-bugs from outside the University of Washington.  The automated
reply will not reference pine-info in the headers.  I am appending a copy
of the text of the message below for your reference. 

I'm sorry if this causes undue clutter on comp.mail.pine/pine-info.

--DLM

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

-------
This is a response to your Pine* bug report.  The purpose of this message
is to: 1) acknowledge receipt of your report, 2) apologize in advance for
the fact that you may not receive any other response to it, 3) assure you
that if it is a bug report or enhancement suggestion, we will look at it
carefully, and 4) tell you how to get more information or help. 

Pine is now used by well over a million people around the world, and
thousands more every day.  Not surprisingly, the number of messages sent
to our "pine-bugs" address has become enormous.  Since we receive no
funding to support anyone outside the University of Washington, it is no
longer possible to answer all of them individually. 

Please note that we get many questions which are not actually about Pine.
We can't help you with other programs (talk, chat, IRC), with disk space
on your system, or with unknown/invalid email addresses.  Talk with your
local computer support people about these issues. 

Below is the entry from the Pine Frequently Asked Questions (FAQ) list
about Pine information resources.  We hope it points you to the answers
you need.  If you would like to receive the *entire* Pine FAQ by email, 
simply REPLY to this message.

  The Pine Development Team            * Pine is a registered trademark
   University of Washington               of, and copyright by, the
      Seattle, WA, USA                       University of Washington.

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

                  PINE INFORMATION  RESOURCES

For information on how to configure and use Pine, we encourage you
to read Pine's on-line help, including the Release Notes (the R command
on the Main Menu.)  In addition, those of you handy with FTP or WWW
tools may find some useful documentation on our Pine Information
Center servers:
        ftp://ftp.cac.washington.edu/pine
        http://www.cac.washington.edu/pine

The Pine Frequently Asked Question (FAQ) list is available on those
servers.

Here are some additional sources of assistance:

 o Check with your local support staff.  If you are not sure how to
   contact them, try sending a very polite note to "postmaster"
   on your system, asking that your inquiry be directed to the help desk.

 o If you can't get any help from your local support staff (or you
   *are* the local support staff), consider sending a message to the
   world-wide "pine-info" email list at:
         pine-info@cac.washington.edu
   or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
   are linked together, so there is no need to both send email and post).
   Your message will be seen by thousands of Pine users and system
   administrators, one of whom may have just the information you seek.

 o If you really, *really* need to get in touch with the Pine development
   team directly, send a message to:
         pine@cac.washington.edu


From owner-pine-info@cac.washington.edu  Mon Jan  9 15:52:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04894;
	Mon, 9 Jan 95 15:52:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13103;
	Mon, 9 Jan 95 15:48:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13097;
	Mon, 9 Jan 95 15:48:47 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRTbr-00038LC; Mon, 9 Jan 95 15:34 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: A GUI for Unix-based Pine?
Date: Mon, 9 Jan 1995 14:24:29 -0800
Message-Id: <Pine.ULT.3.92.950109142328.2851y-100000@shiva1.cac.washington.edu>
References: <D205wq.L9z@bcstec.ca.boeing.com> <Pine.SUN.3.91.950106175715.24772B@linda.teleport.com> <3el2fa$33e@ixnews2.ix.netcom.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3el2fa$33e@ixnews2.ix.netcom.com> 


We are currently experimenting with limited mouse capabilities when
running Pine in an xterm.  This feature will probably be included in Pine
3.92... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 7 Jan 1995, Craig Marker wrote:

> Date: 7 JAN 1995 03:40:26 GMT 
> From: Craig Marker <csm@ix.netcom.com>
> Newgroups: comp.mail.pine
> Subject: A GUI for Unix-based Pine? 
> 
> 6. January 1995
> 
> To Whoever can answer...
> 
> I am looking for a GUI for Unix-based Pine, preferably something like 
> Mosaic.  
> 
> If anyone could point me in the right direction, I would really 
> appreciate it.
> 
> Craig
> 
> 


From owner-pine-info@cac.washington.edu  Mon Jan  9 15:59:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05187;
	Mon, 9 Jan 95 15:59:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10352;
	Mon, 9 Jan 95 15:51:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from aldus.northnet.org by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10346;
	Mon, 9 Jan 95 15:51:09 -0800
Received: by Aldus.NorthNet.org (4.1/SMI-4.1)
	id AA12185; Mon, 9 Jan 95 18:51:48 EST
Date: Mon, 9 Jan 1995 18:51:47 -0500 (EST)
From: Nick Zappia <zappia@aldus.NorthNet.org>
To: Pine Information List <pine-info@cac.washington.edu>
Cc: Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID F31U4): M
In-Reply-To: <Pine.ULT.3.92.950109133329.2851i-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950109184411.11962A-100000@aldus.northnet.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

In response to your response.  Sunday night I was on the net and my 
screen flashed this message about a bug.  I did not understand the 
message and inadvertantly sent a message.  I appologize for any 
inconvience I may have caused you.
                                         zappia@northnet.org
On Mon, 9 Jan 1995, David L Miller wrote:

> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Sun, 8 Jan 1995, Nick Zappia wrote:
> 
> > Date: Sun, 8 Jan 1995 19:10:44 -0500 (EST)
> > From: Nick Zappia <zappia@aldus.NorthNet.org>
> > To: Pine Developers <pine-bugs@cac.washington.edu>
> > Subject: Bug (ID F31U4): M
> > 
> 
> 


From owner-pine-info@cac.washington.edu  Mon Jan  9 16:03:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05489;
	Mon, 9 Jan 95 16:03:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10490;
	Mon, 9 Jan 95 15:57:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10484;
	Mon, 9 Jan 95 15:57:22 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRTn1-00038KC; Mon, 9 Jan 95 15:46 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Setting Followup-To header
Date: Mon, 9 Jan 1995 14:37:41 -0800
Message-Id: <Pine.ULT.3.92.950109143619.2851A-100000@shiva1.cac.washington.edu>
References: <3ep130$l5a@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3ep130$l5a@cronkite.ocis.temple.edu> 


Pine allows you to define any headers you want, but it does not currently
understand that followup-to has any special meaning....

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 8 Jan 1995, Wet-Sprocket wrote:

> Date: 8 JAN 1995 15:41:20 GMT 
> From: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: Setting Followup-To header 
> 
> Piners,
> 
> I have added a "Followup-To" header in my customized-hdrs option.
> When I post to a newsgroup, I can set the followups to go to another
> newsgroup by simply typing that newsgroups name at the Followup-To:
> header. It accepts the value, so far so good the article gets posted.
> 
> Then I want to Reply to this post to see if this actually works from
> Pine. Nope, it takes the value in Newsgrps: header but not the other.
> 
> But when I use Tin to reply to this post, it warns me that the followups
> are re-directed to another newsgroup and the newsgroup name.
> 
> Question is why does Pine ignore my Followup-To header while Tin doesn't?
> 
> --
>       o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
>     o      _____            |  /__                 | | Compt. Svcs.  |
>   .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
>  >(________|__|_[_________]_|______________________|_|_______________|_
>  _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
> ========================================================================
> Talk about me doing the talking for others, esp. My Employers!!
> Mac*CHAT List Moderator.
> 
> 


From owner-pine-info@cac.washington.edu  Mon Jan  9 17:00:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08282;
	Mon, 9 Jan 95 17:00:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14877;
	Mon, 9 Jan 95 16:56:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ucsbuxa.ucsb.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14871;
	Mon, 9 Jan 95 16:56:06 -0800
Received: by ucsbuxa.ucsb.edu (4.1/SMI-3.2)
	id AA01233; Mon, 9 Jan 95 16:57:13 PST
Date: Mon, 9 Jan 1995 16:57:13 -0800 (PST)
From: Susanne Riedel <6500sra@ucsbuxa.ucsb.edu>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Bug (ID U72X1): Misspellings
In-Reply-To: <Pine.ULT.3.92.950109115128.2851f-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950109164652.29696B-100000@ucsbuxa.ucsb.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Please send me the *entire* Pine Frequent Asked Question List.
Thank you very much, Susanne Riedel
On Jan 9, David Miller wrote:
> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Wed, 4 Jan 1995, Susanne Riedel wrote:
> 
> > Date: Wed, 4 Jan 1995 10:26:35 -0800 (PST)
> > From: Susanne Riedel <6500sra@ucsbuxa.ucsb.edu>
> > To: Pine Developers <pine-bugs@cac.washington.edu>
> > Subject: Bug (ID U72X1): Misspellings
> > 
> > I am excited about the new Pine version. However, one very simple task 
> > does not seem to be resolved or I cannot figure out how to do it. I am 
> > never able to correct a misspelled word in a text without deleting all 
> > the following words. I was hoping the new Pine version would resolve this 
> > easy problem but I am still not able to find out how to correct a word 
> > further up in the text I want to send by e-mail. Am I just ignorant about 
> > a command or how do I correct my text? I would appreciate a lot if you 
> > could help me.
> > Thank you very much for your time and consideration, 
> > Susanne Riedel
> 


From owner-pine-info@cac.washington.edu  Mon Jan  9 17:40:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10552;
	Mon, 9 Jan 95 17:40:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15964;
	Mon, 9 Jan 95 17:37:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15958;
	Mon, 9 Jan 95 17:37:33 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRVN4-00038CC; Mon, 9 Jan 95 17:27 PST
To: pine-info@cac.washington.edu
From: calfeld@eratosth (Chris Alfeld)
Subject: Re: [ killfile ]
Date: Tue, 10 Jan 1995 00:24:54 GMT
Message-Id: <1995Jan10.002454.3778@math.utah.edu>
References: <3eqd71$hgt@xcalibur.IntNet.net>

Jonathan Cooper (entropy@news.IntNet.net) wrote:
: How would I kill all mail that comes from a certain address using
: pine itself?  Does pine support killfiles?

: Yes, I know I could just make a procmail recipe, but I'd like to
: use just pine.

: -jon
: -- 
: ( --------[ Jonathan D. Cooper ]--------[ entropy@intnet.net ]-------- )
: ( PGP 2.6.2 keyprint: 31 50 8F 82 B9 79 ED C4  5B 12 A0 35 E0 9B C0 01 )
: ( home page: http://taz.hyperreal.com/~entropy/ ]---[ Key-ID: 4082CCB5 )

--
-Chris 	(calfeld@math.utah.edu calfeld@east.east-slc.edu)
	Home Page: http://www.math.utah.edu/~calfeld/


From owner-pine-info@cac.washington.edu  Mon Jan  9 18:19:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11711;
	Mon, 9 Jan 95 18:19:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16668;
	Mon, 9 Jan 95 18:16:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from coho.halcyon.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16662;
	Mon, 9 Jan 95 18:16:54 -0800
Received: by halcyon.com id AA18400
  (5.65c/IDA-1.4.4); Mon, 9 Jan 1995 18:16:48 -0800
Date: Mon, 9 Jan 1995 18:16:46 -0800 (PST)
From: Nathaniel Obezo <zendog@halcyon.com>
X-Sender: zendog@coho.halcyon.com
To: Pine Information List <pine-info@cac.washington.edu>
Cc: Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID SV6TB): 00000000000000
In-Reply-To: <Pine.ULT.3.92.950109132837.2851T-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.ULT.3.91.950109181615.18343A-100000@coho.halcyon.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

please send me the FAQ

thank you Nathaniel Obezo


From owner-pine-info@cac.washington.edu  Mon Jan  9 20:05:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14410;
	Mon, 9 Jan 95 20:05:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18247;
	Mon, 9 Jan 95 20:00:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from axe.humboldt.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18241;
	Mon, 9 Jan 95 20:00:57 -0800
Received: from AXE.HUMBOLDT.EDU by AXE.HUMBOLDT.EDU (PMDF V4.3-10 #8697)
 id <01HLNL0RZ24K8WWFGT@AXE.HUMBOLDT.EDU>; Mon, 09 Jan 1995 20:00:40 -0700 (PDT)
Date: Mon, 09 Jan 1995 20:00:39 -0700 (PDT)
From: WITTMANS@axe.humboldt.edu
Subject: FAQ, please
In-Reply-To: <Pine.ULT.3.92.950109131022.2851h-100000@shiva1.cac.washington.edu>
To: Pine Information List <pine-info@cac.washington.edu>
Message-Id: <Pine.3.89.9501092011.D538990157-0100000@AXE.HUMBOLDT.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT




From owner-pine-info@cac.washington.edu  Mon Jan  9 23:26:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18926;
	Mon, 9 Jan 95 23:26:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21075;
	Mon, 9 Jan 95 23:23:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21069;
	Mon, 9 Jan 95 23:23:28 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRalM-00038KC; Mon, 9 Jan 95 23:13 PST
To: pine-info@cac.washington.edu
From: fpotter@solar.sky.net (Fred Potter)
Subject: Does a Pine "Viewer" Program for PC Exist?
Date: 9 Jan 1995 20:03:54 -0600
Message-Id: <3espua$pvu@solar.sky.net>

Hi folks.  This may sound goofy but here goes.

I prefer *not* to use all the graphical stuff via SLIP etc. that is
available because text is faster for me at 14.4.  I'm kind of a packrat
and I save all my mail.  Here's what I'd like to do: download my
saved-messages and sent-mail files from my Internet provider, store them
on floppies and then view them on my PC with a small DOS program that
looks like the Pine interface.  That way I could view the "directory" of
messages by subject line and date as though I was online.  It would keep
my workspace cleaned out, which would make my sysop happy.  The
alternative is scrolling through the entire file with a text editor or
something.  

Is there such a program for DOS?

Thanks,
Fred


From owner-pine-info@cac.washington.edu  Mon Jan  9 23:42:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19181;
	Mon, 9 Jan 95 23:42:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18308;
	Mon, 9 Jan 95 23:38:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18302;
	Mon, 9 Jan 95 23:38:30 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRb1g-00038CC; Mon, 9 Jan 95 23:29 PST
To: pine-info@cac.washington.edu
From: Ray McAllister <mcallist@gate.net>
Subject: Home directory
Date: Tue, 10 Jan 1995 02:24:02 -0500 (EST)
Message-Id: <Pine.A32.3.90.950110021643.36940A-100000@seminole.gate.net>
References: <3dt0gr$8b2@cronkite.ocis.temple.edu>  <Pine.A32.3.91.950105093453.21569A-100000@smail.hrz.uni-giessen.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.A32.3.91.950105093453.21569A-100000@smail.hrz.uni-giessen.de> 

	Question 1, Please help! How can I access or see what is in my "Home 
Directory"? I cannot seem to find it anywhere on either hard drive, to see
what is in it; to use it, or to delete it. Thanks a million.
	Question 2, Where or how can I get a manual for Pine?
	Question 3, When I go into rz to bring a pre-existing file into 
my home directory I sometimes end up with the Procom 2 screen telling me 
Port in use, yet I have hung up. How can I get rid of Port in use and 
continue with Procom and pine without closing everything back to C:?
	Ray McAllister  mcallist@gate.net


From owner-pine-info@cac.washington.edu  Mon Jan  9 23:59:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19652;
	Mon, 9 Jan 95 23:59:53 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21520;
	Mon, 9 Jan 95 23:55:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from sun.lclark.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21514;
	Mon, 9 Jan 95 23:55:16 -0800
Received: by sun; (5.65/1.1.8.2/29Jul94-0309AM)
	id AA29854; Mon, 9 Jan 1995 23:54:20 -0800
Date: Mon, 9 Jan 1995 23:54:20 -0800 (PST)
From: Stuart Smith <slsmith@lclark.edu>
X-Sender: slsmith@sun
To: Pine Information List <pine-info@cac.washington.edu>
Cc: Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID 6V7HI): problems accessing mail server, junk at end of , address"
In-Reply-To: <Pine.ULT.3.92.950109133250.2851f-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.OSF.3.91.950109235141.29736A-100000@sun>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Thank you for replying so quickly. Sorry about my spelling!! By the time 
I received your reply, I'd already solved the problem. I made a mistake 
when I configured pine. thanx again for your reply.

						Stuart L. Smith
						Lewis & Clark College
						Physical Plant Services
						Engineering services

On Mon, 9 Jan 1995, David L Miller wrote:

> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Sun, 8 Jan 1995, Stuart Smith wrote:
> 
> > Date: Sun, 8 Jan 1995 13:59:18 -0800 (PST)
> > From: Stuart Smith <slsmith@lclark.edu>
> > To: Pine Developers <pine-bugs@cac.washington.edu>
> > Subject: Bug (ID 6V7HI): problems accessing mail server, junk at end of , address"
> > 
> > That's the error I'm getting when I try to send any mail. Can you help me?
> > Reply to:slsmith@lclark.edu
> 


From owner-pine-info@cac.washington.edu  Tue Jan 10 00:33:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20404;
	Tue, 10 Jan 95 00:33:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18924;
	Tue, 10 Jan 95 00:30:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.Germany.EU.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18918;
	Tue, 10 Jan 95 00:30:10 -0800
Received: by mail.Germany.EU.net with UUCP (8.6.5:29/EUnetD-2.5.1.c) via EUnet
	id JAA06566; Tue, 10 Jan 1995 09:31:51 +0100
Received: from sun51.fz.telekom.de (sun51.fz.telekom.de [192.166.56.95]) by mailserver.fz.telekom.de (8.6.5/8.6.5) with SMTP id JAA01870 for <pine-info@cac.washington.edu>; Tue, 10 Jan 1995 09:26:07 +0100
Received: by sun51.fz.telekom.de (4.1/SMI-4.1)
	id AA06095; Tue, 10 Jan 95 09:28:34 +0100
Date: Tue, 10 Jan 1995 09:28:33 +0100 (MET)
From: Ralf Widera <widera@fz.telekom.de>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Bug (ID DL4RK): cannot change standard-printer 
In-Reply-To: <Pine.ULT.3.92.950109124030.2851D-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950110092801.6091B-100000@sun51.fz.telekom.de>
"Reply-To: widera@fz.telekom.de"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 9 Jan 1995, David L Miller wrote:

> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 

------------------------------------------------------------------------------
Ralf Widera, FZ 211b                               Email: widera@fz.telekom.de
DBP Telekom FTZ                                                DBP Telekom FTZ
Forschungs- und Technologiezentrum                             Research Center
Am Kavalleriesand 3 (Postfach 10 00 03)                       PO Box: 10 00 03
64276 Darmstadt                                              D-64276 Darmstadt
06151/83-3855, FAX: 06151/83-4066      +49 6151 83 3855, FAX: +49 6151 83 4066



From owner-pine-info@cac.washington.edu  Tue Jan 10 00:37:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20531;
	Tue, 10 Jan 95 00:37:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22066;
	Tue, 10 Jan 95 00:33:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22060;
	Tue, 10 Jan 95 00:33:47 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRbre-00038KC; Tue, 10 Jan 95 00:23 PST
To: pine-info@cac.washington.edu
From: calimero@lcco.u-strasbg.fr (Guy BRAND)
Subject: Sum Up PGP use within Pine please...
Date: 10 Jan 1995 09:25:06 GMT
Message-Id: <3etjpi$aps@thot.u-strasbg.fr>

-- 

Hi All,

The question has been posted several times but I can't find a sum up of the
answers in this newsgroup so here it is again... I will post a small FAQ if
I receive enough answers :

           How to use PGP from within Pine ?

Thanks
Guy
 
PS: it's illegal to use PGP encryption of the message's bodies in France, 
    but for some security reasons people run PGP to certify emails and 
    data sent over the net.


-----------------------------------------------------------------------------
Guy BRAND                                         guybrand@chimie.u-strasbg.fr
Centre de Recherche Chimie                             ULP Strasbourg (FRANCE)



From owner-pine-info@cac.washington.edu  Tue Jan 10 01:04:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21230;
	Tue, 10 Jan 95 01:04:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19312;
	Tue, 10 Jan 95 00:59:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19306;
	Tue, 10 Jan 95 00:59:57 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRcEh-00038CC; Tue, 10 Jan 95 00:47 PST
To: pine-info@cac.washington.edu
From: ycl6@namaste.cc.columbia.edu (Yeechang Lee)
Subject: JOE 2.5
Date: 10 Jan 1995 08:02:23 GMT
Message-Id: <3eteuf$1jk@apakabar.cc.columbia.edu>
References: <D224M0.HAo@world.std.com> <D238Is.8vG@world.std.com>

Joseph H Allen <jhallen@world.std.com> says:
|Please wait for version 2.5 to appear.  Version 2.4 has a minor bug which
|prevents you from creating new files.

Well, I have 2.5 up and running, and it's nice!  (I'm surprised the man
page doesn't mention JOETERM, though.)  I can't really say I've noticed
much of a difference, but I'm sure it's all there.  More kudos to Joe
and JOE!

And for you comp.mail.pine folk who have been looking for a nice,
easy-to-use editor that doesn't have Pico's clunks, check out JOE--it
fits the bill!
--   _____________________________________________________________________
     Yeechang Lee  (ycl6@columbia.edu)|Nevada Las Vegas Mission Jul'92-'94
     Columbia University/New York City|Celestial Kingdom through Taco Bell
     Still working on my juggling-while-I-play-the-harmonica routine . . .


From owner-pine-info@cac.washington.edu  Tue Jan 10 01:27:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21902;
	Tue, 10 Jan 95 01:27:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22833;
	Tue, 10 Jan 95 01:23:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22827;
	Tue, 10 Jan 95 01:23:48 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRccT-00038KC; Tue, 10 Jan 95 01:12 PST
To: pine-info@cac.washington.edu
From: Mark Crispin <mrc@CAC.Washington.EDU>
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu
Date: Tue, 10 Jan 1995 00:42:54 -0800
Message-Id: <Pine.NXT.3.92.950110002650.23434A-100000@Tomobiki-Cho.CAC.Washington.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3estf0$saa@news.halcyon.com> 

Thank you, Ralph.

The incoming volumne of mail has been terrible; many days there have been
over 150 messages.  That means that just to keep up, we have to answer
mail at an average of one message every 3 minutes.  Even if many messages
can be ignored (either because the message is garbage or if it's clearly
something that some other programmer should take care of), there are the
messages which require a long, carefully-thought-out response that takes
20+ minutes.  The worst cases were the ones where the user needed
handholding; a single such user can take up a day or more, especially 
the ones who insist upon sending messages to our personal mailboxes...

And that's with not getting any *programming work* done.  I hoped to 
have IMAP4 done by early December, when I left for a one-month 
vacation.  The flood of mail made it impossible.

We hate having to send the canned message.  But there's no choice; we
have to get some work done, otherwise what with state budget cuts there
might not be a Pine team (not that getting work done is any guarantee
that the axe won't fall -- they are in a sour mood in Olympia, and axing
visible efforts as a demonstration of "trimming the fat until it hurts"
is very Politically Correct).  Please keep the bouquets and testimonials
coming -- it *does* help in justifying our continued existance!

-- Mark --

On 10 Jan 1995, Ralph Sims wrote:
> One might quip "You get what you pay for."


From owner-pine-info@cac.washington.edu  Tue Jan 10 01:42:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22428;
	Tue, 10 Jan 95 01:42:07 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19969;
	Tue, 10 Jan 95 01:38:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19963;
	Tue, 10 Jan 95 01:38:48 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRcsi-00038CC; Tue, 10 Jan 95 01:28 PST
To: pine-info@cac.washington.edu
From: kjell@ulrik.uio.no (Kjell Andresen)
Subject: mimecodes in header (v3.89)
Date: 10 Jan 1995 09:26:01 GMT
Message-Id: <3etjr9$29d@hermod.uio.no>

I know there is newer pine-versions, but before I start compiling the
newest version I wonder if this problem is solved:

As a Norwegian I recieve a lot of mail using mime-characters.
This is OK in the body (and even the attachments/viewing) of the message,
but the header is *no* good. In this case the message origin is a mac,
which is not set up correctly to ISO-8859-1:
--------------------------
>From Steinar.Moum@usit.uio.no Tue Jan 10 10:23:20 1995
Date: Tue, 10 Jan 1995 08:01:36 +0100
Subject: =?NS_4551-1?Q?R=7Cra?= er klar

    [The following text is in the "NS_4551-1" character set]
    [Your display is set for the "ISO-8859-1" character set]
    [Some characters may be displayed incorrectly]

Fra kl 08.30 og deretter erfaringsvis ca 25 minutter, vil det v{re en
vaffelsteking (buffret med to jern) p} gang i haven i 3. etg.

>>>>>>> Mail-programmet er: Eudora 2.1.1  <<<<<<<<<<<
---------------------------

Regards, Kjell



From owner-pine-info@cac.washington.edu  Tue Jan 10 01:51:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22666;
	Tue, 10 Jan 95 01:51:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23121;
	Tue, 10 Jan 95 01:45:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23115;
	Tue, 10 Jan 95 01:45:05 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRcvE-00038LC; Tue, 10 Jan 95 01:31 PST
To: pine-info@cac.washington.edu
From: ralphs@halcyon.halcyon.com (Ralph Sims)
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu
Date: 10 Jan 1995 03:04:00 GMT
Message-Id: <3estf0$saa@news.halcyon.com>
References: <9501091902.AA18795@cv4.chem.purdue.edu>

lev@cv4.chem.purdue.edu (Lev A. Gorenstein) writes:

>Guys, 

>my mail)...  Well, if so, than I have no words...  This is not the 
>civilized way of treating people:  first you ask "Please, send us bug 
>reports, we will greatly appreciate it!", and than you just pee at those 
>who did answer to your soliciting and send you a letter about improving 
>YOUR server.   Damn, I expect apologees!

One might quip "You get what you pay for."

--

  Northwest NEXUS, Inc. takes Internet OUT of the box!
  info@nwnexus.wa.com, finger info@halcyon.com, or:
  http://www.halcyon.com / +1 206 455 3505 voice


From owner-pine-info@cac.washington.edu  Tue Jan 10 03:12:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24172;
	Tue, 10 Jan 95 03:12:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20948;
	Tue, 10 Jan 95 03:05:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20942;
	Tue, 10 Jan 95 03:05:56 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRe6a-00038SC; Tue, 10 Jan 95 02:47 PST
To: pine-info@cac.washington.edu
From: adf@aficom.ocunix.on.ca (Andrew Farmer)
Subject: Re: Filtering w/ Procmail Help
Date: 9 Jan 1995 19:46:17 -0500
Message-Id: <3eslcp$5ce@aficom.ocunix.on.ca>
References: <3eqjj3$s2h@nntp.crl.com>

Dan Kraemer (dkraemer@crl.com) wrote:
: From danorton@chsw.win.netSun Jan  8 21:59:55 1995
: Date: Sun, 8 Jan 1995 11:53:09 -0600
: From: "Daniel A. Norton" <danorton@chsw.win.net>
: Reply to: familylaw-l@acc.wuacc.edu
: To: dkraemer@crl.com
: Subject: Re: Group Therapy, Evidentiar...

: What recipe should I use to save this to INFAMILYLAW?

:0
* ^Reply-To.*familylaw-l@acc.wuacc.edu
$MAILDIR/INFAMILYLAW

-- 
Andrew Farmer // adf@aficom.ocunix.on.ca
AFI Communications, P.O.Box 11087 Station H, Nepean, Ontario, Canada, K2H 7T8


From owner-pine-info@cac.washington.edu  Tue Jan 10 03:27:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24554;
	Tue, 10 Jan 95 03:27:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24157;
	Tue, 10 Jan 95 03:20:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24151;
	Tue, 10 Jan 95 03:20:55 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rReNT-00038LC; Tue, 10 Jan 95 03:04 PST
To: pine-info@cac.washington.edu
From: mdeem@crash.cts.com (Mike Deem)
Subject: pine? lost ^c command
Date: Tue, 10 Jan 1995 03:30:49 GMT
Message-Id: <D2673E.Epr@crash.cts.com>

Can't control my cancel or arrow commands . Does anyone know What could 
be the problem.

thanks



From owner-pine-info@cac.washington.edu  Tue Jan 10 03:42:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24993;
	Tue, 10 Jan 95 03:42:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21373;
	Tue, 10 Jan 95 03:36:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21367;
	Tue, 10 Jan 95 03:36:03 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRebM-00038SC; Tue, 10 Jan 95 03:19 PST
To: pine-info@cac.washington.edu
From: Bill Murray <arwhead@tyrell.net>
Subject: Highlight Problem
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SUN.3.91.950109172003.15336C-100000@tyrell.net>
Mime-Version: 1.0
Date: Mon, 9 Jan 1995 23:24:29 GMT


I have dumped the control characters PINE sends to a file to examine.  My 
findings are that Pine sends:

Highlight on, Cursor Position, Text, Highlight off

VT100 emulation doesn't seem to mind this syntax, however, my terminal 
wants to see:

Cursor Position, Highlight on, Text and Highlight off

Any ideas on how to change this.  I have been through all of PINE's docs 
and can't find anything, been through termcaps info on my system and 
can't find anything.

Bill Murray
Systems Manager
Arrowhead Distributors, Inc.
arwhead@tyrell.net


From owner-pine-info@cac.washington.edu  Tue Jan 10 03:51:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25182;
	Tue, 10 Jan 95 03:51:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24448;
	Tue, 10 Jan 95 03:44:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24442;
	Tue, 10 Jan 95 03:44:45 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRekJ-00038LC; Tue, 10 Jan 95 03:28 PST
To: pine-info@cac.washington.edu
From: david@hpsgcsgb.sgp.hp.com (David Wong)
Subject: Re: Why no uudecode in Pine?
Message-Id: <D26sBA.Jo3@news.sgp.hp.com>
Date: Tue, 10 Jan 1995 11:09:09 GMT
References: <3ddfin$fem@news.halcyon.com> <Pine.SOL.3.91.941223143542.28750J-100000@hobbes>

In article <Pine.SOL.3.91.941223143542.28750J-100000@hobbes>, egreshko@hobbes.twntpe.cdc.com (Ed Greshko) says:
>
>        Simply use:
>
>        | uudecode
>
>        The file name to be created in in the first line of the uuencoded
>data.  i.e. begin file.gz 666
>

Sorry to bug in, but can a multi-parts uuencoded file be decoded
using Pine? I'm hunting for a reader that can do that. Thanks!

Dave


From owner-pine-info@cac.washington.edu  Tue Jan 10 04:19:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26399;
	Tue, 10 Jan 95 04:19:54 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22012;
	Tue, 10 Jan 95 04:11:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22006;
	Tue, 10 Jan 95 04:11:39 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRfBM-00038LC; Tue, 10 Jan 95 03:56 PST
To: pine-info@cac.washington.edu
From: jhallen@world.std.com (Joseph H Allen)
Subject: Re: JOE 2.4 - Now with SuperPico mode
Message-Id: <D26uHs.3u2@world.std.com>
References: <D224M0.HAo@world.std.com> <D238Is.8vG@world.std.com>
Date: Tue, 10 Jan 1995 11:56:16 GMT

In article <D238Is.8vG@world.std.com>,
Joseph H Allen <jhallen@world.std.com> wrote:
>In article <D224M0.HAo@world.std.com>,
>Joseph H Allen <jhallen@world.std.com> wrote:
>>Version 2.4 of my editor is ready.  You can get it by anonymous ftp from
>>ftp.std.com, file: src/editors/joe2.4.tar.Z.  It probably will not appear
>>until the sysop comes in on monday, however.

>Please wait for version 2.5 to appear.  Version 2.4 has a minor bug which
>prevents you from creating new files.

I seem to be having a lot of trouble releasing this version of JOE.  There
is yet another dumb problem.  If you compile it for terminfo, it doesn't
work correctly.  The fix is to replace the lines:

 a=tgoto(str,a1,a0);
 tputs(a,l,outout);

in file termcap.c with:

 a=tgoto(s,a1,a0);		/* Notice 'str' becomes 's' */
 tputs(a,l,outout);
 return;			/* Plus this 'return' is needed */

Also version 2.6 should appear some time today, which will have this fix.
Thank you for your continued patience and support :-)

-- 
/*  jhallen@world.std.com (192.74.137.5) */               /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}


From owner-pine-info@cac.washington.edu  Tue Jan 10 04:33:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26730;
	Tue, 10 Jan 95 04:33:56 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25131;
	Tue, 10 Jan 95 04:20:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25125;
	Tue, 10 Jan 95 04:20:10 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRfJA-00038OC; Tue, 10 Jan 95 04:04 PST
To: pine-info@cac.washington.edu
From: Ponnusamy Rajendran <raj@matilda.vut.edu.au>
Subject: News Collection - Empty List
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SUN.3.91.950110164442.25753A-100000@matilda.vut.edu.au>
Mime-Version: 1.0
Date: Tue, 10 Jan 1995 05:56:30 GMT


We have Pine 3.91 running on a SunOS4.1.x system. When expanding 
the News Collection folder I get

  [ ** Empty List **  Select Here to Try Re-Expanding ]

message.  But when telnet to port 119 (for nntp services) on the 
news server, I can see the news group listing.

Any suggestions ...

Thanks


************************************************************
*                                                                     *
* Ponnusamy Rajendran (Raj)                                           *
* Department of Computer and Mathematical Sciences                    *
* Victoria University of Technology   Email: raj@yarra.vut.edu.au   *
* P.O. 14428, Melbourne Mail Centre   Fax:   +61 3 688 4050           *
* MELBOURNE 3001, AUSTRALIA           Tel:   +61 3 688 4682           * 
*                                                                     * 
************************************************************************




From owner-pine-info@cac.washington.edu  Tue Jan 10 04:39:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26879;
	Tue, 10 Jan 95 04:39:52 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22263;
	Tue, 10 Jan 95 04:34:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22257;
	Tue, 10 Jan 95 04:34:16 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRfcU-00038OC; Tue, 10 Jan 95 04:24 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Highlighting and News reader capabilities
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950110121902.19542A-100000@bambix.icce.rug.nl>
Mime-Version: 1.0
Date: Tue, 10 Jan 1995 11:37:24 GMT

First of all, congratulations to the Pine folks. I've been using Elm and Nn
for e-mail / news, and I have just installed Pine (10 minutes of work) -- and
it really surprised me that the thing runs. In fact, it runs like a dream.

I have however a couple of questions. Please bear with me, I'm a novice
concerning Pine. RTFM-pointers are welcome too, though I'd prefer an
explanation.

(1) I am using X-windows (Pine in an xterm window) and I _hate_ the reverse
video displays that Pine uses. I managed to eliminate the reverse video as far
as selected articles/mails go, but the main menu and other menus still use
reverse video. Isn't there a better way? Even my non-X "man" can do
underlines and boldfaces instead of reverse video!

A _big_ request: how do I get Pine to discard reverse video completely, but
use other termcap capabilities (e.g., color changes, boldface, or even
underlining) instead?

(2) When I use function keys (-k switch) I get rubbish, Pine fails to
recognize them. I _know_ that I'm not using a proper VT100, but that should
not matter. My /etc/termcap (yes, I've compiled Pine with termcap support, not
terminfo) is correct though; e.g., my favorite editor Jove recognizes :k1, :k2
etc. correctly and translates the corresponding escape sequences to the right
keys.

So, another _big_ request: Pine should check /etc/termcap (if compiled so) and
match incoming escape sequences to the keys stated there! Not hardwire F1, F2
etc!

(3) I've set up Pine to get newsfeed from another cite. Pine seems to retrieve
all messages when opening the corresponding folder! That's not really what I
want. I've set up nn (nnmaster, nnadmin etc.) in such a way that _only_ the
article titles are retrieved from the newsfeeder; the actual article is only
requested when I want to read it.

How do I get Pine to emulate such behavior?

(4) Can Pine mark all the articles in a newsgroup as "read" at once? I would
like this capability when I come home from a vacation, and get thousands of
articles in some groups.. I just want to mark "all" as "read" and restart
fresh the next day.

Anyway, again: great work, Pine group. I am really extremely pleased,
especially with the installation ease and simple usage.

Please reply by e-mail (preferred) -- I am likely to miss follow-ups.
--
Karel Kubat (karel@bambix.icce.rug.nl).
You might be a redneck if..
Your mother does not remove the Marlboro from her mouth before telling the
state trooper to kiss her ass.



From owner-pine-info@cac.washington.edu  Tue Jan 10 05:26:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28040;
	Tue, 10 Jan 95 05:26:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25833;
	Tue, 10 Jan 95 05:18:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25827;
	Tue, 10 Jan 95 05:18:04 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRgDF-00038LC; Tue, 10 Jan 95 05:02 PST
To: pine-info@cac.washington.edu
From: fyao@calum.csclub.uwaterloo.ca (Frank Yao)
Subject: Adding to addressbook answered (and a ?? of my own)
Message-Id: <D26ox6.A1@undergrad.math.uwaterloo.ca>
References: <Pine.SUN.3.91.950106165903.6579A-100000@antares>
Date: Tue, 10 Jan 1995 09:55:54 GMT

In article <Pine.SUN.3.91.950106165903.6579A-100000@antares>,
Keith M. Rainey <kmr@engr.latech.edu> wrote:
>
>	I use a lot of lists in my addressbook and I am constantly
>changing lists, and adding new lists.  Is there a way to append a
>text file of addresses into the .addressbook file?  It would make 
>my life a little easier (since I'm so lazy).  Also, is there a
>way to send address lists to other users without them having to 
>type in all of the names?

I would think doing something like:

cat text.file >> .addressbook 

would do it.  

I don't quite understand the second part of what you are asking.

However, since I am at it, I will ask a question of my own:

In the index screen, we get a flag (N,D,A etc), the sender, the size
and the subject.  What exactly is that size indicating, and is there a
way to change it to reflect the number of LINES in the mail message?

- frank


-- 
**************************************************************************
* 	Forever is a very brief time for a mortal...		         * 
*					- Victoria, Vampire Goddess	 *
************************** Frank Yao, fyao@calum.csclub.uwaterloo.ca *****


From owner-pine-info@cac.washington.edu  Tue Jan 10 05:41:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28343;
	Tue, 10 Jan 95 05:41:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26024;
	Tue, 10 Jan 95 05:32:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from info.elf.stuba.sk by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26020;
	Tue, 10 Jan 95 05:31:58 -0800
Received: from elf.stuba.sk (decef.elf.stuba.sk) by info.elf.stuba.sk with SMTP id AA17641
  (5.67b/IDA-1.5 for <pine-info@cac.washington.edu>); Tue, 10 Jan 1995 14:16:27 +0100
Received: by elf.stuba.sk id AA10325
  (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Tue, 10 Jan 1995 14:17:30 +0100
Date: Tue, 10 Jan 1995 14:15:32 +0100 (MET)
From: Jay R McVeigh <mcveigh@elf.stuba.sk>
Subject: advice (fwd)
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.87.9501101432.A9956-0100000@decef.elf.stuba.sk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Any help would be appreciated in setting up the system!!!!!!!!!

Jay R McVeigh
Biomedical Engineering Educator
c/o Project HOPE	email: mcveigh@elf.stuba.sk
Limbova 12
833 03
Bratislava, Slovak Republic
phone ++42-7 (377-051) (377-052)
fax   ++42-7 (374-587)
---------- Forwarded message ----------
Date: Fri, 6 Jan 1995 12:31:33 +0100 (MET)
From: Jay R McVeigh <mcveigh@elf.stuba.sk>
To: Tech Assistance Pine <pine-bugs@cac.washington.edu>
Subject: advice

I would appreciate some assistance and advice in setting up a 486 system
with the PC Pine programme.  The system now uses a uupc programe to tie into
what I believe is individual mail addresses for some doctors (10) I work
with here in Bratislava.  There is no technical support for the system and
I am asked to help make the system more user friendly.  The pc uses a
phone line to dial into the mail addresses at another site and is very
cumbersom and user un friendly.  Windows 3.1 is being used on the pc and I
would like to install pc pine for windows and hopefully make it easier.  I
have downloaded the pc pine for windows on my pc and also, mosaic and
trumpet winsock.  My problem is I am unsure as how to set up pine to dial
out to the remote site and process the email.

Thank you for your attention and Merry Christmas and Happy New Year
ps This is my own email address at the university and totaly unrelated

Jay R McVeigh
Biomedical Engineering Educator
c/o Project HOPE	email: mcveigh@elf.stuba.sk
Limbova 12
833 03
Bratislava, Slovak Republic
phone ++42-7 (377-051) (377-052)
fax   ++42-7 (374-587)




From owner-pine-info@cac.washington.edu  Tue Jan 10 06:08:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28847;
	Tue, 10 Jan 95 06:08:19 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23395;
	Tue, 10 Jan 95 06:02:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23389;
	Tue, 10 Jan 95 06:02:05 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRgyP-00038OC; Tue, 10 Jan 95 05:50 PST
To: pine-info@cac.washington.edu
From: jcg@osf01.cc.rl.ac.uk (Dr J Gordon)
Subject: Re: trouble with the return address
Date: 10 Jan 1995 13:25:52 GMT
Message-Id: <3eu1t0$1sd8@unixfe.rl.ac.uk>
References: <9601051344.AA26314@poseidon.ifctr.mi.cnr.it> <Pine.ULT.3.92.950105113332.5215J-100000@shiva2.cac.washington.edu>


Terry Gray gave a clear explanation last week of what pine does 
with the address to the right of the @.

Can he or anyone else describe how I can change the text to 
the left of the @? ie the username. 

My site runs a central mailer which knows about us all by name 
eg mail to me as j.c.gordon@rl.ac.uk is directed to my preferred mailbox.
This all works fine and I use some MUAs which allow me to have a From: field
of <j.c.gordon@rl.ac.uk>. Eudora and PC-PINE allow this. This way I only 
have to look in one place for incoming mail no matter how many machines 
I send from.

Q: Can I achieve this with PINE on Unix?

I know that I can add a Reply-To: header but this doesn't catch all the 
people who use useful tools like PINE's Takeaddress to copy From fields
out of mail headers into addressbooks or nickname files.

John Gordon 


From owner-pine-info@cac.washington.edu  Tue Jan 10 06:25:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29235;
	Tue, 10 Jan 95 06:25:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23569;
	Tue, 10 Jan 95 06:17:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mineshaft.odi.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23563;
	Tue, 10 Jan 95 06:17:05 -0800
Received: from odi.com (mastermind.odi.com) by mineshaft.odi.com (5.65c/SMI-4.0/ODI-5)
	id AA03292; Tue, 10 Jan 1995 09:17:04 -0500
Received: from ima.odi.com by odi.com (4.1/SMI-4.0/ODI-15)
	id AA19320; Tue, 10 Jan 95 09:17:02 EST
Received: (bsmith@localhost) by ima.odi.com (8.6.9/8.6.9) id JAA07463; Tue, 10 Jan 1995 09:16:51 -0500
Date: Tue, 10 Jan 1995 09:16:51 -0500 (EST)
From: "Bill R. Smith" <bsmith@odi.com>
To: pine-info@cac.washington.edu
Subject: FAQ Addition Request: You should put how to unsubscribe pine-info in there
Message-Id: <Pine.SUN.3.91.950110091404.5510i-100000@ima>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I was a little surprised by the volume of email when I subscribed to 
pine-info.  I deleted my pine-info subscription acknowledgement a little 
too hasty.  In the FAQ, you should put in how to unsubscribe from the 
pine-info mailing list.


From owner-pine-info@cac.washington.edu  Tue Jan 10 06:26:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29256;
	Tue, 10 Jan 95 06:26:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26583;
	Tue, 10 Jan 95 06:17:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26577;
	Tue, 10 Jan 95 06:17:07 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRhCd-00038OC; Tue, 10 Jan 95 06:05 PST
To: pine-info@cac.washington.edu
From: viljanen@cc.Helsinki.FI (Lea Viljanen)
Subject: Re: base64 encoded text/plain
Date: 4 Jan 1995 11:34:12 -0000
Message-Id: <3ee13k$lcq@kantti.Helsinki.FI>
References: <9501031735.AA13736@cli51ak>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Daniel Glazman <Daniel.Glazman@der.edf.fr> wrote:
>I often receive 7bit us-ascii text/plain bodyparts base64 encoded !!!!
>But I can't determine which software is (automatically I believe,
>I can't imagine it's the result of a human action) incriminated...

Pine does this if you make the ASCII file an attachment of the 
message. If you just include the ASCII file in the message, this
doesn't happen.

I solved this annoyance by teaching my MTA to decode C-T: text/plain
C-T-E: BASE64 to C-T-E: 7 or 8bit (depending on the charset).

></Daniel>

-- 
Lea 'LadyBug' Viljanen        University of Helsinki      Lea doesn't
Lea.Viljanen@Helsinki.FI      Computing Centre            rhyme with tea.


From owner-pine-info@cac.washington.edu  Tue Jan 10 06:32:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29399;
	Tue, 10 Jan 95 06:32:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23622;
	Tue, 10 Jan 95 06:20:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.ois.state.de.us by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23616;
	Tue, 10 Jan 95 06:20:11 -0800
Received: by ns.ois.state.de.us; Tue, 10 Jan 95 9:21:00 EST
Date: Tue, 10 Jan 95 9:08:32 EST
Message-Id: <GNJ8+0Td2jA@ns.ois.state.de.us>
X-Priority: 1 (High)
From: "Michael F. Stratton" <MStratton@ns.ois.state.de.us>
To: pine-info@cac.washington.edu
Subject: How do I set up my sendmail host for PCPINE
X-Incognito-Sn: 1000
X-Incognito-Format: VERSION=2.00 EAP-1 ENCRYPTED=NO

I am trying to set up PCPINE on my network.

I use Winsock from a several vendors.

My mailhost is a Sun SPARCServer20 running Solaris 2.3.  \

PINE runs fine on the SPARC, and if you telnet to the SPARC.
                                                           
I read the FAQ and README files for PCPINE, and see that I have to set up an 
INBOX on my sendmail host.

How do I set up these INBOX's and how do I give permission/allow connection 
to the SUN box for PCPINE to open this INBOX?

I work for the State government, and we are attempting to set up mail 
accounts for all 100,000+ students K-12 in the states public school system.  
They will all have T-1 speed connections (SMDS) to my site to get to their 
mailboxes.  (obviously I will need a bigger SPARC when they are all online).

Any help would be appreciated.

-Mike Stratton
State of Delaware
Office of Telecom Mgt.
302-739-9655


From owner-pine-info@cac.washington.edu  Tue Jan 10 06:48:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29865;
	Tue, 10 Jan 95 06:48:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23972;
	Tue, 10 Jan 95 06:40:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23589;
	Tue, 10 Jan 95 06:18:12 -0800
Received: from mineshaft.odi.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23583;
	Tue, 10 Jan 95 06:18:10 -0800
Received: from odi.com (mastermind.odi.com) by mineshaft.odi.com (5.65c/SMI-4.0/ODI-5)
	id AA03298; Tue, 10 Jan 1995 09:18:09 -0500
Received: from ima.odi.com by odi.com (4.1/SMI-4.0/ODI-15)
	id AA19355; Tue, 10 Jan 95 09:18:08 EST
Received: (bsmith@localhost) by ima.odi.com (8.6.9/8.6.9) id JAA07469; Tue, 10 Jan 1995 09:17:58 -0500
Date: Tue, 10 Jan 1995 09:17:57 -0500 (EST)
From: "Bill R. Smith" <bsmith@odi.com>
To: pine-announce@cac.washington.edu
Message-Id: <Pine.SUN.3.91.950110091730.5510j-100000@ima>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

subscribe pine-announce


From owner-pine-info@cac.washington.edu  Tue Jan 10 10:02:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08922;
	Tue, 10 Jan 95 10:02:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28206;
	Tue, 10 Jan 95 09:54:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28200;
	Tue, 10 Jan 95 09:54:56 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRkfC-00038CC; Tue, 10 Jan 95 09:47 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Re: advice (fwd) 
In-Reply-To: <Pine.3.87.9501101432.A9956-0100000@decef.elf.stuba.sk> 
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950110164108.21261A-100000@bambix.icce.rug.nl>
References: <Pine.3.87.9501101432.A9956-0100000@decef.elf.stuba.sk> 
Mime-Version: 1.0
Date: Tue, 10 Jan 1995 15:46:39 GMT

Hi Jay,

On Tue, 10 Jan 1995, Jay R McVeigh wrote:

> I would appreciate some assistance and advice in setting up a 486 system
> with the PC Pine programme.  The system now uses a uupc programe to tie into
> what I believe is individual mail addresses for some doctors (10) I work
> with here in Bratislava.  There is no technical support for the system and
> I am asked to help make the system more user friendly.  The pc uses a
> phone line to dial into the mail addresses at another site and is very
> cumbersom and user un friendly.  Windows 3.1 is being used on the pc and I
> would like to install pc pine for windows and hopefully make it easier.  I
> have downloaded the pc pine for windows on my pc and also, mosaic and
> trumpet winsock.  My problem is I am unsure as how to set up pine to dial
> out to the remote site and process the email.

If you want to do it the "hard" but perfect way, toss Dos + Windows and go for
a Unix operating system. Linux is a good choice; it should run without
problems on your 486 system. You'd get yourself into some trouble by promoting
to system administrator, but being "root" is somehow cool too. The way I'd set
this up is:

    - sendmail as the recepient + delivery agent, also using deliver for local
    users; the uucp thing would be handled inside sendmail

    - regular times to dial out and retrieve mail; sendmail has lots of info
    on how to do this

    - give your 10 doctors local usernames and a telnet connection; if they
    won't do other stuff than read mail they should be quite happy on one
    Linux box.

    - set up Pine as the mail reader.

I may be quite wrong, but I thought that Pine was a _reader_ and not a
_retriever_ of mail..

--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
I'd rather have a full bottle in front of me than a full frontal lobotomy.


From owner-pine-info@cac.washington.edu  Tue Jan 10 10:12:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09556;
	Tue, 10 Jan 95 10:12:35 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01735;
	Tue, 10 Jan 95 10:05:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01715;
	Tue, 10 Jan 95 10:04:59 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRknx-00038CC; Tue, 10 Jan 95 09:56 PST
To: pine-info@cac.washington.edu
From: harris@email.unc.edu (Trey Harris)
Subject: zero-length .pine-interrupted-mail files
Date: 10 Jan 1995 17:44:33 GMT
Message-Id: <3euh21$12np@bigblue.oit.unc.edu>

I am running Pine 3.91 on a 15,000-user AIX 3.2.5 site.  Among these 
users, the most common problem they experience with Pine (our Help Desk 
says they get this question several times a day) is zero-length 
.pine-interrupted-mail* files in the home directory.

What happens when they get these is this: Pine tells them they have 
postponed mail, and asks if they wish to continue.  When the user answers 
"Yes", it either says "You don't have any interrupted mail!" and goes 
back to the menu/index, or it core dumps with an "abend" error.

As far as I am able to tell, Pine *never* produces a non-zero-length 
pine-interrupted-mail* file.

We had this problem with even greater frequency than is now the case, but 
I was able to allieviate the problem to some degree by recompiling Pine.  
I had originally compiled Pine without "-DDEBUG" because pine-debug files 
were accumulating on our system, and sometimes Pine would go out of 
control and continue to write to a pine-debug file until the filesystem 
was full.

Once I restored "-DDEBUG" (setting the default debug level to 0) the 
.pine-interrupted-mail files were reduced, but they still occur.

Can anyone suggest how we can fix this?  It is extremely annoying to both 
our Help Desk and our users.
-- 
Trey Harris                              http://sunsite.unc.edu/harris
  System Administrator, Project Isis, Office of Information Technology
                       The University of North Carolina at Chapel Hill


From owner-pine-info@cac.washington.edu  Tue Jan 10 10:47:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11110;
	Tue, 10 Jan 95 10:47:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02780;
	Tue, 10 Jan 95 10:40:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from UCS.ORST.EDU by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02772;
	Tue, 10 Jan 95 10:40:58 -0800
Received: by ucs.orst.edu; (5.65/1.1.8.2/24Sep94-1201PM)
	id AA17051; Tue, 10 Jan 1995 10:40:57 -0800
Date: Tue, 10 Jan 1995 10:40:57 -0800 (PST)
From: Tammy Barr <barrt@ucs.orst.edu>
To: pine-info@cac.washington.edu
Subject: Reading news
Message-Id: <Pine.OSF.3.91.950110102601.32081B-100000@ucs.orst.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there any detailed documentation available for reading news in Pine?

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Tammy Barr                                    Email: barrt@ucs.orst.edu
Consultant, User Services                     Phone: 737-5404
University Computing Services



From owner-pine-info@cac.washington.edu  Tue Jan 10 10:56:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11519;
	Tue, 10 Jan 95 10:56:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29595;
	Tue, 10 Jan 95 10:50:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29589;
	Tue, 10 Jan 95 10:50:28 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRlV9-00038QC; Tue, 10 Jan 95 10:41 PST
To: pine-info@cac.washington.edu
From: offsite@crl.com (Lee (not F) Bailey)
Subject: Re: Highlight Problem
Date: 10 Jan 1995 16:36:35 GMT
Message-Id: <3eud2j$om@nntp.crl.com>
References: <Pine.SUN.3.91.950109172003.15336C-100000@tyrell.net>

Bill Murray (arwhead@tyrell.net) wrote:

> I have dumped the control characters PINE sends to a file to examine.  My 
> findings are that Pine sends:

> Highlight on, Cursor Position, Text, Highlight off

> VT100 emulation doesn't seem to mind this syntax, however, my terminal 
> wants to see:

> Cursor Position, Highlight on, Text and Highlight off

> Any ideas on how to change this.  I have been through all of PINE's docs 
> and can't find anything, been through termcaps info on my system and 
> can't find anything.

Try pine-setup-configure, slow_terminal=on. This will show an arrow 
indicator instead of doing the reverse video bit.

May not be what you want, but it should work for the current message 
line.

If your problem is the reverse video at the top and bottom of the screen 
then you might have to dive into your vt100 termcap on the local machine 
(ugly ;)

 --
______________________________________________________________________________
Lee Bailey	|  E-Mail:   offsite@crl.com
	User of Geoworks Ensemble instead of M$ Windoze
	Try the demo at ftp://arginine.umdnj.edu/pub/geos/publish
		     or ftp://ftp.mcs.com/mcsnet.users/jbarr/GeoPublish	


From owner-pine-info@cac.washington.edu  Tue Jan 10 11:16:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12500;
	Tue, 10 Jan 95 11:16:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03628;
	Tue, 10 Jan 95 11:10:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03622;
	Tue, 10 Jan 95 11:10:06 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRloo-00038CC; Tue, 10 Jan 95 11:01 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: pine? lost ^c command
Date: Tue, 10 Jan 1995 16:19:47 GMT
Message-Id: <D276p0.7BI@ssi.edc.org>
References: <D2673E.Epr@crash.cts.com>

Mike Deem (mdeem@crash.cts.com) wrote:
: Can't control my cancel or arrow commands . Does anyone know What could 
: be the problem.

My first guess is that you're using Terminal for Windows, and you've 
turned on "Use function, arrow and control keys for Windows".  This 
causes all arrow, F-key control keys which might be trapped as windows 
commands to never be sent to the session.  So, ^C is (C)opy to 
clipboard.  And so forth.

Sound plausible?

Gunther Anderson


From owner-pine-info@cac.washington.edu  Tue Jan 10 12:18:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15288;
	Tue, 10 Jan 95 12:18:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01563;
	Tue, 10 Jan 95 12:09:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01557;
	Tue, 10 Jan 95 12:09:12 -0800
Received: from localhost by shiva2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06836;
	Tue, 10 Jan 95 12:09:00 -0800
Date: Tue, 10 Jan 1995 12:08:59 -0800 (PST)
From: Steve Hubert <hubert@cac.washington.edu>
To: "Lev A. Gorenstein" <lev@cv4.chem.purdue.edu>
Cc: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu
In-Reply-To: <9501091902.AA18795@cv4.chem.purdue.edu>
Message-Id: <Pine.ULT.3.92.950110120752.2030D@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 9 Jan 1995, Lev A. Gorenstein wrote:

> Guys, 
> 
> Shame on you!  I understand that you're busy because people are sending 
> you bullshit questions (and the amount of bullshit is much more than the 
> amount of gold in it).  But still, what you've done is, well, let's say
> "impolite", though some other words are on the tip of my tongue.  I 
> received the AUTOMATED answer from you A WEEK (!!!) after I sent you my 
> bug report!  If you use the program to automatically fetch the standard 
> text as a reply-acknoledgement of receiving a report, than it shouldn't 
> take A WEEK to send acknoledgement!  And if I'm wrong and you read my 
> report, and than sent me this formal crap that "people are asking us 
> about IRC, talk chat, disk space..." (and there was nothing about it in
> my mail)...  Well, if so, than I have no words...  This is not the 
> civilized way of treating people:  first you ask "Please, send us bug 
> reports, we will greatly appreciate it!", and than you just pee at those 
> who did answer to your soliciting and send you a letter about improving 
> YOUR server.   Damn, I expect apologees!

Sorry.
 
> Hope that I won't get the same text about "no disk space on your host",
> etc. again.

We do our best.

> ____________________________________________
>   Lev A. Gorenstein
>   Chemistry Department
>   Purdue University
>   W.Lafayette, IN 47907, USA
>   (317)494-5289; Fax (317)494-0239
>   lev@chem.purdue.edu

Steve Hubert <hubert@cac.washington.edu>
Networks and Distributed Computing, Univ. of Washington, Seattle


From owner-pine-info@cac.washington.edu  Tue Jan 10 12:22:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15493;
	Tue, 10 Jan 95 12:22:17 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04957;
	Tue, 10 Jan 95 12:05:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04951;
	Tue, 10 Jan 95 12:05:55 -0800
Received: from localhost by shiva2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06762;
	Tue, 10 Jan 95 12:05:50 -0800
Date: Tue, 10 Jan 1995 12:05:48 -0800 (PST)
From: Steve Hubert <hubert@cac.washington.edu>
To: "Keith M. Rainey" <kmr@engr.latech.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Adding to addressbook
In-Reply-To: <Pine.SUN.3.91.950106165903.6579A-100000@antares>
Message-Id: <Pine.ULT.3.92.950110120131.2030C-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

If you have two files that are both address books, you can combine them 
into one larger one by concatenating the files.  So you could send an 
address book to somebody else by sending the file (usually .addressbook) 
as an attachment.  Then the receiver would save that into a file and 
"cat" it together with their existing address book or have it be a second 
address book.  No way to send part of an address book without some hand 
editing outside of pine.

A distribution list has the format

nickname <TAB> full_list_name <TAB> (addr1,addr2,...)

Check in your .addressbook for an example.  You just need to be sure to 
use tabs in the appropriate places.  A regular simple entry is

nickname <TAB> fullname <TAB> address

Steve Hubert <hubert@cac.washington.edu>
Networks and Distributed Computing, Univ. of Washington, Seattle

On Fri, 6 Jan 1995, Keith M. Rainey wrote:

> 
> 	I use a lot of lists in my addressbook and I am constantly
> changing lists, and adding new lists.  Is there a way to append a
> text file of addresses into the .addressbook file?  It would make 
> my life a little easier (since I'm so lazy).  Also, is there a
> way to send address lists to other users without them having to 
> type in all of the names?
> 
> 	Any help would be greatly appreciated.  Thank you.
> 
> Keith M. Rainey
> Louisiana Tech University
> Biomedical Engineering
> kmr@engr.latech.edu


From owner-pine-info@cac.washington.edu  Tue Jan 10 13:41:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19818;
	Tue, 10 Jan 95 13:41:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03755;
	Tue, 10 Jan 95 13:35:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03747;
	Tue, 10 Jan 95 13:35:23 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRo5u-00038KC; Tue, 10 Jan 95 13:27 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Why no uudecode in Pine?
Date: Tue, 10 Jan 1995 11:40:19 -0800
Message-Id: <Pine.ULT.3.92.950110113741.18990F-100000@shiva1.cac.washington.edu>
References: <3ddfin$fem@news.halcyon.com> <Pine.SOL.3.91.941223143542.28750J-100000@hobbes> <D26sBA.Jo3@news.sgp.hp.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D26sBA.Jo3@news.sgp.hp.com> 


On Tue, 10 Jan 1995, David Wong wrote:

> 
> Sorry to bug in, but can a multi-parts uuencoded file be decoded
> using Pine? I'm hunting for a reader that can do that. Thanks!
> 

Yes, use ';' to select all the parts, then "a|uudecode" to decode them. 
Note that the parts need to be listed in order in the index before doing
the decoding...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Tue Jan 10 15:23:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24416;
	Tue, 10 Jan 95 15:23:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05915;
	Tue, 10 Jan 95 15:03:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.fast.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05909;
	Tue, 10 Jan 95 15:03:15 -0800
Received: from roland.fast.net by fast.net with smtp
	(Smail3.1.28.1 #13) id m0rRpbS-0003WwC; Tue, 10 Jan 95 18:03 EST
Date: Tue, 10 Jan 1995 17:58:52 -0800 (PST)
From: Roland Zuk <roland@fast.net>
To: Mark Crispin <mrc@CAC.Washington.EDU>
Cc: pine-info@cac.washington.edu
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu
X-Sender: roland@ns.fast.net
In-Reply-To: <Pine.NXT.3.92.950110002650.23434A-100000@Tomobiki-Cho.CAC.Washington.EDU>
Message-Id: <Pine.PCW.3.91.950110175044.8231B-100000@roland.fast.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Tue, 10 Jan 1995, Mark Crispin wrote:

> We hate having to send the canned message.  But there's no choice; we
> have to get some work done, otherwise what with state budget cuts there
> might not be a Pine team (not that getting work done is any guarantee

> is very Politically Correct).  Please keep the bouquets and testimonials
> coming -- it *does* help in justifying our continued existance!


Okay, you've got it Mark....OUTSTANDING!  Nice work...please don't let 
the poo-pooers get you sidetracked.  From one avid Unix Pine and 
Winsock Pine user, the Pine team has done an excellent job with very 
little resources and support.  Too bad those who are quick to b!#ch don't 
take the time to read the canned response, lest they understand, and lack 
the initiative to help themselves a little.

Keep up the good work.
Roland




From owner-pine-info@cac.washington.edu  Tue Jan 10 15:35:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25218;
	Tue, 10 Jan 95 15:35:37 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09810;
	Tue, 10 Jan 95 15:19:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09804;
	Tue, 10 Jan 95 15:19:30 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRpbX-00038RC; Tue, 10 Jan 95 15:03 PST
To: pine-info@cac.washington.edu
From: The Group <group@uiuc.edu>
Subject: blind carbon copies
Date: 10 Jan 1995 21:21:20 GMT
Message-Id: <3eutog$9sb@vixen.cso.uiuc.edu>

I'm trying to use Pine to send out announcements 
to a long list of people, but I don't want the addresses
to show up in everyone's mailbox.  Does anyone know how 
send blind carbon copies using Pine?

Thanks,
Peter
Peter Miller
U. of Illinois Physics Dept.
peterm@uiuc.edu



From owner-pine-info@cac.washington.edu  Tue Jan 10 15:41:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25512;
	Tue, 10 Jan 95 15:41:12 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06445;
	Tue, 10 Jan 95 15:25:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.fast.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06439;
	Tue, 10 Jan 95 15:25:10 -0800
Received: from roland.fast.net by fast.net with smtp
	(Smail3.1.28.1 #13) id m0rRpwg-0003TXC; Tue, 10 Jan 95 18:25 EST
Date: Tue, 10 Jan 1995 18:20:48 -0800 (PST)
From: Roland Zuk <roland@fast.net>
To: Fred Potter <fpotter@solar.sky.net>
Cc: pine-info@cac.washington.edu
Subject: Re: Does a Pine "Viewer" Program for PC Exist?
X-Sender: roland@ns.fast.net
In-Reply-To: <3espua$pvu@solar.sky.net>
Message-Id: <Pine.PCW.3.91.950110181225.8231C-100000@roland.fast.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On 9 Jan 1995, Fred Potter wrote:

> I prefer *not* to use all the graphical stuff via SLIP etc. that is

Me too...and I've found what I think is the IDEAL setup with PC-Pine 
Winsock.  It runs with the winsock so I can run my other apps at the same 
time, but Pine is not a full blown Windoze GUI...perfect!  Text based, 
keyboard entry..and just like Unix Pine on my other platform!  I love 
it.  I just hate going back and forth between mouse and kbd all the time 
like you have to with "real" windows pgms.


> available because text is faster for me at 14.4.  I'm kind of a packrat
> and I save all my mail.  Here's what I'd like to do: download my
> saved-messages and sent-mail files from my Internet provider, store them
> on floppies and then view them on my PC with a small DOS program that

This is excatly what I do with Pine.  I fooled around with a LOT of 
offline mail readers and none of them can match the capabilities of Pine 
IMO....searching all text in a folder, etc.  When I want to do some 
archive reading offline, I just ^C at the login prompt to bypass the 
server connection, then switch my modem off.  Pine sqwauks a few times 
about not being able to open the inbox, but it runs just fine as an 
offline reader.

Regards
Roland


From owner-pine-info@cac.washington.edu  Tue Jan 10 16:09:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27759;
	Tue, 10 Jan 95 16:09:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07187;
	Tue, 10 Jan 95 15:54:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from red1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07181;
	Tue, 10 Jan 95 15:54:20 -0800
Received: by red1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00217;
	Tue, 10 Jan 95 15:54:18 -0800
Date: Tue, 10 Jan 1995 15:54:17 -0800 (PST)
From: "Timothy F. Lee" <koolkid@u.washington.edu>
X-Sender: koolkid@red1.cac.washington.edu
To: The Group <group@uiuc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: blind carbon copies
In-Reply-To: <3eutog$9sb@vixen.cso.uiuc.edu>
Message-Id: <Pine.ULT.3.91a.950110155222.27724F-100000@red1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


When you go to compose your mail, press Ctrl-R in the header area to 
expose rich headers.  The rich header contains a couple extra fields, one 
of which is BCC:, for blind carbon copies.

--tim

-------------------------------------------
Timothy F. Lee (koolkid@cac.washington.edu)
Lead ACC Lab Assistant, Client Services
University of Washington



On 10 Jan 1995, The Group wrote:

> I'm trying to use Pine to send out announcements 
> to a long list of people, but I don't want the addresses
> to show up in everyone's mailbox.  Does anyone know how 
> send blind carbon copies using Pine?
> 
> Thanks,
> Peter
> Peter Miller
> U. of Illinois Physics Dept.
> peterm@uiuc.edu
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan 10 16:22:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28254;
	Tue, 10 Jan 95 16:22:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07741;
	Tue, 10 Jan 95 16:17:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07735;
	Tue, 10 Jan 95 16:17:02 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRqYP-00038CC; Tue, 10 Jan 95 16:04 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: mimecodes in header (v3.89)
Date: Tue, 10 Jan 1995 13:51:19 -0800
Message-Id: <Pine.ULT.3.92.950110135030.18990J-100000@shiva1.cac.washington.edu>
References: <3etjr9$29d@hermod.uio.no>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3etjr9$29d@hermod.uio.no> 


Pine does not yet support RFC1522 for 8-bit characters in headers.  That
is planned for a future release though... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 10 Jan 1995, Kjell Andresen wrote:

> Date: 10 JAN 1995 09:26:01 GMT 
> From: Kjell Andresen <kjell@ulrik.uio.no>
> Newgroups: comp.mail.pine
> Subject: mimecodes in header (v3.89) 
> 
> I know there is newer pine-versions, but before I start compiling the
> newest version I wonder if this problem is solved:
> 
> As a Norwegian I recieve a lot of mail using mime-characters.
> This is OK in the body (and even the attachments/viewing) of the message,
> but the header is *no* good. In this case the message origin is a mac,
> which is not set up correctly to ISO-8859-1:
> --------------------------
> From Steinar.Moum@usit.uio.no Tue Jan 10 10:23:20 1995
> Date: Tue, 10 Jan 1995 08:01:36 +0100
> Subject: =?NS_4551-1?Q?R=7Cra?= er klar
> 
>     [The following text is in the "NS_4551-1" character set]
>     [Your display is set for the "ISO-8859-1" character set]
>     [Some characters may be displayed incorrectly]
> 
> Fra kl 08.30 og deretter erfaringsvis ca 25 minutter, vil det v{re en
> vaffelsteking (buffret med to jern) p} gang i haven i 3. etg.
> 
> >>>>>>> Mail-programmet er: Eudora 2.1.1  <<<<<<<<<<<
> ---------------------------
> 
> Regards, Kjell
> 
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan 10 16:56:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29659;
	Tue, 10 Jan 95 16:56:45 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08233;
	Tue, 10 Jan 95 16:39:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08223;
	Tue, 10 Jan 95 16:39:40 -0800
Received: by hobbes.twntpe.cdc.com; Wed, 11 Jan 95 08:38:01 -0800
Date: Wed, 11 Jan 1995 08:38:00 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Kjell Andresen <kjell@ulrik.uio.no>
Cc: pine-info@cac.washington.edu
Subject: Re: mimecodes in header (v3.89)
In-Reply-To: <3etjr9$29d@hermod.uio.no>
Message-Id: <Pine.SOL.3.91.950111083519.1179A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 10 Jan 1995, Kjell Andresen wrote:

> I know there is newer pine-versions, but before I start compiling the
> newest version I wonder if this problem is solved:
> 
> As a Norwegian I recieve a lot of mail using mime-characters.
> This is OK in the body (and even the attachments/viewing) of the message,
> but the header is *no* good. In this case the message origin is a mac,
> which is not set up correctly to ISO-8859-1:
> --------------------------
> >From Steinar.Moum@usit.uio.no Tue Jan 10 10:23:20 1995
> Date: Tue, 10 Jan 1995 08:01:36 +0100
> Subject: =?NS_4551-1?Q?R=7Cra?= er klar
> 
>     [The following text is in the "NS_4551-1" character set]
>     [Your display is set for the "ISO-8859-1" character set]
>     [Some characters may be displayed incorrectly]
> 
> Fra kl 08.30 og deretter erfaringsvis ca 25 minutter, vil det v{re en
> vaffelsteking (buffret med to jern) p} gang i haven i 3. etg.
> 

	The current version of pine does not support RFC 1522, which is
MIME in headers RFC.  I believe this is on the "to do" list...but not
sure of the priority.

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Tue Jan 10 17:59:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02561;
	Tue, 10 Jan 95 17:59:54 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09650;
	Tue, 10 Jan 95 17:43:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09640;
	Tue, 10 Jan 95 17:43:04 -0800
Received: by hobbes.twntpe.cdc.com; Wed, 11 Jan 95 09:41:33 -0800
Date: Wed, 11 Jan 1995 09:41:33 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Tammy Barr <barrt@ucs.orst.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Reading news
In-Reply-To: <Pine.OSF.3.91.950110102601.32081B-100000@ucs.orst.edu>
Message-Id: <Pine.SOL.3.91.950111094057.7273B-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 10 Jan 1995, Tammy Barr wrote:

> Is there any detailed documentation available for reading news in Pine?

	You mean in addition to all of the extensive on-line help?

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Tue Jan 10 18:37:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03545;
	Tue, 10 Jan 95 18:37:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13837;
	Tue, 10 Jan 95 18:22:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13824;
	Tue, 10 Jan 95 18:22:17 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRsRn-00038UC; Tue, 10 Jan 95 18:06 PST
To: pine-info@cac.washington.edu
From: nets@netcom.com (H. Paul Hammann)
Subject: Pine on Sparc Solaris 2.4?
Message-Id: <netsD27p8B.H9s@netcom.com>
Date: Tue, 10 Jan 1995 23:00:10 GMT

    I am having a difficult time getting Pine compiled for Solaris 2.4
using gcc 2.6.3.  If anyone that has installed Pine on a sparc Solaris
2.4 box has any hints they'd like to pass along I'd be very grateful.
If there is sufficient interest I'll summarize to this newsgroup.
Thanks in advance for any help.

-- 
Regards,

H. Paul Hammann
Partner
Next Edition Translating Services, L.L.C.
nets@netcom.com


From owner-pine-info@cac.washington.edu  Tue Jan 10 19:36:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04982;
	Tue, 10 Jan 95 19:36:18 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11041;
	Tue, 10 Jan 95 19:21:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11035;
	Tue, 10 Jan 95 19:21:14 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRtUR-00038RC; Tue, 10 Jan 95 19:12 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu
Date: 11 Jan 1995 00:17:42 GMT
Message-Id: <3ev836$kah@cronkite.ocis.temple.edu>

Mark Crispin justifiably said:
 
 +   We hate having to send the canned message.  But there's no choice; we
 +   have to get some work done, otherwise what with state budget cuts there
 +   might not be a Pine team (not that getting work done is any guarantee
 +   that the axe won't fall -- they are in a sour mood in Olympia, and axing
 +   visible efforts as a demonstration of "trimming the fat until it hurts"
 +   is very Politically Correct).  Please keep the bouquets and testimonials
 +   coming -- it *does* help in justifying our continued existance!

According to Syd, the Elm Team needs to find an oasis pretty soon, else it
might .... due to excessive heat and no water. We would *hate* to see that
repeat .......esp. to The Pine Team.

Muchos Kudos to you Folks!! Great Job !! Keep up the good work!!

We need better and better versions of Pine. We don't need some salesman
plastic politeness/b.s. I/we get that enough already.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 19:47:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05298;
	Tue, 10 Jan 95 19:47:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14869;
	Tue, 10 Jan 95 19:32:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14863;
	Tue, 10 Jan 95 19:32:51 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRtaZ-00038SC; Tue, 10 Jan 95 19:19 PST
To: pine-info@cac.washington.edu
From: iveysoto@vesta.unm.edu (Daniel A Ivey-Soto)
Subject: Re: blind carbon copies
Date: 11 Jan 1995 01:23:02 GMT
Message-Id: <3evbtm$f4e@lynx.unm.edu>
References: <3eutog$9sb@vixen.cso.uiuc.edu>

	In order to use the BCC feature, first type ^R while the curser is
in the header of the document you wish tosend.  This invokes the "Rich
Header"  feature.  Then, in the line titled BCC, just place all the names
as you normally would in the TO: line. 

	Whenever I do this I usually place a descriptive name in the TO: 
line, just for effect.  To do this, remember to use quotes if it is more 
than one word.  PINE then adds your domain name at the end.  When you 
send the message your original one will come back to you as 
undeliverable, since it was a dummy, though descriptive address.

					Hope this helps,


					Daniel.


The Group (group@uiuc.edu) wrote:
: I'm trying to use Pine to send out announcements 
: to a long list of people, but I don't want the addresses
: to show up in everyone's mailbox.  Does anyone know how 
: send blind carbon copies using Pine?

: Thanks,
: Peter
: Peter Miller
: U. of Illinois Physics Dept.
: peterm@uiuc.edu


--

                                       Take care,


                                       Daniel.


From owner-pine-info@cac.washington.edu  Tue Jan 10 19:50:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05335;
	Tue, 10 Jan 95 19:50:23 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11303;
	Tue, 10 Jan 95 19:36:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11297;
	Tue, 10 Jan 95 19:36:13 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRthC-00038RC; Tue, 10 Jan 95 19:26 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: News Collection - Empty List
Date: 11 Jan 1995 00:25:08 GMT
Message-Id: <3ev8h4$kah@cronkite.ocis.temple.edu>

Comes here Mr. Ponnusamy Rajendran with this opinion in the "comp.mail.pine"
group in this article on Tue, 10 Jan 1995 05:56:30 GMT:

 +   We have Pine 3.91 running on a SunOS4.1.x system. When expanding 
 +   the News Collection folder I get

 +     [ ** Empty List **  Select Here to Try Re-Expanding ]

 +   message.  But when telnet to port 119 (for nntp services) on the 
 +   news server, I can see the news group listing.

You probably are missing a ".newsrc" file which is what Pine looks up for
newsgroup local subscription info. Bascically it is the list of all the
newsgroups that you have subscribed to. Your local NewsAdmin will know.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 19:50:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05337;
	Tue, 10 Jan 95 19:50:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14915;
	Tue, 10 Jan 95 19:36:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14909;
	Tue, 10 Jan 95 19:36:17 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRthE-00038XC; Tue, 10 Jan 95 19:26 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: FAQ, please
Date: 11 Jan 1995 00:27:43 GMT
Message-Id: <3ev8lv$kah@cronkite.ocis.temple.edu>

Comes here Mr. WITTMANS@axe.humboldt.edu with this opinion in "comp.mail.pine"
group in this article on Tue, 10 Jan 1995 03:00:39 GMT:

Here's the URL:

ftp://ftp.cac.washington.edu/pine/docs

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 20:09:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05851;
	Tue, 10 Jan 95 20:09:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11679;
	Tue, 10 Jan 95 20:02:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11673;
	Tue, 10 Jan 95 20:02:30 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRu7i-00038UC; Tue, 10 Jan 95 19:53 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Home directory
Date: 11 Jan 1995 00:43:06 GMT
Message-Id: <3ev9iq$kah@cronkite.ocis.temple.edu>

Comes here Mr. Ray McAllister with this opinion in the "comp.mail.pine" group in
this article on Tue, 10 Jan 1995 02:24:02 -0500 (EST):

 +   	Question 1, Please help! How can I access or see what is in my "Home 
 +   Directory"? I cannot seem to find it anywhere on either hard drive, to see
 +   what is in it; to use it, or to delete it. Thanks a million.

/u3/mcallist

That is your "home directory"/"Home Directory"
Here's where you will see all the files that belongs to your account.
/u3/mcallist/mail will be the dir. where you will see all your mail folders.

 +   	Question 2, Where or how can I get a manual for Pine?

ftp://ftp.cac.washington.edu/pine/docs

 +   	Question 3, When I go into rz to bring a pre-existing file into 
 +   my home directory I sometimes end up with the Procom 2 screen telling me 
 +   Port in use, yet I have hung up. How can I get rid of Port in use and 
 +   continue with Procom and pine without closing everything back to C:?

set port port##

Aah! here you seem to know about home directory.
BTW this modem question really doesn't belong to comp.mail.pine or does it?

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 20:19:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06124;
	Tue, 10 Jan 95 20:19:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15562;
	Tue, 10 Jan 95 20:15:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15556;
	Tue, 10 Jan 95 20:15:27 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29362;
	Tue, 10 Jan 95 20:15:24 -0800
Date: Tue, 10 Jan 1995 20:15:23 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Wet-Sprocket <shrim@astro.ocis.temple.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: News Collection - Empty List
In-Reply-To: <3ev8h4$kah@cronkite.ocis.temple.edu>
Message-Id: <Pine.ULT.3.92.950110201255.7374A-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

One clarification: The .newsrc really only needs to include the 
newsgroups to which one is subscribed.  If it is currently empty,
or non-existent, one needs to use the "A Add" command to subscribe.

(We know that this is far from obvious.... sorry.  Also, we know that it 
is a pain to only be able to subscribe to one group at a time.)

-teg

On 11 Jan 1995, Wet-Sprocket wrote:

> Comes here Mr. Ponnusamy Rajendran with this opinion in the "comp.mail.pine"
> group in this article on Tue, 10 Jan 1995 05:56:30 GMT:
> 
>  +   We have Pine 3.91 running on a SunOS4.1.x system. When expanding 
>  +   the News Collection folder I get
> 
>  +     [ ** Empty List **  Select Here to Try Re-Expanding ]
> 
>  +   message.  But when telnet to port 119 (for nntp services) on the 
>  +   news server, I can see the news group listing.
> 
> You probably are missing a ".newsrc" file which is what Pine looks up for
> newsgroup local subscription info. Bascically it is the list of all the
> newsgroups that you have subscribed to. Your local NewsAdmin will know.
> 
> --
>       o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
>     o      _____            |  /__                 | | Compt. Svcs.  |
>   .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
>  >(________|__|_[_________]_|______________________|_|_______________|_
>  _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
> ========================================================================
> Talk about me doing the talking for others, esp. My Employers!!
> Mac*CHAT List Moderator.
> 


From owner-pine-info@cac.washington.edu  Tue Jan 10 21:10:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07426;
	Tue, 10 Jan 95 21:10:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16386;
	Tue, 10 Jan 95 21:06:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16380;
	Tue, 10 Jan 95 21:06:28 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRv8Z-00038dC; Tue, 10 Jan 95 20:58 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Adding to addressbook answered (and a ?? of my own)
Date: 11 Jan 1995 01:10:58 GMT
Message-Id: <3evb72$kah@cronkite.ocis.temple.edu>

Comes here Mr. Frank Yao with this opinion in the "comp.mail.pine" group in this
article on Tue, 10 Jan 1995 09:55:54 GMT:

 +   In article <Pine.SUN.3.91.950106165903.6579A-100000@antares>,
 +   Keith M. Rainey <kmr@engr.latech.edu> wrote:

 +   >	I use a lot of lists in my addressbook and I am constantly
 +   >changing lists, and adding new lists.  Is there a way to append a
 +   >text file of addresses into the .addressbook file?  It would make 
 +   >my life a little easier (since I'm so lazy).  Also, is there a
 +   >way to send address lists to other users without them having to 
 +   >type in all of the names?

 +   I would think doing something like:  cat text.file >> .addressbook 

See I'm not sure that's gonna work as .addressbook is kinda uniquely formatted.
I haven't tried this but if you have a file which is tab separated in this way

first column: nickname
second column: Full Name
third column: complete e-mail address

and each column separated by a tab and then if you cat that file to .addressbook
it might work. Before you try this make sure you make a backup copy of your
.addressbook and .addressbook.lu files.

In Pine 3.91 which was what you are using, you can import a list of addressess
into a new/existing addressbook list. Great Job, kudos to Pine Team!!

And to your second question just send your .addressbook file to whoever you
want it to be sent. Ofcourse I wouldn't include personal address nicknames in
that case.

 +   In the index screen, we get a flag (N,D,A etc), the sender, the size
 +   and the subject.  What exactly is that size indicating, and is there a
 +   way to change it to reflect the number of LINES in the mail message?

The SIZE of each indivual mail in bytes. Number of lines?
If you find out..post it.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 21:27:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08124;
	Tue, 10 Jan 95 21:27:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16716;
	Tue, 10 Jan 95 21:22:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16710;
	Tue, 10 Jan 95 21:22:42 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRvEw-00038gC; Tue, 10 Jan 95 21:04 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: blind carbon copies
Date: 11 Jan 1995 01:29:26 GMT
Message-Id: <3evc9m$kah@cronkite.ocis.temple.edu>

Comes here Mr/Mz. The Group with this opinion in the "comp.mail.pine" group in
this article on 10 Jan 1995 21:21:20 GMT:

 +   I'm trying to use Pine to send out announcements 
 +   to a long list of people, but I don't want the addresses
 +   to show up in everyone's mailbox.  Does anyone know how 
 +   send blind carbon copies using Pine?

Place your cursor at the To: header region and hit Control-R for Rich-Headers.
You will see a Bcc: header, just fill in here the entire list but be told that
there's a limit to how many addressess you can have per header (think itz < 50)

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 21:36:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08293;
	Tue, 10 Jan 95 21:36:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13047;
	Tue, 10 Jan 95 21:22:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13041;
	Tue, 10 Jan 95 21:22:40 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rRvEv-00038XC; Tue, 10 Jan 95 21:04 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: pine? lost ^c command
Date: 11 Jan 1995 01:22:05 GMT
Message-Id: <3evbrt$kah@cronkite.ocis.temple.edu>

Comes here Mr. Mike Deem with this opinion in the "comp.mail.pine" group in this
article on Tue, 10 Jan 1995 03:30:49 GMT:

 +   Can't control my cancel or arrow commands . Does anyone know What could 
 +   be the problem.

If ^C doesn't work, try using this key combination:
esc esc c (twice hit the escape key and then hit the c key)

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 10 23:41:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10973;
	Tue, 10 Jan 95 23:41:05 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18556;
	Tue, 10 Jan 95 23:34:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from cas.crc.edu.ph by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18550;
	Tue, 10 Jan 95 23:34:42 -0800
Received: from NOVELL_SERVER/TEMPQ by othello.crc.edu.ph (Mercury 1.12);
    Wed, 11 Jan 95 11:22:17 +0800
Received: from TEMPQ by NOVELL_SERVER (Mercury 1.12); Wed, 11 Jan 95 11:21:58 +0800
From: "Rafael G. Portillo" <RAFA@othello.crc.edu.ph>
Organization:  CRC College of Arts and Sciences
To: Steve Hubert <hubert@cac.washington.edu>
Date:          Wed, 11 Jan 1995 11:21:55 +0800
Subject:       Re: Bugggggggy pinedemo at demo.cac.washington.edu
Cc: Pine Information List <pine-info@cac.washington.edu>
X-Confirm-Reading-To: "Rafael G. Portillo" <RAFA@othello.crc.edu.ph>
X-Pmrqc:       1
Priority: normal
X-Mailer: Pegasus Mail v3.22
Message-Id: <4018C2ED0@othello.crc.edu.ph>

> On Mon, 9 Jan 1995, Lev A. Gorenstein wrote:
> 
> > Guys, 
> > 
> > Shame on you!  I understand that you're busy because people are sending 
> > you bullshit questions (and the amount of bullshit is much more than the 
> > amount of gold in it).  But still, what you've done is, well, let's say
> > "impolite", though some other words are on the tip of my tongue.  I 
> > received the AUTOMATED answer from you A WEEK (!!!) after I sent you my 

    (more stuff along the same line...)

> > ____________________________________________
> >   Lev A. Gorenstein
> >   Chemistry Department
> >   Purdue University
> >   W.Lafayette, IN 47907, USA
> >   (317)494-5289; Fax (317)494-0239
> >   lev@chem.purdue.edu
> 

I get the impression that YOU are the one being impolite (no other
words in the tip of my tongue).  If a simple bug report makes you
react that way, you may consider taking a vacation, or getting some
professional help.    

My experience when I reported a bug to cac was very positive.

Happy 1995...

Rafa---------------------------------------------------------------------
Rafael (Rafa) G. Portillo           CRC College of Arts and Sciences
rafa@cas.crc.edu.ph                 Pasig, Metro Manila
rafa@othello.crc.edu.ph             Philippines


From owner-pine-info@cac.washington.edu  Wed Jan 11 00:52:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12619;
	Wed, 11 Jan 95 00:52:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15710;
	Wed, 11 Jan 95 00:43:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from sun2.nsfnet-relay.ac.uk by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15704;
	Wed, 11 Jan 95 00:43:55 -0800
Via: uk.ac.durham; Wed, 11 Jan 1995 08:43:35 +0000
Received: from venus.dur.ac.uk by durham.ac.uk; Wed, 11 Jan 95 08:43:25 GMT
Received: from hercules (hercules.dur.ac.uk) by venus.dur.ac.uk;
          Wed, 11 Jan 95 08:43:11 GMT
Date: Wed, 11 Jan 1995 08:43:06 +0000 (GMT)
From: Barry Cornelius <Barry.Cornelius@durham.ac.uk>
To: Tammy Barr <barrt@ucs.orst.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Reading news
In-Reply-To: <Pine.OSF.3.91.950110102601.32081B-100000@ucs.orst.edu>
Message-Id: <Pine.SOL.3.91-941213.950111084038.19534A-100000@hercules.dur.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 7474

Tammy Barr writes:
> Is there any detailed documentation available for reading news in Pine?

Last October, I produced a document for the transition from 3.89 to 3.90.
Part of it referred to accessing Usenet News from Pine.  The details are
given below (and are equally applicable to Pine 3.91).  

Note: the text of Section 13 refers to Sections 6 and 12 which are given
later in this message. 

: 13. Accessing Usenet News from Pine
: 
: In previous versions of Pine, you were able to read the newsgroups of
: Usenet News.  In Pine 3.90, there are additional facilities, e.g., you
: can subscribe/unsubscribe to newsgroups and post articles to
: newsgroups.
: 
: In order to access Usenet News, you should go to the Config Screen (see
: Section 6), move the cursor down to the line starting "nntp-server =",
: press A (for Add Text) and then type the address of an nntpserver:
:    newsserver.site.domain 
: Note that it is not necessary to set the news-collections variable.
: Although optional, I believe it is also useful to include both
: compose-sets-newsgroup-without-confirm and expanded-view-of-folders in
: the setting of the feature-list variable.  To do this, move down to
: compose-sets-newsgroup-without-confirm and press X; and then move down
: to expanded-view-of-folders and press X.
: 
: You will now need to leave Pine, and re-start it.  If you then press L
: to get the folder-list you will see a section headed News-collection.
: If you move to this section, you can press A followed by the name of a
: newsgroup in order to subscribe to that newsgroup.  If you are
: uncertain about the name, then follow the A by Ctrl-T in order to list
: the names of all the newsgroups.  If you press W at this point, you
: can find out those newsgroups whose names contain a particular string.
: 
: The information about which newsgroups you are subscribed to is
: written to the file .newsrc.  If you don't want your subscribed
: newsgroups to be displayed in alphabetical order, you may set the
: news-read-in-newsrc-order feature.  To do this, go to the Config Screen
: (see Section 6) and then move the cursor down to the line containing
: news-read-in-newsrc-order and press X.  You also need to edit your
: .newsrc file so that the lines appear in the order that you wish to
: look at the newsgroups.
: 
: Once you have subscribed to the newsgroups which you think you may be
: interested, you can use them just like mail folders.  
: 
: When you have read an article, you can use the D command to record the
: fact that you have already seen it.  This information is also stored
: in the .newsrc file.  In this way, the article will not be presented
: to you the next time you read Usenet News.
: 
: If you already have the folder for a newsgroup open, you can use the C
: command to post an article to the newsgroup.  If you want to follow-up
: an existing article, or you want to reply to the sender of an article,
: use the R command.
: 
: Some newsreaders provide "threading", a facility where all the
: articles of a newsgroup which have the same subject are grouped
: together.  You can arrange for Pine to present the articles of a
: folder index sorted into threads by pressing $ followed by o whilst
: you are in the folder index.  This only has an effect on the folder
: index: it does not actually alter the folder.
: 
: Although Pine does not have a command to "catch up" in a newsgroup
: (that is, to mark all the articles as deleted), you can use Pine's new
: aggregate command set (see Section 12) to do this.  Pressing the four
: keys ;aad will cause all the articles in the current folder to be
: marked as deleted.  So these articles will not be shown the next time
: you enter the newsgroup.

The above text refers to Sections 6 and 12 which are
reproduced below:
 
: 6.  Configuring Pine using the "Config Screen"
: 
: In previous versions of Pine, you had to alter the .pinerc file if you
: wanted to configure Pine.  In Pine 3.90, you can configure Pine by
: going to the Setup Configuration Screen (which is called the "Config
: Screen" in this document).  To find this screen, go to the Main Menu,
: press S followed by C.
: 
: You can use the Config Screen to change the settings of some of Pine's
: variables.  If you are uncertain as to the purpose of a variable (or a
: value), move the cursor so that the appropriate line of the Config
: Screen is highlighted, and press ? (for Help).  Any changes that you
: make to the Config Screen will eventually be written to your .pinerc
: file.  For many changes, the change that you want will be effected
: immediately: however, for other changes you will need to leave Pine
: and then re-start it.
: 
: 12. Using aggregate commands
: 
: The A, Z and ; commands form the "aggregate command set".  The ;
: command allows you to select all the messages that match some
: criteria; the A command allows to apply some command to each of the
: selected messages; and the Z command allows you to zoom in on the
: selected messages by changing the folder index temporarily so that
: only these messages are displayed.  In order to use any of these
: commands, you need to have enable-aggregate-command-set included in
: the setting of the feature-list variable.  To do this, go to the
: Config Screen (see Section 6) and then move the cursor down to the line
: containing enable-aggregate-command-set and press X.
: 
: Here are some more details about the aggregate commands.
: 
: The ; command selects messages in the folder index according to a
: criterion that you choose.  It can be one of the following: (a) all
: messages, (b) a list or a range of message numbers, (c) messages
: containing a particular string within the From, To, Cc or Subject
: lines or within the entire text of the message, (d) the current
: message, (e) messages on/before/since a specified date, (f) messages
: that have a status flag of new/deleted/answered/important.
: 
: Having chosen the criterion, the selected messages are indicated in
: the folder index by a X in the first column (unless the
: show-selected-in-boldface feature has been chosen).  There is another
: way in which you can show which messages have been selected: if you
: issue a Z command after a ; command it will temporarily restrict the
: folder index to the selected messages --- pressing Z again returns you
: to the full folder index.
: 
: If you have already used a ; command (to select a set of messages),
: then, if you type ; command again, Pine will ask you whether you want
: to (i) unselect all the selected messages, (ii) unselect the current
: message, (iii) add more messages to the set of selected messages, (iv)
: remove some messages from the set of selected messages.  If you choose
: (iii) or (iv), then you can indicate the criterion by which messages
: are added to, or removed from, the current selection.  Once again, the
: criterion can be any of those labelled (a) to (f) above.
: 
: Having selected a set of messages, you can use the A command to apply
: any of the following operations to the set of selected messages: save,
: export, print, delete, undelete, reply, forward, takeaddr, flag or
: pipe.

--
Barry Cornelius                      Telephone: (0191 or +44 191) 374 4717
Academic Support Group, IT Service,            IT Service Office: 374 2892   
Science Site, University of Durham,                          Fax: 374 3741
Durham, DH1 3LE, UK                   E-mail: Barry.Cornelius@durham.ac.uk



From owner-pine-info@cac.washington.edu  Wed Jan 11 01:48:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14397;
	Wed, 11 Jan 95 01:48:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20436;
	Wed, 11 Jan 95 01:41:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from leeman.york.ac.uk by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20430;
	Wed, 11 Jan 95 01:41:05 -0800
Received: from unix.york.ac.uk by leeman.york.ac.uk with SMTP (PP) 
          id <27058-0@leeman.york.ac.uk>; Wed, 11 Jan 1995 09:31:44 +0000
Received: by tower.york.ac.uk (940816.SGI.8.6.9/940406.SGI) id JAA10963;
          Wed, 11 Jan 1995 09:41:04 GMT
Date: Wed, 11 Jan 1995 09:41:04 +0000 (GMT)
From: Mike Brudenell <pmb1@tmphost.york.ac.uk>
X-Sender: pmb1@tower.york.ac.uk
To: Trey Harris <harris@email.unc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: zero-length .pine-interrupted-mail files
In-Reply-To: <3euh21$12np@bigblue.oit.unc.edu>
Message-Id: <Pine.SGI.3.91.950111093850.9824A-100000@tower.york.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Strange... I had to deal with exactly the same problem only yesterday.  
Traced it eventually to the empty interrupted mail file (Pine was 
aborting with a bug detected).

There's also a weakness in the Bezerk mailbox handling if (for whatever 
reason) the last message in the file has the separating "From blah" line 
but no further lines afterward.  We had a few of these appear when our 
mail delivery system threw a wobbler; Pine just aborts with a bug detected.

Mike Brudenell
------------------------------------------------------------------------------
The Computing Service, University of York, Heslington, York, YO1 5DD, UK
Phone: +44-(0)1904-433811  FAX: +44-(0)1904-432767

On 10 Jan 1995, Trey Harris wrote:

> I am running Pine 3.91 on a 15,000-user AIX 3.2.5 site.  Among these 
> users, the most common problem they experience with Pine (our Help Desk 
> says they get this question several times a day) is zero-length 
> .pine-interrupted-mail* files in the home directory.
> 
> What happens when they get these is this: Pine tells them they have 
> postponed mail, and asks if they wish to continue.  When the user answers 
> "Yes", it either says "You don't have any interrupted mail!" and goes 
> back to the menu/index, or it core dumps with an "abend" error.
> 
> As far as I am able to tell, Pine *never* produces a non-zero-length 
> pine-interrupted-mail* file.
> 
> We had this problem with even greater frequency than is now the case, but 
> I was able to allieviate the problem to some degree by recompiling Pine.  
> I had originally compiled Pine without "-DDEBUG" because pine-debug files 
> were accumulating on our system, and sometimes Pine would go out of 
> control and continue to write to a pine-debug file until the filesystem 
> was full.
> 
> Once I restored "-DDEBUG" (setting the default debug level to 0) the 
> .pine-interrupted-mail files were reduced, but they still occur.
> 
> Can anyone suggest how we can fix this?  It is extremely annoying to both 
> our Help Desk and our users.
> -- 
> Trey Harris                              http://sunsite.unc.edu/harris
>   System Administrator, Project Isis, Office of Information Technology
>                        The University of North Carolina at Chapel Hill
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 04:12:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18369;
	Wed, 11 Jan 95 04:12:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18188;
	Wed, 11 Jan 95 04:01:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from cheviot.ncl.ac.uk by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18172;
	Wed, 11 Jan 95 04:01:39 -0800
Received: from monera.newcastle.ac.uk by cheviot.ncl.ac.uk id <MAA05626@cheviot.ncl.ac.uk>
  (8.6.9/ for ncl.ac.uk) with SMTP; Wed, 11 Jan 1995 12:01:14 GMT
Date: Wed, 11 Jan 1995 12:01:12 +0000 (GMT)
From: Alan Ward <Alan.Ward@newcastle.ac.uk>
To: pine-info@cac.washington.edu
Subject: Re: You get what you pay for
Message-Id: <Pine.SUN.3.91.950111115804.4981B-100000@monera>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 'Apologies ...', instant response etc I agree - you can *hope* to get 
what you pay for (you shouldn't *expect* to get what you don't pay for,
though you might)
but I also think 
	you could never have got Pine just by paying for it

Many thanks to UoW, because they *have* paid for it - but they've got
more than they paid for.
Many thanks to all the active Pine community, (as well as the Pine team)
who contribute, try things out, supply work-arounds, answer questions ...
-- 
Email: Alan.Ward@ncl.ac.uk		Alan Ward
FAX: +44 (0) 91 222 7736		Department of Microbiology
Tel: +44 (0) 91 222 7709		University of Newcastle upon Tyne

On 10 Jan 1995, Ralph Sims wrote:

> lev@cv4.chem.purdue.edu (Lev A. Gorenstein) writes:
> ..... irrelevant stuff .....
> >YOUR server.   Damn, I expect apologees!
> 
> One might quip "You get what you pay for."




From owner-pine-info@cac.washington.edu  Wed Jan 11 06:39:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22917;
	Wed, 11 Jan 95 06:39:31 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24457;
	Wed, 11 Jan 95 06:30:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.ge.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24451;
	Wed, 11 Jan 95 06:30:03 -0800
Received: from [3.12.38.33] by ns.GE.com (5.65/GE Gateway 1.32) with SMTP
	 id AA06180; Wed, 11 Jan 1995 09:29:51 -0500
Received: by mmpcs1.PSF.GE.COM (4.1/GEA Sun server 2.7)
	id AA09375; Wed, 11 Jan 95 09:28:21 EST
Date: Wed, 11 Jan 1995 09:28:20 -0500 (EST)
From: Don Sugarman <sugarman@mmpcs1.psf.ge.com>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Pine features
In-Reply-To: <Pine.ULT.3.92.950109115608.2851o-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.90.950111090116.8926A-100000@mmpcs1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Greetings and HELP.  

The PINE folks suggested that I post my questions to the List, so here goes.

I am trying to identify an e-mail program that will serve the 
majority of 2100 people at our facility.  The people in the facility 
currently use MicroSoft Mail (Mac and PC),  PROFS, Unix Mail, Elm, and (a 
few smart ones) PINE.  Our local computer resources include Sun and VAX 
VMS servers, all tied together on a high-speed LAN.  In addition, there 
are a number of individuals who log in locally or remotely via a 
low-speed LAN through a bridge to the high speed LAN and/or to the IBM PROFS 
gateway.

I have been using PINE since discovering it in August.  (I needed a 
program that would handle MIME encoded messages.)  I am very pleased with 
the program, and I am trying to promote it here.

While we would like all users to have a single system address for their 
mail drop, we anticipate that they will want to forward their mail to 
their local Sun server or MS Mail inbox.  We recognize that the Sun 
servers we have bog down with more than 15-20 concurrent logins, so we 
are setting up a pair of VAX systems as a common e-mail server.

1) Does anyone have any information on portability of PINE to VAX VMS? (It
was not listed with successful ports in the August pine-ports file, and
there was no indication whether it had been tried unsuccessfully? 

2) Has anyone tried to incorporate message acknowledgement functionality into
PINE?  That is if a message is sent registered by Pine, a Pine program on
the receiving end would send an registered receipt to the originator when
the message was read.  We have a program on the AT&T that embeds a code of
the form "[R(nnnn)]" in the subject of a registered message.  When the
program receives a message with this code, it sends a registered receipt
under the recipient's login indicating message nnnn was read with the
subject, time, and date.  See below: 

 Receipt Header:  

 From <recipient of registered message>
 To: <sender of registered message>
 Subject: Registered Mail Receipt [A(nnnn)]
 Status: RO
 
 Receipt message:
 
      Your registerd mail message has been reeived and read: 
 
      RECIPIENT:          <recipient of registered message>
      DATE:               <date and time message was read>
      SUBJECT:            <subject of original message>

3) Has anyone tried to incorporate a uuencode recognition/filter into
PINE?  We correspond with users of MicroSoft Mail and CC:MAIL, and would
like to be able to choose between MIME and uuencode on send and to have
PINE recognize both forms on receipt. 

Thanks in advance for any help/info you can provide.

Don

Don Sugarman, Senior Project Engineer
Martin Marietta Defense Systems
Pittsfield, MA 
sugarman@mmpcs1.psf.ge.com


From owner-pine-info@cac.washington.edu  Wed Jan 11 07:55:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25462;
	Wed, 11 Jan 95 07:55:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25896;
	Wed, 11 Jan 95 07:46:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25890;
	Wed, 11 Jan 95 07:46:24 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id HAA01021 for <pine-info@cac.washington.edu>; Wed, 11 Jan 1995 07:46:23 -0800
Date: Wed, 11 Jan 1995 07:46:24 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: The Group <group@uiuc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: blind carbon copies
In-Reply-To: <3eutog$9sb@vixen.cso.uiuc.edu>
Message-Id: <Pine.SUN.3.91.950111073736.8703A-100000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 10 Jan 1995, The Group wrote:

> I'm trying to use Pine to send out announcements 
> to a long list of people, but I don't want the addresses
> to show up in everyone's mailbox.  Does anyone know how 
> send blind carbon copies using Pine?
> 
> Thanks,
> Peter
> Peter Miller
> U. of Illinois Physics Dept.
> peterm@uiuc.edu
> 
> 

I wanted to do the same thing, but if I'm understanding you correctly, it 
can't be done with blind cc's.

What I think you want to do is send mail to a long list of people, but 
have only that person's name show on the To: line.  As far as I know, 
this can't be done without a mailing robot.

The only thing that's blind about a Bcc: is that the people in the To: 
address can't see the addresses of the people in Bcc:, but the people in 
Bcc: can see everything.


---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646




From owner-pine-info@cac.washington.edu  Wed Jan 11 08:02:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25804;
	Wed, 11 Jan 95 08:02:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26011;
	Wed, 11 Jan 95 07:53:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from alpha.loyno.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26005;
	Wed, 11 Jan 95 07:53:28 -0800
Received: by alpha.loyno.edu; (5.65/1.1.8.2/22Jul94-0234PM)
	id AA05345; Wed, 11 Jan 1995 09:54:56 +0100
Date: Wed, 11 Jan 1995 09:54:55 +0100 (MET)
From: Mary Aplin <aplin@alpha.loyno.edu>
To: pine <pine-info@cac.washington.edu>
Subject: Compiling PINE
Message-Id: <Pine.OSF.3.91.950111094838.5330A-100000@alpha.loyno.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello All --

I've just compiled PINE 3.91 under OSF on my DEC Alpha 3300.  

I have a second Alpha 3300, but it does not have the same software setup 
and the first, and I cannot compile PINE on this system;  it bombs out.

When we were running PINE 3.90 I had successfully FTP'd pine over to my 
second Alpha system, and it ran just fine.  (Acutally, I FTP'd pine, 
pico, imapd, and mtest over to the /usr/bin directory)  I just tried to 
FTP PINE 3.91 over to my second Alpha, (in the same directory) and I can't 
get it to run.  The error is   pine: cannot execute

What parts of PINE 3.91 need to be present (and where) in order for it to 
execute?

Thanks
Mary Aplin
Loyola University, New Orleans


From owner-pine-info@cac.washington.edu  Wed Jan 11 08:04:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25893;
	Wed, 11 Jan 95 08:04:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25993;
	Wed, 11 Jan 95 07:51:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25985;
	Wed, 11 Jan 95 07:51:57 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rS5AT-00038KC; Wed, 11 Jan 95 07:41 PST
To: pine-info@cac.washington.edu
From: Bob Burge <burger@cspo.queensu.ca>
Subject: Re: blind carbon copies
Date: Tue, 10 Jan 1995 21:48:59 -0600
Message-Id: <Pine.SOL.3.91.950110214800.2168B-100000@cspo>
References: <3eutog$9sb@vixen.cso.uiuc.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3eutog$9sb@vixen.cso.uiuc.edu> 

On 10 Jan 1995, The Group wrote:

> I'm trying to use Pine to send out announcements 
> to a long list of people, but I don't want the addresses
> to show up in everyone's mailbox.  Does anyone know how 
> send blind carbon copies using Pine?

Go up to the header and get "rich header" -- ctrl-r on 3.91.  Send it to 
yourself, and Bcc it to the rest.

Bob



From owner-pine-info@cac.washington.edu  Wed Jan 11 08:06:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26004;
	Wed, 11 Jan 95 08:06:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22152;
	Wed, 11 Jan 95 07:59:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22146;
	Wed, 11 Jan 95 07:59:37 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rS5Hi-00038YC; Wed, 11 Jan 95 07:48 PST
To: pine-info@cac.washington.edu
From: pucho@netcom.com (Marcos Rubinstein)
Subject: Re: Does a Pine "Viewer" Program for PC Exist?
Message-Id: <puchoD28CHF.A8G@netcom.com>
References: <3espua$pvu@solar.sky.net>
Date: Wed, 11 Jan 1995 07:22:27 GMT

Yes Fred... there is a Santa Claus... :)
and it's called "readmail"....
is an offline reader..*not* an offline mailer.... but I think it will 
serve your purpose...
you can find it at the simtel mirror at
oak.oakland.edu
(if you have lynx... try http://www.oak.oakland.edu )
(if not, you can ftp to oak.oakland.edu )

Pucho
(another packrat)


Fred Potter (fpotter@solar.sky.net) decia:
: Hi folks.  This may sound goofy but here goes.

: I prefer *not* to use all the graphical stuff via SLIP etc. that is
: available because text is faster for me at 14.4.  I'm kind of a packrat
: and I save all my mail.  Here's what I'd like to do: download my
: saved-messages and sent-mail files from my Internet provider, store them
: on floppies and then view them on my PC with a small DOS program that
: looks like the Pine interface.  That way I could view the "directory" of
: messages by subject line and date as though I was online.  It would keep
: my workspace cleaned out, which would make my sysop happy.  The
: alternative is scrolling through the entire file with a text editor or
: something.  

: Is there such a program for DOS?

: Thanks,
: Fred


From owner-pine-info@cac.washington.edu  Wed Jan 11 10:06:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02592;
	Wed, 11 Jan 95 10:06:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29224;
	Wed, 11 Jan 95 09:57:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29216;
	Wed, 11 Jan 95 09:57:15 -0800
Received: by rain.psg.com (Smail3.1.28.1 #7)
	id m0rS76h-00038KC; Wed, 11 Jan 95 09:45 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: alt editor not use TEMP: Bug or feature?
Date: Wed, 11 Jan 1995 17:27:49 +0000
Message-Id: <Pine.SUN.3.91.950111171847.17995L-100000@bootes.cus.cam.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

One of my (new) user of PC-PINE is complaining at the following.
When calling the editor, Pine (appears) to specify a file name in the 
root directory. This means that if the editor makes backups of files as 
they are being made (eg on a time basis) they pile up in root. In 
addition, should a reboot occur (even when using Pico), broken bits are left 
also in root.

He states, and I think that I agree with him, that the Dos TEMP variable 
should be used (if present) to indicate a suitable temporary directory. 
In some circumstances, Pine uses TMP, but not in this one.

Do others agree that this is a bug?

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Wed Jan 11 11:15:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05867;
	Wed, 11 Jan 95 11:15:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01072;
	Wed, 11 Jan 95 11:07:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from alpha.loyno.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01066;
	Wed, 11 Jan 95 11:07:08 -0800
Received: by alpha.loyno.edu; (5.65/1.1.8.2/22Jul94-0234PM)
	id AA05621; Wed, 11 Jan 1995 13:08:36 +0100
Date: Wed, 11 Jan 1995 13:08:36 +0100 (MET)
From: Mary Aplin <aplin@alpha.loyno.edu>
To: pine <pine-info@cac.washington.edu>
Subject: Re: Compiling PINE
In-Reply-To: <Pine.OSF.3.90.950111103532.434A-100000@alpha.mhcc.cc.or.us>
Message-Id: <Pine.OSF.3.91.950111130741.5610B-100000@alpha.loyno.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Wed, 11 Jan 1995, Jeff Moore wrote:

> On Wed, 11 Jan 1995, Mary Aplin wrote:
> 
> > Hello All --
> > 
> > I've just compiled PINE 3.91 under OSF on my DEC Alpha 3300.  
> > 
> > I have a second Alpha 3300, but it does not have the same software setup 
> > and the first, and I cannot compile PINE on this system;  it bombs out.
> > 
> > When we were running PINE 3.90 I had successfully FTP'd pine over to my 
> > second Alpha system, and it ran just fine.  (Acutally, I FTP'd pine, 
> > pico, imapd, and mtest over to the /usr/bin directory)  I just tried to 
> > FTP PINE 3.91 over to my second Alpha, (in the same directory) and I can't 
> > get it to run.  The error is   pine: cannot execute
> > 
> > What parts of PINE 3.91 need to be present (and where) in order for it to 
> > execute?
> > 
> > Thanks
> > Mary Aplin
> > Loyola University, New Orleans
> > 
> I don't know about v3.91 but v3.90 is totally self-contained.  I'm 
> running it on a DEC 3000-300.  This may sound stupid, but have you set 
> the program to be executable using the chmod command?  I know that I had 
> to do that in order for it to run on my system.
> 
> 
That did the trick!!!  
Thanks Jeff!!!


From owner-pine-info@cac.washington.edu  Wed Jan 11 11:32:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06429;
	Wed, 11 Jan 95 11:32:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27289;
	Wed, 11 Jan 95 11:21:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from THOR.INNOSOFT.COM by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27283;
	Wed, 11 Jan 95 11:21:48 -0800
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.3-13 #2001)
 id <01HLPUUM3J468ZE4OD@INNOSOFT.COM>; Wed, 11 Jan 1995 11:03:37 -0700 (PDT)
Date: Wed, 11 Jan 1995 11:03:36 -0700 (PDT)
From: Portia Shao <PORTIA@INNOSOFT.COM>
Subject: Re: Pine features
In-Reply-To: <Pine.SUN.3.90.950111090116.8926A-100000@mmpcs1>
To: Don Sugarman <sugarman@mmpcs1.psf.ge.com>
Cc: Pine Information List <pine-info@cac.washington.edu>
Reply-To: Portia Shao <PORTIA@INNOSOFT.COM>
Message-Id: <Pine.3.89.9501111024.A543175213-0100000@INNOSOFT.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

On Wed, 11 Jan 1995, Don Sugarman wrote:

> Greetings and HELP.  
> 
> The PINE folks suggested that I post my questions to the List, so here goes.
> 
> I am trying to identify an e-mail program that will serve the 
> majority of 2100 people at our facility.  The people in the facility 
> currently use MicroSoft Mail (Mac and PC),  PROFS, Unix Mail, Elm, and (a 
> few smart ones) PINE.  Our local computer resources include Sun and VAX 
> VMS servers, all tied together on a high-speed LAN.  In addition, there 
> are a number of individuals who log in locally or remotely via a 
> low-speed LAN through a bridge to the high speed LAN and/or to the IBM PROFS 
> gateway.
> 
> I have been using PINE since discovering it in August.  (I needed a 
> program that would handle MIME encoded messages.)  I am very pleased with 
> the program, and I am trying to promote it here.
> 
> While we would like all users to have a single system address for their 
> mail drop, we anticipate that they will want to forward their mail to 
> their local Sun server or MS Mail inbox.  We recognize that the Sun 
> servers we have bog down with more than 15-20 concurrent logins, so we 
> are setting up a pair of VAX systems as a common e-mail server.
> 
> 1) Does anyone have any information on portability of PINE to VAX VMS? (It
> was not listed with successful ports in the August pine-ports file, and
> there was no indication whether it had been tried unsuccessfully? 

There are two ports to VMS, one is available as part of the PMDF software
we do (at least some other parts of your company are PMDF customers),
for more information, send mail to sales@innosoft.com ($ related 
questions), or service@innosoft.com (for tech questions).

another is free (ported by yehavi@vms.huji.ac.il),
and available for ftp in the US (see below)

----
Subject: repost: Pine/VMS FTP site in US 

	Since there has been a bit of traffic about it recently, I figured
I'd let people know again that VMS-Pine v3.91 is available for anonymous ftp
from lenin.cc.rochester.edu.  Extracting it requires a recent version of
UNZIP, and you MUST remember to transfer it as a binary.  This version
provides improved TCPIP support, but I've found that 3.89 seems to work
better under my installation of VMS (5.4-2).  (I'm not using TCPIP support,
since I only use it for local mail and I need to talk to PMDF anyway.) BTW: 
Congratulations to the development team; it's a great program.  

	Tom
-- 
| Tom Guptill            I don't speak for UCC from this account. |
| tgpt_ltd@UORDBV                                                 |
| Temporary LARVA-ED resident                                     |


> 
> 2) Has anyone tried to incorporate message acknowledgement functionality into
> PINE?  That is if a message is sent registered by Pine, a Pine program on
> the receiving end would send an registered receipt to the originator when
> the message was read.  We have a program on the AT&T that embeds a code of
> the form "[R(nnnn)]" in the subject of a registered message.  When the
> program receives a message with this code, it sends a registered receipt
> under the recipient's login indicating message nnnn was read with the
> subject, time, and date.  See below: 

no, on VMS Pine uses your VMS MAIL files, a read-receipt (or any other 
receipt) is not supported by VMS MAIL. However, if PMDF is used to 
deliver mail to VMS MAIL mailbox, and the sender requested read or 
delivery receipt, then PMDF turns it into a delivery receipt (because it 
has control at that time) and sends an acknowledgement. Personally I 
think read receipt is an invasion of privacy and would never use any 
software which does not offer me a way to turn it off and on at my 
discretion. None of the PMDF Pine users have asked for read receipt 
capability so far.

 > 
>  Receipt Header:  
> 
>  From <recipient of registered message>
>  To: <sender of registered message>
>  Subject: Registered Mail Receipt [A(nnnn)]
>  Status: RO
>  
>  Receipt message:
>  
>       Your registerd mail message has been reeived and read: 
>  
>       RECIPIENT:          <recipient of registered message>
>       DATE:               <date and time message was read>
>       SUBJECT:            <subject of original message>
> 
> 3) Has anyone tried to incorporate a uuencode recognition/filter into
> PINE?  We correspond with users of MicroSoft Mail and CC:MAIL, and would
> like to be able to choose between MIME and uuencode on send and to have
> PINE recognize both forms on receipt. 

Pine recognizes BASE64, and if you were getting the mail via PMDF's
Microsoft Mail and cc:Mail support (PMDF-LAN product), it has the
capability of turning their messages format into MIME, and thus the 
result would be recognized by Pine. For example, if I send you a message 
from cc:Mail or Microsoft Mail with an attachment, when you get it in Pine
on VMS or Unix or elsewhere, you will get the attachment BASE64 encoded, 
and would be able to extract it.

> 
> Thanks in advance for any help/info you can provide.
> 
> Don
> 
> Don Sugarman, Senior Project Engineer
> Martin Marietta Defense Systems
> Pittsfield, MA 
> sugarman@mmpcs1.psf.ge.com
> 


	/portia		portia@innosoft.com
	Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax
	1050 East Garvey Ave South, West Covina, CA 91790




From owner-pine-info@cac.washington.edu  Wed Jan 11 11:43:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06754;
	Wed, 11 Jan 95 11:43:12 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27493;
	Wed, 11 Jan 95 11:32:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27487;
	Wed, 11 Jan 95 11:32:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rS8eg-00038JC; Wed, 11 Jan 95 11:24 PST
To: pine-info@cac.washington.edu
From: jason@IS.NET (Jason R. Mastaler)
Subject: Re: blind carbon copies
Date: 11 Jan 1995 03:45:49 GMT
Message-Id: <JASON.95Jan10224549@user1.IS.NET>
References: <3eutog$9sb@vixen.cso.uiuc.edu>
In-Reply-To: The Group's message of 10 Jan 1995 21:21:20 GMT

In article <3eutog$9sb@vixen.cso.uiuc.edu> The Group <group@uiuc.edu> writes:

> 
> I'm trying to use Pine to send out announcements 
> to a long list of people, but I don't want the addresses
> to show up in everyone's mailbox.  Does anyone know how 
> send blind carbon copies using Pine?
> 
Yes.  When in COMPOSE mode, use ^R (Rich Hdr) to bring up a few more
mail sending options.  One such options is Bcc: (blind carbon-copy).

Cheers,
Jason 


From owner-pine-info@cac.washington.edu  Wed Jan 11 12:24:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08829;
	Wed, 11 Jan 95 12:24:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02655;
	Wed, 11 Jan 95 12:10:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02649;
	Wed, 11 Jan 95 12:10:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rS9Hm-00038CC; Wed, 11 Jan 95 12:04 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Incorrect behaviour of F12 in Index window
Date: Wed, 11 Jan 1995 15:56:36 +0000
Message-Id: <Pine.SUN.3.91.950111155419.17995J-100000@bootes.cus.cam.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

One of my users has pointed out to me the following bug.
He is using WinPine 3.91, and has function key mode set. When looking at 
a folder index, he wanted to Forward a message, which is called by F12; 
instead of forwarding the message, it generates a Reply.


=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Wed Jan 11 12:43:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09637;
	Wed, 11 Jan 95 12:43:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03193;
	Wed, 11 Jan 95 12:35:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03187;
	Wed, 11 Jan 95 12:35:15 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rS9em-00038JC; Wed, 11 Jan 95 12:28 PST
To: pine-info@cac.washington.edu
From: bravo@ie.technion.ac.il (Bravo_Israel)
Subject: Addressbook and recipients list
Date: Wed, 11 Jan 1995 13:30:41 GMT
Message-Id: <D28tJ6.KKy@discus.technion.ac.il>

	Hi, I'd like to make a distribution list in the address book
of Pine and send a message to some users, but I don't want to let
the recipients to see all the "To:" list. I'd like to make that
each recipient will see only his address, not all list.
	Does anyone use this, and how? Please, help.

	Thank you,
                              ####
                             (0^^0)
   +------------------ooooO---(__)---Ooooo-----------------+
   | Bravo Israel                                          |
   |   Systems staff  E-mail:  bravo@ie.technion.ac.il     |
   |   Faculty of Industrial Engineering,  phone 04-294428 |
   |   Technion, 32000 Haifa, Israel                       |
   +-------------------------------------------------------+



From owner-pine-info@cac.washington.edu  Wed Jan 11 12:49:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09816;
	Wed, 11 Jan 95 12:49:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28985;
	Wed, 11 Jan 95 12:35:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28979;
	Wed, 11 Jan 95 12:35:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rS9dI-00038CC; Wed, 11 Jan 95 12:27 PST
To: pine-info@cac.washington.edu
From: J.S.Peatfield@amtp.cam.ac.uk (Jon Peatfield)
Subject: problem when tmp directory is full
Date: 11 Jan 1995 13:40:38 GMT
Message-Id: <J.S.PEATFIELD.95Jan11134038@kro.amtp.cam.ac.uk>

We have Pine 3.91 running on a variety of machines.  Recently we
noticed that on some of them at least when the tmp directory that pine
stores messages in when sending to sendmail gets full the messages get
lost and the user isn't warned.

We can't test all the machines at this time as e.g. all our Suns use
tmpfs so filling tmp would be a problem for other reasons, but at
least on SGIs this appears to be repeatable just by filling up
/usr/tmp.

Looking at the code in osdep/sendmail it looks like an error from
pine_rfc822_output() will result in a warning for the user:

>   q_status_message2(1, 2, 4, "\007Error \"%s\" writing \"%s\"",
>                          error_description(save_errno), pretty_fn(filename));

but I see no such message.  Looking deaper into pine_rfc822_output() I
can see that the error chain looks ok 'til I get lost inside
pine_rfc822_output_body() where I can't tell what is happening.

Does anyone else see this or is it a symptom of a problem with our
setup?

Does someone who understands the pine source better than me know what
is going on here?

  -- Jon Peatfield  (postmaster@damtp.cam.ac.uk)

--
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852     Mail: J.S.Peatfield@damtp.cam.ac.uk

  NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg


From owner-pine-info@cac.washington.edu  Wed Jan 11 12:58:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10190;
	Wed, 11 Jan 95 12:58:40 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29326;
	Wed, 11 Jan 95 12:47:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29320;
	Wed, 11 Jan 95 12:47:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rS9nW-00038CC; Wed, 11 Jan 95 12:37 PST
To: pine-info@cac.washington.edu
From: helen ruth etters <etters@wfu.edu>
Subject: Re: blind carbon copies
Date: Wed, 11 Jan 1995 12:49:49 -0500
Message-Id: <Pine.HPP.3.91.950111124740.2220A-100000@ac852.wfunet.wfu.edu>
References: <3eutog$9sb@vixen.cso.uiuc.edu> <3evbtm$f4e@lynx.unm.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3evbtm$f4e@lynx.unm.edu> 

On 11 Jan 1995, Daniel A Ivey-Soto wrote:

> "Rich Header".  Then, in the line titled BCC, just place all the names
> as you normally would in the TO: line. 

Then if the recpients wish to reply, will they get the message
"reply to all recipients?" allowing them to send their responses
to everyone?

    @     @       Thanks                                    @     @     @  
 @  |  @  |  @                                           @  |  @  |  @  |  @
\|/\|/\|/\|/\|/             Helen Etters                \|/\|/\|/\|/\|/\|/\|/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^



From owner-pine-info@cac.washington.edu  Wed Jan 11 13:20:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11505;
	Wed, 11 Jan 95 13:20:43 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04318;
	Wed, 11 Jan 95 13:08:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04312;
	Wed, 11 Jan 95 13:08:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rS9x7-00038xC; Wed, 11 Jan 95 12:47 PST
To: pine-info@cac.washington.edu
From: "J. Kelly Cunningham" <deviate@lipschitz>
Subject: Re: PGP mail with pine 
Message-Id: <Pine.NXT.3.91.950111073205.3711D-100000@lipschitz>
Date: Wed, 11 Jan 1995 07:39:03 -0600
References: <3epb7q$o0v@solaris.cc.vt.edu> 
In-Reply-To: <3epb7q$o0v@solaris.cc.vt.edu> 
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

-----BEGIN PGP SIGNED MESSAGE-----

On 8 Jan 1995, matthew c. mead wrote:

   Date: 8 JAN 1995 18:34:34 GMT 
   From: matthew c. mead <mmead@goof.com>
   Newgroups: comp.mail.pine
   Subject: PGP mail with pine 
   
   	I've been using perl scripts for PGP mail in elm for a while, and I've
   been told by a friend of mine that pine has PGP support built it.  Is this
   true?  

Not yet.

           If not, what mechanism is used to achieve the encryption and decryption?
   Also, where can I find it ... thanks for any help!
   
mkpgp is a c-shell script which serves as a liaison for the Pine 
mailer/newsreader and pgp.

It features: external editor of your choice, external spell checker of
your choice, encryption (with or without signing), signing (with or
without encryption), encrypted attachments selected via browser,
effortless public key additions from e-mail, decryption & signature
verification, effortless encrypted attachment extraction, quote 
characters of your choice, and more... 

To get mkpgp, send blank e-mail to slutsky@lipschitz.sfasu.edu with
	Subject: mkpgp
A signed, ascii-armored message should show up in you mailbox within the 
hour.

Process the message with "pgp -p" to produce mkpgp.txt.uu.  mkpgp.txt.uu 
contains the readme atop a uuencode of mkpgp.

(You can add my keys with
        finger deviate@lipschitz.sfasu.edu | pgp -fka +force 
before you process the message if you want to check the signature.)

To receive updates, send blank e-mail to slutsky@lipschitz.sfasu.edu with
	Subject: addtomkpgplist
mkpgp will show up each time the modification date changes.

- -- kc     finger deviate@lipschitz.sfasu.edu | pgp -fka +force

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBLxOLBuBu0383Om6dAQF35AP+Mfuy7jolQ8Kk9sGhCvvX6fpK8qv4HpNv
rn+vLjxrPusdnC8+IUwHhq/CWCzGOpKr5cqMmSdSSB8ACK1b4UfqsyOc3BG4HUY+
4oOgB95HDyhsmJ71ZulU9EaPs8PxY7B5cXsGXeBsQJqPv0Ee+Y1/TsXl7T/zYQTI
zryh24oHiKA=
=41qm
-----END PGP SIGNATURE-----


-- kc       prudence dictates a low profile -- Sandy Sandfort
          finger deviate@lipschitz.sfasu.edu | pgp -fka +force
    finger slutsky@lipschitz.sfasu.edu | pgp -f | tee mkpgp.txt.uu | more


From owner-pine-info@cac.washington.edu  Wed Jan 11 13:22:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11599;
	Wed, 11 Jan 95 13:22:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00135;
	Wed, 11 Jan 95 13:08:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00128;
	Wed, 11 Jan 95 13:08:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSA0R-00038yC; Wed, 11 Jan 95 12:50 PST
To: pine-info@cac.washington.edu
From: J.S.Peatfield@amtp.cam.ac.uk (Jon Peatfield)
Subject: Re: problem when tmp directory is full
Date: 11 Jan 1995 16:41:45 GMT
Message-Id: <J.S.PEATFIELD.95Jan11164146@kro.amtp.cam.ac.uk>
References: <J.S.PEATFIELD.95Jan11134038@kro.amtp.cam.ac.uk>
In-Reply-To: J.S.Peatfield@amtp.cam.ac.uk's message of 11 Jan 1995 13:40:38 GMT

Much as I hate following up to my own items here is some more info.

After discovering the TMPDIR variable, I filled up a filesystem and
pointed TMPDIR at it from a Sun4 (sos4) and got the same behavour as
on the SGI.

The relevant bit of the debug log (-d99) is:

> Sending mail...
> q_status_message, Count 2, "Sending mail....."
> output_message(Sending mail.....)
> call_mailer: handing off
> === calling sendmail ===
> -- pine_rfc822_output
> -- pine_encode_body: 0
> -- pine_rfc822_output_body: 0
> -- pine_rfc822_output_body: segment 0 bytes
> -- gf_reset local_nvtnl
> -- gf_pipe: done.
> Send command "( ( /usr/lib/sendmail -oi -oem -t ; /bin/rm -f /home/fenris/jp107//pinesend001683 ) < /home/fenris/jp107//pinesend001683 & )"
> PID: 1701, COMMAND: ( ( /usr/lib/sendmail -oi -oem -t ; /bin/rm -f /home/fenris/jp107//pinesend001683 ) < /home/fenris/jp107//pinesend001683 & )
> Send SUCCESSFUL.
> To: jp107@cus
> Subject: This is a stupid test
> Message ID: <Pine.SUN.3.91.950111162331.1683B-100000@kro.amtp.cam.ac.uk>
> 
> Writing Fcc
> q_status_message, Count 1, "Writing Fcc..."
> output_message(Writing Fcc...)

The directory /home/fenris/jp107/ had no space left yet I got no error
and the message wasn't sent.  (In fact sendmail sent a null message
which then bounced to postmaster but this isn't helpful.)

Does this give any clues as to the problem?

  -- Jon Peatfield  (postmaster@damtp.cam.ac.uk)

--
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852     Mail: J.S.Peatfield@damtp.cam.ac.uk

  NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg NAg


From owner-pine-info@cac.washington.edu  Wed Jan 11 13:39:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12364;
	Wed, 11 Jan 95 13:39:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04935;
	Wed, 11 Jan 95 13:35:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04929;
	Wed, 11 Jan 95 13:35:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSAbS-00038CC; Wed, 11 Jan 95 13:29 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Compiling PINE
Date: Wed, 11 Jan 1995 11:12:15 -0800
Message-Id: <Pine.ULT.3.92.950111111057.18990C-100000@shiva1.cac.washington.edu>
References: <Pine.OSF.3.91.950111094838.5330A-100000@alpha.loyno.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.OSF.3.91.950111094838.5330A-100000@alpha.loyno.edu> 


Did you make the pine, pico, imapd, and mtest files executable after
ftping them?  (e.g. chmod +x pine)

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Wed, 11 Jan 1995, Mary Aplin wrote:

> Date: Wed, 11 JAN 1995 08:54:55 GMT 
> From: Mary Aplin <aplin@alpha.loyno.edu>
> Newgroups: comp.mail.pine
> Subject: Compiling PINE 
> 
> Hello All --
> 
> I've just compiled PINE 3.91 under OSF on my DEC Alpha 3300.  
> 
> I have a second Alpha 3300, but it does not have the same software setup 
> and the first, and I cannot compile PINE on this system;  it bombs out.
> 
> When we were running PINE 3.90 I had successfully FTP'd pine over to my 
> second Alpha system, and it ran just fine.  (Acutally, I FTP'd pine, 
> pico, imapd, and mtest over to the /usr/bin directory)  I just tried to 
> FTP PINE 3.91 over to my second Alpha, (in the same directory) and I can't 
> get it to run.  The error is   pine: cannot execute
> 
> What parts of PINE 3.91 need to be present (and where) in order for it to 
> execute?
> 
> Thanks
> Mary Aplin
> Loyola University, New Orleans
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 14:34:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15021;
	Wed, 11 Jan 95 14:34:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02009;
	Wed, 11 Jan 95 14:25:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02001;
	Wed, 11 Jan 95 14:25:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSBK7-00038KC; Wed, 11 Jan 95 14:15 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: blind carbon copies
Date: Wed, 11 Jan 1995 09:39:25 -0800
Message-Id: <Pine.ULT.3.92.950111093707.18990k-100000@shiva1.cac.washington.edu>
References: <3evc9m$kah@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3evc9m$kah@cronkite.ocis.temple.edu> 


On 11 Jan 1995, Wet-Sprocket wrote:

> Date: 11 JAN 1995 01:29:26 GMT 
> From: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: Re: blind carbon copies 
> 
> You will see a Bcc: header, just fill in here the entire list but be told that
> there's a limit to how many addressess you can have per header (think itz < 50)
> 

Any such limit is coming from your mail transport (e.g. sendmail), not
from Pine.  Pine does not impose any limits on numbers of addresses... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Wed Jan 11 15:27:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17740;
	Wed, 11 Jan 95 15:27:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07364;
	Wed, 11 Jan 95 15:20:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07358;
	Wed, 11 Jan 95 15:20:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSCCX-00038JC; Wed, 11 Jan 95 15:11 PST
To: pine-info@cac.washington.edu
From: mmead@goof.com (matthew c. mead)
Subject: External Pagers
Date: 11 Jan 1995 20:12:13 GMT
Message-Id: <3f1e2t$ovp@solaris.cc.vt.edu>


	Well, I've built pine now, and got a nice pgp system going with it
(which works well with elm, as well, btw).  The only problem is reading
encrypted messages.  I don't like that you have to reply to them to decrypt and
read them.  In elm, I have a script which will test to see if input is
encrypted, and decrypt it prior to viewing if it is.  I'd like to fully switch
to pine, but the lack of support for external pagers is the only thing holding
me back.  Does anyone know of a hack anywhere that adds this support?
Otherwise it's off to the pine source code with an axe I go...  :-)  Thanks in
advance!







-matt


-- 
Matthew C. Mead -- System/Network Administration, User Support, Software Devel.
Virginia Tech Center for Transportation Research
Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com
WWW: http://www.goof.com:/~mmead


From owner-pine-info@cac.washington.edu  Wed Jan 11 17:31:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24943;
	Wed, 11 Jan 95 17:31:12 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07078;
	Wed, 11 Jan 95 17:20:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07072;
	Wed, 11 Jan 95 17:20:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSE6R-00038JC; Wed, 11 Jan 95 17:13 PST
To: pine-info@cac.washington.edu
From: Mark Crane <psu01055@odin.cc.pdx.edu>
Subject: Re: Addressbook and recipients list
Date: Wed, 11 Jan 1995 09:43:17 -0800
Message-Id: <Pine.PTX.3.91.950111094126.20510A-100000@odin.cc.pdx.edu>
References: <D28tJ6.KKy@discus.technion.ac.il>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D28tJ6.KKy@discus.technion.ac.il> 

As I understand it, in order to not let recipients of carbon copies 
*know* that they are recipients of carbon copies, you have to hit ctrl-r 
while in compose mode, thus enabling the "rich header", which includes 
the "BCC:" option, for "Blind Carbon Copy."  Let me know how lists work 
in the address book. I haven't figured it out.


Mark Crane
psu01055@odin.cc.pdx.edu



From owner-pine-info@cac.washington.edu  Wed Jan 11 17:41:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25400;
	Wed, 11 Jan 95 17:41:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07461;
	Wed, 11 Jan 95 17:37:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07455;
	Wed, 11 Jan 95 17:36:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSEG7-00038KC; Wed, 11 Jan 95 17:23 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Environment variable for pine.conf?
Date: Wed, 11 Jan 1995 14:35:48 -0800
Message-Id: <Pine.ULT.3.92.950111143449.18990X-100000@shiva1.cac.washington.edu>
References: <D1zzLI.5Mv@oci.utoronto.ca> <D1zzzz.5wp@oci.utoronto.ca>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D1zzzz.5wp@oci.utoronto.ca> 


There is no environment variable per-se, but there is a command line
option, -P, that specifies an alternate pine.conf file. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 6 Jan 1995, Tim Bloomfield wrote:

> Date: Fri, 6 JAN 1995 19:11:59 GMT 
> From: Tim Bloomfield <tim@pooh>
> Newgroups: comp.mail.pine
> Subject: Re: Environment variable for pine.conf? 
> 
> Sorry about the previous message. Tin crashed When I resized a window while 
> editing.
> 
> Is there an environment variable that can be set to point to the location of 
> pine.conf? The man page does not mention one. Thanks
> 
> 
> -------------------------------------------------
> Tim Bloomfield  (tim@srcl.sunnybrook.utoronto.ca)
> Sunnybrook Health Science Ctr. 
> North York, Ontario.
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 17:41:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25401;
	Wed, 11 Jan 95 17:41:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07491;
	Wed, 11 Jan 95 17:37:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07479;
	Wed, 11 Jan 95 17:37:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSEKc-00038PC; Wed, 11 Jan 95 17:28 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Turning Off Insert Mode In Pine
Date: Wed, 11 Jan 1995 14:40:07 -0800
Message-Id: <Pine.ULT.3.92.950111143948.18990Z-100000@shiva1.cac.washington.edu>
References: <D20FIG.JtC@dorsai.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D20FIG.JtC@dorsai.org> 


No, there is not currently an overwrite mode in the composer.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Sat, 7 Jan 1995, martin schildkret wrote:

> Date: Sat, 7 JAN 1995 00:47:03 GMT 
> From: martin schildkret <martin@news.dorsai.org>
> Newgroups: comp.mail.pine
> Subject: Turning Off Insert Mode In Pine 
> 
>   Is there any way of turning off the insert mode in PINE. I would much 
> prfer to be in typeover. Thanks for any help that I may receive.....
> 
> --
>        -----------------------------------------------------------
>        | <<<   Martin@Dorsai.Org  |  < Martin Schildkret >   >>> |
>        -----------------------------------------------------------
>                                 
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 17:43:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25459;
	Wed, 11 Jan 95 17:43:02 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11399;
	Wed, 11 Jan 95 17:37:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11393;
	Wed, 11 Jan 95 17:37:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSEJc-00038MC; Wed, 11 Jan 95 17:27 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Pine & Procomm/Prowin
Date: Wed, 11 Jan 1995 14:39:07 -0800
Message-Id: <Pine.ULT.3.92.950111143650.18990Y-100000@shiva1.cac.washington.edu>
References: <3ekd7s$oj3@skivs.ski.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3ekd7s$oj3@skivs.ski.org> 


>From the next release of the Pine FAQ (coming very soon):

Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this 
feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".



|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 6 Jan 1995, Erin O'Neill wrote:

> Date: 6 JAN 1995 13:38:04 -0800 
> From: Erin O'Neill <erin@skivs.ski.org>
> Newgroups: comp.mail.pine
> Subject: Pine & Procomm/Prowin 
> 
> 
> I have some users that are using both the shareware Procomm for DOS & using 
> Prowin (Procomm for windows) and both are complaining about NOT being able 
> to do the 2 following things:
> 
> 1) print a mail message to their local printers 
> 
> 2) capture a mail message to a procomm capture file.
> 
> 
> Many of these users want to stop using mail & only use pine, but they find 
> they can't live without these features.
> 
> Any Suggestions?
> 
> erin
> erin@skivs.ski.org
> -- 
> erin
> erin@skivs.ski.org
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 17:43:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25488;
	Wed, 11 Jan 95 17:43:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11383;
	Wed, 11 Jan 95 17:36:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11377;
	Wed, 11 Jan 95 17:36:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSEDc-00038JC; Wed, 11 Jan 95 17:20 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: WANTED DESPERATELY: books on pine
Date: Wed, 11 Jan 1995 14:33:26 -0800
Message-Id: <Pine.ULT.3.92.950111143140.18990V-100000@shiva1.cac.washington.edu>
References: <Pine.ULT.3.90.950106183019.27529A-100000@coco.ihi.ku.dk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.90.950106183019.27529A-100000@coco.ihi.ku.dk> 


I don't know of any current books dedicated to Pine, but several do have 
chapters on it.  Also, check out the documentation available at

	http://www.cac.washington.edu/pine/
	ftp://ftp.cac.washington.edu/pine/docs/

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 6 Jan 1995, Garbi Schmidt wrote:

> Date: Fri, 6 JAN 1995 18:33:04 +0100 (MET) 
> From: Garbi Schmidt <garbi@coco.ihi.ku.dk>
> Newgroups: comp.mail.pine
> Subject: WANTED DESPERATELY: books on pine 
> 
> 
> Hi there!
> 
> Does anybody out there have the ultimate solution to my quest for a good 
> book on pine, or perhaps som FAQ or HELPsite for pine - especially setup 
> and configuration questions??
> 
> Thanks a lot!
> 			Garbi
> --------------------------------------------------------------------------
> Garbi Schmidt | 'Tomorrow is the most important thing in life.' (John Wayne)
> Copenhagen,DK | 'HALLELUJA -- there is still hope!' (G. Schmidt)
> ---------------------------------------------------------------------------
> 
>  
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 18:34:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26945;
	Wed, 11 Jan 95 18:34:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12112;
	Wed, 11 Jan 95 18:20:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12100;
	Wed, 11 Jan 95 18:20:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSF2E-00038JC; Wed, 11 Jan 95 18:13 PST
To: pine-info@cac.washington.edu
From: PRFW51A@prodigy.com (Jim Mendelson)
Subject: Pine file
Date: 12 Jan 1995 01:25:14 GMT
Message-Id: <3f20dq$j38@usenetw1.news.prodigy.com>

  Hi to all,
   I've been trying to get ahold of this program called pine.  I got my 
first Internet file and I needed this program Pine to uncode it.    I 
wrote to pine@cac.washington.edu and they sent me the discription of what 
the program is.  Can I get this from someone?
     
                                                                          
     Thanks to all,
                                                                          
              Jim



From owner-pine-info@cac.washington.edu  Wed Jan 11 19:15:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28036;
	Wed, 11 Jan 95 19:15:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08994;
	Wed, 11 Jan 95 19:09:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08988;
	Wed, 11 Jan 95 19:09:17 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 12 Jan 95 11:07:35 -0800
Date: Thu, 12 Jan 1995 11:07:34 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Jim Mendelson <PRFW51A@prodigy.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Pine file
In-Reply-To: <3f20dq$j38@usenetw1.news.prodigy.com>
Message-Id: <Pine.SOL.3.91.950112110133.26690A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 12 Jan 1995, Jim Mendelson wrote:

>    I've been trying to get ahold of this program called pine.  I got my 
> first Internet file and I needed this program Pine to uncode it.    I 
> wrote to pine@cac.washington.edu and they sent me the discription of what 
> the program is.  Can I get this from someone?

	You can get source code and binaries for certain platforms from
ftp.cac.washington.edu.  

	Without knowing the specific environment that you are running....it
is not very easy to make suggestions.  Not being familiar with prodigy, I
don't know if you have ftp access.  Also, I don't know how you access your
email.  

	Regards,
					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 11 20:10:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29321;
	Wed, 11 Jan 95 20:10:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13595;
	Wed, 11 Jan 95 20:05:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from kaiwan.kaiwan.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13589;
	Wed, 11 Jan 95 20:05:19 -0800
Received: from kaiwan009.kaiwan.com (2196@kaiwan009.kaiwan.com [192.215.30.9]) by kaiwan.kaiwan.com (8.6.9/8.6.5) with ESMTP 
	  id UAA03606; Wed, 11 Jan 1995 20:05:14 -0800
	  *** KAIWAN Internet Access ***
Received: (from gyuri@localhost) by kaiwan009.kaiwan.com (8.6.9/8.6.9)
	  id UAA01692; Wed, 11 Jan 1995 20:05:16 -0800
	  *** KAIWAN Internet Access ***
Date: Wed, 11 Jan 1995 20:05:14 -0800 (PST)
From: George Szilagyi <gyuri@kaiwan.com>
To: Pine Information List <pine-info@cac.washington.edu>
Cc: Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID VP2K7): Printer setup
In-Reply-To: <Pine.ULT.3.92.950109110903.2851r-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950111200048.572A-100000@kaiwan009.kaiwan.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 9 Jan 1995, David L Miller wrote:

> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Sun, 1 Jan 1995, George Szilagyi wrote:
> 
> > Date: Sun, 1 Jan 1995 16:41:01 -0800 (PST)
> > From: George Szilagyi <gyuri@kaiwan.com>
> > To: Pine Developers <pine-bugs@cac.washington.edu>
> > Subject: Bug (ID VP2K7): Printer setup
> > 
> > I have a HP Laserjet 4. I was trying to print out the instruction to 
> > Pine, but could not get my printer to work with any of the configuration 
> > available. I also have problem receiving messages, but that is a separate 
> > message to root.
> 
> On Tue, 3 Jan 1995, George Szilagyi wrote:
> 
> > Date: Tue, 3 Jan 1995 21:57:20 -0800 (PST)
> > From: George Szilagyi <gyuri@kaiwan.com>
> > To: Pine Developers <pine-bugs@cac.washington.edu>
> > Subject: Re: Bug (ID VP2K7): Printer setup
> > 
> > On Sun, 1 Jan 1995, George Szilagyi wrote:
> > 
> > > I have a HP Laserjet 4. I was trying to print out the instruction to 
> > > Pine, but could not get my printer to work with any of the configuration 
> > > available. I also have problem receiving messages, but that is a separate 
> > > message to root.
> > 
> > I read your answer and it got me more confused than ever. Would you 
> > repeat your set-up instruction clearly, step by step, so I can get a 
> > connection between Kaiwan, Pine and my printer.
> > 
> > Thanks......
> 
I don't think I got the hang of this thing yet, but yes I would like to 
get the faq file.


From owner-pine-info@cac.washington.edu  Wed Jan 11 20:35:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29801;
	Wed, 11 Jan 95 20:35:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10082;
	Wed, 11 Jan 95 20:21:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10061;
	Wed, 11 Jan 95 20:21:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSGoq-00038JC; Wed, 11 Jan 95 20:07 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: blind carbon copies
Date: Wed, 11 Jan 1995 13:20:46 -0800
Message-Id: <Pine.ULT.3.92.950111131712.18990J-100000@shiva1.cac.washington.edu>
References: <3eutog$9sb@vixen.cso.uiuc.edu> <3evbtm$f4e@lynx.unm.edu> <Pine.HPP.3.91.950111124740.2220A-100000@ac852.wfunet.wfu.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.HPP.3.91.950111124740.2220A-100000@ac852.wfunet.wfu.edu> 


None of the recipients will see any of the names in the Bcc.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Wed, 11 Jan 1995, helen ruth etters wrote:

> Date: Wed, 11 JAN 1995 12:49:49 -0500 
> From: helen ruth etters <etters@wfu.edu>
> Newgroups: comp.mail.pine
> Subject: Re: blind carbon copies 
> 
> On 11 Jan 1995, Daniel A Ivey-Soto wrote:
> 
> > "Rich Header".  Then, in the line titled BCC, just place all the names
> > as you normally would in the TO: line. 
> 
> Then if the recpients wish to reply, will they get the message
> "reply to all recipients?" allowing them to send their responses
> to everyone?
> 
>     @     @       Thanks                                    @     @     @  
>  @  |  @  |  @                                           @  |  @  |  @  |  @
> \|/\|/\|/\|/\|/             Helen Etters                \|/\|/\|/\|/\|/\|/\|/
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 20:40:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29925;
	Wed, 11 Jan 95 20:40:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14085;
	Wed, 11 Jan 95 20:35:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14079;
	Wed, 11 Jan 95 20:35:05 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA04958; Wed, 11 Jan 1995 23:34:26 +0500
Date: Wed, 11 Jan 1995 23:34:25 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: Jim Mendelson <PRFW51A@prodigy.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Pine file
In-Reply-To: <3f20dq$j38@usenetw1.news.prodigy.com>
Message-Id: <Pine.SOL.3.90.950111233012.4896B@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 951

On 12 Jan 1995, Jim Mendelson wrote:

>    I've been trying to get ahold of this program called pine.  I got my 
> first Internet file and I needed this program Pine to uncode it.    I 
> wrote to pine@cac.washington.edu and they sent me the discription of what 
> the program is.  Can I get this from someone?
 
You can ftp Pine from cac.washington.edu, where you will find the source 
code as well as precompiled binaries suitable for several platforms.
 
However, your statement "I got my first Internet file and I needed this
program Pine to uncode it" has me puzzled.  Pine is a mail reader.  What 
kind of file do you expect to "uncode" with it?

--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA



From owner-pine-info@cac.washington.edu  Wed Jan 11 20:57:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00394;
	Wed, 11 Jan 95 20:57:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14311;
	Wed, 11 Jan 95 20:51:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14305;
	Wed, 11 Jan 95 20:51:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSHN8-00038LC; Wed, 11 Jan 95 20:42 PST
To: pine-info@cac.washington.edu
From: pauls@locust.cic.net (Paul Southworth)
Subject: Re: Need help with pine and pop/imap
Date: 12 Jan 1995 00:05:06 GMT
Message-Id: <3f1rni$su7@spruce.cic.net>
References: <Pine.HPP.3.91.950111112058.15888A-100000@bon.eng.ohio-state.edu>

In article <Pine.HPP.3.91.950111112058.15888A-100000@bon.eng.ohio-state.edu>,
James Vaughn Brown  <brownj@bon.eng.ohio-state.edu> wrote:
>I need help getting pine to work with a pop server.  Can this be done?  I 
>think Imap is a superset of pop, and should be able to access the pop 
>servers, provided you tell Pine that it is a pop server.

[follow-ups set to comp.mail.pine -- I'm sure those folks will correct
the following comments if they're not right...]

I think this will not work.  IMAP has a number of fundamental
differences from POP.  You should run an IMAP server if you want to run
Pine.  Otherwise you need a real POP mail client.  I don't believe there
is any configuration option in pine to change the service or port number
it connects to -- it's set to 143/tcp (IMAP).  pop3 wants 110/tcp.  I don't
think you can change that outside of the source code, and I also don't
think it would work even if you did.

According to the pine manual, the c-client library doesn't do POP:

   Currently  it  understands  Berkeley  mail
   files, Tenex mail files, the IMAP2bis protocol, and NetNews.

>My problem arises in that I do not know how to specify a user name or a 
>password for the other system.  Could anyone help me with this.  

In pine 3.91, this is handled in the online configuration process.
For earlier versions, you edit .pinerc's "inbox path" according to
the comments in the .pinerc file:

  # Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
  # Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
  inbox-path=

Note that it will assume your remote user name is the same as your 
local user name, but you can override that when it connects (it will
prompt with a default of the local user name).

--
Paul Southworth
CICNet Systems Support
pauls@cic.net


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:11:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00768;
	Wed, 11 Jan 95 21:11:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10805;
	Wed, 11 Jan 95 21:06:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10799;
	Wed, 11 Jan 95 21:06:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSHWS-00038JC; Wed, 11 Jan 95 20:52 PST
To: pine-info@cac.washington.edu
From: ao826@FreeNet.Carleton.CA (David A Hosten)
Subject: 3 questions ? ? ? Mail, Unix, Internet.
Message-Id: <D29rpH.Gwo@freenet.carleton.ca>
Date: Thu, 12 Jan 1995 01:48:52 GMT

I am posting this in the hope somewhere out there [over the rainbow ;) ]
somebody will be able these three questions. I'm a Unix newbie (being very
familiar with less tasking [get it?] systems like Windoze, OS/2, WinNT,
etc. So here are the questions:

1. (a) How do I change my environment to enable Pico to replace the vi editor,
for my own personal use, on the Aix system we have at school. I know Pico
well, and have grown accoustomed to it. Vi is fine, but, to me more of a
pain in the butt to use. I'm auto-launched into a Korn shell at login, but
can change at will. Any suggestions?  (b) How do I edit (and where do I
find) my .tinrc file to enable Pico as my editor for Usenet read/reply?

2. (a) How may I retrieve posts to Usenet groups that my Freenet/University
accounts do not subscribe to? There must be some way of doing an FTP
equivalent to a site that collects the postings. (b) Is there a way of uucp
retrieving them from sites? (c) If so, is it then possible to e-mail a group
directly from the Pine mailer...what would be put into the To:  address
section? (d) Why is the location of usenet-news servers appear to be
so secret and inaccessible to the regular FTP public? Reason: there are some
alt.fan.* groups that we would like to pick up to do some research on
media influence.

3. Our recalcitrant sysadmins won't respond to e-mail, so what are you
normally do with a student aix account? I'm trying to teach myself a bit
of Unix (am going to decide between Free/386/NetBsd, Linux or
Solaris [apparently have a $100 educational deal] versions), so will want
to eventually know the answers to these questions anyway.

Please Reply Via E-Mail

Some of you may notice that I had previously asked one of these questions,
and I thank those who kindly responded, but lost the info on my HD at home
(a friend was playing with the computer and DoD deleted the contents of a
whole directory with PC Tools Pro V.9). 

Thanks to all of you who will help increase knowledge....

 
--
__David Hosten__Publishing Editor__International Free Press_Electronic
ao826@freenet.carleton.ca|dhosten@freenet.fsu.edu|dhosten@ifp.synapse.net
____Department Of Mass Communications___University Of Ottawa__CAN____
//////Unless otherwise stated, comments made here are my own\\\\\\\\


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:26:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01130;
	Wed, 11 Jan 95 21:26:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14774;
	Wed, 11 Jan 95 21:21:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14768;
	Wed, 11 Jan 95 21:21:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSHlE-00038JC; Wed, 11 Jan 95 21:07 PST
To: pine-info@cac.washington.edu
From: bbs.america@loa.com (BBS AMERICA)
Subject: Run a BBS? Want full Internet for $24.95/mo?
Message-Id: <8A16467.04D60000DA.uuout@loa.com>
Date: Wed, 11 Jan 95 18:47:00 -0400

Hello there!  Right about now you're probably wondering just what it is
you've gone and downloaded.  Well, first off, I'll be honest with you...
if you're not a SysOp, it's more than likely just something to upload
to various BBSes for the credit.  But, if you're a SysOp then you have
heard all the rage about the Internet that's come up recently.  I'll bet
you even considered looking into getting full access Internet for your
own system!  Well, more than likely you eventually realized that full
access Internet was way too expensive for your BBS to support.... Until
now.

Log On America is now offering full access internet for any BBS in the
nation for the amazingly low price of $24.95 per month.  That's right,
this is no joke...  All you need is a BBS and at least 2 modems... It's
simple, you merely set up the transport door (included as CST54.ZIP) to
run from your BBS software.  Once you contact us, we will give you the
LOCAL phone number that you will need and set up your account.

Here's how it works.  Your users call your BBS as normal, when they run
the Cyberspace Transporter door, it will have your user wait while it dials
Log On America.  Your user will then get full access to Telnet, FTP, Finger,
Whois, World Wide Web.  Using the Telnet client, your users can access IRC,
MUDs, schools, libraries, and more!  With FTP, millions of files from all
over the world become available!  Easy-to-use hypertext interfaces make
surfing the Internet simple with Gopher and the World Wide Web!  You can
find out information about both people and systems with the Finger and
Whois clients!  For as much time as you care to allow them... Then, when
the user types EXIT, the software will drop carrier and return control to
your BBS -- without the user EVER SEEING Log On America.  It's that easy!

For more information or to sign up, you can contact us by any of the
following:

 Phone: (401)453-6100  M-F 9a-5p EST
   Fax: (401)459-6222
   BBS: (401)459-6200
E-Mail: david.paolo@loa.com
  Mail: Log On America, Inc.
        3 Regency Plaza
        Providence, RI 02903
        ATTN: Internet BBS

--------------------------------------------------------------------------
This article was an automated post.  Any posting in unrelated newsgroups
is an error, please disregard this article if it is off-topic.


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:42:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01489;
	Wed, 11 Jan 95 21:42:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15003;
	Wed, 11 Jan 95 21:36:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14997;
	Wed, 11 Jan 95 21:36:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSI5K-00038SC; Wed, 11 Jan 95 21:28 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: can I post news from pine?
Date: Wed, 11 Jan 1995 14:04:51 -0800
Message-Id: <Pine.ULT.3.92.950111140350.18990N-100000@shiva1.cac.washington.edu>
References: <3eeisg$3vb@fohnix.metronet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3eeisg$3vb@fohnix.metronet.com> 


The closest you can come is to Forward the message to the newsgroup,
editing it as appropriate.  There is no bounce-to-newsgroup command. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 4 Jan 1995, Jacqueline Hamilton wrote:

> Date: 4 JAN 1995 10:37:36 -0600 
> From: Jacqueline Hamilton <kira@fohnix.metronet.com>
> Newgroups: comp.mail.pine
> Subject: can I post news from pine? 
> 
> 
> I've got a mail message that I'd like to redirect as a post to a newsgroup.
> Is this doable from pine?  I'm digging through the builtin help but haven't
> found much about news features.
> 
> (I dont want to reply to the message either - just basically bounce it to 
> news)
> 
> Any info appreciated!
> 
> -j.
> 
> 
> -- 
> -Jackie Hamilton
> kira@metronet.com
> http://fohnix.metronet.com/HomePages/kira/newhome.html
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:43:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01510;
	Wed, 11 Jan 95 21:43:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11213;
	Wed, 11 Jan 95 21:36:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11207;
	Wed, 11 Jan 95 21:36:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSI5E-00038RC; Wed, 11 Jan 95 21:28 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: PC-PINE & X.400
Date: Wed, 11 Jan 1995 14:01:51 -0800
Message-Id: <Pine.ULT.3.92.950111135655.18990M-100000@shiva1.cac.washington.edu>
References: <Pine.NXT.3.91.950103095147.24321C-100000@mulberry>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.NXT.3.91.950103095147.24321C-100000@mulberry> 


On Tue, 3 Jan 1995, Nick Boris wrote:

> Date: Tue, 3 JAN 1995 16:02:04 GMT 
> From: Nick Boris <nmboris@artsci.wustl.edu>
> Newgroups: comp.mail.pine
> Subject: PC-PINE & X.400 
> 
> 
> Happy New Year to all!
> 
> Anyway one of these questions may have already been answered here 
> (several times) but I have (repetadly) missed it. The other question may 
> not be appropriate for this gorup (and you are free to tell me so) but I 
> figured that I might as well try.
> 
> 1) I had been trying to set up PC-Pine about a month ago (before romping
> off to CERN for HTML goo and vacation) and was told my my MIS bud that he
> had not installed IMAP systme-wide. When I returned he said that IMAP is
> not up and running so that we sould try to figure out how to get it 
> running now that we are starting to dissimnate a SLIP/PPP package to any 
> of our users who want it.
> 
> Specifically we want (I want) to set it up so that it leaves all the 
> mailboxes on the server machine and leaves all the dial-up clients alone. 

That is the normal operation of PC-Pine...

> Can this be done so that it reads & writes to the multiple folders in the 
> ~/mail directory? 
> 
> What is the syntax for this and for readin from the inbox {artsci.wustl.edu}.
> 

	inbox-path={artsci.wustl.edu}INBOX
	folder-collections={artsci.wustl.edu}mail/[]

> I also remember something about not being able to share a .newsrc between 
> Client and Server. Is this true?
> 

If you access News via NNTP, the .newsrc will be on the client, if you
access it via IMAP, it will be on the server.  This is independent of
whether the client is a PC or Unix user. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Wed Jan 11 21:44:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01544;
	Wed, 11 Jan 95 21:44:40 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11221;
	Wed, 11 Jan 95 21:36:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11215;
	Wed, 11 Jan 95 21:36:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSI5L-00038TC; Wed, 11 Jan 95 21:28 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Pine bug address problem. HELP!
Date: Wed, 11 Jan 1995 14:06:55 -0800
Message-Id: <Pine.ULT.3.92.950111140517.18990O-200000@shiva1.cac.washington.edu>
References: <Pine.OSF.3.91.950104132155.16499E-100000@hawk.anselm.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-250126436-789862015=:18990"
In-Reply-To: <Pine.OSF.3.91.950104132155.16499E-100000@hawk.anselm.edu> 

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-250126436-789862015=:18990
Content-Type: TEXT/PLAIN; charset=US-ASCII


Attached is a diff that fixes a bug in pine/init.c that causes this 
problem.  Apply the patch to the Pine 3.91 distribution are rebuild.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Wed, 4 Jan 1995, Frank Gallant wrote:

> Date: Wed, 4 JAN 1995 13:22:58 -0500 
> From: Frank Gallant <fgallant@anselm.edu>
> Newgroups: comp.mail.pine
> Subject: Pine bug address problem. HELP! 
> 
> 
> 	I have just set up pine for an OSF1 system. Most of it is working 
> fine EXCEPT:
> 	I want the users on the system to report bugs directly to me 
> instead of the standard bug address.  I've changed the bug-fullname and 
> the bug-address in pine.conf file, but it never sees it.  The pine-degug 
> file still shows the original address being read.  Where should i change 
> this information?
> 	Any assistance would be greatly appreciated.
> 
> 
> Happy Computing
> 
> Frank
> 
> 
> 
> 
--0-250126436-789862015=:18990
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="init.c.diff"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.ULT.3.92.950111140655.18990P@shiva1.cac.washington.edu>
Content-Description: 

KioqIHBpbmUzLjkxL3NyYy9waW5lL2luaXQuYwlNb24gT2N0IDEwIDE0OjM0
OjI5IDE5OTQNCi0tLSBwaW5lMy45Mi9zcmMvcGluZS9pbml0LmMJV2VkIE9j
dCAxMiAxMjozNTo0MSAxOTk0DQoqKioqKioqKioqKioqKioNCioqKiAyMDg5
LDIxMDAgKioqKg0KICAgICAgICAgIH0NCiAgDQogICAgICAgICAgLyotLS0g
VmFyIGlzIG5vdCB1c2VyIGNvbnRyb2xsZWQsIGxlYXZlIGl0IGFsb25lIGZv
ciBiYWNrIGNvbXBhdCAtLS0qLw0KISAgICAgICAgIGlmKCF2LT5pc191c2Vy
KXsNCiEgICAgICAgICAgICAgaWYod2hpY2hfdmFycyA9PSBQYXJzZUxvY2Fs
KXsgICAgICAgICAgIA0KICAgICAgICAgICAgICAgICAgcGxpbmUtPmlzX3Zh
ciA9IDA7DQogICAgICAgICAgICAgICAgICBwbGluZS0+bGluZSA9IGNweXN0
cihsaW5lKTsNCiAgICAgICAgICAgICAgICAgIHBsaW5lKys7DQotICAgICAg
ICAgICAgIH0NCiAgICAgICAgICAgICAgY29udGludWU7DQogICAgICAgICAg
fQ0KICANCi0tLSAyMDg5LDIwOTggLS0tLQ0KICAgICAgICAgIH0NCiAgDQog
ICAgICAgICAgLyotLS0gVmFyIGlzIG5vdCB1c2VyIGNvbnRyb2xsZWQsIGxl
YXZlIGl0IGFsb25lIGZvciBiYWNrIGNvbXBhdCAtLS0qLw0KISAgICAgICAg
IGlmKCF2LT5pc191c2VyICYmIHdoaWNoX3ZhcnMgPT0gUGFyc2VMb2NhbCl7
DQogIAkgICAgcGxpbmUtPmlzX3ZhciA9IDA7DQogIAkgICAgcGxpbmUtPmxp
bmUgPSBjcHlzdHIobGluZSk7DQogIAkgICAgcGxpbmUrKzsNCiAgCSAgICBj
b250aW51ZTsNCiAgICAgICAgICB9DQogIA0K
--0-250126436-789862015=:18990--


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:57:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01750;
	Wed, 11 Jan 95 21:57:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15227;
	Wed, 11 Jan 95 21:51:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15221;
	Wed, 11 Jan 95 21:51:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSILL-00038JC; Wed, 11 Jan 95 21:45 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Insert Mode in Pico?
Date: Wed, 11 Jan 1995 14:09:15 -0800
Message-Id: <Pine.ULT.3.92.950111140859.18990Q-100000@shiva1.cac.washington.edu>
References: <3ef0u0$ppb@hobbes.cc.uga.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3ef0u0$ppb@hobbes.cc.uga.edu> 


Pico does not currently support overwrite mode.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 4 Jan 1995, Greg Derda wrote:

> Date: 4 JAN 1995 20:37:20 GMT 
> From: Greg Derda <derda@dogwood.botany.uga.edu>
> Newgroups: comp.mail.pine
> Subject: Insert Mode in Pico? 
> 
> 
> Does anyone know if there is a way to put 'pico' in the insert (typeover)
> mode?  
> 
> Thank you,
> Greg
> ----
> 
> ###########################################################################
> # GREG DERDA                              Network Administrator           #
> # 2502 Plant Sciences                     derda@dogwood.botany.uga.edu    #
> # Department of Botany                    (706) 542-1804                  #
> # University of Georgia                   (706)-542-1805 FAX              #
> # Athens, GA, USA 30602    dogWWWood -->  http://dogwood.botany.uga.edu/  #
> ###########################################################################
> 
> 
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:57:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01771;
	Wed, 11 Jan 95 21:57:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15235;
	Wed, 11 Jan 95 21:51:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15229;
	Wed, 11 Jan 95 21:51:15 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSILS-00038LC; Wed, 11 Jan 95 21:45 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Problems with PCPINE 3.91 and SunOS
Date: Wed, 11 Jan 1995 14:10:38 -0800
Message-Id: <Pine.ULT.3.92.950111141017.18990R-100000@shiva1.cac.washington.edu>
References: <199501050001.TAA21444@aurore.umd.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <199501050001.TAA21444@aurore.umd.edu> 


This bug will be fixed in Pine 3.92.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 5 Jan 1995, Larry Lentner wrote:

> Date: Thu, 5 JAN 1995 00:01:35 GMT 
> From: Larry Lentner <larry@aurore.umd.edu>
> Newgroups: comp.mail.pine
> Subject: Problems with PCPINE 3.91 and SunOS 
> 
> I have the packet driver version of PCPINE 3.91 that I'm using
> to communicate with a Sun Sparcstation 5 running the imapd
> included in the pine 3.91 distribution and sendmail 8.6.9. It's
> also functioning as a nameserver, running BIND 4.9.2.
> 
> When I finish composing a message and go to send the message,
> there's a 30-second delay between the time I hit send and the
> time pcpine drops me back to a prompt. I had a DECstation 5000/25
> running Ultrix 4.3 and BIND 4.9.2 before I replaced it with the
> Sun and I didn't have this problem with the DEC.
> 
> This is causing my impatient users some major headaches. Has
> anyone else experienced this as well or have any suggestions
> on how I might go about fixing it?
> 
> Thanks,
> 
> Larry Lentner
> UMCEES/CBL Computer Center
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 21:57:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01792;
	Wed, 11 Jan 95 21:57:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11449;
	Wed, 11 Jan 95 21:51:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11443;
	Wed, 11 Jan 95 21:51:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSILN-00038KC; Wed, 11 Jan 95 21:45 PST
To: pine-info@cac.washington.edu
From: stern@amath.washington.edu (L.G. "Ted" Stern)
Subject: disabling ^Z
Date: 11 Jan 1995 22:09:23 GMT
Message-Id: <STERN.95Jan11140923@nooksack.amath.washington.edu>

I have a problem frequently while using Pine in X-windows.  I usually
have a Pine window startup up using

        xterm -geometry -n PINE -sb -sl 250 -e /usr/local/bin/pine &

Quite often I hit ^Z instead of ^X, so everything gets screwed up, and even
after doing

        fg <Return>

(blindly), I don't get full screen access anymore.  I have to quit
out of Pine, *blindly*, by hitting ^X <Ret> y <Ret>.

So I'm wondering whether there is either

1)  A way to disable ^Z inside Pine, or

2)  A way to make sure ^Z inside an "xterm -e" process doesn't lose screen
access.


Possibility for (1):

make ^Z bring up the option

        Suspend Pine? [y]

in Unix, or

        Start a DOS process? [y]

in DOS, with a configuration option that could disable ^Z completely.
But option (2) would probably be best and quickest :).

E-mail replies preferred,


--
	-- Ted
 ============================================================================
 Ted Stern (206) 685-8068                        Dept. of Applied Math, FS-20
 stern@amath.washington.edu                      University of Washington
 http://www.amath.washington.edu/~stern/         Seattle, WA  98195
 ============================================================================


From owner-pine-info@cac.washington.edu  Wed Jan 11 22:02:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01957;
	Wed, 11 Jan 95 22:02:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11525;
	Wed, 11 Jan 95 21:56:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11519;
	Wed, 11 Jan 95 21:56:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSIMK-00038MC; Wed, 11 Jan 95 21:46 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Unable to view attachment - HELP
Date: Wed, 11 Jan 1995 14:17:59 -0800
Message-Id: <Pine.ULT.3.92.950111141209.18990S-100000@shiva1.cac.washington.edu>
References: <ellis.789318601@gmi.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ellis.789318601@gmi.edu> 


My best guess is that the list processing software is corrupting or
stripping off the MIME headers as it passes through.  The long term
solution os to get the list manager to fix or repair the list management
software.  In the interim, about all you can do is save the message and
manually reconstruct the mime-version and content-type headers.  They
should be: 

	Mime-Version: 1.0
	Content-Type: multipart/mixed; boundary="0-1982785689-789276093:#6308"


|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 5 Jan 1995, R. Stewart Ellis wrote:

> Date: 5 JAN 95 15:10:01 GMT 
> From: R. Stewart Ellis <ellis@nova.gmi.edu>
> Newgroups: comp.mail.pine
> Subject: Unable to view attachment - HELP 
> 
> I have received a message on a list I subscribe to that allegedly has an
> attachment.  When I view the attachment I get:
> 
>   PINE 3.90 ATTACHED TEXT Folder: INBOX Message 12 of 7,957 TOP   
> 
>   This message is in MIME format.  The first part should be readable text,
>   while the remaining parts are likely unreadable without MIME-aware tools.
> 
> --0-1982785689-789276093:#6308
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> You are all in my address list thanks to the first CONCOM News release
> which listed EVERYBODY.  As a result, I can share with you the search
> [...]
> qualify and be interested, share the job description with that person.
> 
> UNM is taking applications until January 20.  So, please, let us hear
> from you.
> 
> --0-1982785689-789276093:#6308
> Content-Type: TEXT/PLAIN; charset=US-ASCII; name="plnrjobd.txt"
> Content-Transfer-Encoding: BASE64
> Content-ID: <Pine.3.89.9501042033.E6308@hydra.unm.edu>
> Content-Description:
> 
> DQpUSEUgVU5JVkVSU0lUWSBPRiBORVcgTUVYSUNPDQpWQUNBTkNZIEFOTk9V
> TkNFTUVOVA0KDQoNCg0KUE9TSVRJT046CU5FVFdPUksgU0VSVklDRVMgT0ZG
> SUNFUg0KUkVRVUlTSVRJT04gTlVNQkVSOgk5NDI1OTcqQQ0KREVQQVJUTUVO
> [...]
> 
> 
> 
> I know almost nothing about MIME, and I don't know of anyone else locally
> who knows as much as I do.  What is wrong with the attachment that it is not
> being decoded?
> 
> 
> -- 
>   R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
>   Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
>   Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
>   Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 22:22:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02578;
	Wed, 11 Jan 95 22:22:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15673;
	Wed, 11 Jan 95 22:18:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15667;
	Wed, 11 Jan 95 22:18:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSIjz-00038CC; Wed, 11 Jan 95 22:10 PST
To: pine-info@cac.washington.edu
From: Steven Feinholz <sf3@hostsw7>
Subject: Enhancement Suggestions
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SUN.3.91.950111165553.23954N-100000@hostsw7>
Mime-Version: 1.0
Date: Thu, 12 Jan 1995 00:56:41 GMT


I have 2 enhancement suggestions for easier use of Pine
(they will actually save the user a lot of time):

1. when using Pine as a newsreader for internet newsgroups,
   and I am done with a particular newsgroup, pressing "L"
   returns me to the screen which shows:

       [ Select Here To See Expanded List ]

   It would be nice, and would save time, to be placed back
   into the last expanded list. Otherwise I have to press
   <CR> and wait for the expanded list of newsgroups to be
   generated again.

   When I am in normal (local) email folders and I press "L",
   I am returned to the screen which show my list of folders.
   The newsgroup (remote) list should work the same.

2. Is there a way to show the number of messages on a particular
   newsgroup list from the "Expanded List" screen so that I get
   a visual notification of which newsgroups have messages
   without having to Select the newsgroup?

Thanks.

________________________________________________________________________
 ====  AT&T        | Steven Feinholz        | VOICEplus: 427-5945
=--=== Global      | Client Software        | Phone:     (310) 524-5945
=--=== Information | 100 N. Sepulveda Blvd. | FAX:       (310) 524-5515
 ====  Solutions   | El Segundo, Ca  90245  | sf3@ElSegundoCA.ATTGIS.com
________________________________________________________________________





From owner-pine-info@cac.washington.edu  Wed Jan 11 22:26:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02830;
	Wed, 11 Jan 95 22:26:52 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12006;
	Wed, 11 Jan 95 22:21:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12000;
	Wed, 11 Jan 95 22:21:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSIlM-00038JC; Wed, 11 Jan 95 22:12 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Need help in creating mailing list
Date: Wed, 11 Jan 1995 14:27:22 -0800
Message-Id: <Pine.ULT.3.92.950111142214.18990T-100000@shiva1.cac.washington.edu>
References: <3e414i$o00@cronkite.ocis.temple.edu> <Pine.ULT.3.92.950103122043.27331d-100000@shiva1.cac.washington.edu> <Pine.SUN.3.91.950105183230.29807B-100000@mack>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.91.950105183230.29807B-100000@mack> 


The format of a simple entry in the addressbook is

	nickname<TAB>full name<TAB>address

The format of a distribution list is

	nickname<TAB>list name<TAB>(address,address,...address)

Just convert your list into that form and Pine can read it as an 
addressbook.  Go to the Setup/Config screen and Add it to the 
address-book entry.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 5 Jan 1995, Phil Safier wrote:

> Date: Thu, 5 JAN 1995 18:35:02 -0700 
> From: Phil Safier <psafier@rt66.com>
> Newgroups: comp.mail.pine
> Subject: Need help in creating mailing list 
> 
> Can someone point me to help files on working with mailing lists in the 
> addressbook. I have about 19K worth of names and addresses but can't 
> figure out how to put them into my addressbook at one shot.
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 22:27:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02851;
	Wed, 11 Jan 95 22:27:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15732;
	Wed, 11 Jan 95 22:21:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15726;
	Wed, 11 Jan 95 22:21:21 -0800
Received: by rain.psg.com (Smail3.1.29.1 #26)
	id m0rSIlQ-00038KC; Wed, 11 Jan 95 22:12 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Does PINE supports Internet firewalls.
Date: Wed, 11 Jan 1995 14:30:37 -0800
Message-Id: <Pine.ULT.3.92.950111142838.18990U-100000@shiva1.cac.washington.edu>
References: <199501052333.SAA22988@maple.cgin.us-md.citicorp.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <199501052333.SAA22988@maple.cgin.us-md.citicorp.com> 


Pine does not have any special provisions for firewalls, but then Pine
typically would not be dealing with a firewall directly.  If you are
trying to access a remote folder across a firewall via IMAP there might
be a problem, but I don't know what the issues are there... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 5 Jan 1995, Global LAN Design, CGIN, (703) 708-1256 wrote:

> Date: Thu, 5 JAN 1995 23:33:30 GMT 
> From: Global LAN Design, CGIN, (703) 708-1256 <Vic.Gupta@citicorp.com>
> Newgroups: comp.mail.pine
> Subject: Does PINE supports Internet firewalls. 
> 
> Hi:
> 
> I wanted to know if PINE supports Internet Firewalls.
> 
> Thanks.
> 
> 
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 11 23:31:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04283;
	Wed, 11 Jan 95 23:31:26 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12876;
	Wed, 11 Jan 95 23:26:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12870;
	Wed, 11 Jan 95 23:26:26 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 12 Jan 95 15:24:52 -0800
Date: Thu, 12 Jan 1995 15:24:52 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: "L.G. Ted Stern" <stern@amath.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: disabling ^Z
In-Reply-To: <STERN.95Jan11140923@nooksack.amath.washington.edu>
Message-Id: <Pine.SOL.3.91.950112152250.1367A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 11 Jan 1995, L.G. Ted Stern wrote:

> I have a problem frequently while using Pine in X-windows.  I usually
> have a Pine window startup up using
> 
>         xterm -geometry -n PINE -sb -sl 250 -e /usr/local/bin/pine &
> 
> Quite often I hit ^Z instead of ^X, so everything gets screwed up, and even
> after doing
> 
>         fg <Return>
> 
> (blindly), I don't get full screen access anymore.  I have to quit
> out of Pine, *blindly*, by hitting ^X <Ret> y <Ret>.
> 
> So I'm wondering whether there is either
> 
> 1)  A way to disable ^Z inside Pine, or
> 
> 2)  A way to make sure ^Z inside an "xterm -e" process doesn't lose screen
> access.
> 
> 
> Possibility for (1):
> 
> make ^Z bring up the option
> 
>         Suspend Pine? [y]
> 
> in Unix, or
> 
>         Start a DOS process? [y]
> 
> in DOS, with a configuration option that could disable ^Z completely.
> But option (2) would probably be best and quickest :).
> 

	Are you using pine 3.9x?

	Have you looked in the Configuration menus?

	Have you found:

         [X]  enable-suspend          ???

	Is it enabled, as above?  Try disabling it?

	Good Luck....

				Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 11 23:52:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04666;
	Wed, 11 Jan 95 23:52:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13141;
	Wed, 11 Jan 95 23:47:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13135;
	Wed, 11 Jan 95 23:47:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSK72-00038CC; Wed, 11 Jan 95 23:38 PST
To: pine-info@cac.washington.edu
From: ao826@FreeNet.Carleton.CA
Control: cancel <D29q3u.F4s@freenet.carleton.ca>
Subject: cancel
Message-Id: <D29qsp.Fxy@freenet.carleton.ca>
Date: Thu, 12 Jan 1995 01:29:12 GMT

Article cancelled from nr
--
__David Hosten__Publishing Editor__International Free Press_Electronic
ao826@freenet.carleton.ca|dhosten@freenet.fsu.edu|dhosten@ifp.synapse.net
____Department Of Mass Communications___University Of Ottawa__CAN____
//////Unless otherwise stated, comments made here are my own\\\\\\\\


From owner-pine-info@cac.washington.edu  Wed Jan 11 23:54:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04703;
	Wed, 11 Jan 95 23:54:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13163;
	Wed, 11 Jan 95 23:49:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.Germany.EU.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13157;
	Wed, 11 Jan 95 23:49:43 -0800
Received: by mail.Germany.EU.net with UUCP (8.6.5:29/EUnetD-2.5.1.c) via EUnet
	id IAA27990; Thu, 12 Jan 1995 08:51:25 +0100
Received: from sun51.fz.telekom.de (sun51.fz.telekom.de [192.166.56.95]) by mailserver.fz.telekom.de (8.6.5/8.6.5) with SMTP id IAA00942 for <pine-info@cac.washington.edu>; Thu, 12 Jan 1995 08:44:56 +0100
Received: by sun51.fz.telekom.de (4.1/SMI-4.1)
	id AA00893; Thu, 12 Jan 95 08:47:21 +0100
Date: Thu, 12 Jan 1995 08:47:21 +0100 (MET)
From: Ralf Widera <widera@fz.telekom.de>
To: pine-info@cac.washington.edu
Subject: Re: alt editor not use TEMP: Bug or feature?
In-Reply-To: <Pine.SUN.3.91.950111171847.17995L-100000@bootes.cus.cam.ac.uk>
Message-Id: <Pine.SUN.3.91.950112084535.886B@sun51.fz.telekom.de>
"Reply-To: widera@fz.telekom.de"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have also wondered about this behaviour.
I think it is a bug.

------------------------------------------------------------------------------
Ralf Widera, FZ 211b                               Email: widera@fz.telekom.de
DBP Telekom FTZ                                                DBP Telekom FTZ
Forschungs- und Technologiezentrum                             Research Center
Am Kavalleriesand 3 (Postfach 10 00 03)                       PO Box: 10 00 03
64276 Darmstadt                                              D-64276 Darmstadt
06151/83-3855, FAX: 06151/83-4066      +49 6151 83 3855, FAX: +49 6151 83 4066

> Date: Wed, 11 Jan 1995 17:27:49 +0000
> From: Barry Landy <bl10@cus.cam.ac.uk>
> To: pine-info@cac.washington.edu
> Subject: alt editor not use TEMP: Bug or feature?
> 
> One of my (new) user of PC-PINE is complaining at the following.
> When calling the editor, Pine (appears) to specify a file name in the 
> root directory. This means that if the editor makes backups of files as 
> they are being made (eg on a time basis) they pile up in root. In 
> addition, should a reboot occur (even when using Pico), broken bits are left 
> also in root.
> 
> He states, and I think that I agree with him, that the Dos TEMP variable 
> should be used (if present) to indicate a suitable temporary directory. 
> In some circumstances, Pine uses TMP, but not in this one.
> 
> Do others agree that this is a bug?
> 
> =======================================================================
> Barry Landy, Head of Systems and Development,
> University of Cambridge Computing Service
> Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713


From owner-pine-info@cac.washington.edu  Thu Jan 12 00:01:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04881;
	Thu, 12 Jan 95 00:01:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13252;
	Wed, 11 Jan 95 23:56:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13246;
	Wed, 11 Jan 95 23:56:32 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSKEu-00038PC; Wed, 11 Jan 95 23:46 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: change id name?
Date: Wed, 11 Jan 1995 15:46:29 -0800
Message-Id: <Pine.ULT.3.92.950111154350.18990o-100000@shiva1.cac.washington.edu>
References: <3elun8$egm@news.csus.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3elun8$egm@news.csus.edu> 


On 7 Jan 1995, a wong wrote:

> Date: 7 JAN 1995 11:42:32 GMT 
> From: a wong <eunos@mercury.sfsu.edu>
> Newgroups: comp.mail.pine
> Subject: change id name? 
> 
> I want to change the id  in pine. For ex.
> 
>                     007@school.edu  
>           
>                to   Al@school.edu 
>                     (I want to change or remove 007 ,is this possible?)
> 
> So far I can do this only  Al 007@school.edu
>                               ^^^ still here.             
> 

You can add a Reply-To header in the customized-hdrs entry of the 
Setup/Config screen.  Alternatively, there is a compile-time option that 
allows you to alter the From: header.

> 
> 
> (by configuring  the option menu)
> 
> 
> Also, is there any way to change the IP (domain) address? That is ,from
> @school.edu to @home.edu for ex.? I have already tried the  config
> . values , I can modify this part but once the mail is sent it cannot
> leave my mail system.  I guess to send out mail , the return address
> must be identifiable before mail is to leave the local host? 
> 

This sounds like something your local mail transfer agent is imposing,
and would probably also prevent altering the From: header... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Thu Jan 12 00:01:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04910;
	Thu, 12 Jan 95 00:01:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16954;
	Wed, 11 Jan 95 23:56:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16948;
	Wed, 11 Jan 95 23:56:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSKEi-00038MC; Wed, 11 Jan 95 23:46 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Export marked block from Pine?
Date: Wed, 11 Jan 1995 15:39:36 -0800
Message-Id: <Pine.ULT.3.92.950111153838.18990n-100000@shiva1.cac.washington.edu>
References: <3elbom$sk7@news.primenet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3elbom$sk7@news.primenet.com> 


On 7 Jan 1995, William Smithers wrote:

> Date: 7 JAN 1995 06:19:02 GMT 
> From: William Smithers <bilwil@Primenet.Com>
> Newgroups: comp.mail.pine
> Subject: Export marked block from Pine? 
> 
>   I find no way to export a marked block of text from Pine message to a 
> file. Is there a way?
> 

Not at this time.

>   Will there come a time when Pine exhibits two windows on receiving the 
> Reply command?: Inbox mail in the top window; reply-being-composed in 
> bottom window; marked block can be transferred from one to another.
> 

Perhaps, but we don't have any current plans to do so...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Thu Jan 12 00:13:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05159;
	Thu, 12 Jan 95 00:13:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17100;
	Thu, 12 Jan 95 00:06:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17094;
	Thu, 12 Jan 95 00:06:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSKQa-00038CC; Wed, 11 Jan 95 23:58 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: pine 3.90 eating CPU on exit
Date: Wed, 11 Jan 1995 15:56:52 -0800
Message-Id: <Pine.ULT.3.92.950111155624.18990q-100000@shiva1.cac.washington.edu>
References: <3epc31$d43@news.primenet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3epc31$d43@news.primenet.com> 


Pine 3.91 fixes at least part of the causes for this looping...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 8 Jan 1995, Brandon Lee Poyner wrote:

> Date: 8 JAN 1995 18:49:05 GMT 
> From: Brandon Lee Poyner <poyner@primenet.com>
> Newgroups: comp.mail.pine
> Subject: pine 3.90 eating CPU on exit 
> 
> My internet provider uses pine 3.90 running on BSDI.  Every time I exit  
> pine, it just hangs.  It would hang as long as it could, except that i 
> terminate it with a interupt (^C)
> 
> I have pine aliased to 'pine -d 0 -i -z' .. so that I don't get debug 
> information (-d 0), initially i go into the incoming folder (-i) and I 
> want it to respond to control-z (-z)
> 
> I just logged in twice (via PPP) to see what's happening, and did a 
> 'ps ugx' upon my attempt to exit pine.  Here's what I got...
> 
> USER       PID %CPU %MEM   VSZ  RSS TT  STAT STARTED       TIME COMMAND
> poyner   29541 82.8  0.0  1196  584 pe  R+   11:09PM    0:56.21 pine 0
> poyner   29458  0.0  0.0   572  460 q2  Ss   11:08PM    0:00.68 -bash (bash)
> poyner   29430  0.0  0.0   572  468 pe  Is   11:08PM    0:00.52 -bash (bash)
> poyner   29681  0.0  0.0   272  200 q2  R+   11:11PM    0:00.03 ps -ugx
> 
> I believe it's the -d 0 option that causes this, but to have one process 
> eating 82% CPU really isn't good for the system.  
> 
> I've also used an older (i believe) version of pine and not had this problem 
> with the same command line, but that was also on Ultrix.
> 
> Anybody know what causes this?  Thanks.
> 
>   ____________________________________________________________ ______________
>  )_/~~~~~\____/~~~\___/~~~~~\___/~~\/~~\____/~~~~\___/~~~~\___| poyner@      (
> (__/~\ /~~\__/~\ /~\__/~\   ___/~\/~~\/~\__/~\  /~\__/~\  /~\_|  primenet.com )
>  )_/~\_/~~\__/~~~~~\__/~~~~~\__/~\____/~\__/~\__/~\__/~\__/~\_:--------------(
> (__/~\_/~~\__/~\ /~\__/~\   ___/~\____/~\__/~\__/~\__/~\__/~\_| http://www.   )
>  )_/~~~~~\___/~\_/~\__/~~~~~\__/~\____/~\___/~~~~\___/~\__/~\_| primenet.com (
> (___------____-___-____-----____-______-_____----_____-____-__| /~poyner/     )
>  )-----------------------------------------------------------~---------------(
> ( Price does not include tacks? TACKS? I don't want TACKS in my food! oh, tax )
>  `---------------------------------------------------------------------------'
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 02:24:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08219;
	Thu, 12 Jan 95 02:24:53 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18884;
	Thu, 12 Jan 95 02:17:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailgzrz.TU-Berlin.DE by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18878;
	Thu, 12 Jan 95 02:17:43 -0800
Received: from ftsu09.ee.TU-Berlin.DE by mailgzrz.TU-Berlin.DE with SMTP (PP);
          Thu, 12 Jan 1995 11:08:12 +0100
Date: Thu, 12 Jan 1995 11:10:27 +0100 (MET)
From: Andreas Niebank <niebank@ftsu00.ee.TU-Berlin.DE>
To: Jon Peatfield <J.S.Peatfield@amtp.cam.ac.uk>
Cc: pine-info@cac.washington.edu
Subject: Re: problem when tmp directory is full
In-Reply-To: <J.S.PEATFIELD.95Jan11134038@kro.amtp.cam.ac.uk>
Message-Id: <Pine.SUN.3.91.950112110006.29341B-100000@ftsu09.ee.tu-berlin.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 11 Jan 1995, Jon Peatfield wrote:

> We have Pine 3.91 running on a variety of machines.  Recently we
> noticed that on some of them at least when the tmp directory that pine
> stores messages in when sending to sendmail gets full the messages get
> lost and the user isn't warned.
> 
> 
> Looking at the code in osdep/sendmail it looks like an error from
> pine_rfc822_output() will result in a warning for the user:
> 
> >   q_status_message2(1, 2, 4, "\007Error \"%s\" writing \"%s\"",
> >                          error_description(save_errno), pretty_fn(filename));
> 
> but I see no such message.  Looking deaper into pine_rfc822_output() I
> can see that the error chain looks ok 'til I get lost inside
> pine_rfc822_output_body() where I can't tell what is happening.
> 
> Does anyone else see this or is it a symptom of a problem with our
> setup?
> 

Using pine 3.91 on our Sun Sparc's (SunOS4.1.3) an error message flashes 
only a very short moment, when the file system is full (not only the tmp-area).
Therefore it's sometimes a game of luck if you take notice of it or not.
I'd like pine to double-beep and to wait until I took notice on the error/
warning which occured (typing a key to continue). 
The pine team may consider it as a suggestion for the next release.

	Andreas Niebank

==============================================================================



From owner-pine-info@cac.washington.edu  Thu Jan 12 07:13:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14536;
	Thu, 12 Jan 95 07:13:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22249;
	Thu, 12 Jan 95 06:42:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from inet-gw-1.pa.dec.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22243;
	Thu, 12 Jan 95 06:42:30 -0800
Received: from vodka.rhc.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94)
	id AA02059; Thu, 12 Jan 95 06:38:25 -0800
Received: by vodka.rhc.dec.com (5.61/1.34)
	id AA12746; Thu, 12 Jan 95 14:38:53 GMT
Date: Thu, 12 Jan 1995 14:38:52 +0000 (GMT)
From: Lager Lout <cbh@vodka.rhc.dec.com>
To: pine-info@cac.washington.edu
Subject: Re: Does PINE supports Internet firewalls.
In-Reply-To: <Pine.ULT.3.92.950111142838.18990U-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SV4.3.90.950112143601.12656A-100000@vodka.rhc.dec.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 5 Jan 1995, Global LAN Design, CGIN, (703) 708-1256 wrote:

> Date: Thu, 5 JAN 1995 23:33:30 GMT 
> From: Global LAN Design, CGIN, (703) 708-1256 <Vic.Gupta@citicorp.com>
> Newgroups: comp.mail.pine
> Subject: Does PINE supports Internet firewalls. 
> 
> Hi:
> 
> I wanted to know if PINE supports Internet Firewalls.
> 
> Thanks.

if you're talking in terms of sending/receiving mail using Pine, then
it really depends on which delivery agent you're using.  Sendmail is
intelligent enough to work its way around firewalls (as this message proves,
as Digital uses a firewall to isolate its network!)
Cheers,

Chris.

"If the world was an orange it would be like much too small, y'know?" - Neil'83
Chris Hedley                                    email: cbh@vodka.wlo.dec.com
Digital Equipment Corporation ltd               phone: +44 707 374325
Welwyn, Hertfordshire, England                    fax: +44 707 374302



From owner-pine-info@cac.washington.edu  Thu Jan 12 07:50:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15597;
	Thu, 12 Jan 95 07:50:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22558;
	Thu, 12 Jan 95 07:01:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from alpha.loyno.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22552;
	Thu, 12 Jan 95 07:01:37 -0800
Received: by alpha.loyno.edu; (5.65/1.1.8.2/22Jul94-0234PM)
	id AA06687; Thu, 12 Jan 1995 09:03:05 +0100
Date: Thu, 12 Jan 1995 09:03:04 +0100 (MET)
From: Mary Aplin <aplin@alpha.loyno.edu>
To: pine <pine-info@cac.washington.edu>
Subject: Re: repost: Pine/VMS FTP site in US
In-Reply-To: <1995Jan7.184624.17081@galileo.cc.rochester.edu>
Message-Id: <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Sat, 7 Jan 1995, Thomas Guptill wrote:

> 
> 	Since there has been a bit of traffic about it recently, I figured
> I'd let people know again that VMS-Pine v3.91 is available for anonymous ftp
> from lenin.cc.rochester.edu.  Extracting it requires a recent version of
> UNZIP, and you MUST remember to transfer it as a binary.  This version
> provides improved TCPIP support, but I've found that 3.89 seems to work
> better under my installation of VMS (5.4-2).  (I'm not using TCPIP support,
> since I only use it for local mail and I need to talk to PMDF anyway.) BTW: 
> Congratulations to the development team; it's a great program.  
> 
Does anyone know where I can get UNZIP for VMS??

Thanks,
Mary Aplin
Loyola Univeristy, New Orleans


From owner-pine-info@cac.washington.edu  Thu Jan 12 08:52:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17864;
	Thu, 12 Jan 95 08:52:20 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20592;
	Thu, 12 Jan 95 08:43:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [141.206.10.110] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20586;
	Thu, 12 Jan 95 08:43:27 -0800
Received: from hostsw7.ElSegundoCA.NCR.COM (hostsw7.ElSegundoCA.ATTGIS.COM) by mailhost.ElSegundoCA.ATTGIS.COM (4.1/SMI-4.1)
	id AA03434; Thu, 12 Jan 95 08:42:36 PST
Received: by hostsw7.ElSegundoCA.NCR.COM (4.1/SMI-4.1)
	id AA25910; Thu, 12 Jan 95 08:42:55 PST
Date: Thu, 12 Jan 1995 08:42:55 -0800 (PST)
From: Steven Feinholz <sf3@ElSegundoCA.ATTGIS.COM>
X-Sender: sf3@hostsw7
To: David L Miller <dlm@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Need help in creating mailing list
In-Reply-To: <Pine.ULT.3.92.950111142214.18990T-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950112084033.25906A-100000@hostsw7>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I just tried to place a distribution list inside my address book
and it looks like the syntax is not quite right. What I found is
that:

   nickname<TAB>list-name<TAB>(address,address,...,address)

must be:

   nickname<TAB>list-name<TAB>"(address,adrress,...,address)"

The quotes are very important.

________________________________________________________________________
 ====  AT&T        | Steven Feinholz        | VOICEplus: 427-5945
=--=== Global      | Client Software        | Phone:     (310) 524-5945
=--=== Information | 100 N. Sepulveda Blvd. | FAX:       (310) 524-5515
 ====  Solutions   | El Segundo, Ca  90245  | sf3@ElSegundoCA.ATTGIS.com
________________________________________________________________________


On Wed, 11 Jan 1995, David L Miller wrote:

> 
> The format of a simple entry in the addressbook is
> 
> 	nickname<TAB>full name<TAB>address
> 
> The format of a distribution list is
> 
> 	nickname<TAB>list name<TAB>(address,address,...address)
> 
> Just convert your list into that form and Pine can read it as an 
> addressbook.  Go to the Setup/Config screen and Add it to the 
> address-book entry.
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Thu, 5 Jan 1995, Phil Safier wrote:
> 
> > Date: Thu, 5 JAN 1995 18:35:02 -0700 
> > From: Phil Safier <psafier@rt66.com>
> > Newgroups: comp.mail.pine
> > Subject: Need help in creating mailing list 
> > 
> > Can someone point me to help files on working with mailing lists in the 
> > addressbook. I have about 19K worth of names and addresses but can't 
> > figure out how to put them into my addressbook at one shot.
> > 
> > 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 11:13:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24997;
	Thu, 12 Jan 95 11:13:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27916;
	Thu, 12 Jan 95 11:04:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27910;
	Thu, 12 Jan 95 11:04:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSUhi-00038MC; Thu, 12 Jan 95 10:57 PST
To: pine-info@cac.washington.edu
From: idjfc@imap1.asu.edu
Subject: Re: printer
Date: 12 Jan 1995 07:12:26 GMT
Message-Id: <3f2koq$rre@news.asu.edu>
References: <D23CtH.E76@nbn.com>

tbear (tbear@calon.com) wrote:

: Help I have a problem with my printer using pine. I have a IBM PS/2 Model 
: 30 with mcga screen. My printer is an Epson Action Printer 2250. When I 
: tell the pine to use ansi to ansi and then ask it to print what is in my 
: mail box I get nothing to print. I am not very good at computers but I do 
: understand the basics. Could anyone help with my problem.

: Thank you in advance,

: Tbear

Sorry to see someone other then me is also having printing problems in 
Pine and not getting any answers from the Group.  I know they are very 
busy, but being a Newby also, we are anxious to get on with our work.  I 
posted about a week ago, have read all the FAQs and just can't solve the 
problem.  I think in my case that the System Operator may have an option 
available that doesn't make printing possible.  Have sent a msg to the 
Sys Op, but to no avail.  In my case, when I ask for the printer, it 
actully captures the article and writes it to my hard disk, and of course 
I can then print from there.  You may check your hard disk and see if 
there is a file name "CAPFILE" or something near that.  Maybe someone out 
there will answer us soon.

JB

                                END OF MESSAGE


From owner-pine-info@cac.washington.edu  Thu Jan 12 11:13:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25018;
	Thu, 12 Jan 95 11:13:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23971;
	Thu, 12 Jan 95 11:07:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23965;
	Thu, 12 Jan 95 11:07:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSUiL-00038PC; Thu, 12 Jan 95 10:57 PST
To: pine-info@cac.washington.edu
From: glenn@creator.ucns.uga.edu (Glenn Leavell)
Subject: customizing which headers displayed
Date: 12 Jan 1995 16:39:17 GMT
Message-Id: <3f3lvl$685@hobbes.cc.uga.edu>

When Pine is displaying the text of incoming mail in its default state 
of "full headers OFF", it shows the standard headers like "From:", "To:",
"Date:", "Subject:", etc.  Is there a way to customize this so that other
specific headers can be displayed without turning on full headers?

Thanks for any help.

-- 
Glenn Leavell  University of Georgia  glenn@creator.ucns.uga.edu  706-542-3135
    University Computing and Networking Services, Athens, GA USA 30602-1911


From owner-pine-info@cac.washington.edu  Thu Jan 12 11:13:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25074;
	Thu, 12 Jan 95 11:13:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28002;
	Thu, 12 Jan 95 11:07:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27996;
	Thu, 12 Jan 95 11:07:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSUj1-00038RC; Thu, 12 Jan 95 10:58 PST
To: pine-info@cac.washington.edu
From: idjfc@imap1.asu.edu
Subject: Re: printer
Date: 12 Jan 1995 09:23:07 GMT
Message-Id: <3f2sdr$sun@news.asu.edu>
References: <D23CtH.E76@nbn.com>

tbear (tbear@calon.com) wrote:

: Help I have a problem with my printer using pine. I have a IBM PS/2 Model 
: 30 with mcga screen. My printer is an Epson Action Printer 2250. When I 
: tell the pine to use ansi to ansi and then ask it to print what is in my 
: mail box I get nothing to print. I am not very good at computers but I do 
: understand the basics. Could anyone help with my problem.

: Thank you in advance,

: Tbear

     I have had printer problems also and can't seem to get a response.  
I think everyone must be extremely busy.  I posted a question about a 
week ago and still no response.  I discovered that when I wanted to 
print, that the article was being "captured" and sent to the hard disk.  
I can then of course print the file from the hard disk, it is just a 
major annoyance.  I suspect that the System Operators may have the option 
of not making printing available to the system users.  I have sent a query 
to the Sys Op, but no response from there either.  I, too, am a Newby so 
it is frustrating to try to learn and to be able to find help.  check 
your hard disk and see if you have a file named "CAPFILE".  If so, you can 
print out your article from there.  Hope this was some help.

JB 


From owner-pine-info@cac.washington.edu  Thu Jan 12 11:49:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26541;
	Thu, 12 Jan 95 11:49:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24868;
	Thu, 12 Jan 95 11:42:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24862;
	Thu, 12 Jan 95 11:42:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSVJ7-00038JC; Thu, 12 Jan 95 11:35 PST
To: pine-info@cac.washington.edu
From: pucho@netcom.com (Marcos Rubinstein)
Subject: Inbox empty... NOT!
Message-Id: <puchoD2AFqC.ACE@netcom.com>
Date: Thu, 12 Jan 1995 10:27:48 GMT

I'm reposting from netcom.mail 
to understand the question....
Netcom uses pine 3.89
but a group of users can acces 3.91 ... from a public dir...
I use 3.91 and never had any problem... I read also about some user 
complaining about 3.91 corrupting their inbox... but didn't send any 
details..
any ideas?... or... need more info?... let me now...
TIA
pucho@netcom.com

-------------------article in netcom.mail follws----------------
Subject: Re: NUGLOPS version of PINE
Newsgroups: netcom.mail
References: <mzamokD2ABto.1tE@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)

Mark Zamok (mzamok@netcom.com) decia:

: Ok, I found the newer version of PINE in the NUGLOPS directory, and 
: created an alias pointing to it. (The Nuglops are is already in my path) 
: I run it, and it works fine, sees my existing mail folders. Logout, login 
: the next day (After LOTS of redials - this is the Irvine POP, after all)
: and am greeted with You have Mail after the MOTD. So, I run PINE, and it 
: runs the new version, opens folder INBOX, and shows me....no mail! I 
: press l(ist) folders, they're all there, but INBOX is empty. I quit pine, 
: type unalias pine, and re-enter pine. Now running the older 3.89 version, 
: it shows me my 2 new messages in INBOX. Anybody know the magic trick to 
: making 3.91 work? I'd appreciate any help that was offered.  

: Thanks!




From owner-pine-info@cac.washington.edu  Thu Jan 12 12:06:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27585;
	Thu, 12 Jan 95 12:06:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29249;
	Thu, 12 Jan 95 12:01:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29241;
	Thu, 12 Jan 95 12:00:58 -0800
Received: from localhost by shiva2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25399;
	Thu, 12 Jan 95 12:00:40 -0800
Date: Thu, 12 Jan 1995 12:00:39 -0800 (PST)
From: Michael Seibel <mikes@cac.washington.edu>
To: Barry Landy <bl10@cus.cam.ac.uk>
Cc: pine-info@cac.washington.edu
Subject: Re: alt editor not use TEMP: Bug or feature?
In-Reply-To: <Pine.SUN.3.91.950111171847.17995L-100000@bootes.cus.cam.ac.uk>
Message-Id: <Pine.ULT.3.92.950112115737.17800H-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

This is indeed a bug, and it will be fixed in the 3.92 release.  Thanks! 

-mikes


On Wed, 11 Jan 1995, Barry Landy wrote, in part:

> In some circumstances, Pine uses TMP, but not in this one.
> 
> Do others agree that this is a bug?


From owner-pine-info@cac.washington.edu  Thu Jan 12 12:42:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28917;
	Thu, 12 Jan 95 12:42:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00147;
	Thu, 12 Jan 95 12:33:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00140;
	Thu, 12 Jan 95 12:33:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSW6m-00038JC; Thu, 12 Jan 95 12:27 PST
To: pine-info@cac.washington.edu
From: bbs.america@loa.com (BBS AMERICA)
Subject: cmsg cancel <8A16467.04D60000DA.uuout@loa.com>
Control: cancel <8A16467.04D60000DA.uuout@loa.com>
Date: Wed, 11 Jan 95 18:47:00 -0400
Message-Id: <cancel.8A16467.04D60000DA.uuout@loa.com>

SPAM Cancelled by MAPS 1.1


From owner-pine-info@cac.washington.edu  Thu Jan 12 12:45:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29030;
	Thu, 12 Jan 95 12:45:01 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26103;
	Thu, 12 Jan 95 12:37:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26097;
	Thu, 12 Jan 95 12:37:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSWBM-00038KC; Thu, 12 Jan 95 12:31 PST
To: pine-info@cac.washington.edu
From: Mark Crispin <mrc@CAC.Washington.EDU>
Subject: Re: Need help with pine and pop/imap
Date: Wed, 11 Jan 1995 23:27:09 -0800
Message-Id: <Pine.NXT.3.92.950111232326.25660B-100000@Tomobiki-Cho.CAC.Washington.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3f1rni$su7@spruce.cic.net> 

This is undocumented *and* unsupported *and* there is no guarantee of it
being there in the future, but {host/pop3}INBOX works as a mailbox
specifier in Pine.  Only INBOX is permitted, due to limitations of POP3.

I hope you are patient, because Pine will generate a lot more network 
traffic if it has to use POP3 than it would if it used IMAP.  Also, you 
can forget about flags (seen, deleted, etc) sticking in the mailbox 
between sessions.

Bottom line: it's better to use IMAP.

-- Mark --

On 12 Jan 1995, Paul Southworth wrote:

> 
> In article <Pine.HPP.3.91.950111112058.15888A-100000@bon.eng.ohio-state.edu>,
> James Vaughn Brown  <brownj@bon.eng.ohio-state.edu> wrote:
> >I need help getting pine to work with a pop server.  Can this be done?  I 
> >think Imap is a superset of pop, and should be able to access the pop 
> >servers, provided you tell Pine that it is a pop server.
> 
> [follow-ups set to comp.mail.pine -- I'm sure those folks will correct
> the following comments if they're not right...]
> 
> I think this will not work.  IMAP has a number of fundamental
> differences from POP.  You should run an IMAP server if you want to run
> Pine.  Otherwise you need a real POP mail client.  I don't believe there
> is any configuration option in pine to change the service or port number
> it connects to -- it's set to 143/tcp (IMAP).  pop3 wants 110/tcp.  I don't
> think you can change that outside of the source code, and I also don't
> think it would work even if you did.
> 
> According to the pine manual, the c-client library doesn't do POP:
> 
>    Currently  it  understands  Berkeley  mail
>    files, Tenex mail files, the IMAP2bis protocol, and NetNews.
> 
> >My problem arises in that I do not know how to specify a user name or a 
> >password for the other system.  Could anyone help me with this.  
> 
> In pine 3.91, this is handled in the online configuration process.
> For earlier versions, you edit .pinerc's "inbox path" according to
> the comments in the .pinerc file:
> 
>   # Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
>   # Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
>   inbox-path=
> 
> Note that it will assume your remote user name is the same as your 
> local user name, but you can override that when it connects (it will
> prompt with a default of the local user name).
> 
> --
> Paul Southworth
> CICNet Systems Support
> pauls@cic.net
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 12:58:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29722;
	Thu, 12 Jan 95 12:58:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00472;
	Thu, 12 Jan 95 12:53:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00466;
	Thu, 12 Jan 95 12:53:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSWMs-00038JC; Thu, 12 Jan 95 12:43 PST
To: pine-info@cac.washington.edu
From: cc0luism@lucano (Luis Melendez Aganzo)
Subject: Re: Pine on Sparc Solaris 2.4?
Date: 11 Jan 1995 15:32:52 GMT
Message-Id: <3f0tn4$12n@obelix.cica.es>
References: <netsD27p8B.H9s@netcom.com>

H. Paul Hammann (nets@netcom.com) wrote:
:     I am having a difficult time getting Pine compiled for Solaris 2.4
: using gcc 2.6.3.  If anyone that has installed Pine on a sparc Solaris
: 2.4 box has any hints they'd like to pass along I'd be very grateful.
: If there is sufficient interest I'll summarize to this newsgroup.
: Thanks in advance for any help.

You can download the pine 3.91 executable for Solaris2.3 from our
FTP server:  

    ftp://ftp.uco.es/luism/Solaris2.3/pine3.91.gz

--
+-----------------------------------^---------------------------------------+
| Luis Melendez                     ^  email: cc0luism@lucano.uco.es        |
| Centro de Calculo Cientifico      ^  Tlf: 957-218119                      |
| Universidad de Cordoba (SPAIN)    ^  MIME Spoken Here                     |
| gopher://gopher.uco.es            ^  http://www.uco.es                    |
+-----------------------------------^---------------------------------------+



From owner-pine-info@cac.washington.edu  Thu Jan 12 13:48:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02463;
	Thu, 12 Jan 95 13:48:22 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27672;
	Thu, 12 Jan 95 13:40:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from oeonline.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27666;
	Thu, 12 Jan 95 13:40:30 -0800
Received: by oeonline.oeonline.com (Smail3.1.28.1 #3)
	id m0rSXBD-000ARUC; Thu, 12 Jan 95 16:35 EST
Date: Thu, 12 Jan 1995 16:35:38 -500 (EST)
From: Donald Swensen <dswensen@oeonline.com>
Subject: Re: accessing MIME attachments
To: Pine Information List <pine-info@cac.washington.edu>
In-Reply-To: <Pine.ULT.3.92.950109105209.2851U-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.3.89.9501121607.A1495-0100000@oeonline.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Please send Pine FAQ.


                           ====================
    The opinions expressed in this message are not necessarily the same 
            opinions held by Suburban Communications Corporation
                           ====================

On Mon, 9 Jan 1995, David L Miller wrote:

> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Thu, 29 Dec 1994, Donald Swensen wrote:
> 
> > Date: Thu, 29 Dec 1994 19:29:56 -500 (EST)
> > From: Donald Swensen <dswensen@oeonline.com>
> > To: pine@cac.washington.edu
> > Subject: accessing MIME attachments
> > 
> > 
> > I realize you are not funded to support users, but as I access from home
> > and have no on-site sysadmin, you are my only source.
> > 
> > I recently received e-mail with attachments. I used the "v" to save the
> > attachments, and it placed them in a directory labeled:
> > 
> > /users/2/dswensen/(attachment name)
> > 
> > My problem is that I can find no directions on how to access this directory.
> > 
> > Can you help? Please...I'm desperate....this material is time sensitive.
> > 
> > Thanks in advance,
> > 
> > Don Swensen
> > dswensen@oeonline.com
> > 
> > 
> >                            ====================
> >     The opinions expressed in this message are not necessarily the same 
> >             opinions held by Suburban Communications Corporation
> >                            ====================
> > 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 14:35:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04553;
	Thu, 12 Jan 95 14:35:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28862;
	Thu, 12 Jan 95 14:28:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28856;
	Thu, 12 Jan 95 14:28:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSXqX-00038JC; Thu, 12 Jan 95 14:18 PST
To: pine-info@cac.washington.edu
From: bltst2+@pitt.edu (Brian L.  Tobin)
Subject: Help with pop E-Mail...
Date: Thu, 12 Jan 1995 16:37:03 -0500
Message-Id: <9501121637.AA03026@usenet.srv.cis.pitt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII

Presently, I use TCP/Connect II to grab my mail off the pop server here at 
school.

Sometimes, I can't do this...because I am in the lab or at a friends computer.  
So, I want to be able to log onto the pop sever, like my mail client in TCP/
Connect II does, except I want to do it in my UNIX account.

>From here, I would like to either view the mail in pine, or have them 
downloaded to text files for reading...

Is there any kind of software for this available for UNIX?

Thanks.

Please reply through E-Mail, I don't really read these newsgroups very much.  
Sorry for the cross-posting.



             This post brought to you by:

                   Brian L. Tobin
                  bltst2+@pitt.edu
              http://www.pitt.edu/~bltst2
           *******************************
              Proud Owner of a Macintosh
          You can keep flames, I ignore them.



From owner-pine-info@cac.washington.edu  Thu Jan 12 14:54:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05775;
	Thu, 12 Jan 95 14:54:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03207;
	Thu, 12 Jan 95 14:47:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03201;
	Thu, 12 Jan 95 14:47:21 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSY4g-00038JC; Thu, 12 Jan 95 14:32 PST
To: pine-info@cac.washington.edu
From: pucho@netcom.com (Marcos Rubinstein)
Subject: why not bounce in Apply?
Message-Id: <puchoD2AEvE.9F1@netcom.com>
Date: Thu, 12 Jan 1995 10:09:14 GMT

Is there any reason why you didn't include bounce in Apply?...

sometimes I bounce several messages from a mail-list to a friend, and for 
her it's better to receive them as individual pieces of mail than as 
attachements...

or did I miss something?

BTW.... thanks for pine... I do help a lot of people to deal with their 
mail... and pine, by far, is the easiest to learn and use...

Pucho


From owner-pine-info@cac.washington.edu  Thu Jan 12 15:46:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08675;
	Thu, 12 Jan 95 15:46:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00855;
	Thu, 12 Jan 95 15:38:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00849;
	Thu, 12 Jan 95 15:38:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSYwY-00038JC; Thu, 12 Jan 95 15:28 PST
To: pine-info@cac.washington.edu
From: D.Buitenhek@wbmt.tudelft.nl (D.Buitenhek)
Subject: Gen. Prot. Fault with Pine
Message-Id: <D.Buitenhek.5.000B9B7B@wbmt.tudelft.nl>
Date: Thu, 12 Jan 1995 10:36:21 GMT

I have installed PINE 3.91 on a my PC. Sometimes it is possible to start PINE 
but mostly it stops after input of my passwd.
The error message is "Pine Caused a General Protection Fault in the module 
PINE.EXE at 0008:B600.
The same error exist when I start to config PINE from PIne]

Is there a solution for this problem?

D. Buitenhek

D.Buitenhek@wbmt.tudelft.nl
University of Delft
Department Mechanical Engeneering


From owner-pine-info@cac.washington.edu  Thu Jan 12 16:05:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09929;
	Thu, 12 Jan 95 16:05:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05099;
	Thu, 12 Jan 95 15:58:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05093;
	Thu, 12 Jan 95 15:58:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSZK1-00038KC; Thu, 12 Jan 95 15:52 PST
To: pine-info@cac.washington.edu
From: Amy Lauderdale <alauderd@MSMS.DoE.k12.MS.US>
Subject: Re: printer
Date: Thu, 12 Jan 1995 11:53:40 -0600
Message-Id: <Pine.SOL.3.91.950112115021.21587A-100000@Sparc.MSMS.DoE.k12.MS.US>
References: <D23CtH.E76@nbn.com> <3f2koq$rre@news.asu.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3f2koq$rre@news.asu.edu> 

> Sorry to see someone other then me is also having printing problems in 
> Pine and not getting any answers from the Group.  I know they are very 
> busy, but being a Newby also, we are anxious to get on with our work.  I 
> posted about a week ago, have read all the FAQs and just can't solve the 
> problem.  I think in my case that the System Operator may have an option 
> available that doesn't make printing possible.  Have sent a msg to the 
> Sys Op, but to no avail.  In my case, when I ask for the printer, it 
> actully captures the article and writes it to my hard disk, and of course 
> I can then print from there.  You may check your hard disk and see if 
> there is a file name "CAPFILE" or something near that.  Maybe someone out 
> there will answer us soon.
> 

You folks aren't alone.  I have trouble with printing also and can't seem
to find any help.  Using Procomm, both at home on my Tandy and at
school on my IBM with Epson 870 printer, it completely locks up
if I try to print.  I have to totally re-boot to unlock it.

Using Telix I have a little better luck.  I can print as long as the
message is not too long.  If it is more than two sheets worth of paper,
it gives me an abort message.

Amy 

alauderd@msms.doe.k12.ms.us



From owner-pine-info@cac.washington.edu  Thu Jan 12 16:42:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11895;
	Thu, 12 Jan 95 16:42:23 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02467;
	Thu, 12 Jan 95 16:34:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02459;
	Thu, 12 Jan 95 16:34:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSZnU-00038JC; Thu, 12 Jan 95 16:23 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: pine to cc:Mail
Date: Thu, 12 Jan 1995 14:22:52 -0800
Message-Id: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu>
References: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu> 


Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
good cc:Mail<->Internet gateway should be able to translate between MIME
and cc:Mail attachments, but unfortunately many do not...

You may be able to get the file through by uuencoding it and including
the uuencoded text into the body of a message using ^R. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 12 Jan 1995, Judd Deaver wrote:

> Date: Thu, 12 JAN 1995 10:57:35 -0800 
> From: Judd Deaver <jdeaver@u.washington.edu>
> Newgroups: comp.groupware.lotus-notes.misc, comp.mail.pine,
>     comp.mail.multi-media, comp.mail.misc, comp.mail.mime
> Subject: pine to cc:Mail 
> 
> I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
> network. I sent a Binary attachment but it did not seem to make it. Could 
> this be because his network does not support MIME or because the way pine 
> attaches files is different then cc:mail? If it is because they don't 
> supprt MIME would an ASCII file attachment make it down or does pine 
> automatically MIME encrypt all attachments?
> 
> Any help is GREATLY appreciated (this is an important file) could you 
> please reply via e-mail though to jdeaver@u.washington.edu
> 
> Thank You.
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 17:14:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14257;
	Thu, 12 Jan 95 17:14:12 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03536;
	Thu, 12 Jan 95 17:08:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03530;
	Thu, 12 Jan 95 17:08:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSaNO-00038KC; Thu, 12 Jan 95 17:00 PST
To: pine-info@cac.washington.edu
From: Garbi Schmidt <garbi@coco.ihi.ku.dk>
Subject: Delete lines/blocs from pine
Date: Thu, 12 Jan 1995 18:20:48 +0100 (MET)
Message-Id: <Pine.ULT.3.90.950112181728.24680A-100000@coco.ihi.ku.dk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Dear reader!

If and when I need to edit an incoming file/letter/text in order to save 
it in a - for me - more convenient way - I'm in trouble! How do I delete 
lines or blocs which to me are uninteresting? 
Thanks for your help!

Garbi Schmidt
--------------------------------------------------------------------------
Garbi Schmidt		| When the only tool you have is a hammer, every-
Copenhagen - DENMARK	| thing begins to look like a nail (Lofti Zadeh)
--------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Thu Jan 12 17:25:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14679;
	Thu, 12 Jan 95 17:25:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07337;
	Thu, 12 Jan 95 17:19:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [202.11.252.241] by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07331;
	Thu, 12 Jan 95 17:19:02 -0800
Received: (from andres@localhost) by gol1.gol.com (8.6.9/8.6.9) id JAA03080; Fri, 13 Jan 1995 09:52:41 +0900
From: Mark Andres <andres@gol.com>
Message-Id: <199501130052.JAA03080@gol1.gol.com>
To: pine-info@cac.washington.edu
Subject: Pine Installation
Date: Fri, 13 Jan 1995 09:45:47 +0900
Organization: Temple University Japan Library
X-Mailer: MacSOUP 1.0d4

Is there any documents that explain *step-by-step* how to install Pine?
I have read the FAQ and all the other documents in the Pine FTP archive.

I am at the beginner level with UNIX and, for better or worse, I have
been made the mail administrator of our Sun SPARC station.  I managed to
configure sendmail to work and now our users want something more user
friendly in a  mail system.  Any pointers on where to find an
installation document is greatly appreciated.

Mark Andres, M.L.S.       andres@gol.com  (NEW!)
Systems Librarian &       2-2 Minami-Osawa
Macintosh Consultant      Hachioji-shi, Tokyo 192-03 Japan
Temple University Japan   Fax: +81 (426) 77-5135


From owner-pine-info@cac.washington.edu  Thu Jan 12 17:27:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14779;
	Thu, 12 Jan 95 17:27:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07094;
	Thu, 12 Jan 95 17:08:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07088;
	Thu, 12 Jan 95 17:08:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSaMR-00038JC; Thu, 12 Jan 95 16:59 PST
To: pine-info@cac.washington.edu
From: Nancy McGough <nancym@ii.com>
Subject: Signature and Finger FAQ
Date: 12 Jan 1995 18:27:49 GMT
Message-Id: <signature_finger_faq_789934983@rtfm.mit.edu>

Archive-name: signature_finger_faq
Posting-frequency: approximately monthly
Last-modified: 31 October 1994


            _____________________________________________________
  _________|                                                     |_________
  \        |   SIGNATURE AND FINGER FREQUENTLY ASKED QUESTIONS   |        /
   \       |            Telling the World Who You Are            |       /
    \      |                                                     |      /
     \     |                                                     |     /
     /     |           Copyright (c) 1994 Nancy McGough          |     \
    /      |                                                     |      \
   /       |_____________________________________________________|       \
  /____________)                                              (___________\



  TABLE OF CONTENTS

  0.0 About this Article
  ... 0.1 Copyright Notice
  ... 0.2 Acknowledgements
  ... 0.3 Terminology and Notation
  ... 0.4 Getting the Latest Version of This Article
  ... 0.5 Reading the Hypertext Version of This Article
  ... 0.6 Reading the Plain Text Version of This Article
  1.0 Automatic Signature - Basic Unix Instructions
  ... 1.1 Pine 3.90 and Above
  ... 1.2 Pine 3.89 and Below
  ... 1.3 Elm
  ... 1.4 Mail
  ... 1.5 Emacs Mail Mode
  ... 1.6 MH and Emacs MH-E
  ... 1.7 NN
  ... 1.8 GNUS
  ... 1.9 Troubleshooting Signature Problems
  2.0 Finger - Basic Unix Instructions
  ... 2.1 URLs for Fingering
  ... 2.2 Changing Your Default Finger Info: chfn
  ... 2.3 Adding More to Your Finger Info: .plan & .project
  ... 2.4 Finding Out Who Fingers You
  ... 2.5 Backfinger Script
  ... 2.6 Interesting Places to Finger
  3.0 Putting Ascii Art in your Signature and Finger Files
  4.0 Organization Header
  ... 4.1 Tin and the RN Family
  ... 4.2 Pine 3.90 and Above
  ... 4.3 Elm
  ... 4.4 NN
  5.0 Contributing to this FAQ


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

Date: 31 Oct 1994 00:00:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 0.0 About this Article

This article describes these three ways to tell people on the Internet
more about yourself:
 * Signature file automatically included in your mail and news messages
 * Finger information displayed when people finger you
 * Organization line in your mail and news headers

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

Date: 31 Oct 1994 00:00:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.1 Copyright Notice

Copyright (c) 1994 by Nancy McGough.  This collection of articles is first
published in 1994 and is copyrighted by Nancy McGough (except subjects 1.4,
1.5, 1.6, 1.8, and 2.5 which are Copyright (c) 1994 by the authors named in
the sections).  No portion of this work may be sold or put to commercial use
without express written consent of the authors.  This restriction covers
publication in any form, or distribution by any method, which permits this
work to be visually perceived, either directly or with the aid of any machine
or device. Permission is granted to republish or redistribute this article in
its entirety for noncommercial use if this copyright notice is not removed or
altered.

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

Date: 31 Oct 1994 00:00:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.2 Acknowledgements

+ means someone who is new since the last time I posted this FAQ
  (i.e., since 16 September 1994).

Thanks to these people who contributed digest items:
   Jym Dyer <jym@remarque.berkeley.edu>
   Mike Northam <mbn@greyskul.intel.com>
 + Janet Rosenbaum <ejrosen@merle.acns.nwu.edu>

Thanks to these people who sent suggestions:
 + Jeff Blaine <jblaine@ciesin.org>
   Stephen Cristol <mphbj639@unix.cc.emory.edu>
 + Terry Gray <gray@cac.washington.edu>
 + Sven Guckes <guckes@inf.fu-berlin.de>
 + Mary McGough <mary@hitl.washington.edu>
   David L Miller <dlm@cac.washington.edu>
 + Skip Montanaro <skip@automatrix.com>
   David W. Tamkin <dattier@mcs.com>
   Sid Weinstein <syd@dsinc.myxa.com>

Thanks to these people who've written documents, programs, or asii art that 
are pointed to in this article.  (This list is not complete right now....)
 + Bob Allison <boba@wwwa.com>
 + Jorn Barger <jorn@genesis.mcs.com>
 + Piero Serini <piero@strider.inet.it>
 + Doug Stevenson <doug+@osu.edu>
 + Bill Wohler <wohler@newt.com>
 + Scott A. Yanoff <yanoff@alpha2.csd.uwm.edu>


Special thanks to:
 + Thomas A. Fine <fine@cis.ohio-state.edu> for setting up and
   maintaining the hypertext archive of FAQs.  Congratulations
   to him for winning O'Reilly and Associates' "The Best of the
   Net" award!

Please let me know if I've left you, or anyone else, out of this list.

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

Date: 31 Oct 1994 00:00:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.3 Terminology and Notation

  Term  Meaning
  ====  =======
  FTP   File Transfer Protocol
  HTML  HyperText Markup Language
  HTTP  HyperText Transport Protocol
  RFC   Internet Request For Comments Document
  URL   Uniform Resource Locator
  ^x    Hold down the Ctrl key and the x key at the same time
  ~     your home directory $HOME  (see * below)


* In this article I use ~ (tilde) to mean your home directory.  Note that 
  some shells, like the Bourne shell (sh) and Bourne-again shell (bash), do 
  not understand the tilde notation so you will need to use $HOME instead.  
  You can always get to your home directory by typing ``cd''.

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

Date: 31 Oct 1994 00:00:40 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.4 Getting the Latest Version of This Article

If this article is over two months old then there is probably an updated
version of it in all the usual archives.  Please get the latest version
from one of these places:

World Wide Web (the nicest format for online reading!):
http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

Anonymous FTP:
ftp://rtfm.mit.edu/pub/usenet/news.answers/signature_finger_faq

Email:
Send mail to mail-server@rtfm.mit.edu containing the following:
    send usenet/news.answers/signature_finger_faq

UUCP:
uunet!/archive/usenet/news.answers/signature_finger_faq

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

Date: 31 Oct 1994 00:00:50 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.5 Reading the Hypertext Version of This Article

The best way to read this FAQ (and most other FAQs too) is to view the
hypertext version using a Web browser such as Lynx, Mosaic, Netscape, 
WinWeb, or Cello.  This will allow you to easily jump:
   * between subjects in this article
   * to a Uniform Resource Locator (URL)
   * to an Internet Request For Comments document (RFC)
   * to a manual page

This and all FAQs that are crossposted to news.answers can be accessed through:
http://www.cis.ohio-state.edu/hypertext/faq/usenet/top.html

This particular FAQ is at:
http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

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

Date: 31 Oct 1994 00:00:60 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.6 Reading the Plain Text Version of This Article

If you are reading the plain text version (i.e., not the hypertext version) of 
this FAQ it is in RFC1153 digest format which means each subject is formatted 
as a mini mail message with its own Date, From, and Subject (and sometimes 
Followup-To) headers.  Some newsreaders and mailers make it really easy
to jump to a subject in an article that is in digest format.  Here are 
instruction for some newsreaders:

* NN's default is to split a digest and present each digest item on the
  menu.  If you have changed the default by putting ``set split off'' in
  your ~/.nn/init file then you can split a digested article by typing G%
  while viewing it.  This will present each digest item on a submenu.  You
  can then read, followup-to, save, print, etc. individual digest items.

* In trn (and its relatives like rn and strn) you can type ^g (Ctrl key and
  g key pressed simultaneously) to skip to the next line that begins with
  "Subject: "

* In emacs GNUS, C-c C-n will skip to the next digest article (C-C C-p will
  go back to the previous digest article).


If your newsreader or mailer does not have a built-in command that allows
you to easily read a digest you can pipe the article to ``formail -ds''
which will split the article into separate mail messages, and then you can
use your mailer or newsreader (if it can read mail folders) to read the
folder.  For example, here's what you would do in Tin while viewing
the article:

Type...                             In order to...
-------                             --------------
|                                   Pipe
a                                   Specify the article is to be piped
formail -ds >> ~/Folders/faq.split  Split the digest into individual
                                    messages and put them in a file named
                                    ~/Folders/faq.split.  (Replace ~/Folders
                                    with your folder directory.)
pine -if ~/Folders/faq.split        Use Pine to read the newly created folder.

For more information see the formail(1) and procmail(1) man pages.

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

Date: 31 Oct 1994 00:01:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 1.0 Automatic Signature - Basic Unix Instructions

Q: How can I have a signature automatically appended to my news articles
   and mail messages?

A: The answer depends on your newsreader and mailer but the following
   procedure works for many Unix newsreaders and mailers.


Type...                 In order to...
-------                 --------------
cd                      Change to your home directory (i.e., $HOME or ~)

pico .signature         Use the pico editor to create a .signature file.
                        (Replace "pico" with another editor if you like.)

<your signature>        Note that most systems require your sig to be <= 4
                        lines.  And it's good netiquette to make it as
                        short as possible.

<save and exit>         In Pico use ^x to exit and answer y when asked
                        if you want to save your changes.

chmod 644 .signature    Make .signature readable by all.

ls -l .signature        Check the permission: it should say -rw-r--r--

chmod +x .              Make home directory searchable by all.

ls -ld .                Check permission of home dir: it should say drwx?-x?-x
                        The ?'s may be r's or hyphens or one of each (i.e.,
                        drwx--x--x, drwxr-xr-x, drwxr-x--x, drwx--xr-x).

ls -la .                Check permission of files in home dir.  If any are
                        world or group writable (?????w??w?) you'll probably
                        want to change this by doing a "chmod go-w FileName".
                        For more info on changing permissions see chmod
                        man pages.

For many newsreaders and mailers this is all you need to do to set up your
signature.  For example the default behaviour of tin(1) and the rn family of 
tools - rn(1), trn(1), strn(1), & Pnews(1) - is to automatically append 
 ~/.signature, if it exists.  If you use Pine, Elm, Mail, Emacs Mail Mode, MH, 
NN, or GNUS follow the additional instructions described below.

After you've set everything up use your mailer to mail a test message
to yourself, and your newsreader and/or news poster (such as nnpost or Pnews)
to post an article to a test newsgroup (use a local newsgroup and Distribution
set to ``local'' to save bandwidth).  Note that with many newsreaders and 
mailers you will not see your signature while you are composing a message - 
it will be automaticlally appended when you send the message.  Note also that 
many systems add a line that contains ``-- '' to the top of your sig.  This is 
used by programs that automatically deal with mail or news to identify the 
start of the signature.

If you have a problem with your sig see section 1.9 on Troubleshooting.

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

Date: 31 Oct 1994 00:01:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 1.1 Pine 3.90 and Above
Followup-To: comp.mail.pine

The default for Pine 3.90 and above is to automatically append .signature (if 
it exists) to your messages.  Many people like to set the signature-at-bottom 
variable which will put your signature below both your message and the message 
you are replying to (if you've included it).  Note that if you are forwarding 
a message your signature will be put below the message that you write but 
above the forwarded message.

To change Pine's signature features:

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the signature-at-bottom feature:
   a) Space bar and arrow down to the signature-at-bottom variable
   b) Type x to set/unset this variable.
4. To change the name of your signature file:
   a) Arrow down to the signature-file line
   b) Type c for Change Value
   c) Type the path and name of the file you want to use for your
      signature.  Note that ~ can be used for your $HOME directory.


SEE ALSO
========
Pine FAQ:       http://www.cac.washington.edu/pine/faq/
                ftp://ftp.cac.washington.edu/pine/docs/faq
Pine Manual:    pine(1)
Pine Newsgroup: comp.mail.pine

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

Date: 31 Oct 1994 00:01:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 1.2 Pine 3.89 and Below
Followup-To: comp.mail.pine

In addition to the basic signature instructions in 1.0 above, users of
Pine 3.89 often want to edit their ~/.pinerc file so that it contains
the following:

feature-list=signature-at-bottom

If you want more than one feature in your feature-list then they need to
be comma separated like this:

feature-list=old-growth,
	signature-at-bottom

Note that Pine's default is to use ~/.signature for your signature so you
only need to edit the following line if you are using a different file.

signature-file=

SEE ALSO
========
Pine FAQ:       http://www.cac.washington.edu/pine/faq/
                ftp://ftp.cac.washington.edu/pine/docs/faq
Pine Manual:    pine(1)
Pine Newsgroup: comp.mail.pine

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

Date: 31 Oct 1994 00:01:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 1.3 Elm
Followup-To: comp.mail.elm

In addition to the basic signature instructions in 1.0 above, users of Elm
should edit their ~/.elm/elmrc file so that it contains the following:

signature = ~/.signature
sigdashes = ON

Remember to delete any # characters before any variables you want
to set.  The defaults are indicated in comment lines starting with ###.

Note that if you want to have a different signature for local mail
(i.e., addresses that don't contain a ! or @) then you can use the
localsignature and remotesignature variables instead of the signature
variable (which specifies one sig for all mail).

SEE ALSO
========
Elm FAQs:   http://www.cis.ohio-state.edu/hypertext/faq/usenet/elm/top.html
Elm Manual: elm(1)
Newsgroup:  comp.mail.elm

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

Date: 31 Oct 1994 00:01:40 GMT
From: Jym Dyer <jym@remarque.berkeley.edu>
Subject: ... 1.4 Mail
Followup-To: comp.mail.misc

By Jym Dyer, 1 April 1994

=o= Regular Unix "Mail" and "mail" don't have an automatic
signature mechanism.  Many people who normally use a more deluxe
mail utility occasionally find themselves resorting to using one
of these, in which case all you need to know is this command:

	~r $HOME/.signature

This simply tells Mail to include the text of the your signature
file.

=o= If you use Mail on a regular basis you may want to use the
semi-automatic signature feature.  When you're done typing your
message, you append a signature with this command:

	~a

=o= In order for this to work, though, you need to set the
"sign" mail variable.  There are two ways to implement this
variable.  The first is to set it in a $HOME/.mailrc file with
a command like this:

	set sign="Jym Dyer <jym@remarque.berkeley.edu>"

If your signature is more than one line long, you can use the
C language string syntax, as in these examples:

	set sign="Jym Dyer\n<jym@remarque.berkeley.edu>"

			-or-

	set sign="Jym Dyer\
	\n<jym@remarque.berkeley.edu>"

=o= The disadvantage of doing this in your .mailrc file is
that you now have to maintain the text of your signature in
two places.  Another approach that avoids this problem is to set
"sign" as an environment variable in your shell startup script.
For a Bourne-compatible shell, this is done with this command:

	sign="`cat $HOME/.signature`" export sign

For a C-shell, do this:

	setenv sign "`cat $HOME/.signature`"

SEE ALSO
========
Manual pages: mail(1)
Newsgroup:    comp.mail.misc

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

Date: 31 Oct 1994 00:01:50 GMT
From: Jym Dyer <jym@remarque.berkeley.edu>
Subject: ... 1.5 Emacs Mail Mode

By Jym Dyer, 1 April 1994

=o= Emacs Mail Mode is usually invoked with the "mail" or
"mail-other-window" commands (bound, respectively, to the
"C-x m" and "C-x 4 m" keys by default).  It is also invoked
from various Emacs mail and news packages.

=o= Mail Mode provides a "mail-signature" command to append
the contents of your signature file to the end of your mail
message.  This command is bound to "C-c C-w" by default,
so to insert the signature before mailing, simply type
"C-c "C-w".

=o= If you'd prefer to have your signature automatically
appended to the end of your mail message, the "mail-signature"
command can be put into your "mail-setup-hook" variable in
your $HOME/.emacs file, as in this example:

    (setq mail-setup-hook
      (function
       (lambda ()
	 (mail-signature) )))

This will put the signature in your mail message buffer.

SEE ALSO
========
FAQ: 
http://www.cis.ohio-state.edu/hypertext/faq/usenet/GNU-Emacs-FAQ/part5/faq.html    
Newsgroups: gnus.emacs.help and comp.emacs

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

Date: 31 Oct 1994 00:01:60 GMT
From: Jym Dyer <jym@remarque.berkeley.edu>
Subject: ... 1.6 MH and Emacs MH-E
Followup-To: comp.mail.mh

By Jym Dyer, 1 April 1994

=o= MH doesn't have an automatic signature mechanism, but it
is so configurable that there are a number of different ways
to implement one.  Check the periodic "MH Frequently Asked
Questions (FAQ) with Answers" posting for details.

=o= CAVEAT:  If you use the environment variable SIGNATURE to
point to your signature file, MH will use it not as a signature,
but as your "fullname".  Even worse, if your version of MH was
built with the "UCI" option and you *don't* use the environment
variable SIGNATURE to point to another file, MH will use the
$HOME/.signature file for this purpose!  To see if your version
of MH has this behavior, enter this command:

  % send -help

And look for the string "[UCI]" in the output.

=o= There's an Emacs interface to MH, called MH-E.  It has its
own signature mechanism, which is invoked with the "mh-insert-
signature" command (bound to the "C-c C-s" keys by default).

=o= This will insert the file $HOME/.signature file by default.
If your signature file has another name (e.g., to avoid its
being used by an MH build with the "UCI" option), you can set
the "mh-signature-file-name" variable to refer to a different
file.

SEE ALSO
========
MH FAQ:       http://www.cis.ohio-state.edu/hypertext/faq/usenet/mh-faq/top.html
MH Manual:    mh(1)
MH Newsgroup: comp.mail.mh

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

Date: 31 Oct 1994 00:01:70 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 1.7 NN
Followup-To: news.software.nn

In addition to the basic signature instructions in 1.0 above, users of NN
should edit their ~/.nn/init file so that it contains the following:

set query-signature off
set append-signature-mail on
set append-signature-post offf

Note that the reason that you need to ``set append-signature-post off'' is
that the news posting software (usually inews) automatically appends
 ~/.signature if it exists.  If you ``set append-signature-post on'' then
both nn and inews append your sig and you'll send out two identical sigs
every time.

SEE ALSO
========
FAQ:       http://www.cis.ohio-state.edu/hypertext/faq/usenet/nn-faq/top.html
Manual:    nn(1)
Newsgroup: news.software.nn

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

Date: 31 Oct 1994 00:01:80 GMT
From: Mike Northam <mbn@greyskul.intel.com>
Subject: ... 1.8 GNUS
Followup-To: gnu.emacs.gnus

Copyright (c) 1994 Mike Northam

In addition to the basic signature instructions in 1.0 above, users of GNUS
should verify that the value of the variable gnus-signature-file points to the
right place.  If you're in emacs, you can do so by evaluating the following
expression:
gnus-signature-file
                   ^ put your cursor here and type C-x C-e

you should see "~/.signature" in the echo area.  If not, edit your
$HOME/.emacs file and add the following:
(setq gnus-signature-file "~/.signature"))
Then load your $HOME/.emacs file or merely restart emacs and the variable
should be set correctly.

SEE ALSO
========
FAQ: 
http://www.cis.ohio-state.edu/hypertext/faq/usenet/GNU-Emacs-FAQ/part5/faq.html    
Newsgroup: gnu.emacs.gnus

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

Date: 31 Oct 1994 00:01:90 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 1.9 Troubleshooting Signature Problems

A common problem people have with .signature (and .plan, .project, and
 .forward ) files is that the permissions are not set correctly.  Check
to make sure that you have set the permissions as instructed in 1.0 above.

If you are still having problems read the man pages for your newsreader,
news poster, or mailer and search for the string "signature".  There may be a
variable you need to set in order for the ~/.signature to be appended.

Type...                 In order to...
-------                 --------------
man CommandName |less   Open man pages for CommandName (elm, pine, nn, tin
                        trn, Pnews, etc.) and pipe through less.  If your
                        system doesn't have less replace it with "more".

/signature              Search for first occurrence of "signature".

n                       Search for next occurrence of "signature".
                        Repeat the search until you find the appropriate
                        section of the manual.

u                       Page up half a screen. (This works in less but not in
                        more.)

[spacebar]              Page down a screen. (This works in both less and more.)


For more information on reading manual pages see the man(1), less(1), and/or
more(1) man pages.

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

Date: 31 Oct 1994 00:02:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 2.0 Finger - Basic Unix Instructions

People around the world can find out more about you by fingering you.  
This is done by typing the following at a Unix prompt:

   finger YourUserID@Your.Fully.Qualified.Domain.Name

On some systems finger is linked to f so the following also works:

   f YourUserID@Your.Fully.Qualified.Domain.Name


Finger displays different information on different systems.  Often it will 
display your full name, your default shell, when your were last logged on, 
and your ~/.plan and ~/.project files.

If you finger someone and the display takes more than one page you can pipe 
the output through less (or more if you don't have less).  For example to 
find out about Halcyon, my Internet service provider, type:

  finger info@halcyon.com |less

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

Date: 31 Oct 1994 00:02:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.1 URLs for Fingering

In addition to using the finger or f command you can finger people
through a Web browser.  The following is a form that Doug Stevenson
<doug+@osu.edu> created:
  http://www.mps.ohio-state.edu/cgi-bin/finger.pl

You can also use this URL:
  gopher://fully.qualified.domain.name:79/0userid
                                          ^ Note: 0 precedes the userid

For example you can finger my Internet service provider with this URL:
  gopher://halcyon.com:79/0info


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

Date: 31 Oct 1994 00:02:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.2 Changing Your Default Finger Info: chfn

On many Unix systems you can change some of your default information,
such as your full name, by typing the following at your Unix prompt:

   chfn

If chfn is not available try "passwd -f".  If neither of these are
available then you will need to contact your system administrator and
ask him/her to change your full name, etc.

After you have changed your information check that they are in place
by fingering yourself.  Also to see a different display of your
information type the following at your Unix prompt:

  finger

This displays a one line description of everyone currently logged on
your system.

For more information see the chfn(1), passwd(1), and finger(1) man pages.

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

Date: 31 Oct 1994 00:02:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.3 Adding More to Your Finger Info: .plan & .project

Your ~/.project and ~/.plan files, if they exist, are displayed when you
are fingered.  Setting these up is essentially the same as setting
up a ~/.signature file (described in 1.0 above).

Type...                 In order to...
-------                 --------------
cd                      Change to your home directory.

pico .plan              Use the pico editor to create a .plan file.
                        (Replace "pico" with another editor if you like.)

chmod 644 .plan         Make .plan readable by all.

ls -l .plan             Check the permission: it should say -rw-r--r--

chmod +x .              Make home directory searchable by all.

ls -ld .                Check permission of home dir: it should say drwx?-x?-x.
                        The ?'s may be r's or hyphens or one of each.

ls -la .                Check permission of files in home dir.  If any are
                        world or group writable (?????w??w?) you'll probably
                        want to change this by doing a "chmod go-w FileName".
                        For more info on changing permissions see chmod
                        man pages.


If you want a .project file follow the same procedure.  Note that only the
first line of the .project is displayed (so you might as well only make
it one line!).

To test your changes finger yourself by type each of the following at your
Unix prompt:

    finger YourUserID
    finger YourUserID@Your.Fully.Qualified.Domain.Name

To ensure that people from other systems can finger you should ask someone 
who's not on your system to finger you too.

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

Date: 31 Oct 1994 00:02:40 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.4 Finding Out Who Fingers You

This is complicated - and sometimes impossible - to setup.  For details see
the news.answers article ``Unix - Frequently Asked Questions (4/7) [Frequent
posting]'', subject ``4.9) How do I keep track of people who are fingering 
me?'' This article is archived in a number of places including these two URLs:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/unix-faq/faq/part4/faq-doc-9.html
ftp://rtfm.mit.edu/pub/usenet/news.answers/unix-faq/faq/part4

One easy thing that you can do to see if anyone has fingered you is type the 
following at your Unix prompt:

  ls -lu $HOME/.plan

This tells you the last time someone accessed your .plan, but it doesn't
tell you who it was.  I have this in my .login because it's interesting to
see when the last time someone was checking on me!

[Note that under AFS (Andrew File System, a distributed filesystem),
 ls -lu $HOME/.plan will not work due to the fact that AFS has no 
 notion of ``atime'', or ``last accessed time''.]

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

Date: 31 Oct 1994 00:02:50 GMT
From: Janet Rosenbaum <ejrosen@merle.acns.nwu.edu>
Subject: ... 2.5 Backfinger Script

Copyright (c) 1994 Janet Rosenbaum

There is a script available called, among other things, backfinger,
planner, and finger_logger (flogger or frogger, for short).  This script
makes your plan into a named pipe (just think of this as a sort of
pipe used with plumbing that opens out onto the screen of the person who
is fingering you (fred)) so that when it is accessed, it looks for a
program from which to get something to stick on fred's screen.

The script is called when you are fingered.  At that moment, it looks to
the finger port of your unix machine and sees which machine fred is
on, logs that machine's IP number and hostname, and the date.  The script
can then execute a command to spit a plan out on fred's screen.  (One
might get creative and write a program that generates random poetry or
use the fortune program or just do "cat plan_file".)   To make fred
think you are really cool, it also tells him what machine he is
fingering you from.

Some caveats:

	-- This program must be running at all times on your system even
	when you are logged out.  Leaving a background process like this
	annoys most sys admins to no end, especially on systems with
	high load.  Do **not** run the program unless you are sure that
	you are allowed to run background processes like this.

	-- Also, if you decide you want to stop running this program,
	remove your .plan file as soon as you kill the process.  If you
	do not do this, all finger processes for you will hang.

	-- This script only tells you the machine fred is fingering you
	from, not his actual username.  It is nearly impossible to get
	this information except at sites with bad security.


Given the above, I will distribute the script to those who can use it,
mostly for educational reasons.  I admit that I no longer run the
program, since my two main accounts are on rather high-load systems.
Nevertheless, I learned quite a lot from modifying these scripts and
otherwise playing with these ideas.

Here is the web site:

 http://pubweb.acns.nwu.edu/~jrosen/scripts/logger.src

I will also try to post this answer and the program to comp.sources.misc
at least monthly for those without web access.  (For those who have not
figured out the web, try the program lynx if you are on a vt100 or vt220
type terminal.  If you are on an xterm or hpterm, look for xmosaic.)

Note:  I am not the author of this program.  The version I distribute is
virtually identical to that distributed by Steve Franklin.
Here are the real authors:

Author: Tony Rems <rembo@unisoft.com>
Modifications by Geoff Loker <geoff@mdms.moore.com>
More modifications by Karen Bruner <napalm@ugcs.caltech.edu>
Even more modifications by Norman Franke <franke1@llnl.gov>
More revisions by Steve Franklin <franklin@ug.cs.dal.ca>
Llamas and minor revision by The Blue One

Enjoy!

Janet

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

Date: 31 Oct 1994 00:02:60 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.6 Interesting Places to Finger

Scott Yanoff's "Updated Internet Services List" contains a number of 
interesting places to finger.  If you access it through the following URL 
all the finger commands are links.

  http://www.uwm.edu/Mirror/inet.services.html

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

Date: 31 Oct 1994 00:03:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 3.0 Putting Ascii Art in your Signature and Finger Files

            ,     \    /      ,
           / \    )\__/(     / \
          /   \  (_\  /_)   /   \
     ____/_____\__\@  @/___/_____\____
    |             |\../|              |
    |              \VV/               |
    |        HAPPY HALLOWEEN!         |
    |_________________________________|
     |    /\ /      \\       \ /\    |             
     |  /   V        ))       V   \  |
     |/     `       //        '     \|         Art by Jorn Barger
     `              V                '                <jorn@genesis.mcs.com>

It is considered good netiquette to keep your signature to four lines or
less.  And many news posters, like inews, will not post an article
that has a signature with more than four lines in it.  So, put large
pictures, your life story, etc. in your finger files or in your Web pages
and point people to them in your signature.

A good source of art for your signature and finger files is the ascii art
FAQ which contains (among others) these topics:
   9  Where can I find ASCII art?
  22  How do I put an animation in my plan?
  23  How do I make a sig?
  24  How do I have my sig automatically added to my posts and email?

The Ascii Art FAQ can be found at either of the following.  (I think
these aren't the same so you might want to look at both of them.)
http://gagme.wwa.com/~boba/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/ascii-art-faq/faq.html

One particularly good place to find ascii art is:
http://gagme.wwa.com/~boba/scarecrow.html

SEE ALSO
========
Newsgroups: rec.arts.ascii, alt.ascii-art, alt.binaries.pictures.ascii
            and alt.ascii-art.animation

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

Date: 31 Oct 1994 00:04:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 4.0 Organization Header

The Organization header in news and mail messages is another way you can tell 
people about yourself.  It is an optional header described in section
2.2.8 of RFC1036, "Standard for Interchange of Usenet Messages."

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

Date: 31 Oct 1994 00:04:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 4.1 Tin and the RN Family
Followup-To: news.newusers.questions

Tin and the rn family of tools (Pnews, rn, trn, strn) get information for the 
Organization header from the ORGANIZATION environment variable if it exists.  
In the csh or tcsh you can set this variable in your ~/.login with a line like 
this:

  setenv ORGANIZATION "Your Organization Name"

After you edit your ~/.login you can establish the setting by either logging
out and loggin back in or by typing the following at your Unix prompt:

  source ~/.login

To check that the variable is set type:

  printenv

After it is set, post a test message to a local test newsgroup with local
distribution to check that the Organization header is correct.

SEE ALSO
========
Manual Pages: tin(1), Pnews(1), rn(1), trn(1), strn(1)
Newsgroup:    news.newusers.questions

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

Date: 31 Oct 1994 00:04:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 4.2 Pine 3.90 and Above
Followup-To: comp.mail.pine

In Pine 3.90 or above you set the Organization and other headers using the
customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) Space bar and arrow down to the customized-hdrs variable.
   b) Type a for Add Value
   c) At the prompt type: Organization: Your Organization Name
      Note that if you have set the ORGANIZATION environment variable
      (which is described in 4.1 above) you can type: 
      Organization: $ORGANIZATION

While reading a message that you've received you can view the Organization
header and all the other headers by typing h.  If h does not work you need 
to go to your configuration menu and set the enable-full-header-cmd variable.

Note that the customized-hdrs variable is not available in Pine 3.89 and
below.

SEE ALSO
========
Pine FAQ:       http://www.cac.washington.edu/pine/faq/
                ftp://ftp.cac.washington.edu/pine/docs/faq
Pine Manual:    pine(1)
Pine Newsgroup: comp.mail.pine

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

Date: 31 Oct 1994 00:04:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 4.3 Elm
Followup-To: comp.mail.elm

Use your editor to create a file named ~/.elm/elmheaders that contains
any headers you'd like in your outgoing mail messages.  For example, my
 ~/.elm/elmheaders file contains this one line:

Organization: Infinite Ink, Seattle, WA, USA

SEE ALSO
========
Elm FAQs:   http://www.cis.ohio-state.edu/hypertext/faq/usenet/elm/top.html
Elm Manual: elm(1)
Newsgroup:  comp.mail.elm

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

Date: 31 Oct 1994 00:04:40 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 4.4 NN
Followup-To: news.software.nn

Use your editor to put the following lines in your ~/.nn/init file:

set news-header Organization: Your Organization Name
set mail-header Organization: Your Organization Name

This will add the Organization header to both news and mail messages
sent from NN.

While reading messages with NN you can view the Organization line
by adding O (the letter "oh") to your header-lines variable setting.
I like the following setting:

set header-lines AFOnWK*Y

SEE ALSO
========
FAQ:       http://www.cis.ohio-state.edu/hypertext/faq/usenet/nn-faq/top.html
Manual:    nn(1)
Newsgroup: news.software.nn

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

Date: 31 Oct 1994 00:05:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 5.0 Contributing to this FAQ

If you have any corrections, suggestions, or new digest items to contribute
to this FAQ please send them to me at nancym@ii.com.  If you are reading this
with a viewer that understands the following URL you can use it to send me 
mail:

  mailto:nancym@ii.com

End of signature_finger_faq Digest
**********************************

--
 /\_/\
( o.o )   Nancy McGough   |   http://www.jazzie.com/ii/
 > ^ <    Infinite Ink    |   ftp://ftp.ii.com/pub/ii


From owner-pine-info@cac.washington.edu  Thu Jan 12 17:33:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15026;
	Thu, 12 Jan 95 17:33:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07495;
	Thu, 12 Jan 95 17:28:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07489;
	Thu, 12 Jan 95 17:28:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSafw-00038JC; Thu, 12 Jan 95 17:19 PST
To: pine-info@cac.washington.edu
From: jsumler@bach.ucs.indiana.edu (jeffery sumler)
Subject: Re: Address book tools
Date: 12 Jan 1995 04:51:42 GMT
Message-Id: <3f2cgu$5e8@usenet.ucs.indiana.edu>
References: <Pine.BSI.3.91.950104113141.27761B-100000@recepsen.aa.msen.com> <Pine.ULT.3.92.950104104723.8935R-100000@shiva1.cac.washington.edu>

In article <Pine.ULT.3.92.950104104723.8935R-100000@shiva1.cac.washington.edu>,
David L Miller  <dlm@cac.washington.edu> wrote:
>On Wed, 4 Jan 1995, Edward Vielmetti wrote:

>> - an interface to finger, whois, or some other directory service
>>   so that you can look people up
>
>This is planned....

Can you estimate when this will become available? We've added
finger/whois support to pine and I'd love to drop our changes.

jeff sumler
jsumler@indiana.edu















From owner-pine-info@cac.washington.edu  Thu Jan 12 18:15:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16473;
	Thu, 12 Jan 95 18:15:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04524;
	Thu, 12 Jan 95 18:08:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04518;
	Thu, 12 Jan 95 18:08:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSbLd-00038KC; Thu, 12 Jan 95 18:02 PST
To: pine-info@cac.washington.edu
From: fyao@calum.csclub.uwaterloo.ca (Frank Yao)
Subject: ??? about index screen
Message-Id: <D2A4vv.HwF@undergrad.math.uwaterloo.ca>
Date: Thu, 12 Jan 1995 06:33:30 GMT

I guess I'm just feeling impatient because I've asked this question
before, but I'm afraid it might have been too buried in another
message that it was missed, or that the Subject: was changed and I
missed it.

So, I will ask the question again.  What exactly are the numbers in
brackets next to the sender supposed to represent?  I am guess at
number of characters or something like that.  That is basically
useless to me, compared to knowing how many lines long the e-mail is.
Is there a way to get this?  I went through the .pinerc, and didn't
see anything that was related to it.  Did I plain miss it?

Thanks

- frank (trying to get back to pine after months of elm)
-- 
---
"You _are_ my darling.  My dear, darling Frank, who cares too much,   
 worries too much, and loves those whom he loves fiercely...."         
 - Victoria Smith about me (fyao@calum.csclub.uwaterloo.ca)                


From owner-pine-info@cac.washington.edu  Thu Jan 12 18:42:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17153;
	Thu, 12 Jan 95 18:42:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08697;
	Thu, 12 Jan 95 18:37:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08691;
	Thu, 12 Jan 95 18:37:15 -0800
Received: by hobbes.twntpe.cdc.com; Fri, 13 Jan 95 10:35:41 -0800
Date: Fri, 13 Jan 1995 10:35:40 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Frank Yao <fyao@calum.csclub.uwaterloo.ca>
Cc: pine-info@cac.washington.edu
Subject: Re: ??? about index screen
In-Reply-To: <D2A4vv.HwF@undergrad.math.uwaterloo.ca>
Message-Id: <Pine.SOL.3.91.950113103156.790E-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 12 Jan 1995, Frank Yao wrote:

> I guess I'm just feeling impatient because I've asked this question
> before, but I'm afraid it might have been too buried in another
> message that it was missed, or that the Subject: was changed and I
> missed it.
> 
> So, I will ask the question again.  What exactly are the numbers in
> brackets next to the sender supposed to represent?  I am guess at
> number of characters or something like that.  That is basically
> useless to me, compared to knowing how many lines long the e-mail is.
> Is there a way to get this?  I went through the .pinerc, and didn't
> see anything that was related to it.  Did I plain miss it?

	Yes, you missed something.  It is call the "help" screen.

	Do the following:

1.	Start pine.

2.	Type i (for index).

3.	Type ? (for help).

4.	Read until you find....

	Description of the FOLDER INDEX Screen

5.	Continue reading until you find.

	SIZE:

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C




From owner-pine-info@cac.washington.edu  Thu Jan 12 18:58:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17497;
	Thu, 12 Jan 95 18:58:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08922;
	Thu, 12 Jan 95 18:53:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08916;
	Thu, 12 Jan 95 18:53:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSbzh-00038KC; Thu, 12 Jan 95 18:44 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: ??? about index screen
Date: Thu, 12 Jan 1995 15:17:32 -0800
Message-Id: <Pine.ULT.3.92.950112151640.2637U-100000@shiva1.cac.washington.edu>
References: <D2A4vv.HwF@undergrad.math.uwaterloo.ca>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D2A4vv.HwF@undergrad.math.uwaterloo.ca> 


You are correct that the count is number of characters/bytes in the
message.  There is not currently an option to display the number of
lines... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 12 Jan 1995, Frank Yao wrote:

> Date: Thu, 12 JAN 1995 06:33:30 GMT 
> From: Frank Yao <fyao@calum.csclub.uwaterloo.ca>
> Newgroups: comp.mail.pine
> Subject: ??? about index screen 
> 
> I guess I'm just feeling impatient because I've asked this question
> before, but I'm afraid it might have been too buried in another
> message that it was missed, or that the Subject: was changed and I
> missed it.
> 
> So, I will ask the question again.  What exactly are the numbers in
> brackets next to the sender supposed to represent?  I am guess at
> number of characters or something like that.  That is basically
> useless to me, compared to knowing how many lines long the e-mail is.
> Is there a way to get this?  I went through the .pinerc, and didn't
> see anything that was related to it.  Did I plain miss it?
> 
> Thanks
> 
> - frank (trying to get back to pine after months of elm)
> -- 
> ---
> "You _are_ my darling.  My dear, darling Frank, who cares too much,   
>  worries too much, and loves those whom he loves fiercely...."         
>  - Victoria Smith about me (fyao@calum.csclub.uwaterloo.ca)                
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 18:58:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17518;
	Thu, 12 Jan 95 18:58:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05232;
	Thu, 12 Jan 95 18:53:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05226;
	Thu, 12 Jan 95 18:53:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSbzm-00038LC; Thu, 12 Jan 95 18:44 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: customizing which headers displayed
Date: Thu, 12 Jan 1995 15:18:41 -0800
Message-Id: <Pine.ULT.3.92.950112151826.2637V-100000@shiva1.cac.washington.edu>
References: <3f3lvl$685@hobbes.cc.uga.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3f3lvl$685@hobbes.cc.uga.edu> 


Not currently.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 12 Jan 1995, Glenn Leavell wrote:

> Date: 12 JAN 1995 16:39:17 GMT 
> From: Glenn Leavell <glenn@creator.ucns.uga.edu>
> Newgroups: comp.mail.pine
> Subject: customizing which headers displayed 
> 
> When Pine is displaying the text of incoming mail in its default state 
> of "full headers OFF", it shows the standard headers like "From:", "To:",
> "Date:", "Subject:", etc.  Is there a way to customize this so that other
> specific headers can be displayed without turning on full headers?
> 
> Thanks for any help.
> 
> -- 
> Glenn Leavell  University of Georgia  glenn@creator.ucns.uga.edu  706-542-3135
>     University Computing and Networking Services, Athens, GA USA 30602-1911
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 19:08:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17923;
	Thu, 12 Jan 95 19:08:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09021;
	Thu, 12 Jan 95 19:00:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09015;
	Thu, 12 Jan 95 19:00:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSc85-00038JC; Thu, 12 Jan 95 18:52 PST
To: pine-info@cac.washington.edu
From: Judd Deaver <jdeaver@u.washington.edu>
Subject: pine to cc:Mail
Date: Thu, 12 Jan 1995 10:57:35 -0800
Message-Id: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
network. I sent a Binary attachment but it did not seem to make it. Could 
this be because his network does not support MIME or because the way pine 
attaches files is different then cc:mail? If it is because they don't 
supprt MIME would an ASCII file attachment make it down or does pine 
automatically MIME encrypt all attachments?

Any help is GREATLY appreciated (this is an important file) could you 
please reply via e-mail though to jdeaver@u.washington.edu

Thank You.


From owner-pine-info@cac.washington.edu  Thu Jan 12 19:14:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18112;
	Thu, 12 Jan 95 19:14:58 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09201;
	Thu, 12 Jan 95 19:08:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.ge.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09195;
	Thu, 12 Jan 95 19:07:59 -0800
Received: from [3.12.38.33] by ns.GE.com (5.65/GE Gateway 1.32) with SMTP
	 id AA28154; Thu, 12 Jan 1995 22:07:57 -0500
Received: by mmpcs1.PSF.GE.COM (4.1/GEA Sun server 2.7)
	id AA15602; Thu, 12 Jan 95 22:06:25 EST
Date: Thu, 12 Jan 1995 22:06:24 -0500 (EST)
From: Don Sugarman <sugarman@mmpcs1.psf.ge.com>
To: David L Miller <dlm@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: pine to cc:Mail
In-Reply-To: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.90.950112215735.15596C-100000@mmpcs1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Thu, 12 Jan 1995, David L Miller wrote:

> 
> Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
> good cc:Mail<->Internet gateway should be able to translate between MIME
> and cc:Mail attachments, but unfortunately many do not...
> 
> You may be able to get the file through by uuencoding it and including
> the uuencoded text into the body of a message using ^R. 

In case you haven't used uuencode, this is how I do it:

  uuencode <source file> <source file> > <temp.file>
e.g., uuencode my_file.doc my_file.doc > temp.uu

The first "my_file.doc" tells uuencode what file to process.
The second "my_file.doc" gets stored in the header of the uuencoded file 
and will be the name of the file when uudecoded by the recipient.
File temp.uu is where I temporarily store the uuencoded data.
Then use ^R in the body of the message to read temp.uu into the message.

Your recipient needs to run "uudecode <filename>", where <filename> is 
the name of the file he store your encoded message in.  

Note on uuencode/uudecode, only put one uuencoded message in a file, 
uudecode is not smart enough to close the first and open the next, etc.

Don Sugarman
sugarman@mmpcs1.psf.ge.com


From owner-pine-info@cac.washington.edu  Thu Jan 12 19:41:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18641;
	Thu, 12 Jan 95 19:41:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09495;
	Thu, 12 Jan 95 19:30:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09489;
	Thu, 12 Jan 95 19:30:14 -0800
Received: by hobbes.twntpe.cdc.com; Fri, 13 Jan 95 11:28:46 -0800
Date: Fri, 13 Jan 1995 11:28:45 -0800 (GMT)
From: Ed Greshko <egreshko@hobbes.twntpe.cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Frank Yao <fyao@calum.csclub.uwaterloo.ca>
Cc: pine-info@cac.washington.edu
Subject: Re: ??? about index screen
In-Reply-To: <D2A4vv.HwF@undergrad.math.uwaterloo.ca>
Message-Id: <Pine.SOL.3.91.950113112633.790L-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Frank,

	One thing I omitted.....

	For one message you can do the following while viewing the message:

1.	Type | (pipe).

2.	Type wc -l 

	This will return the line count to you....

						Ed


Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C




From owner-pine-info@cac.washington.edu  Thu Jan 12 20:19:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19516;
	Thu, 12 Jan 95 20:19:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06374;
	Thu, 12 Jan 95 20:13:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06368;
	Thu, 12 Jan 95 20:13:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #27)
	id m0rSdFc-00038KC; Thu, 12 Jan 95 20:04 PST
To: pine-info@cac.washington.edu
From: Judd Deaver <jdeaver@u.washington.edu>
Subject: Re: pine to cc:Mail
Date: Thu, 12 Jan 1995 15:45:14 -0800
Message-Id: <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu>
References: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu>

Does cc:mail include a uudecoding function standard? I tried just reading 
the ascii version of the file into the body but it reformatted the text 
and made it worthless. 

On Thu, 12 Jan 1995, David L Miller wrote:

> 
> Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
> good cc:Mail<->Internet gateway should be able to translate between MIME
> and cc:Mail attachments, but unfortunately many do not...
> 
> You may be able to get the file through by uuencoding it and including
> the uuencoded text into the body of a message using ^R. 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Thu, 12 Jan 1995, Judd Deaver wrote:
> 
> > Date: Thu, 12 JAN 1995 10:57:35 -0800 
> > From: Judd Deaver <jdeaver@u.washington.edu>
> > Newgroups: comp.groupware.lotus-notes.misc, comp.mail.pine,
> >     comp.mail.multi-media, comp.mail.misc, comp.mail.mime
> > Subject: pine to cc:Mail 
> > 
> > I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
> > network. I sent a Binary attachment but it did not seem to make it. Could 
> > this be because his network does not support MIME or because the way pine 
> > attaches files is different then cc:mail? If it is because they don't 
> > supprt MIME would an ASCII file attachment make it down or does pine 
> > automatically MIME encrypt all attachments?
> > 
> > Any help is GREATLY appreciated (this is an important file) could you 
> > please reply via e-mail though to jdeaver@u.washington.edu
> > 
> > Thank You.
> > 
> > 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 12 23:33:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23789;
	Thu, 12 Jan 95 23:33:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08974;
	Thu, 12 Jan 95 23:18:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from hisar.cc.boun.edu.tr by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08964;
	Thu, 12 Jan 95 23:17:53 -0800
Received: by hisar.cc.boun.edu.tr (5.65/DEC-Ultrix/4.3)
	id AA29965; Fri, 13 Jan 1995 09:03:27 -0500
Date: Fri, 13 Jan 1995 09:03:26 -0500 (EST)
From: Kursat Taskin <taskink@boun.edu.tr>
X-Sender: taskink@hisar.cc.boun.edu.tr
To: Pine Information List <pine-info@cac.washington.edu>
Cc: Pine Developers <pine-bugs@cac.washington.edu>
Subject: Re: Bug (ID 4N4DJ): LEARNING ENGILISH
In-Reply-To: <Pine.ULT.3.92.950109113006.2851G-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.ULT.3.91.950113090029.29938A-100000@hisar.cc.boun.edu.tr>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

                                                                                                                       

On Mon, 9 Jan 1995, David L Miller wrote:

> 
> This is a response to your Pine* bug report.  The purpose of this message
> is to: 1) acknowledge receipt of your report, 2) apologize in advance for
> the fact that you may not receive any other response to it, 3) assure you
> that if it is a bug report or enhancement suggestion, we will look at it
> carefully, and 4) tell you how to get more information or help. 
> 
> Pine is now used by well over a million people around the world, and
> thousands more every day.  Not surprisingly, the number of messages sent
> to our "pine-bugs" address has become enormous.  Since we receive no
> funding to support anyone outside the University of Washington, it is no
> longer possible to answer all of them individually. 
> 
> Please note that we get many questions which are not actually about Pine.
> We can't help you with other programs (talk, chat, IRC), with disk space
> on your system, or with unknown/invalid email addresses.  Talk with your
> local computer support people about these issues. 
> 
> Below is the entry from the Pine Frequently Asked Questions (FAQ) list
> about Pine information resources.  We hope it points you to the answers
> you need.  If you would like to receive the *entire* Pine FAQ by email,
> simply REPLY to this message. 
> 
>   The Pine Development Team            * Pine is a registered trademark
>    University of Washington               of, and copyright by, the
>       Seattle, WA, USA                       University of Washington.
> 
> -------------------------------------------------------------------------
> 
>                   PINE INFORMATION  RESOURCES
> 
> For information on how to configure and use Pine, we encourage you
> to read Pine's on-line help, including the Release Notes (the R command
> on the Main Menu.)  In addition, those of you handy with FTP or WWW
> tools may find some useful documentation on our Pine Information
> Center servers:
>         ftp://ftp.cac.washington.edu/pine
>         http://www.cac.washington.edu/pine
> 
> The Pine Frequently Asked Question (FAQ) list is available on those
> servers.
> 
> Here are some additional sources of assistance:
> 
>  o Check with your local support staff.  If you are not sure how to
>    contact them, try sending a very polite note to "postmaster"
>    on your system, asking that your inquiry be directed to the help desk.
> 
>  o If you can't get any help from your local support staff (or you
>    *are* the local support staff), consider sending a message to the
>    world-wide "pine-info" email list at:
>          pine-info@cac.washington.edu
>    or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
>    are linked together, so there is no need to both send email and post).
>    Your message will be seen by thousands of Pine users and system
>    administrators, one of whom may have just the information you seek.
> 
>  o If you really, *really* need to get in touch with the Pine development
>    team directly, send a message to:
>          pine@cac.washington.edu
> 
> 
> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
> 
> On Tue, 3 Jan 1995, Kursat Taskin wrote:
> 
> > Date: Tue, 3 Jan 1995 10:40:52 -0500 (EST)
> > From: Kursat Taskin <taskink@boun.edu.tr>
> > To: Pine Developers <pine-bugs@cac.washington.edu>
> > Subject: Bug (ID 4N4DJ): LEARNING ENGILISH
> > 
> > PLEAS SAY ME HOW CAN I LEARN ENGLISH.
> more information about lerning english


From owner-pine-info@cac.washington.edu  Fri Jan 13 03:12:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28557;
	Fri, 13 Jan 95 03:12:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11804;
	Fri, 13 Jan 95 03:03:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailserv.uni-tuebingen.de by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11798;
	Fri, 13 Jan 95 03:03:47 -0800
Received: from commlink.zdv.uni-tuebingen.de by mailserv.uni-tuebingen.de 
          with SMTP (PP); Fri, 13 Jan 1995 12:03:40 +0000
Received: from bamm.zdv.uni-tuebingen.de by commlink.zdv.uni-tuebingen.de 
          with SMTP (1.37.109.11/16.2) id AA154055018;
          Fri, 13 Jan 1995 12:03:38 +0100
Received: by bamm.zdv.uni-tuebingen.de (4.1/ZDV-Uni-Tuebingen-1.0) id AA11805;
          Fri, 13 Jan 95 12:03:37 +0100
Date: Fri, 13 Jan 1995 12:03:32 +0100 (MET)
From: martin.spohn@zdv.uni-tuebingen.de
X-Sender: zrnsm01@bamm.zdv.uni-tuebingen.de
To: pine-info@cac.washington.edu
Subject: pine locking
Message-Id: <Pine.SUN.3.91.950113114801.11621C-100000@bamm.zdv.uni-tuebingen.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello all,

we use pine-3.91, elm, mail on a variety of UNIX-hosts.

We found that the locking mechanisms used by pine are somewhat different
(more intelligent) than those of other agents.

Could someone please describe in detail the locking that pine uses
for read/write if one user starts several pine sessions. Is the locking
different if imap is used? Is it possible that a (older) pine process can
get back the lock from a newer one under certain circumstances?

The reason for this question is a strange situation that we experienced
on our convex. Sometimes a user can not open his INBOX. When invoking
any user agent this process is hung.
The workaround is to make a copy of /usr/spool/mail/LOGINID and replace the 
"locked" one with the copy.
THe conclusion is that there is a problem with INBOX file logging.

Thanks for any hints and help
------------------------------------------------------------------------------
Martin Spohn                     |
Universitaet Tuebingen           Z                          Tel. 07071 29 6970
Zentrum fuer Datenverarbeitung   D          E-mail: spohn@zdv.uni-tuebingen.de
Abteilung Netze                  V                          Fax: 07071 29 5912
Brunnenstr. 27, 72074 Tuebingen  |
------------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Fri Jan 13 03:46:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29365;
	Fri, 13 Jan 95 03:46:10 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15926;
	Fri, 13 Jan 95 03:36:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from fix.fsz.bme.hu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15917;
	Fri, 13 Jan 95 03:35:44 -0800
Received: from fatime.fsz.bme.hu by fix.fsz.bme.hu with SMTP id AA15796
  (5.65a++/IDA-BME-1.4.2 for pine-info@cac.washington.edu); Fri, 13 Jan 95 12:37:15 +0100
Message-Id: <9501131137.AA15796@fix.fsz.bme.hu>
Received: by fatime.fsz.bme.hu
	(1.37.109.11/16.2) id AA184347140; Fri, 13 Jan 1995 12:39:00 +0100
From: Jeffrey Hall <j_hall@fsz.bme.hu>
Subject: Unsubscribe
To: pine-info@cac.washington.edu
Date: Fri, 13 Jan 1995 12:39:00 MET
X-Mailer: Elm [revision: 109.14]

unsubscribe j_hall@fatime.fsz.bme.hu



From owner-pine-info@cac.washington.edu  Fri Jan 13 08:06:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06241;
	Fri, 13 Jan 95 08:06:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15764;
	Fri, 13 Jan 95 07:58:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15758;
	Fri, 13 Jan 95 07:57:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSoFA-00038MC; Fri, 13 Jan 95 07:48 PST
To: pine-info@cac.washington.edu
From: jason@IS.NET (Jason R. Mastaler)
Subject: 3.92
Date: 13 Jan 1995 06:45:49 GMT
Message-Id: <JASON.95Jan13014549@user1.IS.NET>

Anybody know approxamately when PINE ver 3.92 is due out?

jason


From owner-pine-info@cac.washington.edu  Fri Jan 13 08:07:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06308;
	Fri, 13 Jan 95 08:07:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19537;
	Fri, 13 Jan 95 07:54:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19531;
	Fri, 13 Jan 95 07:54:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSo8Q-00038CC; Fri, 13 Jan 95 07:41 PST
To: pine-info@cac.washington.edu
From: Jim Cozens <jcozens@vacgen.fisons.co.uk>
Subject: memory usage in 3.90
Date: 13 Jan 1995 11:57:10 GMT
Message-Id: <3f5pqm$4uj@netserver.fisonssurf.co.uk>

Since installing Pine 3.90 on ICL DRS6000 running SVR4 
we are running very short of memory. 
It's a great programbut how much memory would Pine be expected
to require per user for simple text messages.
Is there any way of reducing it from just over 2 meg per user 
which it seems to need now.
 Thanks in advance
Jim Cozens
jcozens@vacgen.fisons.co.uk 


From owner-pine-info@cac.washington.edu  Fri Jan 13 08:12:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06566;
	Fri, 13 Jan 95 08:12:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19680;
	Fri, 13 Jan 95 08:00:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from sun2.nsfnet-relay.ac.uk by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19674;
	Fri, 13 Jan 95 08:00:49 -0800
Via: uk.ac.durham; Fri, 13 Jan 1995 13:32:19 +0000
Received: from venus.dur.ac.uk by durham.ac.uk; Fri, 13 Jan 95 12:01:32 GMT
Received: from hercules (hercules.dur.ac.uk) by venus.dur.ac.uk;
          Fri, 13 Jan 95 11:58:48 GMT
Date: Fri, 13 Jan 1995 11:58:42 +0000 (GMT)
From: Barry Cornelius <Barry.Cornelius@durham.ac.uk>
To: martin.spohn@zdv.uni-tuebingen.de
Cc: pine-info@cac.washington.edu
Subject: Re: pine locking
In-Reply-To: <Pine.SUN.3.91.950113114801.11621C-100000@bamm.zdv.uni-tuebingen.de>
Message-Id: <Pine.SOL.3.91-941213.950113112944.22721F-100000@hercules.dur.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1906

> The reason for this question is a strange situation that we experienced
> on our convex. Sometimes a user can not open his INBOX. When invoking
> any user agent this process is hung.
> The workaround is to make a copy of /usr/spool/mail/LOGINID and replace the 
> "locked" one with the copy.
> THe conclusion is that there is a problem with INBOX file logging.

We have a large number of Unix machines of different architectures
networked together automounting a number of filesystems from different
servers using NFS.  In particular, the directory /usr/spool/mail can be
NFS-automounted by most of the machines. 

We occasionally find a locking problem with elm and pine, and the standard
solution I use to solve the problem is the one you describe above:

   cd /usr/spool/mail
   touch FOLDER.lock
   mv FOLDER FOLDER-
   cp -p FOLDER- FOLDER
   rm FOLDER.lock 
   rm FOLDER-

If you then do a "ls -a", you find that the FOLDER- file still exists 
but under the name .nfsXXX where each X is a digit.

It seems that some process somewhere has the file open, and the call of
fcntrl by elm/pine hangs.  The problem occurs here about once a month for
elm and very seldom for pine.  The only time it has occurred for pine was
when we had major problems one day, and many machines were rebooted.  With
elm the problem occurs with the person's inbox, whereas with pine the
problem occurred with folders in the person's mail subdirectory (because
these are NFS-mounted whereas with Pine we use IMAP for the inbox). 

Technically I don't know much about this subject, and so please excuse 
any errors.

--
Barry Cornelius                      Telephone: (0191 or +44 191) 374 4717
Academic Support Group, IT Service,            IT Service Office: 374 2892   
Science Site, University of Durham,                          Fax: 374 3741
Durham, DH1 3LE, UK                   E-mail: Barry.Cornelius@durham.ac.uk



From owner-pine-info@cac.washington.edu  Fri Jan 13 08:16:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06708;
	Fri, 13 Jan 95 08:16:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19869;
	Fri, 13 Jan 95 08:09:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19863;
	Fri, 13 Jan 95 08:09:14 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSoNo-00038CC; Fri, 13 Jan 95 07:57 PST
To: pine-info@cac.washington.edu
From: mraaum@ulrik.uio.no (Margrete Raaum)
Subject: PC-Pine 3.91 and news
Date: 13 Jan 1995 12:08:22 GMT
Message-Id: <3f5qfm$105@hermod.uio.no>

I am using PC-Pine&PC-NFS.
I have no problems reading/sending mail.
My problem is setting up Pine to read news.

In my pinerc i have:
news-collections=CLARINET *{nntp.uio.no/CLARINET *{nntp.uio.no/nntp}[clari.*]
                 COMP *{nntp.uio.no/nntp}[comp.*]
                 ALT *{nntp.uio.no/nntp}[alt.*]

I have tried: CLARINET *{nntp.uio.no/119}

I have tried nntp-server=nntp.uio.no 
and leaving out news-collections

But after monitoring nntp.uio.no/119 i find it doesn't get connection
(or even try to).

Does anyone know what's wrong with the configuration?


Margrete
-- 


*** Murgo optimo maximo



From owner-pine-info@cac.washington.edu  Fri Jan 13 08:56:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08217;
	Fri, 13 Jan 95 08:56:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16688;
	Fri, 13 Jan 95 08:43:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16682;
	Fri, 13 Jan 95 08:43:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSovA-00038CC; Fri, 13 Jan 95 08:32 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: User reporting that Pine 3.91 (SunOS 4.1.3) hangs.  Any ideas?
Date: 13 Jan 95 12:19:35 GMT
Message-Id: <ellis.789999575@gmi.edu>

I have been using 3.90 on SunOS 4.1.x since it came out, recently upgrading
to 3.91.  Apart from some design philosophy differences with the authors the
only real problem I have had with 3.91 is that it is extremely slow handling
my INBOX of 8500 messages, totalling untold megs of filespace.  It has
honestly been so long since I have used another MUA that I do not know if
that problem is also shared by elm and Mail.  Most of my online time is over
a pseudo tcp/ip connection using term to connect my home Sun to the campus
server and leaving pine open in an xterm, while I use other programs such as
nn, gopher, etc. in other xterms.

In preparation for upgrading the systemwide pine from 3.89 to 3.91, I turned
one of my relatively sophisticated DOS modem users who has been using 3.89
to read news and mail loose on it.  He has had to do a lot of fiddling with
setting that involve control characters that I have not had to deal with.
He finally seems to have that straightened out, but he is reporting that it
has hung several times and kicked him back to the Which Host? prompt that he
gets at his local Michnet dialin point.  I cannot really duplicate his
setup, but have seen nothing like this.  Perhaps the sort of thing that is
happening when pine seems to go to sleep on me for several minutes at a time
is causing more serious problems with his type of connection.

Does anybody else have any similar cases?  Any insight?  I really would like
to update the systemwide pine, but am not in a position to hold people's
hands.



-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Fri Jan 13 09:19:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09902;
	Fri, 13 Jan 95 09:19:32 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21388;
	Fri, 13 Jan 95 09:13:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21380;
	Fri, 13 Jan 95 09:13:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSpNA-00038CC; Fri, 13 Jan 95 09:01 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Bugggggggy pinedemo at demo.cac.washington.edu
Date: Fri, 13 Jan 1995 13:02:05 +0000
Message-Id: <Pine.SUN.3.91.950113130038.10594R-100000@apus.cus.cam.ac.uk>
References: <Pine.NXT.3.92.950110002650.23434A-100000@Tomobiki-Cho.CAC.Washington.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.NXT.3.92.950110002650.23434A-100000@Tomobiki-Cho.CAC.Washington.EDU> 

On Tue, 10 Jan 1995, Mark Crispin wrote:

> is very Politically Correct).  Please keep the bouquets and testimonials
> coming -- it *does* help in justifying our continued existance!
> 

You certaintly have my grateful thanks, and even flowers if necessary! 
Several thousand grateful users here, many of the "extremely naive" 
variety. 
Without your good work we would have to spend a lot more time teaching 
them how to do all the arcane things other mailers seem to need.

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Fri Jan 13 10:16:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13001;
	Fri, 13 Jan 95 10:16:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22536;
	Fri, 13 Jan 95 10:04:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22530;
	Fri, 13 Jan 95 10:04:20 -0800
Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13696;
	Fri, 13 Jan 95 10:04:15 -0800
Date: Fri, 13 Jan 1995 10:04:15 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: "Jason R. Mastaler" <jason@IS.NET>
Cc: pine-info@cac.washington.edu
Subject: Re: 3.92
In-Reply-To: <JASON.95Jan13014549@user1.IS.NET>
Message-Id: <Pine.ULT.3.92.950113100324.25529E-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 13 Jan 1995, Jason R. Mastaler wrote:

> Anybody know approxamately when PINE ver 3.92 is due out?

Jason,
"Anybody" might, but *we* don't know yet... :)

-teg


From owner-pine-info@cac.washington.edu  Fri Jan 13 10:27:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13435;
	Fri, 13 Jan 95 10:27:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18974;
	Fri, 13 Jan 95 10:16:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18968;
	Fri, 13 Jan 95 10:16:10 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02738;
	Fri, 13 Jan 95 10:16:09 -0800
Date: Fri, 13 Jan 1995 09:01:46 -0600 (CST)
From: Mark Alan Temple <mtemple1@bigcat.missouri.edu>
Subject: compressed pine format
To: owner-pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501130834.A15669-0100000@bigcat>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 456
Resent-Date: Fri, 13 Jan 1995 10:16:05 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950113101605.2155F@shiva1.cac.washington.edu>

Pine Gurus,

I would like to request that you include the most recent version of the 
pine source in zip format.  We are a vms site and unzip is much easier 
for us that tar and compress.  We like zip because it 
compress/decompresses the files and the structure in one swipe.  I know 
that is one more file to stock, but it might make pine a little more 
universally exportable.

Thanks if you can.

Oh. I think pine is great!!!  Keep up the good work.





From owner-pine-info@cac.washington.edu  Fri Jan 13 10:38:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14011;
	Fri, 13 Jan 95 10:38:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19265;
	Fri, 13 Jan 95 10:28:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19257;
	Fri, 13 Jan 95 10:28:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSqZ6-00038CC; Fri, 13 Jan 95 10:17 PST
To: pine-info@cac.washington.edu
From: gasi@Informatik.Uni-Marburg.de (Herbert Gasiorowski)
Subject: DosPine will not create ~/Mail!?
Date: 13 Jan 1995 11:11:19 GMT
Message-Id: <3f5n4n$8u1@surz03.HRZ.Uni-Marburg.DE>

When used for the first time, DosPine (3.90) will NOT create the Mail
directory in the users home. 
Is might be a fault in imap (imap-3.6.BETA)?

Herbert Gasiorowski



From owner-pine-info@cac.washington.edu  Fri Jan 13 12:07:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23400;
	Fri, 13 Jan 95 12:07:10 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25645;
	Fri, 13 Jan 95 12:00:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from treasure.coastalnet.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25639;
	Fri, 13 Jan 95 12:00:25 -0800
Received: from abaco ([204.183.40.2]) by treasure.coastalnet.com (4.1/SMI-4.1)
	id AA22003; Fri, 13 Jan 95 14:57:53 EST
Date: Fri, 13 Jan 1995 14:57:51 -0500 (EST)
From: Stephen Dorsett <dorsett@coastalnet.com>
Subject: pine running in chroot 
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501131405.A15625-0100000@abaco>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I am trying to get pine 3.89 to run in a chroot environment on SunOS 
4.1.3. It doesn't want to acknowledge the presence of or send mail.

Any ideas ?

========================================================================
Stephen Dorsett                            dorsett.giex@coastalnet.com  
Wide Area Network Manager, GIEx Corp.      1-800-514-5NET   
========================================================================



From owner-pine-info@cac.washington.edu  Fri Jan 13 12:18:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23862;
	Fri, 13 Jan 95 12:18:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25994;
	Fri, 13 Jan 95 12:12:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul4.u.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25988;
	Fri, 13 Jan 95 12:12:15 -0800
Received: by saul4.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23677;
	Fri, 13 Jan 95 12:12:14 -0800
X-Sender: absweger@saul4.u.washington.edu
Date: Fri, 13 Jan 1995 12:12:14 -0800 (PST)
From: Andrew Sweger <absweger@u.washington.edu>
To: Pine Information <pine-info@cac.washington.edu>
Subject: Printing multiple messages
Message-Id: <Pine.OSF.3.91a.950113120709.23176C-100000@saul4.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

In Pine for UNIX, when selecting multiple messages in the index ( ';'
command) and then printing them ( 'ay' to customer printer, lpr), the
messages are streamed together. Any way to cause a FF between pages? Same
problem with 'pipe'. Didn't notice an option to make each message a 
separate call to the program. Thanks.

-- 
absweger@u.washington.edu





From owner-pine-info@cac.washington.edu  Fri Jan 13 12:32:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24663;
	Fri, 13 Jan 95 12:32:54 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26269;
	Fri, 13 Jan 95 12:27:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from noc.tor.hookup.net by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26263;
	Fri, 13 Jan 95 12:27:42 -0800
Received: from jchiso.tor.hookup.net (jchiso.tor.hookup.net [165.154.49.127]) by noc.tor.hookup.net (8.6.9/1.249) with SMTP id PAA03351; Fri, 13 Jan 1995 15:27:39 -0500
Message-Id: <199501132027.PAA03351@noc.tor.hookup.net>
X-Sender: jchiso@noc.tor.hookup.net (Unverified)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 13 Jan 1995 15:21:52 -0500
To: pine-info@cac.washington.edu
From: jchiso@hookup.net (Jeffrey S. Chisholm)
Subject: I need help!
X-Mailer: <PC Eudora Version 1.4>

Hi!
        I have an account at the University of Toronto, and for the past 2 
years, everything has been working just fine. Yesterday morning, however, 
something happened and I can no longer send mail. I receive incoming mail, 
but every time I try to send mail, I get a statement saying "ZMailer ignored 
send-mail option" and then I get a letter from the post office telling me 
that the user is unknown. I know that the users that I write to are known 
because I've been writing to the successfully for quite a while. My account 
is still open, and the school can't detect any problems. I looked through 
the Help menu, and the only option I think I have is to make statements in 
the editor, but I havn't got a clue how to access the editor, or what to 
say. I would really appreciate it if you could assist me in resolving my 
problem. You can either respond to this address, or to mine: 
bense@ecf.toronto.edu . Thank you!



From owner-pine-info@cac.washington.edu  Fri Jan 13 13:35:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28412;
	Fri, 13 Jan 95 13:35:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27918;
	Fri, 13 Jan 95 13:30:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul4.u.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27912;
	Fri, 13 Jan 95 13:30:15 -0800
Received: by saul4.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26588;
	Fri, 13 Jan 95 13:30:09 -0800
X-Sender: absweger@saul4.u.washington.edu
Date: Fri, 13 Jan 1995 13:30:08 -0800 (PST)
From: Andrew Sweger <absweger@u.washington.edu>
To: Stephen Dorsett <dorsett@coastalnet.com>
Cc: Pine Information <pine-info@cac.washington.edu>
Subject: Re: pine running in chroot 
In-Reply-To: <Pine.3.89.9501131405.A15625-0100000@abaco>
Message-Id: <Pine.OSF.3.91a.950113132844.25130A-100000@saul4.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 13 Jan 1995, Stephen Dorsett wrote:

> I am trying to get pine 3.89 to run in a chroot environment on SunOS 
> 4.1.3. It doesn't want to acknowledge the presence of or send mail.
> 
> Any ideas ?

In your pine's new root, you probably don't have a MTA (sendmail) or 
access to the spools (unless you did set it up that way).

-- 
  /  Andrew B. Sweger                      absweger@u.washington.edu
 //  Computer Support Manager              csg@fammed.washington.edu
 \\  Department of Family Medicine, HQ-30  (206) 543-2461 (Office)
 //  UNIVERSITY OF WASHINGTON              (206) 685-4337 (Voice Mail)
 /   Seattle, WA 98195                     (206) 685-0610 (FAX)
------------------------------------------------------------------------------
The great thing about multitasking is that several things can go wrong at once.




From owner-pine-info@cac.washington.edu  Fri Jan 13 13:42:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28696;
	Fri, 13 Jan 95 13:42:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28127;
	Fri, 13 Jan 95 13:37:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from treasure.coastalnet.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28121;
	Fri, 13 Jan 95 13:37:20 -0800
Received: from abaco ([204.183.40.2]) by treasure.coastalnet.com (4.1/SMI-4.1)
	id AA22451; Fri, 13 Jan 95 16:33:33 EST
Date: Fri, 13 Jan 1995 16:33:29 -0500 (EST)
From: Stephen Dorsett <dorsett@coastalnet.com>
Subject: Re: pine running in chroot 
To: Andrew Sweger <absweger@u.washington.edu>
Cc: Pine Information <pine-info@cac.washington.edu>
In-Reply-To: <Pine.OSF.3.91a.950113132844.25130A-100000@saul4.u.washington.edu>
Message-Id: <Pine.3.89.9501131653.A20417-0100000@abaco>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


It was REALLY simple. Pine wanted to look in some really bizarre (from my
BSD perspective) place for the mail spool directory. I just set up the
pine.conf to point to /var/spool/mail, and we are up and running.

Thanks for the quick reply !

========================================================================
Stephen Dorsett                            dorsett.giex@coastalnet.com  
Wide Area Network Manager, GIEx Corp.      1-800-514-5NET   
========================================================================



From owner-pine-info@cac.washington.edu  Fri Jan 13 14:25:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01193;
	Fri, 13 Jan 95 14:25:45 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25184;
	Fri, 13 Jan 95 14:10:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25174;
	Fri, 13 Jan 95 14:10:30 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09549;
	Fri, 13 Jan 95 14:10:28 -0800
Date: Tue, 10 Jan 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Message-Id: <9408241626.AA29044@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="=========="
Subject: Pine Frequently Asked Questions
Resent-Date: Fri, 13 Jan 1995 14:10:12 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950113141010.9523A@shiva1.cac.washington.edu>

--==========
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--==========
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--==========
Content-Description: General Questions About Pine
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: General Questions About Pine


                         GENERAL QUESTIONS ABOUT PINE

------------
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

------------
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

------------
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

------------
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

------------
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
------------
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

------------
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

------------
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--------------
--==========
Content-Description: Basic Usage Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Basic Usage Problems

                        BASIC USAGE PROBLEMS
                                       
------------
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

------------
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
------------
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


------------
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

------------
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

------------
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

------------
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
------------
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
------------
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

------------
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--------------
--==========
Content-Description: Printing
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Printing


                              PRINTING

------------
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


------------
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
------------
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
------------
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

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

--==========
Content-Description: Newsreading and Posting
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Newsreading and Posting

------------
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

------------
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--------------

--==========
Content-Description: Attachments
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Attachments

------------
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

------------
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
------------
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

------------
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.perl";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.c";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++--
--------------

--==========
Content-Description: Folder Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Folder Problems


                            FOLDER PROBLEMS
                                       
------------
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
------------
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
------------
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
------------
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
------------
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
------------
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--------------
--==========
Content-Description: Addressbook Usage and Conversions
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Addressbook Usage and Conversions


                      ADDRESSBOOK USAGE AND CONVERSIONS

------------
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
------------
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--+++++
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="elm-to-pine"

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--+++++--

--------------
                                       
--==========
Content-Description: Installation and Configuration
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Installation and Configuration


                        INSTALLATION AND CONFIGURATION
                                       
------------
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
------------
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
------------
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
------------
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
------------
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
------------
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--------------
                                       
--==========
Content-Description: Platform-specific Issues
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Platform-specific Issues


                         PLATFORM-SPECIFIC ISSUES

------------
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
------------
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
------------
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support.. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--------------
--==========
Content-Description: Bug Reports
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Bug Reports


                                 BUG REPORTS

------------
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

------------
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

------------
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--------------
--==========
Content-Description: Development Info
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Development Info


                               DEVELOPMENT INFO
                                       
------------
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

------------
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
------------
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
------------
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--------------
                                       
--==========--


From owner-pine-info@cac.washington.edu  Fri Jan 13 15:11:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03387;
	Fri, 13 Jan 95 15:11:07 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00263;
	Fri, 13 Jan 95 15:03:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00257;
	Fri, 13 Jan 95 15:03:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSus4-00038JC; Fri, 13 Jan 95 14:53 PST
To: pine-info@cac.washington.edu
From: pvb@paulvb.stortek.com (Paul von Behren)
Subject: Re: JOE 2.5
Message-Id: <D2Cyx0.DDE@stortek.com>
References: <D224M0.HAo@world.std.com> <D238Is.8vG@world.std.com> <3eteuf$1jk@apakabar.cc.columbia.edu>
Date: Fri, 13 Jan 1995 19:17:23 GMT

Yeechang Lee (ycl6@namaste.cc.columbia.edu) wrote:
: Joseph H Allen <jhallen@world.std.com> says:
: |Please wait for version 2.5 to appear.  Version 2.4 has a minor bug which
: |prevents you from creating new files.

: Well, I have 2.5 up and running, and it's nice!  (I'm surprised the man
: page doesn't mention JOETERM, though.)  I can't really say I've noticed
: much of a difference, but I'm sure it's all there.  More kudos to Joe
: and JOE!

: And for you comp.mail.pine folk who have been looking for a nice,
: easy-to-use editor that doesn't have Pico's clunks, check out JOE--it
: fits the bill!

I agree with the joe raves - one thing not mentioned is that joe (and it's
variants) use ispell as a spelling checker.  ispell doesn't just tell you
something is misspelled, it pops up a list of alternates.  You can select an
alternate by number and it replaces it.  You can add words to your private
dictionary.  Based on my observations, usenet NEEDS a good spell checker :-)

, 

: --   _____________________________________________________________________
:      Yeechang Lee  (ycl6@columbia.edu)|Nevada Las Vegas Mission Jul'92-'94
:      Columbia University/New York City|Celestial Kingdom through Taco Bell
:      Still working on my juggling-while-I-play-the-harmonica routine . . .

--
-------------------------------------------------
Paul von Behren       Paul_von_Behren@stortek.com


From owner-pine-info@cac.washington.edu  Fri Jan 13 15:50:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05091;
	Fri, 13 Jan 95 15:50:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01098;
	Fri, 13 Jan 95 15:43:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from uu4.psi.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01092;
	Fri, 13 Jan 95 15:43:03 -0800
Received: from msi.UUCP by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP;
        id AA18697 for ; Fri, 13 Jan 95 18:23:24 -0500
Date: Fri, 13 Jan 1995 14:25:08 -0800 (PST)
From: Knute Snortum <knute@masi.com>
To: Pine Information Discussion Group <pine-info@cac.washington.edu>
Subject: Pine on Altos or SCO
Message-Id: <Pine.SCO.3.91.950113142024.24892B-100000@MSI.masi.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I've asked this before, but does any one have a binary, or know how to 
compile pine on an Altos 1000?  Barring that, how about an SCO System V 
make file?  I've heard that early Xenix is close to old Altos Unix, too.  
I'll take just about anything, I'm not picky.

--- Knute Snortum			Internet: knute@msi.masi.com
    MAS Inc.				Compuserve: 72144,1646



From owner-pine-info@cac.washington.edu  Fri Jan 13 15:52:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05170;
	Fri, 13 Jan 95 15:52:11 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27446;
	Fri, 13 Jan 95 15:49:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27440;
	Fri, 13 Jan 95 15:48:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSvcJ-00038CC; Fri, 13 Jan 95 15:41 PST
To: pine-info@cac.washington.edu
From: pjh@tecoma.mccc.edu (Pete Holsberg)
Subject: Script as printer command ???
Message-Id: <D2CwB4.498@tecoma.mccc.edu>
Date: Fri, 13 Jan 1995 18:21:04 GMT

I would like to use the following script as my printer command,
with <???> representing the name of the current email message.
How do I specify the name???

cat <????> | jetpr -h <???> | lp -dlj

Thanks,
Pete


From owner-pine-info@cac.washington.edu  Fri Jan 13 16:04:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05678;
	Fri, 13 Jan 95 16:04:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01457;
	Fri, 13 Jan 95 15:59:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01451;
	Fri, 13 Jan 95 15:59:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSvi4-00038JC; Fri, 13 Jan 95 15:47 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: pine locking
Date: Fri, 13 Jan 1995 14:45:12 -0800
Message-Id: <Pine.ULT.3.92.950113144405.2155e-100000@shiva1.cac.washington.edu>
References: <Pine.SUN.3.91.950113114801.11621C-100000@bamm.zdv.uni-tuebingen.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.91.950113114801.11621C-100000@bamm.zdv.uni-tuebingen.de> 


>From the Pine FAQ (just updated/posted): 

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   

--DLM

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 13 Jan 1995 martin.spohn@zdv.uni-tuebingen.de wrote:

> Date: Fri, 13 JAN 1995 11:03:32 GMT 
> From: martin.spohn@zdv.uni-tuebingen.de
> Newgroups: comp.mail.pine
> Subject: pine locking 
> 
> Hello all,
> 
> we use pine-3.91, elm, mail on a variety of UNIX-hosts.
> 
> We found that the locking mechanisms used by pine are somewhat different
> (more intelligent) than those of other agents.
> 
> Could someone please describe in detail the locking that pine uses
> for read/write if one user starts several pine sessions. Is the locking
> different if imap is used? Is it possible that a (older) pine process can
> get back the lock from a newer one under certain circumstances?
> 
> The reason for this question is a strange situation that we experienced
> on our convex. Sometimes a user can not open his INBOX. When invoking
> any user agent this process is hung.
> The workaround is to make a copy of /usr/spool/mail/LOGINID and replace the 
> "locked" one with the copy.
> THe conclusion is that there is a problem with INBOX file logging.
> 
> Thanks for any hints and help
> ------------------------------------------------------------------------------
> Martin Spohn                     |
> Universitaet Tuebingen           Z                          Tel. 07071 29 6970
> Zentrum fuer Datenverarbeitung   D          E-mail: spohn@zdv.uni-tuebingen.de
> Abteilung Netze                  V                          Fax: 07071 29 5912
> Brunnenstr. 27, 72074 Tuebingen  |
> ------------------------------------------------------------------------------
> 
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan 13 16:32:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07244;
	Fri, 13 Jan 95 16:32:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28450;
	Fri, 13 Jan 95 16:29:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28444;
	Fri, 13 Jan 95 16:29:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSwC4-00038JC; Fri, 13 Jan 95 16:18 PST
To: pine-info@cac.washington.edu
From: dbrenner@nemo.weeg.uiowa.edu (Doug Brenner)
Subject: Re: zero-length .pine-interrupted-mail files
Date: 13 Jan 95 16:16:51
Message-Id: <DBRENNER.95Jan13161651@nemo.weeg.uiowa.edu>
References: <3euh21$12np@bigblue.oit.unc.edu>
In-Reply-To: pmb1@tmphost.york.ac.uk's message of Wed, 11 Jan 1995 09:41:04 GMT

We also have an AIX 3.2.5 system (around 12,000 user accounts).  We've been
on break, but now that people are returning, our Help Desk is also starting
to receive questions about phantom interrupted mail.

Our problem is also the zero length .pine-interrupted-mail file.  We compiled
Pine 3.91 with "#define DEFAULT_DEBUG 0" to help save disk space.  Based on
the information provided by Trey Harris, I wonder if we should go back to the
default debug level.

pmb1@tmphost.york.ac.uk (Mike Brudenell) writes:

> Strange... I had to deal with exactly the same problem only yesterday.  
> Traced it eventually to the empty interrupted mail file (Pine was 
> aborting with a bug detected).
[...some text deleted...]
> The Computing Service, University of York, Heslington, York, YO1 5DD, UK
> 
> On 10 Jan 1995, Trey Harris wrote:
> 
> > I am running Pine 3.91 on a 15,000-user AIX 3.2.5 site.  Among these 
> > users, the most common problem they experience with Pine (our Help Desk 
> > says they get this question several times a day) is zero-length 
> > .pine-interrupted-mail* files in the home directory.
> > 
> > What happens when they get these is this: Pine tells them they have 
> > postponed mail, and asks if they wish to continue.  When the user answers 
> > "Yes", it either says "You don't have any interrupted mail!" and goes 
> > back to the menu/index, or it core dumps with an "abend" error.
> > 
> > As far as I am able to tell, Pine *never* produces a non-zero-length 
> > pine-interrupted-mail* file.
> > 
> > We had this problem with even greater frequency than is now the case, but 
> > I was able to allieviate the problem to some degree by recompiling Pine.  
> > I had originally compiled Pine without "-DDEBUG" because pine-debug files 
> > were accumulating on our system, and sometimes Pine would go out of 
> > control and continue to write to a pine-debug file until the filesystem 
> > was full.
> > 
> > Once I restored "-DDEBUG" (setting the default debug level to 0) the 
> > .pine-interrupted-mail files were reduced, but they still occur.
> > 
> > Can anyone suggest how we can fix this?  It is extremely annoying to both 
> > our Help Desk and our users.
> > -- 
> > Trey Harris                              http://sunsite.unc.edu/harris
> >   System Administrator, Project Isis, Office of Information Technology
> >                        The University of North Carolina at Chapel Hill


From owner-pine-info@cac.washington.edu  Fri Jan 13 17:02:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08196;
	Fri, 13 Jan 95 17:02:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02634;
	Fri, 13 Jan 95 16:48:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul2.u.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02628;
	Fri, 13 Jan 95 16:48:30 -0800
Received: by saul2.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17351;
	Fri, 13 Jan 95 16:48:29 -0800
X-Sender: absweger@saul2.u.washington.edu
Date: Tue, 10 Jan 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Message-Id: <9408241626.AA29044@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="=========="
Subject: Pine Frequently Asked Questions
Resent-Date: Fri, 13 Jan 1995 14:10:12 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950113141010.9523A@shiva1.cac.washington.edu>
Resent-Date: Fri, 13 Jan 1995 16:48:25 -0800 (PST)
Resent-From: Andrew Sweger <absweger@u.washington.edu>
Resent-To: nhart@saul.u.washington.edu
Resent-Message-Id: <Pine.OSF.3.91a.950113164824.16911Y@saul2.u.washington.edu>

--==========
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--==========
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--==========
Content-Description: General Questions About Pine
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: General Questions About Pine


                         GENERAL QUESTIONS ABOUT PINE

------------
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

------------
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

------------
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

------------
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

------------
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
------------
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

------------
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

------------
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--------------
--==========
Content-Description: Basic Usage Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Basic Usage Problems

                        BASIC USAGE PROBLEMS
                                       
------------
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

------------
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
------------
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


------------
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

------------
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

------------
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

------------
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
------------
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
------------
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

------------
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--------------
--==========
Content-Description: Printing
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Printing


                              PRINTING

------------
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


------------
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
------------
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
------------
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

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

--==========
Content-Description: Newsreading and Posting
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Newsreading and Posting

------------
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

------------
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--------------

--==========
Content-Description: Attachments
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Attachments

------------
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

------------
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
------------
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

------------
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.perl";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.c";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++--
--------------

--==========
Content-Description: Folder Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Folder Problems


                            FOLDER PROBLEMS
                                       
------------
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
------------
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
------------
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
------------
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
------------
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
------------
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--------------
--==========
Content-Description: Addressbook Usage and Conversions
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Addressbook Usage and Conversions


                      ADDRESSBOOK USAGE AND CONVERSIONS

------------
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
------------
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--+++++
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="elm-to-pine"

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--+++++--

--------------
                                       
--==========
Content-Description: Installation and Configuration
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Installation and Configuration


                        INSTALLATION AND CONFIGURATION
                                       
------------
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
------------
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
------------
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
------------
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
------------
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
------------
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--------------
                                       
--==========
Content-Description: Platform-specific Issues
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Platform-specific Issues


                         PLATFORM-SPECIFIC ISSUES

------------
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
------------
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
------------
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support.. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--------------
--==========
Content-Description: Bug Reports
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Bug Reports


                                 BUG REPORTS

------------
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

------------
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

------------
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--------------
--==========
Content-Description: Development Info
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Development Info


                               DEVELOPMENT INFO
                                       
------------
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

------------
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
------------
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
------------
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--------------
                                       
--==========--



From owner-pine-info@cac.washington.edu  Fri Jan 13 17:04:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08417;
	Fri, 13 Jan 95 17:04:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02548;
	Fri, 13 Jan 95 16:43:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul2.u.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02542;
	Fri, 13 Jan 95 16:43:50 -0800
Received: by saul2.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17136;
	Fri, 13 Jan 95 16:43:49 -0800
X-Sender: absweger@saul2.u.washington.edu
Date: Tue, 10 Jan 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Message-Id: <9408241626.AA29044@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="=========="
Subject: Pine Frequently Asked Questions
Resent-Date: Fri, 13 Jan 1995 14:10:12 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950113141010.9523A@shiva1.cac.washington.edu>
Resent-Date: Fri, 13 Jan 1995 16:43:38 -0800 (PST)
Resent-From: Andrew Sweger <absweger@u.washington.edu>
Resent-To: nhart@saul.u.washington.edu
Resent-Message-Id: <Pine.OSF.3.91a.950113164338.16911X@saul2.u.washington.edu>

--==========
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--==========
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--==========
Content-Description: General Questions About Pine
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: General Questions About Pine


                         GENERAL QUESTIONS ABOUT PINE

------------
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

------------
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

------------
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

------------
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

------------
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
------------
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

------------
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

------------
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--------------
--==========
Content-Description: Basic Usage Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Basic Usage Problems

                        BASIC USAGE PROBLEMS
                                       
------------
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

------------
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
------------
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


------------
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

------------
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

------------
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

------------
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
------------
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
------------
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

------------
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--------------
--==========
Content-Description: Printing
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Printing


                              PRINTING

------------
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


------------
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
------------
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
------------
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

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

--==========
Content-Description: Newsreading and Posting
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Newsreading and Posting

------------
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

------------
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--------------

--==========
Content-Description: Attachments
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Attachments

------------
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

------------
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
------------
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

------------
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.perl";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.c";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++--
--------------

--==========
Content-Description: Folder Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Folder Problems


                            FOLDER PROBLEMS
                                       
------------
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
------------
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
------------
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
------------
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
------------
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
------------
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--------------
--==========
Content-Description: Addressbook Usage and Conversions
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Addressbook Usage and Conversions


                      ADDRESSBOOK USAGE AND CONVERSIONS

------------
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
------------
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--+++++
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="elm-to-pine"

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--+++++--

--------------
                                       
--==========
Content-Description: Installation and Configuration
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Installation and Configuration


                        INSTALLATION AND CONFIGURATION
                                       
------------
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
------------
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
------------
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
------------
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
------------
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
------------
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--------------
                                       
--==========
Content-Description: Platform-specific Issues
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Platform-specific Issues


                         PLATFORM-SPECIFIC ISSUES

------------
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
------------
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
------------
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support.. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--------------
--==========
Content-Description: Bug Reports
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Bug Reports


                                 BUG REPORTS

------------
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

------------
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

------------
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--------------
--==========
Content-Description: Development Info
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Development Info


                               DEVELOPMENT INFO
                                       
------------
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

------------
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
------------
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
------------
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--------------
                                       
--==========--



From owner-pine-info@cac.washington.edu  Fri Jan 13 17:14:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09181;
	Fri, 13 Jan 95 17:14:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03295;
	Fri, 13 Jan 95 17:10:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03289;
	Fri, 13 Jan 95 17:10:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSwpP-00038CC; Fri, 13 Jan 95 16:58 PST
To: pine-info@cac.washington.edu
From: Brad <syb3@aber.ac.uk>
Subject: Re: jpico editor
Date: Fri, 13 Jan 1995 18:03:53 +0000
Message-Id: <Pine.OSF.3.91.950113180252.25490E-100000@osfb.aber.ac.uk>
References: <Pine.OSF.3.91.950113173957.25490B-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.OSF.3.91.950113173957.25490B-100000@osfb.aber.ac.uk> 

	Okay, I *almost* have this now, but pine dies with this: 

Making Pine.
cc -O4 -Olimit 604  -g3 -DDEBUG -D_BSD -DSYSTYPE=\"OSF\" -c helptext.c
umerge: Error: Out of memory!  Check datasize limit.
*** Exit 1
Stop.

Does anyone have any idea what that means? :) Thanks again!! 

 ___  _                     _a' /(   <.  Simon Bradley, Knight Protector!
/ __><_>._ _ _  ___ ._ _ ~~ _}\ \(  _  ) E-mail: syb3@aber.ac.uk
\__ \| || ' ' |/ . \| ' |      \(._(.)'  Finger: syb3@osfb.aber.ac.uk
<___/|_||_|_|_|\___/|_|_|     ._>. _>.   WWW: http://www.aber.ac.uk/~syb3/

On Fri, 13 Jan 1995, Brad wrote:

> 	Does anyone know how I can get this 'enhanced' version of pico to
> be the *default* editor (as opposed to the alternate editor)? I've tried
> figuring out how to do it by recompiling Pine, but I'm not exactly a
> computer guru. :) Thanks... 


From owner-pine-info@cac.washington.edu  Fri Jan 13 17:17:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09254;
	Fri, 13 Jan 95 17:17:01 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29544;
	Fri, 13 Jan 95 17:14:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29538;
	Fri, 13 Jan 95 17:14:14 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSwuW-00038JC; Fri, 13 Jan 95 17:04 PST
To: pine-info@cac.washington.edu
From: geert@dialis.xs4all.nl (Geert Bosch)
Date: 12 Jan 95 21:26:01 
Subject: Pine ported to OS/2 (?)
Message-Id: <202_9501131806@dialis.xs4all.nl>

Hallo All!

Does anybody know whether Pine has been ported to OS/2 already, or if anybody
is busy or planning to do so. I think there would be a lot of people
interested in it.

Groetjes, Geert 



From owner-pine-info@cac.washington.edu  Fri Jan 13 17:31:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09724;
	Fri, 13 Jan 95 17:31:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29783;
	Fri, 13 Jan 95 17:27:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from uu4.psi.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29768;
	Fri, 13 Jan 95 17:27:39 -0800
Received: from msi.UUCP by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP;
        id AA03066 for ; Fri, 13 Jan 95 20:14:27 -0500
Date: Fri, 13 Jan 1995 16:42:46 -0800 (PST)
From: Scott McClure <scott@masi.com>
To: pine-info@cac.washington.edu
Subject: Re: JOE 2.5
In-Reply-To: <D2Cyx0.DDE@stortek.com>
Message-Id: <Pine.SCO.3.91.950113163948.29764F-100000@MSI.masi.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 13 Jan 1995, Paul von Behren wrote:

> Yeechang Lee (ycl6@namaste.cc.columbia.edu) wrote:
> : easy-to-use editor that doesn't have Pico's clunks, check out JOE--it
> : fits the bill!
> 
> I agree with the joe raves - one thing not mentioned is that joe (and it's
> variants) use ispell as a spelling checker.  ispell doesn't just tell you
> something is misspelled, it pops up a list of alternates.  You can select an
> alternate by number and it replaces it.  You can add words to your private
> dictionary.  Based on my observations, usenet NEEDS a good spell checker :-)

OK, I'll finally bite.  Where can I get ispell?  Being one of the world's 
worst spellers this is something I need!  We are a SCO shop.

> 
> : --   _____________________________________________________________________
> :      Yeechang Lee  (ycl6@columbia.edu)|Nevada Las Vegas Mission Jul'92-'94
> :      Columbia University/New York City|Celestial Kingdom through Taco Bell
> :      Still working on my juggling-while-I-play-the-harmonica routine . . .
> 
> --
> -------------------------------------------------
> Paul von Behren       Paul_von_Behren@stortek.com

______________________________________________________________________
Scott McClure, CPIM                           Mail: scott@msi.masi.com
MicroAccounting Systems, Inc.                    Voice: (503) 641-4200
Portland, Or                                       Fax: (503) 643-1386



From owner-pine-info@cac.washington.edu  Fri Jan 13 17:59:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10503;
	Fri, 13 Jan 95 17:59:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04027;
	Fri, 13 Jan 95 17:55:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04020;
	Fri, 13 Jan 95 17:55:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSxXj-00038KC; Fri, 13 Jan 95 17:44 PST
To: pine-info@cac.washington.edu
From: Brad <syb3@aber.ac.uk>
Subject: jpico editor
Date: Fri, 13 Jan 1995 17:41:34 +0000
Message-Id: <Pine.OSF.3.91.950113173957.25490B-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

	Does anyone know how I can get this 'enhanced' version of pico to
be the *default* editor (as opposed to the alternate editor)? I've tried
figuring out how to do it by recompiling Pine, but I'm not exactly a
computer guru. :) Thanks... 

 ___  _                     _a' /(   <.  Simon Bradley, Knight Protector!
/ __><_>._ _ _  ___ ._ _ ~~ _}\ \(  _  ) E-mail: syb3@aber.ac.uk
\__ \| || ' ' |/ . \| ' |      \(._(.)'  Finger: syb3@osfb.aber.ac.uk
<___/|_||_|_|_|\___/|_|_|     ._>. _>.   WWW: http://www.aber.ac.uk/~syb3/


From owner-pine-info@cac.washington.edu  Fri Jan 13 18:21:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11111;
	Fri, 13 Jan 95 18:21:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00706;
	Fri, 13 Jan 95 18:19:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00700;
	Fri, 13 Jan 95 18:19:22 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSxwT-00038CC; Fri, 13 Jan 95 18:10 PST
To: pine-info@cac.washington.edu
From: jmcging@access3.digex.net (John McGing)
Subject: Re: pine to cc:Mail
Date: 13 Jan 1995 19:17:03 -0500
Message-Id: <jmcging.790042329@access3>
References: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu> <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu>

Judd Deaver <jdeaver@u.washington.edu> writes:

>Does cc:mail include a uudecoding function standard? I tried just reading 
>the ascii version of the file into the body but it reformatted the text 
>and made it worthless. 

>On Thu, 12 Jan 1995, David L Miller wrote:

>> 
>> Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
>> good cc:Mail<->Internet gateway should be able to translate between MIME
>> and cc:Mail attachments, but unfortunately many do not...
>> 
>> You may be able to get the file through by uuencoding it and including
>> the uuencoded text into the body of a message using ^R. 
>> 
>> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
>> 
>> On Thu, 12 Jan 1995, Judd Deaver wrote:
>> 
>> > Date: Thu, 12 JAN 1995 10:57:35 -0800 
>> > From: Judd Deaver <jdeaver@u.washington.edu>
>> > Newgroups: comp.groupware.lotus-notes.misc, comp.mail.pine,
>> >     comp.mail.multi-media, comp.mail.misc, comp.mail.mime
>> > Subject: pine to cc:Mail 
>> > 
>> > I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
>> > network. I sent a Binary attachment but it did not seem to make it. Could 
>> > this be because his network does not support MIME or because the way pine 
>> > attaches files is different then cc:mail? If it is because they don't 
>> > supprt MIME would an ASCII file attachment make it down or does pine 
>> > automatically MIME encrypt all attachments?
>> > 
>> > Any help is GREATLY appreciated (this is an important file) could you 
>> > please reply via e-mail though to jdeaver@u.washington.edu
>> > 
>> > Thank You.
>> > 
>> > 
>> 


Sorry for the long quoting, but I couldn't figure out what wasn't important.

I sent myself a cc:Mail to internet message a few hours ago.  The attached
file was a wordperfect file.  Pine got it and the note attached to the
message from the cc:Mail gateway told me it had uuencoded the 
attachment.  I've sent many things via Pine to my office and found that 
zip files were recognized and handled by cc:Mail properly but everything 
else comes out MIMEd.

When I was using elm, I often sent uuencoded files to my office and they 
were converted (uudecoded) into zip files when they landed in my cc:Mail box.

John

-- 
------------------------------------------------------------------
jmcging@access.digex.net   Nobody knows the troubles I've seen
J.MCGING on GEnie              .... and nobody cares!
70142,1357 on Compuserve                              Team OS/2


From owner-pine-info@cac.washington.edu  Fri Jan 13 18:35:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11439;
	Fri, 13 Jan 95 18:35:52 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00927;
	Fri, 13 Jan 95 18:33:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00921;
	Fri, 13 Jan 95 18:33:19 -0800
Received: by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17627;
	Fri, 13 Jan 95 18:33:18 -0800
Date: Fri, 13 Jan 1995 18:33:18 -0800 (PST)
From: Radney Jasmin <rmjasmin@cac.washington.edu>
To: pine-info@cac.washington.edu
Subject: Mac-Pine
Message-Id: <Pine.ULT.3.91a.950113183158.13334E-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Are there any plans to port Pine over to the Mac?  Do you know of any 
programs out there ala Pine for the Mac?

Thanks,

Radney Jasmin
----------------------------------------------------------------------------
Networks and Distributed Computing     Internet: rmjasmin@cac.washington.edu
University of Washington               Phone:    (206) 543-5128
4545 15th. Avenue N.E. JE-20           Fax:      (206) 685-4044
Seattle, WA  98105                     
----------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Fri Jan 13 19:11:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12492;
	Fri, 13 Jan 95 19:11:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04866;
	Fri, 13 Jan 95 18:57:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04860;
	Fri, 13 Jan 95 18:56:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSyUo-00038JC; Fri, 13 Jan 95 18:45 PST
To: pine-info@cac.washington.edu
From: Nancy McGough <nancym@ii.com>
Subject: Filtering Mail FAQ
Date: 13 Jan 1995 18:22:27 GMT
Message-Id: <mail/filtering-faq_790020960@rtfm.mit.edu>

Archive-name: mail/filtering-faq
Posting-frequency: approximately monthly
Last-modified: 17 November 1994


            _____________________________________________________
  _________|                                                     |_________
  \        |                                                     |        /
   \       |                  FILTERING MAIL FAQ                 |       /
    \      |                                                     |      /
     \     |                                                     |     /
     /     |           Copyright (c) 1994 Nancy McGough          |     \
    /      |                                                     |      \
   /       |_____________________________________________________|       \
  /____________)                                              (___________\



  TABLE OF CONTENTS

   0.0 About this Article
   ... 0.1 Copyright Notice
   ... 0.2 Acknowledgements
   ... 0.3 Terminology and Notation
   ... 0.4 Getting the Latest Version of This Article
   ... 0.5 Reading the Hypertext Version of This Article
   ... 0.6 Reading the Plain Text Version of This Article
   1.0 Naming Your Incoming Mail Folders
   2.0 Procmail
   ... 2.1 Setting Up Procmail
   ... 2.2 Tracking Your Incoming Mail
   ... 2.3 Explanation of Test Recipe
   ... 2.4 Troubleshooting: Alternate .forward Files for Procmail
   ... 2.5 Procmail References
   3.0 Filter
   ... 3.1 Setting up Filter
   ... 3.2 Tracking Your Incoming Mail
   ... 3.3 Filter References
   4.0 Reading Incoming Mail Folders
   5.0 Contributing to this FAQ

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

Date: 17 Nov 1994 23:00:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 0.0 About this Article

Q: How can I have my incoming mail messages automatically put into an 
   appropriate folder?

This is one of the most frequently asked questions about email.  This article 
is the first release of an FAQ that addresses this question.  This version 
gives basic instructions for how to set up either procmail or Elm's filter 
to filter incoming mailing list messages.  Future versions of this FAQ will 
include instructions for doing other things like automatically replying to 
certain messages.

If your system has both procmail and filter installed then you should use 
procmail which is *much* more robust and powerful than filter.  This 
recommendation is almost universal; even the Elm and filter developers
recommend procmail over filter.

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

Date: 17 Nov 1994 23:00:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.1 Copyright Notice

Copyright (c) 1994 by Nancy McGough.  No portion of this work may be sold or 
put to commercial use without express written consent of the author.  This 
restriction covers publication in any form, or distribution by any method, 
which permits this work to be visually perceived, either directly or with the 
aid of any machine or device. Permission is granted to republish or 
redistribute this article in its entirety for noncommercial use if this 
copyright notice is not removed or altered.

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

Date: 17 Nov 1994 23:00:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.2 Acknowledgements

Thanks to these people who sent suggestions:
   David L. Miller <dlm@cac.washington.edu>
   Cookie Monster <kmanley@bits.fc.hp.com>
   Jim Showalter <gamma@mintaka.disa.mil>
   David W. Tamkin <dattier@mcs.com>
   Rick Troxel <rick@helix.nih.gov>
   Stephen R. van den Berg <berg@pool.informatik.rwth-aachen.de>
   Syd Weinstein <syd@dsinc.myxa.com>

Special thanks to:
   Thomas A. Fine <fine@cis.ohio-state.edu> for setting up and
   maintaining the hypertext archive of FAQs.  Congratulations
   to him for winning O'Reilly and Associates' "The Best of the
   Net" award!

Please let me know if I've left you, or anyone else, out of this list.

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

Date: 17 Nov 1994 23:00:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.3 Terminology and Notation

  Term    Meaning
  ====    =======
  FTP     File Transfer Protocol
  HTML    HyperText Markup Language
  HTTP    HyperText Transport Protocol
  mailer  Mail user agent (MUA) such as Pine or Elm
  pico    PIne COmposer - friendly editor that's part of the Pine package
  RFC     Internet "Request For Comments" document
  URL     Uniform Resource Locator (specified in RFC1630)
  ^x      Press the Ctrl key and then, while holding down the Ctrl key, 
          press the x key
  ~       Your home directory $HOME  (see * below)

* In this article I use ~ (tilde) to mean your home directory.  Note that 
  some shells, such as the Bourne shell (sh), do not understand the tilde 
  notation so you will need to use $HOME instead.  You can always get to 
  your home directory by typing ``cd''.

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

Date: 17 Nov 1994 23:00:40 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.4 Getting the Latest Version of This Article

If this article is over two months old then there is probably an updated
version of it in all the usual archives.  Please get the latest version
from one of these places:

World Wide Web (the nicest format for online reading!):
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html

Anonymous FTP:
ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/filtering-faq

Email:
Send mail to mail-server@rtfm.mit.edu containing the following:
    send usenet/news.answers/mail/filtering-faq

UUCP:
uunet!/archive/usenet/news.answers/mail/filtering-faq

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

Date: 17 Nov 1994 23:00:50 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.5 Reading the Hypertext Version of This Article

The best way to read this FAQ (and most other FAQs too) is to view the
hypertext version using a Web browser such as Lynx, Mosaic, Netscape, 
WinWeb, or Cello.  This will allow you to easily jump:
   * between subjects in this article
   * to a Uniform Resource Locator (URL)
   * to an Internet Request For Comments document (RFC)
   * to some manual pages

This, and all FAQs that are crossposted to news.answers, can be accessed 
through:  http://www.cis.ohio-state.edu/hypertext/faq/usenet/top.html

This particular FAQ is at:
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html

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

Date: 17 Nov 1994 23:00:60 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 0.6 Reading the Plain Text Version of This Article

If you are reading the plain text version (i.e., not the hypertext version) of 
this FAQ it is in RFC1153 digest format which means each subject is formatted 
as a mini mail message with its own Date, From, and Subject (and sometimes 
 Followup-To) headers.  Some newsreaders and mailers make it really easy
to jump to a subject in an article that is in digest format.  Here are 
instruction for some newsreaders:

* NN's default is to split a digest and present each digest item on the 
  menu.  If you have changed the default by putting ``set split off'' in 
  your ~/.nn/init file then you can split an article that is in digest 
  format by typing G% while viewing it.  This will present each digest item 
  on a submenu.  You can then read, followup-to, save, print, etc. individual 
  digest items.

* In trn (and its relatives like rn and strn) you can type ^g (Ctrl key 
  and g key pressed together) to skip to the next line that begins with
  "Subject: "

* In emacs GNUS, C-c C-n will skip to the next digest article (C-C C-p will
  go back to the previous digest article).


If your newsreader or mailer does not have a built-in command that allows
you to easily read a digest you can pipe the article to ``formail -ds''
which will split the article into separate mail messages, and then you can
use your mailer or newsreader (if it can read mail folders) to read the
folder.  For example, here's what you would do in Tin while viewing
the article:

Type...                           In order to...
-------                           --------------
|                                 Pipe
a                                 Specify the article is to be piped
formail -ds >> ~/mail/faq.split   Split the digest into individual
                                  messages and put them in a file named
                                  ~/mail/faq.split.  (Replace ~/mail
                                  with your folder directory.)
pine -if faq.split                Use Pine to read the newly created folder.

For more information see the formail(1) man pages.

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

Date: 17 Nov 1994 23:01:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 1.0 Naming Your Incoming Mail Folders

For my incoming mail folders I use names that start with ``IN''.
For example, I put mail sent to the procmail mailing list into a
folder named IN.procmail.  I do this so that when all my folders
are listed alphabetically the incoming folders are together and
near the top.  They are near the top because Unix is case sensitive
and upper case letters come before lower case letters in an ascii
sort.

Of course, you can use any names you like for your mail folders.

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

Date: 17 Nov 1994 23:02:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 2.0 Procmail

Procmail is a powerful mail processor that can be used to process your
mail messages either as they arrive or after they are in a mail folder.  
This version of the FAQ describes the basics of setting up procmail to
filter incoming mailing list messages.

To find out how to process existing mail folders see the NOTES section
of the procmail(1) man page.

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

Date: 17 Nov 1994 23:02:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.1 Setting Up Procmail

1] Find out if procmail is on your system and what the full path to it is.  
   If you are using csh type:

     which procmail

   Or if you are using sh or ksh type:

     type procmail

   If neither ``which'' nor ``type'' are on your system try ``whereis'' and
   ``where''.  If your system doesn't have procmail ask your system 
   administrator to install it.  If your sys admin isn't able to do this,
   use a different mail processor like deliver, mailagent, or filter 
   (described in part 2 of this FAQ).


2a] Create ~/.procmailrc.  (Note that throughout this article I use
    pico for editing files.  Replace ``pico'' with your editor.)

     cd
     pico .procmailrc

  
2b] Enter a modified version of the following in your ~/.procmailrc.
    Note that lines that begin with # are comments and are ignored by
    procmail.

     #Set on when debugging
     VERBOSE=off
 
     #Replace ``mail'' with your mail directory (Pine uses mail, Elm uses Mail)
     MAILDIR=$HOME/mail
     
     #Directory for storing procmail log and rc files
     PMDIR=$HOME/.procmail
     
     LOGFILE=$PMDIR/log
     INCLUDERC=$PMDIR/rc.test
     INCLUDERC=$PMDIR/rc.folders

3] Create the directory where you will store your procmail log and rc files 
   (this is $PMDIR that you set above).

     cd
     mkdir .procmail


4a] Create an rc (run commands) file for testing:

     cd
     cd .procmail
     pico rc.test


4b] Enter the following in ~/.procmail/rc.test:

      :0:
      * ^Subject: .*test
      IN.testing

    Note that the first line contains a zero (0), not the letter "oh".
    For now, don't worry about the meaning of this recipe.  It is
    explained in the subject "Explanation of Test Recipe" below.


5a] Create a ~/.forward file by typing the following. (Pico's -w flag tells 
    pico not to auto wrap lines.)

     cd
     pico -w .forward



5b] Enter a modified version of the following in your ~/.forward:


     "|IFS=' ' && exec /usr/local/bin/procmail -f- || exit 75 #nancym"


    == IMPORTANT NOTES ==
    * Make sure you include all the quotes, both double (") and single (').
    * The vertical bar (|) is a pipe.
    * Replace /usr/local/bin with the correct path for procmail (see step 1).
    * Replace ``nancym'' with your userid.  You need to put your userid in 
      your .forward so that it will be different than any other .forward file 
      on your system.
   
    * Do NOT use environment variables, like $HOME, in your .forward file.
    * Do NOT expect ~ to mean your home directory in the .forward file: If 
      procmail resides below your home directory write out the *full* path.


5c] Note that on many systems you need to make your .forward world 
    readable and your home directory world searchable in order for the
    mail transport agent to "see" it.  To do this type:
   
      cd
      chmod 644 .forward
      chmod a+x .


6] Send yourself two test messages: one with ``test'' in the subject
   and one without ``test'' in the subject.


7a] Start your mailer (pine, elm, etc.) and check that the messages
    were delivered correctly.  The one with ``test'' in the subject
    should be in the folder $MAILDIR/IN.testing and the one without 
    ``test'' in the subject should be in your inbox.  If these were
    delivered correctly go on to step 8.


7b] TROUBLESHOOTING
    * If the two messages were not delivered correctly look at your
      $LOGFILE (~/.procmail/log) to see if you can determine what
      the problem is.  

    * Check these three files for typos:
        ~/.forward
        ~/.procmailrc
        ~/.procmail/rc.test

    * Check the file and directory permissions of your .forward (set in 
      5c above).

      Type...          In order to...
      -------          --------------
      cd               Go to your home directory.
      
      ls -l .forward   Check the permission: it should say -rw-r--r--
      
      ls -ld .         Check permission of home dir: it should say drwx?-x?-x
                       The ?'s may be r's or hyphens or one of each (i.e.,
                       drwx--x--x, drwxr-xr-x, drwxr-x--x, drwx--xr-x).
      

    * If none of these turn up the problem edit your ~/.procmailrc so
      that it contains:

        VERBOSE=on

      And repeat steps 6 and 7.  If you are still having problems see the 
      subject "Troubleshooting: Alternate .forward Files for Procmail" below.

   
8a] Once you have successfully tested procmail in steps 6 and 7, create 
     rc.folders for filtering incoming messages into mail folders.
  
      cd
      cd .procmail
      pico rc.folders


8b] Enter a modified version of the following in ~/.procmail/rc.folders

     :0:
     * ^TOwww-talk
     IN.www-talk

     :0:
     * ^TOprocmail
     IN.procmail
     
     The first recipe filters the www-talk mailing list and the second recipe
     filters the procmail mailing lists  The meaning of the first recipe is 
     as follows:

     Notation      Meaning
     ========      =======
     :0            Begin a recipe
       :           Use a lock file
     *             Begin a condition 
       ^TO         Match ``To:'' ``Cc:'' or other synonyms for To at the
                   beginning of a line, followed by any or no characters,
                   followed by....
          www-talk  ``www-talk''
     IN.www-talk   If successful match, put in folder $MAILDIR/IN.www-talk

  
     Create a recipe for each of your mailing lists.  Make sure that you
     use ``^TO'' with no space between the caret (^) and the word ``TO'', 
     and that both letters are capitalized -- if you don't it won't work.

     Note that ^TO is not a normal regular expression.  It is a special
     procmail expression that is designed to catch any destination 
     specification.  See the MISCELLANEOUS section of the procmailrc(5)
     man page for details.  For examples, see procmailex(5) man page.
     

9]  Repeat steps 6 and 7 to make sure that things are still working.


10]  Comment out the rc.test line in you .procmailrc file so that it looks 
     like this:
          
       VERBOSE=off
       MAILDIR=$HOME/mail
       PMDIR=$HOME/.procmail
       LOGFILE=$PMDIR/log
       # INCLUDERC=$PMDIR/rc.test
       INCLUDERC=$PMDIR/rc.folders

     Note that it's useful to leave the rc.test line there for future testing.

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

Date: 17 Nov 1994 23:02:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.2 Tracking Your Incoming Mail

There is a useful script, which is part of the procmail package, for 
checking your procmail log file called mailstat.  Check to see if it is 
on your system by typing either ``which mailstat'' or ``type mailstat''.  
If it's on your system type:

  mailstat $HOME/.procmail/log

This displays a concise version of your log file and moves your log 
file to log.old.  You may want to put the above line in your .login so that 
each time you log in you will see a listing of how many messages you've
received since the last time you ran mailstat, and what folders these
messages were delivered to.

You can get a mailstat listing of log.old by using the -o flag:

  mailstat -o $HOME/.procmail/log


If mailstat is not on your system ask your system administrator to
install it.  It is located with all the other procmail tools at:

ftp://ftp.informatik.rwth-aachen.de/pub/packages/procmail/procmail.tar.gz

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

Date: 17 Nov 1994 23:02:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.3 Explanation of Test Recipe

The recipe we used for testing is:

:0:
* ^Subject: .*test
IN.testing


The meaning of this recipe is:

Notation            Meaning
========            =======
:0                  Begin a recipe
  :                 Use a lock file
*                   Begin a condition 
  ^                 Match the beginning of a line followed by....
   Subject:         ``Subject:'' followed by....
            .       a space followed by any character (.) followed by....
             *      0 or more of preceding character (any character in this 
                       case) followed by....
              test  ``test''
IN.testing          If successful match, put in folder $MAILDIR/IN.testing

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

Date: 17 Nov 1994 23:02:40 GMT
From: "Stephen R. van den Berg" <berg@pool.informatik.rwth-aachen.de>
Subject: ... 2.4 Troubleshooting: Alternate .forward Files for Procmail

If the .forward template in 5b above doesn't work the following alternatives 
might be helpful:

In a perfect world:
	"|exec /usr/local/bin/procmail #nancym"
In an almost perfect world:
	"|exec /usr/local/bin/procmail USER=nancym"
In another world:
	"|IFS=' ';exec /usr/local/bin/procmail #nancym"
In a different world:
	"|IFS=' ';exec /usr/local/bin/procmail USER=nancym"
In a smrsh world:
	"|/usr/local/bin/procmail #nancym"

These formats can be tried in different combinations, the leading "| can
be tried as |" instead, or vice versa.

Some systems do not need a .forward file (i.e., having a .procmailrc file 
suffices if procmail already is the local delivery agent).

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

Date: 17 Nov 1994 23:02:50 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 2.5 Procmail References

Manuals:   procmail(1)   - autonomous mail processor
           procmailrc(5) - procmail rc file
           procmailex(5) - procmail rc file examples
           procmailsc(5) - procmail weighted scoring techique
           egrep(1)      - search file for regular expression (procmail uses
                           egrep-style regular exprssions along with some of 
                           its own expressions like ^TO)
           formail(1)    - mail reformatter
           sendmail(8)   - send mail over the internet
Newsgroup: comp.mail.misc
Mailing List: procmail@informatik.rwth-aachen.de
           Subscribe to the procmail mailing list by sending mail:
             To: procmail-request@informatik.rwth-aachen.de 
             Subject: subscribe

Procmail Archives:
           Get a list of files available at the procmail mail server by 
           sending mail:
             To: procmail-request@informatik.rwth-aachen.de 
             Subject: archive ls

           Get Best of the Procmail mailing list by sending mail (you'll 
           need gzip and a MIME-decoder to unpack it):
             To: procmail-request@informatik.rwth-aachen.de 
             Subject: archive get best_of_procmail_list*

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

Date: 17 Nov 1994 23:03:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 3.0 Filter

Filter is part of the Elm package of tools.  Note that you can use filter
to filter your incoming mail even if you are not using Elm to read your mail.

IMPORTANT NOTE
==============
If your system has both procmail and filter installed then you should use 
procmail which is *much* more robust and powerful than filter.  This 
recommendation is almost universal; even the developers of Elm and Filter
recommend procmail over filter.  IT IS POSSIBLE TO LOSE MAIL MESSAGES
WHEN USING FILTER; this is rare but it has happened.

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

Date: 17 Nov 1994 23:03:10 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 3.1 Setting up Filter
Followup-To: comp.mail.elm

1] Find out if filter is on your system and what the full path to it is.  
   If you are using the C shell (csh) type:

     which filter

   Or, if you are using the Korn shell (ksh) or the Bourne shell (sh) type:

     type filter

   If neither ``which'' nor ``type'' are on your system try ``where'' and
   ``whereis''.  If your system doesn't have filter ask your system 
   administrator to install it; or even better ask her to install procmail.


2] Note the full path of your home directory by typing:

     cd
     pwd


3a] Create ~/.elm/filter-rules.  (Note that throughout this article I use
    pico for editing files.  Replace ``pico'' with your editor.)

     cd
     mkdir .elm
     cd .elm
     pico filter-rules

  
3b] Enter a modified version of the following in your ~/.elm/filter-rules

     if (subject contains "test") then save "/j/nancym/Mail/IN.testing"
   
   Replace /j/nancym with your home directory path (see step 2).
   Replace /Mail with the name of the directory where your mail folders are
   stored.  Pine and Berkeley Mail use /mail (lower case m) and Elm uses 
   /Mail (upper case M).
   

4] To see what the filter rule will do type the following at your Unix 
   prompt:  

     filter -r


5a] Create a ~/.forward file by typing the following. (Pico's -w flag tells 
    pico not to auto wrap lines.)

      cd
      pico -w .forward


5b] Enter a modified version of the following in your ~/.forward:


     "|/usr/local/bin/filter -o /j/nancym/.elm/filter-errors"


    == IMPORTANT NOTES ==
    * Make sure you include the quotes (").
    * The vertical bar (|) is a pipe.
    * Replace /usr/local/bin with the correct path for filter (see step 1).
    * Replace /j/nancym with your home directory (see step 2).
   
    * Do NOT expect environment variables, like $HOME, to work in your 
      .forward file.
    * Do NOT expect ~ to mean your home directory in the .forward file.


5c] Note that on many systems you need to make your .forward is world 
    readable and your home directory world searchable in order for the
    mail transport agent to "see" it.  To do this type:
   
      cd
      chmod 644 .forward
      chmod a+x .


6] Send yourself two test messages: one with ``test'' in the subject
   and one without ``test'' in the subject.


7a] Start your mailer (pine, elm, etc.) and check that the messages
    were delivered correctly.  The one with ``test'' in the subject
    should be in the folder IN.testing and the one without ``test'' 
    in the subject should be in your inbox.  If these were delivered 
    correctly go on to step 8.


7b] TROUBLESHOOTING
    * If the two messages were not delivered correctly look at your
      ~/.elm/filter-errors to see if you can determine what the problem 
      is.  

    * Check these two files for typos:
        ~/.forward
        ~/.elm/filter-rules

    * Check the file and directory permissions of your .forward (set in 
      5c above).

      Type...          In order to...
      -------          --------------
      cd               Go to your home directory.
      
      ls -l .forward   Check the permission: it should say -rw-r--r--
      
      ls -ld .         Check permission of home dir: it should say drwx?-x?-x
                       The ?'s may be r's or hyphens or one of each (i.e.,
                       drwx--x--x, drwxr-xr-x, drwxr-x--x, drwx--xr-x).
      

    * If none of these turn up the problem edit your ~/.forward so
      that filter will be verbose with it's output (use the -vo flag).

        "|/usr/local/bin/filter -vo /j/nancym/.elm/filter-errors"

      And repeat steps 6 and 7.  After you get filter to work you 
      will probably want to change the ``-vo'' flag back to ``-o''.

   
8]  After you have successfully tested filter in steps 6 and 7, edit
    ~/.elm/filter-rules so that it contains a modified version of the
    following:

     # if (subject contains "test") then save "/j/nancym/Mail/IN.testing"
     if (to contains "www-talk") then save "/j/nancym/Mail/IN.www-talk"
     if (to contains "hopos-l") then save "/j/nancym/Mail/IN.hopos"

     Replace /j/nancym with your home directory path and
     /Mail with the name of your mail directory.  Replace the mailing 
     list string (e.g., "www-talk") and the name of the mail folder
     (e.g., IN.www-talk) with text for your mailing lists.

     Note that ``to contains...'' means either the To or Cc header contains...

     Rather than deleting the test line, it's useful to just turn it
     into a comment (by preceding it with #) so that you can easily
     use it for future testing.

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

Date: 17 Nov 1994 23:03:20 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 3.2 Tracking Your Incoming Mail
Followup-To: comp.mail.elm

You can get a short summary of filter's activity by typing:

    filter -s

For a longer summary type:

    filter -S

Or you can look at the log file itself, ~/.elm/filterlog.

You should regularly look at ~/.elm/filter-errors to make sure things 
are working.  You can automatically check filter-errors each time you
log in by putting the following in your .login:

    tail ~/.elm/filter-errors

Also you probably want to regularly delete filterlog and filter-errors so 
they don't fill up your disk space.  To get a summary of the filter log and 
clear it type:

    filter -cs

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

Date: 17 Nov 1994 23:03:30 GMT
From: Nancy McGough <nancym@ii.com>
Subject: ... 3.3 Filter References
Followup-To: comp.mail.elm

Web Page:  http://www.myxa.com/elm.html
FAQs:      http://www.cis.ohio-state.edu/hypertext/faq/usenet/elm/top.html
Manual:    filter(1)
Newsgroup: comp.mail.elm

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

Date: 17 Nov 1994 23:04:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 4.0 Reading Incoming Mail Folders

To read an incoming mail folder use your mailer or newsreader (if it
can read mail folders).  For more information see documentation for your 
mailer or newsreader.  Here are some pointers.

PINE
====
FAQ:       http://www.cac.washington.edu/pine/faq/
           ftp://ftp.cac.washington.edu/pine/docs/faq
Manual:    pine(1)
Newsgroup: comp.mail.pine (linked to Pine mailing list)
Mailing List: pine-info@cac.washington.edu (linked to Pine newsgroup)
           Subscribe to the pine-info mailing list by sending mail to:
                     majordomo@cac.washington.edu
           With...
                     subscribe pine-info
           in the body of the message.


ELM
===
Web Page:  http://www.myxa.com/elm.html
FAQs:      http://www.cis.ohio-state.edu/hypertext/faq/usenet/elm/top.html
Manual:    elm(1)
Newsgroup: comp.mail.elm


Emacs Mail Mode
===============
Newsgroups: gnus.emacs.help and comp.emacs
http://www.cis.ohio-state.edu/hypertext/faq/usenet/GNU-Emacs-FAQ/part5/faq.html    

MH
==
FAQ:       http://www.cis.ohio-state.edu/hypertext/faq/usenet/mh-faq/top.html
Manual:    mh(1)
Newsgroup: comp.mail.mh


MAIL
====
Manual:    mail(1)
Newsgroup: comp.mail.misc


NN
==
FAQ:       http://www.cis.ohio-state.edu/hypertext/faq/usenet/nn-faq/top.html
Manual:    nn(1)
Newsgroup: news.software.nn

(Does anyone know if nn uses lock files?  Is there any problem using nn
to read a mail folder that is receiving mail?  Please let me know!)

(Also, please let me know what other newsreaders can read mail folders?)

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

Date: 17 Nov 1994 23:05:00 GMT
From: Nancy McGough <nancym@ii.com>
Subject: 5.0 Contributing to this FAQ

If you have any corrections, suggestions, or new digest items to contribute
to this FAQ please send them to me at nancym@ii.com.  If you are reading this
with a viewer that understands the following URL you can use it to send me 
mail:   mailto:nancym@ii.com

Between official releases of this FAQ the plain text (ascii) version of
the most up to date version of it is at:

   ftp://ftp.halcyon.com/pub/ii/Internet/filtering_mail_faq


End of Filtering Mail Digest
****************************

-- 
 /\_/\
( o.o )   Nancy McGough       http://www.jazzie.com/ii/
 > ^ <    Infinite Ink        ftp://ftp.halcyon.com/pub/ii


From owner-pine-info@cac.washington.edu  Fri Jan 13 20:16:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13977;
	Fri, 13 Jan 95 20:16:08 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02361;
	Fri, 13 Jan 95 20:12:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02355;
	Fri, 13 Jan 95 20:12:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rSzfH-00038CC; Fri, 13 Jan 95 20:00 PST
To: pine-info@cac.washington.edu
From: dorsett@treasure.coastalnet.com (Stephen Dorsett)
Subject: running pine in chroot on SunOS
Date: 13 Jan 1995 15:09:12 -0500
Message-Id: <3f6ml8$g2c@abaco.coastalnet.com>


I am trying to use pine 3.89 as the mail tool of choice for users
on my SunOs 4.1.3 system.

We have set up a "chroot" environment, and pine does not want to 
acknowledge the existence of mail, not will it send it when run in the 
"chroot'ed" environment.

/bin/mail and /usr/ucb/mail are quite happy in the chroot environment, 
and pine runs fine when run as a 'trusted' user. (outside the chroot)

Any suggestions ?


-- 
========================================================================
Stephen Dorsett                            dorsett.giex@coastalnet.com  
Wide Area Network Manager, GIEx Corp.      1-800-514-5NET   
========================================================================


From owner-pine-info@cac.washington.edu  Fri Jan 13 20:49:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14752;
	Fri, 13 Jan 95 20:49:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06293;
	Fri, 13 Jan 95 20:45:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06287;
	Fri, 13 Jan 95 20:45:44 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14757;
	Fri, 13 Jan 95 20:45:43 -0800
Date: Fri, 13 Jan 1995 20:45:42 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Radney Jasmin <rmjasmin@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Mac-Pine
In-Reply-To: <Pine.ULT.3.91a.950113183158.13334E-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.ULT.3.92.950113204323.14820P-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Radney,
See ftp://ftp.cac.washington.edu/mail/imap.software for a list of all 
known IMAP clients.  

We do not currently have funding for a Mac version of Pine, but who knows 
what the future might bring...

-teg

p.s. You can always run MachTen's Unix emulator on your Mac; there is a 
port of Pine for that!

On Fri, 13 Jan 1995, Radney Jasmin wrote:

> 
> Are there any plans to port Pine over to the Mac?  Do you know of any 
> programs out there ala Pine for the Mac?
> 
> Thanks,
> 
> Radney Jasmin
> ----------------------------------------------------------------------------
> Networks and Distributed Computing     Internet: rmjasmin@cac.washington.edu
> University of Washington               Phone:    (206) 543-5128
> 4545 15th. Avenue N.E. JE-20           Fax:      (206) 685-4044
> Seattle, WA  98105                     
> ----------------------------------------------------------------------------
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan 13 21:14:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15204;
	Fri, 13 Jan 95 21:14:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03022;
	Fri, 13 Jan 95 21:10:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mote.Berkeley.EDU by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03016;
	Fri, 13 Jan 95 21:10:45 -0800
Received: by mote.Berkeley.EDU (5.57/1.28)
	id AA26225; Fri, 13 Jan 95 21:10:44 -0800
Date: Fri, 13 Jan 1995 21:10:44 -0800 (PST)
From: Eric Mockensturm <eric@mote.Berkeley.EDU>
Subject: Re: Mac-Pine
To: Radney Jasmin <rmjasmin@cac.washington.edu>
Cc: pine-info@cac.washington.edu
In-Reply-To: <Pine.ULT.3.91a.950113183158.13334E-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.3.89.9501132139.A26082-0100000@mote.Berkeley.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'd recommend using Eudora.  There are both shareware and commercial 
versions of this.  You need a POP3 server on your unix box to serve the 
mail to the mac.  One nice thing about the commercial version on Eudora 
is that it will filter mail for you.

Take a look at Qualcomm's home page for info (http://www.qualcomm.com/).

You can find the shareware version on most big mac archives.  I'd suggest

ftp://ftp.hawaii.edu/mirrors/info-mac/comm/tcp/mail/eudora-151.hqx

On Fri, 13 Jan 1995, Radney Jasmin wrote:

> 
> Are there any plans to port Pine over to the Mac?  Do you know of any 
> programs out there ala Pine for the Mac?
> 
> Thanks,
> 
> Radney Jasmin
> ----------------------------------------------------------------------------
> Networks and Distributed Computing     Internet: rmjasmin@cac.washington.edu
> University of Washington               Phone:    (206) 543-5128
> 4545 15th. Avenue N.E. JE-20           Fax:      (206) 685-4044
> Seattle, WA  98105                     
> ----------------------------------------------------------------------------
> 

Eric Mockensturm

Dynamic Stability Lab
1113 Etcheverry Hall
University of California - Berkeley
(510) 642-6371



From owner-pine-info@cac.washington.edu  Fri Jan 13 22:01:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16148;
	Fri, 13 Jan 95 22:01:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07112;
	Fri, 13 Jan 95 21:57:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07106;
	Fri, 13 Jan 95 21:57:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT1J1-00038CC; Fri, 13 Jan 95 21:45 PST
To: pine-info@cac.washington.edu
From: "Juan M. Courcoul" <courcoul@campus.qro.itesm.mx>
Subject: Re: Setting up for news, upgrading pine systemwide.
Date: Fri, 13 Jan 1995 14:27:44 -0600
Message-Id: <Pine.SOL.3.91.950113141301.20677A-100000@campus.qro.itesm.mx>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.92.950106132601.2851P-100000@shiva1.cac.washington.edu> 

On Fri, 6 Jan 1995, David L Miller wrote:

> FWIW, if you set
> 	
> 	nntp-server=$NNTPSERVER
> 
> and leave news-collections blank, Pine 3.91 will assume a default
> news-collection.  Note that the "News/[]" in your example above is only
> the nickname for the collection and does not have any other significance. 

This brings to light a configuration problem I am having regarding local 
news access. Most of my users on this host would like to peruse the news, 
available on the locally-installed INN server. 

First, I tried setting the 'nntp-server' variable in 
/usr/local/lib/pine.conf.fixed, and discovered that this did not set up 
the default news folder. I then switched it to the 
/usr/local/lib/pine.conf, and then discovered that the 'news-collections' 
had been set by default to <No Value Set: using 
*{campus.qro.itesm.mx/nntp}[]> 

Since I want them to do a local access (and save a few cycles on the 
nnrpd), I tried setting 'news-collections' to "News *[]". Unfortunately, 
this doesn't work: none of the [previously configured] groups on the 
.newsrc files are seen and when you try to subscribe and request to go to 
all groups, it says there are no groups to select from ! Is there a 
confirmed way to do local access, instead of having to go thru the nnrp ?
BTW, the local news server's directory hierarcy is located on /news, with 
a symlink in /var/spool/news pointing to it.

Thanks for your help.

Juan Courcoul
Instituto Tecnologico de Monterrey
Campus Queretaro




From owner-pine-info@cac.washington.edu  Fri Jan 13 23:30:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17711;
	Fri, 13 Jan 95 23:30:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08138;
	Fri, 13 Jan 95 23:24:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08132;
	Fri, 13 Jan 95 23:24:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT2hu-00038CC; Fri, 13 Jan 95 23:15 PST
To: pine-info@cac.washington.edu
From: vbhalla@mtu.edu (Vbhalla)
Subject: Re: JOE 2.5
Date: 13 Jan 1995 14:46:39 -0500
Message-Id: <3f6lav$jh7@pacemaker.cts>
References: <D224M0.HAo@world.std.com> <D238Is.8vG@world.std.com> <3eteuf$1jk@apakabar.cc.columbia.edu>

Yeechang Lee (ycl6@namaste.cc.columbia.edu) wrote:
: Joseph H Allen <jhallen@world.std.com> says:
: |Please wait for version 2.5 to appear.  Version 2.4 has a minor bug which
: |prevents you from creating new files.
: 
: Well, I have 2.5 up and running, and it's nice!  (I'm surprised the man
: page doesn't mention JOETERM, though.)  I can't really say I've noticed
: much of a difference, but I'm sure it's all there.  More kudos to Joe
: and JOE!
: 
: And for you comp.mail.pine folk who have been looking for a nice,
: easy-to-use editor that doesn't have Pico's clunks, check out JOE--it
: fits the bill!

I am not sure if you know it or not but joe2.6 is now awailable on  ftp.std.com.
in dir /src/editors as file joe2.6.tar.Z

Take a look if you like it or not.
--
                                                vbhalla@mtu.edu
/***********************************************************************/
Just Call me Swifty Yar!!!              http://pace1.cts:8080/MyHome.html
C.T.S Consultant. 			http://pace1.cts:8080/Consul.html
Intl. Students Association. 		http://pace1.cts:8080/Intl.html
      President.				
/***********************************************************************/
 


From owner-pine-info@cac.washington.edu  Sat Jan 14 01:42:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20680;
	Sat, 14 Jan 95 01:42:35 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09913;
	Sat, 14 Jan 95 01:38:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.wesleyan.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09902;
	Sat, 14 Jan 95 01:38:54 -0800
Received: from [129.133.76.45] (jrvincent.buttc.wesleyan.edu)
 by MAIL.WESLEYAN.EDU (PMDF V4.3-10 #5526)
 id <01HLTO9VENF40008UM@MAIL.WESLEYAN.EDU>; Sat,
 14 Jan 1995 04:38:52 -0400 (EDT)
Date: Sat, 14 Jan 1995 04:39:53 -0500
From: jrvincent@MAIL.WESLEYAN.EDU (Jesse R  Vincent)
Subject: pine/vmsbuild.com
X-Sender: jrvincent@mail.wesleyan.edu
To: pine-info@cac.washington.edu
Message-Id: <v02110103ab3d4c428183@[129.133.76.45]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7BIT

hello..i was very happily suprised to find that pine had been fully
compiled to run under vms...there were only minor hitches until time came
to execute the vmsbuild.com in the /pine subdirectory (the one for building
the pine executable itself)  The problem was that this file did not appear
to be included in the tar file....any pointers as to its whereabouts would
make me very happy...
        thanks,
        jesse

---------------------------------------------------------------
Jesse Vincent--Voice:203/685-4955--Email:jrvincent@wesleyan.edu
Box 5433--Wesleyan Station--222 Church St--Middletown, CT 06459
http://www.con.wesleyan.edu/~jesse/jesse.html-------Being Built
---------------------------------------------------------------
bits/keyID    User ID                     (PGP Public Key Info)
1024/4B0085E9 Jesse R. Vincent <jrvincent@wesleyan.edu>
Key fingerprint:74 C4 D3 B8 7F B3 A6 02 04 0F 22 B3 E2 57 8E 5F
---------------------------------------------------------------




From owner-pine-info@cac.washington.edu  Sat Jan 14 01:43:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20709;
	Sat, 14 Jan 95 01:43:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09926;
	Sat, 14 Jan 95 01:39:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09918;
	Sat, 14 Jan 95 01:39:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT4lN-00038CC; Sat, 14 Jan 95 01:27 PST
To: pine-info@cac.washington.edu
From: openway@CERF.NET (LIOCS Corporation)
Subject: Segmenting mail attachments
Date: 13 Jan 1995 13:24:46 -0800
Message-Id: <3f6r2u$2oh@nic.cerf.net>

Can someone provide insight into how I can segment mail attachments into
multiple parts?  My users want to be able to send mail messages which 
can be quite large 30-900k and my SMTP mailer(ultrix) seems to strip
off after 32 k.

Thanks for your help
dave@liocs.com



From owner-pine-info@cac.washington.edu  Sat Jan 14 03:53:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23025;
	Sat, 14 Jan 95 03:53:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07782;
	Sat, 14 Jan 95 03:48:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07776;
	Sat, 14 Jan 95 03:48:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT6qO-00038JC; Sat, 14 Jan 95 03:40 PST
To: pine-info@cac.washington.edu
From: fjv@insas.po.my (John Vogelsang)
Subject: Re: pine to cc:Mail
Date: 14 Jan 1995 04:20:02 GMT
Message-Id: <3f7jdi$po@jaring.my>
References: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu> <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu>

In article <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu>, Judd Deaver <jdeaver@u.washington.edu> says:
>
>Does cc:mail include a uudecoding function standard? I tried just reading 
>the ascii version of the file into the body but it reformatted the text 
>and made it worthless. 
>

As far as I know cc:Mail itself does not handle encoding/decoding. Lotus 
Link to UUCP does handle MIME / uuencoded attachments properly. 
I.e. Send a MIME message from internet through UUCPLink to cc:Mail and
the received mail will have an attachment.

On Thu, 12 Jan 1995, David L Miller wrote:

> 
> Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
> good cc:Mail<->Internet gateway should be able to translate between MIME
> and cc:Mail attachments, but unfortunately many do not...
>

Could somebody provide an example of "A good cc:Mail<->Internet 
gateway" or is this just a hypothetical entity.


Thanks, John Vogelsang.

--
GeneSys Software Sdn. Bhd.
----------------------------------------------------------------
                                        145A, Jalan Maharajalela 
Tel:  +(603) 242 0411                   50150 Kuala Lumpur  
Fax:  +(603) 248 0503                   Malaysia


From owner-pine-info@cac.washington.edu  Sat Jan 14 04:13:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23986;
	Sat, 14 Jan 95 04:13:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11809;
	Sat, 14 Jan 95 04:10:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11803;
	Sat, 14 Jan 95 04:10:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT79r-00038CC; Sat, 14 Jan 95 04:00 PST
To: pine-info@cac.washington.edu
From: mr_ski@prairienet.org (Mitch Duszynski)
Subject: Timeout and K-Block
Date: 14 Jan 1995 12:00:29 GMT
Message-Id: <3f8ect$dgo@vixen.cso.uiuc.edu>

Out of curiosity, I was wondering what would happen if you have activated 
to K-Block feature of PINE, and before you return to exit it, your 
connection is lost?  WIll it reset the K-BLOCK or lock it up?  Or will 
you just need to re-enter your password the next time you enter PINE?

--
Mayor Ski, sysop of SUBURBIA! BBS   217-337-6312
(A backroad just off the information Super Highway!)


From owner-pine-info@cac.washington.edu  Sat Jan 14 05:20:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25253;
	Sat, 14 Jan 95 05:20:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08984;
	Sat, 14 Jan 95 05:14:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08978;
	Sat, 14 Jan 95 05:14:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT8AC-00038CC; Sat, 14 Jan 95 05:05 PST
To: pine-info@cac.washington.edu
From: wieruc@eng.auburn.edu (Weiru Chen)
Subject: Re: Signature and Finger FAQ
Message-Id: <D2DLGM.MqE@mail.auburn.edu>
References: <3cqchl$3uj@news.halcyon.com>
Date: Sat, 14 Jan 1995 03:24:21 GMT





From owner-pine-info@cac.washington.edu  Sat Jan 14 05:37:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25594;
	Sat, 14 Jan 95 05:37:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12681;
	Sat, 14 Jan 95 05:25:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12675;
	Sat, 14 Jan 95 05:25:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT8K2-00038CC; Sat, 14 Jan 95 05:15 PST
To: pine-info@cac.washington.edu
From: PRFW51A@prodigy.com (Jim Mendelson)
Subject: Re: Pine file
Date: 14 Jan 1995 04:14:44 GMT
Message-Id: <3f7j3k$l78@usenetw1.news.prodigy.com>

  Chip,
   As far as the environment that I am running, I'm not quite sure what 
you mean.  At Prodigy, we won't be able to access FTP until February.  I 
recieved a ANSI II file, the first part written in ANSI II, the second 
portion written in code.  The sender notified me that I needed "pine" to 
decode the file, an all-files list for a BBS.  As far as recieving e-mail 
on Prodigy, we can recieve anything that can be sent.  
   Thanks for the help, hope this discription helps you a little me.  
Thanks again,

                                                                           
        Jim



From owner-pine-info@cac.washington.edu  Sat Jan 14 06:19:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26255;
	Sat, 14 Jan 95 06:19:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09646;
	Sat, 14 Jan 95 06:14:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09640;
	Sat, 14 Jan 95 06:14:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rT94K-00038CC; Sat, 14 Jan 95 06:03 PST
To: pine-info@cac.washington.edu
From: Judd Deaver <jdeaver@u.washington.edu>
Subject: Re: pine to cc:Mail
Date: Fri, 13 Jan 1995 20:56:50 -0800
Message-Id: <Pine.OSF.3.91a.950113205211.8117C-100000@saul4.u.washington.edu>
References: <199501132153.QAA03293@little-miami.iac.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <199501132153.QAA03293@little-miami.iac.net>

I tried that but PICO (the editor in PINE) screwed with the formatting 
and the file did not work when exported and the header removed. I ended 
up just going to their branch office here in Seattle and mailing it 
through their cc:mail network. I thank everybody for their replies. My 
corporation shall be mailing out to all different types of systems and 
although I will probably hire someone for this I need to know this 
information anyways. Thank you all.
						Judd Deaver

On Fri, 13 Jan 1995, Carl Jolley wrote:

> In article <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu> you wrote:
> : I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
> : network. I sent a Binary attachment but it did not seem to make it. Could 
> : this be because his network does not support MIME or because the way pine 
> : attaches files is different then cc:mail? If it is because they don't 
> : supprt MIME would an ASCII file attachment make it down or does pine 
> : automatically MIME encrypt all attachments?
> 
> : Any help is GREATLY appreciated (this is an important file) could you 
> : please reply via e-mail though to jdeaver@u.washington.edu
> 
> If you are sending "Internet mail" to a cc:Mail network the destination
> may have a cc:Mail gateway in place. There are only two that I know of
> that just do SMTP <--> cc:Mail. One is the Lotus product called Link to
> SMTP. It does not support MIME. The other gateway product is Internet
> Exchange by International Messaging Associates (e-mail address:
> sales@ima.com) It DOES support MIME. If your attachment is just ASCII then
> I'd suggest you not send it as a binary attachment, in fact why send it as
> an attachment at all? Just combine the body of your message and the
> attachment text and send it as a message with no attachments. 
> 
> --
> **** cjolley@iac.net <Carl Jolley>
> **** All opinions are my own and not necessarily those of my employer ****
> 


From owner-pine-info@cac.washington.edu  Sat Jan 14 07:00:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27048;
	Sat, 14 Jan 95 07:00:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13709;
	Sat, 14 Jan 95 06:55:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from uu3.psi.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13703;
	Sat, 14 Jan 95 06:55:16 -0800
Received: from naz.edu by uu3.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP;
        id AA04932 for ; Sat, 14 Jan 95 09:46:47 -0500
Received: from hydra.naz.edu.naz.edu by  naz.edu (4.1/SMI-4.1-DNI)
	id AA29962; Sat, 14 Jan 95 09:21:34 EST
Received: by hydra.naz.edu.naz.edu (5.65/Ultrix3.0-C)
	id AA21803; Sat, 14 Jan 1995 09:37:48 -0500
Date: Sat, 14 Jan 1995 09:37:47 -0500 (EST)
From: "Michael A. Naud" <manaud@naz.edu>
To: Amy Lauderdale <alauderd@MSMS.DoE.k12.MS.US>
Cc: Pine Discussion Group <pine-info@cac.washington.edu>
Subject: Re: printer
In-Reply-To: <Pine.SOL.3.91.950112115021.21587A-100000@Sparc.MSMS.DoE.k12.MS.US>
Message-Id: <Pine.ULT.3.91.950114093227.21747A-100000@hydra.naz.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 12 Jan 1995, Amy Lauderdale wrote:

> > Sorry to see someone other then me is also having printing problems in 
> > Pine and not getting any answers from the Group.  I know they are very 
> > busy, but being a Newby also, we are anxious to get on with our work.  I 
> > posted about a week ago, have read all the FAQs and just can't solve the 
> > problem.  I think in my case that the System Operator may have an option 
> > available that doesn't make printing possible.  Have sent a msg to the 
> > Sys Op, but to no avail.  In my case, when I ask for the printer, it 
> > actully captures the article and writes it to my hard disk, and of course 
> > I can then print from there.  You may check your hard disk and see if 
> > there is a file name "CAPFILE" or something near that.  Maybe someone out 
> > there will answer us soon.
> > 
> 
> You folks aren't alone.  I have trouble with printing also and can't seem
> to find any help.  Using Procomm, both at home on my Tandy and at
> school on my IBM with Epson 870 printer, it completely locks up
> if I try to print.  I have to totally re-boot to unlock it.
> 
> Using Telix I have a little better luck.  I can print as long as the
> message is not too long.  If it is more than two sheets worth of paper,
> it gives me an abort message.
> 
> Amy 
> 
> alauderd@msms.doe.k12.ms.us
> 
> 
> 

I just saw this same problem when I upgraded users to Pine 3.91 from 
3.87. When printing long messages, the terminal hangs and the printer 
stops short of finishing the message. It seems to happen with only _some_ 
terminal emulation packages and _certain_ printers. I have found a work 
around. You need to add the following entry to your feature-list. This 
acn either be done in the .pinerc or from the Setup Config menu

preserve-start-stop-characters

This made it disappear for all of my users. But be warned, you can press 
the wrong control key and Pine will stop. Read the help screen that is 
found in the setup menu on this feature. This probelm only surfaced when 
switvhing to the new Pine. No of my users ever had the problem before.

Hope this helps your plight.

Michael A. Naud

----
Michael A. Naud                          Internet:      manaud@naz.edu
Internet Administrator                   Fascimile:       716.586.2452
Nazareth College, Rochester NY 14618     Voice:      716.586.2525 x827




From owner-pine-info@cac.washington.edu  Sat Jan 14 09:04:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29127;
	Sat, 14 Jan 95 09:04:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15157;
	Sat, 14 Jan 95 08:59:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15151;
	Sat, 14 Jan 95 08:59:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTBfI-00038CC; Sat, 14 Jan 95 08:49 PST
To: pine-info@cac.washington.edu
From: gjmagg@ix.netcom.com (Gerald Maggioncalda)
Subject: Re: Pine & Procomm/Prowin
Date: 14 Jan 1995 16:42:28 GMT
Message-Id: <3f8utk$lu@ixnews3.ix.netcom.com>
References: <3ekd7s$oj3@skivs.ski.org>

In <3ekd7s$oj3@skivs.ski.org> erin@skivs.ski.org (Erin O'Neill) writes: 

>
>Prowin (Procomm for windows) and both are complaining about NOT being 
able 
>to do the 2 following things:
>
>1) print a mail message to their local printers 
>
>2) capture a mail message to a procomm capture file.
>

To print a message using Pine's attached-to-ansi with Procomm for 
Windows, first activate Printer Capture (using either the toolbar icon 
or from the File menu), then issue the 'y' print command. When Pine is 
done 'printing' the message, then click Procomm's Printer Capture icon 
again to deactivate printer capture and initiate output to the printer. 
At that point, the message should print out on your PC printer.

I am using Procomm for Windows version 1.02 and Pine version 3.89 and it 
works fine as described.




From owner-pine-info@cac.washington.edu  Sat Jan 14 09:35:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29719;
	Sat, 14 Jan 95 09:35:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12046;
	Sat, 14 Jan 95 09:31:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12032;
	Sat, 14 Jan 95 09:31:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTC8f-00038MC; Sat, 14 Jan 95 09:19 PST
To: pine-info@cac.washington.edu
From: ufeiner@moose.uvm.edu (Uri A. Feiner)
Subject: Can I Disable "save messages in read-mail"
Message-Id: <1995Jan14.163718.19175@emba.uvm.edu>
Date: Sat, 14 Jan 1995 16:37:18 GMT

Anyone out there know if there is a way to turn off this question?  An 
older version of Pine never bothered to ask and that's how I liked it!

Thanks.

Uri.

PS- An email response would be great since I don't frequent this newsgroup.


From owner-pine-info@cac.washington.edu  Sat Jan 14 10:48:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01220;
	Sat, 14 Jan 95 10:48:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16508;
	Sat, 14 Jan 95 10:43:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16502;
	Sat, 14 Jan 95 10:43:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTDD3-00038QC; Sat, 14 Jan 95 10:28 PST
To: pine-info@cac.washington.edu
From: brh@rhi.hi.is (Broddi Reyr Hansen)
Subject: pico: delete a block, paragraph etc..????
Date: 14 Jan 1995 17:51:30 GMT
Message-Id: <3f92v2$lkq@eldborg.rhi.hi.is>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


How can I delete a block of text with pico.  Aka I need to mark the text,
say few screen fills and then del it!!! 

broddur...
-----------------

please email if you have any suggestions...
--------------------------------------------------

brh@rhi.hi.is
--------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Sat Jan 14 12:08:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02772;
	Sat, 14 Jan 95 12:08:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13885;
	Sat, 14 Jan 95 12:00:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13879;
	Sat, 14 Jan 95 12:00:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTES3-00038CC; Sat, 14 Jan 95 11:47 PST
To: pine-info@cac.washington.edu
From: "Mark E. Crane" <psu01055@odin.cc.pdx.edu>
Subject: Threading messages and From: entry
Date: Fri, 13 Jan 1995 20:16:09 -0800
Message-Id: <Pine.PTX.3.91.950113201058.27437C-100000@odin.cc.pdx.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Pine--it is a truly useful program.  Are you guys making anything from 
this?  You should be.  I must have shown five people how to use pine at 
work today.  Fortunately that wasn't very difficult.  

When I used another email program (shudder), It would print the name of 
the listserver in the FROM: section of the header, rather than the 
individual that posted the message.  This would be nice to be able to do 
in Pine, because I am trying to develop a crude script with telix that 
will sort my incoming listserv mail.  Also, will any future incarnations 
of pine have threaded messages?  This would be nice when reading news.  
Finally, is there anyway I can sort my news by subject and my normal mail 
by arrival time?   Thanks!




Mark Crane
psu01055@odin.cc.pdx.edu



From owner-pine-info@cac.washington.edu  Sat Jan 14 13:52:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05060;
	Sat, 14 Jan 95 13:52:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18629;
	Sat, 14 Jan 95 13:40:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18623;
	Sat, 14 Jan 95 13:40:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTG3S-00038CC; Sat, 14 Jan 95 13:30 PST
To: pine-info@cac.washington.edu
From: Carlos Reed <creed@fse.ulaval.ca>
Subject: pine.conf
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SOL.3.90.950114111045.2405A-100000@rescol.fse.ulaval.ca>
Mime-Version: 1.0
Date: Sat, 14 Jan 1995 16:14:34 GMT

Hi gang!			

Can anybody send me its pine.conf, I don't have any examples of this file.


Carlos Reed , from beautiful and lovely Quebec.

BTW, it is pretty warm outhere. Crazi weather!


From owner-pine-info@cac.washington.edu  Sat Jan 14 13:55:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05157;
	Sat, 14 Jan 95 13:55:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15315;
	Sat, 14 Jan 95 13:51:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15309;
	Sat, 14 Jan 95 13:51:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTGAz-00038JC; Sat, 14 Jan 95 13:38 PST
To: pine-info@cac.washington.edu
From: csylk@csfaculty (Yoon Kimn)
Subject: Help me with PICO
Message-Id: <D2Csqz.D0n@ees1a0.engr.ccny.cuny.edu>
Date: Fri, 13 Jan 1995 17:04:11 GMT

Hi, all.

I need to know if there is a way to change the number of
columns per line in PICO. I want it to be 60 columms per
line instead of 80. Can it be configured that way?

Any kind of help will be greatly appreciated.

---------------------------------------------------------
Yoon Kimn

tyoon@cairn.org
yoon@cs-mail.engr.ccny.cuny.edu


From owner-pine-info@cac.washington.edu  Sat Jan 14 23:28:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15948;
	Sat, 14 Jan 95 23:28:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26008;
	Sat, 14 Jan 95 23:22:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26002;
	Sat, 14 Jan 95 23:22:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTP6v-00038KC; Sat, 14 Jan 95 23:10 PST
To: pine-info@cac.washington.edu
From: charlie@deltanet.com (Charles Lawrence)
Subject: 3 meg file hangs in pine
Date: 13 Jan 1995 07:34:03 GMT
Message-Id: <3f5adb$5ge@news1.deltanet.com>

X-Newsreader: WinVN 0.92.6+

When reading a large 2.5meg+ file into a pine message I hang and have to 
kill pine.  I am able to read in the same file fine in mail.  Is there
a system wide pine option I need to set?  
charlie



From owner-pine-info@cac.washington.edu  Sat Jan 14 23:58:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16453;
	Sat, 14 Jan 95 23:58:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22626;
	Sat, 14 Jan 95 23:52:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22620;
	Sat, 14 Jan 95 23:52:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTPZL-00038KC; Sat, 14 Jan 95 23:40 PST
To: pine-info@cac.washington.edu
From: chander@imap1.asu.edu
Subject: Re: pico: delete a block, paragraph etc..????
Date: 15 Jan 1995 02:07:15 GMT
Message-Id: <3fa00j$pct@news.asu.edu>
References: <3f92v2$lkq@eldborg.rhi.hi.is>

Broddi Reyr Hansen (brh@rhi.hi.is) wrote:

: How can I delete a block of text with pico.  Aka I need to mark the text,
: say few screen fills and then del it!!! 


	Place the cursor at the start of the block of text and press 
Control-^(Control-6 on the IBM keyboard).  Then move the cursor to the 
end of the block and press Control-K to cut the block of selected text.

---
Chander Ganesan
Arizona State University
Chander.Ganesan@Asu.Edu



From owner-pine-info@cac.washington.edu  Sun Jan 15 01:29:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18333;
	Sun, 15 Jan 95 01:29:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23780;
	Sun, 15 Jan 95 01:22:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from pluto.mscc.huji.ac.il by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23774;
	Sun, 15 Jan 95 01:22:25 -0800
Received: by pluto.mscc.huji.ac.il (AIX 3.2/UCB 5.64/4.03)
          id AA111757; Sun, 15 Jan 1995 11:22:07 +0200
Date: Sun, 15 Jan 1995 11:22:05 +0200 (WET)
From: marc bregman <msmarco@pluto.mscc.huji.ac.il>
To: pine-info@cac.washington.edu
Subject: Printing and Saving (fwd)
Message-Id: <Pine.A32.3.91.950115111642.108436B-100000@pluto.mscc.huji.ac.il>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I sent the following message to the pine-bugs email address and got back 
the standard automated reply saying my message would probably not be 
answered more specifically but suggesting I send my questions to the 
pine-info list which is what I am doing here. Replies directly to me 
and/or to the pine-info email list would be highly appreciated.

  Can anyone help with the following two problems: 

---------- Forwarded message ----------
Date: Sun, 15 Jan 1995 10:31:47 +0200 (WET)
From: marc bregman <msmarco@pluto.mscc.huji.ac.il>
To: pine-bugs@cac.washington.edu
Subject: Printing and Saving

I have been using Pine on my email account at The Hebrew University in 
Jerusalem for several years and love it. They now have installed Pine 
3.91 which I assume is a fairly updated version. I have two questions.

1) SAVING some time ago I wrote you all asking about whether there was any 
way to automatically save any sent message, not to the general SENT-MAIL 
folder, but to the same folder that the incoming mail message being 
replied is saved to by default with the save command. For example, if I 
get a message from someone for whom the default save folder is Joe, when 
I send a reply it will automatically (by default) be saved to the same 
Joe folder, not to the general SENT-MAIL folder. I had this feature on a 
mailer I was using when I had an account on an IBM/VM machine several 
years ago and it is the only thing I miss with PINE. The answer I got 
from you is that this feature was in planning but not yet implemented. 
Has there been any futher progress on getting such a feature into Pine?

2) PRINTING. When I try to print to a printer "slaved" to my PC using the
^Y command I get the following results. If it is a short file or incoming
message I am trying to print from within Pine, it prints but at the end of
the printing I get a flashing error message saying I need to set the
xon/xoff "preserve start stop character feature" in Config and I find the
computer is hung and I can only get unhung by breaking out of the session 
and login on again to my mainfram account. If it is longer document, it 
also doesn't print ok, but I have a string of ^Q^S every so often in the 
printout. 

I am using a special version of Kermit, prepared by the Hebrew U to 
permit use of Hebrew characters a well. This is what the computer center 
here recommends as a communications protocol package. I am printing to a 
HP laser printer over a Novelle network. I don't this this is the problem 
since I have tried printing files not from pine, but from my Unix account 
directly to the printer using a command PrintPC and this works just fine. 
I am connected to the my mainframe account using a modem set to 2400 baud 
with MNP3 error correction. I have the Pine printer setup set to 
"attached to ansi" option. Other settings such as LPR seem to send 
output to lineprinter attached to mainframe which is miles from where I 
am so that is not a solution for me.

Setting the preserve start stop character feature also does not seem to 
solve the problem of printing to the slaved laser printer. I still get 
the same problem of getting hung with the same flashing error message. 
Also the commands Ctrl-S and Ctrl-Q which are I understand supposed to 
freeze and restore flow control (according to Pine Help on this feature) 
don't seem to have any effect.

Is there anything else you would suggest to try to resolve this problem?
Thanks for your help.

                      Marc Bregman
  Hebrew Union College -- Jewish Institute of Religion
                  13 King David Street
                    Jerusalem 94101
                         Israel
         
            Voice                      E-Mail
  (+972-2) 203-234 (office)     msmarco@pluto.mscc.huji.ac.il
           203-333 (messages)   FAX (+972-2) 251-478
           724-049 (home)






From owner-pine-info@cac.washington.edu  Sun Jan 15 01:31:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18561;
	Sun, 15 Jan 95 01:31:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27593;
	Sun, 15 Jan 95 01:24:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27587;
	Sun, 15 Jan 95 01:24:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTR37-00038QC; Sun, 15 Jan 95 01:15 PST
To: pine-info@cac.washington.edu
From: Neil Steffen <nsteffen@cyberport.net>
Subject: How Can I POST Pretyped Documents in NEWS??
Date: 4 Jan 1995 06:00:12 GMT
Message-Id: <3eddhc$5mc@cpmt.cyberport.net>

       I have MOZILLA 1.0N and  Chameleon. I have typed many documents
 that I cannot export into NEWS via "newspost:comp.mail.pine"  with
my  Mail Document Button. 
	What is the command or do I need to use a GATEWAY to transfer
 Documents?     Thanks for your support.
  


From owner-pine-info@cac.washington.edu  Sun Jan 15 03:18:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20806;
	Sun, 15 Jan 95 03:18:13 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25018;
	Sun, 15 Jan 95 03:08:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25012;
	Sun, 15 Jan 95 03:08:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTSVQ-00038QC; Sun, 15 Jan 95 02:48 PST
To: pine-info@cac.washington.edu
From: "J. Kelly Cunningham" <deviate@lipschitz>
Subject: Re: Why no uudecode in Pine? 
Message-Id: <Pine.NXT.3.91.950114182607.5421A-100000@lipschitz>
Date: Sat, 14 Jan 1995 18:32:52 -0600
References: <3ddfin$fem@news.halcyon.com> <Pine.SOL.3.91.941223143542.28750J-100000@hobbes
In-Reply-To: <Pine.ULT.3.92.950110113741.18990F-100000@shiva1.cac.washington.edu> 
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

-----BEGIN PGP SIGNED MESSAGE-----

On Tue, 10 Jan 1995, David L Miller wrote:

   On Tue, 10 Jan 1995, David Wong wrote:
   
   > 
   > Sorry to bug in, but can a multi-parts uuencoded file be decoded
   > using Pine? I'm hunting for a reader that can do that. Thanks!
   > 
   
   Yes, use ';' to select all the parts, then "a|uudecode" to decode them. 
   Note that the parts need to be listed in order in the index before doing
   the decoding...

Well, sort of...

- -rw-r--r--  1 deviate   224567 Jan 14 18:20 froggy.pine.wav
- -rw-r--r--  1 deviate   221802 Jan 14 18:15 froggy.trn.wav

froggy.pine.wav will play, but it doesn't sound quite right.  Pine seems 
to be adding something.
   
   |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
   



-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBLxgYrOBu0383Om6dAQEBVwP+PvylnVzKUSKozPrxosVySQOT/tN/VO1A
SnoNagc8Q9UkXXyqISTku3OM7iI1/PDjSohQotFgiI3dRZF3QeT2cVh8s/EKcH1E
HWO957KHolVRUTnnscepuG71BPIbqFOF2jaab8jACgv4oOXvFpO6Y/D/9C63ahVV
5a3nzpRIFNM=
=+w28
-----END PGP SIGNATURE-----


-- kc       prudence dictates a low profile -- Sandy Sandfort
          finger deviate@lipschitz.sfasu.edu | pgp -fka +force
    finger slutsky@lipschitz.sfasu.edu | pgp -f | tee mkpgp.txt.uu | more


From owner-pine-info@cac.washington.edu  Sun Jan 15 05:30:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24296;
	Sun, 15 Jan 95 05:30:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00676;
	Sun, 15 Jan 95 05:23:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00670;
	Sun, 15 Jan 95 05:23:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTUjp-00038JC; Sun, 15 Jan 95 05:11 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: pine to cc:Mail
Date: 15 Jan 1995 06:36:13 -0500
Message-Id: <3fb1bd$egh@little-miami.iac.net>
References: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu> <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu> <3f7jdi$po@jaring.my>

John Vogelsang (fjv@insas.po.my) wrote:
: In article <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu>, Judd Deaver <jdeaver@u.washington.edu> says:
: >
: >Does cc:mail include a uudecoding function standard? I tried just reading 
: >the ascii version of the file into the body but it reformatted the text 
: >and made it worthless. 
: >

: As far as I know cc:Mail itself does not handle encoding/decoding. Lotus 
: Link to UUCP does handle MIME / uuencoded attachments properly. 
: I.e. Send a MIME message from internet through UUCPLink to cc:Mail and
: the received mail will have an attachment.

: On Thu, 12 Jan 1995, David L Miller wrote:

: > 
: > Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
: > good cc:Mail<->Internet gateway should be able to translate between MIME
: > and cc:Mail attachments, but unfortunately many do not...
: >

: Could somebody provide an example of "A good cc:Mail<->Internet 
: gateway" or is this just a hypothetical entity.

Internet Exchange from International Messaging Associates.
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Sun Jan 15 06:30:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25312;
	Sun, 15 Jan 95 06:30:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27481;
	Sun, 15 Jan 95 06:24:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27475;
	Sun, 15 Jan 95 06:24:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTVfV-00038KC; Sun, 15 Jan 95 06:10 PST
To: pine-info@cac.washington.edu
From: Halldor Arnason <harnason@u.washington.edu>
Subject: 8bit characters
Date: Sun, 15 Jan 1995 06:00:28 -0800
Message-Id: <Pine.OSF.3.91a.950115053719.2190F-100000-100000-100000@saul1.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE


I am having trouble sending 8bit characters using pine.  I want to define=
=20
in the header "Content-Transfer-Encoding: 8bit" and can do that.  The=20
trouble is when pine finds any foreign characters in the text (as it=20
will in this message), it defines it's own C-T-E header with=20
QUOTED-PRINTABLE, which overwrites my header.  It does this just silently=
=20
when sending mail, but gives a error message because of duplicate headers=
=20
when I try to post to a news-group.  So I had to remove my header to be=20
able to send this message.

This means that if the people I send mail to are using e.g. Elm, the=20
message is unreadable.  If they on the other hand are using pine it is=20
readable, but still has the disadvantage of when it is saved, the file=20
does not include the characters in their right form, while mail sent using=
=20
the 8bit encoding does.

I hope someone has a solution to this problem.

Thanks in advance, Halld=F3r

---
Halld=F3r =C1rnason
Dept. of Civil Eng.
University of Washington







From owner-pine-info@cac.washington.edu  Sun Jan 15 07:26:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26118;
	Sun, 15 Jan 95 07:26:31 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01945;
	Sun, 15 Jan 95 07:18:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01939;
	Sun, 15 Jan 95 07:18:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTWVB-00038JC; Sun, 15 Jan 95 07:04 PST
To: pine-info@cac.washington.edu
From: kehres@hk.net (Tim Kehres)
Subject: Re: pine to cc:Mail
Date: 15 Jan 1995 14:43:54 GMT
Message-Id: <3fbcba$csk@news.hk.net>
References: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>

In article <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>,
Judd Deaver  <jdeaver@u.washington.edu> wrote:
>I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
>network. I sent a Binary attachment but it did not seem to make it. Could 
>this be because his network does not support MIME or because the way pine 
>attaches files is different then cc:mail? If it is because they don't 
>supprt MIME would an ASCII file attachment make it down or does pine 
>automatically MIME encrypt all attachments?

A lot will depend upon what gateway you are using to get Internet based
email into and out of the cc:Mail world.  It is my understanding that the
Lotus gateways (UUCP/SMTP) do not yet have support for MIME, so there 
would be problems if you tried to get MIME messages in through one of these
gateways.  There are a few third party gateways on the market (Internet 
Exchange for cc:Mail from our company is one), which should provide the
functionality you are looking for however.

Best Regards,

Tim Kehres
International Messaging Associates Ltd


From owner-pine-info@cac.washington.edu  Sun Jan 15 09:34:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28401;
	Sun, 15 Jan 95 09:34:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29523;
	Sun, 15 Jan 95 09:30:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29517;
	Sun, 15 Jan 95 09:30:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTYY5-00038JC; Sun, 15 Jan 95 09:15 PST
To: pine-info@cac.washington.edu
From: mpbrowni@nyx10.cs.du.edu (Michael  Browning)
Subject: return receipt
Date: 15 Jan 1995 10:07:21 -0700
Message-Id: <3fbko9$r7@nyx10.cs.du.edu>

Is it possible to get a return receipt on your mail?


From owner-pine-info@cac.washington.edu  Sun Jan 15 11:16:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00362;
	Sun, 15 Jan 95 11:16:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04553;
	Sun, 15 Jan 95 11:09:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04547;
	Sun, 15 Jan 95 11:09:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTaCz-00038KC; Sun, 15 Jan 95 11:01 PST
To: pine-info@cac.washington.edu
From: harris@email.unc.edu (Trey Harris)
Subject: Re: zero-length .pine-interrupted-mail files
Date: 15 Jan 1995 18:56:05 GMT
Message-Id: <3fbr45$ks5@bigblue.oit.unc.edu>
References: <3euh21$12np@bigblue.oit.unc.edu> <Pine.SGI.3.91.950111093850.9824A-100000@tower.york.ac.uk> <DBRENNER.95Jan13161651@nemo.weeg.uiowa.edu>

In article <DBRENNER.95Jan13161651@nemo.weeg.uiowa.edu>,
Doug Brenner <dbrenner@nemo.weeg.uiowa.edu> wrote:
>We also have an AIX 3.2.5 system (around 12,000 user accounts).  We've been
>on break, but now that people are returning, our Help Desk is also starting
>to receive questions about phantom interrupted mail.
>
>Our problem is also the zero length .pine-interrupted-mail file.  We compiled
>Pine 3.91 with "#define DEFAULT_DEBUG 0" to help save disk space.  Based on
>the information provided by Trey Harris, I wonder if we should go back to the
>default debug level.

I wouldn't, and I'll tell you why.

I don't know what sort of disk quota you give your 12,000 users, but we
give our 15,000 three megabytes each.  For some months we ran Pine 3.90
with the default debug level.  In November, we upgraded to 3.91 with the
debug option turned off.

This was coincidental to a real disk crunch; we had the physical disk for
the explosion of around two hundred extra users a week, but with AIX3's
two-gigabyte limit on filesystems it was going to be a very laborious
process to move all those old users. 

Immediately after making the Pine upgrade, we ran a process to run 
through all the user's home directories and delete the 
.pine-debug* files.

Even as our user base has grown by three thousand since that time, WE HAVE 
NOT HAD TO WORRY ABOUT USER DISK SPACE SINCE.  We gained close to one 
GIGABYTE by making this change, and since you're at about the same scale, 
you'll lose about that much.

That's how much disk space those .pine-debug files take up.  I've spoken 
to a *bunch* of people who say they're having the .pine-interrupted-mail 
problem, all on AIX 3.2.5 boxes.  Are the Pine developers out there?  Are 
they listening?

(That's the one problem with using free software.  If there's a serious
serious bug that only affects a relatively small number of people, and
you're one of them, you can't get any help to fix it.  Sigh.)
-- 
Trey Harris                              http://sunsite.unc.edu/harris
--Stranger in a Strange Thread!
--
     My preferred email address has changed to harris@email.unc.edu.


From owner-pine-info@cac.washington.edu  Sun Jan 15 12:51:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02381;
	Sun, 15 Jan 95 12:51:28 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01810;
	Sun, 15 Jan 95 12:41:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01804;
	Sun, 15 Jan 95 12:40:58 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTbYe-00038PC; Sun, 15 Jan 95 12:28 PST
To: pine-info@cac.washington.edu
From: "Michael P. Browning" <bbrown@moe.coe.uga.edu>
Subject: threads
Date: Sun, 15 Jan 1995 15:28:10 -0500
Message-Id: <Pine.SUN.3.91.950115152051.2626A-100000@moe.coe.uga.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I just began using pine as a newsreader and basically like it.  My 
question is this: Is there a way to put all messages of a thread into one 
line (like nn).  You see the original post on one line and then the 
replies scattered throughout the list (like rn).  Personally I don't like 
this, can someone answer this?  Thanks.

Mike



From owner-pine-info@cac.washington.edu  Sun Jan 15 13:43:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03330;
	Sun, 15 Jan 95 13:43:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06279;
	Sun, 15 Jan 95 13:34:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06273;
	Sun, 15 Jan 95 13:34:05 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15053;
	Sun, 15 Jan 95 13:34:01 -0800
Date: Sun, 15 Jan 1995 13:34:01 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Trey Harris <harris@email.unc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: zero-length .pine-interrupted-mail files
In-Reply-To: <3fbr45$ks5@bigblue.oit.unc.edu>
Message-Id: <Pine.ULT.3.92.950115132923.8726G@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


> That's how much disk space those .pine-debug files take up.  I've spoken 
> to a *bunch* of people who say they're having the .pine-interrupted-mail 
> problem, all on AIX 3.2.5 boxes.  Are the Pine developers out there?  Are 
> they listening?

Yes.

Yes.
 
> (That's the one problem with using free software.  If there's a serious
> serious bug that only affects a relatively small number of people, and
> you're one of them, you can't get any help to fix it.  Sigh.)

That's the trouble with people using our code in environments that we 
can't replicate :)

Seriously, we have tried several times to reproduce this bug without 
success.  If anyone *can* reproduce it on demand, or run under a debugger 
until it happens, we could really use your help in getting to the bottom 
of this problem.

-teg


From owner-pine-info@cac.washington.edu  Sun Jan 15 14:10:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03812;
	Sun, 15 Jan 95 14:10:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02649;
	Sun, 15 Jan 95 13:55:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02643;
	Sun, 15 Jan 95 13:55:37 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07666;
	Sun, 15 Jan 95 13:55:35 -0800
Date: Sun, 15 Jan 1995 13:55:32 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Halldor Arnason <harnason@u.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: 8bit characters
In-Reply-To: <Pine.OSF.3.91a.950115053719.2190F-100000-100000-100000@saul1.u.washington.edu>
Message-Id: <Pine.ULT.3.92.950115133518.8726H-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE

Halld=F3r,
The best solution is for your recipients to use MIME-capable tools.
Elm users can add metamail support to Elm for handling MIME encoding of
8bit characters.

Pine users can either Save from the *attachment index*, or use the
*Export* command, rather than use the Save message command, if they wish
to have the stored text file fully decoded.  (Pine's message Save cmd will
always preserve the Quoted-Printable C.T.E.)

Pine will never support "just-send-8bit" as this approach violates
Internet mail standards.  However, version 3.92 *will* negotiate with
ESMTP-capable MTAs to do 8BITMIME.  (Don't ask when 3.92 will be ready.=20
We don't know yet.)

-teg

On Sun, 15 Jan 1995, Halldor Arnason wrote:

>=20
> I am having trouble sending 8bit characters using pine.  I want to define=
=20
> in the header "Content-Transfer-Encoding: 8bit" and can do that.  The=20
> trouble is when pine finds any foreign characters in the text (as it=20
> will in this message), it defines it's own C-T-E header with=20
> QUOTED-PRINTABLE, which overwrites my header.  It does this just silently=
=20
> when sending mail, but gives a error message because of duplicate headers=
=20
> when I try to post to a news-group.  So I had to remove my header to be=
=20
> able to send this message.
>=20
> This means that if the people I send mail to are using e.g. Elm, the=20
> message is unreadable.  If they on the other hand are using pine it is=20
> readable, but still has the disadvantage of when it is saved, the file=20
> does not include the characters in their right form, while mail sent usin=
g=20
> the 8bit encoding does.
>=20
> I hope someone has a solution to this problem.
>=20
> Thanks in advance, Halld=F3r
>=20
> ---
> Halld=F3r =C1rnason
> Dept. of Civil Eng.
> University of Washington



From owner-pine-info@cac.washington.edu  Sun Jan 15 15:21:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05422;
	Sun, 15 Jan 95 15:21:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07555;
	Sun, 15 Jan 95 15:15:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07549;
	Sun, 15 Jan 95 15:15:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTe0v-00038TC; Sun, 15 Jan 95 15:05 PST
To: pine-info@cac.washington.edu
From: rcsjr@crl.com (Robert C. Strain, Jr.)
Subject: Exporting folders to PC Eudora
Date: 15 Jan 1995 23:04:05 GMT
Message-Id: <3fc9l5$jsu@nntp.crl.com>
Mime-Version: 1.0

I would like to export all my folders (sent_mail & saved_mail) for use 
with a winsock client (PC Eudora v1.4.4) without losing the time and date 
stamp.  Can this be done?

Robert C. Strain, Jr.
St. Louis, MO
CompuServe: 71062,215

Internet: rcsjr@crl.com
January 15, 1995



From owner-pine-info@cac.washington.edu  Sun Jan 15 15:38:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05805;
	Sun, 15 Jan 95 15:38:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03911;
	Sun, 15 Jan 95 15:34:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from isisa.oit.unc.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03905;
	Sun, 15 Jan 95 15:34:47 -0800
Received: by email.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA154637; Sun, 15 Jan 1995 18:34:46 -0500
Date: Sun, 15 Jan 1995 18:34:46 -0500 (EST)
From: Trey Harris <harris@email.unc.edu>
X-Sender: harris@isisa.oit.unc.edu
To: Terry Gray <gray@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: zero-length .pine-interrupted-mail files
In-Reply-To: <Pine.ULT.3.92.950115132923.8726G@shiva1.cac.washington.edu>
Message-Id: <Pine.A32.3.91.950115183340.176689B-100000@isisa.oit.unc.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'd be happy to provide you with a staff account on our machine with 
unlimited disk space for your use to see our problem.

Trey Harris                              http://sunsite.unc.edu/harris
  System Administrator, Project Isis, Office of Information Technology
                       The University of North Carolina at Chapel Hill


From owner-pine-info@cac.washington.edu  Sun Jan 15 16:19:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06538;
	Sun, 15 Jan 95 16:19:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04432;
	Sun, 15 Jan 95 16:15:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04426;
	Sun, 15 Jan 95 16:15:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTezQ-00038KC; Sun, 15 Jan 95 16:08 PST
To: pine-info@cac.washington.edu
From: lef@wuacn.wustl.edu (Lori Fox)
Subject: Another Printing Problem
Date: 16 Jan 1995 00:08:03 GMT
Message-Id: <3fcdd3$sp8@newsreader.wustl.edu>

       I am using PINE as a mailreader (but not a newreader).  I have no 
trouble printing documents with the "y" command.   I would like to be 
able to print each message on a separate piece of paper, but the system 
as it is set up runs the various documents together.  (For example, if I 
give *separte* "y" commands for messages 4, 12 and 23, I will get those 
three documents printed, seriatum, on the same piece of paper.)  My 
system administrator doesn't understand why this is happening.  Does 
anyone else have any ideas ?  Is there something I can add to my file to 
correct this ?  (If it is significant:  I use PCAnywhere to connect to my 
internet account by phone line; I work on a 386SX computer (no laughing) 
which is part of a Novell network which includes a shared printer.  

      I would be very grateful for any ideas about how to fix this.  Thanks.

LEF


From owner-pine-info@cac.washington.edu  Sun Jan 15 16:41:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07014;
	Sun, 15 Jan 95 16:41:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08625;
	Sun, 15 Jan 95 16:37:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08619;
	Sun, 15 Jan 95 16:37:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTfHT-00038KC; Sun, 15 Jan 95 16:26 PST
To: pine-info@cac.washington.edu
From: flaczko@PROBLEM_WITH_INEWS_DOMAIN_FILE (Frank L Laczko Sr)
Subject: Help with news ...
Date: 16 Jan 1995 00:13:16 GMT
Message-Id: <3fcdms$c6f@gandalf.pic.net>

I am currently using Pine for mail, and Rtin for news. I like Pine much
better, but have been unable to configure it to handle News.

I am using Linux running on a 486 box, with a leased line Internet
connection. Mail is using Sendmail -- that works fine with Pine.
News is using nntp to my Internet provider's news server. Rtin works
OK -- as a matter of fact, there was no configuration required beyond
setting the NNTPSERVER variable. But, it is not the most user friendly
reader, particularly to my users from the DOS world.

Where do I find information on how to configure Pine to work in my
configuration? I would appreciate any help. 

Frank L Laczko Sr
flaczko@conline.com



From owner-pine-info@cac.washington.edu  Sun Jan 15 16:42:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07055;
	Sun, 15 Jan 95 16:42:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04726;
	Sun, 15 Jan 95 16:35:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.nada.kth.se by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04720;
	Sun, 15 Jan 95 16:35:29 -0800
Received: from staff.nada.kth.se (staff.nada.kth.se [130.237.225.70])
	by mail.nada.kth.se (8.6.9/8.6.9) with SMTP
	id BAA06970 for <pine-info@cac.washington.edu>;
	Mon, 16 Jan 1995 01:35:23 +0100
Message-Id: <199501160035.BAA06970@mail.nada.kth.se>
X-Authentication-Warning: mail.nada.kth.se: Host staff.nada.kth.se didn't use HELO protocol
To: pine-info@cac.washington.edu
Subject: Problem report: Decoding q-p before reply insertion
Date: Mon, 16 Jan 1995 01:35:23 +0100
From: Peter Svanberg <psv@nada.kth.se>

(Also sent, separately, to bine-bugs.)

In certain situations the content-transfer-encoding q-p 
in a text/plain part is not decoded before inserting it
in a reply.

The situation when I noticed it was when replying to a
multipart/alternative message, where the first part was
text/plain and the second was application/quickmail. The first
part was inserted but just "as is", i.e. with the "=xx" strings
left.
---
Peter Svanberg, NADA, KTH		    Email: psv@nada.kth.se
Dept of Num An & CS,
Royal Inst of Tech			    Phone: +46 8 790 71 40
S-100 44  Stockholm, SWEDEN		    Fax:   +46 8 790 09 30


From owner-pine-info@cac.washington.edu  Sun Jan 15 16:57:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07332;
	Sun, 15 Jan 95 16:57:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08797;
	Sun, 15 Jan 95 16:51:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.nada.kth.se by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08791;
	Sun, 15 Jan 95 16:51:45 -0800
Received: from staff.nada.kth.se (staff.nada.kth.se [130.237.225.70])
	by mail.nada.kth.se (8.6.9/8.6.9) with SMTP
	id BAA07189 for <pine-info@cac.washington.edu>;
	Mon, 16 Jan 1995 01:51:37 +0100
Message-Id: <199501160051.BAA07189@mail.nada.kth.se>
X-Authentication-Warning: mail.nada.kth.se: Host staff.nada.kth.se didn't use HELO protocol
To: pine-info@cac.washington.edu
Subject: Problem report: Long lines and reply insertion 
Date: Mon, 16 Jan 1995 01:51:36 +0100
From: Peter Svanberg <psv@nada.kth.se>

(Also sent, separately, to pine-bugs.)

When inserting text of the original message in a reply, no line
wrapping is done. This is not manageable when the lines are
very long.

Some UA:s makes one text paragraph into one message line,
and breaks it up with q-p soft line breaks. Is this,
by the way, correct and well-behaved MIME-usage? I can't
find any words against it in RFC 1521.
---
Peter Svanberg, NADA, KTH                   Email: psv@nada.kth.se
Dept of Num An & CS,
Royal Inst of Tech                          Phone: +46 8 790 71 40
S-100 44  Stockholm, SWEDEN                 Fax:   +46 8 790 09 30


From owner-pine-info@cac.washington.edu  Sun Jan 15 17:14:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07742;
	Sun, 15 Jan 95 17:14:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05156;
	Sun, 15 Jan 95 17:09:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05150;
	Sun, 15 Jan 95 17:09:45 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id RAA09631 for <pine-info@cac.washington.edu>; Sun, 15 Jan 1995 17:09:44 -0800
Date: Sun, 15 Jan 1995 17:09:45 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Pete Holsberg <pjh@tecoma.mccc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Script as printer command ???
In-Reply-To: <D2CwB4.498@tecoma.mccc.edu>
Message-Id: <Pine.SUN.3.91.950115170653.22858A-100000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 13 Jan 1995, Pete Holsberg wrote:

> I would like to use the following script as my printer command,
> with <???> representing the name of the current email message.
> How do I specify the name???
> 
> cat <????> | jetpr -h <???> | lp -dlj
> 
> Thanks,
> Pete
> 

I'm no expert, but I don't think you need the file name at all.  In fact, 
I would try just:

  jetpr -h | lpr -dlj

and see what happens.

---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646



From owner-pine-info@cac.washington.edu  Sun Jan 15 17:21:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07858;
	Sun, 15 Jan 95 17:21:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05231;
	Sun, 15 Jan 95 17:16:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05225;
	Sun, 15 Jan 95 17:16:20 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id RAA10280 for <pine-info@cac.washington.edu>; Sun, 15 Jan 1995 17:16:18 -0800
Date: Sun, 15 Jan 1995 17:16:20 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Pine Information Discussion Group <pine-info@cac.washington.edu>
Subject: Print to file script
Message-Id: <Pine.SUN.3.91.950115171012.22858B-200000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2131424143-340105332-790218980=:22858"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---2131424143-340105332-790218980=:22858
Content-Type: TEXT/PLAIN; charset=US-ASCII

I sometimes use pine on a remote system.  In this situation printing a 
mail message doesn't produce the desired results, unless you enjoy driving 
across town (or country!)

So I wrote a little script that will print mail messages to a file.  You 
can print several at a time and it won't overwrite them.

Just detach, change a few paths, and put it in your printer setup.

---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646

---2131424143-340105332-790218980=:22858
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=printout
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SUN.3.91.950115171620.22858C@linda.teleport.com>
Content-Description: 

Iw0KIyBwcmludG91dCAtIFByaW50IHBpbmUgbWFpbCB0byBhIGZpbGUNCiMN
Cg0KTlVNPTENCk1BSUxGSUxFPSRIT01FL3ByaW50b3V0L21haWwkTlVNDQoN
CndoaWxlIFsgLWYgJE1BSUxGSUxFIF0NCmRvDQogIE5VTT1gZXhwciAkTlVN
ICsgMWANCiAgTUFJTEZJTEU9JEhPTUUvcHJpbnRvdXQvbWFpbCROVU0NCmRv
bmUNCg0KY2F0ID4gJE1BSUxGSUxFDQo=
---2131424143-340105332-790218980=:22858--


From owner-pine-info@cac.washington.edu  Sun Jan 15 17:30:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07982;
	Sun, 15 Jan 95 17:30:18 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05354;
	Sun, 15 Jan 95 17:25:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05348;
	Sun, 15 Jan 95 17:25:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTg2d-00038QC; Sun, 15 Jan 95 17:15 PST
To: pine-info@cac.washington.edu
From: lawrld@law.lawlib.emory.edu (Richard L. Doernberg)
Subject: Passwords
Date: Sun, 15 Jan 1995 20:12:07 +1000
Message-Id: <lawrld.2.0601F5D9@law.emory.edu>

I am running Pcpine on my local pc. Is there any way that I can avoid entering 
my password each time that I log on to the mainframe to get my mail? I did not 
see anything in the configuration options.

Richard L. Doernberg
Richard L. Doernberg
Emory University School of Law
Atlanta, GA 30322
Phone: 404 727 6836
Fax:   404 727 6850
Email: lawrld@law.emory.edu


From owner-pine-info@cac.washington.edu  Sun Jan 15 21:41:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13518;
	Sun, 15 Jan 95 21:41:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12573;
	Sun, 15 Jan 95 21:36:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12567;
	Sun, 15 Jan 95 21:36:53 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA21999; Mon, 16 Jan 1995 00:36:22 +0500
Date: Mon, 16 Jan 1995 00:36:22 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: threads
In-Reply-To: <Pine.SUN.3.91.950115152051.2626A-100000@moe.coe.uga.edu>
Message-Id: <Pine.SOL.3.90.950116002637.21669F-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1325

On Sun, 15 Jan 1995, Michael P. Browning wrote:

> I just began using pine as a newsreader and basically like it.  My 
> question is this: Is there a way to put all messages of a thread into one 
> line (like nn).  You see the original post on one line and then the 
> replies scattered throughout the list (like rn).  Personally I don't like 
> this, can someone answer this?  Thanks.
 
Yes, though it isn't 100% foolproof.  In the folder index for the Inbox, 
hit "$" to sort, then "o" to sort by ordered subject.  This places all 
messages with the same subject together, in order by date.
 
If you decide that you like it, you can make it the default sort method 
as follows:
 
 o At Pine's main menu press "s" (setup)
 o Press "c" (congiguration)
 o Scroll through the configuration options until you find "sort-key"
 o Move down to highlight "ordered subject"
 o Press Return to mark that option
 o Press "e" to exit setup.
 
>From then on your folder indexes will be sorted by ordered subject when 
you start up Pine.
 
--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA




From owner-pine-info@cac.washington.edu  Sun Jan 15 23:31:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15328;
	Sun, 15 Jan 95 23:31:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13884;
	Sun, 15 Jan 95 23:27:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13878;
	Sun, 15 Jan 95 23:27:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTlgN-00038MC; Sun, 15 Jan 95 23:16 PST
To: pine-info@cac.washington.edu
From: parastat@alpha.it.teithe.gr (Savas Parastatidis)
Subject: Smaller binary for Pine 3.91!
Date: 15 Jan 95 21:02:43 GMT
Message-Id: <parastat.790203763@alpha.it.teithe.gr>


Hello everyboy,

I have already compiled Pine 3.91 on a DEC3100 Alpha system running OSF1
v1.3. My problem is that the executable is near 3.3Mb. I want it to be
smaller. So my thought was not to include some features of Pine, like
motd, mh. 

I found that I can exclude these by erasing their names from the
DEFAULTDRIVERS variable of the Makefile. But I don't know what every
driver is for. Can anyone help me with this?

Any other way of reducing the binary size of pine is more than welcome. 

Thank you very much,
-- 
+---------------------+
|.Savas  Parastatidis.|
|parastat@it.teithe.gr|
+---------------------+


From owner-pine-info@cac.washington.edu  Mon Jan 16 01:00:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16983;
	Mon, 16 Jan 95 01:00:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15105;
	Mon, 16 Jan 95 00:55:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15099;
	Mon, 16 Jan 95 00:55:36 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa08680;
          16 Jan 95 1:43 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA14275; Mon, 16 Jan 1995 08:56:54 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id IAA15735; Mon, 16 Jan 1995 08:54:44 GMT
Date: Mon, 16 Jan 1995 08:54:44 +0000 (GMT)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: "Mark E. Crane" <psu01055@odin.cc.pdx.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Threading messages and From: entry
In-Reply-To: <Pine.PTX.3.91.950113201058.27437C-100000@odin.cc.pdx.edu>
Message-Id: <Pine.LNX.3.91.950116085044.15700D-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 13 Jan 1995, Mark E. Crane wrote:

> Pine--it is a truly useful program.  Are you guys making anything from 
> this?  You should be.  I must have shown five people how to use pine at 
> work today.  Fortunately that wasn't very difficult.  

Totally agree that it is a great program.  Unfortunately unless we let 
the development team know, it may stop at the next release due to cuts.

> 
> When I used another email program (shudder), It would print the name of 
> the listserver in the FROM: section of the header, rather than the 
> individual that posted the message.  This would be nice to be able to do 
> in Pine, because I am trying to develop a crude script with telix that 
> will sort my incoming listserv mail.  Also, will any future incarnations 

I would recommend using procmail for this.  Procmail is another great 
"free" program which can be used for filtering incoming mail.  There are 
many things which you can do with procmail such as set up auto-replies 
etc.  If you need further information, please feel free to mail me.

Stuart

> 
> 
> Mark Crane
> psu01055@odin.cc.pdx.edu
> 

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Mon Jan 16 01:13:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17521;
	Mon, 16 Jan 95 01:13:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15361;
	Mon, 16 Jan 95 01:07:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15355;
	Mon, 16 Jan 95 01:07:37 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa09206;
          16 Jan 95 1:55 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA15919; Mon, 16 Jan 1995 09:08:59 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id JAA15762; Mon, 16 Jan 1995 09:06:51 GMT
Date: Mon, 16 Jan 1995 09:06:51 +0000 (GMT)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Michael Browning <mpbrowni@nyx10.cs.du.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: return receipt
In-Reply-To: <3fbko9$r7@nyx10.cs.du.edu>
Message-Id: <Pine.LNX.3.91.950116090345.15700E-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 15 Jan 1995, Michael Browning wrote:

> Is it possible to get a return receipt on your mail?
> 

The only way I know of doing this will only work if the receipient has a 
MTA (such as sendmail) which understands Return-Receipt-To:.

If this is the case, then set up a customised header. 

Please note that Return-Receipt-To: is not intended to be used all the 
time but more as debugging tool.

Stuart

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Mon Jan 16 02:07:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18591;
	Mon, 16 Jan 95 02:07:17 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16037;
	Mon, 16 Jan 95 02:01:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16031;
	Mon, 16 Jan 95 02:01:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTo4i-00038MC; Mon, 16 Jan 95 01:50 PST
To: pine-info@cac.washington.edu
From: chengman@umich.edu (Dennis Cheng)
Subject: Pine 3.9 for AIX
Date: 16 Jan 1995 09:04:01 GMT
Message-Id: <3fdcq1$nsj@lastactionhero.rs.itd.umich.edu>



Is Pine v 3.9 or 3.91 out and compiled for AIX yet?




From owner-pine-info@cac.washington.edu  Mon Jan 16 02:08:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18632;
	Mon, 16 Jan 95 02:08:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12272;
	Mon, 16 Jan 95 02:01:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12266;
	Mon, 16 Jan 95 02:01:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTo4i-00038KC; Mon, 16 Jan 95 01:50 PST
To: pine-info@cac.washington.edu
From: chengman@umich.edu (Dennis Cheng)
Subject: AIX Pine v3.9?
Date: 16 Jan 1995 09:00:18 GMT
Message-Id: <3fdcj2$nrv@lastactionhero.rs.itd.umich.edu>


Is Pine v 3.9 or 3.91 out and compiled for AIX yet?



From owner-pine-info@cac.washington.edu  Mon Jan 16 02:54:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19296;
	Mon, 16 Jan 95 02:54:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12706;
	Mon, 16 Jan 95 02:42:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12700;
	Mon, 16 Jan 95 02:42:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rToiS-00038TC; Mon, 16 Jan 95 02:31 PST
To: pine-info@cac.washington.edu
From: caj@tower.stc.housing.washington.edu (Craig A. Johnston)
Subject: PICO on Linux annoyance..
Date: 16 Jan 1995 10:11:05 GMT
Message-Id: <3fdgnp$4p0@news.u.washington.edu>

Problem is this: PICO always has an 'a' with an umlaut over it
(those two little dots) in the upper left-hand square.  It's only
an annoyance, as it's a spot where text never will be, but it's
ugly and I'm afraid it'll scare my users.. <g>  This was a problem
with the PICO included in my Linux distribution and one I compiled
myself from the source.  The 'a' is below the highlighted top line but
above all the text -- there is a single line there w/no text, and
that's where it is.  Oh, yeah -- it's highlighted.

Anyone run into this, or have any ideas?

Thanks in advance,
Craig.


From owner-pine-info@cac.washington.edu  Mon Jan 16 04:40:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22011;
	Mon, 16 Jan 95 04:40:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17947;
	Mon, 16 Jan 95 04:31:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17941;
	Mon, 16 Jan 95 04:31:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTqQo-00038PC; Mon, 16 Jan 95 04:21 PST
To: pine-info@cac.washington.edu
From: brennan@cchs.su.edu.au (Luke Brennan)
Subject: Re: Pine/VMS
Date: 14 Jan 95 22:05:20 +1000
Message-Id: <1995Jan14.220520@cchs.su.edu.au>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu>

	G'day..

>> UNZIP, and you MUST remember to transfer it as a binary.  This version
>> provides improved TCPIP support, but I've found that 3.89 seems to work
>> better under my installation of VMS (5.4-2).  (I'm not using TCPIP support,
	[...]

	My VMS PINE users are complaining that it's buggier than the
	previous version. They *like* it, but it's not quite as robust.

> Does anyone know where I can get UNZIP for VMS??

	ftp.spc.edu  in [.macro32.savesets] will provide you
	just about every tool you're ever likely to need for VMS.

	Luke.


From owner-pine-info@cac.washington.edu  Mon Jan 16 06:27:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24071;
	Mon, 16 Jan 95 06:27:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15384;
	Mon, 16 Jan 95 06:15:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15378;
	Mon, 16 Jan 95 06:15:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTs1o-00038TC; Mon, 16 Jan 95 06:03 PST
To: pine-info@cac.washington.edu
From: "Johan T Lindgren aka Lindus @ IRC" <johan-li@dsv.su.se>
Subject: Using Pine to Read Usenet.
Date: Mon, 16 Jan 1995 15:03:04 +0100
Message-Id: <Pine.ULT.3.91.950116145821.11172F-100000@saturn>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

	Hmm, perhaps I am just daft or haven't found the right function
yet but: How do I make a whole subject marked in such a way that I don't
have to see it any more? I mean in whatever version of rn you got there is
a "junk subject" or something equally sound. I don't crave for the command
to eXpunge them as well, but it would be great though. I suppose one could
sort the subjects and then just read what one is interested in and so on
but still...
	Ok, that was what I wondered about and if there isn't any command 
like this I think there should be one.

		Johan T Lindgren aka Lindus @ IRC


From owner-pine-info@cac.washington.edu  Mon Jan 16 07:51:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25637;
	Mon, 16 Jan 95 07:51:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16453;
	Mon, 16 Jan 95 07:42:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16447;
	Mon, 16 Jan 95 07:42:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTtPU-00038VC; Mon, 16 Jan 95 07:32 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Smaller binary for Pine 3.91!
Date: 16 Jan 95 15:35:31 GMT
Message-Id: <ellis.790270531@gmi.edu>
References: <parastat.790203763@alpha.it.teithe.gr>

parastat@alpha.it.teithe.gr (Savas Parastatidis) writes:


 >Hello everyboy,

 >I have already compiled Pine 3.91 on a DEC3100 Alpha system running OSF1
 >v1.3. My problem is that the executable is near 3.3Mb. I want it to be
 >smaller. So my thought was not to include some features of Pine, like
 >motd, mh. 

 >I found that I can exclude these by erasing their names from the
 >DEFAULTDRIVERS variable of the Makefile. But I don't know what every
 >driver is for. Can anyone help me with this?

 >Any other way of reducing the binary size of pine is more than welcome. 

On SunOS the bin is over 2.5 M.  Stripping reduces it to less than 1.5M.
You might also make sure the binary is linked dynamically.

 >Thank you very much,
 >-- 
 >+---------------------+
 >|.Savas  Parastatidis.|
 >|parastat@it.teithe.gr|
 >+---------------------+
-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Mon Jan 16 07:56:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25736;
	Mon, 16 Jan 95 07:56:00 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20283;
	Mon, 16 Jan 95 07:42:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20277;
	Mon, 16 Jan 95 07:42:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTtJa-00038RC; Mon, 16 Jan 95 07:25 PST
To: pine-info@cac.washington.edu
From: clear@wingra.com (Mark Clear)
Subject: Re: pine to cc:Mail
Date: Mon, 16 Jan 1995 09:27:04 -0600
Message-Id: <clear-1601950927040001@www.wingra.com>
References: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu> <3fbcba$csk@news.hk.net>

In article <3fbcba$csk@news.hk.net>, kehres@hk.net (Tim Kehres) wrote:

> In article <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>,
> Judd Deaver  <jdeaver@u.washington.edu> wrote:
> >I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
> >network. I sent a Binary attachment but it did not seem to make it. Could 
> >this be because his network does not support MIME or because the way pine 
> >attaches files is different then cc:mail? If it is because they don't 
> >supprt MIME would an ASCII file attachment make it down or does pine 
> >automatically MIME encrypt all attachments?
> 
> A lot will depend upon what gateway you are using to get Internet based
> email into and out of the cc:Mail world.  It is my understanding that the
> Lotus gateways (UUCP/SMTP) do not yet have support for MIME, so there 
> would be problems if you tried to get MIME messages in through one of these
> gateways.  There are a few third party gateways on the market (Internet 
> Exchange for cc:Mail from our company is one), which should provide the
> functionality you are looking for however.
> 

Missive, from our company, is another.  Missive integrates all the leading
mail systems (cc:Mail, SMTP, VMSmail, Microsoft Mail, etc) into one
seamless network.  Missive's SMTP inbound channel can decode MIME and turn
the attachment into the appropriate format for the destination, be it
cc:Mail or whatever.  In the other direction, the SMTP outbound channel
can encode attachments into MIME as well.

(end commercial)

|-----------------------------------------------------------------------------|
| Mark Clear                                       Internet: clear@wingra.com |
| Wingra Technologies, Inc.                       WWW: http://www.wingra.com/ |
| Madison, WI                                             Phone: 608-238-4454 |
|                                                                             |
| Dr. Seuss predicted net surfing 30 years ago: "I bet with my net I can get  |
| those things yet!" -- The Cat In the Hat                                    |
|-----------------------------------------------------------------------------|


From owner-pine-info@cac.washington.edu  Mon Jan 16 10:07:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29020;
	Mon, 16 Jan 95 10:07:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22348;
	Mon, 16 Jan 95 09:58:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from clark.net by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22342;
	Mon, 16 Jan 95 09:58:22 -0800
Received: (gonzales@localhost) by clark.net (8.6.9/8.6.5) id MAA06169; Mon, 16 Jan 1995 12:58:20 -0500
Date: Mon, 16 Jan 1995 12:58:19 -0500 (EST)
From: Cuauhtemoc <gonzales@clark.net>
To: pine-info@cac.washington.edu
Subject: attachments
Message-Id: <Pine.SOL.3.91.950116125705.5703A-100000@explorer>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

	Pine,
		I have a slip account with a local Internet access 
provider and would like to attach a document from my a:drive to an email 
message using pine.  I can't seem to get it to work.  Is it possible?  

Thanks


Enrique Gonzales



From owner-pine-info@cac.washington.edu  Mon Jan 16 10:56:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00301;
	Mon, 16 Jan 95 10:56:13 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19478;
	Mon, 16 Jan 95 10:47:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19472;
	Mon, 16 Jan 95 10:47:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTwGp-00038RC; Mon, 16 Jan 95 10:35 PST
To: pine-info@cac.washington.edu
From: bilwil@Primenet.Com (William Smithers)
Subject: Re: pico: delete a block, paragraph etc..????
Date: 14 Jan 1995 19:45:54 GMT
Message-Id: <3f99li$hp7@news.primenet.com>
References: <3f92v2$lkq@eldborg.rhi.hi.is>

In article <3f92v2$lkq@eldborg.rhi.hi.is>,
Broddi Reyr Hansen <brh@rhi.hi.is> wrote:
>
>How can I delete a block of text with pico.  Aka I need to mark the text,
>say few screen fills and then del it!!! 
>
  =========================================================================

  <Ctrl-^> begins to mark a block. Move the cursor to highlight the 
desired block. <Ctrl-k> will delete it. <Ctrl-u> will deposit the marked 
block at the cursor.         ..... <Ctrl-g> is for "Get Help" :-)

  ========================================================================


From owner-pine-info@cac.washington.edu  Mon Jan 16 10:56:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00322;
	Mon, 16 Jan 95 10:56:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23125;
	Mon, 16 Jan 95 10:47:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23119;
	Mon, 16 Jan 95 10:47:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTwGF-00038PC; Mon, 16 Jan 95 10:34 PST
To: pine-info@cac.washington.edu
From: jdulaney@crl.com (John Dulaney)
Subject: .addressbook lost/screwed up! HELP!
Date: 16 Jan 1995 16:39:38 GMT
Message-Id: <3fe7ga$mvb@nntp.crl.com>

	When PINE's new V. kicked in a few months ago my provider lost a 
lot of my addresses. With my backup I I tried to re-insert them but it 
didn't work at all! PINE looked at my backup and used every line as the 
nickname line only and so its a MESS! I hope someone can tell me what I 
can do to recover the thousands of addresses for me. I'm so depressed.
	Thanks--don't forget to enter the contest below. (Not mine.)
	Best, John
--------------------------------------------------------------------------
You could win $500 (hey, this is no joke)

* * * * * * * * * * ** * * * * * * * * * * * * * * * * * * * * * * * * *
*FREE CD-ROM disks/hardware/PAL/SECAM video catalog & Cool ICONS at my *
*WWW HOME PAGE http://xmission.com/~wwwads/mind/logic.html Or E-mailed *
*catalog as text, zipped, UUEncoded. OR get catalog only from our ftp  *
*site: xmission.com /pub/users/wwwads/logic.zip WORLDWIDE SHIPPING VISA*
*/MC/AMEX Wholesale/Retail jdulaney@crl.com - A nice guy in California *
*Plug for friend:Blind or seeing impaired? Ask for a free Scatalog.exe *
*     ---------------------------------------------------------------  *
*     As regards this contest, of which I have no part, please try my  *
*     HOME PAGE storefront in WWW, address above. John - MIND LOGIC -  *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 

by voting for your favorite Internet Entrepreneur and telling us what is 
your favorite Internet store front.

This contest is sponsored by The Internet Business Journal, for our 
March issue (our first annual Internet Marketing Awards).

Here is how to enter the contest:

(1)  Tell us who you think is the Internet Entrepreneur of 1994 and 
explain why.

(2) Tell us what your favorite Internet store is and explain why (to 
qualify, the store must have been open for business on the Net in 1994).

(3) Tell us what you think was the most creative advertising on the 
Internet in 1994 and explain why.

(4) Tell us what you think was the worst advertising on the Internet in 
1994 and explain why.

Contest Rules:

Only entries sent by e-mail to michael@strangelove.com will be 
accepted. Only one entry per person will be accepted. Send in two 
entries and you will be disqualified from the draw.

Valid entries must answer all questions. Entries must be received before 
midnight, February 20, 1995. The winner will be determined by random 
selection from all valid entries. We retain full copyright on all 
submissions. We reserve the right to publish any submissions. We 
reserve the right to publish the winner's name and e-mail address.

The Prize: Five hundred dollars (Canadian funds).

Why are we doing this?

We are curious to see how often lawyers will be picked and for which 
categories.

Also, The Internet Business Journal's March issue will present our first 
annual Internet Marketing Awards and Internet Entrepreneur of the 
year. We think that the people most qualified to pick the winners are the 
Internet community members and not some greasy advertising executive 
who normally tries to figure out new ways of selling cigarettes to 
children.

Think of it as our way of helping to create a Spam-Free Internet.

We are Strangelove Internet Enterprises, purveyors of fine Internet 
publications. Watch us in 1995 as we demonstrate what creative 
Internet marketing is all about. Reviews of our latest book, How to 
Advertise on the Internet, are available at 
http://arganet.tenagra.com/Tenagra/books.html.

Michael Strangelove
CEO, SIE Inc.
January 2, 1995
Michael@Strangelove.com

This document may be archived, forwarded, and reprinted, as long as no 
changes are made to the text. (An HTML version of this text is 
available upon request).


From owner-pine-info@cac.washington.edu  Mon Jan 16 11:01:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00453;
	Mon, 16 Jan 95 11:01:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23238;
	Mon, 16 Jan 95 10:56:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23232;
	Mon, 16 Jan 95 10:56:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTwM0-00038TC; Mon, 16 Jan 95 10:40 PST
To: pine-info@cac.washington.edu
From: bilwil@Primenet.Com (William Smithers)
Subject: JOE 2.2 - What is it doing?
Date: 15 Jan 1995 06:54:33 GMT
Message-Id: <3fagr9$kpb@news.primenet.com>

  Today I installed JOE 2.2 (the version provided at PrimeNet) in Pine 3.91.

  No sooner did I try to write my first sentence with it, then the program
inserted unwanted letters in the typed words; it sometimes inserted
unwanted groups of letters in strange places. 

  I want a text editor which helps, not confounds me. JOE has been removed.

                                 -- Bill Smithers
  


From owner-pine-info@cac.washington.edu  Mon Jan 16 12:00:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01803;
	Mon, 16 Jan 95 12:00:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20469;
	Mon, 16 Jan 95 11:49:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20463;
	Mon, 16 Jan 95 11:49:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTxF3-00038TC; Mon, 16 Jan 95 11:37 PST
To: pine-info@cac.washington.edu
From: brogers@utic.unicomp.net (Bryan Rogers)
Subject: Re: threads
Date: 16 Jan 1995 12:43:28 -0600
Message-Id: <3feeog$p82@utic.unicomp.net>
References: <Pine.SUN.3.91.950115152051.2626A-100000@moe.coe.uga.edu>

In the folder index pressing the keys "$s" will sort the folder on subject.
This, I believe, is the closest Pine comes to threading.

Seizure Later!
-- 
/* Brian Rogers, disciple of Java, brogers@integctr.com */


From owner-pine-info@cac.washington.edu  Mon Jan 16 14:14:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05365;
	Mon, 16 Jan 95 14:14:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26315;
	Mon, 16 Jan 95 13:57:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26309;
	Mon, 16 Jan 95 13:57:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rTzCq-00038XC; Mon, 16 Jan 95 13:43 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: HELP: Need SCO binary decoder
Date: 16 Jan 1995 12:39:58 -0800
Message-Id: <3feliu$mss@garlic.com>


HELP!  I need an SCO decoder for MIME messages.  I don't have a compiler, 
so I need binaries for an Intel platform.  Can someone point me in the 
right direction?

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


From owner-pine-info@cac.washington.edu  Mon Jan 16 14:35:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05767;
	Mon, 16 Jan 95 14:35:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26809;
	Mon, 16 Jan 95 14:29:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from bru.mayo.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26803;
	Mon, 16 Jan 95 14:29:34 -0800
Received: from fermat.Mayo.EDU by bru.mayo.EDU (4.1/SMI-4.0)
	id AA26571; Mon, 16 Jan 95 16:29:29 CST
Received: by fermat.Mayo.EDU (5.57/Ultrix2.4-C)
	id AA01096; Mon, 16 Jan 95 16:29:25 -0600
Date: Mon, 16 Jan 1995 16:29:20 +0200 (IST)
From: ravindra kahatapitiya <KAHATAPITIYA@rcf.mayo.edu>
Subject: How do I Set HP Laser 4 printer to print Pine
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.1.2-VMS-9.9501161658.A595600959-0100000@HARVEY.MAYO.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi there everyone!
	Could someone out there help me to get my laser printer to print 
pine mail.  I am able to print stuff out using a computer that is 
attached to regular dot matrix printer attached to another computer.  The 
command line when I request to print says "attached-to-ansi" or something 
like that.  However, this does nothing when I am on a computer that is 
attached to a laser printer.  PLEASE HELP ME!!!!
	I don't usually get this mail group, so those of you who do reply 
will have to respond directly to me:
	My address : kahatapitiya@mayo.rcf.edu
			507 284 4928
	Many thanks,
			Ravi.


From owner-pine-info@cac.washington.edu  Mon Jan 16 16:30:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07892;
	Mon, 16 Jan 95 16:30:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24557;
	Mon, 16 Jan 95 16:25:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24551;
	Mon, 16 Jan 95 16:25:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU1Wu-00038JC; Mon, 16 Jan 95 16:12 PST
To: pine-info@cac.washington.edu
From: pucho@netcom.com (Marcos Rubinstein)
Subject: Re: Help me with PICO
Message-Id: <puchoD2Iv02.832@netcom.com>
References: <D2Csqz.D0n@ees1a0.engr.ccny.cuny.edu>
Date: Mon, 16 Jan 1995 23:38:26 GMT

only one word:
NO

(no help possible... no way to change the number of columns)

:(

Pucho


From owner-pine-info@cac.washington.edu  Mon Jan 16 17:49:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10636;
	Mon, 16 Jan 95 17:49:09 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00153;
	Mon, 16 Jan 95 17:42:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00146;
	Mon, 16 Jan 95 17:42:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU2nH-00038KC; Mon, 16 Jan 95 17:33 PST
To: pine-info@cac.washington.edu
From: Grant Young <young@ucla.edu>
Subject: SLIP, Packet Driver & PINE--HELP
Date: Mon, 16 Jan 1995 17:27:34 -0800 (PST)
Message-Id: <Pine.PCN.3.90.950116172451.12362A-100000@[128.97.72.121]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello Pine Folks:

I'm truly in need of help.  I want to use the packet version of
PC Pine 3.91 to connect via a SLIP connection to my school's
mail/news system.  I am using the Univ. of Minnesota's UMSLIP.COM
Packet driver for SLIP, version 2.1 and PHONE.EXE to dial into
my school's slip server.  Gopher, Minuet and DosLynx are working
great.  Whenever I try to run Pine, I get an error message stating
that BOOTP failed.  When I manually enter my IP address, gateway,
nameserver, etc., Pine returns a message stating that my INBOX cannot
be opened because the [Host cannot be found].

I can successfully run the packet version of PC Pine with the Crynwr
Packet driver for a 3c509 NIC, version 11.2.  I do not use BOOTP
when I use the Crynwr 3c509 packet driver.

Any thoughts as to what the problem is?

Grant Young
young@ucla.edu
UCLA OAC Microcomputer Support Office




From owner-pine-info@cac.washington.edu  Mon Jan 16 18:01:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10895;
	Mon, 16 Jan 95 18:01:28 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26190;
	Mon, 16 Jan 95 17:58:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26184;
	Mon, 16 Jan 95 17:58:02 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU33g-00038PC; Mon, 16 Jan 95 17:50 PST
To: pine-info@cac.washington.edu
From: teale@acs.ucalgary.ca (Debbie Teale)
Subject: How to manage mailing lists with pine
Message-Id: <Jan16.213457.131659@acs.ucalgary.ca>
Date: Mon, 16 Jan 1995 21:34:57 GMT

Several users on campus are now using pine on AIX (some former
elm users) and pc-pine, and enquiries are coming in on handling
mailing lists.  In 3.91 can an addressbook reside on AIX and:

1) be firstly shared and used by several users, this seems
probable once access has been worked out.
2) be used by pc-pine users as well 
3) be updated by a pc-pine user
4) suppress the list of cc recipients

Thanks for your guidance in this area.  Mailing list management
seems to be a hot topic here especially with a mix of elm and
pine users on different platforms so if anyone with experience could
comment I would appreciate the input.



-- 
Deborah Teale, UCS, MS736, 220-4467
E-mail: teale@acs.ucalgary.ca


From owner-pine-info@cac.washington.edu  Mon Jan 16 18:46:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11809;
	Mon, 16 Jan 95 18:46:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00983;
	Mon, 16 Jan 95 18:42:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00977;
	Mon, 16 Jan 95 18:42:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU3iP-00038KC; Mon, 16 Jan 95 18:32 PST
To: pine-info@cac.washington.edu
From: jason@IS.NET (Jason R. Mastaler)
Subject: Re: PICO on Linux annoyance..
Date: 17 Jan 1995 02:23:44 GMT
Message-Id: <JASON.95Jan16212344@user1.IS.NET>
References: <3fdgnp$4p0@news.u.washington.edu>
In-Reply-To: caj@tower.stc.housing.washington.edu's message of 16 Jan 1995 10:11:05 GMT

In article <3fdgnp$4p0@news.u.washington.edu> caj@tower.stc.housing.washington.edu (Craig A. Johnston) writes:

> 
> Problem is this: PICO always has an 'a' with an umlaut over it
> (those two little dots) in the upper left-hand square.  It's only
> an annoyance, as it's a spot where text never will be, but it's
> ugly and I'm afraid it'll scare my users.. <g>  This was a problem
> with the PICO included in my Linux distribution and one I compiled
> myself from the source.  The 'a' is below the highlighted top line but
> above all the text -- there is a single line there w/no text, and
> that's where it is.  Oh, yeah -- it's highlighted.
> 
> Anyone run into this, or have any ideas?
> 
Yes, I have run into this.  I too originally had the PICO that came
distributed with LINUX, and it has the same strange 'bugs' in it as
you describe.  I really don't have any idea why it is like this.  

I recently picked up another PICO binary from ftp.cac.washington.edu
and this one does NOT have those same problems.  It is version 2.5,
in the /pine/unix-bin directory as pico-bin.linux.  

Cheers,

Jason R. Mastaler
(jason@is.net)


From owner-pine-info@cac.washington.edu  Mon Jan 16 19:12:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12367;
	Mon, 16 Jan 95 19:12:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27110;
	Mon, 16 Jan 95 19:08:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27102;
	Mon, 16 Jan 95 19:07:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU46S-00038JC; Mon, 16 Jan 95 18:57 PST
To: pine-info@cac.washington.edu
From: vince@kbrown.oldcampus.yale.edu (Vince Chan)
Subject: Problems with pine reading pine.conf
Date: 16 Jan 1995 19:29:58 -0500
Message-Id: <3ff326$gq4@kbrown.oldcampus.yale.edu>


	I have built pine and am experiencing a problem.  Somehow pine 
doesn't know that /usr/local/lib/pine.conf is there since all the .pinerc
it creates are from the same settings as the output from pine -conf so
does anyone have any ideas what might be wrong?  Thanks for any help.


                              Cheers,
          		       Vince
E-mail:
vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. 
  root@berkeley.circlestar.com,(o o) San Francisco, California USA
  _________________________oOO__(_)__OOo_____________________________
 |  There are many forms of science but only physics is the quantum  |
 |                    leap of the 21st Century.  	             |
  \_________________________________________________________________/
	uPoy@physics.ucla.edu	     UCLA Physics/Electrical Engineering
	 			     Los Angeles, California USA
	    
GUS Digest Adminstrator
Advanced Gravis UltraSound Card - The ultimate in soundcard technology 

System Administrator - bigbang.HIP.Berkeley.EDU





From owner-pine-info@cac.washington.edu  Mon Jan 16 19:23:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12569;
	Mon, 16 Jan 95 19:23:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27303;
	Mon, 16 Jan 95 19:20:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from tyrell.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27297;
	Mon, 16 Jan 95 19:20:33 -0800
Received: by tyrell.net id AA29077
  (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 16 Jan 1995 21:18:02 -0600
Date: Mon, 16 Jan 1995 21:18:01 -0600 (CST)
From: Bill Murray <arwhead@tyrell.net>
To: pine-info@cac.washington.edu
Subject: Emulation - Highlight
Message-Id: <Pine.SUN.3.91.950116211529.28786A-100000@tyrell.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Why does Pine send the following construct:

highlight on (smso), cursor address, text, hightlight off (rmso)

Shouldn't it send:

cursor address, highlight on (smso), text, highlight off (rmso)

????????????????????????????????????????????????????????????????????????

Bill Murray
arwhead@tyrell.net


From owner-pine-info@cac.washington.edu  Mon Jan 16 19:26:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12628;
	Mon, 16 Jan 95 19:26:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27376;
	Mon, 16 Jan 95 19:23:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27370;
	Mon, 16 Jan 95 19:23:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU4Et-00039hC; Mon, 16 Jan 95 19:05 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: 3 questions ? ? ? Mail, Unix, Internet.
Date: 17 Jan 1995 02:58:13 GMT
Message-Id: <3ffbo5$8gg@cronkite.ocis.temple.edu>

Comes here Mr. David A Hosten with this opinion in the "comp.mail.pine" group in
this article on Thu, 12 Jan 1995 01:48:52 GMT:

 +   1. (a) How do I change my environment to enable Pico to replace the vi

setenv EDITOR pico

 +   2. (a) How may I retrieve posts to Usenet groups that my Freenet/University
 +   accounts do not subscribe to?

Just set your nntp-server to another newserver that carries such newsgroups
of your choice.

 +   of Unix (am going to decide between Free/386/NetBsd, Linux or

Linux seems to be the choice of the GNU generation. Give it a try.
      
--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Mon Jan 16 19:26:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12655;
	Mon, 16 Jan 95 19:26:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01572;
	Mon, 16 Jan 95 19:23:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01566;
	Mon, 16 Jan 95 19:23:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU4Ep-00039eC; Mon, 16 Jan 95 19:05 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Enhancement Suggestions
Date: 17 Jan 1995 02:50:17 GMT
Message-Id: <3ffb99$8gg@cronkite.ocis.temple.edu>

Comes here Mr. Steven Feinholz with this opinion in the "comp.mail.pine"
group in this article on Thu, 12 Jan 1995 00:56:41 GMT:

 +   I have 2 enhancement suggestions for easier use of Pine

 +      It would be nice, and would save time, to be placed back
 +      into the last expanded list. Otherwise I have to press
 +      <CR> and wait for the expanded list of newsgroups to be
 +      generated again.

You can set this option in the Setup/Config screen by selecting this option:

                [X] expanded-view-of-folders

 +   2. Is there a way to show the number of messages on a particular
 +      newsgroup list from the "Expanded List" screen so that I get
 +      a visual notification of which newsgroups have messages
 +      without having to Select the newsgroup?

Good point what would be nicer is if it notifies as to how many new messages,
as supposed to just the number of messages.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Mon Jan 16 19:51:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13121;
	Mon, 16 Jan 95 19:51:01 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27735;
	Mon, 16 Jan 95 19:48:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27727;
	Mon, 16 Jan 95 19:48:09 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU4io-00038MC; Mon, 16 Jan 95 19:36 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: User reporting that Pine 3.91 (SunOS 4.1.3) hangs.  Any ideas?
Date: 17 Jan 1995 03:25:53 GMT
Message-Id: <3ffdc1$8gg@cronkite.ocis.temple.edu>

Comes here Mr. R. Stewart Ellis with this opinion in the "comp.mail.pine" group
in this article on 13 Jan 95 12:19:35 GMT:

 +   I have been using 3.90 on SunOS 4.1.x since it came out, recently upgrading
 +   to 3.91. Apart from some design philosophy differences with the authors the
 +   only real problem I have had with 3.91 is that it is extremely slow handlin
 +   my INBOX of 8500 messages, totalling untold megs of filespace.

8500 messages in the INBOX?
How about reading/deleting/moving/saving read mail elsewhere....things can get
much better then. Doncha think so ?

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Mon Jan 16 19:51:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13138;
	Mon, 16 Jan 95 19:51:02 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01947;
	Mon, 16 Jan 95 19:48:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01941;
	Mon, 16 Jan 95 19:48:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU4in-00038KC; Mon, 16 Jan 95 19:36 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Pine Installation
Date: 17 Jan 1995 03:20:31 GMT
Message-Id: <3ffd1v$8gg@cronkite.ocis.temple.edu>

Comes here Mr. Mark Andres with this opinion in the "comp.mail.pine" group in
this article on Fri, 13 Jan 1995 00:45:47 GMT:

 +   I am at the beginner level with UNIX and, for better or worse, I have
 +   been made the mail administrator of our Sun SPARC station.  I managed to
 +   configure sendmail to work and now our users want something more user
 +   friendly in a  mail system.  Any pointers on where to find an
 +   installation document is greatly appreciated.

There's a pre-compiled binary for Pine.SUN avail at:

ftp://ftp.cac.washington.edu/pine/unix-bin/pine-bin.sun

There's also a Solaris version if you are using Solaris instead of SunOS 4.1+

 +   Mark Andres, M.L.S.       andres@gol.com  (NEW!)
 +   Systems Librarian &       2-2 Minami-Osawa
 +   Macintosh Consultant      Hachioji-shi, Tokyo 192-03 Japan
 +   Temple University Japan   Fax: +81 (426) 77-5135

Hello fellow univ. admin from far east!
  
--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Mon Jan 16 20:07:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13509;
	Mon, 16 Jan 95 20:07:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27954;
	Mon, 16 Jan 95 20:03:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27948;
	Mon, 16 Jan 95 20:03:48 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25991;
	Mon, 16 Jan 95 20:03:43 -0800
Date: Mon, 16 Jan 1995 20:03:43 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: "Richard L. Doernberg" <lawrld@law.lawlib.emory.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Passwords
In-Reply-To: <lawrld.2.0601F5D9@law.emory.edu>
Message-Id: <Pine.ULT.3.92.950116200237.8726O-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Yes, create the file "pine.pwd" in the same directory that your pinerc is in.
Then you will be asked if you want your password saved.

-teg

On Sun, 15 Jan 1995, Richard L. Doernberg wrote:

> I am running Pcpine on my local pc. Is there any way that I can avoid entering 
> my password each time that I log on to the mainframe to get my mail? I did not 
> see anything in the configuration options.
> 
> Richard L. Doernberg
> Richard L. Doernberg
> Emory University School of Law
> Atlanta, GA 30322
> Phone: 404 727 6836
> Fax:   404 727 6850
> Email: lawrld@law.emory.edu
> 


From owner-pine-info@cac.washington.edu  Mon Jan 16 20:46:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14282;
	Mon, 16 Jan 95 20:46:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02747;
	Mon, 16 Jan 95 20:43:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02741;
	Mon, 16 Jan 95 20:43:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU5Yw-00038KC; Mon, 16 Jan 95 20:30 PST
To: pine-info@cac.washington.edu
From: joeclark@freenet3.scri.fsu.edu (Joe Clark)
Subject: Re: pico: delete a block, paragraph etc..????
Date: 16 Jan 1995 22:24:46 -0500
Message-Id: <3ffd9u$56e@freenet3.scri.fsu.edu>
References: <3f92v2$lkq@eldborg.rhi.hi.is>

Broddi Reyr Hansen (brh@rhi.hi.is) was reputed to have uttered:

: How can I delete a block of text with pico.  Aka I need to mark the text,
: say few screen fills and then del it!!! 

On mine it's:
CTRL^ - start block marking
CTRL K - cut the marked block
CTRL U - paste the cut.

Joe

-- 
joeclark@freenet.scri.fsu.edu                      Where there's no sense,
Tallahassee, Fla.                                      there's no feeling.
Florida info, original fiction, VW stuff, IVD & kids' links:
<a href="http://freenet3.scri.fsu.edu:81/users/joeclark/index.html">Me</a>


From owner-pine-info@cac.washington.edu  Mon Jan 16 21:21:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15186;
	Mon, 16 Jan 95 21:21:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28981;
	Mon, 16 Jan 95 21:18:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28975;
	Mon, 16 Jan 95 21:18:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU675-00038JC; Mon, 16 Jan 95 21:05 PST
To: pine-info@cac.washington.edu
From: jdulaney@crl.com (John Dulaney)
Subject: Re: .addressbook lost/screwed up! HELP!
Date: 17 Jan 1995 05:03:44 GMT
Message-Id: <3ffj3g$fn4@nntp.crl.com>
References: <3fe7ga$mvb@nntp.crl.com>

	
Problem cleared up thanks to Chris Alfeld.
	Best, John


From owner-pine-info@cac.washington.edu  Mon Jan 16 21:21:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15215;
	Mon, 16 Jan 95 21:21:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03192;
	Mon, 16 Jan 95 21:18:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03186;
	Mon, 16 Jan 95 21:18:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU677-00038KC; Mon, 16 Jan 95 21:05 PST
To: pine-info@cac.washington.edu
From: jdulaney@crl.com (John Dulaney)
Subject: Re: .addressbook lost/screwed up! HELP!
Date: 17 Jan 1995 05:04:11 GMT
Message-Id: <3ffj4b$fn4@nntp.crl.com>
References: <3fe7ga$mvb@nntp.crl.com>

	Problem cured thanks to Chris Alfeld.
	Best, John


From owner-pine-info@cac.washington.edu  Mon Jan 16 23:41:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18636;
	Mon, 16 Jan 95 23:41:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04878;
	Mon, 16 Jan 95 23:28:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04872;
	Mon, 16 Jan 95 23:28:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU8DC-00038QC; Mon, 16 Jan 95 23:20 PST
To: pine-info@cac.washington.edu
From: csaldanh@mae.carleton.ca (Chris Saldanha)
Subject: Specify alternate IMAP login name?
Message-Id: <D2JFvM.8IA@cunews.carleton.ca>
Date: Tue, 17 Jan 1995 07:09:22 GMT

I have several accounts on various networks around our campus. Most have 
my standard username (csaldanh). But, two accounts that I have impose 
numbered accounts, rather than proper usernames.

When I enter pine, it asks me to log into my IMAP server. But, it always 
feeds me my acutal account login name as the default. On those two 
accounts, I have to erase that name, and type in the proper one 
(csaldanh) to log into IMAP.

Is it possible to specify an alternate IMAP login name with pine 3.89? If 
not, could pine be setup to type out some keystrokes (a bunch of 
backspaces, and then "csaldanh") using the "startup keystrokes" default? 
How do I specify the backspaces?

Other than this little annoyance, I must say that I find pine and IMAP 
amazingly useful tools. They have rendered my email management so 
simple. Can't imagine why anyone would use POP...

--Chris
Chris Saldanha                         |  "Can I tell you what makes love
Carleton University (Comp. Sci)        |   so frightening?
csaldanh@mae.carleton.ca  (NeXT/MIME)  |   Its that you don't own it.
http://www.mae.carleton.ca/~csaldanh   |   It owns you."


From owner-pine-info@cac.washington.edu  Tue Jan 17 01:16:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21511;
	Tue, 17 Jan 95 01:16:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02216;
	Tue, 17 Jan 95 01:09:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02210;
	Tue, 17 Jan 95 01:09:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU9jy-00038MC; Tue, 17 Jan 95 00:58 PST
To: pine-info@cac.washington.edu
From: John Furman <johnf@sparc>
Subject: Domain in From: field
Message-Id: <Pine.SV4.3.91.950116184743.16494B-100000@sparc>
Date: Mon, 16 Jan 1995 18:51:25 -0800
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

We are experiencing a problem with the "From:" field in our pine messages.

It reads:

	From: johnf@sparc

Rather than the desired:

	From: johnf@sparc.nic.bc.ca


	The steps we've taken so far are:

	Created 'pine.conf.fixed' in the directory where Pine 3.91 resides.
	Set the 'user-domain=' to the following:

	# Sets domain part of From: and local addresses in outgoing mail.
	user-domain=nic.bc.ca

	Please respond via E-mail any suggestions you might have as to 
	what we're missing.
	
	Regards,
	johnf@sparc.nic.bc.ca


	P.S.  There was a message posted a few days ago, requesting info 
about compiling PINE with GCC under Solaris operating system.  You might 
try the following:

 
Add the following line to the CFLAGS in the makefile.sol in the pine and
pico subdirs.
 
-Dconst=
 
that should do it.
 
 




From owner-pine-info@cac.washington.edu  Tue Jan 17 01:16:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21558;
	Tue, 17 Jan 95 01:16:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06306;
	Tue, 17 Jan 95 01:09:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06300;
	Tue, 17 Jan 95 01:09:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rU9lE-00038PC; Tue, 17 Jan 95 00:59 PST
To: pine-info@cac.washington.edu
From: naegele@worms.fh-rpl.de (Ralf Naegele)
Subject: Re: Where are my TIN saved files?
Date: Mon, 16 Jan 1995 20:56:23
Message-Id: <naegele.4.0014F133@worms.fh-rpl.de>
References: <3edgn0$f42@news.asu.edu> <3eib08$qdm$2@heifetz.msen.com>

In article <3eib08$qdm$2@heifetz.msen.com> mcphail@garnet.msen.com (Michael McPhail) writes:
>From: mcphail@garnet.msen.com (Michael McPhail)
>Subject: Re: Where are my TIN saved files?
>Date: 6 Jan 1995 02:47:36 GMT

>mlk68@imap1.asu.edu wrote:
>:       I am working with a TIN newsreader and can not locate my saved 
>: article files. I go through the process of saving files that I find in 
>: the Internet newsgroups and giving them a name. When I go to the FTP 
>: saved files directory, they aren't there. Please, please help.

>: --
>: Michael Leshowitz
>: mlk68@imap1.asu.edu

>You should have a directory in your home directory called Mail (or mail). 
>Try that location.

No, tin saves files by default in the ~/News directory.
To change this go to the .tin directory and look in the tinrc file

Ralf

-----------------\
Ralf Naegele      \    naegele@she.de 
ShE GmbH           \   naegele@worms.fh-rpl.de
                    \---------------------------


From owner-pine-info@cac.washington.edu  Tue Jan 17 02:07:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23023;
	Tue, 17 Jan 95 02:07:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07000;
	Tue, 17 Jan 95 02:02:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.nada.kth.se by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06994;
	Tue, 17 Jan 95 02:02:05 -0800
Received: from staff.nada.kth.se (staff.nada.kth.se [130.237.225.70])
	by mail.nada.kth.se (8.6.9/8.6.9) with SMTP
	id LAA17433 for <pine-info@cac.washington.edu>;
	Tue, 17 Jan 1995 11:02:01 +0100
Message-Id: <199501171002.LAA17433@mail.nada.kth.se>
X-Authentication-Warning: mail.nada.kth.se: Host staff.nada.kth.se didn't use HELO protocol
To: pine-info@cac.washington.edu
Subject: Controlling header-contents display
Date: Tue, 17 Jan 1995 11:01:57 +0100
From: Peter Svanberg <psv@nada.kth.se>

I would like good tools to control how header contents
are displayed on screen. I see three ways to do this:

(1) Define some configuration language with which you
    can specify how the headers should be used. MH
    has a *bad* - but usable - example of such a language
    in it's "mhl" facility.

(2) Allow the user to filter it himself, i.e. to define a
    filter which, given all the headers (and maybe the screen
    dimensions and display type and...), returns a string which
    should be output to the screen.

(3) Define a configuration parameter "default-message-hdrs" (in
    line with default-composer-hdrs and customized-hdrs) which
    defines which set of headers which normally should be
    displayed (i.e. when FULL HEADERS is off).

I guess at least (3) would be valuable to many but I hope
there are others than me who dislikes the space consuming (and
ugly) <tag>:<value> display of headers, which would like (1)
or (2) or something else.
---
Peter Svanberg, NADA, KTH		    Email: psv@nada.kth.se
Dept of Num An & CS,
Royal Inst of Tech			    Phone: +46 8 790 71 40
S-100 44  Stockholm, SWEDEN		    Fax:   +46 8 790 09 30


From owner-pine-info@cac.washington.edu  Tue Jan 17 02:33:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23680;
	Tue, 17 Jan 95 02:33:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07294;
	Tue, 17 Jan 95 02:28:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from visla.utia.cas.cz by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07288;
	Tue, 17 Jan 95 02:28:01 -0800
Message-Id: <9501171028.AA07288@mx2.cac.washington.edu>
Received: by visla.utia.cas.cz
	(16.7/16.2) id AA15834; Tue, 17 Jan 95 11:26:33 +0100
From: Vladimir Solnicky <vs@utia.cas.cz>
Subject: Re: Controlling header-contents display
To: pine-info@cac.washington.edu
Date: Tue, 17 Jan 95 11:26:32 MET
In-Reply-To: <199501171002.LAA17433@mail.nada.kth.se>; from "Peter Svanberg" at Jan 17, 95 11:01 am
Mailer: Elm [revision: 66.33]

> I would like good tools to control how header contents
> are displayed on screen. I see three ways to do this:
> 
> (1) Define some configuration language with which you
>     can specify how the headers should be used. MH
>     has a *bad* - but usable - example of such a language
>     in it's "mhl" facility.
> 
> (2) Allow the user to filter it himself, i.e. to define a
>     filter which, given all the headers (and maybe the screen
>     dimensions and display type and...), returns a string which
>     should be output to the screen.
> 
> (3) Define a configuration parameter "default-message-hdrs" (in
>     line with default-composer-hdrs and customized-hdrs) which
>     defines which set of headers which normally should be
>     displayed (i.e. when FULL HEADERS is off).
> 
> I guess at least (3) would be valuable to many but I hope
> there are others than me who dislikes the space consuming (and
> ugly) <tag>:<value> display of headers, which would like (1)
> or (2) or something else.
> ---
> Peter Svanberg, NADA, KTH                 Email: psv@nada.kth.se

I would like to have any of the possibilities mentioned above, in case
 (3) I would prefere to say what I don't like to see instead of what I
like to see or, at least:

 (4) Define a configuration parameter which would control if rich
     headers are off or on after starting pine.

Vladimir Solnicky   <vs@utia.cas.cz>
in case of MIME message:  <vs@site.cas.cz>



From owner-pine-info@cac.washington.edu  Tue Jan 17 02:38:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23832;
	Tue, 17 Jan 95 02:38:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03305;
	Tue, 17 Jan 95 02:32:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.nada.kth.se by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03299;
	Tue, 17 Jan 95 02:32:10 -0800
Received: from staff.nada.kth.se (staff.nada.kth.se [130.237.225.70])
	by mail.nada.kth.se (8.6.9/8.6.9) with SMTP
	id LAA18138 for <pine-info@cac.washington.edu>;
	Tue, 17 Jan 1995 11:32:07 +0100
Message-Id: <199501171032.LAA18138@mail.nada.kth.se>
X-Authentication-Warning: mail.nada.kth.se: Host staff.nada.kth.se didn't use HELO protocol
To: pine-info@cac.washington.edu
Subject: Message boundaries and Pipe command
Date: Tue, 17 Jan 1995 11:32:05 +0100
From: Peter Svanberg <psv@nada.kth.se>

There is no boundaries between messages if you do
Apply Pipe. When you do Apply Export, a faked "From " line is
inserted as a boundary(*). Could this be done with Apply
Pipe also, controlled by (for example) a configuration
parameter message-boundaries-in-pipe? (Or all-data-in-pipe,
implying message boundaries *and* all headers.)

(Yes, I want to filter output of message header contents
before printing also... (see my previous note).)

(*) There seems to be a bug in the faking-"From "-line code:
    Missing SPACE between address and date.
---
Peter Svanberg, NADA, KTH		    Email: psv@nada.kth.se
Dept of Num An & CS,
Royal Inst of Tech			    Phone: +46 8 790 71 40
S-100 44  Stockholm, SWEDEN		    Fax:   +46 8 790 09 30


From owner-pine-info@cac.washington.edu  Tue Jan 17 03:00:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24384;
	Tue, 17 Jan 95 03:00:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03543;
	Tue, 17 Jan 95 02:54:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03537;
	Tue, 17 Jan 95 02:54:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUBOv-00038JC; Tue, 17 Jan 95 02:44 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Feature request (cancel in config)
Date: Tue, 17 Jan 1995 10:44:29 +0000
Message-Id: <Pine.SUN.3.91.950117104143.868E-100000@grus.cus.cam.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

In the course of investigating a problem report from one of my users, I 
made some changes to the config, and then realised that I did not want to 
make those changes to that config. However, there was then no way of 
backing out except by reversing those changes. 

In the "good old days" pre 3.90, when such edits were made with an editor,
I always kept a backup copy. Now that things are improved, I wonder if ^C
in Config could exit without saving changes (with of course a prompt). 


=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Tue Jan 17 04:36:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27201;
	Tue, 17 Jan 95 04:36:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08974;
	Tue, 17 Jan 95 04:28:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08968;
	Tue, 17 Jan 95 04:28:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUCtX-00038JC; Tue, 17 Jan 95 04:20 PST
To: pine-info@cac.washington.edu
From: Uptal Khandu Mistry <ssu94148@reading.ac.uk>
Subject: More newsgroups
Date: Tue, 17 Jan 1995 12:13:56 +0000
Message-Id: <Pine.SUN.3.91.950117120740.1964B-100000@ssssgw26>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Using pine i can get access to lots of news groups but only a handful of 
alt. groups.
 
Does anyone know how to access more groups.

Is there a site on the internet that can be accessed by FTP or GOPHER 
that may have more newsgroups?

I think there should be an address for newsgroups, if theyre on the 
internet.

	thanks,



From owner-pine-info@cac.washington.edu  Tue Jan 17 04:44:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27438;
	Tue, 17 Jan 95 04:44:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04946;
	Tue, 17 Jan 95 04:33:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04940;
	Tue, 17 Jan 95 04:33:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUCvB-00038KC; Tue, 17 Jan 95 04:22 PST
To: pine-info@cac.washington.edu
From: vchui@taz.dra.hmg.gb
Subject: HOW TO READ SAVED NEWS
Date: 17 Jan 1995 12:14:47 GMT
Message-Id: <3fgcbn$163@trog.dra.hmg.gb>

Hello,

I have saved some postings from my news reader and would like to read them
as if they are mail folders. Is is possible to use Pine to read saved usenet
news files as mail or news folders?

Thanks in advance
Victor Hui


From owner-pine-info@cac.washington.edu  Tue Jan 17 05:35:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28784;
	Tue, 17 Jan 95 05:35:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09552;
	Tue, 17 Jan 95 05:13:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09546;
	Tue, 17 Jan 95 05:13:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUDT2-00038PC; Tue, 17 Jan 95 04:57 PST
To: pine-info@cac.washington.edu
From: mahdi@vms.cis.pitt.edu
Subject: >>> Any Wizard Out There? <<<
Date: 17 Jan 95 07:56:23 EST
Message-Id: <3fgeqa$7bt@usenet.srv.cis.pitt.edu>

Hi
Dear wizards,

I am using pine in unix to send mails. I have 10 big files named "filex.txt"
where x=1,...,10 stored in directory named "myfiles". So the files are:
"myfiles/file1.txt" to "myfiles/file10.txt"

I want to send these files to an adress via Email (preferably pine) with the
subject heading of each file as "This is the subject of file x" where 
x=1,...,10

Is there any way to automate this? The address that I send is not known
beforehand, so it might be nice if it can be entered as input. The reasons 
that files are separate is because they are big.

Thank you for the solution!
Sincerely Wizard


From owner-pine-info@cac.washington.edu  Tue Jan 17 06:15:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29658;
	Tue, 17 Jan 95 06:15:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06150;
	Tue, 17 Jan 95 06:05:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06144;
	Tue, 17 Jan 95 06:05:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUEKr-00038QC; Tue, 17 Jan 95 05:52 PST
To: pine-info@cac.washington.edu
From: eg6@aixterm1.urz.uni-heidelberg.de (Nina Kirchner)
Subject: Filtering in Pine?
Date: 17 Jan 1995 12:11:22 GMT
Message-Id: <3fgc5a$kh@sun0.urz.uni-heidelberg.de>

Hello,
1. I don't know if it's FAQ, but I'm interested to filter my mail messages in special Folder when I get one.

How does that work?

2. Is it possible to send bcc (blind carbon copy) in pine?

Thanx alot 

Cheers Nina


From owner-pine-info@cac.washington.edu  Tue Jan 17 06:41:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00449;
	Tue, 17 Jan 95 06:41:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10290;
	Tue, 17 Jan 95 06:14:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10284;
	Tue, 17 Jan 95 06:14:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUEVL-00038TC; Tue, 17 Jan 95 06:03 PST
To: pine-info@cac.washington.edu
From: s001pme@discover.wright.edu (Phil Edwards)
Subject: Re: Passwords
Date: 17 Jan 1995 13:55:08 GMT
Message-Id: <3fgi7s$7ob@valhalla.cs.wright.edu>
References: <lawrld.2.0601F5D9@law.emory.edu>

Using the secret identity of <lawrld.2.0601F5D9@law.emory.edu>,
	 it seems Richard L. Doernberg (lawrld@law.emory.edu) sez:

:I am running Pcpine on my local pc. Is there any way that I can avoid entering 
:my password each time that I log on to the mainframe to get my mail? I did not 
:see anything in the configuration options.

I hope not.  This means that any old turkey could read your mail.  Even
if your mainframe was set to look at the PC address instead of a
password, all I have to do is set my PC address to be the same as
yours...and after the resulting crash of the subnets, get logged on
before you do, and whoops, I'm in your mail.

--
Phil Edwards                    | The gods do not protect fools.  Fools
pedwards@valhalla.cs.wright.edu | are protected by more capable fools.
--------------------------------|                          -Larry Niven


From owner-pine-info@cac.washington.edu  Tue Jan 17 06:49:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00643;
	Tue, 17 Jan 95 06:49:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06619;
	Tue, 17 Jan 95 06:37:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gatekeeper.sial.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06613;
	Tue, 17 Jan 95 06:37:21 -0800
Received: from localhost (schuchas@localhost) by gatekeeper.sial.com (8.6.5/8.6.5) id IAA23886; Tue, 17 Jan 1995 08:20:46 -0600
Date: Tue, 17 Jan 1995 08:20:46 -0600 (CST)
From: Stanley Schuchat <schuchas@sial.com>
To: ravindra kahatapitiya <KAHATAPITIYA@rcf.mayo.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: How do I Set HP Laser 4 printer to print Pine
In-Reply-To: <Pine.3.89.1.2-VMS-9.9501161658.A595600959-0100000@HARVEY.MAYO.EDU>
Message-Id: <Pine.BSI.3.91.950117081739.23880A-100000@gatekeeper.sial.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 16 Jan 1995, ravindra kahatapitiya wrote:

> I am able to print stuff out using a computer that is 
> attached to regular dot matrix printer attached to another computer.  The 
> command line when I request to print says "attached-to-ansi" or something 
> like that.  However, this does nothing when I am on a computer that is 
> attached to a laser printer.  PLEASE HELP ME!!!!
> 
I have the same problem with a LaserJet 4, but can print to a LaserJet 
III, LaserJet IIIP, LaserJet II. I also have problems with a DeskJet 320.

_______________________________________________________________________
Stanley Schuchat		|		 Sigma Chemical Company
Analyst, Competition Department	|	3050 Spruce, St Louis, MO 63103
schuchas@spruce.sial.com 	|		    (314)771-5765 x2624




From owner-pine-info@cac.washington.edu  Tue Jan 17 07:13:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01294;
	Tue, 17 Jan 95 07:13:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06907;
	Tue, 17 Jan 95 06:58:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06901;
	Tue, 17 Jan 95 06:58:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUFAr-00038bC; Tue, 17 Jan 95 06:46 PST
To: pine-info@cac.washington.edu
From: hoang1@litwin.com (Ted Hoang)
Subject: HOWTO Delete messages with a specified pattern...
Message-Id: <D2I64p.7rx@litwin.com>
Date: Mon, 16 Jan 1995 14:41:13 GMT

Hi,
Could anyone tell me how to Delete messages with a specified pattern (similar
with ^D in elm) if exists!!!

Thanks in advance,

-- 
---------------------------------------------------------------------------
Ted Hoang               Email:Ted.Hoang@litwin.com      Tel: (713) 267-7122
Litwin Process Automation                               Fax: (713) 267-7908
1250 W. Sam Houston Pkwy S.        Houston, TX 77042


From owner-pine-info@cac.washington.edu  Tue Jan 17 07:20:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01438;
	Tue, 17 Jan 95 07:20:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07129;
	Tue, 17 Jan 95 07:09:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07123;
	Tue, 17 Jan 95 07:09:08 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa17293;
          17 Jan 95 7:56 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA26282; Tue, 17 Jan 1995 15:10:06 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id PAA20132; Tue, 17 Jan 1995 15:07:50 GMT
Date: Tue, 17 Jan 1995 15:07:48 +0000 (GMT)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Nina Kirchner <eg6@aixterm1.urz.uni-heidelberg.de>
Cc: pine-info@cac.washington.edu
Subject: Re: Filtering in Pine?
In-Reply-To: <3fgc5a$kh@sun0.urz.uni-heidelberg.de>
Message-Id: <Pine.LNX.3.91.950117150140.19890A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 17 Jan 1995, Nina Kirchner wrote:

> Hello,
> 1. I don't know if it's FAQ, but I'm interested to filter my mail messages in special Folder when I get one.
> 
> How does that work?

>From the PINE faq:

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Of those mentioned, I have found procmail to be the best of the lot.

The faq for procmail can be found at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

> 
> 2. Is it possible to send bcc (blind carbon copy) in pine?

When you are in the header section of the email, press ^R (control R) and 
this will bring up what pine calls rich headers.  In here, you will find 
a Bcc field.

> 
> Thanx alot 
> 

No problems.

> Cheers Nina
> 

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Tue Jan 17 07:38:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02050;
	Tue, 17 Jan 95 07:38:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07381;
	Tue, 17 Jan 95 07:26:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from picard.isocor.ie by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07375;
	Tue, 17 Jan 95 07:26:50 -0800
Received: (from alan@localhost) by picard.isocor.ie (8.6.9/8.6.9) id PAA04767; Tue, 17 Jan 1995 15:22:48 GMT
Date: Tue, 17 Jan 1995 15:22:47 +0000 (GMT)
From: Alan Byrne <alan@picard.isocor.ie>
To: mahdi@vms.cis.pitt.edu
Cc: pine-info@cac.washington.edu
Subject: Re: >>> Any Wizard Out There? <<<
In-Reply-To: <3fgeqa$7bt@usenet.srv.cis.pitt.edu>
Message-Id: <Pine.PTX.3.91.950117151314.24836A@picard.isocor.ie>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi,
I'm not sure how to do this with pine, but you could try a simple 
shell script something along the following...

#!/bin/sh

echo -n "Enter mail address to send files to: "
read Address

cd myfiles
for i in file*
do
	mailx -s "This is the subject of $i" $Address < $i
echo "sent $i"
done

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

The above script will be dependent on version of un*x you are running, 
and what mailers you have at your disposal, (some local mailers don't 
have a subject line for the command line interface - mailx does).

Regards

Alan Byrne



On 17 Jan 1995 
mahdi@vms.cis.pitt.edu wrote:

> Hi
> Dear wizards,
> 
> I am using pine in unix to send mails. I have 10 big files named "filex.txt"
> where x=1,...,10 stored in directory named "myfiles". So the files are:
> "myfiles/file1.txt" to "myfiles/file10.txt"
> 
> I want to send these files to an adress via Email (preferably pine) with the
> subject heading of each file as "This is the subject of file x" where 
> x=1,...,10
> 
> Is there any way to automate this? The address that I send is not known
> beforehand, so it might be nice if it can be entered as input. The reasons 
> that files are separate is because they are big.
> 
> Thank you for the solution!
> Sincerely Wizard
> 


From owner-pine-info@cac.washington.edu  Tue Jan 17 07:38:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02085;
	Tue, 17 Jan 95 07:38:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11395;
	Tue, 17 Jan 95 07:28:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11389;
	Tue, 17 Jan 95 07:28:13 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id HAA23421 for <pine-info@cac.washington.edu>; Tue, 17 Jan 1995 07:28:11 -0800
Date: Tue, 17 Jan 1995 07:28:13 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Cc: pine-info@cac.washington.edu
Subject: Do we appreciate pine?
In-Reply-To: <Pine.LNX.3.91.950116085044.15700D-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
Message-Id: <Pine.SUN.3.91.950117072441.15760B-100000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 16 Jan 1995, Stuart Tares wrote:

> Totally agree that it is a great program.  Unfortunately unless we let 
> the development team know, it may stop at the next release due to cuts.

Whoa!  Did I read that right?  3.92 may be the last release of pine?

Who do I e-mail to tell them that I *love* pine and I am so happy that 
it's well-written, well-supported and free!  (A very rare combination.)

---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646



From owner-pine-info@cac.washington.edu  Tue Jan 17 07:41:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02182;
	Tue, 17 Jan 95 07:41:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07487;
	Tue, 17 Jan 95 07:32:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07481;
	Tue, 17 Jan 95 07:32:54 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa18802;
          17 Jan 95 8:21 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA00468; Tue, 17 Jan 1995 15:34:21 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id PAA20446; Tue, 17 Jan 1995 15:32:05 GMT
Date: Tue, 17 Jan 1995 15:32:00 +0000 (GMT)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Knute Snortum <knute@teleport.com>
Cc: Stuart.Tares@lhr-sys.bru-ro.DHL.COM, pine-info@cac.washington.edu
Subject: Re: Do we appreciate pine?
In-Reply-To: <Pine.SUN.3.91.950117072441.15760B-100000@linda.teleport.com>
Message-Id: <Pine.LNX.3.91.950117153058.20138A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 17 Jan 1995, Knute Snortum wrote:

> On Mon, 16 Jan 1995, Stuart Tares wrote:
> 
> > Totally agree that it is a great program.  Unfortunately unless we let 
> > the development team know, it may stop at the next release due to cuts.
> 
> Whoa!  Did I read that right?  3.92 may be the last release of pine?
> 
> Who do I e-mail to tell them that I *love* pine and I am so happy that 
> it's well-written, well-supported and free!  (A very rare combination.)

I am sure that the developers will see this just by sending it to 
pine-info.  If that is not the case I am sure they will let you know.

> 
> ---Knute Snortum             Internet:   knute@msi.masi.com
>    MAS, Inc.                    or       knute@teleport.com
> 			    CompuServe:  72144,1646
> 

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Tue Jan 17 07:48:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02407;
	Tue, 17 Jan 95 07:48:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07654;
	Tue, 17 Jan 95 07:39:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07644;
	Tue, 17 Jan 95 07:39:23 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa19229;
          17 Jan 95 8:27 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA01723; Tue, 17 Jan 1995 15:40:46 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id PAA20495; Tue, 17 Jan 1995 15:38:30 GMT
Date: Tue, 17 Jan 1995 15:38:29 +0000 (GMT)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Ted Hoang <hoang1@litwin.com>
Cc: pine-info@cac.washington.edu
Subject: Re: HOWTO Delete messages with a specified pattern...
In-Reply-To: <D2I64p.7rx@litwin.com>
Message-Id: <Pine.LNX.3.91.950117153451.20485A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 16 Jan 1995, Ted Hoang wrote:

> Hi,
> Could anyone tell me how to Delete messages with a specified pattern (similar
> with ^D in elm) if exists!!!
> 

At the Index screen press the following keys:

;		- Go into select mode
T		- T is for text - there are other selection criteria
F		- F is for from - there are other selection criteria
string		- The string which you want to search for
Z		- Zoom in - just to check that you have selected the messages
		  you thought you had
D		- Delete them

Stuart

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Tue Jan 17 07:48:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02436;
	Tue, 17 Jan 95 07:48:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11648;
	Tue, 17 Jan 95 07:40:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11642;
	Tue, 17 Jan 95 07:40:14 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUFpv-00038KC; Tue, 17 Jan 95 07:28 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: HELP: Need SCO binary decoder
Date: Tue, 17 Jan 1995 15:05:23 GMT
Message-Id: <D2K1x2.M1s@ssi.edc.org>
References: <3feliu$mss@garlic.com>

Robert Mann Packaging Co. (rmp@garlic.com) wrote:

: HELP!  I need an SCO decoder for MIME messages.  I don't have a compiler, 
: so I need binaries for an Intel platform.  Can someone point me in the 
: right direction?

Sure.  You can find MIME pack and unpack routines (mpack/munpack) on 
ftp.sco.com, buried somewhere in the Skunkware CD directories.  They 
start at either /Skunk or /pub/Skunk.  A few minutes of nosing around 
should find them for you.  If you completely fail to find them, let me 
know and I'll look them up and get back to you with the full path.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Tue Jan 17 08:35:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04397;
	Tue, 17 Jan 95 08:35:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08535;
	Tue, 17 Jan 95 08:23:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from sun2.nsfnet-relay.ac.uk by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08529;
	Tue, 17 Jan 95 08:22:58 -0800
Via: uk.ac.durham; Tue, 17 Jan 1995 14:02:27 +0000
Received: from venus.dur.ac.uk by durham.ac.uk; Tue, 17 Jan 95 10:49:00 GMT
Received: from hercules (hercules.dur.ac.uk) by venus.dur.ac.uk;
          Tue, 17 Jan 95 10:47:25 GMT
Date: Tue, 17 Jan 1995 10:47:20 +0000 (GMT)
From: Barry Cornelius <Barry.Cornelius@durham.ac.uk>
To: John Furman <johnf@sparc.nic.bc.ca>
Cc: pine-info@cac.washington.edu
Subject: Re: Domain in From: field
In-Reply-To: <Pine.SV4.3.91.950116184743.16494B-100000@sparc>
Message-Id: <Pine.SOL.3.91-941213.950117103228.27159C-100000@hercules.dur.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 2243

> We are experiencing a problem with the "From:" field in our pine messages.
> It reads:
> 	From: johnf@sparc
> Rather than the desired:
> 	From: johnf@sparc.nic.bc.ca

Getting a fully qualified domain name is done by functions in the files
canonicl and domnames in the directory .../pine/osdep of the Pine
distribution.  Both of these files use gethostbyname.  My experience is
that the gethostbyname of SunOS 5.3 (a part of Solaris 2.3) does not give
a FQDN.  I'm not sure but I think that if Pine expects a FQDN, and so
other parts may not work if a FQDN is not obtained.  If I don't know what
happens in SunOS 5.4 (a part of Solaris 2.4) because we do not have that
yet. 

Here is a test program:
---cut here---
#include <sys/types.h>
#include <sys/socket.h>
#include <sys/utsname.h>
#include <netdb.h>
#include <string.h>

int main ()
{
    char hname[512];
    struct hostent *he;
    struct utsname un;

    (void) uname(&un);
    strcpy(hname, un.nodename);
    printf("the name of the machine is: %s\n", hname);

    he = gethostbyname(hname);
    if(he == NULL) {
        printf("unfortunately he is NULL\n");
    } else {
        printf("gethostbyname gives: %s\n", he->h_name);
    }
    return 0;
}
---cut here---

On a SunOS 5.3 computer, I used Sun's unbundled cc:
   cc testdom.c -l nsl -o testdom
   testdom
and got the following:
   the name of the machine is: hercules
   gethostbyname gives: hercules

On a SunOS 4.1.3 computer, I used Sun's cc:
   cc testdom.c -o testdom
   testdom
and got the following:
   the name of the machine is: perseus
   gethostbyname gives: perseus.dur.ac.uk

On an HP-UX 9.01 computer, I used HP's cc:
   cc testdom.c -o testdom
   testdom
and got the following:
   the name of the machine is: pahang
   gethostbyname gives: pahang.dur.ac.uk

Aside: the version of Pine used here in Durham has had patches to the two
files mentioned above to add the ".dur.ac.uk" bit to the end.  Yuk.

--
Barry Cornelius                      Telephone: (0191 or +44 191) 374 4717
Academic Support Group, IT Service,            IT Service Office: 374 2892   
Science Site, University of Durham,                          Fax: 374 3741
Durham, DH1 3LE, UK                   E-mail: Barry.Cornelius@durham.ac.uk



From owner-pine-info@cac.washington.edu  Tue Jan 17 08:55:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05153;
	Tue, 17 Jan 95 08:55:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09060;
	Tue, 17 Jan 95 08:48:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from calafia.uabcs.mx by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09054;
	Tue, 17 Jan 95 08:47:58 -0800
Received: by calafia.uabcs.mx (AIX 3.2/UCB 5.64/4.03)
          id AA09723; Tue, 17 Jan 1995 08:46:56 -0600
Date: Tue, 17 Jan 1995 08:46:56 -0600 (CST)
From: root@calafia.uabcs.mx
To: pine-info@cac.washington.edu
Message-Id: <Pine.A32.3.91.950117084554.8664A-100000@calafia.uabcs.mx>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

SUB PINE-INFO THOMAS HUCKE



From owner-pine-info@cac.washington.edu  Tue Jan 17 09:31:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07409;
	Tue, 17 Jan 95 09:31:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10031;
	Tue, 17 Jan 95 09:24:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10025;
	Tue, 17 Jan 95 09:24:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUHUU-00038KC; Tue, 17 Jan 95 09:14 PST
To: pine-info@cac.washington.edu
From: Alan Robiette <cudaf@csv.warwick.ac.uk>
Subject: Re: JOE 2.5
Date: Tue, 17 Jan 1995 17:14:03 +0000
Message-Id: <Pine.SV4.3.91.950117165939.26373A-100000@crocus>
References: <D224M0.HAo@world.std.com> <D238Is.8vG@world.std.com> <3eteuf$1jk@apakabar.cc.columbia.edu> <3f6lav$jh7@pacemaker.cts>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3f6lav$jh7@pacemaker.cts> 

On 13 Jan 1995, Vbhalla wrote:

> Yeechang Lee (ycl6@namaste.cc.columbia.edu) wrote:
> : Well, I have 2.5 up and running, and it's nice!  (I'm surprised the man
> : page doesn't mention JOETERM, though.)  I can't really say I've noticed
> : much of a difference, but I'm sure it's all there.  More kudos to Joe
> : and JOE!
> : 
> : And for you comp.mail.pine folk who have been looking for a nice,
> : easy-to-use editor that doesn't have Pico's clunks, check out JOE--it
> : fits the bill!
> 
> I am not sure if you know it or not but joe2.6 is now awailable on  ftp.std.com.
> in dir /src/editors as file joe2.6.tar.Z

I too have been impressed by the "superpico" mode of joe2.5 and would
encourage anyone who wants a more powerful - but highly compatible -
alternative to pico to give it a try. 

There are a few omissions from the key mappings in the .jpicorc file
supplied with joe2.5.  I passed these on to the author and they may be
included in 2.6; I haven't had time to check yet.  What may bother more
people is that a (very) few keys in the .jpicorc have different meaning
from those in pico itself: e.g. ^T becomes spell check word only (ESC T is
used to spell check the whole file) and ^@ (or Ctrl-space) is no longer
used to move forward by word. 

I've tweaked my own .jpicorc so that *all* keys have exactly the same
meaning as in pico itself, but one still has all the added functionality. 
If anyone would like a copy let me know; I can post it on this newsgroup
if there is sufficient interest. 

Alan
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Alan Robiette, University of Warwick, Coventry CV4 7AL, UK
Tel +44-1203-524459;  Fax +44-1203-461606;  Email A.Robiette@warwick.ac.uk


From owner-pine-info@cac.washington.edu  Tue Jan 17 09:47:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08078;
	Tue, 17 Jan 95 09:47:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14496;
	Tue, 17 Jan 95 09:39:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14490;
	Tue, 17 Jan 95 09:39:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUHjw-00038KC; Tue, 17 Jan 95 09:30 PST
To: pine-info@cac.washington.edu
From: ii@best.com (Nancy McGough)
Subject: Re: Specify alternate IMAP login name?
Date: 17 Jan 1995 09:04:06 -0800
Message-Id: <ii.790362194@shell1.best.com>
References: <D2JFvM.8IA@cunews.carleton.ca>

csaldanh@mae.carleton.ca (Chris Saldanha) writes:
>Is it possible to specify an alternate IMAP login name with pine 3.89? 

I asked about this before (for 3.91) and the answer was "not yet".


>If not, could pine be setup to type out some keystrokes (a bunch of 
>backspaces, and then "csaldanh") using the "startup keystrokes" default? 
>How do I specify the backspaces?

I haven't been able to figure out how to use "pine -I <initial commands>"
for input strings (other than command keys).  If anyone knows how, please
post.  Of course, what I really want is to be able to write macros for
Pine...


>Other than this little annoyance, I must say that I find pine and IMAP 
>amazingly useful tools. They have rendered my email management so 
>simple. Can't imagine why anyone would use POP...

I agree - soon Pine and IMAP will take over the world!


-- 
 /\_/\    Nancy McGough
( o.o )   Infinite Ink
 > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/


From owner-pine-info@cac.washington.edu  Tue Jan 17 09:48:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08129;
	Tue, 17 Jan 95 09:48:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10376;
	Tue, 17 Jan 95 09:39:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from uu4.psi.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10370;
	Tue, 17 Jan 95 09:39:46 -0800
Received: from msi.UUCP by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP;
        id AA07741 for ; Tue, 17 Jan 95 12:21:38 -0500
Date: Tue, 17 Jan 1995 09:09:24 -0800 (PST)
From: Scott McClure <scott@masi.com>
To: Pine Mail List <pine-info@cac.washington.edu>
Subject: Select options
Message-Id: <Pine.SCO.3.91.950117090637.14432D-100000@MSI.masi.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

In looking at the select options (for a zoom to follow) I find no way to 
select those items addressed to me (+ on index display).  Am I missing 
something?

BTW, please add my name to the list of pine lovers.  You (the development 
team) have done a great job.  I always love seeing public domain stuff 
that's far and away better then the megabuck stuff!  How do we go about 
keeping you 'in business?'

______________________________________________________________________
Scott McClure, CPIM                           Mail: scott@msi.masi.com
MicroAccounting Systems, Inc.                    Voice: (503) 641-4200
Portland, Or                                       Fax: (503) 643-1386



From owner-pine-info@cac.washington.edu  Tue Jan 17 10:28:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09755;
	Tue, 17 Jan 95 10:28:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11321;
	Tue, 17 Jan 95 10:19:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11309;
	Tue, 17 Jan 95 10:19:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUIJ5-00038MC; Tue, 17 Jan 95 10:07 PST
To: pine-info@cac.washington.edu
From: Bob Byers <bob@hsph>
Subject: reading news without an inbox
Date: Tue, 17 Jan 1995 12:52:17 -0500
Message-Id: <Pine.SUN.3.91.950117124438.2222A-100000@hsph>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I would like to have an alternate pine 3.91 .pinerc file that will allow.. 

 1.) read news from a news server,..
 2.) use the expanded-view-of-folders feature,..
 3.) ignore my incoming email INBOX and other mail folders

In other words, when I startup pine with the alternate pinerc file, it
goes directly into the list of subscribed newsgroups, and, when I use 'L'
to change to another group, it auto expands the new folder display. For
the duration of the session, there is no access to my mail folders, only
to news groups. 

Anybody have any hints on how to do this?

-Bob Byers


From owner-pine-info@cac.washington.edu  Tue Jan 17 11:06:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11554;
	Tue, 17 Jan 95 11:06:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12301;
	Tue, 17 Jan 95 10:55:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from lupine.nsi.nasa.gov by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12295;
	Tue, 17 Jan 95 10:55:27 -0800
Received: (from mnewell@localhost) by lupine.nsi.nasa.gov (8.6.9/8.6.9) id NAA15933; Tue, 17 Jan 1995 13:54:17 -0500
Date: Tue, 17 Jan 1995 13:54:13 -0500 (EST)
From: "Michael C. Newell" <mnewell@lupine.nsi.nasa.gov>
To: Ralf Naegele <naegele@worms.fh-rpl.de>
Cc: pine-info@cac.washington.edu
Subject: Re: Where are my TIN saved files?
In-Reply-To: <naegele.4.0014F133@worms.fh-rpl.de>
Message-Id: <Pine.SUN.3.91.950117135302.15061Q-100000@lupine.nsi.nasa.gov>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 16 Jan 1995, Ralf Naegele wrote:

> No, tin saves files by default in the ~/News directory.
> To change this go to the .tin directory and look in the tinrc file

It's also configurable from the "M" menu.  Unfortunately when you change 
the directory [or just about anything else] via the "M" menu you have to 
exit and re-enter TIN for the changes to take effect...

Thanks,

Mike

+--------------------------------------+------------------------------------+
|Mike Newell                           | The opinions expressed herein are  |
|NASA Science Internet Network Systems | my own, and do not necessarily     |
|Sterling Software, Inc.               | reflect those of the NSI program,  |
|MNewell@nsipo.nasa.gov                | Sterling Software, NASA, or anyone |
|+1-202-434-8954                       | else.                              |
+--------------------------------------+------------------------------------+



From owner-pine-info@cac.washington.edu  Tue Jan 17 11:13:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11969;
	Tue, 17 Jan 95 11:13:53 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16527;
	Tue, 17 Jan 95 11:01:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16521;
	Tue, 17 Jan 95 11:01:50 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUIyR-00038MC; Tue, 17 Jan 95 10:49 PST
To: pine-info@cac.washington.edu
From: konradv@welchlink.welch.jhu.edu (Konrad Vandegaer)
Subject: Automated mail
Date: 17 Jan 1995 12:48:45 -0600
Message-Id: <Pine.SOL.3.91.950117134607.3211A-100000@welchlink.welch.jhu.edu>

Where can I find instructions for running an automated mail program?
I am working on a Gateway 2000 and telneting to a Unix host which runs
pine.
Thanks in advance, Konrad Vandegaer


From owner-pine-info@cac.washington.edu  Tue Jan 17 12:06:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15129;
	Tue, 17 Jan 95 12:06:57 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14252;
	Tue, 17 Jan 95 11:58:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14244;
	Tue, 17 Jan 95 11:58:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUJn9-00038QC; Tue, 17 Jan 95 11:42 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Enhancement Suggestions
Date: Tue, 17 Jan 1995 11:24:50 -0800
Message-Id: <Pine.ULT.3.92.950117112245.2155i-100000@shiva1.cac.washington.edu>
References: <3ffb99$8gg@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3ffb99$8gg@cronkite.ocis.temple.edu> 


On 17 Jan 1995, Wet-Sprocket wrote:

> Date: 17 JAN 1995 02:50:17 GMT 
> From: Wet-Sprocket <shrim@astro.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: Re: Enhancement Suggestions 
> 
> Comes here Mr. Steven Feinholz with this opinion in the "comp.mail.pine"
> group in this article on Thu, 12 Jan 1995 00:56:41 GMT:
> 
>  +   2. Is there a way to show the number of messages on a particular
>  +      newsgroup list from the "Expanded List" screen so that I get
>  +      a visual notification of which newsgroups have messages
>  +      without having to Select the newsgroup?
> 
> Good point what would be nicer is if it notifies as to how many new messages,
> as supposed to just the number of messages.
> 

We experimented with something like this for the incoming-folders list for
a while, but decided the overhead was too high at this time to make it
practical.  We will reconsider it in the future when we have more
efficient mechanisms in the low-level (c-client) code... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Tue Jan 17 12:52:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16952;
	Tue, 17 Jan 95 12:52:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19416;
	Tue, 17 Jan 95 12:44:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19410;
	Tue, 17 Jan 95 12:44:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUKcp-00038MC; Tue, 17 Jan 95 12:35 PST
To: pine-info@cac.washington.edu
From: "Giang Nguyen (CS)" <gnguyen@csee.usf.edu>
Subject: How do I run IMAP??
Date: Tue, 17 Jan 1995 15:28:33 -0500
Message-Id: <Pine.SUN.3.91.950117152718.310G-100000@babbage>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

	
Could someone please tell me how to run IMAP.

Thanks!

gnguyen@babbage.csee.usf.edu




From owner-pine-info@cac.washington.edu  Tue Jan 17 12:54:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17033;
	Tue, 17 Jan 95 12:54:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19424;
	Tue, 17 Jan 95 12:44:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19418;
	Tue, 17 Jan 95 12:44:35 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07579;
	Tue, 17 Jan 95 12:44:18 -0800
Date: Tue, 17 Jan 1995 12:44:15 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Knute Snortum <knute@teleport.com>
Cc: Stuart.Tares@lhr-sys.bru-ro.DHL.COM, pine-info@cac.washington.edu
Subject: Re: Do we appreciate pine?
In-Reply-To: <Pine.SUN.3.91.950117072441.15760B-100000@linda.teleport.com>
Message-Id: <Pine.ULT.3.92.950117123605.6494J-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Just to try to clarify the current reality:

 o It is true that there are budget cuts going on at the University of 
   Washington, and...
 o It is possible that some of these cuts may impact some aspects
   of the Pine project; 
 o HOWEVER... I don't expect that 3.92 will be the last version of pine.
 o Even so, we still like to get words of encouragement, even the ones
   that end with "but..." :)

-teg

On Tue, 17 Jan 1995, Knute Snortum wrote:

> On Mon, 16 Jan 1995, Stuart Tares wrote:
> 
> > Totally agree that it is a great program.  Unfortunately unless we let 
> > the development team know, it may stop at the next release due to cuts.
> 
> Whoa!  Did I read that right?  3.92 may be the last release of pine?
> 
> Who do I e-mail to tell them that I *love* pine and I am so happy that 
> it's well-written, well-supported and free!  (A very rare combination.)
> 
> ---Knute Snortum             Internet:   knute@msi.masi.com
>    MAS, Inc.                    or       knute@teleport.com
> 			    CompuServe:  72144,1646
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan 17 13:54:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20587;
	Tue, 17 Jan 95 13:54:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16980;
	Tue, 17 Jan 95 13:44:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16974;
	Tue, 17 Jan 95 13:44:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rULVV-00038MC; Tue, 17 Jan 95 13:32 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: Re: HELP: Need SCO binary decoder
Date: 17 Jan 1995 13:00:11 -0800
Message-Id: <3fhb4r$tds@garlic.com>
References: <3feliu$mss@garlic.com> <D2K1x2.M1s@ssi.edc.org>

Gunther Anderson (gunther@ssi.edc.org) wrote:

: Sure.  You can find MIME pack and unpack routines (mpack/munpack) on 
: ftp.sco.com, buried somewhere in the Skunkware CD directories.  They 
: start at either /Skunk or /pub/Skunk.  A few minutes of nosing around 
: should find them for you.  If you completely fail to find them, let me 
: know and I'll look them up and get back to you with the full path.

THANK-YOU!!!  I found them.  

For the record, the path is /Skunk/bin/*

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


From owner-pine-info@cac.washington.edu  Tue Jan 17 15:53:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26559;
	Tue, 17 Jan 95 15:53:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23868;
	Tue, 17 Jan 95 15:42:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23862;
	Tue, 17 Jan 95 15:42:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUNNE-00038QC; Tue, 17 Jan 95 15:31 PST
To: pine-info@cac.washington.edu
From: Brad <syb3@aber.ac.uk>
Subject: Re: HOWTO Delete messages with a specified pattern...
Date: Tue, 17 Jan 1995 23:26:21 +0000
Message-Id: <Pine.OSF.3.91.950117232502.9133E-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.LNX.3.91.950117153451.20485A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM> 

On Tue, 17 Jan 1995, Stuart Tares wrote:

> At the Index screen press the following keys:
> 
> ;		- Go into select mode
> T		- T is for text - there are other selection criteria
> F		- F is for from - there are other selection criteria
> string		- The string which you want to search for
> Z		- Zoom in - just to check that you have selected the messages
> 		  you thought you had
> D		- Delete them

	Easier than the Z and D at the end is to press A for apply
followed by D for delete--this will delete all the selected mails at once,
and will be a lot easier if you have selected many mails! 

 ___  _                     _a' /(   <.  Simon Bradley, Knight Protector!
/ __><_>._ _ _  ___ ._ _ ~~ _}\ \(  _  ) E-mail: syb3@aber.ac.uk
\__ \| || ' ' |/ . \| ' |      \(._(.)'  Finger: syb3@osfb.aber.ac.uk
<___/|_||_|_|_|\___/|_|_|     ._>. _>.   WWW: http://www.aber.ac.uk/~syb3/


From owner-pine-info@cac.washington.edu  Tue Jan 17 16:36:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28422;
	Tue, 17 Jan 95 16:36:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23882;
	Tue, 17 Jan 95 15:42:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23876;
	Tue, 17 Jan 95 15:42:51 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21577;
	Tue, 17 Jan 95 15:42:50 -0800
Date: Tue, 10 Jan 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Message-Id: <9408241626.AA29044@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="=========="
Subject: Pine Frequently Asked Questions
Resent-Date: Tue, 17 Jan 1995 15:42:32 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950117154230.9523C@shiva1.cac.washington.edu>

--==========
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--==========
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--==========
Content-Description: General Questions About Pine
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: General Questions About Pine


                         GENERAL QUESTIONS ABOUT PINE

------------
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

------------
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

------------
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

------------
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

------------
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
------------
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

------------
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

------------
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--------------
--==========
Content-Description: Basic Usage Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Basic Usage Problems

                        BASIC USAGE PROBLEMS
                                       
------------
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

------------
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
------------
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


------------
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

------------
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

------------
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

------------
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
------------
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
------------
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

------------
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--------------
--==========
Content-Description: Printing
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Printing


                              PRINTING

------------
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


------------
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
------------
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
------------
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

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

--==========
Content-Description: Newsreading and Posting
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Newsreading and Posting

------------
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

------------
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--------------

--==========
Content-Description: Attachments
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Attachments

------------
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

------------
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
------------
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

------------
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.perl";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.c";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++--
--------------

--==========
Content-Description: Folder Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Folder Problems


                            FOLDER PROBLEMS
                                       
------------
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
------------
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
------------
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
------------
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
------------
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
------------
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--------------
--==========
Content-Description: Addressbook Usage and Conversions
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Addressbook Usage and Conversions


                      ADDRESSBOOK USAGE AND CONVERSIONS

------------
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
------------
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--+++++
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="elm-to-pine"

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--+++++--

--------------
                                       
--==========
Content-Description: Installation and Configuration
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Installation and Configuration


                        INSTALLATION AND CONFIGURATION
                                       
------------
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
------------
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
------------
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
------------
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
------------
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
------------
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--------------
                                       
--==========
Content-Description: Platform-specific Issues
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Platform-specific Issues


                         PLATFORM-SPECIFIC ISSUES

------------
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
------------
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
------------
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support.. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--------------
--==========
Content-Description: Bug Reports
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Bug Reports


                                 BUG REPORTS

------------
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

------------
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

------------
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--------------
--==========
Content-Description: Development Info
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Development Info


                               DEVELOPMENT INFO
                                       
------------
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

------------
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
------------
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
------------
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--------------
                                       
--==========--


From owner-pine-info@cac.washington.edu  Tue Jan 17 16:41:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28723;
	Tue, 17 Jan 95 16:41:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25052;
	Tue, 17 Jan 95 16:29:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25046;
	Tue, 17 Jan 95 16:29:50 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUO7c-00038QC; Tue, 17 Jan 95 16:19 PST
To: pine-info@cac.washington.edu
From: Jay Faubion <jfaubion@iohk.com>
Subject: Pine for Windows/DOS
Date: 18 Jan 1995 00:18:13 GMT
Message-Id: <3fhmo5$lfg@news.hk.net>

I've been trying for about four days to get a copy of PINE for Windows/DOS.

Can't get on to ftp.cac.washington.edu!

Does anyone know of another site where I can get it?

THANKS!

Jay Faubion  (Hong Kong)


From owner-pine-info@cac.washington.edu  Tue Jan 17 16:47:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28824;
	Tue, 17 Jan 95 16:47:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21033;
	Tue, 17 Jan 95 16:29:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21027;
	Tue, 17 Jan 95 16:29:48 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUO70-00038MC; Tue, 17 Jan 95 16:18 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: running pine in chroot on SunOS
Date: 18 Jan 1995 00:03:10 GMT
Message-Id: <3fhlru$ak3@cronkite.ocis.temple.edu>

Comes here Mr. Stephen Dorsett with this opinion in the "comp.mail.pine" group
in this article on 13 Jan 1995 15:09:12 -0500:

 +   I am trying to use pine 3.89 as the mail tool of choice for users
 +   on my SunOs 4.1.3 system.

Have you tried the pre-compiled 3.92 binary avail. for Sun-OS 4.1.3 at:

ftp://ftp.cac.washington.edu/pine/unix-bin/pine-bin.sun

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 17 16:54:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29242;
	Tue, 17 Jan 95 16:54:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21411;
	Tue, 17 Jan 95 16:42:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21399;
	Tue, 17 Jan 95 16:42:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUOFS-00038VC; Tue, 17 Jan 95 16:27 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: cmsg cancel <3fhlru$ak3@cronkite.ocis.temple.edu>
Control: cancel <3fhlru$ak3@cronkite.ocis.temple.edu>
Date: 18 Jan 1995 00:13:36 GMT
Message-Id: <3fhmfg$ak3@cronkite.ocis.temple.edu>

Article cancelled from within tin [v1.2 PL2]


From owner-pine-info@cac.washington.edu  Tue Jan 17 19:00:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04077;
	Tue, 17 Jan 95 19:00:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28109;
	Tue, 17 Jan 95 18:57:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28103;
	Tue, 17 Jan 95 18:56:58 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA29921; Tue, 17 Jan 1995 21:56:24 +0500
Date: Tue, 17 Jan 1995 21:56:24 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: Domain in From: field
In-Reply-To: <Pine.SOL.3.91-941213.950117103228.27159C-100000@hercules.dur.ac.uk>
Message-Id: <Pine.SOL.3.90.950117214648.29882A-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 724

On Tue, 17 Jan 1995, Barry Cornelius wrote:

> Getting a fully qualified domain name is done by functions in the files
> canonicl and domnames in the directory .../pine/osdep of the Pine
> distribution.  Both of these files use gethostbyname.  My experience is
> that the gethostbyname of SunOS 5.3 (a part of Solaris 2.3) does not give
> a FQDN.
 
This reply originated from Pine 3.90 running under SunOS 5.3/Solaris 2.3. 
You should see a FQDN (mail.bcpl.lib.md.us) in the "From:" field, unless I
miss my guess.  Why would it work correctly here but not at
sparc.nic.bc.ca (from which the message to which you were replying to 
originated)? 
 
-------------------------------------
Chip Old   <fold@mail.bcpl.lib.md.us>




From owner-pine-info@cac.washington.edu  Tue Jan 17 19:09:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04386;
	Tue, 17 Jan 95 19:09:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28234;
	Tue, 17 Jan 95 19:05:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28228;
	Tue, 17 Jan 95 19:05:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUQXQ-00038VC; Tue, 17 Jan 95 18:54 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: reading news without an inbox
Message-Id: <3fhu6i$ak3@cronkite.ocis.temple.edu>
Date: 18 Jan 95 02:25:22 GMT

Comes here Mr. Bob Byers with this opinion in the "comp.mail.pine" group in this
article on Tue, 17 Jan 1995 12:52:17 -0500:

 +   I would like to have an alternate pine 3.91 .pinerc file that will allow.. 

 +    1.) read news from a news server,..
 +    2.) use the expanded-view-of-folders feature,..
 +    3.) ignore my incoming email INBOX and other mail folders

First make a copy of the current .pinerc to say .pinefornewsrc
Then invoke pine with the duplicate copy of the pine config file with -p flag
(% pine -p .pinefornewsrc)

Go to the Setup/Config screen and then modify the following options to:

inbox-path = <Empty Value>           /* Add value and hit Return immediately */

nntp-server = netnews.at.your.site   /* Add the netnews server address here */

initial-keystroke-list = l,n,v,v     /* List, Next, View, View */


And this feature-list

[ ] - expanded-view-of-folders       /* Leave it unchecked */

Exit and Quit out of Pine. Restart Pine again with this config file and you
will be led into the first newsgroup in your .newsrc file. When once read hit
the tabkey to go to the next group automatically. Hit y to read or n to skip
to the next group that you would like to read. You don't need to go into List
folder screen at all if you have checked the news-read-in-newsrc-order option.

Hope this helps.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Tue Jan 17 20:18:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06211;
	Tue, 17 Jan 95 20:18:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25478;
	Tue, 17 Jan 95 20:14:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from admin.aurora.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25472;
	Tue, 17 Jan 95 20:14:46 -0800
Received: by admin.aurora.edu (5.65/DEC-Ultrix/4.3)
	id AA16519; Tue, 17 Jan 1995 22:15:10 -0600
Date: Tue, 17 Jan 1995 22:15:10 -0600 (CST)
From: Steve Lowe <slowe@admin.aurora.edu>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Header for Read Receipts
Message-Id: <Pine.ULT.3.91.950117221054.16491A-100000@admin.aurora.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I understand how to customize my headers in terms of display when I 
compose a message.  But I am confused on how to setup (require) a receipt 
when a message is read by the receiver.

Thanks in advance.

 - Steve Lowe
   Aurora University               slowe@admin.aurora.edu

PS -- I was under the impression that PINE3.91 would give me this option.




From owner-pine-info@cac.washington.edu  Tue Jan 17 20:29:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06438;
	Tue, 17 Jan 95 20:29:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25616;
	Tue, 17 Jan 95 20:26:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25610;
	Tue, 17 Jan 95 20:26:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rURpZ-00038VC; Tue, 17 Jan 95 20:17 PST
To: pine-info@cac.washington.edu
From: mcphail@garnet.msen.com (Michael McPhail)
Subject: Re: Where are my TIN saved files?
Date: 6 Jan 1995 02:47:36 GMT
Message-Id: <3eib08$qdm$2@heifetz.msen.com>
References: <3edgn0$f42@news.asu.edu>

mlk68@imap1.asu.edu wrote:
: 	I am working with a TIN newsreader and can not locate my saved 
: article files. I go through the process of saving files that I find in 
: the Internet newsgroups and giving them a name. When I go to the FTP 
: saved files directory, they aren't there. Please, please help.

: --
: Michael Leshowitz
: mlk68@imap1.asu.edu

You should have a directory in your home directory called Mail (or mail). 
Try that location.

 =======================================================================
[                                    |                                  ]
[       Mike McPhail                 |     My other computer            ]
[    mcphail@mail.msen.com           |     is a Cray.                   ]
[  aa351@detroit.freenet.org         |                                  ]
[                                    |                                  ]
 =======================================================================


From owner-pine-info@cac.washington.edu  Tue Jan 17 21:23:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07884;
	Tue, 17 Jan 95 21:23:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00363;
	Tue, 17 Jan 95 21:15:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00357;
	Tue, 17 Jan 95 21:15:16 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUSa2-00038jC; Tue, 17 Jan 95 21:05 PST
To: pine-info@cac.washington.edu
From: Ian Russell Ollmann <iano@wong>
Subject: Re: Can I Disable "save messages in read-mail"
Date: Tue, 17 Jan 1995 20:54:57 -0800
Message-Id: <Pine.SGI.3.91.950117205209.23541D-100000@wong>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <1995Jan14.163718.19175@emba.uvm.edu> 



On Sat, 14 Jan 1995, Uri A. Feiner wrote:

> Anyone out there know if there is a way to turn off this question?  An 
> older version of Pine never bothered to ask and that's how I liked it! 
> 
> Thanks.  

	I think that if you check the auto-move-read-msgs option under
Settings/Config that it should quit asking you this question. The help for
that option is shown below (as appears in pine 3.91). I think you can 
probably also get to this by editing you .pinerc, if you prefer.


                      		  Ian




                     FEATURE: auto-move-read-msgs 

This feature controls an aspect of Pine's behavior upon quitting.  If set,
and the "read-message-folder" variable is also set, then Pine will
automatically transfer all read messages to the designated folder and mark
them as deleted in the INBOX.  Messages in the INBOX marked with an "N" 
(meaning New, or unseen) are not affected.  <End of help on this topic>



From owner-pine-info@cac.washington.edu  Tue Jan 17 21:44:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08432;
	Tue, 17 Jan 95 21:44:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26859;
	Tue, 17 Jan 95 21:40:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26853;
	Tue, 17 Jan 95 21:40:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUSyK-00038lC; Tue, 17 Jan 95 21:30 PST
To: pine-info@cac.washington.edu
From: dsacks@primenet.com (Dennis Sacks)
Subject: Pine ported to Sol 2.3?
Date: 18 Jan 1995 05:23:28 GMT
Message-Id: <3fi8kh$ch@news.primenet.com>

Pine 3.91 doesn't seem to say anything about being able to be built
for solaris 2.x. Am I missing something, or must I get a version of Pine
ported to Solaris?

Thanks,

Dennis
dsacks@primenet.com



From owner-pine-info@cac.washington.edu  Tue Jan 17 22:30:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09673;
	Tue, 17 Jan 95 22:30:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27571;
	Tue, 17 Jan 95 22:26:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27565;
	Tue, 17 Jan 95 22:26:56 -0800
Received: by hobbes.twntpe.cdc.com; Wed, 18 Jan 95 14:25:28 -0800
Date: Wed, 18 Jan 1995 14:25:28 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Dennis Sacks <dsacks@primenet.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Pine ported to Sol 2.3?
In-Reply-To: <3fi8kh$ch@news.primenet.com>
Message-Id: <Pine.SOL.3.91.950118142051.3406B-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 18 Jan 1995, Dennis Sacks wrote:

> Pine 3.91 doesn't seem to say anything about being able to be built
> for solaris 2.x. Am I missing something, or must I get a version of Pine
> ported to Solaris?

	Pine builds with ease for Solaris 2.x

	You will need to add -Dconst= to the CFLAGS in makefile.sol....and
then simply type "build sol".

	A note of caution....make sure that SPARCWorks/SUNWspro/bin is in
your PATH prior to /usr/ucb and do not have /usr/ucbinclude in your 
LD_LIBRARY_PATH.

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Tue Jan 17 22:57:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10197;
	Tue, 17 Jan 95 22:57:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01771;
	Tue, 17 Jan 95 22:52:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01765;
	Tue, 17 Jan 95 22:52:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUU2t-00038lC; Tue, 17 Jan 95 22:39 PST
To: pine-info@cac.washington.edu
From: mnewell@gatecoms.gatecom.com (Matt Newell)
Subject: Mailing List
Date: 18 Jan 1995 04:36:01 GMT
Message-Id: <3fi5rh$ehn@gatecoms.gatecom.com>

	Is it possible with Pine (Unix v3.90) to mail out to a large list of
users with pine. (Names kept in a file, or the like) This isn't a real
regular thing, and not worth starting a Majordomo or Listserv over, but still,
can't be typed in every time. Is there any other solution not using pine for a
SysVR4 system? Sorry if this has been asked before, any help will of course be
apricated.

     Thanks bunches,
     Matt

**   Matt Newell                             mnewell@gatecoms.gatecom.com   **
------------------------------------------------------------------------------
Any man's death diminishes me, because I am involved in mankind. Therefore,
never send to know for whom the bell tolls, It tolls for thee.
                                                              -John Donne


From owner-pine-info@cac.washington.edu  Tue Jan 17 23:24:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10742;
	Tue, 17 Jan 95 23:24:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02133;
	Tue, 17 Jan 95 23:22:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02127;
	Tue, 17 Jan 95 23:22:05 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA00582; Wed, 18 Jan 1995 02:21:36 +0500
Date: Wed, 18 Jan 1995 02:21:36 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: "List (pine-info)" <pine-info@cac.washington.edu>
Subject: Pine 3.91 SOL Oddities
Message-Id: <Pine.SOL.3.91.950118020649.555B-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1079

We've just installed Pine 3.91 SOL (replacing 3.90 SOL) and there are a 
couple of odd things I can't figure out:
 
(1) Ctrl-Space does not advance the cursor one full word like it is
supposed to.  In 3.91 it does nothing.  In 3.90 it inserted a space.  I
use 3.90 and 3.91 under Xenix on an old account that I still have, and
Ctrl-Space works perfectly there.  Should I be looking for a problem in
Pine, or in some system configuration? 
 
(2) If the user's TERM variable is set to vt100, the reverse video
displayed by Pine and Pico appears to be boldfaced as well, making it very
clunky and difficult to read.  If the TERM variable is reset to vt102, the
reversee video is crisp and clear.  Again, this is not what I was used to
under Xenix.  Pine problem or system problem? 
 
--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA



From owner-pine-info@cac.washington.edu  Tue Jan 17 23:28:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10795;
	Tue, 17 Jan 95 23:28:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28367;
	Tue, 17 Jan 95 23:25:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28361;
	Tue, 17 Jan 95 23:25:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUUaz-00038nC; Tue, 17 Jan 95 23:14 PST
To: pine-info@cac.washington.edu
From: Bob Burge <burger@cspo.queensu.ca>
Subject: Archiving folders/Future reference
Date: Tue, 17 Jan 1995 22:49:30 -0600
Message-Id: <Pine.SOL.3.91.950117224321.559A-100000@cspo>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Howdy!  I'm looking for a useful way to archive my folders (by putting
them on my pc), while leaving the opportunity to view them (in pine folder
format) in the future.  My concern is not with space on either the unix 
or pc, but with being able to read them on the pc at a later date.

Is there a standalone reader for pine folders?

Thanks,
Bob


From owner-pine-info@cac.washington.edu  Tue Jan 17 23:29:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10816;
	Tue, 17 Jan 95 23:29:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02165;
	Tue, 17 Jan 95 23:25:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02159;
	Tue, 17 Jan 95 23:25:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUUcl-00038lC; Tue, 17 Jan 95 23:16 PST
To: pine-info@cac.washington.edu
From: jsweet@cory.eecs.berkeley.edu (Julian Sweet)
Subject: multiple receipients
Date: Tue, 17 Jan 1995 22:47:03
Message-Id: <jsweet.2.0016C918@cory.eecs.berkeley.edu>

I can't seem to figure out how I can send one letter to multiple recipients. 
Namely, one's that I pick out of my address book.


From owner-pine-info@cac.washington.edu  Tue Jan 17 23:37:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11014;
	Tue, 17 Jan 95 23:37:52 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28492;
	Tue, 17 Jan 95 23:34:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28486;
	Tue, 17 Jan 95 23:34:19 -0800
Received: by hobbes.twntpe.cdc.com; Wed, 18 Jan 95 15:32:48 -0800
Date: Wed, 18 Jan 1995 15:32:47 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Matt Newell <mnewell@gatecoms.gatecom.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Mailing List
In-Reply-To: <3fi5rh$ehn@gatecoms.gatecom.com>
Message-Id: <Pine.SOL.3.91.950118152924.9161A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 18 Jan 1995, Matt Newell wrote:

> 	Is it possible with Pine (Unix v3.90) to mail out to a large list of
> users with pine. (Names kept in a file, or the like) This isn't a real
> regular thing, and not worth starting a Majordomo or Listserv over, but still,
> can't be typed in every time. Is there any other solution not using pine for a
> SysVR4 system? Sorry if this has been asked before, any help will of course be
> apricated.

	Why not make use of your aliases file?  On some systems this is in
/usr/lib and on other is /etc/mail.  You can put in a line similar to:

tp.all: :include:/usr/spool/lists/alltps

	Then, in the file /usr/spool/lists/alltps put your list of addresses.

	You will need to run "newaliases" ... and then you can send to 
tp.all and out it goes....to the list....

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 18 01:56:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14749;
	Wed, 18 Jan 95 01:56:10 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00460;
	Wed, 18 Jan 95 01:48:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00454;
	Wed, 18 Jan 95 01:48:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUWmD-00038oC; Wed, 18 Jan 95 01:34 PST
To: pine-info@cac.washington.edu
From: weber@library.wustl.edu (Grant Weber)
Subject: Re: Pine for Windows/DOS
Date: 18 Jan 1995 06:43:03 GMT
Message-Id: <3fid9n$rrs@newsreader.wustl.edu>
References: <3fhmo5$lfg@news.hk.net>

Jay Faubion (jfaubion@iohk.com) wrote:
: I've been trying for about four days to get a copy of PINE for Windows/DOS.

: Can't get on to ftp.cac.washington.edu!

: Does anyone know of another site where I can get it?

I've got it on anonymous FTP at the following site:

	ftp://notis.wustl.edu/pub/Launchpad.helpers

or for the complete distribution of all versions, you can try

	ftp://wuarchive.wustl.edu/packages/mail/pine


--
Grant
=========================================================================
Grant Weber				One Brookings Drive
Library Systems				Campus Box 1061	
Washington University			St. Louis, MO  63130-4899

Grant-Weber@library.wustl.edu		Voice: (314) 935-5497	
http://library.wustl.edu/~weber/	Fax  : (314) 935-4045
=========================================================================


From owner-pine-info@cac.washington.edu  Wed Jan 18 02:38:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15634;
	Wed, 18 Jan 95 02:38:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04526;
	Wed, 18 Jan 95 02:29:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04520;
	Wed, 18 Jan 95 02:29:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUXOT-00038oC; Wed, 18 Jan 95 02:13 PST
To: pine-info@cac.washington.edu
From: roland@spinnaker.rhein.de (Roland Rosenfeld)
Subject: Re: Smaller binary for Pine 3.91!
Date: 16 Jan 1995 19:36:57 +0100
Message-Id: <3feec9$4on@spinnaker.rhein.de>
References: <parastat.790203763@alpha.it.teithe.gr>

Hi Savas!

Savas Parastatidis (parastat@alpha.it.teithe.gr) wrote:

> I have already compiled Pine 3.91 on a DEC3100 Alpha system running OSF1
> v1.3. My problem is that the executable is near 3.3Mb. I want it to be
> smaller. So my thought was not to include some features of Pine, like
> motd, mh. 

> I found that I can exclude these by erasing their names from the
> DEFAULTDRIVERS variable of the Makefile. But I don't know what every
> driver is for. Can anyone help me with this?

> Any other way of reducing the binary size of pine is more than welcome. 

I edited all makesfiles and replaced the compiler-flags "-g -O" with
"-fomit-frame-pointer -O2" and the linux-binary is only 877572 bytes
(after stripping it). I didn't remove any of the drivers!

Bye

	Roland

-- 
  * Internet: roland@spinnaker.rhein.de * Fido: 2:2450/111.13 *


From owner-pine-info@cac.washington.edu  Wed Jan 18 05:24:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20253;
	Wed, 18 Jan 95 05:24:23 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03218;
	Wed, 18 Jan 95 05:12:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03212;
	Wed, 18 Jan 95 05:12:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUa1F-00038KC; Wed, 18 Jan 95 05:01 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Alias expander for pine addressbook?
Date: 18 Jan 95 12:52:02 GMT
Message-Id: <ellis.790433522@gmi.edu>

As someone who prefers to use pine as my MUA and nn as my reader, I would
like to be able to have the pine aliases available to me from inside nn.  nn
seems to be able to use an external alias expander, and people have even
re-written aux (the nn posting/mailing script) to use elm aliases, or to use
elm as the mailer.  While elm can be used as a mailer at the UNIX prompt,
pine does not seem to support this mode.  

I think I would be satisfied to simply be able to use ~/.addressbook to
expand pine aliases.  I thought it would be a simple hack with cut or awk in
a shell script, resetting the field separation character to TAB.  However
the entries do not appear one per line in the .addressbook.  By quickly
reading the code for handling the addressbook, I think there are 4 TAB
separated fields per entry, with CR having no significance.  This is
difficult to handle with cut and I cannot figure how to get a native nawk
script to open a file other than stdin or one given on the commandline.  I
could probably write the nawk code in a code file, call nawk from a
shellscript with an input file and nawk code file and get it done that way,
but that would be two pieces to maintain, while I really want to keep this
to one piece other than ~/.addressbook.

I have thought about "borrowing" the pieces to do this from pine putting
them together into a C program, but this is turning into more trouble than I
have time for.

Has anyone written a simple alias handler that will take as an arg or on
stdin the alias and spit out the mail address on the stdout?



-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Wed Jan 18 06:53:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23316;
	Wed, 18 Jan 95 06:53:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08201;
	Wed, 18 Jan 95 06:45:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08195;
	Wed, 18 Jan 95 06:45:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUbSN-00038JC; Wed, 18 Jan 95 06:33 PST
To: pine-info@cac.washington.edu
From: Uptal Khandu Mistry <ssu94148@reading.ac.uk>
Subject: Configuring Pine
Date: Wed, 18 Jan 1995 14:24:32 +0000
Message-Id: <Pine.SUN.3.91.950118142255.26220B-100000@ssssgw25>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Does anyone know how to configure pine to look at other news sites, and do
you know the addresses of any good news sites?

What does the  *  and the  []  do in  *{example.abc.edu/nntp}board-name[] , 
and how do you know what name to call the news group board? 
        thanks,




From owner-pine-info@cac.washington.edu  Wed Jan 18 07:33:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24675;
	Wed, 18 Jan 95 07:33:37 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08339;
	Wed, 18 Jan 95 06:52:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from visla.utia.cas.cz by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08333;
	Wed, 18 Jan 95 06:52:06 -0800
Received: by visla.utia.cas.cz
	(16.7/16.2) id AA23654; Wed, 18 Jan 95 15:50:41 +0100
Date: Tue, 10 Jan 95 15:40:48 -0800
From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Message-Id: <9408241626.AA29044@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="=========="
Subject: Pine Frequently Asked Questions
Resent-Date: Tue, 17 Jan 1995 15:42:32 -0800 (PST)
Resent-From: David L Miller <dlm@cac.washington.edu>
Resent-To: pine-info@cac.washington.edu
Resent-Message-Id: <Pine.ULT.3.92.950117154230.9523C@shiva1.cac.washington.edu>
Apparently-To: <vs@visla.utia.cas.cz>
Resent-Date: Wed, 18 Jan 1995 15:50:33 +0100 (MET)
Resent-From: Vladimir Solnicky <vs@utia.cas.cz>
Resent-To: vs@site.cas.cz
Resent-Message-Id: <Pine.HPP.3.91.950118155032.23650A@visla.utia.cas.cz>

--==========
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--==========
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--==========
Content-Description: General Questions About Pine
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: General Questions About Pine


                         GENERAL QUESTIONS ABOUT PINE

------------
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

------------
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

------------
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

------------
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

------------
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
------------
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

------------
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

------------
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--------------
--==========
Content-Description: Basic Usage Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Basic Usage Problems

                        BASIC USAGE PROBLEMS
                                       
------------
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

------------
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
------------
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


------------
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

------------
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

------------
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

------------
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
------------
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
------------
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

------------
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--------------
--==========
Content-Description: Printing
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Printing


                              PRINTING

------------
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


------------
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
------------
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
------------
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

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

--==========
Content-Description: Newsreading and Posting
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Newsreading and Posting

------------
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

------------
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--------------

--==========
Content-Description: Attachments
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Attachments

------------
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

------------
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
------------
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

------------
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.perl";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++
Content-Type: MESSAGE/EXTERNAL-BODY;
	name="sun-to-mime.c";
	site="cs.utk.edu";
	access-type=ANON-FTP;
	directory="pub/MIME";
	mode="ASCII"

Content-type: TEXT/PLAIN

--+++++--
--------------

--==========
Content-Description: Folder Problems
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Folder Problems


                            FOLDER PROBLEMS
                                       
------------
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
------------
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
------------
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
------------
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
------------
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
------------
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--------------
--==========
Content-Description: Addressbook Usage and Conversions
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Addressbook Usage and Conversions


                      ADDRESSBOOK USAGE AND CONVERSIONS

------------
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
------------
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
------------
Content-Type: MULTIPART/MIXED; BOUNDARY="+++++"

--+++++
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--+++++
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="elm-to-pine"

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--+++++--

--------------
                                       
--==========
Content-Description: Installation and Configuration
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Installation and Configuration


                        INSTALLATION AND CONFIGURATION
                                       
------------
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
------------
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
------------
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
------------
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
------------
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
------------
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--------------
                                       
--==========
Content-Description: Platform-specific Issues
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Platform-specific Issues


                         PLATFORM-SPECIFIC ISSUES

------------
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
------------
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
------------
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support.. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--------------
--==========
Content-Description: Bug Reports
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Bug Reports


                                 BUG REPORTS

------------
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

------------
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

------------
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--------------
--==========
Content-Description: Development Info
Content-Type: MULTIPART/DIGEST; BOUNDARY="----------"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Development Info


                               DEVELOPMENT INFO
                                       
------------
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

------------
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
------------
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
------------
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--------------
                                       
--==========--



From owner-pine-info@cac.washington.edu  Wed Jan 18 08:04:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25838;
	Wed, 18 Jan 95 08:04:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05807;
	Wed, 18 Jan 95 07:56:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05801;
	Wed, 18 Jan 95 07:56:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUcbQ-00038JC; Wed, 18 Jan 95 07:47 PST
To: pine-info@cac.washington.edu
From: idjfc@imap1.asu.edu
Subject: printing problems
Date: 6 Jan 1995 02:48:17 GMT
Message-Id: <3eib1h$cd3@news.asu.edu>

I am using Pine 3.91 (a newby to the net) and am having problems getting 
my printer to work with it. The printer worked fine with the previous 
version of Pine.  I am using an IBM Compatable, 486DX, 8 meg of ram, 
TCP/IP, trumpet telnet.  The modem is a Practical Peripheral 28.8.  I use 
a PPP connection to a SPARCSERVER 1000 running Solaris 2.3.  While in 
Pine, when I type "y" for print, a message "Caption Onsing" appears in the 
lower right hand corner of the screen, and everything is dumped to my 
hard disk.  I have read through all the Pine FAQs and can't come up with 
anything that closely matches my problem.  The printer is a Panasonic 
KX-P2123 which emulates an IBM Proprinter X24E.  It is a 24-pin.  Of 
course after things are dumped into the hard disk, I can then print it 
out fine, but it is an inconvenience, and I'm not too pleased about 
something just dumping to the hard disk without my control.  Under the 
Pine printer options, I have selected the "ansi" selection.  Requesting 
help within the Pine program doesn't give me mush, just tells me to make 
a selection.  I work within both MS-DOS 6.22 and Windows 3.1 and the 
problem is the same under both platforms.  The printer works fine on-line 
with everything else; i.e., netscape, HGopher, etc.
     I would greatly appreciate any information.  Thank you. - JB    


From owner-pine-info@cac.washington.edu  Wed Jan 18 08:34:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27131;
	Wed, 18 Jan 95 08:34:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06243;
	Wed, 18 Jan 95 08:16:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from minerva.cis.yale.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06237;
	Wed, 18 Jan 95 08:16:44 -0800
Received: from mercury.cis.yale.edu by minerva.cis.yale.edu with SMTP id AA18780
  (5.67a/IDA-1.5 for <pine-info@cac.washington.edu>); Wed, 18 Jan 1995 11:16:38 -0500
Received: by mercury.cis.yale.edu id AA18785
  (5.67a/IDA-1.5 for pine-info@cac.washington.edu); Wed, 18 Jan 1995 11:16:36 -0500
Date: Wed, 18 Jan 1995 11:16:35 -0500 (EST)
From: Ruth M Sanchez <ruths@minerva.cis.yale.edu>
X-Sender: ruths@mercury
To: pine-info@cac.washington.edu
Subject: mail
Message-Id: <Pine.SOL.3.91.950118111536.18567A-100000@mercury>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Unsubsribe pine-info


From owner-pine-info@cac.washington.edu  Wed Jan 18 08:38:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27298;
	Wed, 18 Jan 95 08:38:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09886;
	Wed, 18 Jan 95 08:26:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09880;
	Wed, 18 Jan 95 08:26:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUd2P-00038aC; Wed, 18 Jan 95 08:15 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Divers suggestions and questions.. retrying!
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950118155511.15242A-100000@bambix.icce.rug.nl>
Mime-Version: 1.0
Date: Wed, 18 Jan 1995 15:04:51 GMT

Hiya Peeps,

I didn't receive much of a reply when I tried this before, so here goes again.
Though I am extremely pleased with Pine, here's a couple of questions /
suggestions:

    1. Can I turn off reverse video _completely_? That is, not only for
    selected articles or mails (I've figured that one out), but also for e.g.
    the main menu?

    I'd much prefer underlining.. even "man" can do that! So here's a
    suggestion: make two configurable settings, "start standout" and "end
    standout". Could be configured as start/end boldface, but also as other
    stuff! E.g., under an xterm I could then define standout text to be
    colored.

    2. Pine insists on VT100 codes for function keys, which is definitely
    wrong behavior. I compiled pine with /etc/termcap support, which to my
    knowledge means that Pine should check that file and match incoming keys
    to symbols. E.g., if my /etc/termcap says that :k1 is ^[[12~, then Pine
    should convert escape, [, 1, 2, and a tilde to a symbolic code for F1.
    That's how /etc/termcap works.. Same argument goes for arrow keys.

    3. Some of nn's behavior for news reading is extremely useful, e.g. the X
    key to mark an entire group as "read" and skip to the next one. I'd love
    that in Pine! Any suggestions on how to emulate this?

    4. I got my nn configured in such a way that only the _subjects_ of
    articles are retrieved. When I actually want to _read_ the article, the
    body is retrieved. This saves masses of network traffic.

    How do I get Pine to act in this way ?!

Thanks for listening.. any suggestions are welcome.

--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
You might be a redneck if..
Your father executes the "pull my finger" trick during Christmas dinner.



From owner-pine-info@cac.washington.edu  Wed Jan 18 09:13:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29560;
	Wed, 18 Jan 95 09:13:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10733;
	Wed, 18 Jan 95 09:00:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from magellan.cloudnet.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10727;
	Wed, 18 Jan 95 09:00:05 -0800
Received: by magellan.cloudnet.com (931110.SGI/930416.SGI)
	for pine-info@cac.washington.edu id AA01555; Wed, 18 Jan 95 10:59:38 -0600
Date: Wed, 18 Jan 1995 10:59:37 -0600 (CST)
From: Metal Head <metal@magellan.cloudnet.com>
To: pine-info@cac.washington.edu
Subject: subscribe pine info
Message-Id: <Pine.SGI.3.91.950118105918.1547A-100000@magellan.cloudnet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

subscribe pine info

metal@geeks.org                      http://www.winternet.com/~metal
--------------------------------------------------------------------        
Res ipsa loquitor. (Let the good times roll.) Dr. Hunter S. Thompson 
*** O U T L A W S  On The  E L E C T R O N I C  F R O N T I E R **** 
***** Committed to Free Public Internet Access for World Peace ***** 
"When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!" JPB




From owner-pine-info@cac.washington.edu  Wed Jan 18 09:28:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00301;
	Wed, 18 Jan 95 09:28:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07821;
	Wed, 18 Jan 95 09:19:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from minerva.cis.yale.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07809;
	Wed, 18 Jan 95 09:19:35 -0800
Received: from mercury.cis.yale.edu by minerva.cis.yale.edu with SMTP id AA06959
  (5.67a/IDA-1.5 for <Pine-info@cac.washington.edu>); Wed, 18 Jan 1995 12:19:30 -0500
Received: by mercury.cis.yale.edu id AA27567
  (5.67a/IDA-1.5 for Pine-info@cac.washington.edu); Wed, 18 Jan 1995 12:19:27 -0500
Date: Wed, 18 Jan 1995 12:19:26 -0500 (EST)
From: Ruth M Sanchez <ruths@minerva.cis.yale.edu>
X-Sender: ruths@mercury
To: Pine-info@cac.washington.edu
Subject: Re: mail
In-Reply-To: <Pine.SOL.3.91.950118111536.18567A-100000@mercury>
Message-Id: <Pine.SOL.3.91.950118121742.27180A-100000@mercury>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Pine Frequently Asked Questions: General Questions about Pine.
Unsubscribe pine-info


From owner-pine-info@cac.washington.edu  Wed Jan 18 09:35:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00787;
	Wed, 18 Jan 95 09:35:10 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07972;
	Wed, 18 Jan 95 09:26:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07966;
	Wed, 18 Jan 95 09:26:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUe0l-00038KC; Wed, 18 Jan 95 09:17 PST
To: pine-info@cac.washington.edu
From: rrogers@minnie.imd.nrc.ca (Rick Rogers)
Subject: FAQ?? or VMS PINE??
Date: 6 Jan 95 09:35:30 NDT
Message-Id: <1995Jan6.093530.1@minnie.imd.nrc.ca>

Hi all,

   Where is the FAQ for this group (assuming there is one), I can't
find it as far back as my feed has.

   If there isn't a FAQ I'm specifically looking for info on PINE
for VMS to work with SMTP.

Thanks,

Rick


From owner-pine-info@cac.washington.edu  Wed Jan 18 10:00:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02277;
	Wed, 18 Jan 95 10:00:54 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12281;
	Wed, 18 Jan 95 09:46:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12275;
	Wed, 18 Jan 95 09:46:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUeIK-00038JC; Wed, 18 Jan 95 09:35 PST
To: pine-info@cac.washington.edu
From: J.S.Peatfield@amtp.cam.ac.uk (Jon Peatfield)
Subject: Re: problem when tmp directory is full
Date: 18 Jan 1995 17:10:11 GMT
Message-Id: <J.S.PEATFIELD.95Jan18171011@kro.amtp.cam.ac.uk>
References: <J.S.PEATFIELD.95Jan11134038@kro.amtp.cam.ac.uk>
In-Reply-To: niebank@ftsu00.ee.TU-Berlin.DE's message of Thu, 12 Jan 1995 10:10:27 GMT

> Using pine 3.91 on our Sun Sparc's (SunOS4.1.3) an error message flashes 
> only a very short moment, when the file system is full (not only the tmp-area).
> Therefore it's sometimes a game of luck if you take notice of it or not.
> I'd like pine to double-beep and to wait until I took notice on the error/
> warning which occured (typing a key to continue). 
> The pine team may consider it as a suggestion for the next release.

I don't see any warning flash up for any time at all.  Still I agree
that it should pause and wait for the user to acknowledge the error
before carrying on.  Some people don't notice brief messages.

As I said in another article:

> After discovering the TMPDIR variable, I filled up a filesystem and
> pointed TMPDIR at it from a Sun4 (sos4) and got the same behavour as
> on the SGI.
> 
> The relevant bit of the debug log (-d99) is:
> 
> > Sending mail...
> > q_status_message, Count 2, "Sending mail....."
> > output_message(Sending mail.....)
> > call_mailer: handing off
> > === calling sendmail ===
> > -- pine_rfc822_output
> > -- pine_encode_body: 0
> > -- pine_rfc822_output_body: 0
> > -- pine_rfc822_output_body: segment 0 bytes
> > -- gf_reset local_nvtnl
> > -- gf_pipe: done.
> > Send command "( ( /usr/lib/sendmail -oi -oem -t ; /bin/rm -f /home/fenris/jp107//pinesend001683 ) < /home/fenris/jp107//pinesend001683 & )"
> > PID: 1701, COMMAND: ( ( /usr/lib/sendmail -oi -oem -t ; /bin/rm -f /home/fenris/jp107//pinesend001683 ) < /home/fenris/jp107//pinesend001683 & )
> > Send SUCCESSFUL.
> > To: jp107@cus
> > Subject: This is a stupid test
> > Message ID: <Pine.SUN.3.91.950111162331.1683B-100000@kro.amtp.cam.ac.uk>
> > 
> > Writing Fcc
> > q_status_message, Count 1, "Writing Fcc..."
> > output_message(Writing Fcc...)
> 
> The directory /home/fenris/jp107/ had no space left yet I got no error
> and the message wasn't sent.  (In fact sendmail sent a null message
> which then bounced to postmaster but this isn't helpful.)
> 
> Does this give any clues as to the problem?
> 

In pine3.91/pine/osdep/sendmail in append_mesage2() the following code
tests for an error writing the message to be sent:

>     if(!rv){
>         save_errno = errno;
>         truncate(filename, start_of_append);
>         q_status_message2(1, 2, 4, "\007Error \"%s\" writing \"%s\"",
>                           error_description(save_errno), pretty_fn(filename));
>         dprint(1, (debugfile, "Error writing %s: %s\n",
>                    filename, error_description(save_errno)));
>         return(-1);
>     }
> 

Thus I should have had a log of an error in the .pinedebug file but I
saw none.

I have spotted one bug in this area in that no checks are performed on
the return code from fclose().  If (for eg.) you are sending a message
short enough to fit in the stdio buffers or are talking accross NFS
(as I was in my test) then it may well fail horribly.

>     if(!filename || !(folder_stream = fopen(filename, "w"))){
>         q_status_message2(1, 2, 4, "\007Error opening file \"%s\", %s",
> 			  filename ? pretty_fn(filename) : "<NO FILE NAME>",
> 			  error_description(errno));
>         return(-1);
>     }
> 
>     (void) chmod(filename, 0600);
>     start_of_append = ftell(folder_stream);
> 
>     rv = pine_rfc822_output(header,bod,unix_puts,(TCPSTREAM *)folder_stream);
> 
>     fclose(folder_stream);
****  ^^^^^^ no error checking here  ****
> 
>   done:
>     if(!rv){
>         save_errno = errno;
> 

A quick grep through the pine 3.91 sources suggest that there are lots
of other places where the results of fclose() are ignored possibly
leading to similar problems.

Would a simple fix like:

  rv |= fclose(folder_stream) ;

be suitable in this case?  What about all the other fcloses?

Is there a member of the Pine development team who can comment on
this?

  -- Jon Peatfield  (postmaster@damtp.cam.ac.uk)

--
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852     Mail: J.S.Peatfield@damtp.cam.ac.uk



From owner-pine-info@cac.washington.edu  Wed Jan 18 11:16:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06866;
	Wed, 18 Jan 95 11:16:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14145;
	Wed, 18 Jan 95 11:01:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14139;
	Wed, 18 Jan 95 11:01:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUfOC-00038YC; Wed, 18 Jan 95 10:45 PST
To: pine-info@cac.washington.edu
From: Nancy McGough <nancym@ii.com>
Subject: Re: Looking for Windows newsreader with marking ability
Date: 18 Jan 1995 10:33:39 -0800
Message-Id: <ii.790453662@shell1.best.com>
References: <marcsD2LDEJ.7pH@netcom.com>

marcs@netcom.com (Marc San Soucie) writes:
>What I miss most, though, is the ability to mark articles for
>re-reading later.
>Has anyone experienced a Windows-based (SLIP/PPP) newsreader which
>offers this capability?

Pine for Windows, which is both a mailer and newsreader and works over
SLIP/PPP, has this.  You press the * key to flag a message.


>And while I'm at it, is there one which does a good job of providing
>keystroke-only manipulation?
>
>And on the dreamy edge, is there one which would let me use my own
>text editor?

Pine also does both of these.  

Unfortuantely, when I've used Pine over a PPP connection to read
news, it's been excruciatingly slow.  Is there anyone who uses Pine 
for Windows over SLIP/PPP for newsreading, who's happy with the speed?
Just curious.

Thanks,
Nancy


-- 
 /\_/\    Nancy McGough
( o.o )   Infinite Ink
 > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/


From owner-pine-info@cac.washington.edu  Wed Jan 18 11:26:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07376;
	Wed, 18 Jan 95 11:26:40 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10210;
	Wed, 18 Jan 95 10:46:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10204;
	Wed, 18 Jan 95 10:46:21 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUfEW-00038JC; Wed, 18 Jan 95 10:35 PST
To: pine-info@cac.washington.edu
From: bmclean@biostat.soph.uab.edu
Subject: Attaching binaries to mail in Pine
Date: 18 Jan 1995 18:22:21 GMT
Message-Id: <3fjm8t$oml@maze.dpo.uab.edu>

I need to attach binary files to e-mail when communicating with
an individual who is using Pine to read mail on a Unix system.

I do not use Pine and the person that I need to communicate with
does not know more than the basics of Pine use.

My e-mail software (Pegasus Windows on a Novell system) will
attach a binary file to e-mail after uuencoding it.  Pegasus
will automatically uudecode a received uuencoded binary.
Apparently Pegasus also supports MIME decoding of received
encoded binaries.

What format does Pine use to encode transmitted binaries?

Is Pine capable of using uuencode and uudecode?

Is there a on-line manual for Pine somewhere on the internet?

Any help would be greatly appreciated.
Thanks in advance.


From owner-pine-info@cac.washington.edu  Wed Jan 18 12:31:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10808;
	Wed, 18 Jan 95 12:31:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16177;
	Wed, 18 Jan 95 12:20:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from PAULAP.INNOSOFT.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16167;
	Wed, 18 Jan 95 12:20:04 -0800
Received: from PAULAP.INNOSOFT.COM by PAULAP.INNOSOFT.COM (PMDF V4.3-13 #9441)
 id <01HLZPHBFET891VTJL@PAULAP.INNOSOFT.COM>; Wed,
 18 Jan 1995 12:18:02 -0800 (PST)
Date: Wed, 18 Jan 1995 12:18:02 -0800 (PST)
From: portia@innosoft.com
Subject: Re: pine to cc:Mail
In-Reply-To: <3f7jdi$po@jaring.my>
To: John Vogelsang <fjv@insas.po.my>
Cc: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501181229.F547359825-0100000@PAULAP.INNOSOFT.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

On Sat, 14 Jan 1995, John Vogelsang wrote:

> 
> Could somebody provide an example of "A good cc:Mail<->Internet 
> gateway" or is this just a hypothetical entity.

Innosoft's PMDF is a commerical product which does MIME to cc:Mail (and
other PC mailers like WPO aka Groupwise, Microsoft Mail (PC), and MHS
based mailers). PMDF can talk to SMTP, X.400, FAX and pagers among its many
capabilities. A VMS port of Pine is also available as part of PMDF. 

PMDF is available on VMS systems, and is field testing on DEC's OSF/1 system.

> 
> 
> Thanks, John Vogelsang.
> 
> --
> GeneSys Software Sdn. Bhd.
> ----------------------------------------------------------------
>                                         145A, Jalan Maharajalela 
> Tel:  +(603) 242 0411                   50150 Kuala Lumpur  
> Fax:  +(603) 248 0503                   Malaysia
> 


	/portia		portia@innosoft.com
	Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax
	1050 East Garvey Ave South, West Covina, CA 91790



From owner-pine-info@cac.washington.edu  Wed Jan 18 12:53:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11491;
	Wed, 18 Jan 95 12:53:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13156;
	Wed, 18 Jan 95 12:43:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13150;
	Wed, 18 Jan 95 12:43:19 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25359;
	Wed, 18 Jan 95 12:43:14 -0800
Date: Wed, 18 Jan 1995 12:43:14 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Karel Kubat <karel@bambix.icce.rug.nl>
Cc: pine-info@cac.washington.edu
Subject: Re: Divers suggestions and questions.. retrying!
In-Reply-To: <Pine.LNX.3.91.950118155511.15242A-100000@bambix.icce.rug.nl>
Message-Id: <Pine.ULT.3.92.950118123958.19446A-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Wed, 18 Jan 1995, Karel Kubat wrote:

 
>     3. Some of nn's behavior for news reading is extremely useful, e.g. the X
>     key to mark an entire group as "read" and skip to the next one. I'd love
>     that in Pine! Any suggestions on how to emulate this?

Use: ;aad 
then TAB to go to the next folder.
Make sure you have aggregate operations enabled.
 
>     4. I got my nn configured in such a way that only the _subjects_ of
>     articles are retrieved. When I actually want to _read_ the article, the
>     body is retrieved. This saves masses of network traffic.
> 
>     How do I get Pine to act in this way ?!

We thought it did already... if you have evidence to the contrary, please 
send details to "pine-bugs@cac.washington.edu" so we can try to track down 
the problem.

-teg


From owner-pine-info@cac.washington.edu  Wed Jan 18 12:59:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11679;
	Wed, 18 Jan 95 12:59:05 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16883;
	Wed, 18 Jan 95 12:51:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16877;
	Wed, 18 Jan 95 12:51:51 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25486;
	Wed, 18 Jan 95 12:51:47 -0800
Date: Wed, 18 Jan 1995 12:51:42 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Nancy McGough <nancym@ii.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Looking for Windows newsreader with marking ability
In-Reply-To: <ii.790453662@shell1.best.com>
Message-Id: <Pine.ULT.3.92.950118124528.19446C-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Nancy,
Note that flagging a message as "important" is beyond the design goals of 
NNTP, so the flag will not persist across sessions for *news* messages,
only messages in local or IMAP mailboxes.  However, the "Pine theory of 
newsreading" is that news articles of no further interest get marked as 
Deleted and become invisible in the next session, thus leaving only the 
messages that you might want to go back and look at again.

Re: PC-Pine newsreading performance... We are looking into this.
I've noticed the same thing.

-teg

On 18 Jan 1995, Nancy McGough wrote:

> marcs@netcom.com (Marc San Soucie) writes:
> >What I miss most, though, is the ability to mark articles for
> >re-reading later.
> >Has anyone experienced a Windows-based (SLIP/PPP) newsreader which
> >offers this capability?
> 
> Pine for Windows, which is both a mailer and newsreader and works over
> SLIP/PPP, has this.  You press the * key to flag a message.
> 
> 
> >And while I'm at it, is there one which does a good job of providing
> >keystroke-only manipulation?
> >
> >And on the dreamy edge, is there one which would let me use my own
> >text editor?
> 
> Pine also does both of these.  
> 
> Unfortuantely, when I've used Pine over a PPP connection to read
> news, it's been excruciatingly slow.  Is there anyone who uses Pine 
> for Windows over SLIP/PPP for newsreading, who's happy with the speed?
> Just curious.
> 
> Thanks,
> Nancy
> 
> 
> -- 
>  /\_/\    Nancy McGough
> ( o.o )   Infinite Ink
>  > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/
> 


From owner-pine-info@cac.washington.edu  Wed Jan 18 15:16:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19642;
	Wed, 18 Jan 95 15:16:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16452;
	Wed, 18 Jan 95 14:57:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16446;
	Wed, 18 Jan 95 14:57:56 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUj8M-00038JC; Wed, 18 Jan 95 14:45 PST
To: pine-info@cac.washington.edu
From: Nancy McGough <nancym@ii.com>
Subject: "pico -w" and long lines
Date: 18 Jan 1995 12:26:52 -0801
Message-Id: <ii.790460725@shell1.best.com>

If you use "pico -w" to edit a file, what are the longest lines
it can deal with?  I know vi has a problem with long lines and
I'm wondering if Pico does too.

Thanks,
Nancy

-- 
 /\_/\    Nancy McGough
( o.o )   Infinite Ink
 > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/


From owner-pine-info@cac.washington.edu  Wed Jan 18 15:30:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20369;
	Wed, 18 Jan 95 15:30:09 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20908;
	Wed, 18 Jan 95 15:23:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20900;
	Wed, 18 Jan 95 15:22:58 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUjXo-00038KC; Wed, 18 Jan 95 15:12 PST
To: pine-info@cac.washington.edu
From: ccurtis@ee.fit.edu (Christopher W. Curtis)
Subject: Auto-Cc Posts?
Message-Id: <ccurtis.790466001@ee.fit.edu>
Date: Wed, 18 Jan 1995 21:53:21 GMT

Is it possible to set up PINE so that if you reply to a news article it will
automatically Cc the message to the sender?  In a related question, is it
possible to tell if a message was sent to a newsgroup or directly to you?
I've gotten messages that ask, "Do you want to post followup to newsgroups?"
but the thing to which I'm replying wasn't posted there - it was sent directly
to me but contained the newsgroup reference.

Personally, if ity wasn't sent to the newgroup, I don't think PINE should ask
this, and that it should automatically Cc a posted message to the sender, or
at least have the option of doing so.  How's this sound?

--
T |        Christopher Curtis       |                                  | O
E |   Sun Lab System Administrator  |       Fear the government        | S
A | Florida Institute of Technology |       That fears your gun        | /
M |       Melbourne, Florida       N|N                                 | 2


From owner-pine-info@cac.washington.edu  Wed Jan 18 16:27:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23712;
	Wed, 18 Jan 95 16:27:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18786;
	Wed, 18 Jan 95 16:19:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18780;
	Wed, 18 Jan 95 16:19:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUkQk-00038JC; Wed, 18 Jan 95 16:08 PST
To: pine-info@cac.washington.edu
From: J.S.Peatfield@amtp.cam.ac.uk (Jon Peatfield)
Subject: Re: problem when tmp directory is full
Date: 18 Jan 1995 22:36:55 GMT
Message-Id: <J.S.PEATFIELD.95Jan18223655@kro.amtp.cam.ac.uk>
References: <J.S.PEATFIELD.95Jan11134038@kro.amtp.cam.ac.uk>
In-Reply-To: J.S.Peatfield@amtp.cam.ac.uk's message of 18 Jan 1995 17:10:11 GMT

> A quick grep through the pine 3.91 sources suggest that there are lots
> of other places where the results of fclose() are ignored possibly
> leading to similar problems.

A more detailed reading of all the occurances of fclose() in the pine
source <sigh> has led me to believe that most of the other unchecked
ones are either cases where the file was only opened for reading or we
really don't care if it succeeded or not (like the debug log).  Thus
I'd offer the following patch(let) to osdep/sendmail which I believe
fixes this particular buglet.  I'm still waiting for the build to
finish so I've not tested it yet but it can't really make things much
worse (I hope.)

--cut-here--
*** osdep/sendmail.orig	Wed Sep 21 23:39:39 1994
--- osdep/sendmail	Wed Jan 18 21:53:10 1995
***************
*** 68,74 ****
  
      rv = pine_rfc822_output(header,bod,unix_puts,(TCPSTREAM *)folder_stream);
  
!     fclose(folder_stream);
  
    done:
      if(!rv){
--- 68,74 ----
  
      rv = pine_rfc822_output(header,bod,unix_puts,(TCPSTREAM *)folder_stream);
  
!     rv |= fclose(folder_stream);  /* catch errors on fclose() JSP 1995-01-18 */
  
    done:
      if(!rv){
--cut-here--

****  I'd prefer it if one of the Pine maintainers checked that I'm not
****  being stupid here.



On a different matter can someone tell me what the modal argument to
q_status_message() (in status.c) is for?  The code seems to ignore it
completely.

> void
> q_status_message(modal, min_time, max_time, message)
>      char *message;
>      int   min_time,max_time, modal;
> {
>     strncpy(message_queue[queue_length].text, message, MAX_SCREEN_COLS);
>     (message_queue[queue_length].text)[MAX_SCREEN_COLS] = '\0';
> 
>     /* save the display time length */
>     message_queue[queue_length].min_display_time = min_time;
>     message_queue[queue_length].max_display_time = max_time;
> 
> 
>     /* Bump up the queue length if it's not full. (If there's more than
>          6 messages we just over write last message */
>     if(queue_length < QUEUE_LENGTH - 1 )
>       queue_length++;
>     dprint(9, (debugfile, "q_status_message, Count %d, \"%s\"\n",
> 	       queue_length, message))
> }
> 

I'd hoped it might wait for a user acknowlegment but it isn't passed
on to anything else.  Maybe this is for a later version (I hope.)

Just in case people think I'm just complaining, I actually like
pine3.91 a lot.  It is the mailer we currently suggest to our new
users and seems to have a much faster learning cycle than most of the
other mailers we have used.  I just hope to iron out a few niggles so
that our users don't have mail vanish.

  -- Jon Peatfield  (DAMTP unix network admin, postmaster@damtp.cam.ac.uk)

--
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852     Mail: J.S.Peatfield@damtp.cam.ac.uk



From owner-pine-info@cac.washington.edu  Wed Jan 18 16:41:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24318;
	Wed, 18 Jan 95 16:41:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22657;
	Wed, 18 Jan 95 16:34:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22651;
	Wed, 18 Jan 95 16:34:34 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUkeC-00038KC; Wed, 18 Jan 95 16:22 PST
To: pine-info@cac.washington.edu
From: Eric Force <eforce@acy1.digex.net>
Subject: EXPORT Message Text Question
Date: Wed, 18 Jan 1995 16:29:40 -0500
Message-Id: <Pine.SUN.3.91.950118162404.10780A-100000@acy1.digex.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there a way to export JUST the Message Text portion of a
received message in PINE? (i.e. Without the Message Header Info)

Many Thanks!

Eric

 ======================================================================
  |   Have a Great Day!  |  Challenging Crossword Puzzles via Email  |
  |      Eric Force      |     New Puzzle Daily. For Information:    |
  | eforce@acy.digex.net | -->   finger xword@acy.digex.net   <--    |
 ======================================================================



From owner-pine-info@cac.washington.edu  Wed Jan 18 17:36:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27083;
	Wed, 18 Jan 95 17:36:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24110;
	Wed, 18 Jan 95 17:31:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24104;
	Wed, 18 Jan 95 17:31:25 -0800
Received: from localhost by shiva2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23866;
	Wed, 18 Jan 95 17:31:22 -0800
Date: Wed, 18 Jan 1995 17:31:20 -0800 (PST)
From: Steve Hubert <hubert@cac.washington.edu>
To: "R. Stewart Ellis" <ellis@nova.gmi.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Alias expander for pine addressbook?
In-Reply-To: <ellis.790433522@gmi.edu>
Message-Id: <Pine.ULT.3.92.950118172918.21434D-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 18 Jan 1995, R. Stewart Ellis wrote:

> As someone who prefers to use pine as my MUA and nn as my reader, I would
> like to be able to have the pine aliases available to me from inside nn.  nn
> seems to be able to use an external alias expander, and people have even
> re-written aux (the nn posting/mailing script) to use elm aliases, or to use
> elm as the mailer.  While elm can be used as a mailer at the UNIX prompt,
> pine does not seem to support this mode.  

I'm not very familiar with nn but pine can be used from the UNIX prompt.

% pine address

will put you into the composer with address filled-in in the To field 
(and expanded from addrbook).  I don't know of any stand-alone pine alias 
expanders.> 

Steve Hubert <hubert@cac.washington.edu>
Networks and Distributed Computing, Univ. of Washington, Seattle


From owner-pine-info@cac.washington.edu  Wed Jan 18 17:56:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27625;
	Wed, 18 Jan 95 17:56:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24504;
	Wed, 18 Jan 95 17:53:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24498;
	Wed, 18 Jan 95 17:53:07 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00550;
	Wed, 18 Jan 95 17:52:55 -0800
Date: Wed, 18 Jan 1995 17:52:54 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Eric Force <eforce@acy1.digex.net>
Cc: pine-info@cac.washington.edu
Subject: Re: EXPORT Message Text Question
In-Reply-To: <Pine.SUN.3.91.950118162404.10780A-100000@acy1.digex.net>
Message-Id: <Pine.ULT.3.92.950118174942.29312B-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Yes, go to the attachment viewer (V) and use "S Save"...

-teg

On Wed, 18 Jan 1995, Eric Force wrote:

> Is there a way to export JUST the Message Text portion of a
> received message in PINE? (i.e. Without the Message Header Info)
> 
> Many Thanks!
> 
> Eric
> 
>  ======================================================================
>   |   Have a Great Day!  |  Challenging Crossword Puzzles via Email  |
>   |      Eric Force      |     New Puzzle Daily. For Information:    |
>   | eforce@acy.digex.net | -->   finger xword@acy.digex.net   <--    |
>  ======================================================================
> 
> 


From owner-pine-info@cac.washington.edu  Wed Jan 18 18:09:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27975;
	Wed, 18 Jan 95 18:09:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21179;
	Wed, 18 Jan 95 18:04:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21171;
	Wed, 18 Jan 95 18:04:54 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 19 Jan 95 10:03:20 -0800
Date: Thu, 19 Jan 1995 10:03:19 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: bmclean@biostat.soph.uab.edu
Cc: pine-info@cac.washington.edu
Subject: Re: Attaching binaries to mail in Pine
In-Reply-To: <3fjm8t$oml@maze.dpo.uab.edu>
Message-Id: <Pine.SOL.3.91.950119095904.18267A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 18 Jan 1995 bmclean@biostat.soph.uab.edu wrote:

> What format does Pine use to encode transmitted binaries?

	Since pine is a MIME compliant UA it sticks to the standards and
uses base64 encoding its attachments.

> Is Pine capable of using uuencode and uudecode?

	Yes, but not fully integrated.

	If you receive an email with data that has been uuencoded you can
(within pine) pipe the message to uudecode.

	If you wish to send an email with a uuencoded file, you can uuencode
the file prior to entering pine (or you can ctrl-z and suspend pine) and then
"read" it in to the body of the message from the editor.

	Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 18 18:17:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28173;
	Wed, 18 Jan 95 18:17:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21336;
	Wed, 18 Jan 95 18:14:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21330;
	Wed, 18 Jan 95 18:14:34 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUmAO-00038JC; Wed, 18 Jan 95 18:00 PST
To: pine-info@cac.washington.edu
From: fried@freddy.in-berlin.de (Friedhelm Kappen)
Subject: [Q] What does "POPmail" mean?
Message-Id: <D2MGoJ.2Jt@freddy.in-berlin.de>
Date: Wed, 18 Jan 1995 22:19:30 GMT

Well, can some kind soul please explain to me the 
signification of "POPmail" or give me tips where
I can learn more about that expression.

Thank you
Friedhelm

-- 
----____   __  _ ------------------------------------------------ 
   ( /_   ( /_/	    Friedhelm Kappen   fried@freddy.in-berlin.de
   _/     _/ \_     Marschnerstr. 8
     *          *   D-12203 BERLIN     phone +49 30 834 1679


From owner-pine-info@cac.washington.edu  Wed Jan 18 18:52:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29135;
	Wed, 18 Jan 95 18:52:37 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25357;
	Wed, 18 Jan 95 18:48:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25351;
	Wed, 18 Jan 95 18:48:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUmi8-00038QC; Wed, 18 Jan 95 18:34 PST
To: pine-info@cac.washington.edu
From: ii@best.com (Nancy McGough)
Subject: Re: HOW TO READ SAVED NEWS
Date: 18 Jan 1995 18:08:39 -0800
Message-Id: <ii.790481235@shell1.best.com>
References: <3fgcbn$163@trog.dra.hmg.gb>

vchui@taz.dra.hmg.gb writes:
>I have saved some postings from my news reader and would like to read them
>as if they are mail folders. Is is possible to use Pine to read saved usenet
>news files as mail or news folders?

It depends on your newsreader and how it saves articles.  You can
try using Pine on your folder by typing this at the Unix prompt:

  pine -if /full/path/to/folder/foldername

Good luck,
Nancy
-- 
 /\_/\   DUE TO EMAIL PROBLEMS, PLEASE SEND MAIL TO ME TO EITHER:   /\_/\
( o.o )                                                            ( o.o )
 > ~ <           nancym@halcyon    -OR-    ii@best.com              > o <


From owner-pine-info@cac.washington.edu  Wed Jan 18 19:02:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29519;
	Wed, 18 Jan 95 19:02:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22032;
	Wed, 18 Jan 95 18:58:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22026;
	Wed, 18 Jan 95 18:58:22 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUmtz-00038JC; Wed, 18 Jan 95 18:47 PST
To: pine-info@cac.washington.edu
From: ii@best.com (Nancy McGough)
Subject: Changing From: header
Date: 18 Jan 1995 18:22:18 -0800
Message-Id: <ii.790481918@shell1.best.com>

I'd like to change the From: header in mail I send from Pine
by putting something like this in my .pinerc:

customized-hdrs=Organization: $ORGANIZATION,
        From: Nancy McGough <nancym@ii.com>


Unfortunately, when I try this Pine gives a message that says
I can't change the From header.  Is there any way around this?
E.g., could the system admins reset something to allow this?

Thanks for any info,
Nancy

-- 
 /\_/\   DUE TO EMAIL PROBLEMS, PLEASE SEND MAIL TO ME TO EITHER:   /\_/\
( o.o )                                                            ( o.o )
 > ~ <           nancym@halcyon    -OR-    ii@best.com              > o <


From owner-pine-info@cac.washington.edu  Wed Jan 18 20:28:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01579;
	Wed, 18 Jan 95 20:28:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26762;
	Wed, 18 Jan 95 20:25:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26754;
	Wed, 18 Jan 95 20:25:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUoDS-00038RC; Wed, 18 Jan 95 20:11 PST
To: pine-info@cac.washington.edu
From: htan@acs.ryerson.ca (Haan Tan - SHTM/W94)
Subject: Auto-expunge mails within pine?
Date: 18 Jan 1995 23:21:22 GMT
Message-Id: <3fk7pi$3ql8@hermes.acs.ryerson.ca>

hi all,

	is there anyway to configure pine to automatically expunge mails 
once they have been saved or deleted?  i know of the 
expunge-without-confirm feature, but what i'd like is to have the 
"D"elete key do the work of both deleting and expunging AS WELL AS having 
pine look out for any "D"eletes that arise when mail is saved to another 
directory.

	thanks for any help, i really appreciate this.

Nick :)


From owner-pine-info@cac.washington.edu  Wed Jan 18 20:43:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01980;
	Wed, 18 Jan 95 20:43:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23691;
	Wed, 18 Jan 95 20:39:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23685;
	Wed, 18 Jan 95 20:39:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUoT3-00038JC; Wed, 18 Jan 95 20:27 PST
To: pine-info@cac.washington.edu
From: Eric Force <eforce@acy1.digex.net>
Subject: Re: EXPORT Message Text Problem Solved
Date: Wed, 18 Jan 1995 23:26:55 -0500
Message-Id: <Pine.SUN.3.91.950118231122.18963B-100000@acy1.digex.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Many thanks to Terry Gray <gray@cac.washington.edu> for
the solution to my question:

Is there a way to export just the text portion of a received
message in PINE. (i.e. Without the Message header Info)

Terry's eloquent solution:

 ... go to the attachment viewer (V) and use "S Save" ...

Incredible! Thanks again Terry!

Eric

 ======================================================================
  |   Have a Great Day!  |  Challenging Crossword Puzzles via Email  |
  |      Eric Force      |     New Puzzle Daily. For Information:    |
  | eforce@acy.digex.net | -->   finger xword@acy.digex.net   <--    |
 ======================================================================




From owner-pine-info@cac.washington.edu  Wed Jan 18 20:58:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02235;
	Wed, 18 Jan 95 20:58:33 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27128;
	Wed, 18 Jan 95 20:54:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27122;
	Wed, 18 Jan 95 20:54:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUofB-00038JC; Wed, 18 Jan 95 20:40 PST
To: pine-info@cac.washington.edu
From: gweil@ibeam.jf.intel.com (Garry Weil)
Subject: Reading folders on Unix w/PCPine
Date: Wed, 18 Jan 1995 12:38:05 -0800
Message-Id: <gweil-1801951238050001@macindeo.jf.intel.com>

I have been trying to set my folder collection so that I can read and
write to the folders created by Pine, on Unix, on my PC using PCPINE.

I set the folder-collections={mumble.mumble}mail/[]. This does not work.
It will show any folders that are in my ~mail directory. 

Can anybody help?

Garry Weil

-- 
Garry Weil                            gweil@ibeam.intel.com
Indeo(TM) Technology Support          
(800) 628-8686, 1-3-1 menu prompts


From owner-pine-info@cac.washington.edu  Wed Jan 18 21:48:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03672;
	Wed, 18 Jan 95 21:48:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27940;
	Wed, 18 Jan 95 21:45:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27934;
	Wed, 18 Jan 95 21:45:46 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11386;
	Wed, 18 Jan 95 21:45:42 -0800
Date: Wed, 18 Jan 1995 21:45:42 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Haan Tan - SHTM/W94 <htan@acs.ryerson.ca>
Cc: pine-info@cac.washington.edu
Subject: Re: Auto-expunge mails within pine?
In-Reply-To: <3fk7pi$3ql8@hermes.acs.ryerson.ca>
Message-Id: <Pine.ULT.3.92.950118214325.100H-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

You really want to work without a net!

There is no way to have "D" imply immediate expunge.

Regarding the preservation of the "Deleted" flag when you Save a message:
we agree that this is a misfeature, and it will be corrected in 3.92. 

-teg

On 18 Jan 1995, Haan Tan - SHTM/W94 wrote:

> hi all,
> 
> 	is there anyway to configure pine to automatically expunge mails 
> once they have been saved or deleted?  i know of the 
> expunge-without-confirm feature, but what i'd like is to have the 
> "D"elete key do the work of both deleting and expunging AS WELL AS having 
> pine look out for any "D"eletes that arise when mail is saved to another 
> directory.
> 
> 	thanks for any help, i really appreciate this.
> 
> Nick :)
> 


From owner-pine-info@cac.washington.edu  Thu Jan 19 00:23:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07454;
	Thu, 19 Jan 95 00:23:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00246;
	Thu, 19 Jan 95 00:18:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00240;
	Thu, 19 Jan 95 00:18:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUrwG-00038MC; Thu, 19 Jan 95 00:09 PST
To: pine-info@cac.washington.edu
From: jsweet@cory.eecs.berkeley.edu (Julian Sweet)
Subject: PC-Pine & POP
Date: Thu, 19 Jan 1995 00:09:41
Message-Id: <jsweet.3.00002905@cory.eecs.berkeley.edu>

Does my mail server have to be POP for PC-Pine to work? I got SLIP running no 
problem....


From owner-pine-info@cac.washington.edu  Thu Jan 19 00:24:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07489;
	Thu, 19 Jan 95 00:24:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26753;
	Thu, 19 Jan 95 00:13:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26747;
	Thu, 19 Jan 95 00:13:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUrnT-00038JC; Thu, 19 Jan 95 00:00 PST
To: pine-info@cac.washington.edu
From: ii@best.com (Nancy McGough)
Subject: Re: How do I Set HP Laser 4 printer to print Pine
Date: 18 Jan 1995 23:52:10 -0800
Message-Id: <ii.790501785@shell1.best.com>
References: <Pine.3.89.1.2-VMS-9.9501161658.A595600959-0100000@HARVEY.MAYO.EDU> <Pine.BSI.3.91.950117081739.23880A-100000@gatekeeper.sial.com>

schuchas@sial.com (Stanley Schuchat) writes:
>I have the same problem with a LaserJet 4, but can print to a LaserJet 
>III, LaserJet IIIP, LaserJet II. I also have problems with a DeskJet 320.

Is it a postscript printer?  If so, set your print driver to something
like:

   HP Laserjet 4/4M on LPT1

Rather than:

   HP Laserjet Postscript 4/4M on LPT1

Hope this helps,
Nancy

-- 
 /\_/\   DUE TO EMAIL PROBLEMS, PLEASE SEND MAIL TO ME TO EITHER:   /\_/\
( o.o )                                                            ( o.o )
 > ~ <        nancym@halcyon.com    -OR-    ii@best.com             > ^ <


From owner-pine-info@cac.washington.edu  Thu Jan 19 03:53:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12328;
	Thu, 19 Jan 95 03:53:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02935;
	Thu, 19 Jan 95 03:46:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02929;
	Thu, 19 Jan 95 03:46:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUv6H-00038KC; Thu, 19 Jan 95 03:32 PST
To: pine-info@cac.washington.edu
From: J.S.Peatfield@amtp.cam.ac.uk (Jon Peatfield)
Subject: cmsg cancel <J.S.PEATFIELD.95Jan19112051@kro.amtp.cam.ac.uk>
Control: cancel <J.S.PEATFIELD.95Jan19112051@kro.amtp.cam.ac.uk>
Date: 19 Jan 1995 11:32:14 GMT
Message-Id: <J.S.PEATFIELD.95Jan19113214@kro.amtp.cam.ac.uk>

--
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852     Mail: J.S.Peatfield@damtp.cam.ac.uk



From owner-pine-info@cac.washington.edu  Thu Jan 19 04:10:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13270;
	Thu, 19 Jan 95 04:10:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29667;
	Thu, 19 Jan 95 04:03:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29661;
	Thu, 19 Jan 95 04:03:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUvK0-00038RC; Thu, 19 Jan 95 03:46 PST
To: pine-info@cac.washington.edu
From: mraaum@ulrik.uio.no (Margrete Raaum)
Subject: Re: Reading folders on Unix w/PCPine
Date: 19 Jan 1995 11:36:13 GMT
Message-Id: <3flird$fcp@hermod.uio.no>
References: <gweil-1801951238050001@macindeo.jf.intel.com>



This is how I chose to do it.
It works for me.
Are you sure IMAP i running on the server?

smtp-server=machine.dom.ain
inbox-path={machine.dom.ain}inbox
folder-collections= Archive {machine.dom.ain}mail/[]
default-fcc={machine.dom.ain}mail/sent-mail
read-message-folder={machine.dom.ain}mail/MAIL


Margrete
-- 


*** Murgo optimo maximo



From owner-pine-info@cac.washington.edu  Thu Jan 19 04:22:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13574;
	Thu, 19 Jan 95 04:22:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03464;
	Thu, 19 Jan 95 04:13:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03458;
	Thu, 19 Jan 95 04:13:34 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUvVC-00038KC; Thu, 19 Jan 95 03:58 PST
To: pine-info@cac.washington.edu
From: J.S.Peatfield@amtp.cam.ac.uk (Jon Peatfield)
Subject: Re: problem when tmp directory is full
Date: 19 Jan 1995 11:58:04 GMT
Message-Id: <J.S.PEATFIELD.95Jan19115804@kro.amtp.cam.ac.uk>
References: <J.S.PEATFIELD.95Jan11134038@kro.amtp.cam.ac.uk>
In-Reply-To: J.S.Peatfield@amtp.cam.ac.uk's message of 18 Jan 1995 22:36:55 GMT


Eeek I'm really getting old or stupid.  I missed that the return code
being tested for in append_message2() was if rv == 0.

Here is a patch which I've verified works at least on SunOS4, and logs
and error to the debugfile if this happens.

--cut-here--
*** osdep/sendmail.orig	Wed Sep 21 23:39:39 1994
--- osdep/sendmail	Thu Jan 19 11:49:10 1995
***************
*** 68,74 ****
  
      rv = pine_rfc822_output(header,bod,unix_puts,(TCPSTREAM *)folder_stream);
  
!     fclose(folder_stream);
  
    done:
      if(!rv){
--- 68,91 ----
  
      rv = pine_rfc822_output(header,bod,unix_puts,(TCPSTREAM *)folder_stream);
  
!     /* Catch any previous errors which may have been missed elsewhere
!        JSP 1995-01-19 */
!     if (ferror(folder_stream)) {  /* An error occured somewhere else */
!       rv = 0 ;
!       save_errno = errno ;
!       dprint(1, (debugfile, "Error ferror on %s  error: %s\n",
! 		 filename, error_description(save_errno))) ;
!       errno = save_errno ;
!     }
! 
!     /* catch errors on fclose() JSP 1995-01-19 */
!     if (fclose(folder_stream) < 0) {
!       rv = 0 ;  /* error condition */
!       save_errno = errno ;
!       dprint(1, (debugfile, "Error fclose on %s  error: %s\n",
! 		 filename, error_description(save_errno))) ;
!       errno = save_errno ;
!     }
  
    done:
      if(!rv){
--cut-here--

Any chance of this being included in the next release?

Now back to your regular group...

  -- Jon
--
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852     Mail: J.S.Peatfield@damtp.cam.ac.uk



From owner-pine-info@cac.washington.edu  Thu Jan 19 05:16:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14680;
	Thu, 19 Jan 95 05:16:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00791;
	Thu, 19 Jan 95 05:03:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00785;
	Thu, 19 Jan 95 05:03:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUwJE-00038KC; Thu, 19 Jan 95 04:49 PST
To: pine-info@cac.washington.edu
From: keviny@hk.super.net (Mr Kevin Yeung)
Subject: ANSI colors in emails?
Date: 19 Jan 1995 10:41:07 GMT
Message-Id: <3flfk3$hoa@hk.super.net>

Hi all,

Is it possible to make emails colorful using ANSI control characters?  If 
yes, how?  Or is this question in any FAQ available on the Net?  Thanks.

--
Kevin Yeung
email: keviny@hk.super.net



From owner-pine-info@cac.washington.edu  Thu Jan 19 05:52:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15520;
	Thu, 19 Jan 95 05:52:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04492;
	Thu, 19 Jan 95 05:40:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04486;
	Thu, 19 Jan 95 05:40:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rUwwN-00038MC; Thu, 19 Jan 95 05:30 PST
To: pine-info@cac.washington.edu
From: "Roy M. Indrebo" <roy@lyr>
Subject: Question about pine
Date: Thu, 19 Jan 1995 14:28:17 +0100
Message-Id: <Pine.ULT.3.91.950119142423.6486C-100000@lyr>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there any way that I can save messages(mails) from a certain person to 
a certain folder.

I'd like to do this because I subscribe to some mailinglists, and mails 
from other persons than the mailinglist tends to get lost in all the 
other messages.

So, if you have a solution to my problem, please e-mail me.
(I'll try not to loose your mail. :-)

Thanks in advance!

------------------------------------------------------------------------------
Name: Roy Magne Indreboe - e-mail: roy.m.indrebo@hiMolde.no
IRC: PigOnWing - Mail: Bergveien 2, 6400 MOLDE, NORWAY - Phone:71254934
------------------------------------------------------------------------------




From owner-pine-info@cac.washington.edu  Thu Jan 19 08:49:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20733;
	Thu, 19 Jan 95 08:49:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04402;
	Thu, 19 Jan 95 08:39:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from Gayle-Gaston.tenet.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04396;
	Thu, 19 Jan 95 08:39:18 -0800
Received: (from cross@localhost) by Gayle-Gaston.tenet.edu (8.6.9/8.6.9) id KAA15364; Thu, 19 Jan 1995 10:39:17 -0600
Date: Thu, 19 Jan 1995 10:39:16 -0600 (CST)
From: Carolyn Ross <cross@tenet.edu>
Subject: Don't know (fwd)
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501191052.A14408-0100000@Gayle-Gaston.tenet.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



Can anyone out there help me, I'm stumped. See the message below that I 
received from a Pine 3.89 user.

Carolyn J. Ross				 P.O. Box 400, Austin, TX 78767-0400
TENET Master Trainer			 Voice 512-467-0222 or 800-580-8272
Special Services Manager, Communications Fax 512-467-6927
Texas Association of School Boards	 E-Mail: cross@tenet.edu
				
				* * * * * * *

---------- Forwarded message ----------

Don't know what I did, but somehow I disabled the automatic monthly 
sent-mail filing system.  Now my sent mail has several months worth of 
stuff in it and it doesn't prompt me for a new folder at the end of the 
month!  YIPES.  Do you know how to return to the original arrangement?




From owner-pine-info@cac.washington.edu  Thu Jan 19 09:28:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23245;
	Thu, 19 Jan 95 09:28:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05361;
	Thu, 19 Jan 95 09:17:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05351;
	Thu, 19 Jan 95 09:17:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV0DI-00038KC; Thu, 19 Jan 95 09:00 PST
To: pine-info@cac.washington.edu
From: wyrickk@myhost.subdomain.domain (Kevin Wyrick)
Subject: .signature over quoted text
Date: 19 Jan 1995 16:48:51 GMT
Message-Id: <3fm55j$69d@bruce.uncg.edu>

Hi,

I'm convert from elm over to pine recently, and I have a question about
the .signature file on my replies.  When I try to reply to any mail message
and I copy the text from the first note, Pine will always start off with
my signature first, and then below that it will put the quoted text.  Does
anyone else have this problem?  Is there a switch somewhere in the setup
or the .pinerc file that will fix this?

Thanks,

--
Kevin Wyrick
---------------------------
wyrickk@timewarp.uncg.edu

	"I see you in my head, and I wonder if you're looking down
	 at me and smiling right now, oh and I want to know if it's
	 true, when he looks at me, won't you tell me, does he realize
	 he came down here, and took you too soon."

					"Not Even the Trees"
			            - Hootie and the Blowfish '94


From owner-pine-info@cac.washington.edu  Thu Jan 19 11:31:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29667;
	Thu, 19 Jan 95 11:31:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08679;
	Thu, 19 Jan 95 11:17:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08672;
	Thu, 19 Jan 95 11:17:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV26k-00038TC; Thu, 19 Jan 95 11:01 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: [Q] What does "POPmail" mean?
Date: 19 Jan 1995 13:06:44 -0500
Message-Id: <3fm9nk$b87@little-miami.iac.net>
References: <D2MGoJ.2Jt@freddy.in-berlin.de>

Friedhelm Kappen (fried@freddy.in-berlin.de) wrote:
: Well, can some kind soul please explain to me the 
: signification of "POPmail" or give me tips where
: I can learn more about that expression.

: Thank you
: Friedhelm

The reference is to the Post Office Protocol. There are at least 2 versions
POP2 and POP3 that are around. The protocols(s) are covered by RFC's, the
specific numbers I don't recall. The InterNIC has a gopher that will
search for words in the text of the RCF's. You might try that method to
find the corresponding RFC's for POP.
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Thu Jan 19 11:32:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29724;
	Thu, 19 Jan 95 11:32:07 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11494;
	Thu, 19 Jan 95 11:17:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11488;
	Thu, 19 Jan 95 11:17:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV26i-00038VC; Thu, 19 Jan 95 11:01 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: pine to cc:Mail
Date: 19 Jan 1995 12:57:01 -0500
Message-Id: <3fm95d$b5k@little-miami.iac.net>
References: <Pine.ULT.3.92.950112141946.2637O-100000@shiva1.cac.washington.edu> <Pine.OSF.3.91a.950112154312.11982E-100000@saul1.u.washington.edu> <jmcging.790042329@access3>

John McGing (jmcging@access3.digex.net) wrote:
: Judd Deaver <jdeaver@u.washington.edu> writes:

: >Does cc:mail include a uudecoding function standard? I tried just reading 
: >the ascii version of the file into the body but it reformatted the text 
: >and made it worthless. 

: >On Thu, 12 Jan 1995, David L Miller wrote:

: >> 
: >> Pine uses MIME for all attachments and BASE64 encodes all attachments.  A
: >> good cc:Mail<->Internet gateway should be able to translate between MIME
: >> and cc:Mail attachments, but unfortunately many do not...
: >> 
: >> You may be able to get the file through by uuencoding it and including
: >> the uuencoded text into the body of a message using ^R. 
: >> 
: >> |\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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
: >> 
: >> On Thu, 12 Jan 1995, Judd Deaver wrote:
: >> 
: >> > Date: Thu, 12 JAN 1995 10:57:35 -0800 
: >> > From: Judd Deaver <jdeaver@u.washington.edu>
: >> > Newgroups: comp.groupware.lotus-notes.misc, comp.mail.pine,
: >> >     comp.mail.multi-media, comp.mail.misc, comp.mail.mime
: >> > Subject: pine to cc:Mail 
: >> > 
: >> > I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
: >> > network. I sent a Binary attachment but it did not seem to make it. Could 
: >> > this be because his network does not support MIME or because the way pine 
: >> > attaches files is different then cc:mail? If it is because they don't 
: >> > supprt MIME would an ASCII file attachment make it down or does pine 
: >> > automatically MIME encrypt all attachments?
: >> > 
: >> > Any help is GREATLY appreciated (this is an important file) could you 
: >> > please reply via e-mail though to jdeaver@u.washington.edu
: >> > 
: >> > Thank You.
: >> > 
: >> > 
: >> 


: Sorry for the long quoting, but I couldn't figure out what wasn't important.

: I sent myself a cc:Mail to internet message a few hours ago.  The attached
: file was a wordperfect file.  Pine got it and the note attached to the
: message from the cc:Mail gateway told me it had uuencoded the 
: attachment.  I've sent many things via Pine to my office and found that 
: zip files were recognized and handled by cc:Mail properly but everything 
: else comes out MIMEd.

: When I was using elm, I often sent uuencoded files to my office and they 
: were converted (uudecoded) into zip files when they landed in my cc:Mail box.

What software are you using for your cc:mail <--> Internet mail gateway?
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Thu Jan 19 11:59:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01480;
	Thu, 19 Jan 95 11:59:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12465;
	Thu, 19 Jan 95 11:47:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12459;
	Thu, 19 Jan 95 11:47:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV2aP-00038PC; Thu, 19 Jan 95 11:32 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: OS/2 version of Pine?
Date: Fri, 6 Jan 1995 12:55:12 -0800
Message-Id: <Pine.ULT.3.92.950106125142.2851M-100000@shiva1.cac.washington.edu>
References: <3e7iav$n31@ionews.io.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3e7iav$n31@ionews.io.org> 


There is not currently a native OS/2 version of Pine, but PC-Pine for
Windows is reported to work if you have winsock on your machine.  The FAQ 
is in

	ftp://ftp.cac.washington.edu/pine/docs/faq

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 2 Jan 1995 mfrisch@io.org wrote:

> Date: 2 JAN 1995 00:45:19 GMT 
> From: mfrisch@io.org
> Newgroups: comp.mail.pine
> Subject: OS/2 version of Pine? 
> 
> 	Is there an OS/2 version of Pine available that works with a POP mail
> server?  If this is a FAQ, please direct me to the source of the FAQ.
> 
> 	Thank you very much in advance!
> 
> Mike - Team OS/2
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 19 15:28:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12694;
	Thu, 19 Jan 95 15:28:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17762;
	Thu, 19 Jan 95 15:09:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17756;
	Thu, 19 Jan 95 15:09:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV5ec-00038WC; Thu, 19 Jan 95 14:48 PST
To: pine-info@cac.washington.edu
From: sam@texas.hous.inmet.com (Sam Adams)
Subject: Re: pine to cc:Mail
Message-Id: <sam.1.0010547C@texas.hous.inmet.com>
References: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu> <3fbcba$csk@news.hk.net> <clear-1601950927040001@www.wingra.com>
Date: Thu, 19 Jan 1995 21:19:41 GMT

In article <clear-1601950927040001@www.wingra.com> clear@wingra.com (Mark Clear) writes:
>From: clear@wingra.com (Mark Clear)
>Subject: Re: pine to cc:Mail
>Date: Mon, 16 Jan 1995 09:27:04 -0600

>In article <3fbcba$csk@news.hk.net>, kehres@hk.net (Tim Kehres) wrote:

>> In article <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>,
>> Judd Deaver  <jdeaver@u.washington.edu> wrote:
>> >I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
>> >network. I sent a Binary attachment but it did not seem to make it. Could 
>> >this be because his network does not support MIME or because the way pine 
>> >attaches files is different then cc:mail? If it is because they don't 
>> >supprt MIME would an ASCII file attachment make it down or does pine 
>> >automatically MIME encrypt all attachments?
>> 
>> A lot will depend upon what gateway you are using to get Internet based
>> email into and out of the cc:Mail world.  It is my understanding that the
>> Lotus gateways (UUCP/SMTP) do not yet have support for MIME, so there 
>> would be problems if you tried to get MIME messages in through one of these
>> gateways.  There are a few third party gateways on the market (Internet 
>> Exchange for cc:Mail from our company is one), which should provide the
>> functionality you are looking for however.
>> 

>Missive, from our company, is another.  Missive integrates all the leading
>mail systems (cc:Mail, SMTP, VMSmail, Microsoft Mail, etc) into one
>seamless network.  Missive's SMTP inbound channel can decode MIME and turn
>the attachment into the appropriate format for the destination, be it
>cc:Mail or whatever.  In the other direction, the SMTP outbound channel
>can encode attachments into MIME as well.

>(end commercial)

>|-----------------------------------------------------------------------------|
>| Mark Clear                                       Internet: clear@wingra.com |
>| Wingra Technologies, Inc.                       WWW: http://www.wingra.com/ |
>| Madison, WI                                             Phone: 608-238-4454 |
>|                                                                             |
>| Dr. Seuss predicted net surfing 30 years ago: "I bet with my net I can get  |
>| those things yet!" -- The Cat In the Hat                                    |
>|-----------------------------------------------------------------------------|

What makes you think we have a VAX.  Does Missive run on a PC?

-Kevin


From owner-pine-info@cac.washington.edu  Thu Jan 19 16:43:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15931;
	Thu, 19 Jan 95 16:43:43 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19427;
	Thu, 19 Jan 95 16:20:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19421;
	Thu, 19 Jan 95 16:20:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV6og-00038TC; Thu, 19 Jan 95 16:03 PST
To: pine-info@cac.washington.edu
From: lef@wuacn.wustl.edu (Lori Fox)
Subject: Re: Welcome to pine-info
Date: 19 Jan 1995 23:35:30 GMT
Message-Id: <3fmt02$r46@newsreader.wustl.edu>
References: <9501192250.AA10637@shivams.cac.washington.edu>

Majordomo@cac.washington.edu wrote:
: Welcome to the pine-info mailing list!


Forgive this novice, but may I assume that everything that goes to this 
mailing list will also go to comp.mail.pine ?

Thanks.



From owner-pine-info@cac.washington.edu  Thu Jan 19 17:31:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18755;
	Thu, 19 Jan 95 17:31:43 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21020;
	Thu, 19 Jan 95 17:22:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21014;
	Thu, 19 Jan 95 17:22:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rV7q0-00038KC; Thu, 19 Jan 95 17:08 PST
To: pine-info@cac.washington.edu
From: jonc@pinnacle.co.nz (Jonathan Chen)
Subject: Re: .signature over quoted text
Date: 20 Jan 1995 10:33:22 +1300
Message-Id: <3fmlr2$9qc@kea.pinnacle.co.nz>
References: <3fm55j$69d@bruce.uncg.edu>

In <3fm55j$69d@bruce.uncg.edu> wyrickk@myhost.subdomain.domain (Kevin Wyrick) writes:

>Hi,
>
>I'm convert from elm over to pine recently, and I have a question about
>the .signature file on my replies.  When I try to reply to any mail message
>and I copy the text from the first note, Pine will always start off with
>my signature first, and then below that it will put the quoted text.  Does
>anyone else have this problem?  Is there a switch somewhere in the setup
>or the .pinerc file that will fix this?
>

Enable the signature-at-bottom feature either by Setup/Config or editing
.pinerc feature-list entry.
-- 
+---------------------------------------------------------------------+
| Jonathan Chen <jonc@pinnacle.co.nz>     | #include <std/disclaimer> |
+---------------------------------------------------------------------+


From owner-pine-info@cac.washington.edu  Thu Jan 19 17:52:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19537;
	Thu, 19 Jan 95 17:52:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18809;
	Thu, 19 Jan 95 17:43:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18803;
	Thu, 19 Jan 95 17:43:50 -0800
Received: by hobbes.twntpe.cdc.com; Fri, 20 Jan 95 09:42:07 -0800
Date: Fri, 20 Jan 1995 09:42:05 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Lori Fox <lef@wuacn.wustl.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Welcome to pine-info
In-Reply-To: <3fmt02$r46@newsreader.wustl.edu>
Message-Id: <Pine.SOL.3.91.950120094003.3007A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 19 Jan 1995, Lori Fox wrote:

> Forgive this novice, but may I assume that everything that goes to this 
> mailing list will also go to comp.mail.pine ?

	Yes, you can assume that.  However, I've noticed that there is
often a delay between the time people post to comp.mail.pine and it
showing up on pine-info.  Today a piece written on Jan. 6th showed up
in the mail.....

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Thu Jan 19 22:30:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28705;
	Thu, 19 Jan 95 22:30:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25868;
	Thu, 19 Jan 95 22:20:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25862;
	Thu, 19 Jan 95 22:20:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVCSZ-00038MC; Thu, 19 Jan 95 22:04 PST
To: pine-info@cac.washington.edu
From: jcolman@j51.com <Jake@psg.com Colman - JNC Consulting Group>
Subject: Pine for MS-Windoze
Date: 19 Jan 1995 04:13:05 GMT
Message-Id: <3fkosh$ouc@j51.com>

Is there a version of Pine that will run over a PPP connection under Windoze?

Thanx!

..Jake




From owner-pine-info@cac.washington.edu  Thu Jan 19 23:44:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00677;
	Thu, 19 Jan 95 23:44:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24421;
	Thu, 19 Jan 95 23:36:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24415;
	Thu, 19 Jan 95 23:36:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVDb7-00038MC; Thu, 19 Jan 95 23:17 PST
To: pine-info@cac.washington.edu
From: gillman@almaak.usc.edu ([Howard Gillman])
Subject: Abort signal
Date: 19 Jan 1995 23:17:24 -0800
Message-Id: <3fno24$38e@almaak.usc.edu>

I asked a new listserv to send me mail in digest format.  When I received 
the message the index indicated that it was 43,810 characters.  When I 
opened the file I received a blank screen with a note 
"Parts/Attachments"; at the bottom of the blank screen it said "All of 
message text."  I tried to View the attachments, but the attachment index 
had nothing on it.  When I press [V]iew anyway pine quick with the 
message "But in Pine detected:  'Received abort signal.'  Exiting pine."  
So, what the heck is the problem with the message I received, and why 
can't I get access to it?  Thanks in advance.


From owner-pine-info@cac.washington.edu  Thu Jan 19 23:59:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01114;
	Thu, 19 Jan 95 23:59:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27182;
	Thu, 19 Jan 95 23:51:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27176;
	Thu, 19 Jan 95 23:51:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVDt2-00038RC; Thu, 19 Jan 95 23:36 PST
To: pine-info@cac.washington.edu
From: rhsiung@kaiwan009.kaiwan.com (Richard Hsiung)
Subject: Need HELP! BinHEX conversion?
Date: 19 Jan 1995 16:13:15 -0800
Message-Id: <3fmv6r$86n@kaiwan009.kaiwan.com>

I got a mail from someone with an attachment (supposedly), well, in the 
message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
BinHex and how do I get this attachment back into file form?

Please help!  Thanks....


--
Richard Hsiung <rhsiung@kaiwan.com>       PGP public key via finger/keyserver
                 WWW URL= http://www.kaiwan.com/~rhsiung


From owner-pine-info@cac.washington.edu  Fri Jan 20 00:17:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01580;
	Fri, 20 Jan 95 00:17:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27446;
	Fri, 20 Jan 95 00:08:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27440;
	Fri, 20 Jan 95 00:08:08 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa20043;
          20 Jan 95 0:56 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA08846; Fri, 20 Jan 1995 08:09:42 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id IAA01819; Fri, 20 Jan 1995 08:07:10 GMT
Date: Fri, 20 Jan 1995 08:07:10 +0000 (GMT)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Kevin Wyrick <wyrickk@myhost.subdomain.domain>
Cc: pine-info@cac.washington.edu
Subject: Re: .signature over quoted text
In-Reply-To: <3fm55j$69d@bruce.uncg.edu>
Message-Id: <Pine.LNX.3.91.950120080557.1806A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 19 Jan 1995, Kevin Wyrick wrote:

> Hi,
> 
> I'm convert from elm over to pine recently, and I have a question about
> the .signature file on my replies.  When I try to reply to any mail message
> and I copy the text from the first note, Pine will always start off with
> my signature first, and then below that it will put the quoted text.  Does
> anyone else have this problem?  Is there a switch somewhere in the setup
> or the .pinerc file that will fix this?
> 
> Thanks,
> 
> --
> Kevin Wyrick

If you are use pine v3.91 then from the main menu, press S (setup), C 
(config).  You then move to the feature list and check the signature at 
bottom item.


----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Fri Jan 20 01:45:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03847;
	Fri, 20 Jan 95 01:45:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28825;
	Fri, 20 Jan 95 01:35:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rzserv2.fh-lueneburg.de by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28803;
	Fri, 20 Jan 95 01:35:00 -0800
Received: by rzserv2.fh-lueneburg.de (AIX 3.2/UCB 5.64/4.03)
          id AA25512; Fri, 20 Jan 1995 10:33:28 +0100
Date: Fri, 20 Jan 1995 10:33:28 +0100 (NFT)
From: Ralf Matthies <matthies@rzserv2.fh-lueneburg.de>
To: Richard Hsiung <rhsiung@kaiwan009.kaiwan.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Need HELP! BinHEX conversion?
In-Reply-To: <3fmv6r$86n@kaiwan009.kaiwan.com>
Message-Id: <Pine.A32.3.91.950120100755.27547B-100000@rzserv2.fh-lueneburg.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 19 Jan 1995, Richard Hsiung wrote:

> I got a mail from someone with an attachment (supposedly), well, in the 
> message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
> BinHex and how do I get this attachment back into file form?
> 
> Please help!  Thanks....
> 
> 
> --
> Richard Hsiung <rhsiung@kaiwan.com>       PGP public key via finger/keyserver
>                  WWW URL= http://www.kaiwan.com/~rhsiung
> 


Hi,

you will find BinHex on the following aFTP servers:

              ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip
              micros.hensa.ac.uk  /mirrors/simtel/msdos/mac/binhex13.zip

and some other hosts (Mirrors of SimTel)
Or simply use ArchiePlexForm at:

        http://src.doc.ic.ac.uk/archieplexform.html

And now the things you have to do, when you've got BinHex:

   Start Pine (i use Version 3.91...)
   Press 'I' ( for Folder Index of Inbox)
   Select the message
   Press 'V' to View Message
   Press 'V' to view Attachment
   Select the Attachment (there are two or more, one with the original
    mail and one ore more attachments, i hope ;-)
   Press 'S' to save the attachment _without_ the rest of the mail
   I hope you will find the saved attachment in your actual directory
   or your Home directory

Use BinHex on a PC to extract the original file from the
binhex'ed file you have previously extracted.

Hope it will help,

Bye

(R)alf Matthies
Fachhochschule Nordostniedersachsen


PS: Ask me, if you have more questions... ;-)






From owner-pine-info@cac.washington.edu  Fri Jan 20 05:26:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09036;
	Fri, 20 Jan 95 05:26:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29231;
	Fri, 20 Jan 95 05:15:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29225;
	Fri, 20 Jan 95 05:15:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVIuV-00038KC; Fri, 20 Jan 95 04:57 PST
To: pine-info@cac.washington.edu
From: geert@dialis.xs4all.nl (Geert Bosch)
Date: 19 Jan 95 22:25:00 
Subject: Pine for OS/2 (!)
Message-Id: <5f8_9501200953@dialis.xs4all.nl>

For those interested, I read that Steve Willer is currently porting the Pine
reader to OS/2. At least there are some developments now...

Groetjes, Geert 



From owner-pine-info@cac.washington.edu  Fri Jan 20 05:50:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09459;
	Fri, 20 Jan 95 05:50:54 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02223;
	Fri, 20 Jan 95 05:40:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02217;
	Fri, 20 Jan 95 05:40:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVJIh-00038kC; Fri, 20 Jan 95 05:22 PST
To: pine-info@cac.washington.edu
From: pisati@pippo.sm.dsi.unimi.it (Stefano Pisati IW2JXK)
Subject: Space Problem...
Date: 20 Jan 1995 11:52:25 +0100
Message-Id: <3fo4la$5bk@pippo.sm.dsi.unimi.it>


Hi, I have installed Pine for HP-UX and I discover that requira
3.3 Mb of HD space !?! I'm not interested on NEWS capabiliti
cause I've another prg for this purpose... where can I find
the source of pine for HP-UX ? How can I compile it without
NEWS support ? In a short way... how to reduce the size of
pine bin ?!?

		 Tnx in advance !!!

                    73 de -_ Stefano _-
PS: Please, reply via e-mail. Tnx !!!

       "Stat rosa pristina nomine nomina nuda tenemus"
----------------------------------------------------------------
Stefano Pisati  IW2JXK          Internet: pisati@dsi.unimi.it
PGP:  finger pisati@ghost.dsi.unimi.it  or
      e-mail pgp@dsi.unimi.it with Subject: GET Pisati
     http://www.dsi.unimi.it/Users/Students/pisati/home
----------------------------------------------------------------




From owner-pine-info@cac.washington.edu  Fri Jan 20 06:27:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10243;
	Fri, 20 Jan 95 06:27:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00154;
	Fri, 20 Jan 95 06:12:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00147;
	Fri, 20 Jan 95 06:12:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVJuR-00038TC; Fri, 20 Jan 95 06:01 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Setting up for news, upgrading pine systemwide.
Date: Fri, 6 Jan 1995 13:37:11 -0800
Message-Id: <Pine.ULT.3.92.950106132601.2851P-100000@shiva1.cac.washington.edu>
References: <ellis.789413557@gmi.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ellis.789413557@gmi.edu> 

On 6 Jan 1995, R. Stewart Ellis wrote:

> Date: 6 JAN 95 17:32:37 GMT 
> From: R. Stewart Ellis <ellis@nova.gmi.edu>
> Newgroups: comp.mail.pine
> Subject: Setting up for news, upgrading pine systemwide. 
> 
> First of all, although I generally think pine is a great MUA, I am
> distinctly uncomfortable with it as a newsreader, preferring nn.  However I
> am the one who originally installed elm and nn on our site several years
> ago, followed shortly by tin, and about a year ago, pine.  Currently the
> systemwide pine is 3.89, but I want to upgrade to 3.91.  
> 
> Part of what prevented me was an error message I keep getting when running
> 3.91 about unbalanced {.  I posted on it in the past but got no real help.
> Today I finally figured it out.  It had to do with the value of
> news-collections in the systemwide pine.conf file.  It was set to:
> 
> news-collections=News/[] *{$NNTPSERVER/nntp}[]
> 
> which correctly pointed 3.89 at our nntpserver, set in a global cshrc file.
> However this was not being instantiated properly by 3.9{0|1}.  I had to
> experiment with brackets and parens until I finally got a version that would
> work correctly with both 3.89 and 3.91:
> 
> news-collections=News/[] *{${NNTPSERVER}/nntp}[]
> 

FWIW, if you set
	
	nntp-server=$NNTPSERVER

and leave news-collections blank, Pine 3.91 will assume a default
news-collection.  Note that the "News/[]" in your example above is only
the nickname for the collection and does not have any other significance. 
 
> 
> Now I am trying to make sense of the folders issue.  Although I would expect
> the immediately preceding news-collection setting to look in ~/News then at
> the nntpserver, I do not seem to see any folders from my ~/News directory.
> I also experimented with setting the folder-collection to:
> 
> folder-collections=Mail/[] News/[]
> 
> This latter gave me a merged list of folders from ~/Mail and ~/News, but I
> could not append to the folders that I knew were in News.  Part of this may
> have been because they were saved by nn, which does not by default setup a
> folder in completely proper UNIX mail format.  I also could not just save to
> the folders by name, so I am quite confused about the relationship between
> news and folders.
> 

"Mail/[]" in the above example is only specifying a nickname and does not
have anything to do with the ~/Mail directory.  You have specified a
folder collection called "Mail/[]" that resides in the ~/News directory... 

> The model I want, because it is most compatible with our other newsreaders
> and MUAs, is to have news saved in folders in ~/News, mail saved in ~/Mail.
> Then I want users to be able to open the folders of saved news in a way
> distinct from their mail folders.  I know this runs against the cognitive
> model that the pine team seem to be pushing, but it is the one I am most
> comfortable trying to support, as an unpaid volunteer, in addition to my 12
> hrs/qtr teaching load, maintaining gopher and www, and serving on about a
> dozen committees.
> 

You can have as many folder collections as you want in Pine, but the first
one listed is the default for saves from any collection. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Fri Jan 20 07:50:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12498;
	Fri, 20 Jan 95 07:50:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04109;
	Fri, 20 Jan 95 07:43:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from orca.fhcrc.org by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04103;
	Fri, 20 Jan 95 07:43:02 -0800
Received: by orca.fhcrc.org (AIX 3.2/UCB 5.64/4.03)
          id AA59135; Fri, 20 Jan 1995 07:44:08 -0800
Date: Fri, 20 Jan 1995 07:44:07 -0800 (PST)
From: Brent Blumenstein <brentb@orca.fhcrc.org>
To: Geert Bosch <geert@dialis.xs4all.nl>
Cc: pine-info@cac.washington.edu
Subject: Re: Pine for OS/2 (!)
In-Reply-To: <5f8_9501200953@dialis.xs4all.nl>
Message-Id: <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Now that is good news.  When?  And are beta testers needed.  I volunteer.

--
Brent A. Blumenstein                   | tel.:   206 667 4623
Fred Hutchinson Cancer Research Center | fax:    206 667 4408
1124 Columbia Street  MP-557           | e-mail: brentb@orca.fhcrc.org
Seattle, WA 98104    USA               |

On 19 Jan 1995, Geert Bosch wrote:

> For those interested, I read that Steve Willer is currently porting the Pine
> reader to OS/2. At least there are some developments now...
> 
> Groetjes, Geert 
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan 20 08:14:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13387;
	Fri, 20 Jan 95 08:14:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04513;
	Fri, 20 Jan 95 08:03:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04507;
	Fri, 20 Jan 95 08:03:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVLYR-00038QC; Fri, 20 Jan 95 07:47 PST
To: pine-info@cac.washington.edu
From: Brad <syb3@aber.ac.uk>
Subject: Re: Changing From: header
Date: Fri, 20 Jan 1995 11:14:59 +0000
Message-Id: <Pine.OSF.3.91.950120111207.28526C-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ii.790481918@shell1.best.com> 

	Yep indeedy! You have to uncomment the following line in
pine/osdep/os-xxx.h: 

/* #define ALLOW_CHANGING_FROM  /* comment out to not allow changing From */

Then you should be able to change your From address. However, I've never
tried doing it via the Customized-hdrs... 

 ___  _                     _a' /(   <.  Simon Bradley, Knight Protector!
/ __><_>._ _ _  ___ ._ _ ~~ _}\ \(  _  ) E-mail: syb3@aber.ac.uk
\__ \| || ' ' |/ . \| ' |      \(._(.)'  Finger: syb3@osfb.aber.ac.uk
<___/|_||_|_|_|\___/|_|_|     ._>. _>.   WWW: http://www.aber.ac.uk/~syb3/

On 18 Jan 1995, Nancy McGough wrote:

> I'd like to change the From: header in mail I send from Pine
> by putting something like this in my .pinerc:
> 
> customized-hdrs=Organization: $ORGANIZATION,
>         From: Nancy McGough <nancym@ii.com>
> 
> 
> Unfortunately, when I try this Pine gives a message that says
> I can't change the From header.  Is there any way around this?
> E.g., could the system admins reset something to allow this?
> 
> Thanks for any info,
> Nancy


From owner-pine-info@cac.washington.edu  Fri Jan 20 08:19:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13604;
	Fri, 20 Jan 95 08:19:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02281;
	Fri, 20 Jan 95 08:13:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02275;
	Fri, 20 Jan 95 08:13:53 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06947;
	Fri, 20 Jan 95 08:13:49 -0800
Date: Fri, 20 Jan 1995 08:13:49 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: "[Howard Gillman]" <gillman@almaak.usc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Abort signal
In-Reply-To: <3fno24$38e@almaak.usc.edu>
Message-Id: <Pine.ULT.3.92.950120081231.29471C-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Please use the Pine bug report command (B on the Main Menu) and say Yes 
when it asks you if you want to attach the problem message.

Thanks.

-teg

On 19 Jan 1995, [Howard Gillman] wrote:

> I asked a new listserv to send me mail in digest format.  When I received 
> the message the index indicated that it was 43,810 characters.  When I 
> opened the file I received a blank screen with a note 
> "Parts/Attachments"; at the bottom of the blank screen it said "All of 
> message text."  I tried to View the attachments, but the attachment index 
> had nothing on it.  When I press [V]iew anyway pine quick with the 
> message "But in Pine detected:  'Received abort signal.'  Exiting pine."  
> So, what the heck is the problem with the message I received, and why 
> can't I get access to it?  Thanks in advance.
> 


From owner-pine-info@cac.washington.edu  Fri Jan 20 09:16:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16978;
	Fri, 20 Jan 95 09:16:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06279;
	Fri, 20 Jan 95 09:06:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from bigdog.engr.arizona.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06273;
	Fri, 20 Jan 95 09:06:50 -0800
Received: by bigdog.engr.arizona.edu (5.65/DEC-Ultrix/4.3)
	id AA09876; Fri, 20 Jan 1995 10:07:39 -0700
Date: Fri, 20 Jan 1995 10:07:37 -0700 (MST)
From: "K. D. Akre Kristensen" <akre@bigdog.engr.arizona.edu>
To: pine-info@cac.washington.edu
Cc: "K. D. A. Kristensen" <akre@bigdog.engr.arizona.edu>
Subject: pine
Message-Id: <Pine.ULT.3.90.950120100524.9561A-100000@bigdog.engr.arizona.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Is there such an option available on pine to get "return receipt", i.e. 
after sending someone e-mail to recieve a message, etc., after the person 
has read that particular piece of e-mail?

Thanks,
Kris

+---------------------------------------------------------------------+
|  Kristen David Akre Kristensen     { akre@bigdog.engr.arizona.edu } |
|  Chemical Engineering Dept.                                         |
|  University of Arizona, Tucson, AZ                                  |
+=====================================================================+
|  "I swear -- by my life and my love of it -- that I will never live |
|   for the sake of another man, nor ask another man to live for      |
|   mine."  (Ayn Rand)                                                |
+---------------------------------------------------------------------+
|  "A man's gotta know his limitations." (Dirty Harry)                |
+=====================================================================+



From owner-pine-info@cac.washington.edu  Fri Jan 20 11:08:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23267;
	Fri, 20 Jan 95 11:08:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06652;
	Fri, 20 Jan 95 11:01:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06646;
	Fri, 20 Jan 95 11:01:16 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVOKV-00038RC; Fri, 20 Jan 95 10:45 PST
To: pine-info@cac.washington.edu
From: "J. Kelly Cunningham" <deviate@lipschitz.sfasu.edu>
Subject: Re: Using Pine to Read Usenet. 
Message-Id: <Pine.NXT.3.91.950119190957.745B-100000@lipschitz>
Date: Thu, 19 Jan 1995 19:13:59 -0600
References: <Pine.ULT.3.91.950116145821.11172F-100000@saturn> 
In-Reply-To: <Pine.ULT.3.91.950116145821.11172F-100000@saturn> 
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

-----BEGIN PGP SIGNED MESSAGE-----

On Mon, 16 Jan 1995, Johan T Lindgren aka Lindus @ IRC wrote:

   	Hmm, perhaps I am just daft or haven't found the right function
   yet but: How do I make a whole subject marked in such a way that I don't
   have to see it any more? I mean in whatever version of rn you got there is
   a "junk subject" or something equally sound. I don't crave for the command
   to eXpunge them as well, but it would be great though. I suppose one could
   sort the subjects and then just read what one is interested in and so on
   but still...
   	Ok, that was what I wondered about and if there isn't any command 
   like this I think there should be one.
   
   		Johan T Lindgren aka Lindus @ IRC
   
;ts string adx  junks subjects containing "string" for the current 
session.   



-----BEGIN PGP SIGNATURE-----
Version: 2.6.1

iQCVAgUBLx655OBu0383Om6dAQHr0AP+LQ5zNiIU/GuNGuDXQOKUAbEduedu9hyI
LR18gFHCPoTrB+137r1EdDAd9ARXgeFGhA2C6Amln1rvNsA3aaui7bOTjD5iu37Q
m4gqX5FccjsA5Uyktr7spfg1ORQox9Rrl/ma8xTRUJUaHvf67h5jszLC2p8OIM+i
9U9G9moSHd0=
=mHA9
-----END PGP SIGNATURE-----


-- kc       prudence dictates a low profile -- Sandy Sandfort
          finger deviate@lipschitz.sfasu.edu | pgp -fka +force


From owner-pine-info@cac.washington.edu  Fri Jan 20 11:49:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25419;
	Fri, 20 Jan 95 11:49:09 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10249;
	Fri, 20 Jan 95 11:37:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10243;
	Fri, 20 Jan 95 11:37:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVOsj-00038MC; Fri, 20 Jan 95 11:20 PST
To: pine-info@cac.washington.edu
From: swald@cde2s.ssc.wisc.edu (Sandra Wald)
Subject: getting elm mail aliases/addresses into PINE addressbook
Date: 20 Jan 1995 16:17:00 GMT
Message-Id: <3fonls$fpg@news.doit.wisc.edu>

Does anyone have a program/procedure for putting Elm's mail aliases (addresses)
into the PINE address book?

many thanks,
Sandra
Keywords: 


-- 
Sandra J. Wald
swald@ssc.wisc.edu
(608) 265-4922


From owner-pine-info@cac.washington.edu  Fri Jan 20 11:52:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25534;
	Fri, 20 Jan 95 11:52:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07869;
	Fri, 20 Jan 95 11:45:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.ge.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07863;
	Fri, 20 Jan 95 11:45:46 -0800
Received: from [3.12.38.33] by ns.GE.com (5.65/GE Gateway 1.32) with SMTP
	 id AA24366; Fri, 20 Jan 1995 14:45:43 -0500
Received: by mmpcs1.PSF.GE.COM (4.1/GEA Sun server 2.7)
	id AA16120; Fri, 20 Jan 95 14:44:08 EST
Date: Fri, 20 Jan 1995 14:44:07 -0500 (EST)
From: Don Sugarman <sugarman@mmpcs1.psf.ge.com>
To: Pine Info Mail List <pine-info@cac.washington.edu>
Subject: PINE for HP/UX 9.05
Message-Id: <Pine.SUN.3.90.950120144004.16107A-100000@mmpcs1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'd like to compile pine on an HP 712 running under HP/UX 9.05.  Can
someone point me to the source for this platform.  We have the 3.90 and 
3.91(B) tar files.  Do we need a special makefile?

Thanks in advance.

Don Sugarman
Martin Marietta Defense Systems
sugarman@mmpcs1.psf.ge.com



From owner-pine-info@cac.washington.edu  Fri Jan 20 11:57:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25852;
	Fri, 20 Jan 95 11:57:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08044;
	Fri, 20 Jan 95 11:52:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08038;
	Fri, 20 Jan 95 11:52:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVP8V-00038RC; Fri, 20 Jan 95 11:36 PST
To: pine-info@cac.washington.edu
From: Leslie Troutman <troutman@ux1.cso.uiuc.edu>
Subject: Suppressing list of names in Address List
Date: Fri, 20 Jan 1995 10:36:21 -0600
Message-Id: <Pine.DYN.3.91.950120103357.16617B-100000@ux1.cso.uiuc.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have created an address list of about 40 people that I need to send a
monthly message to.  Is there anyway to suppress the list of names?  I
would like to just display a group name and not take up all that space
with each name and address.  Please reply to my email address.  Thanks,
Leslie

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Leslie Troutman					EMAIL:	TROUTMAN@UIUC.EDU
Music User-Services Coordinator			PHONE:	217-244-4071
University of Illinois at Urbana-Champaign	FAX:	217-244-9097
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



From owner-pine-info@cac.washington.edu  Fri Jan 20 12:07:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26540;
	Fri, 20 Jan 95 12:07:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10794;
	Fri, 20 Jan 95 12:00:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from kaiwan.kaiwan.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10788;
	Fri, 20 Jan 95 12:00:47 -0800
Received: from kaiwan009.kaiwan.com (416@kaiwan009.kaiwan.com [198.178.203.9]) by kaiwan.kaiwan.com (8.6.9/8.6.5) with ESMTP 
	  id MAA20661; Fri, 20 Jan 1995 12:00:41 -0800
	  *** KAIWAN Internet Access ***
Received: (from rhsiung@localhost) by kaiwan009.kaiwan.com (8.6.9/8.6.9)
	  id MAA28195; Fri, 20 Jan 1995 12:00:44 -0800
	  *** KAIWAN Internet Access ***
To: matthies@rzserv2.fh-lueneburg.de
Cc: pine-info@cac.washington.edu
From: rhsiung@kaiwan.com (Richard Hsiung)
Subject: Re: Need HELP! BinHEX conversion?
Date: Fri, 20 Jan 1995 11:36:05 -0800
Organization: pi alpha omega epsilon alpha
Message-Id: <b218lCO9arX6078yn@kaiwan.com>
In-Reply-To: <Pine.A32.3.91.950120100755.27547B-100000@rzserv2.fh-lueneburg.de>
X-Mailer: Yarn 0.78 with YESX v.0.14.B0115
Lines: 18


>              ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip

>Use BinHex on a PC to extract the original file from the
>binhex'ed file you have previously extracted.

Thanks a lot for the location of binhex.  I was looking in
/msdos/decode and couldn't find anything there!  However, after
decoding the file, I got a binary file called Picture_1 which
supposedly was scanned with hyperscan on a Mac.  Any ideas on how
to read this picture?  (I'm on a PC)

Thanks again for the help!


--
Richard Hsiung <rhsiung@kaiwan.com>       PGP public key via finger/keyserver
                 WWW URL= http://www.kaiwan.com/~rhsiung


From owner-pine-info@cac.washington.edu  Fri Jan 20 12:19:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27100;
	Fri, 20 Jan 95 12:19:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11323;
	Fri, 20 Jan 95 12:14:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.ge.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11317;
	Fri, 20 Jan 95 12:14:35 -0800
Received: from [3.12.38.33] by ns.GE.com (5.65/GE Gateway 1.32) with SMTP
	 id AA27203; Fri, 20 Jan 1995 15:14:33 -0500
Received: by mmpcs1.PSF.GE.COM (4.1/GEA Sun server 2.7)
	id AA16248; Fri, 20 Jan 95 15:13:02 EST
Date: Fri, 20 Jan 1995 15:13:01 -0500 (EST)
From: Don Sugarman <sugarman@mmpcs1.psf.ge.com>
To: Pine Info Mail List <pine-info@cac.washington.edu>
Subject: Re: PINE for HP/UX 9.05
In-Reply-To: <Pine.SUN.3.90.950120144004.16107A-100000@mmpcs1>
Message-Id: <Pine.SUN.3.90.950120151200.16241A-100000@mmpcs1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Cancel request!!!!!!!!!!!!!!

Just downloaded source and executables from ftp.cac....

Love that NET. :-)

Don Sugarman
sugarman@mmpcs1.psf.ge.com

On Fri, 20 Jan 1995, Don Sugarman wrote:

> I'd like to compile pine on an HP 712 running under HP/UX 9.05.  Can
> someone point me to the source for this platform.  We have the 3.90 and 
> 3.91(B) tar files.  Do we need a special makefile?
> 
> Thanks in advance.
> 
> Don Sugarman
> Martin Marietta Defense Systems
> sugarman@mmpcs1.psf.ge.com
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan 20 14:16:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03539;
	Fri, 20 Jan 95 14:16:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12158;
	Fri, 20 Jan 95 14:06:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from suprahwy.supra.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12150;
	Fri, 20 Jan 95 14:06:23 -0800
Received: from localhost (smap@localhost) by suprahwy.supra.com (8.6.5/8.6.5) id OAA21841 for <pine-info@cac.washington.edu>; Fri, 20 Jan 1995 14:06:19 -0800
Received: from a_mail.supra.com(192.203.198.11) by suprahwy via smap (V1.0mjr)
	id sma021839; Fri Jan 20 14:06:16 1995
Received: from altos.supra.com by a_mail.supra.com id aa27141;
          20 Jan 95 14:06 PST
From: Jerry Koch <jerry@supra.com>
Reply-To: jerry@supra.com
To: pine-info@cac.washington.edu
Subject: help
Date: Fri Jan 20 14:02:25 1995
Message-Id:  <9501201402.aa29549@altos.supra.com>

help



From owner-pine-info@cac.washington.edu  Fri Jan 20 14:39:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05046;
	Fri, 20 Jan 95 14:39:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15209;
	Fri, 20 Jan 95 14:30:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from omega.oac.ucla.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15203;
	Fri, 20 Jan 95 14:30:46 -0800
Received: from youngpc.mic.ucla.edu by ucla.edu (AIX 3.2/UCB 5.64/4.03)
          id AA15883; Fri, 20 Jan 1995 14:30:45 -0800
Date: Fri, 20 Jan 1995 14:30:42 -0800 (PST)
From: Grant Young <young@ucla.edu>
To: pine-info@cac.washington.edu
Cc: Patrick Burke <burke@ucla.edu>
Subject: Packet ver. of Pine troubles
X-Sender: young@ben2.ucla.edu
Message-Id: <Pine.PCN.3.90.950120142914.13209A-100000@[128.97.72.121]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Well, I've posted this question a couple of times on comp.mail.pine
with no response.  Perhaps this will be my lucky day!

I'm truly in need of help.  I want to use the packet version of
PC Pine 3.91 (or 3.90) to connect via a SLIP connection to my school's
mail/news system.  I am using the Univ. of Minnesota's UMSLIP.COM
Packet driver for SLIP, version 2.1 and PHONE.EXE to dial into
my school's slip server.  Gopher, Minuet and DosLynx are working
great.  Whenever I try to run Pine, I get an error message stating
that BOOTP failed.  When I manually enter my IP address, gateway,
nameserver, etc., Pine returns a message stating that my INBOX cannot
be opened because the [Host cannot be found].

I can successfully run the packet version of PC Pine with the Crynwr
Packet driver for a 3c509 NIC, version 11.2.  I do not use BOOTP
when I use the Crynwr 3c509 packet driver.

Any thoughts as to what the problem is?

Grant Young
young@ucla.edu
UCLA OAC Microcomputer Support Office




From owner-pine-info@cac.washington.edu  Fri Jan 20 15:21:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07499;
	Fri, 20 Jan 95 15:21:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16305;
	Fri, 20 Jan 95 15:12:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16299;
	Fri, 20 Jan 95 15:12:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVSGF-00038bC; Fri, 20 Jan 95 14:56 PST
To: pine-info@cac.washington.edu
From: Brad <syb3@aber.ac.uk>
Subject: Re: Looking for Windows newsreader with marking ability
Date: Fri, 20 Jan 1995 18:50:17 +0000
Message-Id: <Pine.OSF.3.91.950120183842.31227D-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.92.950118124528.19446C-100000@shiva1.cac.washington.edu> 

	I *think* I've found a bug in this. I'm running Pine on a DEC OSF
system, and if I hit 'N' to go over a post/posts (I want to keep it/them
so that it/they appear in the index next time) and then delete posts after
this one, the next time I go into that news group, these posts do *not*
appear, although they remain marked unread in my .newsrc file (e.g.
comp.mail.pine: 1-3242,3244,3246-3247). If, however, I go to the news
group by using the 'G' command, then they *do* show up in the index! 

	If you have any ideas about this, I'd be glad to know why it
happens (and if there's anything I can do about it)! If not, then maybe
the Pine Team can check it out (though maybe not on an OSF system... does
this happen on other platforms?). 

	Thanks, Pine People (especially the Pine Team--you do a great
job)! 

 ___  _                     _a' /(   <.  Simon Bradley, Knight Protector!
/ __><_>._ _ _  ___ ._ _ ~~ _}\ \(  _  ) E-mail: syb3@aber.ac.uk
\__ \| || ' ' |/ . \| ' |      \(._(.)'  Finger: syb3@osfb.aber.ac.uk
<___/|_||_|_|_|\___/|_|_|     ._>. _>.   WWW: http://www.aber.ac.uk/~syb3/

On Wed, 18 Jan 1995, Terry Gray wrote:

> However, the "Pine theory of 
> newsreading" is that news articles of no further interest get marked as 
> Deleted and become invisible in the next session, thus leaving only the 
> messages that you might want to go back and look at again.


From owner-pine-info@cac.washington.edu  Fri Jan 20 15:42:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08708;
	Fri, 20 Jan 95 15:42:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14581;
	Fri, 20 Jan 95 15:36:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14573;
	Fri, 20 Jan 95 15:36:47 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16821;
	Fri, 20 Jan 95 15:36:30 -0800
Date: Fri, 20 Jan 1995 15:36:29 -0800 (PST)
From: David L Miller <dlm@cac.washington.edu>
To: Brent Blumenstein <brentb@orca.fhcrc.org>
Cc: Geert Bosch <geert@dialis.xs4all.nl>, pine-info@cac.washington.edu
Subject: Re: Pine for OS/2 (!)
In-Reply-To: <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org>
Message-Id: <Pine.ULT.3.92.950120153515.22534j-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Mike Frisch <mfrisch@io.org> has also reported that he is working on an OS/2
port of Pine....

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 20 Jan 1995, Brent Blumenstein wrote:

> Date: Fri, 20 Jan 1995 07:44:07 -0800 (PST)
> From: Brent Blumenstein <brentb@orca.fhcrc.org>
> To: Geert Bosch <geert@dialis.xs4all.nl>
> Cc: pine-info@cac.washington.edu
> Subject: Re: Pine for OS/2 (!)
> 
> Now that is good news.  When?  And are beta testers needed.  I volunteer.
> 
> --
> Brent A. Blumenstein                   | tel.:   206 667 4623
> Fred Hutchinson Cancer Research Center | fax:    206 667 4408
> 1124 Columbia Street  MP-557           | e-mail: brentb@orca.fhcrc.org
> Seattle, WA 98104    USA               |
> 
> On 19 Jan 1995, Geert Bosch wrote:
> 
> > For those interested, I read that Steve Willer is currently porting the Pine
> > reader to OS/2. At least there are some developments now...
> > 
> > Groetjes, Geert 
> > 
> > 
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan 20 18:31:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16715;
	Fri, 20 Jan 95 18:31:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18656;
	Fri, 20 Jan 95 18:26:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18650;
	Fri, 20 Jan 95 18:26:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVVJ1-00038VC; Fri, 20 Jan 95 18:11 PST
To: pine-info@cac.washington.edu
From: Dierk Schwick <zrnsc01@stoertebeker.zdv.uni-tuebingen.de>
Subject: [Q] How can I include video attachments (.mpeg) ?
Date: Fri, 20 Jan 1995 17:23:49 +0100
Message-Id: <Pine.LNX.3.91.950120165657.5045A-100000@stoertebeker.zdv.uni-tuebingen.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I didn't find any answer in the FAQ's nor in documentations at
http://www.cac.washington.edu:1180/pine/

therefore i ask here.

I want to know if and when how it's possible to include video animations
in a normal email message with pine and have a look on them later on from 
pine via external viewer.

When I try so have a look on the attachment it's impossible in Pine!
Images will be shown via the image-viewer configuration in .pinerc or
my .mailcap but .mpegs aren't recogneized. It looks like that they 
are mime-coded as application and not as video.

Here an extract from my .mailcap:

# This maps MPEG video data to the viewer 'mpeg_play'.
# (Mpeg_play is part of the MPEG distribution from The Berkeley Plateau
# Research Group and is available via anonymous ftp from toe.cs.berkeley.edu.)
video/mpeg; mpeg_play %s ; test=test -n "$DISPLAY"

# Type octet-stream (binary) data can be displayed as a hex dump before
# you decide whether or not you want to save it to a file.  (Hd is just
# a standard hex dump program.  You could use "od" if you don't have an
# "hd".  Naive users may find the output from this entry confusing.)
application/octet-stream; hd; copiousoutput; description="Hex dump of data"

There is no global mailcap only my personal here! And the global pine.conf
looks like the personal (the viewers obviously)

INcluding postscript-files or images works really fine. When i want to 
have a look on the attachments the external viewer (ghostview or xv) will
be opened automatically from pine. So far so good, but why don't work my 
animations?

I don't read ths conference regularly, therefore please post answers to my
email address, too! 

Thanks a lot!

-- Dierk Schwick

----------------------------------------------------------------------------
Dierk Schwick                          |Tel.:               +49-7071-29-6957
                                       |Fax :               +49-7071-29-5912
Zentrum fuer Datenverarbeitung         |privat:               +49-7071-49813
Universitaet Tuebingen                 |email: dschwick@zdv.uni-tuebingen.de
----------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Fri Jan 20 18:51:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17201;
	Fri, 20 Jan 95 18:51:02 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20623;
	Fri, 20 Jan 95 18:46:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20617;
	Fri, 20 Jan 95 18:46:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVVcP-00038TC; Fri, 20 Jan 95 18:32 PST
To: pine-info@cac.washington.edu
From: isdmill@gatekeeper.ddp.state.me.us (David Miller)
Subject: Re: Welcome to pine-info
Date: 20 Jan 1995 15:01:47 -0500
Message-Id: <3fp4rb$7cp@gatekeeper.ddp.state.me.us>
References: <9501192250.AA10637@shivams.cac.washington.edu> <3fmt02$r46@newsreader.wustl.edu>

Lori Fox (lef@wuacn.wustl.edu) wrote:
: Majordomo@cac.washington.edu wrote:
: : Welcome to the pine-info mailing list!


: Forgive this novice, but may I assume that everything that goes to this 
: mailing list will also go to comp.mail.pine ?

: Thanks.

Does anyone know of software which does this automatically?  I would love 
to move a bunch of maillists to local newsgroups!

Thanks in advance,

--- David
-- 
David Miller			Usual disclaimers apply
Maine State Government


From owner-pine-info@cac.washington.edu  Fri Jan 20 20:38:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20133;
	Fri, 20 Jan 95 20:38:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20555;
	Fri, 20 Jan 95 20:33:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20549;
	Fri, 20 Jan 95 20:33:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVXDu-00038RC; Fri, 20 Jan 95 20:14 PST
To: pine-info@cac.washington.edu
From: Ray McAllister <mcallist@gate.net>
Subject: Re: pine
Date: Fri, 20 Jan 1995 17:25:19 -0500 (EST)
Message-Id: <Pine.A32.3.90.950120172345.65770F-100000@seminole.gate.net>
References: <Pine.ULT.3.90.950120100524.9561A-100000@bigdog.engr.arizona.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.90.950120100524.9561A-100000@bigdog.engr.arizona.edu> 

Kris, I may be too new to know that this is not an answer, but I put my 
email address in the cc. when I mail. IfI get a copy of my message, it 
went out and probably was received. Too simple???

Ray McAllister, Prof (Emeritus) Ocean Eng., FAU, Boca Raton, FL 33064
Diving Dinosaur, Geologist/Oceanographer/Ocean Engineer, 43 years SCUBA
mcallist@gate.net (305) 426-0808, Author Diving Locations, Boynton/Dania


On 20 Jan 1995, K. D. Akre Kristensen wrote:

> Is there such an option available on pine to get "return receipt", i.e. 
> after sending someone e-mail to recieve a message, etc., after the person 
> has read that particular piece of e-mail?
> 
> Thanks,
> Kris
> 
> +---------------------------------------------------------------------+
> |  Kristen David Akre Kristensen     { akre@bigdog.engr.arizona.edu } |
> |  Chemical Engineering Dept.                                         |
> |  University of Arizona, Tucson, AZ                                  |
> +=====================================================================+
> |  "I swear -- by my life and my love of it -- that I will never live |
> |   for the sake of another man, nor ask another man to live for      |
> |   mine."  (Ayn Rand)                                                |
> +---------------------------------------------------------------------+
> |  "A man's gotta know his limitations." (Dirty Harry)                |
> +=====================================================================+
> 
> 
> 
> 
> 


From owner-pine-info@cac.washington.edu  Fri Jan 20 21:14:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21143;
	Fri, 20 Jan 95 21:14:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21073;
	Fri, 20 Jan 95 21:10:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21067;
	Fri, 20 Jan 95 21:09:57 -0800
Received: by hobbes.twntpe.cdc.com; Sat, 21 Jan 95 13:08:15 -0800
Date: Sat, 21 Jan 1995 13:08:14 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Ray McAllister <mcallist@gate.net>
Cc: pine-info@cac.washington.edu
Subject: Re: pine
In-Reply-To: <Pine.A32.3.90.950120172345.65770F-100000@seminole.gate.net>
Message-Id: <Pine.SOL.3.91.950121130057.4901A-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 20 Jan 1995, Ray McAllister wrote:

> Kris, I may be too new to know that this is not an answer, but I put my 
> email address in the cc. when I mail. IfI get a copy of my message, it 
> went out and probably was received. Too simple???

	Yes, too simple.....and too assuming.

	If you cc: yourself the message to you only "loops" within the
system that you are using.  It only means you received it.

> On 20 Jan 1995, K. D. Akre Kristensen wrote:
> 
> > Is there such an option available on pine to get "return receipt", i.e. 
> > after sending someone e-mail to recieve a message, etc., after the person 
> > has read that particular piece of e-mail?

	There is a *non-standard* way to "request" delivery report.  That 
way is to create a custom header like "Return-Receipt-To: your@addres.com"
If the MTA at the receiving end supports this....chances are you will get
a "delivery report".  

	The "read receipt" generally implemented at the UA.  At this point
it is totally non-standard.  Some UAs implement their own proprietary methods
for "read receipt".

	Be advised that there is work currently going on to standardize 
various types of "notifications."  

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Fri Jan 20 21:28:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21436;
	Fri, 20 Jan 95 21:28:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22877;
	Fri, 20 Jan 95 21:24:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22870;
	Fri, 20 Jan 95 21:24:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVY3j-00038QC; Fri, 20 Jan 95 21:08 PST
To: pine-info@cac.washington.edu
From: offsite@crl.com (Lee (not F) Bailey)
Subject: Re: .signature over quoted text
Date: 20 Jan 1995 23:23:20 GMT
Message-Id: <3fpgl8$odk@nntp.crl.com>
References: <3fm55j$69d@bruce.uncg.edu> <Pine.LNX.3.91.950120080557.1806A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>

It should be noted that the signature-at-bottom switch only works for 
replies not forwards. There is no way to put sig at bott for forwards, 
unless you manually add it using ^R.



--
______________________________________________________________________________
Lee Bailey	|  E-Mail:   offsite@crl.com
	User of Geoworks Ensemble instead of M$ Windoze
	Try the demo at ftp://arginine.umdnj.edu/pub/geos/publish
		     or ftp://ftp.mcs.com/mcsnet.users/jbarr/GeoPublish	


From owner-pine-info@cac.washington.edu  Fri Jan 20 22:01:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22335;
	Fri, 20 Jan 95 22:01:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21761;
	Fri, 20 Jan 95 21:57:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21755;
	Fri, 20 Jan 95 21:57:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVYZm-00038cC; Fri, 20 Jan 95 21:41 PST
To: pine-info@cac.washington.edu
From: fetchi@freenet2.scri.fsu.edu (Ivan Fetch)
Subject: Off-Line Mail Reading/Writing?
Date: 21 Jan 1995 03:06:19 GMT
Message-Id: <3fptnb$fn5@freenet3.scri.fsu.edu>



    I am currently using Pine on a FreeNet, which has no Slip or PPP
connection.  Is there an off-line mail reader I can used to read and write
mail, then upload it back to my Mail directory and have pine send the
newly writtn mail?  Any ideas?  I'd appreciate anyone emailing me with
their suggestions.


<pine is the best!>



From owner-pine-info@cac.washington.edu  Fri Jan 20 22:31:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22988;
	Fri, 20 Jan 95 22:31:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23613;
	Fri, 20 Jan 95 22:27:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23607;
	Fri, 20 Jan 95 22:27:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVZ1E-00038YC; Fri, 20 Jan 95 22:09 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: Need Pine Binaries
Date: 20 Jan 1995 15:38:53 -0800
Message-Id: <3fphid$a38@garlic.com>

Hello again ...

I am still trying to find someone out there who can tell me where I can ftp 
Pine binaries for SCO  ...

Thanks for your help.

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


From owner-pine-info@cac.washington.edu  Sat Jan 21 03:23:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29698;
	Sat, 21 Jan 95 03:23:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25870;
	Sat, 21 Jan 95 03:19:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25864;
	Sat, 21 Jan 95 03:19:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVdZa-00038TC; Sat, 21 Jan 95 03:01 PST
To: pine-info@cac.washington.edu
From: icaseadm@icase.edu (ICASE System Administrator)
Subject: HELP....
Date: 21 Jan 1995 00:54:53 GMT
Message-Id: <3fpm0t$hnd@reznor.larc.nasa.gov>

I am in the process of installing Pine 3.91 on our Sun systems as well as the PC network
using windows.  I *think* the software has been installed correctly on the sun's as I am
able to read/send mail without any problems...
The PC's for some reason are not working...when I try to run pine from one of the PC's, the
INBOX does not get opened...I am aware that the pinerc has to be changed...I am not sure as
to what entry I need to put for the INBOX...
our server name: fennel.cs.hamptonu.edu
smtp-server: fennel.cs.hamptonu.edu
imap server: fennel.cs.hamptonu.edu

this is the entry in the pinerc file currently: inbox-path=/var/spool/mail/$USER  (SUN'S)
PC's: inbox-path={fennel.cs.hamptonu.edu}/var/spool/mail --- I know this entry is incorrect..

Any help will be greatly appreciated..... PLEASE EMAIL DIRECTLY TO ME AT:
tm@cs.hamptonu.edu 

thanking you in advance.....

tm@cs.hamptonu.edu  PLEASE DONT POST TO THIS NEWSGROUP...email to me..


From owner-pine-info@cac.washington.edu  Sat Jan 21 08:40:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06240;
	Sat, 21 Jan 95 08:40:40 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29940;
	Sat, 21 Jan 95 08:36:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from admin.aurora.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29934;
	Sat, 21 Jan 95 08:36:08 -0800
Received: by admin.aurora.edu (5.65/DEC-Ultrix/4.3)
	id AA04030; Sat, 21 Jan 1995 10:36:34 -0600
Date: Sat, 21 Jan 1995 10:36:34 -0600 (CST)
From: Steve Lowe <slowe@admin.aurora.edu>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Handling Return Receipts within PINE
Message-Id: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


As soon as I read Ed Gresshko's latest message on handling return 
receipts within PINE, I wanted to try it.  Below is the message that I 
received (as a receipt).  The sender is the mailer-daemon, not the 
purpose who reads the message.

What I was hoping for was that the receipt would appear to have come from 
the message reader, not the mailer-daemon.

Any suggestions?  This is a big (but not major) issue for some of my PINE 
users.

TIA.

 - Steve Lowe
   Aurora University                  slowe@admin.aurora.edu

---------- Forwarded message ----------
Date: Sat, 21 Jan 1995 10:27:40 -0600
From: Mail Delivery Subsystem <MAILER-DAEMON@admin.aurora.edu>
To: slowe@admin.aurora.edu
Subject: Returned mail: Return receipt

   ----- Transcript of session follows -----

  ----- Message header follows -----
Date: Sat, 21 Jan 1995 10:27:40 -0600 (CST)
From: Steve Lowe <slowe>
To: Datatel Login <datatel>
Subject: Test of Receipt
Message-Id: <Pine.ULT.3.91.950121102715.3947A-100000@admin.aurora.edu>
Return-Receipt-To: slowe
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



From owner-pine-info@cac.washington.edu  Sat Jan 21 09:58:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07935;
	Sat, 21 Jan 95 09:58:10 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01065;
	Sat, 21 Jan 95 09:55:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01059;
	Sat, 21 Jan 95 09:55:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVjoU-00038PC; Sat, 21 Jan 95 09:41 PST
To: pine-info@cac.washington.edu
From: classonl@usnet.us.net (Mike Sullivan)
Subject: Pine on ISC unix?
Date: 21 Jan 1995 12:31:31 -0500
Message-Id: <3frgdj$iev@usnet.us.net>

Does anyone have/know of an ftp site for an executable version of pine 
for ISC v3.0 unix? If not, can I compile the source w/ ISCs standard cc 
w/ few problems?


From owner-pine-info@cac.washington.edu  Sat Jan 21 12:53:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11801;
	Sat, 21 Jan 95 12:53:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04354;
	Sat, 21 Jan 95 12:50:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04348;
	Sat, 21 Jan 95 12:50:21 -0800
Received: from kelly.teleport.com (knute@kelly.teleport.com [192.108.254.10]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id MAA08594 for <pine-info@cac.washington.edu>; Sat, 21 Jan 1995 12:50:19 -0800
Date: Sat, 21 Jan 1995 12:50:17 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: "Robert Mann Packaging Co." <rmp@garlic.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Need Pine Binaries
In-Reply-To: <3fphid$a38@garlic.com>
Message-Id: <Pine.SUN.3.91.950121124836.6023A-100000@kelly.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 20 Jan 1995, Robert Mann Packaging Co. wrote:

> Hello again ...
> 
> I am still trying to find someone out there who can tell me where I can ftp 
> Pine binaries for SCO  ...
> 
> Thanks for your help.
> 
> ============================================================================
> Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
> bill@rmp.com   rmp@garlic.com   408/848-5440
> 
I have been told there are some at celestial.com, but I have yet to find 
them.  

 ---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646



From owner-pine-info@cac.washington.edu  Sat Jan 21 13:44:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13005;
	Sat, 21 Jan 95 13:44:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05061;
	Sat, 21 Jan 95 13:41:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05055;
	Sat, 21 Jan 95 13:41:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVnMb-00038MC; Sat, 21 Jan 95 13:28 PST
To: pine-info@cac.washington.edu
From: scott@henson.cc.wwu.edu (J. Scott Williams)
Subject: PC Pine and NFS?
Message-Id: <1995Jan21.211826.20141@henson.cc.wwu.edu>
Date: Sat, 21 Jan 1995 21:18:26 GMT


We currently are successfully using Pine on our Unix platforms.  We
want to develop an additional method of reading email using PC-Pine
from within MS Windows using IMAP and NFS.  The PC Pine method will be
primarily for use in student labs.  We want to be able to use IMAP to
read the INBOX and folders and use NFS to access the address books and
signature files on the Unix systems.  At this time we have the IMAP
part working.

I am looking for any configuration information, product names, tips of
any nature from people who have successfully done the NFS part.

Thank you.

-jscott-

-- 
|J. Scott Williams, BH 313     Ph: (360) 650-2868  FAX: (360) 650-7323 |
|Academic Tech. User Services  Internet:  scott@cc.wwu.edu             |
|Western Washington Univ.      "Internet--Talking across the electronic|
|Bellingham, WA  98225-9094               back fence of the world."-JSW|


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:50:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10132;
	Sun, 22 Jan 95 09:50:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20091;
	Sun, 22 Jan 95 09:45:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20085;
	Sun, 22 Jan 95 09:45:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVp2P-00038cC; Sat, 21 Jan 95 15:16 PST
To: pine-info@cac.washington.edu
From: FLAVELL@crnvma.cern.ch (Alan J Flavell)
Subject: Q. about HUJI VMS Pine 3.91 beta 3
Message-Id: <1732D14368S86.FLAVELL@cernvm.cern.ch>
Date: Sat, 21 Jan 1995 22:59:52 GMT

Is there a better place for discussing the HUJI port of VMS Pine?
I see some discussions here (and some where it is not clear whether
the HUJI port is meant, or the one associated with PMDF), but
perhaps there is a mailing list specifically for this package?
 
I am just starting to investigate the HUJI port.  I acquired
PINE_3_91_BETA_3.ZIP to our VMS system, which uses Multinet, and
built it with the Multinet option.  Everything seemed to go well.
 
Problem I am having is that whenever I try to compose a message,
it asks if I want to continue the postponed one.  If I say no, it
works OK.  If I say yes or take the default, it crashes.  The
README.VMS _says_ that "messages cannot be postponed".
 
What makes it think I have a postponed mail?
 
Also, can someone explain just what it means under 1. in "Restrictions"?
It says "the user must not switch to another folder as long as NEWMAIL
has items".  Does something terrible happen?
 
regards


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:55:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10230;
	Sun, 22 Jan 95 09:55:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20140;
	Sun, 22 Jan 95 09:50:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20134;
	Sun, 22 Jan 95 09:50:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVwke-00039DC; Sat, 21 Jan 95 23:30 PST
To: pine-info@cac.washington.edu
From: blane@nyx10.cs.du.edu (Brian Lane)
Subject: Pine: can't open folder lock
Date: 22 Jan 1995 00:17:23 -0700
Message-Id: <3ft0q3$skc@nyx10.cs.du.edu>

  I'm running pine with Linux 1.0.9 -- I've installed it several times in 
the last 6 months or so, and never seen this problem before. All users 
other than root cannot open folder lock, and can't delete messages in 
their inbox.

   I'm stuck....


       Brian

-- 
------------------------------------------------------------------------------
 "Everyone is a prisoner holding their own key." | Enigma BBS (360)569-2911
  http://nyx10.cs.du.edu:8001/~blane/home.html   |   Electronics/uP files
------------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:55:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10251;
	Sun, 22 Jan 95 09:55:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19013;
	Sun, 22 Jan 95 09:51:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19007;
	Sun, 22 Jan 95 09:51:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVxhM-00039PC; Sun, 22 Jan 95 00:31 PST
To: pine-info@cac.washington.edu
From: nets@netcom.com (H. Paul Hammann)
Subject: Pine on Sparc Solaris 2.4?
Message-Id: <netsD27p8B.H9s@netcom.com>
Date: Tue, 10 Jan 1995 23:00:10 GMT

    I am having a difficult time getting Pine compiled for Solaris 2.4
using gcc 2.6.3.  If anyone that has installed Pine on a sparc Solaris
2.4 box has any hints they'd like to pass along I'd be very grateful.
If there is sufficient interest I'll summarize to this newsgroup.
Thanks in advance for any help.

-- 
Regards,

H. Paul Hammann
Partner
Next Edition Translating Services, L.L.C.
nets@netcom.com


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:56:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10286;
	Sun, 22 Jan 95 09:56:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20177;
	Sun, 22 Jan 95 09:51:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20171;
	Sun, 22 Jan 95 09:51:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVxLY-00039NC; Sun, 22 Jan 95 00:08 PST
To: pine-info@cac.washington.edu
From: billy@utdallas.edu (Billy Barron)
Subject: Cyrus IMAP/IMSP vs C-Client
Date: 20 Jan 1995 21:23:46 GMT
Message-Id: <3fp9l2$t2t@news.utdallas.edu>

I'm running an old C-client IMAP server (3.0).  I need IMSP for addressbook
capability in ECSMail.  I've tried to apply the patches to IMAP 3.3 and
3.6BETA for Kerberos, IMSP-API, and IMSP.  To say the least, I had
multiple problems taking that approach.

Then I turned around and looked at Cyrus IMAP/IMSP.  I was disappointed
to find that Cyrus IMAPD can't use C-client IMAP because all I wanted
was the addressbook feature.  I've had bad luck with Cyrus IMAPD compiling
to as follows:

gcc -c -I. -I. -I./../lib -I./../et  -I/usr/local/include -DHAVE_LONG_FILE_NAMES=1 -DHAVE_UNISTD_H=1 -DDIRENT=1 -DSETPROCTITLE=1 -DHAVE_MMAP=1 -g cyradmapp.c
cyradmapp.c: In function `Tcl_AppInit':
cyradmapp.c:45: too few arguments to function `Tcl_Eval'
cyradmapp.c:49: `tcl_RcFileName' undeclared (first use this function)
cyradmapp.c:49: (Each undeclared identifier is reported only once
cyradmapp.c:49: for each function it appears in.)
cyradmapp.c: In function `fatal':
cyradmapp.c:56: `stderr' undeclared (first use this function)

Anyway, I am wondering if anybody has the c-client IMAP and IMSP bundled
together into a single package that can compile on SunOS 4.1.3 or
Solaris 2.  Also, I am wondering what whether I should stay with c-client IMAP
or switch to Cyrus.

Oh well, if this doesn't pan out, it's time to do my X.500 server which I
have to do eventually anyway.

--
Billy Barron,  Network Services Manager, Univ of Texas at Dallas
billy@utdallas.edu 


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:56:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10307;
	Sun, 22 Jan 95 09:56:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18937;
	Sun, 22 Jan 95 09:45:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18931;
	Sun, 22 Jan 95 09:45:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVpdd-00038dC; Sat, 21 Jan 95 15:54 PST
To: pine-info@cac.washington.edu
From: fyao@calum.csclub.uwaterloo.ca (Frank Yao)
Subject: Re: getting elm mail aliases/addresses into PINE addressbook
Message-Id: <D2s11C.2ED@undergrad.math.uwaterloo.ca>
References: <3fonls$fpg@news.doit.wisc.edu>
Date: Sat, 21 Jan 1995 22:27:12 GMT

Sandra Wald <swald@cde2s.ssc.wisc.edu> wrote:

>Does anyone have a program/procedure for putting Elm's mail aliases
>(addresses) into the PINE address book?

cat aliases.text | sed 's/=/ /g' > ~swald/.addressbook

I'm not quite sure about the syntax there, but it basically changes
the ='s in the elm address book to the space (or tabs) required by
pine.

- frank
-- 
---
"You _are_ my darling.  My dear, darling Frank, who cares too much,   
 worries too much, and loves those whom he loves fiercely...."         
 - Victoria Smith about me (fyao@calum.csclub.uwaterloo.ca)                


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:58:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10421;
	Sun, 22 Jan 95 09:58:17 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20217;
	Sun, 22 Jan 95 09:54:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20211;
	Sun, 22 Jan 95 09:54:22 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rW1vl-0003AAC; Sun, 22 Jan 95 05:02 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: pine? lost ^c command
Date: 11 Jan 1995 01:22:05 GMT
Message-Id: <3evbrt$kah@cronkite.ocis.temple.edu>

Comes here Mr. Mike Deem with this opinion in the "comp.mail.pine" group in this
article on Tue, 10 Jan 1995 03:30:49 GMT:

 +   Can't control my cancel or arrow commands . Does anyone know What could 
 +   be the problem.

If ^C doesn't work, try using this key combination:
esc esc c (twice hit the escape key and then hit the c key)

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:58:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10447;
	Sun, 22 Jan 95 09:58:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20203;
	Sun, 22 Jan 95 09:54:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20197;
	Sun, 22 Jan 95 09:54:02 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVzz6-0003A3C; Sun, 22 Jan 95 02:57 PST
To: pine-info@cac.washington.edu
From: a2816ai@sunmail.lrz-muenchen.de (Stephan De Spiegeleire)
Subject: Xtboa decoder
Date: 22 Jan 1995 10:51:31 GMT
Message-Id: <3ftdbj$rja@sunserver.lrz-muenchen.de>

Can somebody tell me where to find a DOS or Windows decoder for messages 
that were encoded with xtboa?

-Stephan
-- 
----------------------------------------------------------------------
Stephan De Spiegeleire
Stiftung Wissenschaft und Politik (SWP)          Tel. (49) 8178/70-360
Research Institute for International Affairs     Fax  (49) 8178/70-312
D-82067 Ebenhausen/Isar, Federal Republic of Germany
----------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:58:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10461;
	Sun, 22 Jan 95 09:58:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19055;
	Sun, 22 Jan 95 09:54:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19049;
	Sun, 22 Jan 95 09:54:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rW0hP-0003A9C; Sun, 22 Jan 95 03:43 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Adding to addressbook answered (and a ?? of my own)
Date: 11 Jan 1995 01:10:58 GMT
Message-Id: <3evb72$kah@cronkite.ocis.temple.edu>

Comes here Mr. Frank Yao with this opinion in the "comp.mail.pine" group in this
article on Tue, 10 Jan 1995 09:55:54 GMT:

 +   In article <Pine.SUN.3.91.950106165903.6579A-100000@antares>,
 +   Keith M. Rainey <kmr@engr.latech.edu> wrote:

 +   >	I use a lot of lists in my addressbook and I am constantly
 +   >changing lists, and adding new lists.  Is there a way to append a
 +   >text file of addresses into the .addressbook file?  It would make 
 +   >my life a little easier (since I'm so lazy).  Also, is there a
 +   >way to send address lists to other users without them having to 
 +   >type in all of the names?

 +   I would think doing something like:  cat text.file >> .addressbook 

See I'm not sure that's gonna work as .addressbook is kinda uniquely formatted.
I haven't tried this but if you have a file which is tab separated in this way

first column: nickname
second column: Full Name
third column: complete e-mail address

and each column separated by a tab and then if you cat that file to .addressbook
it might work. Before you try this make sure you make a backup copy of your
.addressbook and .addressbook.lu files.

In Pine 3.91 which was what you are using, you can import a list of addressess
into a new/existing addressbook list. Great Job, kudos to Pine Team!!

And to your second question just send your .addressbook file to whoever you
want it to be sent. Ofcourse I wouldn't include personal address nicknames in
that case.

 +   In the index screen, we get a flag (N,D,A etc), the sender, the size
 +   and the subject.  What exactly is that size indicating, and is there a
 +   way to change it to reflect the number of LINES in the mail message?

The SIZE of each indivual mail in bytes. Number of lines?
If you find out..post it.

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:58:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10472;
	Sun, 22 Jan 95 09:58:26 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19039;
	Sun, 22 Jan 95 09:53:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19033;
	Sun, 22 Jan 95 09:53:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rVziJ-0003A0C; Sun, 22 Jan 95 02:40 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Home directory
Date: 11 Jan 1995 00:43:06 GMT
Message-Id: <3ev9iq$kah@cronkite.ocis.temple.edu>

Comes here Mr. Ray McAllister with this opinion in the "comp.mail.pine" group in
this article on Tue, 10 Jan 1995 02:24:02 -0500 (EST):

 +   	Question 1, Please help! How can I access or see what is in my "Home 
 +   Directory"? I cannot seem to find it anywhere on either hard drive, to see
 +   what is in it; to use it, or to delete it. Thanks a million.

/u3/mcallist

That is your "home directory"/"Home Directory"
Here's where you will see all the files that belongs to your account.
/u3/mcallist/mail will be the dir. where you will see all your mail folders.

 +   	Question 2, Where or how can I get a manual for Pine?

ftp://ftp.cac.washington.edu/pine/docs

 +   	Question 3, When I go into rz to bring a pre-existing file into 
 +   my home directory I sometimes end up with the Procom 2 screen telling me 
 +   Port in use, yet I have hung up. How can I get rid of Port in use and 
 +   continue with Procom and pine without closing everything back to C:?

set port port##

Aah! here you seem to know about home directory.
BTW this modem question really doesn't belong to comp.mail.pine or does it?

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:58:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10516;
	Sun, 22 Jan 95 09:58:33 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20231;
	Sun, 22 Jan 95 09:54:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20225;
	Sun, 22 Jan 95 09:54:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rW2A4-0003AEC; Sun, 22 Jan 95 05:16 PST
To: pine-info@cac.washington.edu
From: iveysoto@vesta.unm.edu (Daniel A Ivey-Soto)
Subject: Re: blind carbon copies
Date: 11 Jan 1995 01:23:02 GMT
Message-Id: <3evbtm$f4e@lynx.unm.edu>
References: <3eutog$9sb@vixen.cso.uiuc.edu>

	In order to use the BCC feature, first type ^R while the curser is
in the header of the document you wish tosend.  This invokes the "Rich
Header"  feature.  Then, in the line titled BCC, just place all the names
as you normally would in the TO: line. 

	Whenever I do this I usually place a descriptive name in the TO: 
line, just for effect.  To do this, remember to use quotes if it is more 
than one word.  PINE then adds your domain name at the end.  When you 
send the message your original one will come back to you as 
undeliverable, since it was a dummy, though descriptive address.

					Hope this helps,


					Daniel.


The Group (group@uiuc.edu) wrote:
: I'm trying to use Pine to send out announcements 
: to a long list of people, but I don't want the addresses
: to show up in everyone's mailbox.  Does anyone know how 
: send blind carbon copies using Pine?

: Thanks,
: Peter
: Peter Miller
: U. of Illinois Physics Dept.
: peterm@uiuc.edu


--

                                       Take care,


                                       Daniel.


From owner-pine-info@cac.washington.edu  Sun Jan 22 09:58:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10524;
	Sun, 22 Jan 95 09:58:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19075;
	Sun, 22 Jan 95 09:54:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19069;
	Sun, 22 Jan 95 09:54:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rW4W5-0003AHC; Sun, 22 Jan 95 07:47 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: Pine Pipe to Zmodem
Date: 7 Jan 1995 11:19:44 -0500
Message-Id: <3emev0$o7a@wabash.iac.net>
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu> <3eeni5$t36@wabash.iac.net> <ellis.789325031@gmi.edu>  <Pine.NXT.3.91.950106012216.22917A-100000@lipschitz>

J. Kelly Cunningham (deviate@lipschitz) wrote:
: -----BEGIN PGP SIGNED MESSAGE-----

: On 5 Jan 1995, R. Stewart Ellis wrote:

:    cjolley@iac.net (Carl Jolley) writes:
:    
:     >Chris Alfeld (calfeld@ceslab03) wrote:
:     >: Carl Jolley (cjolley@iac.net) wrote:
:     >: : I'm doing terminal emulation to my ISP. The default mailer is Pine. The
:     >: : pipe command IS configured but I can't get piping to: sz - to work. When
:     >: : I try it, the screen does display the zmodem init string, i.e *B00000....
: [...]   
:     >: 	| (cat > tmpfile;sz tmpfile;rm -f tmpfile)
:    
: This isn't really what you want, but how 'bout this?
[rest deleted, but saved for later study]
 
You are correct, I could always just export the message I am interested in
and later download them after I quit Pine. I sounds like there is no way
to interactively download a Pine message ala Elm's pipe. The behavior of
Pine's pipe, i.e. pipe to a command and capture the output back into
a viewer, does not seem to be documented in either the man pages or in
Pine's help screens. I thought that something was broken, but now I
understand that the operation of Pine's pipe is a "feature". It would be
nice if in addition to the current operation of Pine's pipe there was an
option to do a pipe without capturing the command's stdout.
-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Sun Jan 22 10:00:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10601;
	Sun, 22 Jan 95 10:00:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19063;
	Sun, 22 Jan 95 09:54:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19057;
	Sun, 22 Jan 95 09:54:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rW1wg-0003ACC; Sun, 22 Jan 95 05:03 PST
To: pine-info@cac.washington.edu
From: shrim@astro.ocis.temple.edu (Wet-Sprocket)
Subject: Re: blind carbon copies
Date: 11 Jan 1995 01:29:26 GMT
Message-Id: <3evc9m$kah@cronkite.ocis.temple.edu>

Comes here Mr/Mz. The Group with this opinion in the "comp.mail.pine" group in
this article on 10 Jan 1995 21:21:20 GMT:

 +   I'm trying to use Pine to send out announcements 
 +   to a long list of people, but I don't want the addresses
 +   to show up in everyone's mailbox.  Does anyone know how 
 +   send blind carbon copies using Pine?

Place your cursor at the To: header region and hit Control-R for Rich-Headers.
You will see a Bcc: header, just fill in here the entire list but be told that
there's a limit to how many addressess you can have per header (think itz < 50)

--
      o o o o o o o . . .   _~~~__~~~~~~~~~~~~~~~~\_ _~~~~~~~~~~~~~~~\_
    o      _____            |  /__                 | | Compt. Svcs.  |
  .][__n_n_|DD[  ====_____  |  __/ riram NCV       | | Temple Univ.  |
 >(________|__|_[_________]_|______________________|_|_______________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o         o^o`
========================================================================
Talk about me doing the talking for others, esp. My Employers!!
Mac*CHAT List Moderator.


From owner-pine-info@cac.washington.edu  Sun Jan 22 11:05:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12024;
	Sun, 22 Jan 95 11:05:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21091;
	Sun, 22 Jan 95 11:02:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from THOR.INNOSOFT.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21085;
	Sun, 22 Jan 95 11:02:49 -0800
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.3-13 #2001)
 id <01HM581BWCEO8ZEVC6@INNOSOFT.COM>; Sun, 22 Jan 1995 11:02:45 -0800 (PST)
Date: Sun, 22 Jan 1995 11:02:44 -0800 (PST)
From: Portia Shao <PORTIA@INNOSOFT.COM>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu>
To: Steve Lowe <slowe@admin.aurora.edu>
Cc: Pine Information List <pine-info@cac.washington.edu>
Message-Id: <Pine.3.89.9501221046.A543209766-0100000@INNOSOFT.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

On Sat, 21 Jan 1995, Steve Lowe wrote:

> 
> As soon as I read Ed Gresshko's latest message on handling return 
> receipts within PINE, I wanted to try it.  Below is the message that I 
> received (as a receipt).  The sender is the mailer-daemon, not the 
> purpose who reads the message.
> 
> What I was hoping for was that the receipt would appear to have come from 
> the message reader, not the mailer-daemon.

this is not always possible, because you can only get such a thing if the 
recipient's user agent supports read receipts.

Read receipt is a user agent issue, not an MTA (mail transfer agent) issue.
The MTA was nice enough to turn the read receipt into a delivery receipt, 
which is what you get in this case. The MTA does this probably because it 
knows the user agents there does not support read receipt, its other 
alternative is to simply pass it on and you would get nothing if the user 
agent does not support it.

 > 
> Any suggestions?  This is a big (but not major) issue for some of my PINE 
> users.
> 
> TIA.
> 
>  - Steve Lowe
>    Aurora University                  slowe@admin.aurora.edu
> 
> ---------- Forwarded message ----------
> Date: Sat, 21 Jan 1995 10:27:40 -0600
> From: Mail Delivery Subsystem <MAILER-DAEMON@admin.aurora.edu>
> To: slowe@admin.aurora.edu
> Subject: Returned mail: Return receipt
> 
>    ----- Transcript of session follows -----
> 
>   ----- Message header follows -----
> Date: Sat, 21 Jan 1995 10:27:40 -0600 (CST)
> From: Steve Lowe <slowe>
> To: Datatel Login <datatel>
> Subject: Test of Receipt
> Message-Id: <Pine.ULT.3.91.950121102715.3947A-100000@admin.aurora.edu>
> Return-Receipt-To: slowe
> Mime-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> 


	/portia		portia@innosoft.com
	Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax
	1050 East Garvey Ave South, West Covina, CA 91790



From owner-pine-info@cac.washington.edu  Sun Jan 22 11:17:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12295;
	Sun, 22 Jan 95 11:17:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20084;
	Sun, 22 Jan 95 11:15:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from arthur.cs.purdue.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20078;
	Sun, 22 Jan 95 11:15:42 -0800
Received: from lab19.cs.purdue.edu (root@lab19.cs.purdue.edu [128.10.11.119])
    by arthur.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with ESMTP
    id <OAA22798>; Sun, 22 Jan 1995 14:15:40 -0500
Received: from lab19.cs.purdue.edu (simmonmt@lab19.cs.purdue.edu [128.10.11.119])
    by lab19.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with SMTP
    id <OAA22151>; Sun, 22 Jan 1995 14:15:38 -0500
Date: Sun, 22 Jan 1995 14:15:37 -0500 (EST)
From: Matt Simmons <simmonmt@cs.purdue.edu>
To: Portia Shao <PORTIA@INNOSOFT.COM>
Cc: Steve Lowe <slowe@admin.aurora.edu>,
        Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.3.89.9501221046.A543209766-0100000@INNOSOFT.COM>
Message-Id: <Pine.SUN.3.91.950122141406.22083C-100000@lab19.cs.purdue.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 22 Jan 1995, Portia Shao wrote:
> On Sat, 21 Jan 1995, Steve Lowe wrote:
> this is not always possible, because you can only get such a thing if the 
> recipient's user agent supports read receipts.
How hard would it be to just have Pine start supporting read receipts?  Once
a major MUA like Pine starts supporting it, other MUAs are bound to jump on
the band-wagon.


From owner-pine-info@cac.washington.edu  Sun Jan 22 12:06:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13262;
	Sun, 22 Jan 95 12:06:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20539;
	Sun, 22 Jan 95 11:56:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20533;
	Sun, 22 Jan 95 11:56:04 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01796;
	Sun, 22 Jan 95 11:55:52 -0800
Date: Sun, 22 Jan 1995 11:55:52 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Matt Simmons <simmonmt@cs.purdue.edu>
Cc: Portia Shao <PORTIA@INNOSOFT.COM>, Steve Lowe <slowe@admin.aurora.edu>,
        Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.SUN.3.91.950122141406.22083C-100000@lab19.cs.purdue.edu>
Message-Id: <Pine.ULT.3.92.950122115323.21432V-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Matt,
Many, *many* people consider read-receipts to be an invasion of privacy and 
would refuse to use any tool that "offered" such a facility.  I would not 
look for this feature in Pine anytime soon...

*Delivery* receipts are a different story.

Best bet is to include in your message the words: PLEASE ACKNOWLEDGE RECEIPT.

-teg

On Sun, 22 Jan 1995, Matt Simmons wrote:

> On Sun, 22 Jan 1995, Portia Shao wrote:
> > On Sat, 21 Jan 1995, Steve Lowe wrote:
> > this is not always possible, because you can only get such a thing if the 
> > recipient's user agent supports read receipts.

> How hard would it be to just have Pine start supporting read receipts?  Once
> a major MUA like Pine starts supporting it, other MUAs are bound to jump on
> the band-wagon.
> 



From owner-pine-info@cac.washington.edu  Sun Jan 22 12:06:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13291;
	Sun, 22 Jan 95 12:06:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20623;
	Sun, 22 Jan 95 12:02:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from arthur.cs.purdue.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20617;
	Sun, 22 Jan 95 12:02:34 -0800
Received: from lab19.cs.purdue.edu (root@lab19.cs.purdue.edu [128.10.11.119])
    by arthur.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with ESMTP
    id <PAA24871>; Sun, 22 Jan 1995 15:02:33 -0500
Received: from lab19.cs.purdue.edu (simmonmt@lab19.cs.purdue.edu [128.10.11.119])
    by lab19.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with SMTP
    id <PAA22340>; Sun, 22 Jan 1995 15:02:31 -0500
Date: Sun, 22 Jan 1995 15:02:29 -0500 (EST)
From: Matt Simmons <simmonmt@cs.purdue.edu>
To: Terry Gray <gray@cac.washington.edu>
Cc: Portia Shao <PORTIA@INNOSOFT.COM>, Steve Lowe <slowe@admin.aurora.edu>,
        Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.ULT.3.92.950122115323.21432V-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950122145639.22083E-100000@lab19.cs.purdue.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 22 Jan 1995, Terry Gray wrote:
> Many, *many* people consider read-receipts to be an invasion of privacy and 
> would refuse to use any tool that "offered" such a facility.  I would not 
> look for this feature in Pine anytime soon...
So just have an option (settable from the setup menu) that turns receipts
on.  (ie have it default to off)  This is a feature available on cc:Mail,
and was used extensively where I last worked -- it can be a great help


From owner-pine-info@cac.washington.edu  Sun Jan 22 12:12:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13473;
	Sun, 22 Jan 95 12:12:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21869;
	Sun, 22 Jan 95 12:10:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from admin.aurora.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21863;
	Sun, 22 Jan 95 12:10:18 -0800
Received: by admin.aurora.edu (5.65/DEC-Ultrix/4.3)
	id AA28556; Sun, 22 Jan 1995 14:10:43 -0600
Date: Sun, 22 Jan 1995 14:10:42 -0600 (CST)
From: Steve Lowe <slowe@admin.aurora.edu>
To: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE (fwd)
Message-Id: <Pine.ULT.3.91.950122140551.28499A-100000@admin.aurora.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Terry --

The VMS mail package that we replaced with PINE offered the user the 
option of sending mail messages registered.  If I wanted to send a 
specific mail message registered, I could do that.

I prompted this discussion with how could I send mail messages 
registered.  Is there a simple way to do this within PINE 3.91?

 - Steve Lowe
   Aurora University


---------- Forwarded message ----------
Date: Sun, 22 Jan 1995 15:02:29 -0500 (EST)
From: Matt Simmons <simmonmt@cs.purdue.edu>
To: Terry Gray <gray@cac.washington.edu>
Cc: Portia Shao <PORTIA@INNOSOFT.COM>, Steve Lowe <slowe@admin.aurora.edu>,
    Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE

On Sun, 22 Jan 1995, Terry Gray wrote:
> Many, *many* people consider read-receipts to be an invasion of privacy and 
> would refuse to use any tool that "offered" such a facility.  I would not 
> look for this feature in Pine anytime soon...
So just have an option (settable from the setup menu) that turns receipts
on.  (ie have it default to off)  This is a feature available on cc:Mail,
and was used extensively where I last worked -- it can be a great help



From owner-pine-info@cac.washington.edu  Sun Jan 22 12:15:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13644;
	Sun, 22 Jan 95 12:15:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21922;
	Sun, 22 Jan 95 12:13:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21916;
	Sun, 22 Jan 95 12:13:06 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01983;
	Sun, 22 Jan 95 12:12:56 -0800
Date: Sun, 22 Jan 1995 12:12:55 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Matt Simmons <simmonmt@cs.purdue.edu>
Cc: Portia Shao <PORTIA@INNOSOFT.COM>, Steve Lowe <slowe@admin.aurora.edu>,
        Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.SUN.3.91.950122145639.22083E-100000@lab19.cs.purdue.edu>
Message-Id: <Pine.ULT.3.92.950122121002.21432W-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 22 Jan 1995, Matt Simmons wrote:

> > Many, *many* people consider read-receipts to be an invasion of privacy and 
> > would refuse to use any tool that "offered" such a facility.  I would not 
> > look for this feature in Pine anytime soon...
>
> So just have an option (settable from the setup menu) that turns receipts
> on.  (ie have it default to off)  This is a feature available on cc:Mail,
> and was used extensively where I last worked -- it can be a great help

If and when an Internet standard emerges for Read receipt requests and
responses, we would certainly consider such an option... and you can
definitely bank on the fact that the default would be OFF! 

-teg


From owner-pine-info@cac.washington.edu  Sun Jan 22 12:18:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13729;
	Sun, 22 Jan 95 12:18:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20810;
	Sun, 22 Jan 95 12:15:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from arthur.cs.purdue.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20804;
	Sun, 22 Jan 95 12:15:41 -0800
Received: from lab19.cs.purdue.edu (root@lab19.cs.purdue.edu [128.10.11.119])
    by arthur.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with ESMTP
    id <PAA25369>; Sun, 22 Jan 1995 15:15:39 -0500
Received: from lab19.cs.purdue.edu (simmonmt@lab19.cs.purdue.edu [128.10.11.119])
    by lab19.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with SMTP
    id <PAA22396>; Sun, 22 Jan 1995 15:15:38 -0500
Date: Sun, 22 Jan 1995 15:15:36 -0500 (EST)
From: Matt Simmons <simmonmt@cs.purdue.edu>
To: Terry Gray <gray@cac.washington.edu>
Cc: Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.ULT.3.92.950122121002.21432W-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950122151411.22083G-100000@lab19.cs.purdue.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 22 Jan 1995, Terry Gray wrote:
> If and when an Internet standard emerges for Read receipt requests and
> responses, we would certainly consider such an option... and you can
> definitely bank on the fact that the default would be OFF! 

Which leaves us with the chicken and the egg problem -- the standard won't
be created until programs support it, and programs won't support it until
there's a standard. That's why I suggested what I did in my first post --
that Pine take the lead, create a standard, and let the world follow.


From owner-pine-info@cac.washington.edu  Sun Jan 22 18:38:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22717;
	Sun, 22 Jan 95 18:38:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26986;
	Sun, 22 Jan 95 18:32:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26980;
	Sun, 22 Jan 95 18:32:13 -0800
Received: by hobbes.twntpe.cdc.com; Mon, 23 Jan 95 10:30:39 -0800
Date: Mon, 23 Jan 1995 10:30:38 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Matt Simmons <simmonmt@cs.purdue.edu>
Cc: Terry Gray <gray@cac.washington.edu>,
        Pine Information List <pine-info@cac.washington.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: <Pine.SUN.3.91.950122151411.22083G-100000@lab19.cs.purdue.edu>
Message-Id: <Pine.SOL.3.91.950123102912.5751B-300000@hobbes>
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-790885838=:5751"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-851401618-790885838=:5751
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 22 Jan 1995, Matt Simmons wrote:

> On Sun, 22 Jan 1995, Terry Gray wrote:
> > If and when an Internet standard emerges for Read receipt requests and
> > responses, we would certainly consider such an option... and you can
> > definitely bank on the fact that the default would be OFF! 
> 
> Which leaves us with the chicken and the egg problem -- the standard won't
> be created until programs support it, and programs won't support it until
> there's a standard. That's why I suggested what I did in my first post --
> that Pine take the lead, create a standard, and let the world follow.
> 

	I don't believe you have a c&e problem.  

	Please obtain and read the current IETF drafts referenced in the
attached files.

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C

---559023410-851401618-790885838=:5751
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=notice
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SOL.3.91.950123103038.5751C@hobbes>
Content-Description: 

RnJvbSBJbnRlcm5ldC1EcmFmdHNAQ05SSS5SZXN0b24uVkEuVVNNb24gSmFu
IDIzIDEwOjI4OjE5IDE5OTUNCkRhdGU6IFRodSwgMTkgSmFuIDk1IDE0OjM5
OjE3IC0wNTAwDQpGcm9tOiBJbnRlcm5ldC1EcmFmdHNAQ05SSS5SZXN0b24u
VkEuVVMNClRvOiBJRVRGLUFubm91bmNlOiAgOw0KQ2M6IG5vdGlmaWNhdGlv
bnNAQ1MuVVRLLkVEVQ0KU3ViamVjdDogSS1EIEFDVElPTjpkcmFmdC1pZXRm
LW5vdGFyeS1taW1lLXJlcG9ydC0wMS50eHQNCg0KQSBSZXZpc2VkIEludGVy
bmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVy
bmV0LURyYWZ0cyANCmRpcmVjdG9yaWVzLiBUaGlzIGRyYWZ0IGlzIGEgd29y
ayBpdGVtIG9mIHRoZSBOb3RpZmljYXRpb25zIGFuZCANCkFja25vd2xlZGdl
bWVudHMgUmVxdWlyZW1lbnRzIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYu
ICAgICAgICAgICAgICAgICAgIA0KDQogICAgICAgVGl0bGUgICAgIDogVGhl
IE11bHRpcGFydC9SZXBvcnQgQ29udGVudCBUeXBlIA0KICAgICAgICAgICAg
ICAgICAgICAgICAgIGZvciB0aGUgUmVwb3J0aW5nIG9mIA0KICAgICAgICAg
ICAgICAgICAgIE1haWwgU3lzdGVtIEFkbWluaXN0cmF0aXZlIE1lc3NhZ2Vz
ICAgICAgICAgICAgICAgICAgICAgDQogICAgICAgQXV0aG9yKHMpIDogRy4g
VmF1ZHJldWlsDQogICAgICAgRmlsZW5hbWUgIDogZHJhZnQtaWV0Zi1ub3Rh
cnktbWltZS1yZXBvcnQtMDEudHh0DQogICAgICAgUGFnZXMgICAgIDogNA0K
ICAgICAgIERhdGUgICAgICA6IDAxLzE4LzE5OTUNCg0KVGhpcyBtZW1vIGRl
ZmluZXMgYSBnZW5lcmljIHBhY2thZ2luZyBtZWNoYW5pc20gZm9yIG1haWwg
c3lzdGVtIHJlcG9ydHMuICAgDQoNCkludGVybmV0LURyYWZ0cyBhcmUgYXZh
aWxhYmxlIGJ5IGFub255bW91cyBGVFAuICBMb2dpbiB3aXRoIHRoZSB1c2Vy
bmFtZQ0KImFub255bW91cyIgYW5kIGEgcGFzc3dvcmQgb2YgeW91ciBlLW1h
aWwgYWRkcmVzcy4gIEFmdGVyIGxvZ2dpbmcgaW4sDQp0eXBlICJjZCBpbnRl
cm5ldC1kcmFmdHMiIGFuZCB0aGVuDQogICAgICJnZXQgZHJhZnQtaWV0Zi1u
b3RhcnktbWltZS1yZXBvcnQtMDEudHh0Ii4NCkEgVVJMIGZvciB0aGUgSW50
ZXJuZXQtRHJhZnQgaXM6DQpmdHA6Ly9kcy5pbnRlcm5pYy5uZXQvaW50ZXJu
ZXQtZHJhZnRzL2RyYWZ0LWlldGYtbm90YXJ5LW1pbWUtcmVwb3J0LTAxLnR4
dA0KIA0KSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzIGFyZSBsb2NhdGVk
IGF0OgkNCgkgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICANCiAgICAgbyAgQWZyaWNhICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICANCiAgICAgICAgQWRkcmVzczogIGZ0cC5pcy5j
by56YSAoMTk2LjQuMTYwLjIpCQ0KCSAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICBvICBFdXJvcGUgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgICBBZGRy
ZXNzOiAgbmljLm5vcmR1Lm5ldCAoMTkyLjM2LjE0OC4xNykJDQoJICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQog
ICAgIG8gIFBhY2lmaWMgUmltICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgDQogICAgICAgIEFkZHJlc3M6ICBtdW5uYXJpLm96LmF1ICgxMjguMjUw
LjEuMjEpCQ0KCSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA0KICAgICBvICBVUyBFYXN0IENvYXN0ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIA0KICAgICAgICBBZGRyZXNzOiAgZHMuaW50
ZXJuaWMubmV0ICgxOTguNDkuNDUuMTApCQ0KCSAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICBvICBVUyBX
ZXN0IENvYXN0ICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAg
ICBBZGRyZXNzOiAgZnRwLmlzaS5lZHUgKDEyOC45LjAuMzIpICAJDQoJICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
DQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IG1haWwu
CQ0KCSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIA0KU2VuZCBhIG1lc3NhZ2UgdG86ICBtYWlsc2VydkBkcy5pbnRl
cm5pYy5uZXQuIEluIHRoZSBib2R5IHR5cGU6IA0KICAgICAiRklMRSAvaW50
ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbm90YXJ5LW1pbWUtcmVwb3J0LTAx
LnR4dCIuDQoJCQkJCQkJDQpOT1RFOiBUaGUgbWFpbCBzZXJ2ZXIgYXQgZHMu
aW50ZXJuaWMubmV0IGNhbiByZXR1cm4gdGhlIGRvY3VtZW50IGluDQogICAg
ICBNSU1FLWVuY29kZWQgZm9ybSBieSB1c2luZyB0aGUgIm1wYWNrIiB1dGls
aXR5LiAgVG8gdXNlIHRoaXMNCiAgICAgIGZlYXR1cmUsIGluc2VydCB0aGUg
Y29tbWFuZCAiRU5DT0RJTkcgbWltZSIgYmVmb3JlIHRoZSAiRklMRSINCiAg
ICAgIGNvbW1hbmQuICBUbyBkZWNvZGUgdGhlIHJlc3BvbnNlKHMpLCB5b3Ug
d2lsbCBuZWVkICJtdW5wYWNrIiBvcg0KICAgICAgYSBNSU1FLWNvbXBsaWFu
dCBtYWlsIHJlYWRlci4gIERpZmZlcmVudCBNSU1FLWNvbXBsaWFudCBtYWls
IHJlYWRlcnMNCiAgICAgIGV4aGliaXQgZGlmZmVyZW50IGJlaGF2aW9yLCBl
c3BlY2lhbGx5IHdoZW4gZGVhbGluZyB3aXRoDQogICAgICAibXVsdGlwYXJ0
IiBNSU1FIG1lc3NhZ2VzIChpLmUuLCBkb2N1bWVudHMgd2hpY2ggaGF2ZSBi
ZWVuIHNwbGl0DQogICAgICB1cCBpbnRvIG11bHRpcGxlIG1lc3NhZ2VzKSwg
c28gY2hlY2sgeW91ciBsb2NhbCBkb2N1bWVudGF0aW9uIG9uDQogICAgICBo
b3cgdG8gbWFuaXB1bGF0ZSB0aGVzZSBtZXNzYWdlcy4NCgkJCQkJCQkNCkZv
ciBxdWVzdGlvbnMsIHBsZWFzZSBtYWlsIHRvIEludGVybmV0LURyYWZ0c0Bj
bnJpLnJlc3Rvbi52YS51cy4NCgkJCQkJCQkNCg0KQmVsb3cgaXMgdGhlIGRh
dGEgd2hpY2ggd2lsbCBlbmFibGUgYSBNSU1FIGNvbXBsaWFudCBtYWlsIHJl
YWRlciANCmltcGxlbWVudGF0aW9uIHRvIGF1dG9tYXRpY2FsbHkgcmV0cmll
dmUgdGhlIEFTQ0lJIHZlcnNpb24NCm9mIHRoZSBJbnRlcm5ldC1EcmFmdC4N
Cg0KICBbUGFydCAyLjEsIE1lc3NhZ2UvRVhURVJOQUwtQk9EWSAgMTU1Ynl0
ZXNdDQogIFtVbmFibGUgdG8gcHJpbnQgdGhpcyBwYXJ0XQ0KDQoNCiAgWyBQ
YXJ0IDIuMjogIkluY2x1ZGVkIE1lc3NhZ2UiIF0NCg0KVGhpcyBwYXJ0IGlz
IG5vdCBpbmNsdWRlZCBhbmQgY2FuIGJlIGZldGNoZWQgYXMgZm9sbG93czoN
Ck5BTUUgICAgICAgOiBkcmFmdC1pZXRmLW5vdGFyeS1taW1lLXJlcG9ydC0w
MS50eHQNClNJVEUgICAgICAgOiBkcy5pbnRlcm5pYy5uZXQNCkFDQ0VTUy1U
WVBFOiBhbm9uLWZ0cA0KRElSRUNUT1JZICA6IGludGVybmV0LWRyYWZ0cw0K
DQo=
---559023410-851401618-790885838=:5751
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=notice2
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.SOL.3.91.950123103038.5751D@hobbes>
Content-Description: 

RnJvbSBJbnRlcm5ldC1EcmFmdHNAQ05SSS5SZXN0b24uVkEuVVNNb24gSmFu
IDIzIDEwOjI4OjQ0IDE5OTUNCkRhdGU6IFRodSwgMTkgSmFuIDk1IDE0OjM5
OjIzIC0wNTAwDQpGcm9tOiBJbnRlcm5ldC1EcmFmdHNAQ05SSS5SZXN0b24u
VkEuVVMNClRvOiBJRVRGLUFubm91bmNlOiAgOw0KQ2M6IG5vdGlmaWNhdGlv
bnNAQ1MuVVRLLkVEVQ0KU3ViamVjdDogSS1EIEFDVElPTjpkcmFmdC1pZXRm
LW5vdGFyeS1zdGF0dXMtMDEudHh0DQoNCkEgUmV2aXNlZCBJbnRlcm5ldC1E
cmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1E
cmFmdHMgDQpkaXJlY3Rvcmllcy4gVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRl
bSBvZiB0aGUgTm90aWZpY2F0aW9ucyBhbmQgDQpBY2tub3dsZWRnZW1lbnRz
IFJlcXVpcmVtZW50cyBXb3JraW5nIEdyb3VwIG9mIHRoZSBJRVRGLiAgICAg
ICAgICAgICAgICAgICANCg0KICAgICAgIFRpdGxlICAgICA6IEVuaGFuY2Vk
IE1haWwgU3lzdGVtIFN0YXR1cyBDb2RlcyAgICAgICAgICAgICAgICAgICAg
ICAgDQogICAgICAgQXV0aG9yKHMpIDogRy4gVmF1ZHJldWlsDQogICAgICAg
RmlsZW5hbWUgIDogZHJhZnQtaWV0Zi1ub3Rhcnktc3RhdHVzLTAxLnR4dA0K
ICAgICAgIFBhZ2VzICAgICA6IDE1DQogICAgICAgRGF0ZSAgICAgIDogMDEv
MTgvMTk5NQ0KDQpUaGVyZSBjdXJyZW50bHkgaXMgbm90IGEgc3RhbmRhcmQg
bWVjaGFuaXNtIGZvciB0aGUgcmVwb3J0aW5nIG9mIG1haWwgDQpzeXN0ZW0g
ZXJyb3JzIGV4Y2VwdCBmb3IgdGhlIGxpbWl0ZWQgc2V0IG9mZmVyZWQgYnkg
U01UUCBhbmQgdGhlIHN5c3RlbSANCnNwZWNpZmljIHRleHQgZGVzY3JpcHRp
b25zIHNlbnQgaW4gbWFpbCBtZXNzYWdlcy4gICAgICAgICAgICAgICAgICAg
ICAgICAgIA0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGF2YWlsYWJsZSBieSBh
bm9ueW1vdXMgRlRQLiAgTG9naW4gd2l0aCB0aGUgdXNlcm5hbWUNCiJhbm9u
eW1vdXMiIGFuZCBhIHBhc3N3b3JkIG9mIHlvdXIgZS1tYWlsIGFkZHJlc3Mu
ICBBZnRlciBsb2dnaW5nIGluLA0KdHlwZSAiY2QgaW50ZXJuZXQtZHJhZnRz
IiBhbmQgdGhlbg0KICAgICAiZ2V0IGRyYWZ0LWlldGYtbm90YXJ5LXN0YXR1
cy0wMS50eHQiLg0KQSBVUkwgZm9yIHRoZSBJbnRlcm5ldC1EcmFmdCBpczoN
CmZ0cDovL2RzLmludGVybmljLm5ldC9pbnRlcm5ldC1kcmFmdHMvZHJhZnQt
aWV0Zi1ub3Rhcnktc3RhdHVzLTAxLnR4dA0KIA0KSW50ZXJuZXQtRHJhZnRz
IGRpcmVjdG9yaWVzIGFyZSBsb2NhdGVkIGF0OgkNCgkgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgbyAg
QWZyaWNhICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAg
ICAgICAgQWRkcmVzczogIGZ0cC5pcy5jby56YSAoMTk2LjQuMTYwLjIpCQ0K
CSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIA0KICAgICBvICBFdXJvcGUgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIA0KICAgICAgICBBZGRyZXNzOiAgbmljLm5vcmR1Lm5ldCAo
MTkyLjM2LjE0OC4xNykJDQoJICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgDQogICAgIG8gIFBhY2lmaWMgUmltICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgDQogICAgICAgIEFkZHJlc3M6
ICBtdW5uYXJpLm96LmF1ICgxMjguMjUwLjEuMjEpCQ0KCSAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICBv
ICBVUyBFYXN0IENvYXN0ICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K
ICAgICAgICBBZGRyZXNzOiAgZHMuaW50ZXJuaWMubmV0ICgxOTguNDkuNDUu
MTApCQ0KCSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIA0KICAgICBvICBVUyBXZXN0IENvYXN0ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIA0KICAgICAgICBBZGRyZXNzOiAgZnRwLmlzaS5l
ZHUgKDEyOC45LjAuMzIpICAJDQoJICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgDQpJbnRlcm5ldC1EcmFmdHMgYXJl
IGFsc28gYXZhaWxhYmxlIGJ5IG1haWwuCQ0KCSAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KU2VuZCBhIG1lc3Nh
Z2UgdG86ICBtYWlsc2VydkBkcy5pbnRlcm5pYy5uZXQuIEluIHRoZSBib2R5
IHR5cGU6IA0KICAgICAiRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWll
dGYtbm90YXJ5LXN0YXR1cy0wMS50eHQiLg0KCQkJCQkJCQ0KTk9URTogVGhl
IG1haWwgc2VydmVyIGF0IGRzLmludGVybmljLm5ldCBjYW4gcmV0dXJuIHRo
ZSBkb2N1bWVudCBpbg0KICAgICAgTUlNRS1lbmNvZGVkIGZvcm0gYnkgdXNp
bmcgdGhlICJtcGFjayIgdXRpbGl0eS4gIFRvIHVzZSB0aGlzDQogICAgICBm
ZWF0dXJlLCBpbnNlcnQgdGhlIGNvbW1hbmQgIkVOQ09ESU5HIG1pbWUiIGJl
Zm9yZSB0aGUgIkZJTEUiDQogICAgICBjb21tYW5kLiAgVG8gZGVjb2RlIHRo
ZSByZXNwb25zZShzKSwgeW91IHdpbGwgbmVlZCAibXVucGFjayIgb3INCiAg
ICAgIGEgTUlNRS1jb21wbGlhbnQgbWFpbCByZWFkZXIuICBEaWZmZXJlbnQg
TUlNRS1jb21wbGlhbnQgbWFpbCByZWFkZXJzDQogICAgICBleGhpYml0IGRp
ZmZlcmVudCBiZWhhdmlvciwgZXNwZWNpYWxseSB3aGVuIGRlYWxpbmcgd2l0
aA0KICAgICAgIm11bHRpcGFydCIgTUlNRSBtZXNzYWdlcyAoaS5lLiwgZG9j
dW1lbnRzIHdoaWNoIGhhdmUgYmVlbiBzcGxpdA0KICAgICAgdXAgaW50byBt
dWx0aXBsZSBtZXNzYWdlcyksIHNvIGNoZWNrIHlvdXIgbG9jYWwgZG9jdW1l
bnRhdGlvbiBvbg0KICAgICAgaG93IHRvIG1hbmlwdWxhdGUgdGhlc2UgbWVz
c2FnZXMuDQoJCQkJCQkJDQpGb3IgcXVlc3Rpb25zLCBwbGVhc2UgbWFpbCB0
byBJbnRlcm5ldC1EcmFmdHNAY25yaS5yZXN0b24udmEudXMuDQoJCQkJCQkJ
DQoNCkJlbG93IGlzIHRoZSBkYXRhIHdoaWNoIHdpbGwgZW5hYmxlIGEgTUlN
RSBjb21wbGlhbnQgbWFpbCByZWFkZXIgDQppbXBsZW1lbnRhdGlvbiB0byBh
dXRvbWF0aWNhbGx5IHJldHJpZXZlIHRoZSBBU0NJSSB2ZXJzaW9uDQpvZiB0
aGUgSW50ZXJuZXQtRHJhZnQuDQoNCiAgW1BhcnQgMi4xLCBNZXNzYWdlL0VY
VEVSTkFMLUJPRFkgIDE1MGJ5dGVzXQ0KICBbVW5hYmxlIHRvIHByaW50IHRo
aXMgcGFydF0NCg0KDQogIFsgUGFydCAyLjI6ICJJbmNsdWRlZCBNZXNzYWdl
IiBdDQoNClRoaXMgcGFydCBpcyBub3QgaW5jbHVkZWQgYW5kIGNhbiBiZSBm
ZXRjaGVkIGFzIGZvbGxvd3M6DQpOQU1FICAgICAgIDogZHJhZnQtaWV0Zi1u
b3Rhcnktc3RhdHVzLTAxLnR4dA0KU0lURSAgICAgICA6IGRzLmludGVybmlj
Lm5ldA0KQUNDRVNTLVRZUEU6IGFub24tZnRwDQpESVJFQ1RPUlkgIDogaW50
ZXJuZXQtZHJhZnRzDQoNCg==
---559023410-851401618-790885838=:5751--


From owner-pine-info@cac.washington.edu  Sun Jan 22 19:27:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23773;
	Sun, 22 Jan 95 19:27:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26588;
	Sun, 22 Jan 95 19:21:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26582;
	Sun, 22 Jan 95 19:21:44 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA09411; Sun, 22 Jan 1995 22:21:17 +0500
Date: Sun, 22 Jan 1995 22:21:17 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: Pine on Sparc Solaris 2.4?
In-Reply-To: <netsD27p8B.H9s@netcom.com>
Message-Id: <Pine.SOL.3.91.950122221247.9334A-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 943

On Tue, 10 Jan 1995, H. Paul Hammann wrote:

>     I am having a difficult time getting Pine compiled for Solaris 2.4
> using gcc 2.6.3.  If anyone that has installed Pine on a sparc Solaris
> 2.4 box has any hints they'd like to pass along I'd be very grateful.
> If there is sufficient interest I'll summarize to this newsgroup.
> Thanks in advance for any help.
 
I had the same problem, so finally gave up and ftp'd the precompiled
binaries pine-bin.solaris, pico-bin.solaris, and imapd-bin.solaris from
ftp.cac.washington.edu.  They work like a charm here, but I was 
simply substituting them for older versions.  Your mileage may vary...

--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA



From owner-pine-info@cac.washington.edu  Sun Jan 22 23:55:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29342;
	Sun, 22 Jan 95 23:55:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01451;
	Sun, 22 Jan 95 23:51:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01445;
	Sun, 22 Jan 95 23:51:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rW97W-0003A6C; Sun, 22 Jan 95 12:42 PST
To: pine-info@cac.washington.edu
From: root@whacked.dorm.lsu.edu (Ben Curtis)
Subject: POP
Date: 7 Jan 1995 05:44:28 GMT
Message-Id: <3el9ns$nn@deathstar.cris.com>

	I tried using the POP capability of 3.91 by specifying my INBOX 
as the POP mailbox, but something is screwy.  Until today (one day of 
use) it worked fine, but when I read my mail today, one message had no 
text, and another message was mangled similarly.  I have no clue as to 
the problem, so any suggestions would be greatly appreciated.

--
   __                __  _      _____          _                      
  / /  ______ ______/ /_(_)___ / ___ \________(_)___    _______  __ _ 
 / _ \/ __/ // / __/ __/ /(_-</ / _ `/ __/ __/ /(_-< _ / __/ _ \/  ' \
/_.__/\__/\_,_/_/  \__/_//___/\ \_,_/\__/_/ /_//___/(_)\__/\___/_/_/_/
                               \___/                                  
Linux Lover ... Talker Coder ... Ultimate Player ... Animaniacs Watcher


From owner-pine-info@cac.washington.edu  Sun Jan 22 23:57:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29394;
	Sun, 22 Jan 95 23:57:28 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00558;
	Sun, 22 Jan 95 23:54:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00552;
	Sun, 22 Jan 95 23:54:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWItU-0003B0C; Sun, 22 Jan 95 23:08 PST
To: pine-info@cac.washington.edu
From: hirshaut@yu1.yu.edu
Subject: Printing Pine Messages
Message-Id: <Pine.A32.3.91.950122220907.29370A-100000@yu1.yu.edu>
Date: 23 Jan 95 03:16:04 GMT
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am using a Lynx 125 terminal (in the VT100 emulation mode) to connect 
to an AIX version of pine.  I have a NEC Pinwriter P5XL printer attached 
to the terminal via a parallel port.  While using a similar setup permits 
me to print successfully from a CD-ROM based Medline system at our 
hospital's library, it does not seem to respond properly either to the 
PC or lprint mode of printing from pine.  Without buying a home computer 
and a communication package, is there any way of printing directly in 
this terminal-parallel printer configuration from pine?

Your reply is much appreciated.  










From owner-pine-info@cac.washington.edu  Mon Jan 23 01:54:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02340;
	Mon, 23 Jan 95 01:54:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02104;
	Mon, 23 Jan 95 01:49:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02098;
	Mon, 23 Jan 95 01:49:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWL6A-00038TC; Mon, 23 Jan 95 01:30 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Pine for OS/2 (!)
Date: Mon, 23 Jan 1995 09:24:43 +0000
Message-Id: <Pine.SUN.3.91.950123092405.26876D-100000@grus.cus.cam.ac.uk>
References: <5f8_9501200953@dialis.xs4all.nl> <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org> 

On 20 Jan 1995, Brent Blumenstein wrote:

> Now that is good news.  When?  And are beta testers needed.  I volunteer.

I volunteer also.

> On 19 Jan 1995, Geert Bosch wrote:
> 
> > For those interested, I read that Steve Willer is currently porting the Pine
> > reader to OS/2. At least there are some developments now...
> > 

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Mon Jan 23 01:58:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02409;
	Mon, 23 Jan 95 01:58:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02993;
	Mon, 23 Jan 95 01:49:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02987;
	Mon, 23 Jan 95 01:49:22 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWL5S-00038RC; Mon, 23 Jan 95 01:29 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Changing From: header
Date: Mon, 23 Jan 1995 09:22:15 +0000
Message-Id: <Pine.SUN.3.91.950123092105.26876C-100000@grus.cus.cam.ac.uk>
References: <Pine.OSF.3.91.950120111207.28526C-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.OSF.3.91.950120111207.28526C-100000@osfb.aber.ac.uk> 

On Fri, 20 Jan 1995, Brad wrote:

> 	Yep indeedy! You have to uncomment the following line in
> pine/osdep/os-xxx.h: 
> 
> /* #define ALLOW_CHANGING_FROM  /* comment out to not allow changing From */
> 
> Then you should be able to change your From address. However, I've never
> tried doing it via the Customized-hdrs... 
> 

Some of our customers have done this and it works fine.

> 
> On 18 Jan 1995, Nancy McGough wrote:
> 
> > I'd like to change the From: header in mail I send from Pine
> > by putting something like this in my .pinerc:
> > 
> > customized-hdrs=Organization: $ORGANIZATION,
> >         From: Nancy McGough <nancym@ii.com>
> > 

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Mon Jan 23 02:42:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03289;
	Mon, 23 Jan 95 02:42:32 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03467;
	Mon, 23 Jan 95 02:30:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03461;
	Mon, 23 Jan 95 02:30:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWLit-00038RC; Mon, 23 Jan 95 02:10 PST
To: pine-info@cac.washington.edu
From: Rahul Dhesi <dhesi@rahul.net>
Subject: Re: Handling Return Receipts within PINE
Date: 23 Jan 1995 10:10:04 GMT
Message-Id: <3fvv9s$ivj@hustle.rahul.net>
References: <Pine.3.89.9501221046.A543209766-0100000@INNOSOFT.COM> <Pine.SUN.3.91.950122141406.22083C-100000@lab19.cs.purdue.edu>

In <Pine.SUN.3.91.950122141406.22083C-100000@lab19.cs.purdue.edu>
simmonmt@cs.purdue.edu (Matt Simmons) writes:

>How hard would it be to just have Pine start supporting read receipts?

It would cause a serious invasion of privacy, so it would ideally
be a user-settable option.
-- 
Rahul Dhesi <dhesi@rahul.net>


From owner-pine-info@cac.washington.edu  Mon Jan 23 04:29:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06158;
	Mon, 23 Jan 95 04:29:19 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03952;
	Mon, 23 Jan 95 04:12:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03946;
	Mon, 23 Jan 95 04:12:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWNHG-00038KC; Mon, 23 Jan 95 03:49 PST
To: pine-info@cac.washington.edu
From: sysop@mome-raths.iac.net (March Hare)
Subject: Re: Pine for OS/2 (!)
Message-Id: <2f22a733.4d4f4d45@mome-raths.iac.net>
Date: Sun, 22 Jan 1995 13:42:59 -0500
References: <5f8_9501200953@dialis.xs4all.nl> <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org>

Brent Blumenstein (brentb@orca.fhcrc.org) wrote:
: Now that is good news.  When?  And are beta testers needed.  I volunteer.


: > For those interested, I read that Steve Willer is currently porting the Pine
: > reader to OS/2. At least there are some developments now...
: > 

Hi, I just got onto this list.  I'm told there is a general belief
that there's no interest in a Pine port for OS/2.  I'm here to
state that it's more likely that few OS/2 users know about this
newsgroup/mailing-list.

BTW - I picked up on the OS/2 groups that a port of pico is 
available ftp, which I'm using right now to write this message.
It works pretty well.  I'm planning on using it for accessing
UUCP news through my BBS.  Now, I just have to work out extracting
the user name, which shouldn't be too difficult.  Pico will be
ideal for this, since I don't have to worry about [Esc] or
function keys or any of that other junk that DOS & OS/2 programs
seem to rely on.

I also noticed in the docs that Pine was written with NNTP
in mind (please correct me if I read wrong).  Will it work
with UUCP (esp. UUPC from Clarkson)?

John

--
Mome Raths BBS                          General Pix, Adult Pix, Messages,
(513)523-7887                           DOS, Windows and OS/2 programs,
Oxford, Ohio                            12 Step echos and much more


From owner-pine-info@cac.washington.edu  Mon Jan 23 04:30:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06196;
	Mon, 23 Jan 95 04:30:32 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04998;
	Mon, 23 Jan 95 04:22:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from scorpio.gold.ac.uk by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04986;
	Mon, 23 Jan 95 04:22:45 -0800
Received: from pc438.gold.ac.uk by gold.ac.uk; Mon, 23 Jan 95 12:21:38 GMT
Date: Mon, 23 Jan 1995 12:21:37 -0800 (PST)
From: Guy Boanas <guy@gold.ac.uk>
To: "J. Scott Williams" <scott@henson.cc.wwu.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: PC Pine and NFS?
X-Sender: guy@scorpio.gold.ac.uk
In-Reply-To: <1995Jan21.211826.20141@henson.cc.wwu.edu>
Message-Id: <Pine.PCW.3.91.950123121144.8623A-100000@pc438.gold.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

We use Winsock Pine at our College. At the moment it's only available for use
by staff although we hope to introduce it onto the Student Open Access PCs
next academic year (there students telnet to the UNIX server and use UNIX
pine). Using PC-NFS or B&W NFS Connect we have a system that dynamically
mounts remote NFS drives (including a user's own server area) according to
username/password validation. This way staff can run Winsock Pine from 
any PC so configured. The binaries (pine.exe etc) are located on the 
local HD but the pinerc and other bits are in the user's remote  N:\PINE.

Getting WinPine to use UNIX versions of news and address --.newsrc and 
.addressbook -- is possible if you use the cookied version of the 
filename in the WinPine pinerc. file. Not a great solution and has its 
dangers but ...

I've done a document (Word 6 format) for users taking them through the 
process of setting a copy of the program up. Mail me if you'd like it 
e-mailed to you.

Guy Boanas
guy@gold.ac.uk

> We currently are successfully using Pine 
on our Unix platforms.  
We > want to develop an additional method of reading email using PC-Pine
> from within MS Windows using IMAP and NFS.  The PC Pine method will be
> primarily for use in student labs.  We want to be able to use IMAP to
> read the INBOX and folders and use NFS to access the address books and
> signature files on the Unix systems.  At this time we have the IMAP
> part working.
> 
> I am looking for any configuration information, product names, tips of
> any nature from people who have successfully done the NFS part.
> 
> Thank you.
> 
> -jscott-
> 
> -- 
> |J. Scott Williams, BH 313     Ph: (360) 650-2868  FAX: (360) 650-7323 |
> |Academic Tech. User Services  Internet:  scott@cc.wwu.edu             |
> |Western Washington Univ.      "Internet--Talking across the electronic|
> |Bellingham, WA  98225-9094               back fence of the world."-JSW|
> 


From owner-pine-info@cac.washington.edu  Mon Jan 23 06:44:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08909;
	Mon, 23 Jan 95 06:44:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05680;
	Mon, 23 Jan 95 06:33:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from watsun.cc.columbia.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05674;
	Mon, 23 Jan 95 06:33:29 -0800
Received: by watsun.cc.columbia.edu id AA13935
  (5.65c+CU/IDA-1.4.4/HLK for Pine Information List <pine-info@cac.washington.edu>); Mon, 23 Jan 1995 09:33:27 -0500
Date: Mon, 23 Jan 95 9:33:27 EST
From: Joe Brennan <brennan@watsun.cc.columbia.edu>
Subject: Re: Handling Return Receipts within PINE
In-Reply-To: Your message of Sun, 22 Jan 1995 15:02:29 -0500 (EST)
To: Pine Information List <pine-info@cac.washington.edu>
Message-Id: <CMM.0.90.4.790871607.brennan@watsun.cc.columbia.edu>

> On Sun, 22 Jan 1995, Terry Gray wrote:
> > Many, *many* people consider read-receipts to be an invasion of privacy
> So just have an option (settable from the setup menu) that turns receipts
> on.  (ie have it default to off) 

It would be off by default on our system, I am sure.  As long as
receipts are dependent on the site and even the user, they are close
to meaningless since you would never be sure what to conclude when you
do not get a return receipt

Note also that even a receipt does not mean the message was *read*
which is probably what the sender wants to know.  At best an automatic
reply could tell you whether the message was put on screen, but the
recipient could still blow past it without reading it.

The only reliable method is to ask the recipient to send a reply
acknowledging the message.

Joseph Brennan  Postmaster  Academic Information Systems
                Columbia University in the City of New York
                postmaster@columbia.edu



From owner-pine-info@cac.washington.edu  Mon Jan 23 08:39:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12621;
	Mon, 23 Jan 95 08:39:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08653;
	Mon, 23 Jan 95 08:32:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08647;
	Mon, 23 Jan 95 08:32:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWRK9-00038PC; Mon, 23 Jan 95 08:09 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: Re: Need Pine Binaries
Date: 23 Jan 1995 07:53:41 -0800
Message-Id: <3g0je5$kft@garlic.com>
References: <3fphid$a38@garlic.com>

: I am still trying to find someone out there who can tell me where I can ftp 
: Pine binaries for SCO  ...

Well, so far I've been pointed to ftp.cac.washington.edu, and celestial.com.
Washington doesn't have the compiled binaries for SCO (although they have
most everything else) and celestial.com doesn't seem to exist ...

Surely SOMEONE out there has compiled Pine/pico under SCO???  

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


From owner-pine-info@cac.washington.edu  Mon Jan 23 08:45:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13113;
	Mon, 23 Jan 95 08:45:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07730;
	Mon, 23 Jan 95 08:32:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07724;
	Mon, 23 Jan 95 08:32:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWRMW-00038OC; Mon, 23 Jan 95 08:11 PST
To: pine-info@cac.washington.edu
From: sef@primenet.com (Stephen E. Farnum)
Subject: Re: Pine for MS-Windoze
Date: Sun, 22 Jan 95 16:45:34 PST
Message-Id: <3fuu8e$7de@news.primenet.com>
References: <3fkosh$ouc@j51.com>
Mime-Version: 1.0

In article <3fkosh$ouc@j51.com>, JakeColman-JNCConsultingGroup says...
>
>Is there a version of Pine that will run over a PPP connection under Windoze?
>
[snip]

Jake,

I use PC Pine For Windows over a PPP connection without problems. The most difficult 
step is setting up the inbox address correctly. 

Try ftp'ing ftp.cac.washington.edu and check the /mail/ directory for the latest 
version.
-- 
|===========================================================================|
|=============  Stephen E. Farnum             sef@primenet.com  ============|
|=============  Woodland Hills CA 91364           sef@lafn.org  ============|
|=============                                                  ============|
|=============  Voice: 818-888-7815 Ext: 333  Fax: 818-348-4039 ============|
|===========================================================================|



From owner-pine-info@cac.washington.edu  Mon Jan 23 10:12:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18978;
	Mon, 23 Jan 95 10:12:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11054;
	Mon, 23 Jan 95 10:00:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11048;
	Mon, 23 Jan 95 10:00:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWShI-00038MC; Mon, 23 Jan 95 09:37 PST
To: pine-info@cac.washington.edu
From: rbawa@gbc.gbrownc.on.ca (Rashid Bawa)
Subject: POP binaries for SOLARIS 2.3
Date: 23 Jan 1995 11:49:21 -0500
Message-Id: <3g0mmh$1bg@gbc.gbrownc.on.ca>

I am looking out for POP binaries (POP, POP2, POP3) that will run on
a SparcClassic running Solaris 2.3. If anyone has the location of a site,
please send me email.

Thanking you in advance.

------------------------------------------------------------------------ 
Rashid Bawa                     George Brown College
System Administrator            146 Kendal Ave.
                                Toronto, Ontario
Phone:  (416) 944-4591          Canada
rbawa@gbrownc.on.ca
------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Mon Jan 23 10:12:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18999;
	Mon, 23 Jan 95 10:12:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10177;
	Mon, 23 Jan 95 10:00:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10171;
	Mon, 23 Jan 95 10:00:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWShk-00038KC; Mon, 23 Jan 95 09:37 PST
To: pine-info@cac.washington.edu
From: glenn@creator.ucns.uga.edu (Glenn Leavell)
Subject: several Pine suggestions
Date: 23 Jan 1995 17:35:56 GMT
Message-Id: <3g0pds$r9c@hobbes.cc.uga.edu>

I really enjoy using Pine, and I appreciate the work that the authors have
put into developing and supporting it.  Here are a few suggestions for
future releases of Pine that the developers can "take or leave".  Thanks!

1)  In INDEX mode, allow the 'k' and 'j' keys to be used to move the current
    pointer up and down (j key would only function like this if
    jump short cut were turned on).  This convention can be
    found in vi, Elm, Gopher, and other utilities, so it makes things
    somewhat consistent.

2)  When reading a message with the builtin Pine pager, the spacebar
    scrolls the message down one page.  Add a feature such that the
    RETURN key can be used to scroll down one line.  This convention
    is used with the Unix more and less commands, as well as some
    other pagers.

3)  Add a special Quit-type command that will exit Pine without making
    any changes to the current folder.  For example, when this command
    is used, all messages marked for deletion will NOT be deleted, and
    all messages that were marked as new ('N') when the folder was
    opened will still be marked as such when the folder is opened 
    the next time.

4)  Add an option that makes the 'n' (NextMsg) command in the INDEX skip
    over messages marked for deletion.

-- 
Glenn Leavell, glenn@uga.edu
University of Georgia, University Computing and Networking Services



From owner-pine-info@cac.washington.edu  Mon Jan 23 10:18:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19420;
	Mon, 23 Jan 95 10:18:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11399;
	Mon, 23 Jan 95 10:12:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11393;
	Mon, 23 Jan 95 10:12:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWSuF-00038QC; Mon, 23 Jan 95 09:50 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: Need Pine Binaries
Date: Mon, 23 Jan 1995 17:24:14 GMT
Message-Id: <D2vCCE.5p4@ssi.edc.org>
References: <3fphid$a38@garlic.com> <Pine.SUN.3.91.950121124836.6023A-100000@kelly.teleport.com>

Knute Snortum (knute@teleport.com) wrote:
: On 20 Jan 1995, Robert Mann Packaging Co. wrote:

: > I am still trying to find someone out there who can tell me where I can ftp 
: > Pine binaries for SCO  ...
: > 
: I have been told there are some at celestial.com, but I have yet to find 
: them.  

They're definitely there.  However, frp.celestial.com recently changes 
its IP address, and a lot of sites still don't know about it.  The change 
happened a couple of months ago, but my site (for instance) still finds 
the old address.  I've just looked at the real site, and there are two 
files which you are looking for:

-rw-rw-r--   1 jwc      4217275 Nov 25 11:10 pine-3.91.tar.gz
-rw-rw-r--   1 jwc      1065011 Nov 28 17:47 pine3.91.sco.bins.tar.gz

The first has both source and binaries.  The second, binaries only.

The new information for ftp.celestial.com is that it's an alias for 
camco1.celestial.com, 192.136.111.2.  Go there directly.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Mon Jan 23 10:42:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20806;
	Mon, 23 Jan 95 10:42:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11132;
	Mon, 23 Jan 95 10:30:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11126;
	Mon, 23 Jan 95 10:30:29 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id KAA26514 for <pine-info@cac.washington.edu>; Mon, 23 Jan 1995 10:30:25 -0800
Date: Mon, 23 Jan 1995 10:30:24 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: "Robert Mann Packaging Co." <rmp@garlic.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Need Pine Binaries, where's celestial.com?
In-Reply-To: <3g0je5$kft@garlic.com>
Message-Id: <Pine.SUN.3.91.950123102443.15201A-100000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 23 Jan 1995, Robert Mann Packaging Co. wrote:

> : I am still trying to find someone out there who can tell me where I can ftp 
> : Pine binaries for SCO  ...
> 
> Well, so far I've been pointed to ftp.cac.washington.edu, and celestial.com.
> Washington doesn't have the compiled binaries for SCO (although they have
> most everything else) and celestial.com doesn't seem to exist ...
> 
> Surely SOMEONE out there has compiled Pine/pico under SCO???  

celestial.com *does* (or did) exist; I've been on there, but perhaps like 
you, I haven't been able to connect to them recently, and I *really* want 
to!

I did find an old file listing of their's, and it seems it has pine 
binaries in it.  If anyone knows what happenned to celestial.com, please 
tell us!

If you're desparate, I have a binary for SCO 3.2v4.1, if that helps. 

---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646



From owner-pine-info@cac.washington.edu  Mon Jan 23 10:44:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20862;
	Mon, 23 Jan 95 10:44:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11124;
	Mon, 23 Jan 95 10:30:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11118;
	Mon, 23 Jan 95 10:30:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWTCX-00038RC; Mon, 23 Jan 95 10:09 PST
To: pine-info@cac.washington.edu
From: jywong@abalone.ucsb.edu (Joyce Y. Wong)
Subject: Pine compiled for silicon graphics????
Date: 23 Jan 1995 09:45:43 -0800
Message-Id: <3g0q07$qo2@abalone.ucsb.edu>

I am looking for pine compiled for a silicon graphics machine
running irix 4.0

Can anyone help me??

thanks

joyce



From owner-pine-info@cac.washington.edu  Mon Jan 23 11:38:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24024;
	Mon, 23 Jan 95 11:38:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13442;
	Mon, 23 Jan 95 11:30:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul4.u.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13436;
	Mon, 23 Jan 95 11:30:20 -0800
Received: by saul4.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23441;
	Mon, 23 Jan 95 11:30:17 -0800
X-Sender: absweger@saul4.u.washington.edu
Date: Mon, 23 Jan 1995 11:30:16 -0800 (PST)
From: Andrew Sweger <absweger@u.washington.edu>
To: Glenn Leavell <glenn@creator.ucns.uga.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: several Pine suggestions
In-Reply-To: <3g0pds$r9c@hobbes.cc.uga.edu>
Message-Id: <Pine.OSF.3.91a.950123112810.21590B-100000@saul4.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 23 Jan 1995, Glenn Leavell wrote:

> I really enjoy using Pine, and I appreciate the work that the authors have
> put into developing and supporting it.  Here are a few suggestions for
> future releases of Pine that the developers can "take or leave".  Thanks!
> 
> 3)  Add a special Quit-type command that will exit Pine without making
>     any changes to the current folder.  For example, when this command
>     is used, all messages marked for deletion will NOT be deleted, and
>     all messages that were marked as new ('N') when the folder was
>     opened will still be marked as such when the folder is opened 
>     the next time.

By default (new users), Pine will ask if you want messages marked for 
deletion to be removed permanently.

> 4)  Add an option that makes the 'n' (NextMsg) command in the INDEX skip
>     over messages marked for deletion.

Try the [TAB] key. You might need to set some options in your 
configuration. Basically, it will cause you to jump to the next 
new/unread message.

Happy trails!

-- 
  /  Andrew B. Sweger                      absweger@u.washington.edu
 //  Computer Support Manager              csg@fammed.washington.edu
 \\  Department of Family Medicine, HQ-30  (206) 543-2461 (Office)
 //  UNIVERSITY OF WASHINGTON              (206) 685-4337 (Voice Mail)
 /   Seattle, WA 98195                     (206) 685-0610 (FAX)
------------------------------------------------------------------------------
The great thing about multitasking is that several things can go wrong at once.




From owner-pine-info@cac.washington.edu  Mon Jan 23 13:43:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01632;
	Mon, 23 Jan 95 13:43:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17033;
	Mon, 23 Jan 95 13:36:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ns.ge.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17027;
	Mon, 23 Jan 95 13:36:10 -0800
Received: from [3.12.38.33] by ns.GE.com (5.65/GE Gateway 1.32) with SMTP
	 id AA04120; Mon, 23 Jan 1995 16:35:38 -0500
Received: by mmpcs1.PSF.GE.COM (4.1/GEA Sun server 2.7)
	id AA23246; Mon, 23 Jan 95 16:33:54 EST
Date: Mon, 23 Jan 1995 16:33:53 -0500 (EST)
From: Don Sugarman <sugarman@mmpcs1.psf.ge.com>
To: Knute Snortum <knute@teleport.com>
Cc: "Robert Mann Packaging Co." <rmp@garlic.com>, pine-info@cac.washington.edu
Subject: Re: Need Pine Binaries, where's celestial.com?
In-Reply-To: <Pine.SUN.3.91.950123102443.15201A-100000@linda.teleport.com>
Message-Id: <Pine.SUN.3.90.950123163243.23242A-100000@mmpcs1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I just got into celestial via connect to anonymous@192.136.111.2, as 
mentioned in an earlier posting.

Thanks to whomever..
Don Sugarman
sugarman@mmpcs1.psf.ge.com


On Mon, 23 Jan 1995, Knute Snortum wrote:

> On 23 Jan 1995, Robert Mann Packaging Co. wrote:
> 
> > : I am still trying to find someone out there who can tell me where I can ftp 
> > : Pine binaries for SCO  ...
> > 
> > Well, so far I've been pointed to ftp.cac.washington.edu, and celestial.com.
> > Washington doesn't have the compiled binaries for SCO (although they have
> > most everything else) and celestial.com doesn't seem to exist ...
> > 
> > Surely SOMEONE out there has compiled Pine/pico under SCO???  
> 
> celestial.com *does* (or did) exist; I've been on there, but perhaps like 
> you, I haven't been able to connect to them recently, and I *really* want 
> to!
> 
> I did find an old file listing of their's, and it seems it has pine 
> binaries in it.  If anyone knows what happenned to celestial.com, please 
> tell us!
> 
> If you're desparate, I have a binary for SCO 3.2v4.1, if that helps. 
> 
> ---Knute Snortum             Internet:   knute@msi.masi.com
>    MAS, Inc.                    or       knute@teleport.com
> 			    CompuServe:  72144,1646
> 
> 


From owner-pine-info@cac.washington.edu  Mon Jan 23 13:54:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02288;
	Mon, 23 Jan 95 13:54:23 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16460;
	Mon, 23 Jan 95 13:46:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from dns1.uga.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16454;
	Mon, 23 Jan 95 13:45:58 -0800
Received: from creator.ucns.uga.edu by dns1.uga.edu with SMTP id AA26039
  (5.67b/IDA-1.5 for <pine-info@cac.washington.edu>); Mon, 23 Jan 1995 16:45:57 -0500
Received: by creator.ucns.uga.edu id AA36814
  (5.67b/IDA-1.5); Mon, 23 Jan 1995 16:45:56 -0500
Date: Mon, 23 Jan 1995 16:45:56 -0500 (EST)
From: Glenn Leavell <glenn@uga.edu>
X-Sender: glenn@creator.ucns.uga.edu
To: Andrew Sweger <absweger@u.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: several Pine suggestions
In-Reply-To: <Pine.OSF.3.91a.950123112810.21590B-100000@saul4.u.washington.edu>
Message-Id: <Pine.A32.3.91.950123162021.34575E-100000@creator.ucns.uga.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

Thanks for your note and your comments.

> > 3)  Add a special Quit-type command that will exit Pine without making
> >     any changes to the current folder.  For example, when this command
> >     is used, all messages marked for deletion will NOT be deleted, and
> >     all messages that were marked as new ('N') when the folder was
> >     opened will still be marked as such when the folder is opened 
> >     the next time.
> 
> By default (new users), Pine will ask if you want messages marked for 
> deletion to be removed permanently.

Right.  But, I was thinking of something more global, that would allow the
user to exit the folder without marking ANY changes to folder that were made
since the last Expunge.  This would be especially useful for system
administrators who are sometimes called to open user's mail folders when they
complain of a corrupt folder, etc.  In this case, it would be nice to "reset"
the folder so that all new ('N') messages stayed marked that way, even if they
had actually been read.


> > 4)  Add an option that makes the 'n' (NextMsg) command in the INDEX skip
> >     over messages marked for deletion.
> 
> Try the [TAB] key. You might need to set some options in your 
> configuration. Basically, it will cause you to jump to the next 
> new/unread message.

Yes, I use it regularly.  But, it only goes to the next new/unread
message.  Several new Pine users here have mentioned to me that they 
would like to be able to quickly be able to get to the next message
that has not been marked for deletion.  Maybe that's being too picky, though.

Thanks again.

-- 
Glenn Leavell, glenn@uga.edu
University of Georgia, University Computing and Networking Services



From owner-pine-info@cac.washington.edu  Mon Jan 23 14:30:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03893;
	Mon, 23 Jan 95 14:30:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18289;
	Mon, 23 Jan 95 14:22:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul2.u.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18283;
	Mon, 23 Jan 95 14:22:02 -0800
Received: by saul2.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27827;
	Mon, 23 Jan 95 14:21:55 -0800
X-Sender: absweger@saul2.u.washington.edu
Date: Mon, 23 Jan 1995 14:21:55 -0800 (PST)
From: Andrew Sweger <absweger@u.washington.edu>
To: Glenn Leavell <glenn@uga.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: several Pine suggestions
In-Reply-To: <Pine.A32.3.91.950123162021.34575E-100000@creator.ucns.uga.edu>
Message-Id: <Pine.OSF.3.91a.950123141642.26347C-100000@saul2.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 23 Jan 1995, Glenn Leavell wrote:

> Right.  But, I was thinking of something more global, that would allow the
> user to exit the folder without marking ANY changes to folder that were made
> since the last Expunge.  This would be especially useful for system
> administrators who are sometimes called to open user's mail folders when they
> complain of a corrupt folder, etc.  In this case, it would be nice to "reset"
> the folder so that all new ('N') messages stayed marked that way, even if they
> had actually been read.

SysAdmins can start pine with the -o option to cause the first 
mailbox/folder to be openned as read only.

> Yes, I use ([TAB]) regularly.  But, it only goes to the next new/unread
> message.  Several new Pine users here have mentioned to me that they 
> would like to be able to quickly be able to get to the next message
> that has not been marked for deletion.  Maybe that's being too picky, though.

Either way, it's feaping creaturism, I say. I wouldn't say one option is 
any better than the other, so it could be either way for me.

-- 
  /  Andrew B. Sweger                      absweger@u.washington.edu
 //  Computer Support Manager              csg@fammed.washington.edu
 \\  Department of Family Medicine, HQ-30  (206) 543-2461 (Office)
 //  UNIVERSITY OF WASHINGTON              (206) 685-4337 (Voice Mail)
 /   Seattle, WA 98195                     (206) 685-0610 (FAX)
------------------------------------------------------------------------------
The great thing about multitasking is that several things can go wrong at once.


From owner-pine-info@cac.washington.edu  Mon Jan 23 14:31:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03968;
	Mon, 23 Jan 95 14:31:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17463;
	Mon, 23 Jan 95 14:21:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17457;
	Mon, 23 Jan 95 14:21:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWWmW-00038TC; Mon, 23 Jan 95 13:58 PST
To: pine-info@cac.washington.edu
From: schueman@access.digex.net (Greg Schueman)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 23 Jan 1995 16:16:23 -0500
Message-Id: <3g16b7$r06@access1.digex.net>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca>

In article <3g0mmh$1bg@gbc.gbrownc.on.ca>,
Rashid Bawa <rbawa@gbc.gbrownc.on.ca> wrote:
>I am looking out for POP binaries (POP, POP2, POP3) that will run on
>a SparcClassic running Solaris 2.3. If anyone has the location of a site,

Look at ftp://ftp.digex.net/pub/access/schueman/popper.tar.gz.

This contains source + binaries for a POP3 server. It was compiled under
Solaris 2.3 on a Sparc 10.

Enjoy,
  -Greg


From owner-pine-info@cac.washington.edu  Mon Jan 23 14:53:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05054;
	Mon, 23 Jan 95 14:53:02 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18046;
	Mon, 23 Jan 95 14:45:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18039;
	Mon, 23 Jan 95 14:45:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWXB0-00038MC; Mon, 23 Jan 95 14:23 PST
To: pine-info@cac.washington.edu
From: pflores@phoenix.phoenix.net (Paul Flores)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 23 Jan 1995 21:49:57 GMT
Message-Id: <3g18a5$epp@gryphon.phoenix.net>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca>

Rashid Bawa (rbawa@gbc.gbrownc.on.ca) wrote:
: I am looking out for POP binaries (POP, POP2, POP3) that will run on
: a SparcClassic running Solaris 2.3. If anyone has the location of a site,
: please send me email.

: Thanking you in advance.


Please post here as well!!!!   (Or send me email as well!!!)

Paul

http://www.phoenix.net/USERS/pflores.html



From owner-pine-info@cac.washington.edu  Mon Jan 23 15:43:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07590;
	Mon, 23 Jan 95 15:43:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20257;
	Mon, 23 Jan 95 15:36:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from desiree.teleport.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20251;
	Mon, 23 Jan 95 15:36:55 -0800
Received: from linda.teleport.com (knute@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.9/8.6.9) with ESMTP id PAA24307 for <pine-info@cac.washington.edu>; Mon, 23 Jan 1995 15:36:52 -0800
Date: Mon, 23 Jan 1995 15:36:53 -0800 (PST)
From: Knute Snortum <knute@teleport.com>
To: Bill Hudson <bill@rmp.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Need Pine Binaries, where's celestial.com? (fwd) 
In-Reply-To: <9501231049.aa19310@gilroy.rmp.com>
Message-Id: <Pine.SUN.3.91.950123153434.8922A-100000@linda.teleport.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 23 Jan 1995, Bill Hudson wrote:

> Reply From bill At 10:46A On Mon Jan 23 1995:
> 
> >If you're desparate, I have a binary for SCO 3.2v4.1, if that helps.
> 
> Thanks.  Do you know if that will work under 3.2v4.2?  If nothing else pans 
> out, I may tap you for it ...
> 
> Thanks again!.

I found binaries on odi.cwc.whecn.edu/ub/sco-ports.  Also, check the mail 
on celestial.com. 

---Knute Snortum             Internet:   knute@msi.masi.com
   MAS, Inc.                    or       knute@teleport.com
			    CompuServe:  72144,1646



From owner-pine-info@cac.washington.edu  Mon Jan 23 15:57:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08292;
	Mon, 23 Jan 95 15:57:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20646;
	Mon, 23 Jan 95 15:50:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20640;
	Mon, 23 Jan 95 15:50:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWYHk-00038UC; Mon, 23 Jan 95 15:35 PST
To: pine-info@cac.washington.edu
From: offsite@crl.com (Lee (not F) Bailey)
Subject: [Q] pine-debug* files -- Make it *STOP*
Date: 23 Jan 1995 22:58:40 GMT
Message-Id: <3g1cb0$dgd@nntp.crl.com>

What have I done to my pine program to make it hate me? I was toolin along
just fine for weeks, then suddenly pine starts makeing these files in my
$HOME. They are of the form pine-debug1, 2, ... 
  
How do I make it stop??? I have 'whereis'd everything I could find, but 
nothing about these files.
  
Please help. Thanks

--
______________________________________________________________________________
Lee Bailey	|  E-Mail:   offsite@crl.com
	User of Geoworks Ensemble instead of M$ Windoze
	Try the demo at ftp://arginine.umdnj.edu/pub/geos/publish
		     or ftp://ftp.mcs.com/mcsnet.users/jbarr/GeoPublish	


From owner-pine-info@cac.washington.edu  Mon Jan 23 16:06:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08805;
	Mon, 23 Jan 95 16:06:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19942;
	Mon, 23 Jan 95 15:59:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19936;
	Mon, 23 Jan 95 15:59:21 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWYSO-00038MC; Mon, 23 Jan 95 15:46 PST
To: pine-info@cac.washington.edu
From: penev@pisa.Rockefeller.edu (Penio Penev)
Subject: Re: Abort signal
Message-Id: <D2vBy3.EDL@rockyd.rockefeller.edu>
References: <3fno24$38e@almaak.usc.edu>
Date: Mon, 23 Jan 1995 17:15:39 GMT

On 19 Jan 1995 23:17:24 -0800 [Howard Gillman] (gillman@almaak.usc.edu) wrote:
| I asked a new listserv to send me mail in digest format.  When I received 
| the message the index indicated that it was 43,810 characters.  When I 
| opened the file I received a blank screen with a note 
| "Parts/Attachments"; at the bottom of the blank screen it said "All of 
| message text."  I tried to View the attachments, but the attachment index 
| had nothing on it.  When I press [V]iew anyway pine quick with the 
| message "But in Pine detected:  'Received abort signal.'  Exiting pine."  
| So, what the heck is the problem with the message I received, and why 
| can't I get access to it?  Thanks in advance.

Something similar happened to me. Pine reports the right length, but
does not display the message. After I looked in my mailbox with emacs
(or any other text editor, capable of displaying control codes), I saw
a block of 4096 zeroes in the file. 4096=4K and is exactly one virtual
memory page. Pine does not display the rest of the text, probably it
is treating the message as a zero-delimited string by the C convention :-( 
The problem is caused most probably by an incoherency in the NSF
mounting of the mail directory :-(

--
Penio Penev <Penev@venezia.Rockefeller.edu> 1-212-327-7423


From owner-pine-info@cac.washington.edu  Mon Jan 23 16:31:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09973;
	Mon, 23 Jan 95 16:31:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21464;
	Mon, 23 Jan 95 16:20:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21458;
	Mon, 23 Jan 95 16:20:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWYlP-00038MC; Mon, 23 Jan 95 16:05 PST
To: pine-info@cac.washington.edu
From: h9397584@hkusub (Michael Agelasto)
Subject: import address list?
Message-Id: <D2vtrK.23K@hkuxb.hku.hk>
Date: Mon, 23 Jan 1995 23:40:31 GMT

How do I import a file that contains addresses and then transfer them to 
the ADDRESS book, or to a list inside ADDRESS book?  

I want to avoid having to retype the entire list within PINE.  

Thanks. 
--
=====================================================================
Michael Agelasto                       Phone: (852) 2858-1914
Department of Education                       (852) 2549-5678 (res)
University of Hong Kong                  Fax: (852) 2858-5649
Hong Kong                              email: h9397584@hkucc.hku.hk
                                       email: h9397584@hkusub.hku.hk
=====================================================================


From owner-pine-info@cac.washington.edu  Mon Jan 23 16:40:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10319;
	Mon, 23 Jan 95 16:40:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20717;
	Mon, 23 Jan 95 16:29:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20711;
	Mon, 23 Jan 95 16:29:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWYuw-00038QC; Mon, 23 Jan 95 16:15 PST
To: pine-info@cac.washington.edu
From: valko@cyberspace.com (Jack Valko)
Subject: Need to secure pine
Date: 23 Jan 1995 15:28:28 -0800
Message-Id: <3g1e2s$5sk@case.cyberspace.com>

I would like to know if there is some way to set a configuration in pine 
so that users can't change it from the Setup menu.  Specifically, I want 
to restrict the alternate editor feature.  I have specified 
'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
doesn't seem to do it.  Can anyone help?

==================================================
Jack Valko           |       - Cyberspace -
System Administrator | 300 Queen Anne Ave. N. #396 
cyberspace.com       |   Seattle, WA 98109-4599 
cyberspace.net       |       (206) 281-5397 
==================================================



From owner-pine-info@cac.washington.edu  Mon Jan 23 17:13:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12958;
	Mon, 23 Jan 95 17:13:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22816;
	Mon, 23 Jan 95 17:05:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22810;
	Mon, 23 Jan 95 17:05:48 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWZQp-00038QC; Mon, 23 Jan 95 16:48 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Handling Return Receipts within PINE (fwd)
Date: 23 Jan 1995 23:59:53 GMT
Message-Id: <3g1ftq$pff@cronkite.ocis.temple.edu>

Comes here Mr. Steve Lowe with this opinion in the "comp.mail.pine" group in
this article on 22 Jan 1995 23:55:04 -0800:

 +   I prompted this discussion with how could I send mail messages 
 +   registered.  Is there a simple way to do this within PINE 3.91?

What do you mean by registered?

 +   > Many, *many* people consider read-receipts to be an invasion of privacy
 +   > would refuse to use any tool that "offered" such a facility.  I would not
 +   > look for this feature in Pine anytime soon...
 +
 +   So just have an option (settable from the setup menu) that turns receipts
 +   on.  (ie have it default to off)  This is a feature available on cc:Mail,
 +   and was used extensively where I last worked -- it can be a great help

We have cc:Mail for inter-office email over a LAN and I (many others) *HATE*
it when someone sends me a mail requesting reciept.

Nowadays mail from "i will always ask for recpt" types don't get read at all.
I just forward them to myself and then read it and if it is worth i will reply
else i will let the sender wonder why I haven't read the "reciept reqd. mail"

Please do not include this feature(or bug i should say) in Pine. I don't want
the system spend precious CPU time sending stupid reciept mail back and forth.

For such extreme cases Return-Receipt-To: works just fine.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 23 17:20:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13214;
	Mon, 23 Jan 95 17:20:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22979;
	Mon, 23 Jan 95 17:14:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22973;
	Mon, 23 Jan 95 17:14:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWZbR-00038TC; Mon, 23 Jan 95 16:59 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 95 00:25:25 GMT
Message-Id: <ellis.790907125@gmi.edu>
References: <Pine.ULT.3.92.950122121002.21432W-100000@shiva1.cac.washington.edu> <Pine.SUN.3.91.950122151411.22083G-100000@lab19.cs.purdue.edu>

simmonmt@cs.purdue.edu (Matt Simmons) writes:

 >On Sun, 22 Jan 1995, Terry Gray wrote:
 >> If and when an Internet standard emerges for Read receipt requests and
 >> responses, we would certainly consider such an option... and you can
 >> definitely bank on the fact that the default would be OFF! 

 >Which leaves us with the chicken and the egg problem -- the standard won't
 >be created until programs support it, and programs won't support it until
 >there's a standard. That's why I suggested what I did in my first post --
 >that Pine take the lead, create a standard, and let the world follow.

Give up.  Most people who have thought about it do not want it, and would
turn off the option anyway.  If it is important for you as a recipient to
let people know you have received it, 'r' and tell them.  If you only want
to know as a sender, then many people consider this to be snooping.


-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Mon Jan 23 17:22:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13336;
	Mon, 23 Jan 95 17:22:10 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22123;
	Mon, 23 Jan 95 17:14:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22117;
	Mon, 23 Jan 95 17:14:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWZbo-00038UC; Mon, 23 Jan 95 16:59 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Handling Return Receipts within PINE (fwd)
Date: 24 Jan 95 00:29:09 GMT
Message-Id: <ellis.790907349@gmi.edu>
References: <Pine.ULT.3.91.950122140551.28499A-100000@admin.aurora.edu>

slowe@admin.aurora.edu (Steve Lowe) writes:


 >Terry --

 >The VMS mail package that we replaced with PINE offered the user the 
 >option of sending mail messages registered.  If I wanted to send a 
 >specific mail message registered, I could do that.

 >I prompted this discussion with how could I send mail messages 
 >registered.  Is there a simple way to do this within PINE 3.91?

Simply put the line:

Please reply when you receive this.

in the message.

 > - Steve Lowe
 >   Aurora University


 >---------- Forwarded message ----------
 >Date: Sun, 22 Jan 1995 15:02:29 -0500 (EST)
 >From: Matt Simmons <simmonmt@cs.purdue.edu>
 >To: Terry Gray <gray@cac.washington.edu>
 >Cc: Portia Shao <PORTIA@INNOSOFT.COM>, Steve Lowe <slowe@admin.aurora.edu>,
 >    Pine Information List <pine-info@cac.washington.edu>
 >Subject: Re: Handling Return Receipts within PINE

 >On Sun, 22 Jan 1995, Terry Gray wrote:
 >> Many, *many* people consider read-receipts to be an invasion of privacy and 
 >> would refuse to use any tool that "offered" such a facility.  I would not 
 >> look for this feature in Pine anytime soon...
 >So just have an option (settable from the setup menu) that turns receipts
 >on.  (ie have it default to off)  This is a feature available on cc:Mail,
 >and was used extensively where I last worked -- it can be a great help

-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Mon Jan 23 17:23:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13365;
	Mon, 23 Jan 95 17:23:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22141;
	Mon, 23 Jan 95 17:14:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22129;
	Mon, 23 Jan 95 17:14:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWZdL-00038SC; Mon, 23 Jan 95 17:01 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 1995 00:09:29 GMT
Message-Id: <3g1gfp$pff@cronkite.ocis.temple.edu>

Comes here Mr. Rahul Dhesi with this opinion in the "comp.mail.pine" group in
this article on 23 Jan 1995 10:10:04 GMT:

 +   >How hard would it be to just have Pine start supporting read receipts?

 +   It would cause a serious invasion of privacy, so it would ideally
 +   be a user-settable option.

This will become such an nightmare, I may have to set it OFF premanently
in pine.conf.fixed atleast here.

That is when and if at all Pine *does* have that feature.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 23 17:46:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14153;
	Mon, 23 Jan 95 17:46:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23410;
	Mon, 23 Jan 95 17:39:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23404;
	Mon, 23 Jan 95 17:39:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWZyU-00038TC; Mon, 23 Jan 95 17:23 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: several Pine suggestions
Date: 24 Jan 1995 00:46:47 GMT
Message-Id: <3g1iln$pff@cronkite.ocis.temple.edu>

Comes here Mr. Glenn Leavell with this opinion in the "comp.mail.pine" group in
this article on 23 Jan 1995 17:35:56 GMT:

 +   1)  In INDEX mode, allow the 'k' and 'j' key to be used to move the current
 +       pointer up and down (j key would only function like this if
 +       jump short cut were turned on).  This convention can be
 +       found in vi, Elm, Gopher, and other utilities, so it makes things
 +       somewhat consistent.

While personally I wouldn't mind using h,j,k&l keys for navigation I can
almost think of all the new users stopping to use Pine if that is implemented
as one of the main reasons why they think VI is eVIl is because if h,j,k&l.

What would be nice is the use of "/" forward slash for Search instead of W,
as most of all the other utilities make use of that.

 +   2)  When reading a message with the builtin Pine pager, the spacebar
 +       scrolls the message down one page.  Add a feature such that the
 +       RETURN key can be used to scroll down one line.  This convention
 +       is used with the Unix more and less commands, as well as some
 +       other pagers.

Up and Down Arrow keys again function very well in this regard.

What would be nice is if there's an option for the user to set the default
action for Return key. One would choose Return to Page Down, while the other
would set it to Advance by one line while the third (me) would set it to
select the body of the message without the headers and print it to the attchd.
printer. Basically what I'm driving at is "user defined key" macros.

 +   3)  Add a special Quit-type command that will exit Pine without making
 +       any changes to the current folder.  For example, when this command
 +       is used, all messages marked for deletion will NOT be deleted, and
 +       all messages that were marked as new ('N') when the folder was
 +       opened will still be marked as such when the folder is opened 
 +       the next time.

Yes, an X for eXit with an Abandon Changes to mailbox prompt will be ideal.

Again here an option for the user to set X to either eXit or Expunge,
whichever he finds useful as I for one almost never use the Expunge feature
but that doesn't mean others aren't. So to strike an balance...!

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 23 18:01:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14832;
	Mon, 23 Jan 95 18:01:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22908;
	Mon, 23 Jan 95 17:56:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22902;
	Mon, 23 Jan 95 17:56:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWaK3-00038QC; Mon, 23 Jan 95 17:45 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: 24 Jan 1995 01:00:35 GMT
Message-Id: <3g1jfj$pff@cronkite.ocis.temple.edu>

Comes here Mr. Lee (not F) Bailey with this opinion in the "comp.mail.pine"
group in this article on 23 Jan 1995 22:58:40 GMT:

 +   What have I done to my pine program to make it hate me? I was toolin along
 +   just fine for weeks, then suddenly pine starts makeing these files in my
 +   $HOME. They are of the form pine-debug1, 2, ... 
 +   How do I make it stop??? I have 'whereis'd everything I could find, but 
 +   nothing about these files.

Invoke Pine with the -d 0 flag to suppress Pine producing debug-level files.
Usage:

% pine -d 0   (0 as in zero and not as in "OhMyGosh, Pine hates me") :-)

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 23 18:07:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14986;
	Mon, 23 Jan 95 18:07:27 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23836;
	Mon, 23 Jan 95 18:02:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23830;
	Mon, 23 Jan 95 18:02:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWaQH-00038SC; Mon, 23 Jan 95 17:51 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Need to secure pine
Date: 24 Jan 1995 01:11:20 GMT
Message-Id: <3g1k3o$pff@cronkite.ocis.temple.edu>

Comes here Mr. Jack Valko with this opinion in the "comp.mail.pine" group in
this article on 23 Jan 1995 15:28:28 -0800:

 +   I would like to know if there is some way to set a configuration in pine 
 +   so that users can't change it from the Setup menu.  Specifically, I want 
 +   to restrict the alternate editor feature.  I have specified 
 +   'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
 +   doesn't seem to do it.  Can anyone help?

While settings in pine.conf can be overridden by the user by making use of
the -P flag, settings in pine.conf.fixed cannot be. So in that file make sure
you give a <Empty Value> ("") value for the editor option.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 23 18:09:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15035;
	Mon, 23 Jan 95 18:09:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23056;
	Mon, 23 Jan 95 18:02:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23050;
	Mon, 23 Jan 95 18:02:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWaQL-00038TC; Mon, 23 Jan 95 17:52 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Need Pine Binaries, where's celestial.com?
Date: 24 Jan 1995 01:18:26 GMT
Message-Id: <3g1kh2$pff@cronkite.ocis.temple.edu>

Comes here Mr. Knute Snortum with this opinion in the "comp.mail.pine" group in
this article on 23 Jan 1995 10:40:41 -0800:

 +   > Surely SOMEONE out there has compiled Pine/pico under SCO???  

 +   celestial.com *does* (or did) exist; I've been on there, but ............ 

Don't they come pre-compiled in the Slackware CD-ROM avail. for free with SCO?

Check out this URL: http://www.sco.com
Enjoy!

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 23 19:05:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16688;
	Mon, 23 Jan 95 19:05:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24713;
	Mon, 23 Jan 95 18:59:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24707;
	Mon, 23 Jan 95 18:59:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWbDj-00038QC; Mon, 23 Jan 95 18:43 PST
To: pine-info@cac.washington.edu
From: glenn@creator.ucns.uga.edu (Glenn Leavell)
Subject: Re: several Pine suggestions
Date: 24 Jan 1995 02:43:07 GMT
Message-Id: <3g1pfr$4p5@hobbes.cc.uga.edu>
References: <3g1iln$pff@cronkite.ocis.temple.edu>

In article <3g1iln$pff@cronkite.ocis.temple.edu>,
Wet-Sprocket <shrim@worf.ocis.temple.edu> wrote:

>While personally I wouldn't mind using h,j,k&l keys for navigation I can
>almost think of all the new users stopping to use Pine if that is implemented
>as one of the main reasons why they think VI is eVIl is because if h,j,k&l.

You're absolutely right; it shouldn't a default.  But, they are rather
ubiquitous, and for those of us who are used to using them, it would
be a nice option.

>What would be nice is the use of "/" forward slash for Search instead of W,
>as most of all the other utilities make use of that.

Agreed.  It would be nice if both worked.

> +   2)  When reading a message with the builtin Pine pager, the spacebar
> +       scrolls the message down one page.  Add a feature such that the
> +       RETURN key can be used to scroll down one line.  This convention
> +       is used with the Unix more and less commands, as well as some
> +       other pagers.
>
>Up and Down Arrow keys again function very well in this regard.
>
>What would be nice is if there's an option for the user to set the default
>action for Return key. One would choose Return to Page Down, while the other
>would set it to Advance by one line while the third (me) would set it to
>select the body of the message without the headers and print it to the attchd.
>printer. Basically what I'm driving at is "user defined key" macros.

The Up and Down Arrow keys do work fine, but when you're used to using
the RETURN key in a bunch of applications, it's awkward when it
doesn't work in another (but of course, I CAN get over this).  User-definable
keys as an advanced feature would be nice too.


-- 
Glenn Leavell, glenn@uga.edu
University of Georgia, University Computing and Networking Services


From owner-pine-info@cac.washington.edu  Mon Jan 23 19:20:18 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17187;
	Mon, 23 Jan 95 19:20:18 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24926;
	Mon, 23 Jan 95 19:12:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24920;
	Mon, 23 Jan 95 19:12:52 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03700;
	Mon, 23 Jan 95 19:12:49 -0800
Date: Mon, 23 Jan 1995 19:12:49 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Jack Valko <valko@cyberspace.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Need to secure pine
In-Reply-To: <3g1e2s$5sk@case.cyberspace.com>
Message-Id: <Pine.ULT.3.92.950123191157.3526D-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Jack,
The fact that setting "no-enable-alternate-editor" in pine.conf.fixed 
fails to have the desired effect is a bug, and it will be fixed in 3.92.

-teg

On 23 Jan 1995, Jack Valko wrote:

> I would like to know if there is some way to set a configuration in pine 
> so that users can't change it from the Setup menu.  Specifically, I want 
> to restrict the alternate editor feature.  I have specified 
> 'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
> doesn't seem to do it.  Can anyone help?
> 
> ==================================================
> Jack Valko           |       - Cyberspace -
> System Administrator | 300 Queen Anne Ave. N. #396 
> cyberspace.com       |   Seattle, WA 98109-4599 
> cyberspace.net       |       (206) 281-5397 
> ==================================================
> 
> 


From owner-pine-info@cac.washington.edu  Mon Jan 23 19:50:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18120;
	Mon, 23 Jan 95 19:50:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24726;
	Mon, 23 Jan 95 19:45:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24720;
	Mon, 23 Jan 95 19:45:09 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWbxn-00038RC; Mon, 23 Jan 95 19:30 PST
To: pine-info@cac.washington.edu
From: lawrld@law.lawlib.emory.edu (Richard L. Doernberg)
Subject: Pcpine/keyboard freeze
Date: Mon, 23 Jan 1995 22:22:15 +1000
Message-Id: <lawrld.12.00168042@law.emory.edu>

Has anybody had any trouble with the keyboard freezing while using pcpine with 
trumpet winsock? This happens to me regularly, but when it does, the mouse 
works fine.

Any ideas?
Richard L. Doernberg
Emory University School of Law
Atlanta, GA 30322
Phone: 404 727 6836
Fax:   404 727 6850
Email: lawrld@law.emory.edu


From owner-pine-info@cac.washington.edu  Mon Jan 23 20:39:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19308;
	Mon, 23 Jan 95 20:39:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26149;
	Mon, 23 Jan 95 20:34:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26143;
	Mon, 23 Jan 95 20:34:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWclO-00038RC; Mon, 23 Jan 95 20:21 PST
To: pine-info@cac.washington.edu
From: "Mark E. Crane" <psu01055@odin.cc.pdx.edu>
Subject: Re: Filtering in Pine?
Date: Mon, 23 Jan 1995 19:45:21 -0800
Message-Id: <Pine.PTX.3.91.950123194405.1443D-100000@odin.cc.pdx.edu>
References: <3fgc5a$kh@sun0.urz.uni-heidelberg.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fgc5a$kh@sun0.urz.uni-heidelberg.de> 

You can filter mail with a separate program, like procmail or filter, 
which may be onn your machine.  Look around for Nancy McGough's excellent 
filtering faq.  I only have a print copy, but it is at her WWW site, 
which you can get from her signature.


On 17 Jan 1995, Nina Kirchner wrote:

> Hello,
> 1. I don't know if it's FAQ, but I'm interested to filter my mail messages in special Folder when I get one.
> 
> How does that work?
> 
> 2. Is it possible to send bcc (blind carbon copy) in pine?
> 
> Thanx alot 
> 
> Cheers Nina
> 
> 


Mark Crane
psu01055@odin.cc.pdx.edu



From owner-pine-info@cac.washington.edu  Mon Jan 23 21:25:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20648;
	Mon, 23 Jan 95 21:25:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26187;
	Mon, 23 Jan 95 21:19:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26177;
	Mon, 23 Jan 95 21:19:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWdPv-00038KC; Mon, 23 Jan 95 21:03 PST
To: pine-info@cac.washington.edu
From: vzvz@netcom.com (Philip Zeyliger)
Subject: Non-standard INBOX locations and pine
Message-Id: <vzvzD2w73C.1M9@netcom.com>
Date: Tue, 24 Jan 1995 04:28:24 GMT


Recently, I have been trying to setup Pine here at Netcom and have run
into a problem:

Some users are reporting that pine doesn't see their INBOX'es.
The inboxes are located at $HOME/.mailbox/inbox.
This is unlike the unix standard /usr/local/spool/mail/$USER (or whatever).
I searched through the makefile and could not see any reference to this.
I did not want to modify the source code since I might not change the right
things.  So I tried to make a general config file.

I made the file setting "inbox-path=" line to whatever I need.
Then i try to execute the following script:

---
#!/bin/sh
#
# Script to launch pine

exec /u3/vzvz/pub/pine/pine -P /u3/vzvz/pub/pine/pine.conf $*
	
---
This gives me the following:

{The pine main menu screen}
[Opening "INBOX"...]
Bug in Pine detected: "Received abort signal".
Exiting pine.

I don't understand why this wouldn't work.  Also if someone could help
with what source code I should change.  I am also interested in what
pine looks to to find INBOX.  So far, i have found that if we set
the $MAIL variable it works.  Even though the MAIL thing is OK I would
like to figure out something in the sense of getting a general config file.

Thanks for all your help! and a great product too!

-- 
   |\__      ----------------------------------------------------      __/| 
  /   o\__                                                          __/o   \
 |    ___='                      Philip Zeyliger                   `=___    |
 |    \                          vzvz@netcom.com                       /    |
  \    \                                                              /    /
   >    \                  ---------> KOHb <---------                /    <
 _| KOHb |_               on the Internet Chess Server             _|      |_
|  ______  |                telnet chess.lm.com 5000              |  ______  |
|__________| ==================================================== |__________|


From owner-pine-info@cac.washington.edu  Mon Jan 23 22:11:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21661;
	Mon, 23 Jan 95 22:11:07 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26768;
	Mon, 23 Jan 95 22:02:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26762;
	Mon, 23 Jan 95 22:02:25 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27613;
	Mon, 23 Jan 95 22:02:15 -0800
Date: Mon, 23 Jan 1995 22:02:14 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Philip Zeyliger <vzvz@netcom.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Non-standard INBOX locations and pine
In-Reply-To: <vzvzD2w73C.1M9@netcom.com>
Message-Id: <Pine.ULT.3.92.950123215458.3526M-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Philip,
You certainly should not need to modify source to change the inbox path!

I would suggest setting the inbox-path entry in /usr/local/lib/pine.conf to:

 inbox-path=.mailbox/inbox

or if you prefer the aesthetics of using $HOME, then use:

 inbox-path=${HOME}/.mailbox/inbox

(The squiggley brackets are needed to delimit the name of the env. var.)

I'm unclear on what you are trying to do in your script, or why it is 
needed in preference to the existing pine.conf facility...

-teg

On Tue, 24 Jan 1995, Philip Zeyliger wrote:

> 
> Recently, I have been trying to setup Pine here at Netcom and have run
> into a problem:
> 
> Some users are reporting that pine doesn't see their INBOX'es.
> The inboxes are located at $HOME/.mailbox/inbox.
> This is unlike the unix standard /usr/local/spool/mail/$USER (or whatever).
> I searched through the makefile and could not see any reference to this.
> I did not want to modify the source code since I might not change the right
> things.  So I tried to make a general config file.
> 
> I made the file setting "inbox-path=" line to whatever I need.
> Then i try to execute the following script:
> 
> ---
> #!/bin/sh
> #
> # Script to launch pine
> 
> exec /u3/vzvz/pub/pine/pine -P /u3/vzvz/pub/pine/pine.conf $*
> 	
> ---
> This gives me the following:
> 
> {The pine main menu screen}
> [Opening "INBOX"...]
> Bug in Pine detected: "Received abort signal".
> Exiting pine.
> 
> I don't understand why this wouldn't work.  Also if someone could help
> with what source code I should change.  I am also interested in what
> pine looks to to find INBOX.  So far, i have found that if we set
> the $MAIL variable it works.  Even though the MAIL thing is OK I would
> like to figure out something in the sense of getting a general config file.
> 
> Thanks for all your help! and a great product too!
> 
> -- 
>    |\__      ----------------------------------------------------      __/| 
>   /   o\__                                                          __/o   \
>  |    ___='                      Philip Zeyliger                   `=___    |
>  |    \                          vzvz@netcom.com                       /    |
>   \    \                                                              /    /
>    >    \                  ---------> KOHb <---------                /    <
>  _| KOHb |_               on the Internet Chess Server             _|      |_
> |  ______  |                telnet chess.lm.com 5000              |  ______  |
> |__________| ==================================================== |__________|
> 


From owner-pine-info@cac.washington.edu  Tue Jan 24 00:18:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24269;
	Tue, 24 Jan 95 00:18:20 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28587;
	Tue, 24 Jan 95 00:12:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28581;
	Tue, 24 Jan 95 00:12:16 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA05539; Tue, 24 Jan 1995 03:11:47 +0500
Date: Tue, 24 Jan 1995 03:11:46 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
In-Reply-To: <3g1cb0$dgd@nntp.crl.com>
Message-Id: <Pine.SOL.3.91.950124025500.5514A-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1616

On 23 Jan 1995, Lee (not F) Bailey wrote:

> What have I done to my pine program to make it hate me? I was toolin along
> just fine for weeks, then suddenly pine starts makeing these files in my
> $HOME. They are of the form pine-debug1, 2, ... 
>   
> How do I make it stop??? I have 'whereis'd everything I could find, but 
> nothing about these files.
 
Pine creates those ".pine-debug..." files automatically each time it is 
used.  The most recent is always .pine-debug1, the one previous to that 
.pine-debug2, and so on up to .pine-debug4.  Obviously each time a new 
.pine-debug1 is created, the old 1, 2, & 3 are renamed 2, 3, & 4 and the 
old 4 is deleted.
 
You can suppress the creation of a .pine-debug file by using "pine -d 0"
to start Pine, instead of just "pine", but why bother?  Those files don't
take up much space and can be a useful diagnostic tool if Pine does
something stupid. 
 
I had something strange happen a couple of times back when Pine 3.89 was
the latest and greatest, where the number of .pine-debug files grew to
well over the limit of four.  That was a long time ago and I don't
remember what the total grew to, but it was a lot.  This was supposedly
impossible, but there they were in my home directory.  Anyone else ever
see this?  It hasn't happened to me with 3.90 or 3.91. 

--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA




From owner-pine-info@cac.washington.edu  Tue Jan 24 02:18:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27295;
	Tue, 24 Jan 95 02:18:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00319;
	Tue, 24 Jan 95 02:09:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.Germany.EU.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00309;
	Tue, 24 Jan 95 02:09:32 -0800
Received: by mail.Germany.EU.net with UUCP (8.6.5:29/EUnetD-2.5.1.c) via EUnet
	id LAA07791; Tue, 24 Jan 1995 11:11:05 +0100
Received: from sun51.fz.telekom.de (sun51.fz.telekom.de [192.166.56.95]) by eunetgate.fz.telekom.de (8.6.5/8.6.5) with SMTP id KAA01661; Tue, 24 Jan 1995 10:52:05 +0100
Received: from magnum.fz.telekom.de by sun51.fz.telekom.de (4.1/SMI-4.1)
	id AA12790; Tue, 24 Jan 95 10:54:23 +0100
Date: Tue, 24 Jan 1995 10:52:32 -0100 (MET)
From: Tobias Pluemer <pluemer@fz.telekom.de>
Reply-To: pluemer@fz.telekom.de
To: Pine Developers <pine-bugs@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Bug (ID VF0FQ): 
X-Sender: pluemer@sun51-lan51.fz.telekom.de
Message-Id: <Pine.PCW.3.91.950124104355.12607L-100000@magnum.fz.telekom.de> 
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-23621000-3422--1294943920=:302526783"
Content-Id: <Pine.PCW.3.91.950124105132.12607N@magnum.fz.telekom.de>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---23621000-3422--1294943920=:302526783
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.PCW.3.91.950124105132.12607O@magnum.fz.telekom.de>

Dear Pine Developers,

I have found a bug in PCPINE for Windows (3.91).

When I include a file via CTRL-R and just type the filename (i.e. without 
CTRL-T to get the browser) the CTRL key seems to be locked, but only for 
the SPACE key. 
this meens:
all keys work as they should, but hitting SPACE the function CTRL-SPACE 
is performed. executing any CTRL-... function or just hitting CTRL stops 
this behavior. 



----------------------------------------------------------------------------
Tobias Pluemer                                 Email: pluemer@fz.telekom.de
Deutsche Telekom AG FTZ                        Deutsche Telekom AG FTZ
Forschungs- und Technologiezentrum             Research Center
Am Kavalleriesand 3 (Postfach 10 00 03)        PO Box: 10 00 03
64276 Darmstadt                                D-64276 Darmstadt
Tel: 06151/83-5545                             Tel: +49 6151 83 5545
FAX: 06151/83-4066                             FAX: +49 6151 83 4066

---23621000-3422--1294943920=:302526783--


From owner-pine-info@cac.washington.edu  Tue Jan 24 03:50:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29374;
	Tue, 24 Jan 95 03:50:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02112;
	Tue, 24 Jan 95 03:45:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02106;
	Tue, 24 Jan 95 03:45:32 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWjSk-00038MC; Tue, 24 Jan 95 03:31 PST
To: pine-info@cac.washington.edu
From: tecnic@tlti.tokem.fi (PeTrI pIeTiKaInEn)
Subject: Mailing list with Pine?
Date: 24 Jan 1995 10:45:39 GMT
Message-Id: <3g2loj$ch3@tethys.otol.fi>

I was wondering is it possible to create a mailing list with Pine, where 
everyone in the list can mail? I mean I created a list for our demo group 
with address books command S CreateList... but I don't know how other 
members could mail into it?

We have Pine v.3.87 

I hope someone could help us? Thanks in advance

--

Jay FX - member of BlacKOuT and Bitch Control  	: Be merry
email:	tecnic@tlti.tokem.fi			:    Be bright...
IRC:	JayFx					: - Carbon D


From owner-pine-info@cac.washington.edu  Tue Jan 24 04:37:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01422;
	Tue, 24 Jan 95 04:37:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02195;
	Tue, 24 Jan 95 04:22:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02189;
	Tue, 24 Jan 95 04:22:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWk6C-00038eC; Tue, 24 Jan 95 04:11 PST
To: pine-info@cac.washington.edu
From: md2jakob@mdstud.chalmers.se (Jakob Schlyter)
Subject: Take addr to dist list?
Date: 24 Jan 1995 11:32:51 GMT
Message-Id: <3g2oh3$d5b@nyheter.chalmers.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Is it possible to do a TakeAddr but add the address to a distribution
list instead? If not, this would be a nice function to add (3.92?).

/Jakob

-- 
Email:      jakob@cs.chalmers.se
Snailmail:  Jakob Schlyter, Ejdergatan 5, S-416 68 Gothenburg
Phone:      +46-31-707 08 36, +46-70-595 07 94, +46-74-010 86 31
URL:        http://www.mdstud.chalmers.se/~md2jakob/


From owner-pine-info@cac.washington.edu  Tue Jan 24 05:00:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01989;
	Tue, 24 Jan 95 05:00:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03171;
	Tue, 24 Jan 95 04:42:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03165;
	Tue, 24 Jan 95 04:42:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWkOO-00038RC; Tue, 24 Jan 95 04:30 PST
To: pine-info@cac.washington.edu
From: walterc@eccomp.icu.eushc.org (Walter C. Cooksey)
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 1995 12:23:47 GMT
Message-Id: <3g2rgj$h9h@moe.cc.emory.edu>
References: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu>

I find the easies thing to do is assume that it has been read within a
reasonable time after delivery -- just like paper inter-office mail.
I hold them responsible and act accordingly.  It would be a nice safety
feature (for them) if I knew it had/had not been read, but they are
responsible.  It will happen as it seems to be a feature in most pc email
systems.  I'd certainly rather bet my job on email than US Mail.





From owner-pine-info@cac.washington.edu  Tue Jan 24 05:08:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02283;
	Tue, 24 Jan 95 05:08:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02653;
	Tue, 24 Jan 95 04:55:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02647;
	Tue, 24 Jan 95 04:55:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWkXm-00038cC; Tue, 24 Jan 95 04:40 PST
To: pine-info@cac.washington.edu
From: Paul Everitt <paul@cminds.com>
Subject: IMAP in this week's Communications Week
Date: 24 Jan 1995 12:07:59 GMT
Message-Id: <3g2qiv$gf8@terminator.ncts.navy.mil>


Reading this week's (or last, I'm not sure) _Communications Week_
magazine, I nearly fell out of my chair when I saw an article
on IMAP.  Pretty succinct in content.

--Paul


From owner-pine-info@cac.washington.edu  Tue Jan 24 08:12:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06721;
	Tue, 24 Jan 95 08:12:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05893;
	Tue, 24 Jan 95 07:59:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05886;
	Tue, 24 Jan 95 07:59:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWnQ5-00038QC; Tue, 24 Jan 95 07:44 PST
To: pine-info@cac.washington.edu
From: offsite@crl.com (Lee (not F) Bailey)
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: 24 Jan 1995 15:34:15 GMT
Message-Id: <3g36ln$aua@nntp.crl.com>
References: <3g1cb0$dgd@nntp.crl.com> <Pine.SOL.3.91.950124025500.5514A-100000@mail>

Chip Old (fold@mail.bcpl.lib.md.us) wrote:
> On 23 Jan 1995, Lee (not F) Bailey wrote:

> > [snip]  
>  
> Pine creates those ".pine-debug..." files automatically each time it is 
> used.  The most recent is always .pine-debug1, the one previous to that 
> .pine-debug2, and so on up to .pine-debug4.  Obviously each time a new 
> .pine-debug1 is created, the old 1, 2, & 3 are renamed 2, 3, & 4 and the 
> old 4 is deleted.
>  
> You can suppress the creation of a .pine-debug file by using "pine -d 0"
> to start Pine, instead of just "pine", but why bother?  Those files don't
> take up much space and can be a useful diagnostic tool if Pine does
> something stupid. 
>  
> I had something strange happen a couple of times back when Pine 3.89 was
> the latest and greatest, where the number of .pine-debug files grew to
> well over the limit of four.  That was a long time ago and I don't
> remember what the total grew to, but it was a lot.  This was supposedly
> impossible, but there they were in my home directory.  Anyone else ever
> see this?  It hasn't happened to me with 3.90 or 3.91. 

I admit these files could be useful, but they clutter up my dir listing. 
Is there a way to redirect them to a folder?

--
______________________________________________________________________________
Lee Bailey	|  E-Mail:   offsite@crl.com
	User of Geoworks Ensemble instead of M$ Windoze
	Try the demo at ftp://arginine.umdnj.edu/pub/geos/publish
		     or ftp://ftp.mcs.com/mcsnet.users/jbarr/GeoPublish	


From owner-pine-info@cac.washington.edu  Tue Jan 24 09:18:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10745;
	Tue, 24 Jan 95 09:18:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07701;
	Tue, 24 Jan 95 09:09:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07695;
	Tue, 24 Jan 95 09:09:05 -0800
Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13282;
	Tue, 24 Jan 95 09:08:47 -0800
Date: Tue, 24 Jan 1995 09:08:45 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Paul Everitt <paul@cminds.com>
Cc: pine-info@cac.washington.edu
Subject: Re: IMAP in this week's Communications Week
In-Reply-To: <3g2qiv$gf8@terminator.ncts.navy.mil>
Message-Id: <Pine.ULT.3.92.950124090123.17268C-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 24 Jan 1995, Paul Everitt wrote:

> Reading this week's (or last, I'm not sure) _Communications Week_
> magazine, I nearly fell out of my chair when I saw an article
> on IMAP.  Pretty succinct in content.
 
Succinct, but not necessarily accurate.  Examples: it's "Internet
*Message* Access Protocol", it was originally developed at Stanford,
and it's not just for Unix servers...

I also disagree with her conclusion that it will have more impact on Unix
users than LAN-based users, even though that is certainly true today. 

Still, it's nice to see that one of the best kept secrets in the email 
world is finally getting some press coverage.

-teg

p.s. it's in the Jan 9th issue, page 11.


From owner-pine-info@cac.washington.edu  Tue Jan 24 09:52:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12240;
	Tue, 24 Jan 95 09:52:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08344;
	Tue, 24 Jan 95 09:34:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08338;
	Tue, 24 Jan 95 09:34:21 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa19802;
          24 Jan 95 10:21 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA23296; Tue, 24 Jan 1995 17:36:17 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id MAA13248; Tue, 24 Jan 1995 12:33:20 -0500
Date: Tue, 24 Jan 1995 12:33:20 -0500 (EST)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Pine Info <pine-info@cac.washington.edu>
Subject: Return Receipt
Message-Id: <Pine.LNX.3.91.950124123230.13238B-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: QUOTED-PRINTABLE


I just thought I would ask my =A30.02 worth (about $0.015 to you Americans =
:-)

I think that return recpeipts in PINE would be bad for a couple of reasons:

1)  This is a quote from the O'Reilly & Associates sendmail book (pg 583)

    The Return-Receipt-To: header should never be declared in the=20
    configuration file, and, in fact, should rarely be used at all.  It
    is not intended as a routine delivery-verification mechanism, but=20
    rather is intended for occasional use in debugging delivery problems.
    It is escpecially dangerous when used in outgoing mailing-list mail,
    because it can cause an avalanche of returned mail, and can possibly
    bring a host to its knees.

As can be seen, the sendmail gurus think that it is a bad idea and they=20
know a thing or two about email !

2) The second problem with return receipt is that a MTA receiving email
will (possibly) automatically send the receipt *without* any user
intervention.  As a there are people in Europe who actually pay for
international email traffic, this function could cost them a lot of money=
=20
which they may not necessarily know about until they get the bill (this=20
obviously depends on how the billing is done)

Just to throw a spanner in the works, however, there is an Internet draft=
=20
called draft-ietf-notary-mime-delivery-04.txt which is titled "An=20
Extensible Message Format for Delivery Status Notifications".  Again=20
quoting from the abstract of the draft:

    This memo defines a MIME content-type that may be used by a message=20
    transfer agent (MTA) or electronic mail gateway to report the result
    of an attempt to deliver a message to one or more recipients.

This draft also highlights some security risks with return receipt=20
messages (such as false headers and confidentionality for instance). =20
This is well worth a read and can be ftp'd from ns.internic.net amongst=20
other places. =20

Stuart

#include <standard_disclaimers>

----
Stuart Tares=09=09=09Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst=09=09Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region




From owner-pine-info@cac.washington.edu  Tue Jan 24 11:14:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15813;
	Tue, 24 Jan 95 11:14:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09822;
	Tue, 24 Jan 95 11:04:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09816;
	Tue, 24 Jan 95 11:04:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWqIK-00038CC; Tue, 24 Jan 95 10:48 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Need to secure pine
Date: Tue, 24 Jan 1995 17:35:17 +0000
Message-Id: <Pine.SUN.3.91.950124173442.24402T-100000@apus.cus.cam.ac.uk>
References: <3g1e2s$5sk@case.cyberspace.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g1e2s$5sk@case.cyberspace.com> 

On 23 Jan 1995, Jack Valko wrote:

> I would like to know if there is some way to set a configuration in pine 
> so that users can't change it from the Setup menu.  Specifically, I want 
> to restrict the alternate editor feature.  I have specified 
> 'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
> doesn't seem to do it.  Can anyone help?
> 
We have the following set in pine.conf.fixed, and it seems to do the job:-

no-enable-alternate-editor-cmd,
no-always-use-alt-editor,
no-enable-alternate-editor-implicitly,


=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Tue Jan 24 15:33:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29478;
	Tue, 24 Jan 95 15:33:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16243;
	Tue, 24 Jan 95 15:26:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16237;
	Tue, 24 Jan 95 15:26:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWqcd-00038CC; Tue, 24 Jan 95 11:09 PST
To: pine-info@cac.washington.edu
From: entropy@IntNet.net (Jonathan Cooper)
Subject: [ killfile ]
Date: 8 Jan 1995 23:14:25 -0500
Message-Id: <3eqd71$hgt@xcalibur.IntNet.net>

How would I kill all mail that comes from a certain address using
pine itself?  Does pine support killfiles?

Yes, I know I could just make a procmail recipe, but I'd like to
use just pine.

-jon
-- 
( --------[ Jonathan D. Cooper ]--------[ entropy@intnet.net ]-------- )
( PGP 2.6.2 keyprint: 31 50 8F 82 B9 79 ED C4  5B 12 A0 35 E0 9B C0 01 )
( home page: http://taz.hyperreal.com/~entropy/ ]---[ Key-ID: 4082CCB5 )


From owner-pine-info@cac.washington.edu  Tue Jan 24 15:58:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00799;
	Tue, 24 Jan 95 15:58:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18130;
	Tue, 24 Jan 95 15:52:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18124;
	Tue, 24 Jan 95 15:52:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWuqX-00038KC; Tue, 24 Jan 95 15:40 PST
To: pine-info@cac.washington.edu
From: pjh@mccc.edu (Pete Holsberg)
Subject: Re: Script as printer command ???
Message-Id: <D2x8x1.57w@mccc.edu>
Date: Tue, 24 Jan 1995 18:05:24 GMT
References: <D2CwB4.498@tecoma.mccc.edu> <Pine.SUN.3.91.950115170653.22858A-100000@linda.teleport.com>

Knute Snortum (knute@teleport.com) wrote:

: On Fri, 13 Jan 1995, Pete Holsberg wrote:

: > I would like to use the following script as my printer command,
: > with <???> representing the name of the current email message.
: > How do I specify the name???
: > 
: > cat <????> | jetpr -h <???> | lp -dlj
: > 

: I'm no expert, but I don't think you need the file name at all.  In fact, 
: I would try just:

:   jetpr -h | lpr -dlj

: and see what happens.

"jetpr | lp -dlj" (without quotes) worked.


From owner-pine-info@cac.washington.edu  Tue Jan 24 16:15:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01803;
	Tue, 24 Jan 95 16:15:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17356;
	Tue, 24 Jan 95 16:10:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17345;
	Tue, 24 Jan 95 16:10:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWv6v-00038KC; Tue, 24 Jan 95 15:57 PST
To: pine-info@cac.washington.edu
From: pjh@mccc.edu (Pete Holsberg)
Subject: Re: Need HELP! BinHEX conversion?
Message-Id: <D2x9pI.5KE@mccc.edu>
Date: Tue, 24 Jan 1995 18:22:30 GMT
References: <3fmv6r$86n@kaiwan009.kaiwan.com> <Pine.A32.3.91.950120100755.27547B-100000@rzserv2.fh-lueneburg.de>

Ralf Matthies (matthies@rzserv2.fh-lueneburg.de) wrote:
: On 19 Jan 1995, Richard Hsiung wrote:

: > I got a mail from someone with an attachment (supposedly), well, in the 
: > message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
: > BinHex and how do I get this attachment back into file form?

: you will find BinHex on the following aFTP servers:

:               ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip
:               micros.hensa.ac.uk  /mirrors/simtel/msdos/mac/binhex13.zip

: PS: Ask me, if you have more questions... ;-)


OK. Where is BINHEX for Unix?





From owner-pine-info@cac.washington.edu  Tue Jan 24 16:23:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02384;
	Tue, 24 Jan 95 16:23:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18650;
	Tue, 24 Jan 95 16:15:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18642;
	Tue, 24 Jan 95 16:15:02 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWvDP-00038PC; Tue, 24 Jan 95 16:04 PST
To: pine-info@cac.washington.edu
From: hobbs@uofport.edu (Eric A. Hobbs)
Subject: Pine Bug?
Date: 24 Jan 1995 10:29:10 -0800
Message-Id: <3g3gtm$g9e@wally.uofport.edu>

I don't know if this is in the documentation or in a FAQ, but I've found 
a way to crash Pine (I've tried v3.89 and v3.91).

A few users and I were able to crash Pine by simply changing the 
capitalization of the first letter of an address book nickname.  We're 
running SunOS 4.1.3_U1 and 4.1.4.  

Is this a documented thing? 

--Eric Hobbs

-- 
------------------------------------------------------------------------------
  Eric A. Hobbs          (hobbs@uofport.edu)    - -- ---=- -===-====(-: 
  UNIX System Manager,   University of Portland      :-o===-==--=--- -- - 
------------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Tue Jan 24 16:36:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03020;
	Tue, 24 Jan 95 16:36:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17531;
	Tue, 24 Jan 95 16:15:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17517;
	Tue, 24 Jan 95 16:15:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWvE7-00038QC; Tue, 24 Jan 95 16:04 PST
To: pine-info@cac.washington.edu
From: pdv2363@cactus.egr.uh.edu (Phu Vu)
Subject: Re: Signature and Finger FAQ
Date: 24 Jan 1995 18:30:17 GMT
Message-Id: <3g3gvp$ip5@masala.cc.uh.edu>
References: <3cqchl$3uj@news.halcyon.com>

In article <3cqchl$3uj@news.halcyon.com> Nancy McGough <nancym@ii.com>  
writes:
> Archive-name: signature_finger_faq
> Posting-frequency: approximately monthly
> Last-modified: 15 December 1994
> 
> Current-versions-at: 
>  
http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/fa 
q.html
> ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq
> 
> 
>             _____________________________________________________
>   _________|                                                      
|_________
>   \        |   SIGNATURE AND FINGER FREQUENTLY ASKED QUESTIONS   |         
/
>    \       |            Telling the World Who You Are            |        
/
>     \      |                                                     |       
/
>      \     |                                                     |     /
>      /     |           Copyright (c) 1994 Nancy McGough          |     \
>     /      |                                                     |       
\
>    /       |_____________________________________________________|        
\
>   /____________)                                               
(___________\
> 
> 
> 
>   TABLE OF CONTENTS
> 
>   0.0 Preliminaries
>   ... 0.1 Reading the Hypertext Version
>   ... 0.2 Reading the Plain Text Version (Digest Format)
>   ... 0.3 Notation
>   ... 0.4 Terminology
>   1.0 Automatic Signature - Basic Unix Instructions
>   ... 1.1 Pine
>   ... ... 1.1.1 Pine 3.90 and Later
>   ... ... 1.1.2 Pine 3.89 and Earlier
>   ... 1.2 Elm
>   ... 1.3 Mail
>   ... 1.4 SUN OpenWindows Mailtool
>   ... 1.5 Emacs Mail Mode
>   ... 1.6 MH and Emacs mh-e
>   ... 1.7 NN
>   ... 1.8 GNUS
>   ... 1.9 Troubleshooting Signature Problems
>   2.0 Finger - Basic Unix Instructions
>   ... 2.1 URLs for Fingering
>   ... 2.2 Changing Your Default Finger Info: chfn
>   ... 2.3 Adding More to Your Finger Info: .plan & .project
>   ... 2.4 Test Fingering Yourself
>   ... 2.5 Finding Out Who Fingers You
>   ... 2.6 Backfinger Script
>   ... 2.7 Interesting Places to Finger
>   3.0 What to Put in Your Signature and Finger Files
>   ... 3.1 URLs
>   ... 3.2 Ascii Art
>   ... 3.3 Animated Text Strings
>   ... 3.4 Robot Fodder
>   ... 3.5 Newsgroups for Sig Discussion
>   4.0 Organization Header
>   ... 4.1 Tin and the RN Family
>   ... 4.2 Pine 3.90 and Later
>   ... 4.3 Elm
>   ... 4.4 NN
>   5.0 Contributors
>   ... 5.1 Acknowledgements
>   ... 5.2 If You'd Like to Contribute
>   6.0 Copyright Notice
> 
> ----------------------------------------------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 0.0 Preliminaries
> 
> This article describes these ways you can tell people on the Internet  
more 
> about yourself:
>  * Your signature file which is automatically included in your mail and 
>    news messages.
>  * Your finger information which is displayed when people finger you.
>  * Your Organization line which is one of the headers in your mail and  
news 
>    messages.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 0.1 Reading the Hypertext Version
> 
> The best way to read this FAQ (and most other FAQs too) is to view the
> hypertext version using a Web browser such as Lynx, Netscape, Mosaic,
> WinWeb, Panda, Tapestry, or Cello.  This will allow you to easily jump:
> 
>    * between subjects in this article
>    * to a Uniform Resource Locator (URL)
>    * to an Internet Request For Comments document (RFC)
>    * to some manual pages
> 
> This and all FAQs that are crossposted to news.answers can be accessed  
through:
> http://www.cis.ohio-state.edu/hypertext/faq/usenet/top.html
> 
> This particular FAQ is at:
>  
http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/fa 
q.html
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 0.2 Reading the Plain Text Version (Digest Format)
> 
> If you are reading the plain text version (i.e., not the hypertext  
version) of 
> this FAQ it is in RFC1153 digest format which means each subject is  
formatted 
> as a mini mail message with its own Date, From, and Subject (and  
sometimes 
> Followup-To) headers.  Some newsreaders and mailers make it really easy
> to jump to a subject in an article that is in digest format.  Here are 
> instruction for some newsreaders:
> 
> * NN's default is to split a digest and present each digest item on the 
>   menu.  If you have changed the default by putting ``set split off'' in 
>   your ~/.nn/init file then you can split an article that is in digest 
>   format by typing G% while viewing it.  This will present each digest  
item 
>   on a submenu.  You can then read, followup-to, save, print, etc.  
individual 
>   digest items.
> 
> * In trn (and its relatives like rn and strn) you can type ^g to skip to 
>   the next line that begins with ``Subject: ''
> 
> * In emacs GNUS, C-c C-n will skip to the next digest article (C-C C-p  
will
>   go back to the previous digest article).
> 
> 
> If your newsreader or mailer does not have a built-in command that  
allows
> you to easily read a digest you can pipe the article to ``formail -ds''
> which will split the article into separate mail messages, and then you  
can
> use your mailer or newsreader (if it can read mail folders) to read the
> folder.  For more information on using formail, see the formail(1) and 
> procmail(1) man pages, and the Procmail FAQ:
>   
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.h 
tml
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 0.3 Notation
> 
> Notation  Meaning
> ========  =======
> TextName  placeholder; replace with appropriate text
> <text>    placeholder; replace with appropriate text without the angle  
brackets
> ``text''  text you type but without the quotes
> "text"    text you type including the double quotes
> 'text'    text you type including the single quotes
> [Key]     press the key, e.g., [Space] or [Enter]
> 
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 0.4 Terminology
> 
>   Term    Meaning
>   ====    =======
>   FTP     File Transfer Protocol
>   FQDN    Full Qualified Domain Name
>   HTML    HyperText Markup Language
>   HTTP    HyperText Transport Protocol
>   mailer  Mail user agent (MUA) such as Pine or Elm
>   pico    PIne COmposer - friendly editor that's part of the Pine  
package
>   RFC     Internet ``Request For Comments'' document
>   URL     Uniform Resource Locator (specified in RFC1630)
>   ^x      Press the Ctrl key and then, while holding down the Ctrl key,
>           press the x key
>   ~       Your home directory $HOME  (see * below)
> 
> * In this article I use ~ (tilde) to mean your home directory.  Note  
that
>   some shells, such as the Bourne shell (sh), do not understand the  
tilde
>   notation so you will need to use $HOME instead.  You can always get to
>   your home directory by typing ``cd''.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 1.0 Automatic Signature - Basic Unix Instructions
> 
> Q: How can I have a signature automatically appended to my news articles
>    and mail messages?
> 
> A: The answer depends on your newsreader and mailer but the following
>    procedure works for many Unix newsreaders and mailers.
> 
> 
> Type...                 In order to...
> =======                 ==============
> cd                      Change to your home directory (i.e., $HOME or ~)
> 
> pico .signature         Use the pico editor to create a .signature file.
>                         (Replace "pico" with another editor if you  
like.)
> 
> <your signature>        Note that most systems require your sig to be <=  
4
>                         lines.  And it's good netiquette to make it as
>                         short as possible.
> 
> <save and exit>         In Pico use ^x to exit and answer y when asked
>                         if you want to save your changes.
> 
> chmod 644 .signature    Make .signature readable by all.
> 
> ls -l .signature        Check the permission: it should say -rw-r--r--
> 
> chmod a+x .             Make home directory searchable by all.
> 
> ls -ld .                Check permission of home dir: it should say  
drwx?-x?-x
>                         The ?'s may be r's or hyphens or one of each  
(i.e.,
>                         drwx--x--x, drwxr-xr-x, drwxr-x--x, drwx--xr-x).
> 
> ls -la .                Check permission of files in home dir.  If any  
are
>                         group or other writable (?????w??w?) you may
>                         want to change this by doing a "chmod go-w  
FileName".
>                         Note that on some systems, such as VMS, some  
files 
>                         and directories in your home directory need to  
be 
>                         group or other writable, so only change  
permissions 
>                         if you know what you're doing.  For more info on 
>                         changing permissions see the chmod man pages.
> 
> For some newsreaders and mailers this is all you need to do to set up  
your
> signature.  For example the default behaviour of pine(1), tin(1), and  
the rn 
> family - rn(1), trn(1), strn(1), & Pnews(1) - is to automatically append 
>  ~/.signature, if it exists.  If you use Elm, Mail, SUN OpenWindows  
Mailtool,
> Emacs Mail Mode, MH, NN, or GNUS follow the additional instructions  
described 
> below.
> 
> After you've set everything up use your mailer to mail a test message
> to yourself, and your newsreader and/or news poster (such as nnpost or  
Pnews)
> to post an article to a test newsgroup (use a local newsgroup and  
Distribution
> set to ``local'' to save bandwidth).  Note that with many newsreaders  
and 
> mailers you will not see your signature while you are composing a  
message - 
> it will be automaticlally appended when you send the message.  Note also  
that 
> many systems add a line that contains ``-- '' to the top of your sig.   
This is 
> used by programs that automatically deal with mail or news to identify  
the 
> start of the signature.
> 
> If you have a problem with your sig see section 1.9 on Troubleshooting.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 1.1 Pine
> Followup-To: comp.mail.pine
> 
> Pine automatically appends ~/.signature (if it exists) to your messages.  
> Many people like to set the signature-at-bottom variable which will put 
> your signature below both your message and the message you are replying 
> to (if you've included it).  Note that if you are forwarding a message 
> your signature will be put below the message that you write but above 
> the forwarded message.
> 
> SEE ALSO
> ========
> Pine FAQ:       http://www.cac.washington.edu/pine/faq/
>                 ftp://ftp.cac.washington.edu/pine/docs/faq
> Pine Manual:    pine(1)
> Pine Newsgroup: comp.mail.pine
> 
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... ... 1.1.1 Pine 3.90 and Later
> Followup-To: comp.mail.pine
> 
> Pine automatically appends ~/.signature (if it exists) to your messages.  
> To change Pine's signature features:
> 
> 1. From the Main Menu type s for Setup
> 2. Type c for Configuration
> 3. To change the value of the signature-at-bottom feature:
>    a) Spacebar and arrow down to the signature-at-bottom variable
>    b) Type x to set/unset this variable.
> 4. To change the name of your signature file:
>    a) Arrow down to the signature-file line
>    b) Type c for Change Value
>    c) Type the path and name of the file you want to use for your
>       signature.  Note that ~ can be used for your $HOME directory.
> 
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... ... 1.1.2 Pine 3.89 and Earlier
> Followup-To: comp.mail.pine
> 
> Pine automatically appends ~/.signature (if it exists) to your messages.  
> To change Pine's signature features in Pine 3.89 (and earlier versions)  
you 
> need to edit your ~/.pinerc file directly.
> 
> Type...                 In order to...
> =======                 ==============
> cd                      Change to your home directory (i.e., $HOME or ~)
> pico .pinerc            Use the pico editor to edit your .pinerc file.
> ^w                      Search for . . .
> feature-list            . . . ``feature-list''
> 
> 
> Edit your .pinerc so that it contains this line:
> 
> feature-list=signature-at-bottom
> 
> If you want more than one feature in your feature-list then they need to
> be comma separated like this:
> 
> feature-list=old-growth,
> 	signature-at-bottom
> 
> 
> If you want to use a file other than ~/.signature for your signature
> edit the following line:
> 
> signature-file=
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 1.2 Elm
> Followup-To: comp.mail.elm
> 
> In addition to the basic signature instructions in 1.0 above, users of  
Elm
> need to edit their ~/.elm/elmrc file so that it contains the following:
> 
> signature = ~/.signature
> sigdashes = ON
> 
> Remember to delete any # characters before any variables you want
> to set.  The defaults are indicated in comment lines starting with ###.
> 
> Note that if you want to have a different signature for local mail
> (i.e., addresses that don't contain a ! or @) then you can use the
> localsignature and remotesignature variables instead of the signature
> variable (which specifies one sig for all mail).
> 
> SEE ALSO
> ========
> Elm Web Page: http://www.myxa.com/elm.html
> Elm FAQs:      
http://www.cis.ohio-state.edu/hypertext/faq/usenet/elm/top.html
> Elm Manual:   elm(1)
> Newsgroup:    comp.mail.elm
> 
> ------------------------------
> 
> From: Jym Dyer <jym@remarque.berkeley.edu>
> Subject: ... 1.3 Mail
> Followup-To: comp.mail.misc
> 
> By Jym Dyer, 1 April 1994
> 
> =o= Regular Unix "Mail" and "mail" don't have an automatic
> signature mechanism.  Many people who normally use a more deluxe
> mail utility occasionally find themselves resorting to using one
> of these, in which case all you need to know is this command:
> 
> 	~r $HOME/.signature
> 
> This simply tells Mail to include the text of the your signature
> file.
> 
> =o= If you use Mail on a regular basis you may want to use the
> semi-automatic signature feature.  When you're done typing your
> message, you append a signature with this command:
> 
> 	~a
> 
> =o= In order for this to work, though, you need to set the
> "sign" mail variable.  There are two ways to implement this
> variable.  The first is to set it in a $HOME/.mailrc file with
> a command like this:
> 
> 	set sign="Jym Dyer <jym@remarque.berkeley.edu>"
> 
> If your signature is more than one line long, you can use the
> C language string syntax, as in these examples:
> 
> 	set sign="Jym Dyer\n<jym@remarque.berkeley.edu>"
> 
> 			-or-
> 
> 	set sign="Jym Dyer\
> 	\n<jym@remarque.berkeley.edu>"
> 
> =o= The disadvantage of doing this in your .mailrc file is
> that you now have to maintain the text of your signature in
> two places.  Another approach that avoids this problem is to set
> "sign" as an environment variable in your shell startup script.
> For a Bourne-compatible shell, this is done with this command:
> 
> 	sign="`cat $HOME/.signature`" export sign
> 
> For a C-shell, do this:
> 
> 	setenv sign "`cat $HOME/.signature`"
> 
> SEE ALSO
> ========
> Manual pages: mail(1)
> Newsgroup:    comp.mail.misc
> 
> ------------------------------
> 
> From: Jochen Bern <bern@uni-trier.de>
> Subject: ... 1.4 SUN OpenWindows Mailtool
> 
> By Jochen Bern, 7 November 1994
> 
> The mailtool of SUNs OpenWindows lacks numerous Things, including the
> Ability to sign Mails. However, most OW Users stick with mailtool
> because of the Ability to use "Attachments" to send around Files.
> 
> A simple Replacement for Signatures is to add a "Template" (click on
> Edit -> Properties, select Category "Template" in the Properties
> Window, and give Name and File as desired). Disadvantage: You have
> to edit in every Signature by Hand, though.
> 
> A better Approach is to use a "set sendmail=..." Line in your ~/.mailrc.
> Mails being sent out will be handed over to the Executable named
> there instead of the Mail Delivery Subsystem. You can easily plug
> in a simple Program to sign your Mails there. However, be warned that
> all too simple Siggers aren't aware of the abovementioned Attachments,
> so the Signature will end up in the last Attachment instead of the
> Mail Text. A Sigger doing this correctly can be found at
> file://ftp.informatik.uni-trier.de/pub/sunos/JoesMailtool/.
> 
> Note that this will cause the standard mail Command to use the Sigger,
> too.
> 
> ------------------------------
> 
> From: Jym Dyer <jym@remarque.berkeley.edu>
> Subject: ... 1.5 Emacs Mail Mode
> 
> By Jym Dyer, 1 April 1994
> 
> =o= Emacs Mail Mode is usually invoked with the "mail" or
> "mail-other-window" commands (bound, respectively, to the
> "C-x m" and "C-x 4 m" keys by default).  It is also invoked
> from various Emacs mail and news packages.
> 
> =o= Mail Mode provides a "mail-signature" command to append
> the contents of your signature file to the end of your mail
> message.  This command is bound to "C-c C-w" by default,
> so to insert the signature before mailing, simply type
> "C-c "C-w".
> 
> =o= If you'd prefer to have your signature automatically
> appended to the end of your mail message, the "mail-signature"
> command can be put into your "mail-setup-hook" variable in
> your $HOME/.emacs file, as in this example:
> 
>     (setq mail-setup-hook
>       (function
>        (lambda ()
> 	 (mail-signature) )))
> 
> This will put the signature in your mail message buffer.
> 
> 
> Instructions for Version 19 by Richard Kasperowski
> ==================================================
> In emacs 19, I use:
> 
>  (setq mail-signature t)
> 
> There is a problem with my expression with respect posting to USENET
> via GNUS.  GNUS automatically appends .signature to the post when it
> is sent out.  With (setq mail-signature t), .signature is appended to
> the end of the emacs buffer in which you edit your post.  When you
> send-out the post, another .signature is appended to the end.  You end
> up with two .signatures on your USENET posts.
> 
>    This will put the signature in your mail message buffer.
> 
> 
> SEE ALSO
> ========
> Newsgroups: gnus.emacs.help and comp.emacs
> FAQ: 
>  
http://www.cis.ohio-state.edu/hypertext/faq/usenet/GNU-Emacs-FAQ/part5/faq 
html
> 
> ------------------------------
> 
> From: Jym Dyer <jym@remarque.berkeley.edu>
> Subject: ... 1.6 MH and Emacs mh-e
> Followup-To: comp.mail.mh
> 
> By Jym Dyer, 1 April 1994
> 
> =o= MH doesn't have an automatic signature mechanism, but it
> is so configurable that there are a number of different ways
> to implement one.  Check the periodic "MH Frequently Asked
> Questions (FAQ) with Answers" posting for details.
> 
> =o= CAVEAT:  If you use the environment variable SIGNATURE to
> point to your signature file, MH will use it not as a signature,
> but as your "fullname".  Even worse, if your version of MH was
> built with the "UCI" option and you *don't* use the environment
> variable SIGNATURE to point to another file, MH will use the
> $HOME/.signature file for this purpose!  To see if your version
> of MH has this behavior, enter this command:
> 
>   % send -help
> 
> And look for the string "[UCI]" in the output.
> 
> =o= There's an Emacs interface to MH, called MH-E.  It has its
> own signature mechanism, which is invoked with the "mh-insert-
> signature" command (bound to the "C-c C-s" keys by default).
> 
> =o= This will insert the file $HOME/.signature file by default.
> If your signature file has another name (e.g., to avoid its
> being used by an MH build with the "UCI" option), you can set
> the "mh-signature-file-name" variable to refer to a different
> file.
> 
> SEE ALSO
> ========
> MH FAQ:        
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mh-faq/top.html
> MH Manual:    mh(1)
> MH Newsgroup: comp.mail.mh
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 1.7 NN
> Followup-To: news.software.nn
> 
> In addition to the basic signature instructions in 1.0 above, users of  
NN
> need to edit their ~/.nn/init file so that it contains the following:
> 
> set query-signature off
> set append-signature-mail on
> set append-signature-post off
> 
> Note that the reason that you need to ``set append-signature-post off''  
is
> that the news posting software (usually inews) automatically appends
>  ~/.signature if it exists.  If you ``set append-signature-post on''  
then
> both nn and inews append your sig and you'll send out two identical sigs
> every time.
> 
> SEE ALSO
> ========
> FAQ:        
http://www.cis.ohio-state.edu/hypertext/faq/usenet/nn-faq/top.html
> Manual:    nn(1), inews(1)
> Newsgroup: news.software.nn
> 
> ------------------------------
> 
> From: Mike Northam <mbn@greyskul.intel.com>
> Subject: ... 1.8 GNUS
> Followup-To: gnu.emacs.gnus
> 
> Copyright (c) 1994 Mike Northam
> 
> In addition to the basic signature instructions in 1.0 above, users of  
GNUS
> should verify that the value of the variable gnus-signature-file points  
to the
> right place.  If you're in emacs, you can do so by evaluating the  
following
> expression:
> gnus-signature-file
>                    ^ put your cursor here and type C-x C-e
> 
> you should see "~/.signature" in the echo area.  If not, edit your
> $HOME/.emacs file and add the following:
> (setq gnus-signature-file "~/.signature"))
> Then load your $HOME/.emacs file or merely restart emacs and the  
variable
> should be set correctly.
> 
> SEE ALSO
> ========
> Newsgroup: gnu.emacs.gnus
> FAQ: 
>  
http://www.cis.ohio-state.edu/hypertext/faq/usenet/GNU-Emacs-FAQ/part5/faq 
html    
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 1.9 Troubleshooting Signature Problems
> 
> A common problem people have with .signature (and .plan, .project, and
>  .forward ) files is that the permissions are not set correctly.  Check
> to make sure that you have set the permissions as instructed in 1.0  
above.
> 
> If you are still having problems read the man pages for your newsreader,
> news poster, or mailer and search for the string ``signature''.  There  
may 
> be a variable you need to set in order for the ~/.signature to be  
appended.
> 
> Type...                 In order to...
> -------                 --------------
> man CommandName |less   Open man pages for CommandName (elm, pine, nn,  
tin
>                         trn, Pnews, etc.) and pipe through less.  If  
your
>                         system doesn't have less replace it with "more".
> 
> /signature              Search for first occurrence of "signature".
> 
> n                       Search for next occurrence of "signature".
>                         Repeat the search until you find the appropriate
>                         section of the manual.
> 
> u                       Page up half a screen. (This works in less but  
not in
>                         more.)
> 
> [Space]                 Page down a screen. (This works in both less and  
more.)
> 
> 
> For more information on reading manual pages see the man(1), less(1),  
and/or
> more(1) man pages.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 2.0 Finger - Basic Unix Instructions
> 
> If your host is running the finger daemon (fingerd) then
> people around the world can find out more about you by fingering you.  
> This is done by typing the following at a Unix prompt:
> 
>    finger YourUserID@your.fully.qualified.domain.name
> 
> On some systems finger is linked to f so the following also works:
> 
>    f YourUserID@your.fqdn
> 
> 
> Finger displays different information on different systems.  Often it  
will 
> display your full name, your default shell, when your were last logged  
on, 
> and your ~/.plan and ~/.project files.
> 
> If you finger someone and the display takes more than one page you can  
pipe 
> the output through less (or more if you don't have less).  For example  
to 
> find out about Halcyon, my Internet service provider, type:
> 
>    finger info@halcyon.com |less
> 
> 
> Finger can also be used to display information about groups of people.
> For example:
> 
>    finger john@random.fqdn |less
> 
> Ths will display finger information about everyone with ``john'' in 
> their name on random.fqdn.  You can get a short listing for each person
> by using:
> 
>    finger -q john@random.fqdn |less
> 
> 
> For technical details about the finger protocol see RFC1288.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 2.1 URLs for Fingering
> 
> In addition to using the finger or f command you can finger people
> through a Web browser.  The following is a form that Doug Stevenson
> <doug+@osu.edu> created:
>   http://www.mps.ohio-state.edu/cgi-bin/finger.pl
> 
> Also, Marc VanHeyningen <mvanheyn@cs.indiana.edu> has a Web finger  
gateway
> at:
>  http://www.cs.indiana.edu/finger/fully.qualified.domain.name/userid/w
> 
> You can also use this URL:
>   gopher://fully.qualified.domain.name:79/0userid
>                                           ^ Note: 0 precedes the userid
> 
> For example you can finger my Internet service provider with this URL:
>   gopher://halcyon.com:79/0info
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 2.2 Changing Your Default Finger Info: chfn
> 
> On many Unix systems you can change some of your default information,
> such as your full name, by typing the following at your Unix prompt:
> 
>    chfn
> 
> If chfn is not available try "passwd -f".  If neither of these are
> available then you will need to contact your system administrator and
> ask him/her to change your full name, etc.
> 
> After you have changed your information check that they are in place
> by fingering yourself.  Also to see a different display of your
> information type the following at your Unix prompt:
> 
>    finger
> 
> This displays a one line description of everyone currently logged on
> your system.
> 
> For more information see the chfn(1), passwd(1), and finger(1) man  
pages.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 2.3 Adding More to Your Finger Info: .plan & .project
> 
> Your ~/.project and ~/.plan files, if they exist, are displayed when you
> are fingered.  Setting these up is essentially the same as setting
> up a ~/.signature file (described in 1.0 above).
> 
> Type...                 In order to...
> -------                 --------------
> cd                      Change to your home directory.
> 
> pico .plan              Use the pico editor to create a .plan file.
>                         (Replace "pico" with another editor if you  
like.)
> 
> chmod 644 .plan         Make .plan readable by all.
> 
> ls -l .plan             Check the permission: it should say -rw-r--r--
> 
> chmod a+x .             Make home directory searchable by all.
> 
> ls -ld .                Check permission of home dir: it should say  
drwx?-x?-x.
>                         The ?'s may be r's or hyphens or one of each.
> 
> ls -la .                Check permission of files in home dir.  If any  
are
>                         world or group writable (?????w??w?) you'll  
probably
>                         want to change this by doing a "chmod go-w  
FileName".
>                         For more info on changing permissions see chmod
>                         man pages.
> 
> 
> If you want a .project file follow the same procedure.  Note that only  
the
> first line of the .project is displayed (so you might as well only make
> it one line!).
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 2.4 Test Fingering Yourself
> 
> To test your changes finger yourself by type each of these at your
> Unix prompt:
> 
>     finger YourUserID
>     finger YourUserID@your.fqdn
>     finger
> 
> To ensure that people from other systems can finger you should ask  
someone 
> who's not on your system to finger you too.  It is possible for you to
> simulate fingering yourself from another machine (another.fqdn) by doing 
> this:
> 
>      finger YourUserID@your.fqdn@another.fqdn
> 
> In order for this to work another.fqdn must support full finger  
functionality.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 2.5 Finding Out Who Fingers You
> 
> This is complicated - and sometimes impossible - to setup.  For more
> information see:
> 
> * The next section of this FAQ on the Backfinger Script.
> 
> * Chris Alfeld's fingertrace: 
>      http://www.math.utah.edu/~calfeld/fingertrace/
> 
> * Unix - Frequently Asked Questions (4/7) [Frequent posting] 
>   4.9) How do I keep track of people who are fingering me? 
> 
>   This article is archived in all the usual FAQ archives, including:
>    
http://www.cis.ohio-state.edu/hypertext/faq/usenet/unix-faq/faq/part4/faq- 
doc-9.html
> 
> 
> An easy thing that you can do to see if anyone has fingered you is type  
the 
> following at your Unix prompt:
> 
>   ls -lu $HOME/.plan
> 
> This tells you the last time someone accessed your .plan, but it doesn't
> tell you who it was.  I have this in my .login because it's interesting  
to
> see when the last time someone was checking on me!
> 
> [Note that under AFS (Andrew File System, a distributed filesystem),
>  ls -lu $HOME/.plan will not work due to the fact that AFS has no 
>  notion of ``atime'', or ``last accessed time''.]
> 
> ------------------------------
> 
> From: Janet Rosenbaum <ejrosen@merle.acns.nwu.edu>
> Subject: ... 2.6 Backfinger Script
> 
> by Janet Rosenbaum
> 
> There is a script available called, among other things, backfinger,
> planner, and finger_logger (flogger or frogger, for short).  This script
> makes your plan into a named pipe (just think of this as a sort of
> pipe used with plumbing that opens out onto the screen of the person who
> is fingering you (fred)) so that when it is accessed, it looks for a
> program from which to get something to stick on fred's screen.
> 
> The script is called when you are fingered.  At that moment, it looks to
> the finger port of your unix machine and sees which machine fred is
> on, logs that machine's IP number and hostname, and the date.  The  
script
> can then execute a command to spit a plan out on fred's screen.  (One
> might get creative and write a program that generates random poetry or
> use the fortune program or just do "cat plan_file".)   To make fred
> think you are really cool, it also tells him what machine he is
> fingering you from.
> 
> Some caveats:
> 
> 	-- This program must be running at all times on your system even
> 	when you are logged out.  Leaving a background process like this
> 	annoys most sys admins to no end, especially on systems with
> 	high load.  Do **not** run the program unless you are sure that
> 	you are allowed to run background processes like this.
> 
> 	-- Also, if you decide you want to stop running this program,
> 	remove your .plan file as soon as you kill the process.  If you
> 	do not do this, all finger processes for you will hang.
> 
> 	-- This script only tells you the machine fred is fingering you
> 	from, not his actual username.  It is nearly impossible to get
> 	this information except at sites with bad security.
> 
> 
> Given the above, I will distribute the script to those who can use it,
> mostly for educational reasons.  I admit that I no longer run the
> program, since my two main accounts are on rather high-load systems.
> Nevertheless, I learned quite a lot from modifying these scripts and
> otherwise playing with these ideas.
> 
> Here is the web site:
> 
>  http://pubweb.acns.nwu.edu/~jrosen/scripts/logger.src
> 
> I will also try to post this answer and the program to comp.sources.misc
> at least monthly for those without web access.  (For those who have not
> figured out the web, try the program lynx if you are on a vt100 or vt220
> type terminal.  If you are on an xterm or hpterm, look for xmosaic.)
> 
> Note:  I am not the author of this program.  The version I distribute is
> virtually identical to that distributed by Steve Franklin.
> Here are the real authors:
> 
> Author: Tony Rems <rembo@unisoft.com>
> Modifications by Geoff Loker <geoff@mdms.moore.com>
> More modifications by Karen Bruner <napalm@ugcs.caltech.edu>
> Even more modifications by Norman Franke <franke1@llnl.gov>
> More revisions by Steve Franklin <franklin@ug.cs.dal.ca>
> Llamas and minor revision by The Blue One
> 
> Enjoy!
> 
> Janet
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 2.7 Interesting Places to Finger
> 
> Scott Yanoff's "Updated Internet Services List" contains a number of 
> interesting places to finger.  If you access it through the following  
URL 
> all the finger commands are links.
> 
>   http://www.uwm.edu/Mirror/inet.services.html
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 3.0 What to Put in Your Signature and Finger Files
> 
> It is good netiquette to keep your signature to four lines or fewer.   
And 
> many news posters, such as some versions of inews(1), will not post an 
> article that has a signature with more than four lines in it.  So, put  
large
> large pictures, your philosophy of life , etc. in your finger files or  
in 
> your Web pages and point people to those in your signature.
> 
> For signatures it's a good idea to keep the width less than 75  
characters
> so that if your signature is included in a followup preceded by an 
> attribution character (like ``> ''), each line will still be on one  
line.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 3.1 URLs
> 
> A good strategy is to keep your signature short and include an
> URL to your Web page, e.g.:
> 
>  <URL:http://www.jazzie.com/ii/>
>   
> 
> If you do not have a Web page you might want to put in an URL 
> that will finger you, e.g.:
> 
>  <URL:gopher://halcyon.com:79/0nancym>
> 
> 
> The format that I've used above, ``<URL:protocol://server:port/name>''
> is the current standard for URL specification.  To find out more about  
this
> standard, see:
> 
>  <URL:http://www.es.net/pub/internet-drafts/draft-ietf-uri-url-08.txt>
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 3.2 Ascii Art
> 
>                                       **
>     .             .                  *@@*      .                               
 
>                                     *@@@@*                      .
>           .                          /@@\
>                            .        //  \\         .
>                                    //    \\                                
 
>                                    //    \\                 .
>   .                              //  Meli  \\
>                 .               // Kalimaka \\    .                 .
>                                  //        \\                                 
 
>                                //            \\
>                               // Joyeux  Nokl \\        .
>        .               .     //  Bonne  Annie  \\
>                             / //              \\ \              .
>                              //                \\   .                          
 
>                             //   Buon Natale e  \\
> .            .             //  Felice Anno Nuovo \\
>                           /  //                \\  \       .           .
>                             //                  \\
>                      .     //   Merry Christmas  \\               .
>                           //    Happy New Year    \\      .                    
 
>       .                  / //                    \\ \
>                           //                      \\
>                  .       //  Frvehliche Weinachten \\              .
>                         // Alles Gute Zum Neuen Jahr\\                      
 
>  .                     /  //                      \\  \
>            .             //                        \\      .
>                         //                          \\
>                    .   //Chuc Mung Giang sinh Nam Moi\\
>     .                 / //                          \\ \           .          
 
>                        //                            \\
>                       //         Feliz Navidad        \\
>              .       //      y Prospero Aqo Nuevo      \\   .
>                     /  //                            \\  \
>                       //                              \\                 
 
> .                    //      Milad sa`id wa in sha     \\
>                     //        allah sana mubaraka       \\
>               .    //                                    \\      .        
 
>      .            //**************************************\\
>                  //              ************              \\                 
 
>                                  ************
>                                  **        **                    .
> .          .                     ************
>                                  ************      Art by Jean-Frangois  
Mezei
> 
> 
> A good source of art for your signature and finger files is the ascii  
art
> FAQ which contains (among others) these topics:
>    9  Where can I find ASCII art?
>   22  How do I put an animation in my plan?
>   23  How do I make a sig?
>   24  How do I have my sig automatically added to my posts and email?
> 
> The Ascii Art FAQ is at:  http://gagme.wwa.com/~boba/faq.html
> 
> One particularly good place to find ascii art is:
>   http://gagme.wwa.com/~boba/scarecrow.html
> 
> SEE ALSO
> ========
> Newsgroups: rec.arts.ascii, alt.ascii-art, alt.binaries.pictures.ascii
>             and alt.ascii-art.animation
> 
> ------------------------------
> 
> From: Marc Kriguer <kriguer@tcs.com>
> Subject: ... 3.3 Animated Text Strings
> 
> Dotplan is a program that performs "animation" effects on text
> strings, so that .plan files (hence the name) look a little more
> fancy (on low-speed dialup lines).  Some of the effects make the
> characters appear one at a time; others have the characters
> appear at once and "move" around.
> 
> EXAMPLES
>      dotplan 3 This is sample text # Display string using style 3
>      dotplan                       # Display usage information
>      dotplan s                     # Display styles in all styles
>      dotplan d This is more text   # Display string in all styles
>      dotplan 1 Hi there... > .plan # Save output in actual .plan file
> 
> 				-- Marc
> 
> The files are at:
>  ftp://ftp.halcyon.com/pub/ii/internet/dotplan.c
>  ftp://ftp.halcyon.com/pub/ii/internet/dotplan.1
> 
> ------------------------------
> 
> From: Tim Pierce <twpierce@midway.uchicago.edu>
> Subject: ... 3.4 Robot Fodder
> 
> Q: Tim, why do you and others put random, provocative words like
>    the following in your sig?
> 
>     -- 
>     Green Card fodder: Canter, Siegel, green card, Joel Furr, liable,
>     fortune, conspiracy, CyberSell, Tennessee Bar.
> 
> 
> A: The original genesis of this bit of lore was the NSA's
>    supposed archiving of Usenet.  It's a popular urban legend
>    that the NSA scans and archives every message posted to
>    Usenet, and in the heyday of this story it was popular to
>    add "spook fodder" to your .signature consisting of words
>    like "conspiracy, bullion, plutonium, Saudi Arabia,
>    president, assassination," and so on.  I think that the GNU
>    Emacs distribution still comes with the code that would
>    insert such words into your posts or .signatures
>    automatically.
>    
>    A couple of years ago there was a nut named Clayton Cramer
>    who would periodically bombard soc.motss with pages and
>    pages of pseudo-scientific babble about the evils of
>    homosexuality.  It got so tiring that after a while I
>    amended my .signature to read "Clayton-Fodder:
>    homosexuality, pedophilia, incest, guns, Second Amendment,
>    Libertarian, Reagan," or some such.  It got quite a few
>    giggles from some of the old hands out there.
>    
>    A more recent example was the case of "Serdar Argic," a
>    program written by a U of Minnesota student to search for
>    any article referencing Turkey or Turkish culture, and
>    follow up with several pages of invective about Armenian
>    genocide.  There were some reports that this program was
>    faulty and began responding to articles about "Thanksgiving
>    Turkey" and the like, but I don't recall ever seeing that
>    happen, myself.  Nevertheless, people started putting "Argic
>    fodder" into their .signatures, like "Turkey, Armenia, SDPA
>    crooks, genocide" in order to bait the "Argic-bot" into
>    following up.
>    
>    The latest rumor is that Canter and Siegel are archiving
>    every post which refers to them, in the hopes of finding
>    grounds for a libel suit.  Hence, my .signature (which only
>    goes to newsgroups in the news.* hierarchy).  It's a
>    ridiculous idea, but this is one of those bits of folklore
>    which I really enjoy perpetuating.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 3.5 Newsgroups for Sig Discussion
> 
> As discussed in 3.2 above there are a number of newsgroups for  
discussing
> ascii art.  There are also these newsgroups where people discuss  
signatures:
> 
> The War Lord of the West Preservation Fan Club:  alt.fan.warlord
> Like alt.fan.warlord, only different:  
alt.stupid.signature.flame.flame.flame 
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 4.0 Organization Header
> 
> The Organization header in news and mail messages is another way you can  
tell 
> people about yourself.  It is an optional header described in section
> 2.2.8 of RFC1036, "Standard for Interchange of Usenet Messages."
> 
> READING MESSAGES
> ================
> Many mailers and newsreaders do not automatically display the  
Organization
> header when you are reading a message you've received.  Often typing  
``h''
> (for header) will display all the headers of a message.  You can usually
> set up your software to automatically display the Organization line each
> time you view a messae.
> 
> COMPOSING MESSAGES
> ==================
> Below are instructions for automatically having your Organization line
> filled in each time you compose a message.  Some composers will 
> automatically display your Organization header while you are composing,
> and others won't.  
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 4.1 Tin and the RN Family
> Followup-To: news.newusers.questions
> 
> Tin and the rn family of tools (Pnews, rn, trn, strn) get information  
for the 
> Organization header from the ORGANIZATION environment variable if it  
exists.  
> In the csh or tcsh you can set this variable in your ~/.login with a  
line like 
> this:
> 
>   setenv ORGANIZATION "Your Organization Name"
> 
> After you edit your ~/.login you can establish the setting by either  
logging
> out and loggin back in or by typing the following at your Unix prompt:
> 
>   source ~/.login
> 
> To check that the variable is set type:
> 
>   printenv
> 
> After it is set, post a test message to a local test newsgroup with  
local
> distribution to check that the Organization header is correct.
> 
> SEE ALSO
> ========
> Manual Pages: tin(1), Pnews(1), rn(1), trn(1), strn(1)
> Newsgroup:    news.newusers.questions
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 4.2 Pine 3.90 and Later
> Followup-To: comp.mail.pine
> 
> In Pine 3.90, and later versions, you set the Organization and other  
headers 
> using the customized-hdrs variable.
> 
> 1. From the Main Menu type s for Setup
> 2. Type c for Configuration
> 3. To change the value of the customized-hdrs variable:
>    a) Space bar and arrow down to the customized-hdrs variable.
>    b) Type a for Add Value
>    c) At the prompt type: Organization: Your Organization Name
>       Note that if you have set the ORGANIZATION environment variable
>       (which is described in 4.1 above) you can type: 
>       Organization: $ORGANIZATION
> 
> While reading a message that you've received you can view the  
Organization
> header and all the other headers by typing h.  If h does not work you  
need 
> to go to your configuration menu and set the enable-full-header-cmd  
variable.
> 
> While composing a message you can view all the headers by placing the  
cursor
> in the header region and typing ^r (view rich headers).
> 
> NOTE: The customized-hdrs variable is not available in Pine 3.89 and  
below.
> 
> SEE ALSO
> ========
> Pine FAQ:       http://www.cac.washington.edu/pine/faq/
>                 ftp://ftp.cac.washington.edu/pine/docs/faq
> Pine Manual:    pine(1)
> Pine Newsgroup: comp.mail.pine
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 4.3 Elm
> Followup-To: comp.mail.elm
> 
> Use your editor to create a file named ~/.elm/elmheaders that contains
> any headers you'd like in your outgoing mail messages.  For example, my
>  ~/.elm/elmheaders file contains this one line:
> 
> Organization: Infinite Ink, Seattle, WA, USA
> 
> SEE ALSO
> ========
> Elm Web Page: http://www.myxa.com/elm.html
> Elm FAQs:      
http://www.cis.ohio-state.edu/hypertext/faq/usenet/elm/top.html
> Elm Manual:   elm(1)
> Newsgroup:    comp.mail.elm
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 4.4 NN
> Followup-To: news.software.nn
> 
> Use your editor to put the following lines in your ~/.nn/init file:
> 
> set news-header Organization: Your Organization Name
> set mail-header Organization: Your Organization Name
> 
> This will add the Organization header to both news and mail messages
> sent from NN.
> 
> While reading messages with NN you can view the Organization line
> by adding O (the letter "oh") to your header-lines variable setting.
> I like the following setting:
> 
> set header-lines AFOnWK*Y
> 
> SEE ALSO
> ========
> FAQ:        
http://www.cis.ohio-state.edu/hypertext/faq/usenet/nn-faq/top.html
> Manual:    nn(1)
> Newsgroup: news.software.nn
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 5.0 Contributors
> 
> This FAQ, like many others, is a collaborative effort.  I learned much
> of the information in newsgroups, especially:
>   comp.unix.*
>   comp.mail.*
>   news.software.*
>   news.newusers.questions
> 
> Also, lots of people have mailed me information and I've tried to
> acknowledge them below. 
> 
> ------------------------------
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 5.1 Acknowledgements
> 
> + means someone who is new since the last time I posted this FAQ
>   (i.e., since 31 October 1994).
> 
> Thanks to these people who sent suggestions and digest items:
>  + Jochen Bern <bern@uni-trier.de>
>    Jym Dyer <jym@remarque.berkeley.edu>
>    Mike Northam <mbn@greyskul.intel.com>
>  + Tim Pierce <twpierce@midway.uchicago.edu>
>    Janet Rosenbaum <ejrosen@merle.acns.nwu.edu>
> 
> Thanks to these people who sent suggestions:
>    Jeff Blaine <jblaine@ciesin.org>
>    Stephen Cristol <mphbj639@unix.cc.emory.edu>
>  + Roman Czyborra <czyborra@cs.tu-berlin.de>
>    Terry Gray <gray@cac.washington.edu>
>    Sven Guckes <guckes@inf.fu-berlin.de>
>    Jon Hamilton <hamilton@cs.iastate.edu>
>  + Rich Kasperowski <richk@icad.com>
>  + Hugh McGough <hughm@halcyon.com>
>    Mary McGough <mary@hitl.washington.edu>
>    David L Miller <dlm@cac.washington.edu>
>    Skip Montanaro <skip@automatrix.com>
>    David W. Tamkin <dattier@mcs.com>
>    Syd Weinstein <syd@dsinc.myxa.com>
>  + Everyone who told me that bash understands tilde (~)!
> 
> 
> Thanks to these people who've created ascii art, programs, and/or  
documents 
> that are pointed to in this article.  (This list is not complete right  
now.)
>  + Chris Alfeld <calfeld@math.utah.edu> or <calfeld@east.east-slc.edu>
>    Bob Allison <boba@wwwa.com>
>    Jorn Barger <jorn@genesis.mcs.com>
>  + Jean-Frangois Mezei 
>    Piero Serini <piero@strider.inet.it>
>    Doug Stevenson <doug+@osu.edu>
>  + Marc VanHeyningen <mvanheyn@cs.indiana.edu>
>    Bill Wohler <wohler@newt.com>
>    Scott A. Yanoff <yanoff@alpha2.csd.uwm.edu>
> 
> 
> Special thanks to:
>    Thomas A. Fine <fine@cis.ohio-state.edu> for setting up and
>    maintaining the hypertext archive of FAQs.  Congratulations
>    to him for winning O'Reilly and Associates' "The Best of the
>    Net" award!
> 
> Please let me know if I've left you, or anyone else, out of this list.
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: ... 5.2 If You'd Like to Contribute
> 
> If you have any corrections, suggestions, or new digest items to  
contribute
> to this FAQ please send them to me.  I'd especially like to learn about:
>   * Cool signatures that have less than or equal to four lines.
>   * Finger clients for Windows or Mac
>  
> Before you send suggestions please take a look at the latest version of  
this 
> article to see if I've already incorporated your suggestion.  It's  
archived
> at:
>  
http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/fa 
q.html
> ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq
> 
> If you are reading this with a viewer that understands the following URL  
you 
> can use it to send me mail:   mailto:nancym@ii.com
> 
> ------------------------------
> 
> From: Nancy McGough <nancym@ii.com>
> Subject: 6.0 Copyright Notice
> 
> Copyright (c) 1994 by Nancy McGough.  This collection of articles is  
first
> published in 1994 and is copyrighted by Nancy McGough (except subjects  
1.4,
> 1.5, 1.6, 1.8, 2.6, 3.3, 3.4) which are Copyright (c) 1994 by the  
authors named 
> in the sections).  No portion of this work may be sold or put to  
commercial 
> use without express written consent of the authors.  This restriction  
covers
> publication in any form, or distribution by any method, which permits  
this
> work to be visually perceived, either directly or with the aid of any  
machine
> or device. Permission is granted to republish or redistribute this  
article in
> its entirety for noncommercial use if this copyright notice is not  
removed or
> altered.
> 
> End of signature_finger_faq Digest
> **********************************
> 
> --
>  /\_/\    Nancy McGough
> ( o.o )   Infinite Ink
>  > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/


From owner-pine-info@cac.washington.edu  Tue Jan 24 16:47:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03498;
	Tue, 24 Jan 95 16:47:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19379;
	Tue, 24 Jan 95 16:43:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19373;
	Tue, 24 Jan 95 16:43:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWva1-00038PC; Tue, 24 Jan 95 16:27 PST
To: pine-info@cac.washington.edu
From: pisati@pippo.sm.dsi.unimi.it (Stefano Pisati IW2JXK)
Subject: Where src for HP ?
Date: 24 Jan 1995 10:39:48 +0100
Message-Id: <3g2ht4$6gg@pippo.sm.dsi.unimi.it>

I need to compile Pine on a HP-UX server and I need the source
ported to HP-UX... I've only found src and makefile only for
other plataform. Where can I find src for HP ???

		  Tnx in advance !!!

                    73 de -_ Stefano _-

PS: Please, reply via e-mail. Tnx !!!


       "Stat rosa pristina nomine nomina nuda tenemus"
----------------------------------------------------------------
Stefano Pisati  IW2JXK          Internet: pisati@dsi.unimi.it
PGP:  finger pisati@ghost.dsi.unimi.it  or
      e-mail pgp@dsi.unimi.it with Subject: GET Pisati
     http://www.dsi.unimi.it/Users/Students/pisati/home
----------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Tue Jan 24 17:08:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05078;
	Tue, 24 Jan 95 17:08:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18837;
	Tue, 24 Jan 95 17:03:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18831;
	Tue, 24 Jan 95 17:03:21 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWvxD-00038KC; Tue, 24 Jan 95 16:51 PST
To: pine-info@cac.washington.edu
From: Rahul Dhesi <dhesi@rahul.net>
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 1995 19:55:14 GMT
Message-Id: <3g3lv2$i90@hustle.rahul.net>
References: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu> <3g2rgj$h9h@moe.cc.emory.edu>

In <3g2rgj$h9h@moe.cc.emory.edu> walterc@eccomp.icu.eushc.org (Walter
C. Cooksey) writes:

>I find the easies thing to do is assume that it has been read within a
>reasonable time after delivery -- just like paper inter-office mail.

Read receipts are a common enough question among my users that I have a
standard reply.  The hint in the last paragraph is much more reliable
than any automatic mechanism ever will be.  Automated read receipts do
not tell you whether your message was read by the user, only if it was
read by his software.

   There is currently no universal mechanism for getting verification
   of email delivery.  One method that almost works is to include a
   header in your message:

	Return-Receipt-To: username@rahul.net

   IF the recipient's system uses 'sendmail' for mail transport, it
   will send back an automated reply saying it received the message.
   But it doesn't guarantee that it reached the recipient's mailbox,
   only that it reached the recipient's host.

   A requirement to get confirmation of mail actually being read by the
   recipient is that sending and receiving hosts have a common protocol
   for this.  This is not the case on the Internet, as sites are
   autonomous and use a variety of software.  The chances of it
   happening in the future is also small:  many people consider it a
   violation of their privacy.

   The best way to find out if somebody read your mail is to send a
   brief follow-up message saying "Hi, I was just wondering if my
   previous message reached...I can't tell if my email is getting
   out."  This will usually result in a quick reply.

-- 
Rahul Dhesi <dhesi@rahul.net>


From owner-pine-info@cac.washington.edu  Tue Jan 24 18:30:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07462;
	Tue, 24 Jan 95 18:30:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20475;
	Tue, 24 Jan 95 18:18:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from netcom15.netcom.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20469;
	Tue, 24 Jan 95 18:18:47 -0800
Received: by netcom15.netcom.com (8.6.9/Netcom)
	id SAA00268; Tue, 24 Jan 1995 18:11:08 -0800
Date: Tue, 24 Jan 1995 18:11:08 -0800 (PST)
From: Philip Zeyliger <vzvz@netcom.com>
X-Sender: vzvz@netcom15
To: Terry Gray <gray@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Non-standard INBOX locations and pine
In-Reply-To: <Pine.ULT.3.92.950123215458.3526M-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SUN.3.91.950124180910.29439A@netcom15>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 23 Jan 1995, Terry Gray wrote:

> Philip,
> You certainly should not need to modify source to change the inbox path!
Ok.`
> 
> I would suggest setting the inbox-path entry in /usr/local/lib/pine.conf to:
> 
>  inbox-path=.mailbox/inbox
> 
> or if you prefer the aesthetics of using $HOME, then use:
> 
>  inbox-path=${HOME}/.mailbox/inbox
> 
> (The squiggley brackets are needed to delimit the name of the env. var.)
> 
> I'm unclear on what you are trying to do in your script, or why it is 
> needed in preference to the existing pine.conf facility...
What is happening is at netcom our admins don't update software.
We are still using 3.89!  A group here compiles their own stuff and makes
it work!  I was helping pine users at netcom nget 3.91 but some had
trouble with mail locations...
I think the brackets around HOME solve everything!
Thanks!
> 
> -teg
> 

--   
   |\__      ----------------------------------------------------      __/| 
  /   o\__                                                          __/o   \
 |    ___='                      Philip Zeyliger                   `=___    |
 |    \                          vzvz@netcom.com                       /    |
  \    \                                                              /    /
   >    \                  ---------> KOHb <---------                /    <
 _| KOHb |_               on the Internet Chess Server             _|      |_
|  ______  |                telnet chess.lm.com 5000              |  ______  |
|__________| ==================================================== |__________|



From owner-pine-info@cac.washington.edu  Tue Jan 24 18:41:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07745;
	Tue, 24 Jan 95 18:41:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21712;
	Tue, 24 Jan 95 18:38:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21706;
	Tue, 24 Jan 95 18:38:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWxOA-00038RC; Tue, 24 Jan 95 18:23 PST
To: pine-info@cac.washington.edu
From: drown@iii1.iii.net (Steve Bernacki Jr)
Subject: Random .sig?
Date: 24 Jan 1995 20:38:33 GMT
Message-Id: <3g3ogs$jkn@nic.iii.net>

Howdy y'all,

Is it possible to somehow have a random signature (out of a directory of
signatures) be selected and pasted into pine?  If not, is there any way
to get pine to run a program that would output such a random sig?

Thanks!
-S
--
Steve Bernacki, Jr.  | unix programmer/ moxie drinker
Email: drown@iii.net | http://www.iii.net/users/drown.html


From owner-pine-info@cac.washington.edu  Tue Jan 24 19:54:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10005;
	Tue, 24 Jan 95 19:54:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21936;
	Tue, 24 Jan 95 19:50:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21930;
	Tue, 24 Jan 95 19:50:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWyV6-00038QC; Tue, 24 Jan 95 19:34 PST
To: pine-info@cac.washington.edu
From: mike@newport.lib.ca.us (Micheal Wojciechowski)
Subject: What do I do once I download pico?
Date: 24 Jan 1995 21:27:08 GMT
Message-Id: <3g3rbc$ke1@nic-nac.CSU.net>

I downloaded the version for HP-UX9, because this is the operating system we
are running, so now I have this file pico-bin.hpux9 and I don't know what 
to do with it now.  I am not very unix literate, although I know it enoough 
that I feel comfortable using it.  Any help would be appreciated. Thanks in 
advance.


Mike


From owner-pine-info@cac.washington.edu  Tue Jan 24 19:56:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10050;
	Tue, 24 Jan 95 19:56:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22862;
	Tue, 24 Jan 95 19:49:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from camco.celestial.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22855;
	Tue, 24 Jan 95 19:49:24 -0800
Received: from raindrop by camco.celestial.com with uucp
	(Smail3.1.28.1 #10) id m0rWyfT-0002AmC; Tue, 24 Jan 95 19:45 PST
Received: by raindrop.seaslug.org (4.1/smail2.5/05-07-92)
	id AA09493; Tue, 24 Jan 95 18:28:08 PST
Date: Tue, 24 Jan 1995 18:28:04 -0800 (PST)
From: Thomas Unger <unger@raindrop.seaslug.org>
To: Tobias Pluemer <pluemer@fz.telekom.de>
Cc: Pine Developers <pine-bugs@cac.washington.edu>,
        pine-info@cac.washington.edu
Subject: Re: Bug (ID VF0FQ): 
In-Reply-To: <Pine.PCW.3.91.950124104355.12607L-100000@magnum.fz.telekom.de> 
Message-Id: <Pine.SUN.3.91.950124182435.6279K-100000@raindrop.seaslug.org>
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-23621000-3422--1294943920=:302526783"
Content-Id: <Pine.PCW.3.91.950124105132.12607N@magnum.fz.telekom.de>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---23621000-3422--1294943920=:302526783
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.PCW.3.91.950124105132.12607O@magnum.fz.telekom.de>


Thanks for the bug report.  I couldn't reproduce it on my machine - but
I do handle CTRL-space as a special case and there may be a bug in that
code.  I'll take a look at it.

--  Tom Unger
    WWC


On Tue, 24 Jan 1995, Tobias Pluemer wrote:

> Dear Pine Developers,
> 
> I have found a bug in PCPINE for Windows (3.91).
> 
> When I include a file via CTRL-R and just type the filename (i.e. without 
> CTRL-T to get the browser) the CTRL key seems to be locked, but only for 
> the SPACE key. 
> this meens:
> all keys work as they should, but hitting SPACE the function CTRL-SPACE 
> is performed. executing any CTRL-... function or just hitting CTRL stops 
> this behavior. 
> 
> 
> 
> ----------------------------------------------------------------------------
> Tobias Pluemer                                 Email: pluemer@fz.telekom.de
> Deutsche Telekom AG FTZ                        Deutsche Telekom AG FTZ
> Forschungs- und Technologiezentrum             Research Center
> Am Kavalleriesand 3 (Postfach 10 00 03)        PO Box: 10 00 03
> 64276 Darmstadt                                D-64276 Darmstadt
> Tel: 06151/83-5545                             Tel: +49 6151 83 5545
> FAX: 06151/83-4066                             FAX: +49 6151 83 4066
> 
---23621000-3422--1294943920=:302526783--


From owner-pine-info@cac.washington.edu  Tue Jan 24 20:29:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10998;
	Tue, 24 Jan 95 20:29:41 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23463;
	Tue, 24 Jan 95 20:24:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23457;
	Tue, 24 Jan 95 20:24:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWz3b-00038TC; Tue, 24 Jan 95 20:10 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: Wyse60 Support
Date: 24 Jan 1995 12:34:40 -0800
Message-Id: <3g3o90$lt9@garlic.com>

Ok ... I finally got pine, and I've been playing around with it, and I 
suddenly realize that the cursor keys on our Wyse60 terminals are not 
working inside Pine ... 

It looks like the cursor keys send ^K, ^J, ^H, and ^L, which Pine uses
for other purposes.  Is there a way to remap these keys inside Pine, or 
do I initialize the terminal to a different type going in??? 

Anybody ever run into this?

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


From owner-pine-info@cac.washington.edu  Tue Jan 24 20:36:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11180;
	Tue, 24 Jan 95 20:36:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22622;
	Tue, 24 Jan 95 20:33:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22616;
	Tue, 24 Jan 95 20:33:34 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rWzBv-00038WC; Tue, 24 Jan 95 20:18 PST
To: pine-info@cac.washington.edu
From: casey@calon.com (casey)
Subject: When oh when filter for mailing lists?
Message-Id: <D2xKAq.Hrx@nbn.com>
Date: Tue, 24 Jan 1995 22:11:13 GMT

You know the problem--you can filter on "from" but not on "reply to".
I'd kill for a good mailing list manager.


From owner-pine-info@cac.washington.edu  Tue Jan 24 20:37:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11231;
	Tue, 24 Jan 95 20:37:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22632;
	Tue, 24 Jan 95 20:33:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22626;
	Tue, 24 Jan 95 20:33:48 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA10961; Tue, 24 Jan 1995 23:33:23 +0500
Date: Tue, 24 Jan 1995 23:33:23 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: Pine Bug?
In-Reply-To: <3g3gtm$g9e@wally.uofport.edu>
Message-Id: <Pine.SOL.3.91.950124233132.10801C-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 703

On 24 Jan 1995, Eric A. Hobbs wrote:

> I don't know if this is in the documentation or in a FAQ, but I've found 
> a way to crash Pine (I've tried v3.89 and v3.91).
> 
> A few users and I were able to crash Pine by simply changing the 
> capitalization of the first letter of an address book nickname.  We're 
> running SunOS 4.1.3_U1 and 4.1.4.  
 
Doesn't happen here under SunOS 5.3 and Pine 3.91.
 
--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA




From owner-pine-info@cac.washington.edu  Tue Jan 24 22:06:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13736;
	Tue, 24 Jan 95 22:06:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25007;
	Tue, 24 Jan 95 22:03:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25001;
	Tue, 24 Jan 95 22:03:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rX0az-00038KC; Tue, 24 Jan 95 21:48 PST
To: pine-info@cac.washington.edu
From: mnewell@gatecoms.gatecom.com (Matt Newell)
Subject: Re: Random .sig?
Date: 25 Jan 1995 00:05:51 GMT
Message-Id: <3g44kv$et4@gatecoms.gatecom.com>
References: <3g3ogs$jkn@nic.iii.net>

Steve Bernacki Jr (drown@iii1.iii.net) wrote:
> Howdy y'all,

> Is it possible to somehow have a random signature (out of a directory of
> signatures) be selected and pasted into pine?  If not, is there any way
> to get pine to run a program that would output such a random sig?

This may not be exactly what you requested, but it works for me.

#! /sbin/sh
mv ${HOME}/.signature ${HOME}/sig1.tmp
mv ${HOME}/.sigb ${HOME}/sig2.tmp
mv ${HOME}/.sigc ${HOME}/sig3.tmp
mv ${HOME}/.sigd ${HOME}/sig4.tmp
mv ${HOME}/.sige ${HOME}/sig5.tmp
mv ${HOME}/sig1.tmp ${HOME}/.sige
mv ${HOME}/sig2.tmp ${HOME}/.signature
mv ${HOME}/sig3.tmp ${HOME}/.sigb
mv ${HOME}/sig4.tmp ${HOME}/.sigc
mv ${HOME}/sig5.tmp ${HOME}/.sigd

This is obviously for 5 sigs, but can be easily changed to work with more
or less

I just have it in my .login, so that I have a different sig each time I
login.

     Hope this helps,
     Matt

**   Matt Newell                             mnewell@gatecoms.gatecom.com   **
------------------------------------------------------------------------------
Any man's death diminishes me, because I am involved in mankind. Therefore,
never send to know for whom the bell tolls, It tolls for thee.
                                                              -John Donne


From owner-pine-info@cac.washington.edu  Tue Jan 24 22:11:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14016;
	Tue, 24 Jan 95 22:11:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24224;
	Tue, 24 Jan 95 22:08:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24218;
	Tue, 24 Jan 95 22:08:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rX0iv-00038OC; Tue, 24 Jan 95 21:56 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: Re: Wyse60 Support
Date: 24 Jan 1995 14:53:35 -0800
Message-Id: <3g40df$gd5@garlic.com>
References: <3g3o90$lt9@garlic.com>

Robert Mann Packaging Co. (rmp@garlic.com) wrote:
: It looks like the cursor keys send ^K, ^J, ^H, and ^L, which Pine uses
: for other purposes.  Is there a way to remap these keys inside Pine, or 
: do I initialize the terminal to a different type going in??? 

O.K.  I figured out how to get around this on my system.  I setup a shell
script that invokes 'tput -T wyse60ak reset' before invoking pine, and 
'tput reset' after invoking pine.  The wyse60ak terminfo has ANSI key 
definitions for the cursor keys.  

Thanks anyway ...

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


From owner-pine-info@cac.washington.edu  Tue Jan 24 22:36:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14603;
	Tue, 24 Jan 95 22:36:05 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24560;
	Tue, 24 Jan 95 22:32:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from asl-labs.bc.ca by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24554;
	Tue, 24 Jan 95 22:32:36 -0800
Received: by asl3.asl-labs.bc.ca (5.4R3.10/200.2.1.5)
	id AA13211; Tue, 24 Jan 1995 22:24:14 -0800
Date: Tue, 24 Jan 1995 22:24:14 -0800 (PST)
From: "Brian P. Hampson" <brian@asl3.asl-labs.bc.ca>
Subject: Re: Wyse60 Support
Cc: pine-info@cac.washington.edu
In-Reply-To: <3g3o90$lt9@garlic.com>
Message-Id: <Pine.3.89.9501242248.A13179-0100000@asl3>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 24 Jan 1995, Robert Mann Packaging Co. wrote:

> Ok ... I finally got pine, and I've been playing around with it, and I 
> suddenly realize that the cursor keys on our Wyse60 terminals are not 
> working inside Pine ... 
> 
> It looks like the cursor keys send ^K, ^J, ^H, and ^L, which Pine uses
> for other purposes.  Is there a way to remap these keys inside Pine, or 
> do I initialize the terminal to a different type going in??? 

Yup. Pine doesn't use TERMINFO or TERMCAP to get cursor movements :(  

^N for next line,
^P for previous line,
^F to move forward one character,
^B to move backward one character.

Is there a SOFTWARE way of switching TERMINAL modes for a WYSE?  I would 
LOVE to be able to turn it into a vt102, and then back again after 
pine....is this possible?

It would also help with lynx.

B.

   ------------------------------------------------------------------------
   |Brian P. Hampson                  Internet: brian@asl-labs.bc.ca      |
   |System Administration,                      			  |
   |Analytical Service Labs           Fidonet : Brian Hampson 1:153/733   |
   |Vancouver, BC                                                         |
   |                                                                      |
   |               Specialists in Environmental Chemistry                 | 
   |                                                                      |
   ------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Tue Jan 24 23:54:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16141;
	Tue, 24 Jan 95 23:54:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26452;
	Tue, 24 Jan 95 23:50:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26446;
	Tue, 24 Jan 95 23:50:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rX2Mk-00038OC; Tue, 24 Jan 95 23:42 PST
To: pine-info@cac.washington.edu
From: harmonr@coho.halcyon.com (robert harmon)
Subject: PICO & SPELL checker
Date: 24 Jan 1995 18:29:06 GMT
Message-Id: <3g3gti$d38@news.halcyon.com>

For some time now I've been frustrated by the spell checker in PICO. I 
use a lot of words that are not in SPELL's default dictionary and wanted 
a better way of bypassing these words than pressing the space bar. After 
some digging I've come up with the following. If it's already common 
knowledge pardon the redundancy. If it's not it might make life a bit 
easier. BTW - I tried ISPELL as a substitute for SPELL but found it klunky 
and confusing.

The following works for those who use PICO as their default editor and 
SPELL as their spell checker. I haven't checked this for other editors.

To create a custom dictionary for SPELL:
- Two files will be created in your HOME directory:

  1 - New words; an ascii file - sorted one word per line - caps 
      don't seem to matter (I named mine .newwords).

  2 - New dictionary; a hashed file (I named mine .newhlista).

- From the UNIX prompt key: 
  cat .newwords | spellin /usr/dict/hlista > .newhlista
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  (The above creates a new custom dictionary.)

  cat .newwords | spellout .newhlista
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  (The above compares new words to words in custom dictionary.)

- Edit your .login file to include:
  setenv SPELL 'spell -d .newhlista'
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Logoff & log back into the system to enable changes made to .login 
environment variables. Now when you use the ^T within PICO SPELL will 
check for your custom dictionary as specified in .login file.

Hope this helps,
	Robert H. Harmon (halcyon.com)
--
	Chris Harmon & Associates
	Management & Training Consultants
	PO Box 2756,  Kirkland, WA 98083-2756
	(206) 820-3204 Vox (206) 820-4807 Fax





From owner-pine-info@cac.washington.edu  Wed Jan 25 00:03:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16398;
	Wed, 25 Jan 95 00:03:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25662;
	Wed, 25 Jan 95 00:00:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from saul1.u.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25655;
	Wed, 25 Jan 95 00:00:26 -0800
Received: by saul1.u.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17985;
	Wed, 25 Jan 95 00:00:25 -0800
X-Sender: absweger@saul1.u.washington.edu
Date: Wed, 25 Jan 1995 00:00:24 -0800 (PST)
From: Andrew Sweger <absweger@u.washington.edu>
To: casey <casey@calon.com>
Cc: pine-info@cac.washington.edu
Subject: Re: When oh when filter for mailing lists?
In-Reply-To: <D2xKAq.Hrx@nbn.com>
Message-Id: <Pine.OSF.3.91a.950124235931.12923B-100000@saul1.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 24 Jan 1995, casey wrote:

> You know the problem--you can filter on "from" but not on "reply to".
> I'd kill for a good mailing list manager.

We know the answer -- procmail



From owner-pine-info@cac.washington.edu  Wed Jan 25 00:43:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17085;
	Wed, 25 Jan 95 00:43:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27098;
	Wed, 25 Jan 95 00:39:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27092;
	Wed, 25 Jan 95 00:39:55 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa09882;
          25 Jan 95 1:27 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA19961; Wed, 25 Jan 1995 08:41:55 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id DAA14234; Wed, 25 Jan 1995 03:38:55 -0500
Date: Wed, 25 Jan 1995 03:38:54 -0500 (EST)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: Steve Bernacki Jr <drown@iii1.iii.net>
Cc: pine-info@cac.washington.edu
Subject: Re: Random .sig?
In-Reply-To: <3g3ogs$jkn@nic.iii.net>
Message-Id: <Pine.LNX.3.91.950125033725.14212A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 24 Jan 1995, Steve Bernacki Jr wrote:

> Howdy y'all,
> 
> Is it possible to somehow have a random signature (out of a directory of
> signatures) be selected and pasted into pine?  If not, is there any way
> to get pine to run a program that would output such a random sig?

If you ftp to typhoon.unl.edu:/pub/mgleason, there is a file called 
sigrnd.tgz which does what you want.  You will gunzip to uncompress it.

Stuart

 ----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Wed Jan 25 00:47:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17178;
	Wed, 25 Jan 95 00:47:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27165;
	Wed, 25 Jan 95 00:43:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.Germany.EU.net by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27159;
	Wed, 25 Jan 95 00:43:46 -0800
Received: by mail.Germany.EU.net with UUCP (8.6.5:29/EUnetD-2.5.1.c) via EUnet
	id JAA23316; Wed, 25 Jan 1995 09:45:28 +0100
Received: from sun51.fz.telekom.de (sun51.fz.telekom.de [192.166.56.95]) by eunetgate.fz.telekom.de (8.6.5/8.6.5) with SMTP id JAA01908; Wed, 25 Jan 1995 09:38:07 +0100
Received: by sun51.fz.telekom.de (4.1/SMI-4.1)
	id AA14967; Wed, 25 Jan 95 09:40:25 +0100
Date: Wed, 25 Jan 1995 09:40:24 +0100 (MET)
From: Ralf Widera <widera@fz.telekom.de>
To: "Eric A. Hobbs" <hobbs@uofport.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Pine Bug?
In-Reply-To: <3g3gtm$g9e@wally.uofport.edu>
Message-Id: <Pine.SUN.3.91.950125093628.14953B-100000@sun51.fz.telekom.de>
"Reply-To: widera@fz.telekom.de"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 24 Jan 1995, Eric A. Hobbs wrote:

> I don't know if this is in the documentation or in a FAQ, but I've found 
> a way to crash Pine (I've tried v3.89 and v3.91).
> 
> A few users and I were able to crash Pine by simply changing the 
> capitalization of the first letter of an address book nickname.  We're 
> running SunOS 4.1.3_U1 and 4.1.4.  
> 

Pine (3.91) didn't crash on my sun (SUNOS 4.1.3), but I got a message 
stating that "xxx already exist in .addressbook as yyy" (replace xxx with 
the new nickname and yyy with the according fullname). This is quite 
unnecessary, because I know that I changed an entry in the .addressbok 
and therefore I know that thgis entry exists.

-raw

---------------------------------------------------------------------------
Ralf Widera, FZ 211b                            Email: widera@fz.telekom.de
Deutsche Telekom AG                             phone: +49 6151 83 3855
Forschungs- und Technologiezentrum              FAX  : +49 6151 83 4066
Postfach 10 00 03
D-64276 Darmstadt, Germany



From owner-pine-info@cac.washington.edu  Wed Jan 25 00:49:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17245;
	Wed, 25 Jan 95 00:49:31 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27185;
	Wed, 25 Jan 95 00:44:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27179;
	Wed, 25 Jan 95 00:44:48 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa10064;
          25 Jan 95 1:32 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA20318; Wed, 25 Jan 1995 08:46:45 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id DAA14244; Wed, 25 Jan 1995 03:43:45 -0500
Date: Wed, 25 Jan 1995 03:43:45 -0500 (EST)
From: Stuart Tares <stares@lhr-sys.bru-ro.DHL.COM>
Reply-To: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
To: casey <casey@calon.com>
Cc: pine-info@cac.washington.edu
Subject: Re: When oh when filter for mailing lists?
In-Reply-To: <D2xKAq.Hrx@nbn.com>
Message-Id: <Pine.LNX.3.91.950125034018.14212B-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 24 Jan 1995, casey wrote:

> You know the problem--you can filter on "from" but not on "reply to".
> I'd kill for a good mailing list manager.
> 

Try looking at procmail which can be found at 
ftp.informatik.rwth-aachen.de:/pub/packages/procmail.  This package 
allows you to filter on virtually anything which occurs anywhere in a 
message (ie you can filter both the body and the header).

Stuart

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Wed Jan 25 03:04:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20615;
	Wed, 25 Jan 95 03:04:22 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28912;
	Wed, 25 Jan 95 02:54:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from calon.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28906;
	Wed, 25 Jan 95 02:54:44 -0800
Received: from calon.com by calon.calon.com; Wed, 25 Jan 95 02:47 PST
Date: Wed, 25 Jan 1995 02:47:52 -0800 (PST)
From: Kathleen Creighton <casey@calon.com>
Subject: Re: When oh when filter for mailing lists?
To: Andrew Sweger <absweger@u.washington.edu>
Cc: pine-info@cac.washington.edu
In-Reply-To: <Pine.OSF.3.91a.950124235931.12923B-100000@saul1.u.washington.edu>
Message-Id: <Pine.3.89.9501250205.A17164-0100000@calon>
Mime-Version: 1.0
Content-Length: 353
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Wed, 25 Jan 1995, Andrew Sweger wrote:

> On Tue, 24 Jan 1995, casey wrote:
> 
> > You know the problem--you can filter on "from" but not on "reply to".
> > I'd kill for a good mailing list manager.
> 
> We know the answer -- procmail
> 
If you're a programmer.  If you're not, you're sunk.  Unless you want to 
give me an exact form for doing it.


From owner-pine-info@cac.washington.edu  Wed Jan 25 03:35:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21660;
	Wed, 25 Jan 95 03:35:10 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29387;
	Wed, 25 Jan 95 03:30:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29381;
	Wed, 25 Jan 95 03:30:43 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa18067;
          25 Jan 95 4:18 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA15610; Wed, 25 Jan 1995 11:32:43 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id GAA18003; Wed, 25 Jan 1995 06:29:44 -0500
Date: Wed, 25 Jan 1995 06:29:43 -0500 (EST)
From: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
X-Sender: stares@lhroas1.lhr-sys.bru-ro.DHL.COM
To: Kathleen Creighton <casey@calon.com>
Cc: Andrew Sweger <absweger@u.washington.edu>, pine-info@cac.washington.edu
Subject: Re: When oh when filter for mailing lists?
In-Reply-To: <Pine.3.89.9501250205.A17164-0100000@calon>
Message-Id: <Pine.LNX.3.91.950125061921.17995A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 25 Jan 1995, Kathleen Creighton wrote:

> 
> 
> > We know the answer -- procmail
> > 
> If you're a programmer.  If you're not, you're sunk.  Unless you want to 
> give me an exact form for doing it.
> 

An example of a procmail "program" is

:0:
* ^From.*pine.*
pine

which says (basically)

:0:              --> Take this message and using a local locfile called 
                     pine.lock (the lock filename is the folder name + 
                     .lock) 

* ^From.*pine.*  --> Egrep for From at the start of the line followed by
                     any number of characters, followed by pine, followed
                     by any number of characters

pine		 --> Put any messages which conform to the above search 
                     into the folder called pine, which will be placed (or
                     found under $MAILDIR)

I realise that this is a *very* simple recipe for procmail but it will 
place any incoming messages which contain the word pine in the From line 
into the folder called pine.  Simply add more conditions to refine the 
process.

In addition, procmail comes with a (IMHO) very good set of manual pages - 
try man procmailex to see some examples.

Stuart

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Wed Jan 25 05:31:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25358;
	Wed, 25 Jan 95 05:31:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01165;
	Wed, 25 Jan 95 05:21:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from arthur.cs.purdue.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01157;
	Wed, 25 Jan 95 05:21:44 -0800
Received: from lab19.cs.purdue.edu (root@lab19.cs.purdue.edu [128.10.11.119])
    by arthur.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with ESMTP
    id <IAA02080> for <pine-info@cac.washington.edu>; Wed, 25 Jan 1995 08:21:43 -0500
Received: from lab19.cs.purdue.edu (simmonmt@lab19.cs.purdue.edu [128.10.11.119])
    by lab19.cs.purdue.edu (8.6.4/PURDUE_CS-1.3) with SMTP
    id <IAA21000> for <pine-info@cac.washington.edu>; Wed, 25 Jan 1995 08:21:41 -0500
Date: Wed, 25 Jan 1995 08:21:40 -0500 (EST)
From: Matt Simmons <simmonmt@cs.purdue.edu>
To: Pine Mailing List <pine-info@cac.washington.edu>
Subject: Pine causes high load
Message-Id: <Pine.SUN.3.91.950125081815.20985A-100000@lab19.cs.purdue.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

When the session running a Pine process suddenly disappears for whatever
reason, the Pine process apparently starts using CPU time like mad.  Is
there any way to make it realize that I'm not logged on anymore, and to make
it quit nicely so it doesn't drive the load up?  I'm using 3.91.


From owner-pine-info@cac.washington.edu  Wed Jan 25 06:26:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27624;
	Wed, 25 Jan 95 06:26:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01963;
	Wed, 25 Jan 95 06:11:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mercury.bih.harvard.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01957;
	Wed, 25 Jan 95 06:11:09 -0800
Received: (from scott@localhost) by BIH Mail Handler (8.6.9/8.6.7) id JAA14640; Wed, 25 Jan 1995 09:11:03 -0500
Date: Wed, 25 Jan 1995 09:11:02 -0500 (EST)
From: Scott McWilliams <scott@bih.harvard.edu>
X-Sender: scott@mercury
To: pine-info@cac.washington.edu
Subject: procmail listserver
In-Reply-To: <Pine.OSF.3.91a.950124235931.12923B-100000@saul1.u.washington.edu>
Message-Id: <Pine.SUN.3.91.950125090651.13925B-100000@mercury>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Is there a procmail listserver at all?

Our procmail handles over 70000 pieces of mail weekly for a centralized 
mail server, but if users use Mosaic or Gopher to a remote site, obtain 
info and try to mail it back, the mail connection opens to our server but 
procmail routinely reports "No such user" and then quotes the exact email 
address between double quotes. This quoted address is indeed a valid 
address despite what procmail says. In the end, the user here does not 
get their Mosaic/Gopher initiated mail.
Ideas?
------------------ - - - - - - - - - - - - - ------------------------------
|  Scott A. McWilliams          Internet: Scott_McWilliams@bih.harvard.edu |
|    Sysadmin, Postmaster                                                  |
|    Beth Israel Hospital, Network Services           Vox: +1 617.667.5559 |
|    330 Brookline Ave, Boston MA 02215              Facs: +1 617.667.3966 |
-------------------- - -Deinimid iarracht ni/os fearr!- - ------------------

On Wed, 25 Jan 1995, Andrew Sweger wrote:

> On Tue, 24 Jan 1995, casey wrote:
> 
> > You know the problem--you can filter on "from" but not on "reply to".
> > I'd kill for a good mailing list manager.
> 
> We know the answer -- procmail
> 


From owner-pine-info@cac.washington.edu  Wed Jan 25 07:01:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28900;
	Wed, 25 Jan 95 07:01:06 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02596;
	Wed, 25 Jan 95 06:50:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02589;
	Wed, 25 Jan 95 06:50:07 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa25243;
          25 Jan 95 7:37 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA15924; Wed, 25 Jan 1995 14:52:05 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id JAA19888; Wed, 25 Jan 1995 09:50:30 -0500
Date: Wed, 25 Jan 1995 09:50:24 -0500 (EST)
From: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
X-Sender: stares@lhroas1.lhr-sys.bru-ro.DHL.COM
To: Scott McWilliams <scott@bih.harvard.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: procmail listserver
In-Reply-To: <Pine.SUN.3.91.950125090651.13925B-100000@mercury>
Message-Id: <Pine.LNX.3.91.950125094857.19881B-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 25 Jan 1995, Scott McWilliams wrote:

> 
> Is there a procmail listserver at all?
> 
[snip]

If you mean a mailing list for procmail then yes there is.  Send email to

	procmail-request@informatik.rwth-aachen.de


----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Wed Jan 25 07:27:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29723;
	Wed, 25 Jan 95 07:27:12 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02298;
	Wed, 25 Jan 95 07:23:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02292;
	Wed, 25 Jan 95 07:23:22 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rX9H6-00038TC; Wed, 25 Jan 95 07:04 PST
To: pine-info@cac.washington.edu
From: twpierce@quads.uchicago.edu (Tim Pierce)
Control: cancel <3g3gvp$ip5@masala.cc.uh.edu>
Subject: Re: Signature and Finger FAQ
Message-Id: <1995Jan25.061648.7513@midway.uchicago.edu>
References: <3cqchl$3uj@news.halcyon.com>
Date: Wed, 25 Jan 1995 06:16:48 GMT

Followup article consisting entirely of quoted text
cancelled.

-- 
Green Card fodder: Canter, Siegel, green card, Joel Furr, liable,
fortune, conspiracy, CyberSell, Tennessee Bar.


From owner-pine-info@cac.washington.edu  Wed Jan 25 07:44:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00550;
	Wed, 25 Jan 95 07:44:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03551;
	Wed, 25 Jan 95 07:38:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03545;
	Wed, 25 Jan 95 07:38:34 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rX9WC-00038XC; Wed, 25 Jan 95 07:20 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: Need Pine Binaries, where's celestial.com?
Date: Wed, 25 Jan 1995 04:35:09 GMT
Message-Id: <D2y22L.950@ssi.edc.org>
References: <3g0je5$kft@garlic.com> <Pine.SUN.3.91.950123102443.15201A-100000@linda.teleport.com>

Knute Snortum (knute@teleport.com) wrote:
: On 23 Jan 1995, Robert Mann Packaging Co. wrote:

: celestial.com *does* (or did) exist; I've been on there, but perhaps like 
: you, I haven't been able to connect to them recently, and I *really* want 
: to!

I've answered this by private mail a lot recently, so a posting is 
definitely in order.  ftp.celestial.com recently changed IP aggresses, 
and most of the world hasn't found out about it.  Someone (probably me) 
needs to prod them about DNS propagation.

ftp.celestial.com is now a CNAME (alias) for camco1.celestial.com, which 
is IP address 192.136.111.2

Another place to find my binaries package for Pine 3.91 for SCO is 
odi.cwc.whecn.edu.  They're on the other side of MCI from me, through 
Sprintnet to Westnet.  MCInet recently had a few serious routing 
glitches, so if you've been unable to get to WHECN, you probably can now, 
since MCInet has settled down.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Wed Jan 25 07:45:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00594;
	Wed, 25 Jan 95 07:45:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02404;
	Wed, 25 Jan 95 07:28:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rzserv2.fh-lueneburg.de by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02386;
	Wed, 25 Jan 95 07:28:18 -0800
Received: by rzserv2.fh-lueneburg.de (AIX 3.2/UCB 5.64/4.03)
          id AA16457; Wed, 25 Jan 1995 16:24:00 +0100
Date: Wed, 25 Jan 1995 16:23:59 +0100 (NFT)
From: Ralf Matthies <matthies@rzserv2.fh-lueneburg.de>
To: Pete Holsberg <pjh@mccc.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Need HELP! BinHEX conversion?
In-Reply-To: <D2x9pI.5KE@mccc.edu>
Message-Id: <Pine.A32.3.91.950125161841.39801A-100000@rzserv2.fh-lueneburg.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 24 Jan 1995, Pete Holsberg wrote:

> Ralf Matthies (matthies@rzserv2.fh-lueneburg.de) wrote:
> : On 19 Jan 1995, Richard Hsiung wrote:
> 
> : > I got a mail from someone with an attachment (supposedly), well, in the 
> : > message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
> : > BinHex and how do I get this attachment back into file form?
> 
> : you will find BinHex on the following aFTP servers:
> 
> :               ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip
> :               micros.hensa.ac.uk  /mirrors/simtel/msdos/mac/binhex13.zip
> 
> : PS: Ask me, if you have more questions... ;-)
> 
> 
> OK. Where is BINHEX for Unix?

Hi,

as far as i know there is no equivalent program on UNIX platforms
available (until yet).    :-(

So short,

(R)alf Matthies
Fachhochschule Nordostniedersachsen, Lueneburg, Germany



From owner-pine-info@cac.washington.edu  Wed Jan 25 07:53:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00849;
	Wed, 25 Jan 95 07:53:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02785;
	Wed, 25 Jan 95 07:48:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02779;
	Wed, 25 Jan 95 07:48:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #1)
	id m0rX9h2-00038TC; Wed, 25 Jan 95 07:31 PST
To: pine-info@cac.washington.edu
From: Dan Mullen <dmullen@gate.net>
Subject: Re-Sending EMail??
Date: Wed, 25 Jan 1995 03:06:08 -0500 (EST)
Message-Id: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Question:
What Pine command do I use to resend a previously sent message
that has been returned due to Wrong Address or Server Error?

This has happened a couple ot times and had to retype the whole message 
again. Suggestion Please!!

dmullen@gate.net


From owner-pine-info@cac.washington.edu  Wed Jan 25 08:40:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02633;
	Wed, 25 Jan 95 08:40:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04803;
	Wed, 25 Jan 95 08:35:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04797;
	Wed, 25 Jan 95 08:35:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXATu-00038PC; Wed, 25 Jan 95 08:22 PST
To: pine-info@cac.washington.edu
From: harmonr@coho.halcyon.com (robert harmon)
Subject: how to KILL in PINE like I do in TIN
Date: 25 Jan 1995 05:21:07 GMT
Message-Id: <3g4n43$qtq@news.halcyon.com>

Is there a way to generate a list of addressees from whom I don't want 
to receive mail or newsgroup feeds? I use the KILL file when I use TIN as 
my newsreader but can't find a similar feature in PINE.

	Thanks,
	Robert H. Harmon (harmonr@halcyon.com)
--
	Chris Harmon & Associates
	Management & Training Consultants
	PO Box 2756,  Kirkland, WA 98083-2756
	(206) 820-3204 Vox (206) 820-4807 Fax





From owner-pine-info@cac.washington.edu  Wed Jan 25 08:56:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03218;
	Wed, 25 Jan 95 08:56:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05106;
	Wed, 25 Jan 95 08:50:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from paradiso.umuc.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05100;
	Wed, 25 Jan 95 08:50:51 -0800
Received:  from rocky@localhost by paradiso.umuc.edu (8.6.8/16.2)
          id LAA24070; Wed, 25 Jan 1995 11:52:00 -0500
From: Rocky Giannini <rocky@paradiso.umuc.edu>
Message-Id: <199501251652.LAA24070@paradiso.umuc.edu>
Subject: Setting up pine to read from our news spool (not nntp)
To: pine-info@cac.washington.edu
Date: Wed, 25 Jan 1995 11:51:59 -0500 (EST)
X-Mailer: ELM [version 2.4 PL22]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 319       

I apologize if this is an FAQ (if it is, please point me to the right place).

We're running Pine 3.91 on the system that contains our news spool files.  
Is there a way to make pine access the news spool directly without initiating
an NNTP connection?

Thanks in advance!

-- 
Rocky Giannini
UMUC Unix and VMS Systems


From owner-pine-info@cac.washington.edu  Wed Jan 25 09:02:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03577;
	Wed, 25 Jan 95 09:02:48 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04196;
	Wed, 25 Jan 95 08:55:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04190;
	Wed, 25 Jan 95 08:55:50 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXAp3-00038PC; Wed, 25 Jan 95 08:43 PST
To: pine-info@cac.washington.edu
From: daud@winternet.com (David Denney)
Subject: Re: Q. about HUJI VMS Pine 3.91 beta 3
Date: 25 Jan 1995 07:03:59 GMT
Message-Id: <3g4t4v$op3@blackice.winternet.com>
References: <1732D14368S86.FLAVELL@cernvm.cern.ch>

Alan J Flavell (FLAVELL@cernvm.cern.ch) wrote:
: Problem I am having is that whenever I try to compose a message,
: it asks if I want to continue the postponed one.  If I say no, it
: works OK.  If I say yes or take the default, it crashes.  The
: README.VMS _says_ that "messages cannot be postponed".
: What makes it think I have a postponed mail?

Add 'postponed-folder=""' in pine.conf (global) or .pinerc (sys$login)

: Also, can someone explain just what it means under 1. in "Restrictions"?
: It says "the user must not switch to another folder as long as NEWMAIL
: has items".  Does something terrible happen?

That is only applicable if you map INBOX to be NEWMAIL. DO NOT DO THIS.
Nasty things will happen. Leave INBOX = INBOX, ignore it completely, and 
make a few extra keystrokes to open NEWMAIL instead. 

--
david@mbcm.org		Sys/Net Admin		David M Denney
612.871.3300 x259	Systems Design		Mem. Blood Centers of MN
612.871.1359 fax	Programming		2304 Park Avenue South
612.899.2743 pager	Hardware Maint.		Minneapolis, MN  55404


From owner-pine-info@cac.washington.edu  Wed Jan 25 09:12:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04491;
	Wed, 25 Jan 95 09:12:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05414;
	Wed, 25 Jan 95 09:04:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05408;
	Wed, 25 Jan 95 09:04:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXAu1-00038VC; Wed, 25 Jan 95 08:49 PST
To: pine-info@cac.washington.edu
From: eks@vki68.aar-vki.dk (Eigil Krogh Sorensen)
Subject: [Q] How to force pine to save Passwd on disk ??
Date: 25 Jan 1995 07:00:55 GMT
Message-Id: <3g4sv7$288@belfort.daimi.aau.dk>

How can you force PC-Pine 3.91 to save passwd on disk, so the user 
doesn't have to sign in each time pine is started ?

Thanks in advance

 -- Eigil Krogh Sorensen
 
-------------------------------------------------------------------------
VKI                     !                                !
Water Quality Institute !Phone:                          !E-mail:
Science Park Aarhus     ! +45  86 20 20 00 or            !
10, Gustav Wieds Vej    ! +45   86 20 20 11  local  2114 ! eks@aar-vki.dk
DK-8000 Aarhus C        !Fax:                            !
DENMARK.                ! +45   86 19 75 11              !
-------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Wed Jan 25 09:15:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04594;
	Wed, 25 Jan 95 09:15:07 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04783;
	Wed, 25 Jan 95 09:09:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04777;
	Wed, 25 Jan 95 09:09:39 -0800
Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03658;
	Wed, 25 Jan 95 09:09:35 -0800
Date: Wed, 25 Jan 1995 09:09:34 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Matt Simmons <simmonmt@cs.purdue.edu>
Cc: Pine Mailing List <pine-info@cac.washington.edu>
Subject: Re: Pine causes high load
In-Reply-To: <Pine.SUN.3.91.950125081815.20985A-100000@lab19.cs.purdue.edu>
Message-Id: <Pine.ULT.3.92.950125090341.23521E-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Matt,
Can you make this bug occur on demand?  If so, please get in touch 
with us directly...

Until the bug is squashed, your only choice is the venerable "kill" command.

-teg

On Wed, 25 Jan 1995, Matt Simmons wrote:

> When the session running a Pine process suddenly disappears for whatever
> reason, the Pine process apparently starts using CPU time like mad.  Is
> there any way to make it realize that I'm not logged on anymore, and to make
> it quit nicely so it doesn't drive the load up?  I'm using 3.91.
> 


From owner-pine-info@cac.washington.edu  Wed Jan 25 09:24:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05356;
	Wed, 25 Jan 95 09:24:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05915;
	Wed, 25 Jan 95 09:18:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from woolf.individual.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05909;
	Wed, 25 Jan 95 09:18:49 -0800
Received: by individual.com (5.65c/Spike-2.1)
	id AA29409; Wed, 25 Jan 1995 12:17:02 -0500
Date: Wed, 25 Jan 1995 12:17:01 -0500 (EST)
From: Adam J Weitzman <weitzman@individual.com>
To: Pine Mailing List <pine-info@cac.washington.edu>
Subject: Pine 3.91 is SLOW, unparseable date
Message-Id: <Pine.SUN.3.91.950125121107.28062A-100000@woolf.individual.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have finally gotten around to installing Pine 3.91 (on SunOS 4.1.3_U1) 
and have been using it in a testing situation for myself. I would like to 
replace the 3.07 that my site is using, except that this version of Pine 
is considerably slower in every respect. Is there any way to speed it up, 
or are there plans to do this in the future? I can't in good conscience 
replace the familiar (and reasonably speedy) 3.07 with this new release 
if it's going to slow everyone down, and I don't want to support two 
releases (one for those who want speed, one for those who want all the 
new features).

Also, is there any way to turn off the "Unparseable date" message that 
sometimes comes up when I open my INBOX? I truly don't care two whits if 
someone doesn't know how to configure their Internet gateway to properly 
generate RFC-821/822 email as long as it gets here in one piece.

                                        - Adam J Weitzman
                                          Individual, Inc.
                                          weitzman@individual.com



From owner-pine-info@cac.washington.edu  Wed Jan 25 09:44:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06461;
	Wed, 25 Jan 95 09:44:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05377;
	Wed, 25 Jan 95 09:34:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05371;
	Wed, 25 Jan 95 09:33:56 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 26 Jan 95 01:25:20 -0800
Date: Thu, 26 Jan 1995 01:25:19 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Ralf Matthies <matthies@rzserv2.fh-lueneburg.de>
Cc: Pete Holsberg <pjh@mccc.edu>, pine-info@cac.washington.edu
Subject: Re: Need HELP! BinHEX conversion?
In-Reply-To: <Pine.A32.3.91.950125161841.39801A-100000@rzserv2.fh-lueneburg.de>
Message-Id: <Pine.SOL.3.91.950126012323.29923D-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 25 Jan 1995, Ralf Matthies wrote:

> 
> On Tue, 24 Jan 1995, Pete Holsberg wrote:
> 
> > Ralf Matthies (matthies@rzserv2.fh-lueneburg.de) wrote:
> > : On 19 Jan 1995, Richard Hsiung wrote:
> > 
> > : > I got a mail from someone with an attachment (supposedly), well, in the 
> > : > message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
> > : > BinHex and how do I get this attachment back into file form?
> > 
> > : you will find BinHex on the following aFTP servers:
> > 
> > :               ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip
> > :               micros.hensa.ac.uk  /mirrors/simtel/msdos/mac/binhex13.zip
> > 
> > : PS: Ask me, if you have more questions... ;-)
> > 
> > 
> > OK. Where is BINHEX for Unix?
> 
> Hi,
> 
> as far as i know there is no equivalent program on UNIX platforms
> available (until yet).    :-(
> 

	Use archie to find the program called "mcvert".

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 25 09:54:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07062;
	Wed, 25 Jan 95 09:54:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05765;
	Wed, 25 Jan 95 09:49:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05759;
	Wed, 25 Jan 95 09:49:09 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXBXl-00038UC; Wed, 25 Jan 95 09:30 PST
To: pine-info@cac.washington.edu
From: hurtta@dionysos.fmi.fi (Kari E. Hurtta)
Subject: Re: Why Message-ID error???
Date: 25 Jan 1995 07:47:54 GMT
Message-Id: <3g4vna$jqu@kronos.fmi.fi>
References: <3g23sv$bq3@mars.mahidol.ac.th>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: Article <3g23sv$bq3@mars.mahidol.ac.th> of Tangsripairoj

ccsts@mucc.mahidol.ac.th (Songsri Tangsripairoj - CC) writes in 
comp.mail.sendmail:

»	I have just compile and config Sendmail8.6.9 for my host which 
»run on Solaris2.3. During this two days, I have tested it and I confront 
»with the problem that why the Message-ID is error.

»Message-ID: <Pine.SOL.3.91.950124122131.554A-100000@earth>

This Message-ID is generated by Pine -- it isn't generated by sendmail.

[ I will add comp.mail.pine as receiver. Perhaps Pine folks tell how to solve
  this error. ]

So your test mail don't indicate error in sendmail. 
--
- Kari E. Hurtta                             /  Elämä on monimutkaista
  Kari.Hurtta@Fmi.FI			     puh. (90) 1929 658
  {hurtta,root,Postmaster}@dionysos.fmi.fi


From owner-pine-info@cac.washington.edu  Wed Jan 25 09:56:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07137;
	Wed, 25 Jan 95 09:56:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06726;
	Wed, 25 Jan 95 09:49:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06720;
	Wed, 25 Jan 95 09:49:24 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 26 Jan 95 01:22:55 -0800
Date: Thu, 26 Jan 1995 01:22:54 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Dan Mullen <dmullen@gate.net>
Cc: pine-info@cac.washington.edu
Subject: Re: Re-Sending EMail??
In-Reply-To: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net>
Message-Id: <Pine.SOL.3.91.950126012119.29923C-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 25 Jan 1995, Dan Mullen wrote:

> What Pine command do I use to resend a previously sent message
> that has been returned due to Wrong Address or Server Error?
> 
> This has happened a couple ot times and had to retype the whole message 
> again. Suggestion Please!!

	Go to your "sent-mail" folder and "F"orward the message to the
proper address.

				Ed
		
Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 25 10:24:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08565;
	Wed, 25 Jan 95 10:24:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07554;
	Wed, 25 Jan 95 10:19:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07548;
	Wed, 25 Jan 95 10:19:16 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXC0T-00038UC; Wed, 25 Jan 95 09:59 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Signature and Finger FAQ
Date: 25 Jan 1995 02:31:20 GMT
Message-Id: <3g4d5o$49c@cronkite.ocis.temple.edu>

Comes here Mr/Mz. Phu Vu with this opinion in the "comp.mail.pine" group in this
article on 24 Jan 1995 18:30:17 GMT:

I can't believe you quoted the entire Signature Faq and posted to "n" groups.
FEDEx yourself a clue, please.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________
Talk about me doing the talking for others, esp. My Employers!!


From owner-pine-info@cac.washington.edu  Wed Jan 25 10:33:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09076;
	Wed, 25 Jan 95 10:33:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06625;
	Wed, 25 Jan 95 10:24:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06613;
	Wed, 25 Jan 95 10:24:15 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXC5Q-00038VC; Wed, 25 Jan 95 10:04 PST
To: pine-info@cac.washington.edu
From: pjh@mccc.edu (Pete Holsberg)
Subject: Pine Can't Find Me Tonight!!!
Message-Id: <D2xwst.ID6@mccc.edu>
Date: Wed, 25 Jan 1995 02:41:17 GMT

Get a load of this one!!


 Script started on Tue Jan 24 20:48:43 1995
 Executing the /home/pjh/.env file
 tecoma [pjh] 20:48 /home/pjh pts025> pine
 @0[?4s[?4h@1[25;1H

[m[A

@0[?4r

 Bug in Pine detected: "Unable to look up user in passwd file".
 Exiting pine.
 Abort(coredump)
 tecoma [pjh] 20:48 /home/pjh pts025> exit

 script done on Tue Jan 24 20:48:50 1995



 Didn't change a thing since the last time I used it, either!!

 Here's the debug file:

 Debug output of the Pine program (at debug level 2).  Version 3.91
 Tue Jan 24 20:48:47 1995

 reading_pinerc "/usr/local/lib/pine.conf"
 Read 6890 characters:
 reading_pinerc "/home/pjh/.pinerc"
 Read 9487 characters:
 reading_pinerc "/usr/local/lib/pine.conf.fixed"
 Open failed: No such file or directory
 Unrecognized feature in feature-list (signature-at-bottom.)
 ======= Current_val options set =======
           user-domain : mccc.edu
           smtp-server : tecoma.mccc.edu
           nntp-server : tecoma.mccc.edu
            inbox-path : inbox
    folder-collections : Mail/[]
      news-collections : *[]
           default-fcc : ""
      postponed-folder : postponed-msgs
        mail-directory : mail
        signature-file : .signature
          address-book : .addressbook
          feature-list : old-growth
                       : signature-at-bottom
                       : old-growth
                       : signature-at-bottom.
                       : enable-incoming-folders
                       : expanded-view-of-addressbooks
                       : expanded-view-of-folders
                       : expunge-without-confirm
                       : include-text-in-reply
                       : save-will-not-delete
                       : save-will-advance
                       : preserve-start-stop-characters
                       : news-post-without-validation
                       : news-read-in-newsrc-order
                       : compose-sets-newsgroup-without-confirm
                       : delete-skips-deleted
                       : show-selected-in-boldface
   saved-msg-name-rule : by-sender
         fcc-name-rule : default-fcc
              sort-key : arrival
    addrbook-sort-rule : fullname-with-lists-last
         character-set : ISO-8859-1
                editor : /opt/bin/emacs
          image-viewer : xv
  use-only-domain-name : true
               printer : jetpr | lp -dlj
  personal-print-comma : jetpr | lp -dlj
      standard-printer : lp
  last-time-prune-ques : 95.1
     last-version-used : 3.91
         bugs-fullname : Pine Developers
          bugs-address : pine-bugs@cac.washington.edu
        elm-style-save : no
       header-in-reply : no
         feature-level : sapling
       old-style-reply : no
        save-by-sender : no
 ======= Command_line_val options set =======
 ======= User_val options set (/home/pjh/.pinerc) =======
           user-domain : mccc.edu
           nntp-server : tecoma.mccc.edu
    folder-collections : Mail/[]
      news-collections : *[]
           default-fcc : ""
          feature-list : old-growth
                       : signature-at-bottom.
                       : enable-incoming-folders
                       : expanded-view-of-addressbooks
                       : expanded-view-of-folders
                       : expunge-without-confirm
                       : include-text-in-reply
                       : save-will-not-delete
                       : save-will-advance
                       : preserve-start-stop-characters
                       : news-post-without-validation
                       : news-read-in-newsrc-order
                       : compose-sets-newsgroup-without-confirm
                       : delete-skips-deleted
                       : show-selected-in-boldface
   saved-msg-name-rule : by-sender
         character-set : ISO-8859-1
                editor : /opt/bin/emacs
          image-viewer : xv
               printer : jetpr | lp -dlj
  personal-print-comma : jetpr | lp -dlj
  last-time-prune-ques : 95.1
     last-version-used : 3.91
 ======= Global_val options set (/usr/local/lib/pine.conf) =======
           user-domain : mccc.edu
           smtp-server : tecoma.mccc.edu
            inbox-path : inbox
           default-fcc : sent-mail
      postponed-folder : postponed-msgs
        mail-directory : mail
        signature-file : .signature
          address-book : .addressbook
          feature-list : old-growth
                       : signature-at-bottom
   saved-msg-name-rule : default-folder
         fcc-name-rule : default-fcc
              sort-key : arrival
    addrbook-sort-rule : fullname-with-lists-last
  use-only-domain-name : true
               printer : attached-to-ansi
      standard-printer : lp
         bugs-fullname : Pine Developers
          bugs-address : pine-bugs@cac.washington.edu
        elm-style-save : no
       header-in-reply : no
         feature-level : sapling
       old-style-reply : no
        save-by-sender : no
 ======= Fixed_val options set (NO pine.conf.fixed) =======
 ========== Feature settings ==========
   no-assume-slow-link
   no-auto-move-read-msgs
   no-auto-open-next-unread
   no-compose-rejects-unqualified-addrs
      compose-sets-newsgroup-without-confirm
      delete-skips-deleted
   no-disable-config-cmd
   no-disable-keyboard-lock-cmd
   no-disable-password-cmd
   no-disable-update-cmd
      enable-aggregate-command-set
      enable-alternate-editor-cmd
   no-enable-alternate-editor-implicitly
      enable-bounce-cmd
      enable-flag-cmd
      enable-full-header-cmd
      enable-incoming-folders
      enable-jump-shortcut
   no-enable-mail-check-cue
      enable-suspend
      enable-tab-completion
      enable-unix-pipe-cmd
      expanded-view-of-addressbooks
      expanded-view-of-folders
      expunge-without-confirm
   no-include-attachments-in-reply
   no-include-header-in-reply
      include-text-in-reply
   no-news-approximates-new-status
      news-post-without-validation
      news-read-in-newsrc-order
      preserve-start-stop-characters
   no-quell-user-lookup-in-passwd-file
      quit-without-confirm
   no-save-will-quote-leading-froms
      save-will-not-delete
      save-will-advance
   no-select-without-confirm
      show-selected-in-boldface
      signature-at-bottom
   no-use-current-dir
   no-use-function-keys
 Userid: pjh
 Fullname: "Pete Holsberg"
 User domain name being used "mccc.edu"
 Local Domain name being used "mccc.edu"
 Host name being used "tecoma.mccc.edu"
 Mail Domain name being used (by c-client too)"mccc.edu"
 Context Mail/[] type: LOCAL
 new win size -----<25 80>------
 Terminal type: xterm
 Context [] type: LOCAL


I am logged into an xterm window under the UnixWare Desktop's
"terminal" program. Could that make a difference???

Thanks.





From owner-pine-info@cac.washington.edu  Wed Jan 25 10:47:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09616;
	Wed, 25 Jan 95 10:47:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08093;
	Wed, 25 Jan 95 10:39:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08087;
	Wed, 25 Jan 95 10:39:14 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXCKK-00038OC; Wed, 25 Jan 95 10:20 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Take addr to dist list?
Date: 25 Jan 1995 02:49:20 GMT
Message-Id: <3g4e7g$49c@cronkite.ocis.temple.edu>

Comes here Mr. Jakob Schlyter with this opinion in the "comp.mail.pine" group in
this article on 24 Jan 1995 11:32:51 GMT:

 +   Is it possible to do a TakeAddr but add the address to a distribution
 +   list instead? If not, this would be a nice function to add (3.92?).

Here's how I do it in 3.91

T L A T nickname A

T - Take Address
L - List Mode
A - Select All
T - Take

Now at the enter nickname prompt, enter the nick of the existing list

A - Add or R for Replace.

Hope this helps.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Wed Jan 25 11:37:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12272;
	Wed, 25 Jan 95 11:37:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08312;
	Wed, 25 Jan 95 11:32:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08306;
	Wed, 25 Jan 95 11:32:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXDJF-00038OC; Wed, 25 Jan 95 11:23 PST
To: pine-info@cac.washington.edu
From: jmcging@access.digex.net (John McGing)
Subject: Re: Pine for OS/2 (!)
Date: 24 Jan 1995 22:37:57 -0500
Message-Id: <jmcging.791004970@access4>
References: <5f8_9501200953@dialis.xs4all.nl> <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org> <2f22a733.4d4f4d45@mome-raths.iac.net>

sysop@mome-raths.iac.net (March Hare) writes:

>Brent Blumenstein (brentb@orca.fhcrc.org) wrote:
>: Now that is good news.  When?  And are beta testers needed.  I volunteer.


>: > For those interested, I read that Steve Willer is currently porting the Pine
>: > reader to OS/2. At least there are some developments now...
>: > 

>Hi, I just got onto this list.  I'm told there is a general belief
>that there's no interest in a Pine port for OS/2.  I'm here to
>state that it's more likely that few OS/2 users know about this
>newsgroup/mailing-list.

Well, more likely since it's only since Warp came out that people cared 
:)  Previously, getting online with OS/2 cost a bit more.  But they are 
around now, I'm one of them and would love a pine port.

>BTW - I picked up on the OS/2 groups that a port of pico is 
>available ftp, which I'm using right now to write this message.
>It works pretty well.  I'm planning on using it for accessing
>UUCP news through my BBS.  Now, I just have to work ou

Is this on hobbes?  Where?  

>John

>--
>Mome Raths BBS                          General Pix, Adult Pix, Messages,
>(513)523-7887                           DOS, Windows and OS/2 programs,
>Oxford, Ohio                            12 Step echos and much more
-- 
------------------------------------------------------------------
jmcging@access.digex.net   Nobody knows the troubles I've seen
J.MCGING on GEnie              .... and nobody cares!
70142,1357 on Compuserve                              Team OS/2


From owner-pine-info@cac.washington.edu  Wed Jan 25 12:37:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15552;
	Wed, 25 Jan 95 12:37:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10811;
	Wed, 25 Jan 95 12:30:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10805;
	Wed, 25 Jan 95 12:30:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXE7J-00038PC; Wed, 25 Jan 95 12:15 PST
To: pine-info@cac.washington.edu
From: gerland@acsu.buffalo.edu (Jim Gerland)
Subject: Does Pine 3.91 have News Authentication?	
Message-Id: <D2yqMw.9sL@acsu.buffalo.edu>
Date: Wed, 25 Jan 1995 13:25:44 GMT


If not, is there plans to add it?
Thanks,

-- 
Jim Gerland  - Manager, Network Information Services    University at Buffalo
Academic Services, Computing & Information Technology   Buffalo, NY 14260
716.645.3557 Work                                       716.645.3734 FAX
gerland@acsu.buffalo.edu            URL: http://www.acsu.buffalo.edu/~gerland


From owner-pine-info@cac.washington.edu  Wed Jan 25 13:44:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19508;
	Wed, 25 Jan 95 13:44:26 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11278;
	Wed, 25 Jan 95 13:30:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11272;
	Wed, 25 Jan 95 13:30:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXF6Q-00038PC; Wed, 25 Jan 95 13:18 PST
To: pine-info@cac.washington.edu
From: ajdevoir@southern.edu (AJDevoir)
Subject: Re: Need to secure pine
Date: 25 Jan 1995 03:22:33 GMT
Message-Id: <3g4g5p$7ab@news.southern.edu>
References: <3g1e2s$5sk@case.cyberspace.com>

Jack Valko (valko@cyberspace.com) wrote:
> I would like to know if there is some way to set a configuration in pine 
> so that users can't change it from the Setup menu.  Specifically, I want 
> to restrict the alternate editor feature.  I have specified 
> 'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
> doesn't seem to do it.  Can anyone help?

> ==================================================
> Jack Valko           |       - Cyberspace -
> System Administrator | 300 Queen Anne Ave. N. #396 
> cyberspace.com       |   Seattle, WA 98109-4599 
> cyberspace.net       |       (206) 281-5397 
> ==================================================

Have you thought about just changing the file permissions on the .pinerc 
file?  (chmod 700 .pinerc)  Maybe i am just reading what you are after wrong,
but is it that people are just coming in and reconfiguring pine for you?
--
Armand Devoir
ajdevoir@ns.southern.edu
file://ns.southern.edu/people/ajdevoir/www/home.html



From owner-pine-info@cac.washington.edu  Wed Jan 25 13:46:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19614;
	Wed, 25 Jan 95 13:46:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12836;
	Wed, 25 Jan 95 13:38:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from digi.syd.deg.CSIRO.AU by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12830;
	Wed, 25 Jan 95 13:38:01 -0800
Received: by digi.syd.deg.csiro.au id AA13566
  (5.67b/IDA-1.5 for pine-info@cac.washington.edu); Thu, 26 Jan 1995 08:31:13 +1100
Date: Thu, 26 Jan 1995 08:28:59 +1100 (EST)
From: Jack Churchill <Jack.Churchill@dem.csiro.au>
Subject: Re: Need HELP! BinHEX conversion?
To: Ralf Matthies <matthies@rzserv2.fh-lueneburg.de>
Cc: Pete Holsberg <pjh@mccc.edu>, pine-info@cac.washington.edu
In-Reply-To: <Pine.A32.3.91.950125161841.39801A-100000@rzserv2.fh-lueneburg.de>
Message-Id: <Pine.3.07.9501260858.A12930-a100000@digi.syd.deg.csiro.au>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 25 Jan 1995, Ralf Matthies wrote:

> On Tue, 24 Jan 1995, Pete Holsberg wrote:
> 
> > Ralf Matthies (matthies@rzserv2.fh-lueneburg.de) wrote:
> > OK. Where is BINHEX for Unix?
> 
> Hi,
> 
> as far as i know there is no equivalent program on UNIX platforms
> available (until yet).    :-(

There're VMS and unix versions of a BinHex converter. I fetched the unix
one from the NYU archives some years ago (ftp.med.nyu.edu).  Works well
both ways. 

--
  Jack N. Churchill                         | Jack.Churchill@dem.csiro.au
  CSIRO  Division of Exploration and Mining | http://www.csiro.au
  PO Box 136  North Ryde  NSW  2113         | Phone:  +61 2 887 8884
  Australia                                 | Fax:    +61 2 887 8921



From owner-pine-info@cac.washington.edu  Wed Jan 25 13:48:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19657;
	Wed, 25 Jan 95 13:48:00 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12910;
	Wed, 25 Jan 95 13:40:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12904;
	Wed, 25 Jan 95 13:40:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXFGM-00038TC; Wed, 25 Jan 95 13:28 PST
To: pine-info@cac.washington.edu
From: "Amy L. Lauderdale" <laall@cotton.vislab.olemiss.edu>
Subject: Using Windows
Date: Wed, 25 Jan 1995 07:38:42 -0600 (CST)
Message-Id: <Pine.SUN.3.90.950125073649.1567C-100000@cotton.vislab.olemiss.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I use telix to connect to my local university and use pine from that
system.  I have a student who is using the windows terminal software
to connect from home.  I tried it here on my computer to try to
help her learn.

There are a couple of problems we ran into.  It will not let us use
the arrow keys in pine.  And it will not let us use ^C to cancel
a message.

Any suggestions?

************************************************************
Amy Lauderdale/Math Teacher
Lafayette High School/Northwest Community College
Oxford, MS          laall@cotton.vislab.olemiss.edu
************************************************************



From owner-pine-info@cac.washington.edu  Wed Jan 25 15:05:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24159;
	Wed, 25 Jan 95 15:05:05 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13505;
	Wed, 25 Jan 95 15:01:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13497;
	Wed, 25 Jan 95 15:01:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXGTL-00038OC; Wed, 25 Jan 95 14:45 PST
To: pine-info@cac.washington.edu
From: oecheruo@forbin.syr.edu (Okechukwu Chima Echeruo)
Subject: Can your EMAIL system do this?
Date: 25 Jan 1995 19:11:50 GMT
Message-Id: <3g67pm$4s7@newstand.syr.edu>

Hi,

I was wondering if there are any mail systems for UNIX<->PC that have these
features. 

Client/Server

100% Server based. Everything is stored on the server such that I can
access all my mail as well as my saved folders and address books from my
client. Since it is TCP/IP based I can access my mail from any node on the
internet without logging into the mail server directly.

UNIX text/ UNIX X Windows/ PC Windows/OS2/Mac(?) mail clients?

Supports SMTP, Novell, POP and IMAP(?) gateways so that I can use one mail
program to read/save all my EMAIL regardless of it's origin.

Does not depend on shared filesystem access (Novell, MSMAIL PO) so that I can
access my mail remotely using SLIP or dialup/terminal (UNIX text client).

Pegasus Mail for windows is the only program that I've used that allows me
to read both my Novell mail as well as my UNIX mail. However it saves
everything locally on my hard drive (work,ethernet) and so I cannot either
my address book or folders when I'm at home (SLIP).

Such a system as I describe will allow students to read their mail from any
machine without a need to create accounts on Novell servers or provide
remote Novell dialup access.

We are currently using PINE and Pegasus Mail (UNIX,Windows,Mac).

Thanks.





From owner-pine-info@cac.washington.edu  Wed Jan 25 15:32:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25698;
	Wed, 25 Jan 95 15:32:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15554;
	Wed, 25 Jan 95 15:26:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15548;
	Wed, 25 Jan 95 15:26:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXGtX-00038CC; Wed, 25 Jan 95 15:12 PST
To: pine-info@cac.washington.edu
From: courcoul@campus.qro.itesm.mx (Juan M. Courcoul)
Subject: Usenet group moderation using Pine
Date: Wed, 25 Jan 1995 13:45:31 -0600
Message-Id: <courcoul-2501951345310001@trantor.qro.itesm.mx>

Is there any way to ease the moderation of Usenet newsgroups, when using Pine ?

As you know, when you are the moderator of a newsgroup, all mail sent to
the group gets forwarded to you, so that you can attach an "Approved:
<your address>" tag in the header and send it back to the server.

So far, what I have done is defined the "Approved" tag via customized
headers, and have to forward the messages, using rich headers so that I
can fill in the newsgroup and leave the To: tag blank.

Is there any trick to simplify this ? Ideally, a sort of "newsbounce"
command that automagically added the missing tag, but kept the original
header as-is, while allowing you to make any desired changes to the body
text would be ideal, but I haven't found it yet amongst Pine's hundreds of
goodies.

Thanks for any pointers.

-- 
Juan M. Courcoul                       courcoul@campus.qro.itesm.mx
Instituto Tecnologico de Monterrey     courcoul@itesmcq1.qro.itesm.mx
Campus Queretaro


From owner-pine-info@cac.washington.edu  Wed Jan 25 17:25:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01293;
	Wed, 25 Jan 95 17:25:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18321;
	Wed, 25 Jan 95 17:21:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18315;
	Wed, 25 Jan 95 17:21:22 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXIis-00038UC; Wed, 25 Jan 95 17:10 PST
To: pine-info@cac.washington.edu
From: penev@pisa.Rockefeller.edu (Penio Penev)
Subject: Re: Pine compiled for silicon graphics????
Message-Id: <D2xq45.I15@rockyd.rockefeller.edu>
References: <3g0q07$qo2@abalone.ucsb.edu>
Date: Wed, 25 Jan 1995 00:16:53 GMT

On 23 Jan 1995 09:45:43 -0800 Joyce Y. Wong (jywong@abalone.ucsb.edu) wrote:
| I am looking for pine compiled for a silicon graphics machine
| running irix 4.0

ftp://venezia.rockefeller.edu/pub/penev/IRIX4/pine-3.91

--
Penio Penev <Penev@venezia.Rockefeller.edu> 1-212-327-7423


From owner-pine-info@cac.washington.edu  Wed Jan 25 17:25:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01320;
	Wed, 25 Jan 95 17:25:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16948;
	Wed, 25 Jan 95 17:21:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16942;
	Wed, 25 Jan 95 17:21:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXIgv-00038PC; Wed, 25 Jan 95 17:08 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: 25 Jan 1995 02:05:14 GMT
Message-Id: <3g4bkq$49c@cronkite.ocis.temple.edu>

Comes here Mr. Lee (not F) Bailey with this opinion in the "comp.mail.pine"
group in this article on 24 Jan 1995 15:34:15 GMT:

 +   I admit these files could be useful, but they clutter up my dir listing. 
 +   Is there a way to redirect them to a folder?

You should define these in the os-xxx.h file in the osdep dir and re-compile.

        #define DEBUGFILE	    ".pine-debug"

For that option you could perhaps put $HOME/.pinedebug/.pine-debug
or whatever is convienient.

        #define NUMDEBUGFILES 4

You can also re-define the number of debug files pine produces.

But then again, the Pine Team has optimized the code so well, so why bother eh!

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Wed Jan 25 17:55:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02494;
	Wed, 25 Jan 95 17:55:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17528;
	Wed, 25 Jan 95 17:48:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17522;
	Wed, 25 Jan 95 17:48:20 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXIxd-00039MC; Wed, 25 Jan 95 17:25 PST
To: pine-info@cac.washington.edu
From: the mole <markusg@darkwing.uoregon.edu>
Subject: Re: Random .sig?
Date: Wed, 25 Jan 1995 11:09:20 -0800
Message-Id: <Pine.SOL.3.91.950125102951.3911D-100000@darkwing>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g3ogs$jkn@nic.iii.net> 

On 24 Jan 1995, Steve Bernacki Jr wrote:

> Howdy y'all,
> 
> Is it possible to somehow have a random signature (out of a directory of
> signatures) be selected and pasted into pine?  If not, is there any way
> to get pine to run a program that would output such a random sig?
> 
> Thanks!
> -S
> --
> Steve Bernacki, Jr.  | unix programmer/ moxie drinker
> Email: drown@iii.net | http://www.iii.net/users/drown.html

Hi!

What I do is run a perl script that writes a random quota to .signature 
before starting pine (actually it writes to stdout but I redirect it to 
.signature).
here's the script:

#!/your/path/to/perl
srand(time ^ $$);
undef $/;
@sigs = split("\n%%\n", <DATA>);
# open(SIG, ">.signature");           
# uncomment above line should it write directly to .signature
print $sigs[rand(@sigs)], "\n";
# above line prints to stdout
# print SIG $sigs[rand(@sigs)], "\n";
# uncomment above line should it write directly to .signature
__END__
--
witty .sig
%%
--
another witty .sig
%%
--
and so on
%%

The sigs are part of the script. I have no experience with perl, but this 
thing works. I have another simple shell script which re-establishes my 
regular sig, this script is called 'regsig'.
I invoke Pine with:
  perl rndsig ; pine ; perl regsig

The original perl script had been posted by somebody either in 
comp.mail.misc or in comp.mail.pine.

Enjoy,

tm
--
      /               . . . . . . . . . . . . . . . . . . . . . . . . . . .
__  __/   __  __     . . . . . . . . . . . . . . . . . . . . . .  the mole
   /     /   /   /  . . . . . . . . . . . .  markusg@darkwing.uoregon.edu
__/   __/ __/ __/  . . . . . . . . http://darkwing.uoregon.edu/~markusg/






From owner-pine-info@cac.washington.edu  Wed Jan 25 18:09:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02975;
	Wed, 25 Jan 95 18:09:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19231;
	Wed, 25 Jan 95 18:06:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19225;
	Wed, 25 Jan 95 18:06:09 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXJPH-00038OC; Wed, 25 Jan 95 17:53 PST
To: pine-info@cac.washington.edu
From: the mole <markusg@darkwing.uoregon.edu>
Subject: Re: Random .sig?
Date: Wed, 25 Jan 1995 11:17:59 -0800
Message-Id: <Pine.SOL.3.91.950125111206.9278B-100000@darkwing>
References: <Pine.SOL.3.91.950125102951.3911D-100000@darkwing>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SOL.3.91.950125102951.3911D-100000@darkwing> 

follow up:
sorry, two typos in my recent posting/reply:

  the script doesn't write 'a quota' but a quote to .signature
and
  to use it one should type
    rm -f .signature ; perl rndsig > .signature ; pine ; perl stdsig

(there a lots of other ways, eg. pine can be started with an option to 
read another sig)

Yours,
tm
--
      /               . . . . . . . . . . . . . . . . . . . . . . . . . . .
__  __/   __  __     . . . . . . . . . . . . . . . . . . . . . .  the mole
   /     /   /   /  . . . . . . . . . . . .  markusg@darkwing.uoregon.edu
__/   __/ __/ __/  . . . . . . . . http://darkwing.uoregon.edu/~markusg/



From owner-pine-info@cac.washington.edu  Wed Jan 25 18:11:07 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03036;
	Wed, 25 Jan 95 18:11:07 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19263;
	Wed, 25 Jan 95 18:07:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from pennet.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19257;
	Wed, 25 Jan 95 18:07:08 -0800
Received:  by pennet.com (5.65/1.2-eef)
	id AA09709; Wed, 25 Jan 95 21:04:36 -0500
Date: Wed, 25 Jan 1995 21:04:35 -0500 (EST)
From: Chuck Baugh <crbaugh@pennet.com>
To: pine-info@cac.washington.edu
Subject: SCO Ports
Message-Id: <Pine.SCO.3.91.950125205802.9679A-100000@pennet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Here is a list of sites that offer sco ports:


ftp.c-mols.siu.edu:	/pub/sco-ports
ftp.celestial.com
ftp.hookup.net:	/pub/sco
ftp.pczz.msk.su: 		/pub/vendors/sco
ftp.sco.com
ftp.uu.net:			/vendors/sco
ftp.wang.com:			/pub/sco
ftp.wimsey.com:			/pub/SCO and /pub/wimseypd
ftp.xenitec.on.ca:		(narrow bandwidth)
kuso.shef.ac.uk:		/pub/sco
odi.cwc.whecn.edu:              /pub/sco-ports (The machine you are on).
pub.vse.cz:			/pub/vendors/SCO
sco-archive.maxcy.brown.edu:	/pub/anomaly-mirror
soils.agron.iastate.edu:	/pub/sco (I think this machine is dead).
sosco.sco.com
src.doc.ic.ac.uk:		/computing/systems/unix/sco-archive
unix.secs.oakland.edu:		/pub/xenix


Chuck









From owner-pine-info@cac.washington.edu  Wed Jan 25 19:25:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05402;
	Wed, 25 Jan 95 19:25:13 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19145;
	Wed, 25 Jan 95 19:21:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19139;
	Wed, 25 Jan 95 19:21:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXKY5-00038OC; Wed, 25 Jan 95 19:07 PST
To: pine-info@cac.washington.edu
From: rick@helix.nih.gov (Rick Troxel)
Subject: Slow screen updates affect one user
Message-Id: <RICK.95Jan25144650@helix.nih.gov>
Date: Wed, 25 Jan 1995 19:46:50 GMT

Of about 2500 users on this SGI, one pine (v3.91) user reports the
following symptoms over a high speed modem connection.  Can anyone
suggest a diagnosis and cure?

   A symptom which is still reliably exhibited in PINE can be done by
   rapidly pressing the down arrow 5 times.  At best, I get all 5
   keypresses in before any response from pine, then pine rapidly moves
   down the mail list EXCEPT that the response to the last keystroke is
   delayed by about 1-2sec.  This is the type of behavior I experienced
   [earlier] but then it was much much more pronounced (2-10sec). It
   works for fewer and more keypresses, and it seems to be there for a
   single keypress, its just not that noticeable under best response
   conditions.

He doesn't say so explicitly, but evidently he's in the folder Index
screen.  The problem appears to be independent of comm programs, and it
does not occur with gopher, another curses based program on the system.

Thanks for any help,
--
-- 
Rick Troxel     Rick_Troxel@nih.gov     rick@helix.nih.gov     301/496-4823
///////////////////////////////////////////////////////////////////////////
     All effort and exertion put forth by man from the fullness of his
     heart is worship, if it  is prompted  by the  highest motives and
     the will to do service to humanity.                 --Abdu'l-Baha


From owner-pine-info@cac.washington.edu  Wed Jan 25 19:26:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05457;
	Wed, 25 Jan 95 19:26:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20598;
	Wed, 25 Jan 95 19:21:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20592;
	Wed, 25 Jan 95 19:21:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXKZu-00038PC; Wed, 25 Jan 95 19:08 PST
To: pine-info@cac.washington.edu
From: jims@garnet.msen.com (Jim Schueler)
Subject: Pipe command in 3.91
Date: 25 Jan 1995 19:51:13 GMT
Message-Id: <3g6a3h$hum$1@heifetz.msen.com>

Any idea why the command | sz - doesn't work on a machine running BSDI 1.1?

I get an unusual response that looks exactly like this:
	?]?????????0000000E Result: rz

'cat myfile | sz -' works fine at the Unix (bash) prompt.

On similar machines, the pipe command works flawlessly.

Any thoughts would be greatly appreciated.

 -Jim


From owner-pine-info@cac.washington.edu  Wed Jan 25 19:34:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05676;
	Wed, 25 Jan 95 19:34:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19297;
	Wed, 25 Jan 95 19:31:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19291;
	Wed, 25 Jan 95 19:31:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXKk4-00038SC; Wed, 25 Jan 95 19:19 PST
To: pine-info@cac.washington.edu
From: mgraham@s-cwis.unomaha.edu (Michael J. Graham)
Subject: Pine Faq
Date: 25 Jan 1995 17:33:39 GMT
Message-Id: <3g621j$hes@s-cwis.unomaha.edu>


hello
	Just wondering where I could find a faq for pine?
			Thanx
				-Mike

-- 

		-Mike
	mgraham@s-cwis.unomaha.edu
         GO HUSKERS!!!!!!!!!!!!!!!!!


From owner-pine-info@cac.washington.edu  Wed Jan 25 21:54:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09471;
	Wed, 25 Jan 95 21:54:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22816;
	Wed, 25 Jan 95 21:51:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22810;
	Wed, 25 Jan 95 21:51:32 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXMsO-00038RC; Wed, 25 Jan 95 21:36 PST
To: pine-info@cac.washington.edu
From: mike@newport.lib.ca.us (Micheal Wojciechowski)
Subject: I renamed and made PICO an executable but still no luck
Date: 26 Jan 1995 01:02:47 GMT
Message-Id: <3g6sbn$fet@nic-nac.CSU.net>

As the subject header says I renamed pico-bin.hpux9 and made it an executable
but I get a message back that says "ksh: pico: cannot execute"  Does anyone have
any clue as to what I need to do.  Does it need to be compiled?

Thanks in advance.

Mike


From owner-pine-info@cac.washington.edu  Wed Jan 25 22:04:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09763;
	Wed, 25 Jan 95 22:04:00 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21664;
	Wed, 25 Jan 95 22:01:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21658;
	Wed, 25 Jan 95 22:01:35 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXN27-00038TC; Wed, 25 Jan 95 21:46 PST
To: pine-info@cac.washington.edu
From: Dan <df@hopper.unh.edu>
Subject: Where Joe?
Date: Wed, 25 Jan 1995 17:44:47 -0500
Message-Id: <Pine.OSF.3.91a.950125174230.18110F-100000@hopper.unh.edu>
References: <3fkosh$ouc@j51.com> <3fuu8e$7de@news.primenet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fuu8e$7de@news.primenet.com> 


Okay. I got Joe, I installed it (I think), and if I load Pine from the 
joe directory I can actually use it. (I am trying to emulate WordStar so 
I don't use the wrong commands in word processing and email letter 
writing, as now happens.)

I don't understand. Should I put joe in my main directory? Or can I 
somehow tell Pine where to find joe?

                 - Dan    <dan.ford@unh.edu>



From owner-pine-info@cac.washington.edu  Wed Jan 25 22:24:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10466;
	Wed, 25 Jan 95 22:24:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23320;
	Wed, 25 Jan 95 22:21:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23314;
	Wed, 25 Jan 95 22:21:47 -0800
Received: by hobbes.twntpe.cdc.com; Thu, 26 Jan 95 14:20:05 -0800
Date: Thu, 26 Jan 1995 14:20:04 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: Micheal Wojciechowski <mike@newport.lib.ca.us>
Cc: pine-info@cac.washington.edu
Subject: Re: I renamed and made PICO an executable but still no luck
In-Reply-To: <3g6sbn$fet@nic-nac.CSU.net>
Message-Id: <Pine.SOL.3.91.950126141925.8733H-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 26 Jan 1995, Micheal Wojciechowski wrote:

> As the subject header says I renamed pico-bin.hpux9 and made it an executable
> but I get a message back that says "ksh: pico: cannot execute"  Does anyone have
> any clue as to what I need to do.  Does it need to be compiled?

	When you ftp that file from ftp.cac.washington.edu did you make
sure that your ftp'd in "binary" mode?

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Wed Jan 25 23:51:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12456;
	Wed, 25 Jan 95 23:51:37 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24467;
	Wed, 25 Jan 95 23:48:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mail.Germany.EU.net by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24461;
	Wed, 25 Jan 95 23:48:37 -0800
Received: by mail.Germany.EU.net with UUCP (8.6.5:29/EUnetD-2.5.1.c) via EUnet
	id IAA01323; Thu, 26 Jan 1995 08:50:21 +0100
Received: from sunshine.fz.telekom.de (sunshine.fz.telekom.de [192.166.56.22]) by eunetgate.fz.telekom.de (8.6.5/8.6.5) with ESMTP id IAA01032 for <pine-info@cac.washington.edu>; Thu, 26 Jan 1995 08:32:32 +0100
Received: from sun51.fz.telekom.de (sun51.fz.telekom.de [192.166.56.95]) by sunshine.fz.telekom.de (8.6.9/8.6.9) with SMTP id IAA05611 for <pine-info@cac.washington.edu>; Thu, 26 Jan 1995 08:34:26 +0100
Received: by sun51.fz.telekom.de (4.1/SMI-4.1)
	id AA18213; Thu, 26 Jan 95 08:34:48 +0100
Date: Thu, 26 Jan 1995 08:34:48 +0100 (MET)
From: Ralf Widera <widera@fz.telekom.de>
Reply-To: widera@fz.telekom.de
To: pine-info@cac.washington.edu
Subject: Re: Take addr to dist list?
In-Reply-To: <3g4e7g$49c@cronkite.ocis.temple.edu>
Message-Id: <Pine.SUN.3.91.950126083331.18205A-100000@sun51.fz.telekom.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 25 Jan 1995, Wet-Sprocket wrote:

>  +   Is it possible to do a TakeAddr but add the address to a distribution
>  +   list instead? If not, this would be a nice function to add (3.92?).
> 
> Here's how I do it in 3.91
> 
> T L A T nickname A
> 
> T - Take Address
> L - List Mode
> A - Select All
> T - Take
> 
> Now at the enter nickname prompt, enter the nick of the existing list
> 
> A - Add or R for Replace.

I have tried this one, but it works only if you take the address out of a
message addressed to more than one recipient. Only in this case can you
switch to List Mode.
 
Is there a way to TakeAddr to a list, when I am the only recipient?
  
-raw

---------------------------------------------------------------------------
Ralf Widera, FZ 211b                            Email: widera@fz.telekom.de
Deutsche Telekom AG                             phone: +49 6151 83 3855
Forschungs- und Technologiezentrum              FAX  : +49 6151 83 4066
Postfach 10 00 03
D-64276 Darmstadt, Germany



From owner-pine-info@cac.washington.edu  Thu Jan 26 00:04:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12832;
	Thu, 26 Jan 95 00:04:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24667;
	Thu, 26 Jan 95 00:01:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24661;
	Thu, 26 Jan 95 00:01:47 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXOvE-00038SC; Wed, 25 Jan 95 23:47 PST
To: pine-info@cac.washington.edu
From: l36867@ci.ist.utl.pt (Nuno Filipe M M Godinho)
Subject: NG: Where is pine for term?
Date: 26 Jan 1995 01:09:03 GMT
Message-Id: <3g6snf$h9t@alfa.ist.utl.pt>

Hi.
Is there any version of pine for term? (the linux modem multiplexer)
I mean, there is tMosaic, tlynx, tncftp...
Do you know of any tpine available?

thanks



From owner-pine-info@cac.washington.edu  Thu Jan 26 00:41:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13663;
	Thu, 26 Jan 95 00:41:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23775;
	Thu, 26 Jan 95 00:38:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23769;
	Thu, 26 Jan 95 00:38:09 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXPSp-00038QC; Thu, 26 Jan 95 00:21 PST
To: pine-info@cac.washington.edu
From: ccurtis@ee.fit.edu (Christopher W. Curtis)
Subject: Re: Non-standard INBOX locations and pine
Message-Id: <ccurtis.791079010@ee.fit.edu>
References: <vzvzD2w73C.1M9@netcom.com>
Date: Thu, 26 Jan 1995 00:10:10 GMT

In <vzvzD2w73C.1M9@netcom.com> vzvz@netcom.com (Philip Zeyliger) writes:

>Some users are reporting that pine doesn't see their INBOX'es.
>The inboxes are located at $HOME/.mailbox/inbox.

We have the same problem here, but it only materializes when using PINE.
Elm sees the real INBOX without any troubles whatsoever, I guess further
showing that "Pine Is Not Elm".  It is annoyong when this happens and we do
not wish to dedicaate the resources to rewriting everyone's login script to
alleviate the problem.  Perhaps the PINE developers should look how Elm
handles the situation and copy it; or at least parse the /etc/alias file to
find the REAL inbox.  Just a suggestion...
--
T |        Christopher Curtis       |  There are two rules to follow   | O
E |   Sun Lab System Administrator  |  to ensure success in life:      | S
A | Florida Institute of Technology |  Rule 1:  Don't tell people      | /
M |       Melbourne, Florida       N|N          everything you know.   | 2


From owner-pine-info@cac.washington.edu  Thu Jan 26 01:12:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14614;
	Thu, 26 Jan 95 01:12:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24186;
	Thu, 26 Jan 95 01:06:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from psws.uia.ac.be by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24180;
	Thu, 26 Jan 95 01:06:08 -0800
Received: from localhost by psws.uia.ac.be (8.6.4/Ultrix3.0-C)
	id KAA23679; Thu, 26 Jan 1995 10:15:01 +0100
Date: Thu, 26 Jan 1995 10:15:01 +0100 (MET)
From: "Bertel.DeGroote" <dgroote@psws.uia.ac.be>
To: pine-info@cac.washington.edu
Subject: Bug Report: Addressbook - pine
Message-Id: <Pine.ULT.3.90.950126101259.23649A-100000@psws.uia.ac.be>
Mime-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1035739271-791055854=:21944"
Content-Id: <Pine.ULT.3.90.950126101259.23649B@psws.uia.ac.be>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1035739271-791055854=:21944
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.90.950126101259.23649C@psws.uia.ac.be>


Hallo,

I tried to create an Adressbook and to take the the adresses out of the 
messages I received and put them in the Adressbook.

When I try  usin, updatin, renaming the Adressbook or I want to correct 
the adresses/names, I somehow create problems.

I can't open the Adressbook

and the application blocks.

On my screen I See : Adressbook changed by another process re-syncing
		
		     Resetting Adress.book
	
And I have to reset the computer (warm .start)

Can you help me and send me also some easy understandable step by 
step information -while I'm not acquainted with computers- relating to the 
use of the Adressbook.

Thank you in advance for your benevolent help.



Bertel De Groote

dgroote@uia.ac.be



			  
--0-1035739271-791055854=:21944--


From owner-pine-info@cac.washington.edu  Thu Jan 26 02:59:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16814;
	Thu, 26 Jan 95 02:59:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25423;
	Thu, 26 Jan 95 02:48:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25417;
	Thu, 26 Jan 95 02:48:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXRbi-00038MC; Thu, 26 Jan 95 02:39 PST
To: pine-info@cac.washington.edu
From: Alan Agnew <agnew@maize.qut.edu.au>
Subject: Re: Pine/VMS
Date: Wed, 25 Jan 1995 10:33:46 +1000
Message-Id: <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu> <1995Jan14.220520@cchs.su.edu.au>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <1995Jan14.220520@cchs.su.edu.au> 

In a previous posting it was stated that PINE 3.91  for VMS is available
from lenin.cc.rochester.edu.

I have been attempting to connect to lenin.cc.rochester.edu from Australia
for several days now, but have never suceeded.

A ping shows 100% packet loss.

A traceroute gets as far as taylor4-bbgw.utd.rochester.edu and then nothing.

Is there a known difficulty in connecting to lenin.cc.rochester.edu?

Does anyone else have this version of PINE on an anonymous FTP  server?


	Alan Agnew
	Network Services
	Computing Services
	Queensland University of Technology

	Phone: (07) 864 1703		E-Mail: A.Agnew@qut.edu.au


From owner-pine-info@cac.washington.edu  Thu Jan 26 03:00:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16852;
	Thu, 26 Jan 95 03:00:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26939;
	Thu, 26 Jan 95 02:53:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26933;
	Thu, 26 Jan 95 02:53:56 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXRhG-00038TC; Thu, 26 Jan 95 02:45 PST
To: pine-info@cac.washington.edu
From: Arcin Bozkurt <arcin@ug.bcc.bilkent.edu.tr>
Subject: some news folders disapper !! HELP
Date: Wed, 25 Jan 1995 23:53:02 +0300 (EET)
Message-Id: <Pine.SUN.3.90.950125232938.14792A-100000-100000-100000@trabzon>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



	Hi,all !!
	I am using Pine 3.90 and I have a problem with my news folders.
The problem is that my folders disappear after i read another folder.
Strange isn't it ?
	Here is the story ...
	I am at the moment subscribed to comp.mail.pine and 
comp.mail.misc. In another pine window i subscribed to sci.space read two 
news there and deleted those two news i read. Then i pressed L to turn 
back to folder list.
	What do you i see at the window? Only sci.space!! The other two 
folders are lost. I happens all the time and i do not the way out.
	I also looked at my .newsrc file. It only contains the following 
after the operation :

sci.space:

	Can anyone with this peculiar behaviour of Pine 3.90.
	Thank you very much in advance .

					Arcin Bozkurt
					Bilkent University
					EE - Junior




From owner-pine-info@cac.washington.edu  Thu Jan 26 03:00:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16928;
	Thu, 26 Jan 95 03:00:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26849;
	Thu, 26 Jan 95 02:45:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26843;
	Thu, 26 Jan 95 02:45:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXRVP-00038VC; Thu, 26 Jan 95 02:32 PST
To: pine-info@cac.washington.edu
From: Joe Ducharme <jduche@creighton.edu>
Subject: Error Posting 441...
Date: Wed, 25 Jan 1995 15:35:04 -0600
Message-Id: <Pine.HPP.3.91.950125153315.12509D-100000@bluejay.creighton.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Why is it (only sometimes, mind you) I get this error when trying to post 
to a newsgroup using pine:

Error Posting 441: Article not posted-- more included text than new text

What the heck is pine trying to tell me? 

*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*
*:  Joe Ducharme                 jduche@creighton.edu      :* 
*:  Creighton University         Omaha, NE USA  68178      :*  
*:           << Joe's Roadside Attraction >>               :*
*:     << http://bluejay.creighton.edu/~jduche/ >>         :*
*: "Time flies like an arrow, Fruit flies like a banana."  :*
*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*



From owner-pine-info@cac.washington.edu  Thu Jan 26 03:23:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17594;
	Thu, 26 Jan 95 03:23:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25801;
	Thu, 26 Jan 95 03:18:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25795;
	Thu, 26 Jan 95 03:18:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXS5O-00038MC; Thu, 26 Jan 95 03:09 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Error Posting 441...
Date: 26 Jan 1995 02:36:16 GMT
Message-Id: <3g71r0$g1p@cronkite.ocis.temple.edu>

Comes here Mr. Joe Ducharme with this opinion in the "comp.mail.pine" group in
this article on Wed, 25 Jan 1995 15:35:04 -0600:

 +   Why is it (only sometimes, mind you) I get this error when trying to post 
 +   to a newsgroup using pine:

 +   Error Posting 441: Article not posted-- more included text than new text

Error Posting 441: This is the error message you will get when your newserver
has 1- run out of diskspace, 2- posting locked, due to fresh newsfeed 3- when
the newserver is updating filetables. As this has nothing to do with Pine, your
local news admin should be notified about this posting-error.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________
Talk about me doing the talking for others, esp. My Employers!!


From owner-pine-info@cac.washington.edu  Thu Jan 26 03:27:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17704;
	Thu, 26 Jan 95 03:27:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27363;
	Thu, 26 Jan 95 03:23:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27357;
	Thu, 26 Jan 95 03:23:56 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXSAP-00038QC; Thu, 26 Jan 95 03:15 PST
To: pine-info@cac.washington.edu
From: Clif Daniel <cdaniel@tyrell.net>
Subject: PINE-Win DLL and/or Code ?
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SUN.3.91.950125164015.15472C-100000@tyrell.net>
Mime-Version: 1.0
Date: Wed, 25 Jan 1995 22:49:48 GMT

 I run a Windows network which supports a multi-node BBS based on PowerBBS
for Windows. 
 I really like PCPine and use it personally whether over SLIP/PPP or logged
on to a providers UNIX system.
 PowrBBS for Windows has the capability of calling Windows Apps when they
are compiled as *.DLL. There are Telnet,FTP,and a few database and BBS door
type *.DLL apps available, well back to the real purpose for posting :

 I would love to be able to allow the dial-up BBS users to use PCPine for
a news / mail reader while on-line .... I'm sure that other PowerBBS
for Windows Administrators would be interested. 


From owner-pine-info@cac.washington.edu  Thu Jan 26 04:44:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19956;
	Thu, 26 Jan 95 04:44:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27019;
	Thu, 26 Jan 95 04:39:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27013;
	Thu, 26 Jan 95 04:39:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXTHU-00038QC; Thu, 26 Jan 95 04:26 PST
To: pine-info@cac.washington.edu
From: Selcuk Ozturk <selcuk@econ5.econ.pitt.edu>
Subject: Re: Error Posting 441...
Date: Wed, 25 Jan 1995 22:25:59 EST
Message-Id: <2592@econ5.econ.pitt.edu>
References: <3g71r0$g1p@cronkite.ocis.temple.edu>
In-Reply-To: your message of Thu Jan 26 02:36:16 1995

> +   Error Posting 441: Article not posted-- more included text than new text
>
>Error Posting 441: This is the error message you will get when your newserver
>has 1- run out of diskspace, 2- posting locked, due to fresh newsfeed 3- when
>the newserver is updating filetables. As this has nothing to do with Pine, your
>local news admin should be notified about this posting-error.

In this case the server does not accept the post since 
there are more quoted text then new text, as it says
in the above error message already.

I have the same problem here. I guess some news servers
have implemented some kind of a check for '>' chars in
the first line so as to keep the messages short. It's 
annoying. But I guess it can be circumvented by changing
the quotation method from '>' to something else. 
But, Pine has not an option to change this.

So, basically this is not a pine problem but, this might
be a good reason to make the quotation char optional in
future releases.

Selcuk



From owner-pine-info@cac.washington.edu  Thu Jan 26 05:43:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21559;
	Thu, 26 Jan 95 05:43:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27868;
	Thu, 26 Jan 95 05:38:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from Emerald.Tufts.EDU by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27862;
	Thu, 26 Jan 95 05:38:29 -0800
Received: (from pstott@localhost) by emerald.tufts.edu (8.6.9/8.6.9) id IAA29953; Thu, 26 Jan 1995 08:38:29 -0500
Date: Thu, 26 Jan 1995 08:38:28 -0500 (EST)
From: Peter Stott <pstott@emerald.tufts.edu>
To: Pine-Info <pine-info@cac.washington.edu>
Subject: PC-PINE and attachments
Message-Id: <Pine.OSF.3.91.950126083215.4625A-100000@emerald.tufts.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Friends,
I have been an enthusiastic user of pine on a unix machine for over
a year. I have just installed pc-pine 3.91 for windows. It seems to
work well... But --

I'm having troubling attaching files that reside on my hard disk or
floppy. The program clearly recognizes the file when I type the path
and file name into the 'attachment' line -- but when I am ready to
send the message, and hit ^X -- pine beeps twice and doesn't send
the message. The only way out is to cancel the message.

Have I misunderstood something here?

Many thanks

Peter Stott
pstott@tufts.edu



From owner-pine-info@cac.washington.edu  Thu Jan 26 08:04:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25007;
	Thu, 26 Jan 95 08:04:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29930;
	Thu, 26 Jan 95 07:57:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29924;
	Thu, 26 Jan 95 07:57:29 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21400;
	Thu, 26 Jan 95 07:56:56 -0800
Date: Thu, 26 Jan 1995 07:56:53 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Ralf Widera <widera@fz.telekom.de>
Cc: pine-info@cac.washington.edu
Subject: Re: Take addr to dist list?
In-Reply-To: <Pine.SUN.3.91.950126083331.18205A-100000@sun51.fz.telekom.de>
Message-Id: <Pine.ULT.3.92.950126075348.24434Q-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 26 Jan 1995, Ralf Widera wrote:

> Is there a way to TakeAddr to a list, when I am the only recipient?

It's a bit obscure, but Yes.  First *Select* the message in question, 
then Apply Take.

We'll probably change the single address case to be more like the multiple
address case for 3.92.  It means one more keystroke for the non-list case,
but avoids the problem of having to be psychic to figure out how to do the
list case... 

-teg


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:07:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25114;
	Thu, 26 Jan 95 08:07:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00167;
	Thu, 26 Jan 95 08:02:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00159;
	Thu, 26 Jan 95 08:02:05 -0800
Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14120;
	Thu, 26 Jan 95 08:01:08 -0800
Date: Thu, 26 Jan 1995 08:01:07 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Arcin Bozkurt <arcin@ug.bcc.bilkent.edu.tr>
Cc: pine-info@cac.washington.edu
Subject: Re: some news folders disapper !! HELP
In-Reply-To: <Pine.SUN.3.90.950125232938.14792A-100000-100000-100000@trabzon>
Message-Id: <Pine.ULT.3.92.950126080009.24434R-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

The .newsrc handling code was rewritten for 3.91, released last October.  
Please try that and let us know if you have any problems.

-teg

On Wed, 25 Jan 1995, Arcin Bozkurt wrote:

> 
> 
> 	Hi,all !!
> 	I am using Pine 3.90 and I have a problem with my news folders.
> The problem is that my folders disappear after i read another folder.
> Strange isn't it ?
> 	Here is the story ...
> 	I am at the moment subscribed to comp.mail.pine and 
> comp.mail.misc. In another pine window i subscribed to sci.space read two 
> news there and deleted those two news i read. Then i pressed L to turn 
> back to folder list.
> 	What do you i see at the window? Only sci.space!! The other two 
> folders are lost. I happens all the time and i do not the way out.
> 	I also looked at my .newsrc file. It only contains the following 
> after the operation :
> 
> sci.space:
> 
> 	Can anyone with this peculiar behaviour of Pine 3.90.
> 	Thank you very much in advance .
> 
> 					Arcin Bozkurt
> 					Bilkent University
> 					EE - Junior
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:15:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25510;
	Thu, 26 Jan 95 08:15:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01740;
	Thu, 26 Jan 95 08:10:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01734;
	Thu, 26 Jan 95 08:10:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXWdG-00038QC; Thu, 26 Jan 95 08:01 PST
To: pine-info@cac.washington.edu
From: fyao@calum.csclub.uwaterloo.ca (Frank Yao)
Subject: Re: Random .sig?
Message-Id: <D3078v.88H@undergrad.math.uwaterloo.ca>
References: <3g3ogs$jkn@nic.iii.net>
Date: Thu, 26 Jan 1995 08:22:06 GMT

Steve Bernacki Jr <drown@iii1.iii.net> wrote:

>Is it possible to somehow have a random signature (out of a directory of
>signatures) be selected and pasted into pine?  If not, is there any way
>to get pine to run a program that would output such a random sig?

The only way I've thought of is to use a script of some sort which
randomly picks a file from a directory, and the pipes that file into
the editor of your choice.  I don't know all the details, but I could
find out if my comments here aren't enough to work with.

- frank


-- 
**********************************************************************
*  You may be right.  I may be crazy.  But it just may be a lunatic  *
*  you're looking for. 			- Billy Joel 		     *
*************************** Frank Yao, fyao@csclub.uwaterloo.ca ******


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:36:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26361;
	Thu, 26 Jan 95 08:36:00 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02285;
	Thu, 26 Jan 95 08:31:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02279;
	Thu, 26 Jan 95 08:31:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXWwg-00038RC; Thu, 26 Jan 95 08:21 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Deletion of empty folders
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl>
Mime-Version: 1.0
Date: Thu, 26 Jan 1995 07:24:08 GMT

I am afraid that I'm missing something quite obvious (but I failed to find a
pointer in the setup menus). I at times keep mail around in temporary folders,
'till I get around to answering it. Then I remove the mail from the temp
folder.

How do I get Pine to automatically remove empty folders? Or do I really have
to run say an external shellscript to accomplish this?

Thanx in advance.. please reply by E-mail too, I might miss an answer.
--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
>From the Obscure Dictionary of Medical Terms:
Lymph: A special Fairy.



From owner-pine-info@cac.washington.edu  Thu Jan 26 08:36:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26384;
	Thu, 26 Jan 95 08:36:10 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02277;
	Thu, 26 Jan 95 08:31:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02271;
	Thu, 26 Jan 95 08:31:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXWwe-00038QC; Thu, 26 Jan 95 08:21 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Re: Re-Sending EMail?? 
In-Reply-To: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> 
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950126082026.5530C-100000@bambix.icce.rug.nl>
References: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> 
Mime-Version: 1.0
Date: Thu, 26 Jan 1995 07:21:38 GMT

On Wed, 25 Jan 1995, Dan Mullen wrote:

> Question:
> What Pine command do I use to resend a previously sent message
> that has been returned due to Wrong Address or Server Error?
> 
> This has happened a couple ot times and had to retype the whole message 
> again. Suggestion Please!!
> 
> dmullen@gate.net

Make sure that you have the "bounce" command enabled (main menu -> setup ->
config). When your get your mail back, re-check the address. Then bounce the
message to the same address or if you know of an alternative, bounce it to the
alternative address.

--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
>From the Obscure Dictionary of Medical Terms:
Lymph: A special Fairy.



From owner-pine-info@cac.washington.edu  Thu Jan 26 08:37:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26529;
	Thu, 26 Jan 95 08:37:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02269;
	Thu, 26 Jan 95 08:31:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02261;
	Thu, 26 Jan 95 08:31:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXWwa-00038MC; Thu, 26 Jan 95 08:21 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Re: Random .sig? 
In-Reply-To: <3g44kv$et4@gatecoms.gatecom.com> 
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950126081804.5530B-100000@bambix.icce.rug.nl>
References: <3g3ogs$jkn@nic.iii.net> <3g44kv$et4@gatecoms.gatecom.com> 
Mime-Version: 1.0
Date: Thu, 26 Jan 1995 07:20:04 GMT

On 25 Jan 1995, Matt Newell wrote:

> Steve Bernacki Jr (drown@iii1.iii.net) wrote:
> > Howdy y'all,
> 
> > Is it possible to somehow have a random signature (out of a directory of
> > signatures) be selected and pasted into pine?  If not, is there any way
> > to get pine to run a program that would output such a random sig?
> 
> This may not be exactly what you requested, but it works for me.
> 
> #! /sbin/sh
> mv ${HOME}/.signature ${HOME}/sig1.tmp
> mv ${HOME}/.sigb ${HOME}/sig2.tmp
> mv ${HOME}/.sigc ${HOME}/sig3.tmp
> mv ${HOME}/.sigd ${HOME}/sig4.tmp
> mv ${HOME}/.sige ${HOME}/sig5.tmp
> mv ${HOME}/sig1.tmp ${HOME}/.sige
> mv ${HOME}/sig2.tmp ${HOME}/.signature
> mv ${HOME}/sig3.tmp ${HOME}/.sigb
> mv ${HOME}/sig4.tmp ${HOME}/.sigc
> mv ${HOME}/sig5.tmp ${HOME}/.sigd
> 
> This is obviously for 5 sigs, but can be easily changed to work with more
> or less
> 
> I just have it in my .login, so that I have a different sig each time I
> login.
> 
>      Hope this helps,
>      Matt
> 
> **   Matt Newell                             mnewell@gatecoms.gatecom.com   **

Or of course grab a "cookie" program. Then have cron run the following shell
say each our:

    #!/bin/sh
    cat > ~/.signature << EOF
    --
    Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
    EOF
    cookie >> ~/.signature
    
That's at least how this below is generated..

--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
>From the Obscure Dictionary of Medical Terms:
Lymph: A special Fairy.


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:41:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26742;
	Thu, 26 Jan 95 08:41:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02405;
	Thu, 26 Jan 95 08:36:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02399;
	Thu, 26 Jan 95 08:36:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXWxd-00038SC; Thu, 26 Jan 95 08:22 PST
To: pine-info@cac.washington.edu
From: robk@stack.urc.tue.nl (Rob Kouwenberg)
Subject: Re: Need to secure pine
Date: 26 Jan 1995 09:05:09 GMT
Message-Id: <3g7ok5$dob@tuegate.tue.nl>
References: <3g1e2s$5sk@case.cyberspace.com> <Pine.SUN.3.91.950124173442.24402T-100000@apus.cus.cam.ac.uk>

Barry Landy (bl10@cus.cam.ac.uk) wrote:
: We have the following set in pine.conf.fixed, and it seems to do the job:-
: no-enable-alternate-editor-cmd,
: no-always-use-alt-editor,
: no-enable-alternate-editor-implicitly,

Stupid question probably, but where to place these files ?

( yes, RTFM, but time is unfortunately not on my side always -:( )

TIA, best regards, Rob Kouwenberg

PS I placed pine in /usr/local/bin if this matters ..
--
[ robk@stack.urc.tue.nl,Gr.Adolfstraat86,5616BX,Eindhoven,The Netherlands ]


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:42:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26808;
	Thu, 26 Jan 95 08:42:10 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02424;
	Thu, 26 Jan 95 08:36:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02417;
	Thu, 26 Jan 95 08:36:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXWyc-00038TC; Thu, 26 Jan 95 08:23 PST
To: pine-info@cac.washington.edu
From: robk@stack.urc.tue.nl (Rob Kouwenberg)
Subject: Re: Need to secure pine
Date: 26 Jan 1995 09:44:55 GMT
Message-Id: <3g7qun$efu@tuegate.tue.nl>
References: <3g1e2s$5sk@case.cyberspace.com> <3g4g5p$7ab@news.southern.edu>

AJDevoir (ajdevoir@southern.edu) wrote:
: Have you thought about just changing the file permissions on the .pinerc 
: file?  (chmod 700 .pinerc)  Maybe i am just reading what you are after wrong,
: but is it that people are just coming in and reconfiguring pine for you?

It's no use; the user can change this value ..

I also found the pine.conf.fixed location to be : /usr/local/lib
Description in the files in the ./pine3.91/doc directory.

'Till next time, best regards, Rob Kouwenberg
--
[ robk@stack.urc.tue.nl,Gr.Adolfstraat86,5616BX,Eindhoven,The Netherlands ]


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:42:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26899;
	Thu, 26 Jan 95 08:42:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02435;
	Thu, 26 Jan 95 08:36:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02429;
	Thu, 26 Jan 95 08:36:14 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXX0V-00038WC; Thu, 26 Jan 95 08:25 PST
To: pine-info@cac.washington.edu
From: FLAVELL@crnvma.cern.ch (Alan J Flavell)
Subject: Re: Q. about HUJI VMS Pine 3.91 beta 3
Message-Id: <17332AE2DS86.FLAVELL@cernvm.cern.ch>
References: <1732D14368S86.FLAVELL@cernvm.cern.ch> <3g4t4v$op3@blackice.winternet.com>
Date: Thu, 26 Jan 1995 12:23:01 GMT

In article <3g4t4v$op3@blackice.winternet.com>
daud@winternet.com (David Denney) writes:
 
>: What makes it think I have a postponed mail?
>
>Add 'postponed-folder=""' in pine.conf (global) or .pinerc (sys$login)
>
>: Also, can someone explain just what it means under 1. in "Restrictions"?
>: It says "the user must not switch to another folder as long as NEWMAIL
>: has items".  Does something terrible happen?
>
>That is only applicable if you map INBOX to be NEWMAIL. DO NOT DO THIS.
>Nasty things will happen. Leave INBOX = INBOX, ignore it completely, and
>make a few extra keystrokes to open NEWMAIL instead.
 
Many thanks for your helpful reply.  In the meantime, I find that
there is a more serious (!) problem: it doesn't seem to understand
MIME encoded mail.  I think this is because the incoming mail gets
an additional set of headers added ahead of the RFC822 headers.
Presumably this is a result of the way we have MULTINET configured,
and it allows MAIL to handle both SMTP and DECNET mail transparently.
 
The same situation probably explains why it does not compose
REPLY addresses properly: it seems to be using the added
headers rather than the RFC822 headers, so (when replying to
incoming SMTP mail) we get a reply address like this:
 
   "SMTP%a.user@some.domain.edu"@our.own.domain.name
 
I think our existing MAIL users would be upset if we were to change
the format of incoming mail, if they lost the ability to reply to
incoming DECNET mail.  Is there anything we can do to live with
this situation, and still use PINE (so as to be able to use MIME)?
 
(And again the question, "is there a better place for discussing
this VMS version"?).
 
best regards


From owner-pine-info@cac.washington.edu  Thu Jan 26 08:57:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27625;
	Thu, 26 Jan 95 08:57:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02772;
	Thu, 26 Jan 95 08:50:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from aurore.umd.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02762;
	Thu, 26 Jan 95 08:49:59 -0800
Received: from LOCALHOST (LOCALHOST [127.0.0.1]) by aurore.umd.edu (8.6.9/8.6.6) with SMTP id LAA03455 for <pine-info@cac.washington.edu>; Thu, 26 Jan 1995 11:46:11 -0500
Message-Id: <199501261646.LAA03455@aurore.umd.edu>
To: pine-info@cac.washington.edu
Subject: PCPine not writing FCC?
Date: Thu, 26 Jan 1995 11:46:10 -0500
From: Larry Lentner <larry@aurore.umd.edu>

One of my users is running the packet driver version of PCPine
3.91 on a Gateway 2000 486SX/33 and complains that the default
FCC folder (SENTMAIL) isn't being written to occasionally when
sending messages. 

I haven't been able to duplicate the problem. Has anyone else
experienced anything similar?

Thanks in advance for any help/ideas,
Larry Lentner
UMCEES/CBL Computer Center
410/326-7306
larry@cbl.umd.edu



From owner-pine-info@cac.washington.edu  Thu Jan 26 09:09:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28886;
	Thu, 26 Jan 95 09:09:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01879;
	Thu, 26 Jan 95 09:04:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01867;
	Thu, 26 Jan 95 09:04:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXXQP-00038SC; Thu, 26 Jan 95 08:52 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Pine/VMS
Date: 26 Jan 95 12:38:37 GMT
Message-Id: <ellis.791123917@gmi.edu>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu> <1995Jan14.220520@cchs.su.edu.au> <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au>

Alan Agnew <agnew@maize.qut.edu.au> writes:

 >In a previous posting it was stated that PINE 3.91  for VMS is available
 >from lenin.cc.rochester.edu.

 >I have been attempting to connect to lenin.cc.rochester.edu from Australia
 >for several days now, but have never suceeded.

 >A ping shows 100% packet loss.

 >A traceroute gets as far as taylor4-bbgw.utd.rochester.edu and then nothing.

 >Is there a known difficulty in connecting to lenin.cc.rochester.edu?

I just tried it with ncftp.

nova_ellis_~/> ncftp lenin.cc.rochester.edu

******************************
LENIN.CC.ROCHESTER.EDU IS DOWN
******************************

        Lenin's second hard disk (the one that contains "/usr") has failed. 
All non-critical network services (including ftp) have been suspended until
the drive can be replaced.  There is no ETA for repair completion.  We
apologize for any inconvenience this may cause.  Please contact
tgpt_ltd@cc.rochester.edu for further details.

        Tom Guptill
        archive@lenin
        acting as root@lenin
User anonymous access denied.
Login failed.


 >Does anyone else have this version of PINE on an anonymous FTP  server?


 >	Alan Agnew
 >	Network Services
 >	Computing Services
 >	Queensland University of Technology

 >	Phone: (07) 864 1703		E-Mail: A.Agnew@qut.edu.au
-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Thu Jan 26 09:09:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28888;
	Thu, 26 Jan 95 09:09:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03299;
	Thu, 26 Jan 95 09:04:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03284;
	Thu, 26 Jan 95 09:04:32 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXXRo-00038UC; Thu, 26 Jan 95 08:53 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: I renamed and made PICO an executable but still no luck
Date: 26 Jan 95 12:41:06 GMT
Message-Id: <ellis.791124066@gmi.edu>
References: <3g6sbn$fet@nic-nac.CSU.net>

mike@newport.lib.ca.us (Micheal Wojciechowski) writes:

 >As the subject header says I renamed pico-bin.hpux9 and made it an executable
 >but I get a message back that says "ksh: pico: cannot execute"  Does anyone have
 >any clue as to what I need to do.  Does it need to be compiled?

Did you 'chmod 755 pico'?

 >Thanks in advance.

 >Mike
-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Thu Jan 26 09:36:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00373;
	Thu, 26 Jan 95 09:36:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02623;
	Thu, 26 Jan 95 09:31:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02617;
	Thu, 26 Jan 95 09:31:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXXq3-00038RC; Thu, 26 Jan 95 09:18 PST
To: pine-info@cac.washington.edu
From: hph@vki68.aar-vki.dk (Hans Peter)
Subject: Global Address Book (RO ??)
Date: 26 Jan 1995 09:41:37 GMT
Message-Id: <3g7qoh$iio@belfort.daimi.aau.dk>

I have a small problem:

Our global address book in pine 3.91 SCO-UNIX in:
/w2/bruger/pineaddr/globaddr

The problem is, that it is set to ReadOnly within pine for all users,
including root, althoug the permissions for the file is set to rw.

So how do I maintain this file?

best regards, Hans Peter
----------------------------------------------------------------
*  Hans Peter Hansen            |  VKI-Water Quality Institute *
*  E-mail: hph@aar-vki.dk       |  Science Park Aarhus         *
*  Phone: +45 86 20 20 00 /2124 |  10, Gustav Wiedsvej         *
*  Fax:   +45 86 19 75 11       |  DK 8000 Aarhus C, Denmark   *
----------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Thu Jan 26 09:56:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01417;
	Thu, 26 Jan 95 09:56:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04422;
	Thu, 26 Jan 95 09:45:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04416;
	Thu, 26 Jan 95 09:45:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXY0X-00038QC; Thu, 26 Jan 95 09:29 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Re-Sending EMail??
Date: Thu, 26 Jan 1995 13:47:58 +0000
Message-Id: <Pine.SUN.3.91.950126134613.26920X-100000@grus.cus.cam.ac.uk>
References: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> 

On Wed, 25 Jan 1995, Dan Mullen wrote:

> Question:
> What Pine command do I use to resend a previously sent message
> that has been returned due to Wrong Address or Server Error?

You save the Fcc copy to your postponed-msgs folder (or whatever name you 
have called the folder where postponed messages go), then type C (ompose) 
and respond Yes (or select the message if you have more than one 
postponed), edit it totaste, and away you go.

> 
> This has happened a couple ot times and had to retype the whole message 
> again. Suggestion Please!!

The above avoids retyping (and I use it frequently!)

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Thu Jan 26 10:06:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02137;
	Thu, 26 Jan 95 10:06:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03379;
	Thu, 26 Jan 95 10:01:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03373;
	Thu, 26 Jan 95 10:01:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXYIl-00038MC; Thu, 26 Jan 95 09:48 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: several Pine suggestions
Date: Thu, 26 Jan 1995 13:55:24 +0000
Message-Id: <Pine.SUN.3.91.950126135229.26920Y-100000@grus.cus.cam.ac.uk>
References: <3g0pds$r9c@hobbes.cc.uga.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g0pds$r9c@hobbes.cc.uga.edu> 

On 23 Jan 1995, Glenn Leavell wrote:

> 
> 1)  In INDEX mode, allow the 'k' and 'j' keys to be used to move the current
>     pointer up and down (j key would only function like this if
>     jump short cut were turned on).  This convention can be
>     found in vi, Elm, Gopher, and other utilities, so it makes things
>     somewhat consistent.
> 
I think this is a dreadful idea. It of course harks back to long dead 
terminals which had arrows engraved on those keys, accessed, I think, in 
ESCAPE mode. 

As someone who teaches Pine, its transparency is a major virtue, and 
those places where this breaks down (like the dreadful Y for prYnt)  
cause problems; when teaching it is wonderful for A to be Add, C compose 
and so on. Previous and Next are enough alternatives to up-arrow and 
down-arrow, thanks.


=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Thu Jan 26 15:34:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18153;
	Thu, 26 Jan 95 15:34:53 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12866;
	Thu, 26 Jan 95 15:30:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12860;
	Thu, 26 Jan 95 15:30:07 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXdRc-00038UC; Thu, 26 Jan 95 15:17 PST
To: pine-info@cac.washington.edu
From: paul@kuhub.cc.ukans.edu (Craig Paul)
Subject: Re: IMAP in this week's Communications Week - IMAP4
Message-Id: <1995Jan26.135406.83753@kuhub.cc.ukans.edu>
Date: 26 Jan 95 13:54:06 CST
References: <3g2qiv$gf8@terminator.ncts.navy.mil>

In article <3g2qiv$gf8@terminator.ncts.navy.mil>, Paul Everitt <paul@cminds.com> writes:
> Reading this week's (or last, I'm not sure) _Communications Week_
> magazine, I nearly fell out of my chair when I saw an article
> on IMAP.  Pretty succinct in content.
> 
> --Paul

Well, that's IMAP4, not IMAP2 (or bis or +). The most important
question is when IMAP4 servers and clients will be available!


From owner-pine-info@cac.washington.edu  Thu Jan 26 15:44:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18523;
	Thu, 26 Jan 95 15:44:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11937;
	Thu, 26 Jan 95 15:40:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11931;
	Thu, 26 Jan 95 15:40:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXdbn-00038TC; Thu, 26 Jan 95 15:28 PST
To: pine-info@cac.washington.edu
From: jrh@swl.msd.ray.com (John Howley {91404})
Subject: Re: Need HELP! BinHEX conversion?
Message-Id: <D30xIr.Es8@swlvx2.msd.ray.com>
References: <3fmv6r$86n@kaiwan009.kaiwan.com> <Pine.A32.3.91.950120100755.27547B-100000@rzserv2.fh-lueneburg.de> <D2x9pI.5KE@mccc.edu>
Date: Thu, 26 Jan 1995 17:49:39 GMT

>Ralf Matthies (matthies@rzserv2.fh-lueneburg.de) wrote:
>: On 19 Jan 1995, Richard Hsiung wrote:

>: > I got a mail from someone with an attachment (supposedly), well, in the 
>: > message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
>: > BinHex and how do I get this attachment back into file form?

>: you will find BinHex on the following aFTP servers:

>:               ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip
>:               micros.hensa.ac.uk  /mirrors/simtel/msdos/mac/binhex13.zip

>: PS: Ask me, if you have more questions... ;-)

What does Binhex do and why is it needed? I have the same problem
when sending an attached file (simple text file) from a PC (with
eudora) to my UNIX workstation (reading with pine). If I use pine
to send and read the attached file (as a test), there is no problem.

-- 
--
John Howley
jrh@swl.msd.ray.com
jrh@id.wing.net


From owner-pine-info@cac.washington.edu  Thu Jan 26 16:26:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20074;
	Thu, 26 Jan 95 16:26:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14039;
	Thu, 26 Jan 95 16:21:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14033;
	Thu, 26 Jan 95 16:21:37 -0800
Received: by hobbes.twntpe.cdc.com; Fri, 27 Jan 95 08:20:00 -0800
Date: Fri, 27 Jan 1995 08:20:00 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: John Howley {91404} <jrh@swl.msd.ray.com>
Cc: pine-info@cac.washington.edu
Subject: Re: Need HELP! BinHEX conversion?
In-Reply-To: <D30xIr.Es8@swlvx2.msd.ray.com>
Message-Id: <Pine.SOL.3.91.950127081042.7390C-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 26 Jan 1995, John Howley {91404} wrote:

 
> What does Binhex do and why is it needed? I have the same problem
> when sending an attached file (simple text file) from a PC (with
> eudora) to my UNIX workstation (reading with pine). If I use pine
> to send and read the attached file (as a test), there is no problem.

	BinHex is the encoding method used by the MAC world.  It is
"similar" to base64 and uuencode.  Whereas uuencode starts with

begin 666 file.name

	a "BinHex'd" file starts with

(This file must be read with BinHex 4.0)   Or something to that effect....

	One of the encoding methods available to eudora users is BinHex.
If they choose to send it to you with BinHex...then you will need BinHex
to decode it.  *IF* eudora would use BinHex within the framework of MIME
then it should be possible to decode the file automagically.  I'd have
to check...but I believe someone defined the headers for use in sending
BinHex files within MIME.

	I'm not familiar with the shareware version of eudora....but
the commercial version allow you to select MIME as your default attachment
handler.

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Thu Jan 26 18:16:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25182;
	Thu, 26 Jan 95 18:16:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16403;
	Thu, 26 Jan 95 18:12:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16397;
	Thu, 26 Jan 95 18:12:18 -0800
Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24392;
	Thu, 26 Jan 95 18:12:13 -0800
Date: Thu, 26 Jan 1995 18:12:12 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Craig Paul <paul@kuhub.cc.ukans.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: IMAP in this week's Communications Week - IMAP4
In-Reply-To: <1995Jan26.135406.83753@kuhub.cc.ukans.edu>
Message-Id: <Pine.ULT.3.92.950126180929.29153R-100000@shiva2.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Craig,
To a first approximation, all IMAP2 and IMAP2bis clients will work with 
IMAP4 servers, even though they will not be able to take advantage of the 
new features in IMAP4.

CMU has had their IMAP4 server in Beta for some time already.
Ours is coming...

-teg

On 26 Jan 1995, Craig Paul wrote:

> In article <3g2qiv$gf8@terminator.ncts.navy.mil>, Paul Everitt <paul@cminds.com> writes:
> > Reading this week's (or last, I'm not sure) _Communications Week_
> > magazine, I nearly fell out of my chair when I saw an article
> > on IMAP.  Pretty succinct in content.
> > 
> > --Paul
> 
> Well, that's IMAP4, not IMAP2 (or bis or +). The most important
> question is when IMAP4 servers and clients will be available!
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 18:58:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26263;
	Thu, 26 Jan 95 18:58:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17046;
	Thu, 26 Jan 95 18:55:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17040;
	Thu, 26 Jan 95 18:55:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXgic-00038UC; Thu, 26 Jan 95 18:47 PST
To: pine-info@cac.washington.edu
From: jywong@abalone.ucsb.edu (Joyce Y. Wong)
Subject: Fcc:  interactive possible?
Date: 26 Jan 1995 16:46:31 -0800
Message-Id: <3g9fp7$dgi@abalone.ucsb.edu>


Is there a way to configure pine such that it will ask you
if you want to send a copy to Fcc: rather than doing it
automatically?  I know that you can turn it on and off, but
is there a way so you can interactively use it?

thanks

joyce


From owner-pine-info@cac.washington.edu  Thu Jan 26 19:42:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27596;
	Thu, 26 Jan 95 19:42:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17770;
	Thu, 26 Jan 95 19:38:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17763;
	Thu, 26 Jan 95 19:38:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhJU-00038TC; Thu, 26 Jan 95 19:25 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: "pico -w" and long lines
Date: Thu, 19 Jan 1995 09:41:08 -0800
Message-Id: <Pine.ULT.3.92.950119093948.22532A-100000@shiva1.cac.washington.edu>
References: <ii.790460725@shell1.best.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ii.790460725@shell1.best.com> 


Pico can only read lines of 256 or less characters.  It can create lines
of any (?) length though... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 18 Jan 1995, Nancy McGough wrote:

> Date: 18 JAN 1995 12:26:52 -0801 
> From: Nancy McGough <nancym@ii.com>
> Newgroups: comp.mail.pine, comp.editors
> Subject: "pico -w" and long lines 
> 
> If you use "pico -w" to edit a file, what are the longest lines
> it can deal with?  I know vi has a problem with long lines and
> I'm wondering if Pico does too.
> 
> Thanks,
> Nancy
> 
> -- 
>  /\_/\    Nancy McGough
> ( o.o )   Infinite Ink
>  > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 19:42:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27617;
	Thu, 26 Jan 95 19:42:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16697;
	Thu, 26 Jan 95 19:38:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16691;
	Thu, 26 Jan 95 19:38:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhJW-00038UC; Thu, 26 Jan 95 19:25 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: PC-Pine & POP
Date: Thu, 19 Jan 1995 09:48:18 -0800
Message-Id: <Pine.ULT.3.92.950119094730.22532B-100000@shiva1.cac.washington.edu>
References: <jsweet.3.00002905@cory.eecs.berkeley.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <jsweet.3.00002905@cory.eecs.berkeley.edu> 


PC-Pine does not use POP, but it does require IMAP service from your mail
server. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 19 Jan 1995, Julian Sweet wrote:

> Date: Thu, 19 JAN 1995 00:09:41 
> From: Julian Sweet <jsweet@cory.eecs.berkeley.edu>
> Newgroups: comp.mail.pine
> Subject: PC-Pine & POP 
> 
> Does my mail server have to be POP for PC-Pine to work? I got SLIP running no 
> problem....
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 19:42:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27638;
	Thu, 26 Jan 95 19:42:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17778;
	Thu, 26 Jan 95 19:38:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17772;
	Thu, 26 Jan 95 19:38:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhLh-00038aC; Thu, 26 Jan 95 19:27 PST
To: pine-info@cac.washington.edu
From: jtl@molehill.org (Todd Larason)
Subject: Berekely fix/speedup patch
Date: 27 Jan 1995 01:21:49 GMT
Message-Id: <3g9hrd$rds@qns1.qns.com>

There was a patch posted here some time back to speed up reading of
berekely-style mail files.  Could someone send it to me or tell me
where I can ftp it, please?

Todd Larason


From owner-pine-info@cac.washington.edu  Thu Jan 26 19:43:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27669;
	Thu, 26 Jan 95 19:43:09 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17761;
	Thu, 26 Jan 95 19:38:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17755;
	Thu, 26 Jan 95 19:38:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhJi-00038XC; Thu, 26 Jan 95 19:25 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Welcome to pine-info
Date: Fri, 20 Jan 1995 08:55:23 -0800
Message-Id: <Pine.ULT.3.92.950120085110.511B-100000@shiva1.cac.washington.edu>
References: <9501192250.AA10637@shivams.cac.washington.edu> <3fmt02$r46@newsreader.wustl.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fmt02$r46@newsreader.wustl.edu> 


On 19 Jan 1995, Lori Fox wrote:

> Date: 19 JAN 1995 23:35:30 GMT 
> From: Lori Fox <lef@wuacn.wustl.edu>
> Newgroups: comp.mail.pine
> Subject: Re: Welcome to pine-info 
> 
> Majordomo@cac.washington.edu wrote:
> : Welcome to the pine-info mailing list!
> 
> 
> Forgive this novice, but may I assume that everything that goes to this 
> mailing list will also go to comp.mail.pine ?
> 

Yes, psg.com runs a bi-directional gateway between comp.mail.pine and the
pine-info mailing list.  Note that it is operated by Randy Bush
<randy@psg.com>, not by the Pine Team.  Due to some lost messages that I 
just noticed a couple days ago the subscription address for the gateway 
was changed.  Hopefully that will improve performance and reliability of 
the gateway.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Thu Jan 26 19:43:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27690;
	Thu, 26 Jan 95 19:43:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16689;
	Thu, 26 Jan 95 19:38:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16683;
	Thu, 26 Jan 95 19:38:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhJl-00038ZC; Thu, 26 Jan 95 19:25 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Pine Pipe to Zmodem
Date: Fri, 20 Jan 1995 08:57:52 -0800
Message-Id: <Pine.ULT.3.92.950120085613.511C-100000@shiva1.cac.washington.edu>
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu> <3eeni5$t36@wabash.iac.net> <ellis.789325031@gmi.edu>  <Pine.NXT.3.91.950106012216.22917A-100000@lipschitz> <3emev0$o7a@wabash.iac.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3emev0$o7a@wabash.iac.net> 


On 7 Jan 1995, Carl Jolley wrote:

> Date: 7 JAN 1995 11:19:44 -0500 
> From: Carl Jolley <cjolley@iac.net>
> Newgroups: comp.mail.pine
> Subject: Re: Pine Pipe to Zmodem 
> 
[...]
> Pine's pipe, i.e. pipe to a command and capture the output back into
> a viewer, does not seem to be documented in either the man pages or in
> Pine's help screens. I thought that something was broken, but now I
> understand that the operation of Pine's pipe is a "feature". It would be
> nice if in addition to the current operation of Pine's pipe there was an
> option to do a pipe without capturing the command's stdout.
> 

Pine 3.92 will allow this...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Thu Jan 26 19:43:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27711;
	Thu, 26 Jan 95 19:43:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16681;
	Thu, 26 Jan 95 19:38:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16675;
	Thu, 26 Jan 95 19:38:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhJc-00038YC; Thu, 26 Jan 95 19:25 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Changing From: header
Date: Thu, 19 Jan 1995 16:13:21 -0800
Message-Id: <Pine.ULT.3.92.950119161233.6255A-100000@shiva1.cac.washington.edu>
References: <ii.790481918@shell1.best.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ii.790481918@shell1.best.com> 


Your system administrator can rebuild Pine with the "#define
ALLOW_CHANGING_FROM" line uncommented in the pine/os-???.h file... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 18 Jan 1995, Nancy McGough wrote:

> Date: 18 JAN 1995 18:22:18 -0800 
> From: Nancy McGough <ii@best.com>
> Newgroups: comp.mail.pine
> Subject: Changing From: header 
> 
> I'd like to change the From: header in mail I send from Pine
> by putting something like this in my .pinerc:
> 
> customized-hdrs=Organization: $ORGANIZATION,
>         From: Nancy McGough <nancym@ii.com>
> 
> 
> Unfortunately, when I try this Pine gives a message that says
> I can't change the From header.  Is there any way around this?
> E.g., could the system admins reset something to allow this?
> 
> Thanks for any info,
> Nancy
> 
> -- 
>  /\_/\   DUE TO EMAIL PROBLEMS, PLEASE SEND MAIL TO ME TO EITHER:   /\_/\
> ( o.o )                                                            ( o.o )
>  > ~ <           nancym@halcyon    -OR-    ii@best.com              > o <
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 19:49:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27892;
	Thu, 26 Jan 95 19:49:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16823;
	Thu, 26 Jan 95 19:45:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16817;
	Thu, 26 Jan 95 19:45:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhTS-00038bC; Thu, 26 Jan 95 19:35 PST
To: pine-info@cac.washington.edu
From: valko@cyberspace.com (Jack Valko)
Subject: Re: Need to secure pine
Date: 26 Jan 1995 16:39:01 -0800
Message-Id: <3g9fb5$gvo@case.cyberspace.com>
References: <3g1e2s$5sk@case.cyberspace.com> <Pine.SUN.3.91.950124173442.24402T-100000@apus.cus.cam.ac.uk>

Barry Landy (bl10@cus.cam.ac.uk) wrote:
: On 23 Jan 1995, Jack Valko wrote:

: > I would like to know if there is some way to set a configuration in pine 
: > so that users can't change it from the Setup menu.  Specifically, I want 
: > to restrict the alternate editor feature.  I have specified 
: > 'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
: > doesn't seem to do it.  Can anyone help?
: > 
: We have the following set in pine.conf.fixed, and it seems to do the job:-

: no-enable-alternate-editor-cmd,
: no-always-use-alt-editor,
: no-enable-alternate-editor-implicitly,

This seems to have fixed the problem.  Thanks to all who responded.

==================================================
Jack Valko           |       - Cyberspace -
System Administrator | 300 Queen Anne Ave. N. #396 
cyberspace.com       |   Seattle, WA 98109-4599 
cyberspace.net       |       (206) 281-5397 
==================================================


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:15:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28596;
	Thu, 26 Jan 95 20:15:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18295;
	Thu, 26 Jan 95 20:10:35 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18289;
	Thu, 26 Jan 95 20:10:34 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXhmu-00038TC; Thu, 26 Jan 95 19:55 PST
To: pine-info@cac.washington.edu
From: chengman@umich.edu (Dennis Cheng)
Subject: VMS Pine problems
Date: 27 Jan 1995 01:41:17 GMT
Message-Id: <3g9ivu$9ga@lastactionhero.rs.itd.umich.edu>

I have been trying to install PINE for VMS for a while now. We are 
running VMS 6.1 with DEC's UCX services. I obtained the PINE code from 
Israel and tried to compile it for the UCX service with little luck. Pine 
for VMS is a fairly important project for my organization so we are 
looking for help in getting PINE up from people who have done it before. 
We are even considering commercial sources for software that utilizes 
IMAP access.


Thanks in advance,

Dennis Cheng
University of Michigan, Ann Arbor MI.
Systems Consultant, Wayne Memorial Hospital-Health System, Honesdale PA.


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:44:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29252;
	Thu, 26 Jan 95 20:44:04 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17613;
	Thu, 26 Jan 95 20:40:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17607;
	Thu, 26 Jan 95 20:40:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiGs-00038TC; Thu, 26 Jan 95 20:26 PST
To: pine-info@cac.washington.edu
From: cellsys@earthlink.net
Subject: Wireless Data SW Devel Opportunity for Pine/E-Mail Developers (0/1)
Date: 27 Jan 1995 01:44:50 GMT
Message-Id: <3g9j6i$c61@moon.earthlink.net>





From owner-pine-info@cac.washington.edu  Thu Jan 26 20:44:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29317;
	Thu, 26 Jan 95 20:44:43 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18747;
	Thu, 26 Jan 95 20:40:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18741;
	Thu, 26 Jan 95 20:40:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiH6-00038UC; Thu, 26 Jan 95 20:27 PST
To: pine-info@cac.washington.edu
From: cellsys@earthlink.net
Subject: Wireless Data SW Devel Opportunity for Pine/E-Mail Developers [swdev1.txt] (1/1)
Date: 27 Jan 1995 01:44:57 GMT
Message-Id: <3g9j6p$c61@moon.earthlink.net>

begin 644 SWDEV1.TXT
M4W5B:F5C=#H@4F5Q=65S=&5D(&%R=&EC;&4@+2`B*$-%3$Q365,M24Y#*2!0
M<F]D=6-T(&1E=F5L;W!M+BXN(@T*#0I9;W4@87-K960@;64@=&\@<F5T<FEE
M=F4@=&AE(&9O;&QO=VEN9R!A<G1I8VQE.@T*("`@("`@("!;0G5S:6YE<W-7
M:7)E.D-O;7!U=&5R+3`Q,C,N-#@U70T*#0I(97)E(&ET(&ES+BXN+@T*#0I;
M0G5S:6YE<W-7:7)E.D-O;7!U=&5R+3`Q,C,N-#@U72`@("`Q+S(S+SDU#0H-
M"B`@("`@("`@*$-%3$Q365,M24Y#*2!0<F]D=6-T(&1E=F5L;W!M96YT("8@
M;&EN92!E>'1E;G-I;VX@;W!P;W)T=6YI='D@9F]R#0H@("`@("`@('-O9G1W
M87)E(&1E=F5L;W!E<G,Z("`B5VER96QE<W,@0V]N;F5C=&EV:71Y(&9O<B!T
M:&4@36%S<V5S(B`@#0H-"B`@("`@("`@("`@0G5S:6YE<W,@161I=&]R<R`F
M($-O;7!U=&5R(%=R:71E<G,-"B`@("`@("`@#0H@("`@("`@(%9!3B!.55E3
M+"!#86QI9BXM*$)54TE.15-3(%=)4D4I+4IA;BX@,C,L(#$Y.34M0V5L;'-Y
M<RP@26YC+BP@80T*("`@("`@("!D979E;&]P97(@;V8@=VER96QE<W,@8V]M
M;75N:6-A=&EO;G,@<')O8V5S<V]R<R!B87-E9"!I;B!3;W5T:&5R;@T*("`@
M("`@("!#86QI9F]R;FEA+"!S965K<R!S;V9T=V%R92!D979E;&]P97)S(&9O
M<B!I=',@;F5W('!R;V1U8W0@8F%S960@;VX-"B`@("`@("`@86X@4D8@<&%R
M86QL96P@<&]R="!A9&%P=&5R+B`@#0H@("`@("`@(`T*("`@("`@("!#96QL
M<WES)R!A9&%P=&5R(&-R96%T97,@<&]I;G0M=&\M<&]I;G0@86YD(&UU;'1I
M<&]I;G0@8V]N;F5C=&EO;G,-"B`@("`@("`@=&\@86YY(&1E=FEC92!W:71H
M;W5T('1H92!C;W-T(&%N9"!C;VUP;&5X:71Y(&]F('=I<FEN9RX@($ET(&-A
M;@T*("`@("`@("!I;G1E<F9A8V4@=VET:"!M86YY(&1I9F9E<F5N="!T>7!E
M<R!O9B!D979I8V5S+"!A;F0@:7,@;F]T(&1E=FEC92!O<@T*("`@("`@("!A
M<'!L:6-A=&EO;B!S<&5C:69I8RX@(%1H92!#96QL<WES(&%D87!T97(@:7,@
M82!V97)S871I;&4@=6YI="!F;W(-"B`@("`@("`@;V9F:6-E(&%N9"!H;VUE
M(&-O;FYE8W1I=FET>2!R97%U:7)E;65N=',@+2T@=VAE=&AE<B!F;W(@4$-S
M+`T*("`@("`@("!P97)I<&AE<F%L<RP@;W(@<V5T+71O<"!B;WAE<RX@(`T*
M("`@("`@("`-"B`@("`@("`@5&AE(&-O;7!A;GD@:7,@;&]O:VEN9R!F;W(@
M<V]F='=A<F4@9&5V96QO<&5R<R!I;B!T:&4@9F]L;&]W:6YG#0H@("`@("`@
M(&%R96%S.@T*("`@("`@("`-"B`@("`@("`@("TM(%)E;6]T92!C;VYT<F]L
M(&%N9"!A8V-E<W,@#0H@("`@("`@("`M+2!!9"!H;V,@3$%.<R!A;F0@(E)O
M;VU,04YS(@T*("`@("`@("`@("`@*$-E;&QS>7,@:&%S(&1E=F5L;W!E9"!A
M(&)A<VEC(&%P<&QI8V%T:6]N<R!P86-K86=E(&9O<B`-"B`@("`@("`@("`@
M("!P<FEN=&5R+W)E<V]U<F-E('-H87)I;F<L(&4M;6%I;"!A;F0@9FEL92!T
M<F%N<V9E<BD@#0H@("`@("`@("`M+2!(;VUE(&%U=&]M871I;VX@86YD(&AO
M;64@3$%.<R`-"B`@("`@("`@("TM($EN=&5R86-T:79E(&5N=&5R=&%I;FUE
M;G0L(&EN8VQU9&EN9R!G86UI;F<@86YD('9I<G1U86P@<F5A;&ET>2`-"B`@
M("`@("`@("TM($UI>&5D(&UE9&EA+"!T:&ER9"!G96YE<F%T:6]N(&5L96-T
M<F]N:6,@;65S<V%G:6YG(`T*("`@("`@("`@+2T@5&5L97!O<G1I;F<@#0H@
M("`@("`@("`M+2!!9V5N="UO<FEE;G1E9"!S;V9T=V%R92\B26YT96QL:6=E
M;G0@86=E;G1S(B`-"B`@("`@("`@("TM($-O;7!U=&5R+6)A<V5D(&EC;VYI
M8R!C;VUM=6YI8V%T:6]N#0H@("`@("`@("`M+2!'<F]U<'=A<F4O0U-#5R`H
M8V]M<'5T97(M<W5P<&]R=&5D(&-O;W!E<F%T:79E('=O<FLI(`T*("`@("`@
M("`@+2T@3F%T=7)A;"!L86YG=6%G92!P<F]C97-S:6YG#0H@("`@("`@("`@
M("`@("`@#0H@("`@("`@(%-P96-I9FEC86QL>2P@0V5L;'-Y<R<@9FER<W0@
M<')I;W)I='D@:7,@97-T86)L:7-H:6YG(')E;&%T:6]N<VAI<',-"B`@("`@
M("`@=VET:"!D979E;&]P97)S(&]F(')E;6]T92!C;VYT<F]L(&%N9"!A8V-E
M<W,@<V]F='=A<F4N($-E;&QS>7,G#0H@("`@("`@('!R97-I9&5N="P@1&%V
M:60@4V-O='0@3&5W:7,L('-T871E9"P@(D]U<B!A9&%P=&5R(&5N86)L97,@
M<V]F='=A<F4-"B`@("`@("`@9&5V96QO<&UE;G0@8V]M<&%N:65S(&%N9"!I
M;F1I=FED=6%L(&!C<F%C:V5R<R<@=VET:"!E>'!E<G1I<V4@:6X-"B`@("`@
M("`@<F5M;W1E(&-O;G1R;VP@86YD(&%C97-S('-O9G1W87)E('1O('1A<"!I
M;G1O('1H92!E;65R9VEN9R!33TA/#0H@("`@("`@("A3;6%L;"!/9F9I8V4O
M2&]M92!/9F9I8V4I(&UA<FME="!F;W(@=VER96QE<W,@8V]N;F5C=&EV:71Y
M+"!A;F0@9F]R#0H@("`@("`@(&5N=&5R<')I<V4O;&5G86-Y(')E<V]U<F-E
M('-H87)I;F<L('!R:6YT97(@<V5R=F5R(&%N9"!T97)M:6YA;`T*("`@("`@
M("!E;75L871I;VX@87!P<RXB("`-"B`@("`@("`@#0H@("`@("`@($ET(&ES
M($-E;&QS>7,G(&5S=&EM871E('1H870@87!P;&EC871I;VYS(&UA>2!T86ME
M(&]N;'D@;VYE('!E<G-O;BT-"B`@("`@("`@;6]N=&@@=&\@861A<'0@=&\@
M0V5L;'-Y<R<@<')O8V5S<V]R+B`@0V5L;'-Y<R!W:6QL('!R;W9I9&4-"B`@
M("`@("`@9&5V96QO<&5R<R!W:71H(&5X86UP;&5S(&%N9"!I;F9O<FUA=&EO
M;B!O;B!H;W<@=&\@86-C97-S('1H96ER#0H@("`@("`@('!R;V-E<W-O<B!I
M;G-T<G5C=&EO;B!S970[(&%N9"P@=&AE>2!W:6QL('!R;W9I9&4@9&5V96QO
M<&5R<R!W:71H#0H@("`@("`@('1H92!$3U,@5%-2+B`@#0H@("`@("`@(`T*
M("`@("`@("!#96QL<WES)R!P<F5S:61E;G0L($1A=FED(%-C;W1T($QE=VES
M+"!A;F0@8VAI968@97AE8W5T:79E(&]F9FEC97(L#0H@("`@("`@($=E;W)G
M92!5>65S=6=I+"!A<F4@:6YT97)E<W1E9"!I;B!B96=I;FYI;F<@82!D:6%L
M;V=U92!W:71H('-O9G1W87)E#0H@("`@("`@(&1E=F5L;W!E<G,@<F5G87)D
M:6YG('!R;V1U8W0@9&5V96QO<&UE;G0@86YD(&QI;F4@97AT96YS:6]N#0H@
M("`@("`@(&]P<&]R='5N:71I97,@8F%S960@;VX@0V5L;'-Y<R<@861A<'1E
M<BX@(`T*("`@("`@("`-"B`@("`@("`@26YF;W)M871I;VX@;VX@=&AE($-E
M;&QS>7,G('=I<F5L97-S(&%D87!T97(@9F]L;&]W<RX-"B`@("`@("`@#0H@
M("`@("`@($-%3$Q365,@5TE214Q%4U,@0T]-355.24-!5$E/3E,@4%)/0T53
M4T]2("A70U`I($%$05!415(-"B`@("`@("`@#0H@("`@("`@(%-P96-I9FEC
M871I;VYS+"`R,R!*86YU87)Y(#$Y.34-"B`@("`@("`@7EY>7EY>7EY>7EY>
M7EX-"B`@("`@("`@0V5L;'-Y<R!70U`@061A<'1E<B!M96%S=7)E<R`U+C4@
M>"`S+C4@:6YC:&5S(&%N9"!A='1A8VAE<R!V:6$@80T*("`@("`@("!P87)A
M;&QE;"!P;W)T(&%N9"!C86)L92!T;R!T:&4@8F%C:R!O9B!A;GD@8V]M<'5T
M97(@;W(@<&5R:7!H97)A;`T*("`@("`@("!S=7!P;W)T:6YG(&$@<&%R86QL
M96P@<&]R="X@($-E;&QS>7,G(&%D87!T97(@=7-E<R!N;VES92!R97-I<W1A
M;G0-"B`@("`@("`@<W!R96%D('-P96-T<G5M('1E8VAN;VQO9WD@=VET:"!A
M="!L96%S="`T(&9U;&P@8VAA;FYE;',@:6X@=&AE(#DP,BT-"B`@("`@("`@
M.3(X($U(>B!B86YD+B`@*$$@;F%R<F]W8F%N9"!V97)S:6]N(&9O<B!U8FEQ
M=6ET;W5S(&-O;7!U=&EN9R!I<R!I;@T*("`@("`@("!D979E;&]P;65N="!A
M;F0@<&QA;FYE9"!F;W(@<F5L96%S92!I;B!T:&4@4W5M;65R(&]F(#$Y.34N
M*2`@0W5R<F5N=`T*("`@("`@("!C87!A8FEL:71Y(&%L;&]W<R!F;W(@,3(Q
M(&MB<R!B=7)S="X@(`T*("`@("`@("`-"B`@("`@("`@57-I;F<@82!P871E
M;G0@<&5N9&EN9R!M=6QT:7!L92!A8V-E<W,@8V]M;75N:6-A=&EO;G,@<')O
M=&]C;VPL(&$-"B`@("`@("`@;75L=&EP;&4@;G5M8F5R(&]F(%=#4',@8V%N
M(&)E(&-O;FYE8W1E9"!T;V=E=&AE<B!F;W(@4$,M=&\M4$,@;W(@4$,M#0H@
M("`@("`@('1O+7!R:6YT97(@8V]M;75N:6-A=&EO;BX@($$@;G5M8F5R(&]F
M(&)U:6QT+6EN(&9E871U<F5S(&%L;&]W(&9O<@T*("`@("`@("!E<G)O<B!F
M<F5E(&-O;6UU;FEC871I;VXN("`-"B`@("`@("`@#0H@("`@("`@(%1H92!#
M96QL<WES($%D87!T97(@86QL;W=S(&9O<B!S96%M;&5S<R!U<V4@;V8@82!W
M:61E('9A<FEE='D@;V8-"B`@("`@("`@=V]R9"!P<F]C97-S:6YG+"!S<')E
M861S:&5E="P@<&5R<V]N86P@9&%T82!M86YA9V5M96YT+"!A;F0-"B`@("`@
M("`@:6YT96=R871E9"!S;V9T=V%R92!P86-K86=E<R!F;W(@<F5M;W1E('!R
M:6YT:6YG+B`@#0H@("`@("`@(`T*("`@("`@("!#96QL<WES)R!!9&%P=&5R
M('-U9V=E<W1E9"!R971A:6P@<')I8V4@;V8@)'AX>"`H5$)$.R`D,SDY('1A
M<F=E=`T*("`@("`@("!F;W(@1%-3('!R;V1U8W0@86YD("0Q-#D@=&%R9V5T
M(&9O<B!.0B!P<F]D=6-T*2!I;F-L=61E<R!T:&4-"B`@("`@("`@861A<'1E
M<BP@:6YS=&%L;&%T:6]N('-O9G1W87)E+"!A;F0@<&]W97(@<W5P<&QY+@T*
M("`@("`@("`-"B`@("`@("`@0V5L;'-Y<R<@061A<'1E<B!F96%T=7)E<R!A
M<F4@<W5M;6%R:7IE9"!B96QO=SH-"B`@("`@("`@#0H@("`@("`@("H@075T
M;VUA=&EC86QL>2!C;VYF:6=U<F5S('1O(&%L;"!P87)A;&QE;"!P;W)T<R`-
M"B`@("`@("`@*B!396QE8W1A8FQE(&1A=&$@8VAA;FYE;"!W:&EC:"!C;VYS
M:7-T<R!O9B!A('!R:6UA<GD@8V%R<FEE<B`-"B`@("`@("`@("!A;F0@>F5R
M;R!T;R!M=6QT:7!L92!S96-O;F1A<GD@8V%R<FEE<B!F<F5Q=65N8VEE<R`M
M+0T*("`@("`@("`@("`M(%9A<FEA8FQE(&9R86UE(&QE;F=T:"!41$U!(&9O
M<B!A('!R:6UA<GD@8V%R<FEE<@T*("`@("`@("`@("`M($9U;&P@=7-E(&]F
M(%)&(&1A=&$@=')A;G-F97(@<F%T92!B>2!U<VEN9R!A('-E8V]N9&%R>2`-
M"B`@("`@("`@("`@("!C87)R:65R(`T*("`@("`@("`J(%-P<F5A9"US<&5C
M=')U;2!R861I;R!T96-H;F]L;V=Y+"`Y,#(M.3(X($U(>B`-"B`@("`@("`@
M("`H;&]W97(@8V]S="!N87)R;W=B86YD('9E<G-I;VX@:6X@9&5V96QO<&UE
M;G0I(`T*("`@("`@("`J($YO(&QI8V5N<V4@<F5Q=6ER960-"B`@("`@("`@
M*B!"=6EL="UI;B!O;6YI+61I<F5C=&EO;F%L(&%N=&5N;F$@9F]R(&]P=&EM
M=6T@<F5C97!T:6]N(`T*("`@("`@("`J($-O=F5R86=E('5P('1O(#,P,"!F
M965T+"!D97!E;F1I;F<@;VX@=&AE(&5N=FER;VYM96YT(`T*("`@("`@("`J
M($Q%1"!I;F1I8V%T;W)S(&9O<B!P;W=E<BP@;&EN:RP@86YD(&5R<F]R(`T*
M("`@("`@("`J($5R<F]R(&1E=&5C=&EO;B!A;F0@9&%T82!T<F%N<V9E<B!V
M97)I9FEC871I;VX@#0H@("`@("`@("H@07-S:6=N86)L92!S96-U<FET>2!C
M;V1E(`T*("`@("`@("`J($%S<VEG;F%B;&4@;6%S=&5R(&-O;G1R;VQL97(@
M#0H@("`@("`@("H@57-E<B!T<F%C:VEN9R!B>2!M87-T97(@8V]N=')O;&QE
M<B`-"B`@("`@("`@*B!!=71O;6%T:6,@87-S:6=N;65N="!O9B!S96-O;F%R
M>2!C87)R:65R(&)Y(&UA<W1E<B!C;VYT<F]L;&5R(`T*("`@("`@("`J($%S
M<VEG;F%B;&4@=6YI="!N971W;W)K(&%D9')E<W,@#0H@("`@("`@("H@04,@
M861A<'1E<B!I;F-L=61E9#L@8V%N(&)E('5S960@=VET:"!A;GD@-58M,C!6
M('!O=V5R('-U<'!L>0T*("`@("`@("`@("AA(&)A='1E<GDM;W!E<F%T960@
M=F5R<VEO;B!I<R!P;&%N;F5D(&9O<B!A(&YE87(M9G5T=7)E(`T*("`@("`@
M("`@("!R96QE87-E*2`-"B`@("`@("`@*B!0871E;G0@<&5N9&EN9R!M961I
M82!A8V-E<W,@<')O=&]C;VP@#0H@("`@("`@("H@365N=2UD<FEV96X@8V]N
M9FEG=7)A=&EO;B!A;F0@9&EA9VYO<W1I8R!S;V9T=V%R92`-"B`@("`@("`@
M*B!/<&5R871E<R!U;F1E<B!-4RU$3U,@,RYX(&%N9"!A8F]V92`-"B`@("`@
M("`@*B!"<F]A9&-A<W0@;6]D92`-"B`@("`@("`@*B!087-S+71H<F]U9V@O
M8V]N=')O;"!M;V1E(`T*("`@("`@("`J(%-T86YD+6)Y+V]N;&EN92!M;V1E
M#0H@("`@("`@(`T*("`@("`@("!!4%!,24-!5$E/3E,-"B`@("`@("`@#0H@
M("`@("`@(%!O:6YT+71O+5!O:6YT(&-O;6UU;FEC871I;VYS(`T*("`@("`@
M("!0;VEN="UT;RU-=6QT:7!O:6YT(&-O;6UU;FEC871I;VYS#0H@("`@("`@
M($UU;'1I<&]I;G0M=&\M375L=&EP;VEN="!C;VUM=6YI8V%T:6]N<PT*("`@
M("`@("`-"B`@("`@("`@15A!35!,15,-"B`@("`@("`@#0H@("`@("`@(')E
M<V]U<F-E('-H87)I;F<[(&9I;&4@=')A;G-F97([(&5L96-T<F]N:6,@;6%I
M;#L@:6YT97)A8W1I=F4-"B`@("`@("`@9V%M:6YG.R!I;G9E;G1O<GD@8V]N
M=')O;#L@:6YS=')U;65N="!M;VYI=&]R:6YG.R!V;VEC92!M86EL.R!P;VEN
M=`T*("`@("`@("!O9B!S86QE<SL@8V]M<'5T97(@:6YT96=R871E9"!M86YU
M9F%C='5R:6YG#0H@("`@("`@(`T*("`@("`@("!#;VYN96-T:79I='D@9F]R
M("XN+@T*("`@("`@("`-"B`@("`@("`@4')I;G1E<G,@#0H@("`@("`@($UO
M9&5M<R`-"B`@("`@("`@1F%X(&UA8VAI;F5S(`T*("`@("`@("!-;V)I;&4@
M8V]M<'5T:6YG(&%N9"!C;VUM=6YI8V%T:6]N(&1E=FEC97,@*&QA<'1O<',L
M(&YO=&5B;V]K<RP@#0H@("`@("`@("!01$%S+"!024-S*2`-"B`@("`@("`@
M3&5G86-Y('-Y<W1E;7,@*&EN8VQU9&EN9R!T97)M:6YA;"!E;75L871I;VXI
M(`T*("`@("`@("!(86YD:&5L9"!E;G1E<G1A:6YM96YT(&%N9"!G86UI;F<@
M=6YI=',@#0H@("`@("`@($EN9'5S=')I86P@8V]N=')O;"!D979I8V5S(`T*
M("`@("`@("!0;VEN="U/9BU386QE('-Y<W1E;7,@#0H@("`@("`@(%-E8W5R
M:71Y('-Y<W1E;7,@#0H@("`@("`@(%9O:6-E(&-O;6UU;FEC871I;VX@=6YI
M=',@#0H@("`@("`@(%-E="UT;W`@=&5R;6EN86QS(`T*("`@("`@("!$871A
M(&-O;&QE8W1I;VX@=&5R;6EN86QS(`T*("`@("`@("!0<F]C97-S(&UO;FET
M;W)I;F<@9&5V:6-E<PT*#0H@("`@("`@($-/3E1!0U0Z("!#96QL<WES+"!)
M;F,N+"!686X@3G5Y<PT*("`@("`@("`-"B`@("`@("`@1&%V:60@4V-O='0@
M3&5W:7,L(#@Q."\W.#8M,#0R,"`H;65D:6$I#0H@("`@("`@(`T*("`@("`@
M("!'96]R9V4@57EE<W5G:2P@.#$X+S<X-BTP-#(P("AS;V9T=V%R92!D979E
M;&]P97(I#0H@("`@("`@(`T*("`@("`@("!&87@Z("`X,3@O.3DT+34P,C8-
M"B`@("`@("`@#0H@("`@("`@($4M;6%I;#H@8V5L;'-Y<T!E87)T:&QI;FLN
M;F5T#0H@("`@("`@(`T*("`@("`@("`H069T97(@36%R8V@@,2!U<V4Z#0H@
M("`@("`@("!D879I9$!C96QL<WES+F-O;2!F;W(@1&%V:60@4V-O='0@3&5W
M:7,[(&%N9"P-"B`@("`@("`@(&=E;W)G94!C96QL<WES+F-O;2!F;W(@1V5O
M<F=E(%5Y97-U9VDI#0H@("`@("`@(`T*("`@("`@("!+15E73U)$.B`@0T%,
M249/4DY)00T*("`@("`@("`-"B`@("`@("`@24Y$55-44ED@2T595T]21#H@
M($-/35!55$524R]%3$5#5%)/3DE#4R`@0T]-140@(%!23T150U0-"B`@("`@
M("`@#0H@("`@("`@(%)%4$5!5%,Z($YE=R!9;W)K(#(Q,BTU-S4M.#@R,B!O
M<B`X,#`M,C(Q+3(T-C([($)O<W1O;B`V,3<M,S,P+34S,3$-"B`@("`@("`@
M;W(@("`@("`@("`X,#`M,C(U+3(P,S`[(%-&(#0Q-2TY.#8M-#0R,B!O<B`X
M,#`M,C(W+3`X-#4[($Q!#0H@("`@("`@(#,Q,"TX,C`M.30W,PT*#0H@("`@
M("`@($-O<'ER:6=H="`Q.3DU($)U<VEN97-S5VER92X@06QL(')I9VAT<R!R
*97-E<G9E9"X-"F
`
end



From owner-pine-info@cac.washington.edu  Thu Jan 26 20:48:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29397;
	Thu, 26 Jan 95 20:48:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17723;
	Thu, 26 Jan 95 20:45:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17717;
	Thu, 26 Jan 95 20:45:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRQ-00038ZC; Thu, 26 Jan 95 20:37 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [ killfile ]
Date: Sat, 21 Jan 1995 14:51:11 -0800
Message-Id: <Pine.ULT.3.92.950121145037.22172I-100000@shiva2.cac.washington.edu>
References: <3eqd71$hgt@xcalibur.IntNet.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3eqd71$hgt@xcalibur.IntNet.net> 


Pine does not currently support killfiles.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 8 Jan 1995, Jonathan Cooper wrote:

> Date: 8 JAN 1995 23:14:25 -0500 
> From: Jonathan Cooper <entropy@news.IntNet.net>
> Newgroups: comp.mail.pine
> Subject: [ killfile ] 
> 
> How would I kill all mail that comes from a certain address using
> pine itself?  Does pine support killfiles?
> 
> Yes, I know I could just make a procmail recipe, but I'd like to
> use just pine.
> 
> -jon
> -- 
> ( --------[ Jonathan D. Cooper ]--------[ entropy@intnet.net ]-------- )
> ( PGP 2.6.2 keyprint: 31 50 8F 82 B9 79 ED C4  5B 12 A0 35 E0 9B C0 01 )
> ( home page: http://taz.hyperreal.com/~entropy/ ]---[ Key-ID: 4082CCB5 )
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:49:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29432;
	Thu, 26 Jan 95 20:49:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18847;
	Thu, 26 Jan 95 20:45:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18841;
	Thu, 26 Jan 95 20:45:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRC-00038YC; Thu, 26 Jan 95 20:37 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: why not bounce in Apply?
Date: Fri, 20 Jan 1995 16:27:45 -0800
Message-Id: <Pine.ULT.3.92.950120162735.22534n-100000@shiva1.cac.washington.edu>
References: <puchoD2AEvE.9F1@netcom.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <puchoD2AEvE.9F1@netcom.com> 


It is on our to-do list to add...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 12 Jan 1995, Marcos Rubinstein wrote:

> Date: Thu, 12 JAN 1995 10:09:14 GMT 
> From: Marcos Rubinstein <pucho@netcom.com>
> Newgroups: comp.mail.pine
> Subject: why not bounce in Apply? 
> 
> Is there any reason why you didn't include bounce in Apply?...
> 
> sometimes I bounce several messages from a mail-list to a friend, and for 
> her it's better to receive them as individual pieces of mail than as 
> attachements...
> 
> or did I miss something?
> 
> BTW.... thanks for pine... I do help a lot of people to deal with their 
> mail... and pine, by far, is the easiest to learn and use...
> 
> Pucho
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:49:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29459;
	Thu, 26 Jan 95 20:49:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17715;
	Thu, 26 Jan 95 20:45:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17709;
	Thu, 26 Jan 95 20:45:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiR6-00038XC; Thu, 26 Jan 95 20:37 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: External Pagers
Date: Fri, 20 Jan 1995 14:46:37 -0800
Message-Id: <Pine.ULT.3.92.950120144130.511f-100000@shiva1.cac.washington.edu>
References: <3f1e2t$ovp@solaris.cc.vt.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3f1e2t$ovp@solaris.cc.vt.edu> 


Pine 3.92 will allow interactive programs to be used with the pipe
command.  

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 11 Jan 1995, matthew c. mead wrote:

> Date: 11 JAN 1995 20:12:13 GMT 
> From: matthew c. mead <mmead@goof.com>
> Newgroups: comp.mail.pine
> Subject: External Pagers 
> 
> 
> 	Well, I've built pine now, and got a nice pgp system going with it
> (which works well with elm, as well, btw).  The only problem is reading
> encrypted messages.  I don't like that you have to reply to them to decrypt and
> read them.  In elm, I have a script which will test to see if input is
> encrypted, and decrypt it prior to viewing if it is.  I'd like to fully switch
> to pine, but the lack of support for external pagers is the only thing holding
> me back.  Does anyone know of a hack anywhere that adds this support?
> Otherwise it's off to the pine source code with an axe I go...  :-)  Thanks in
> advance!
> 
> 
> 
> 
> 
> 
> 
> -matt
> 
> 
> -- 
> Matthew C. Mead -- System/Network Administration, User Support, Software Devel.
> Virginia Tech Center for Transportation Research
> Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com
> WWW: http://www.goof.com:/~mmead
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:49:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29480;
	Thu, 26 Jan 95 20:49:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18855;
	Thu, 26 Jan 95 20:45:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18849;
	Thu, 26 Jan 95 20:45:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRX-00038aC; Thu, 26 Jan 95 20:37 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: AIX Pine v3.9?
Date: Mon, 23 Jan 1995 13:56:55 -0800
Message-Id: <Pine.ULT.3.92.950123135519.22930C-100000@shiva1.cac.washington.edu>
References: <3fdcj2$nrv@lastactionhero.rs.itd.umich.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fdcj2$nrv@lastactionhero.rs.itd.umich.edu> 


A pre-compiled binary of Pine 3.91 for AIX 3.2 is available in

	ftp://ftp.cac.washington.edu/pine/unix-bin/pine-bin.a32

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 16 Jan 1995, Dennis Cheng wrote:

> Date: 16 JAN 1995 09:00:18 GMT 
> From: Dennis Cheng <chengman@umich.edu>
> Newgroups: comp.mail.pine
> Subject: AIX Pine v3.9? 
> 
> 
> Is Pine v 3.9 or 3.91 out and compiled for AIX yet?
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:59:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29655;
	Thu, 26 Jan 95 20:59:32 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19017;
	Thu, 26 Jan 95 20:55:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19011;
	Thu, 26 Jan 95 20:55:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRz-00038gC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: Wed, 25 Jan 1995 10:02:25 -0800
Message-Id: <Pine.ULT.3.92.950125095928.10586H-100000@shiva1.cac.washington.edu>
References: <3g4bkq$49c@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g4bkq$49c@cronkite.ocis.temple.edu> 


On 25 Jan 1995, Wet-Sprocket wrote:

> Date: 25 JAN 1995 02:05:14 GMT 
> From: Wet-Sprocket <shrim@worf.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: Re: [Q] pine-debug* files -- Make it *STOP* 
> 
[...]
>         #define NUMDEBUGFILES 4
> 
> You can also re-define the number of debug files pine produces.
> 

FYI, we are investigating setting this to 0 in future releases.  Doing so in
Pine 3.91, you will not get any .pine-debug files saved, but you will
(should) get a .pine-crash if Pine crashes....

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Thu Jan 26 20:59:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29676;
	Thu, 26 Jan 95 20:59:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17881;
	Thu, 26 Jan 95 20:55:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17875;
	Thu, 26 Jan 95 20:55:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRv-00038fC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Where src for HP ?
Date: Tue, 24 Jan 1995 14:33:43 -0800
Message-Id: <Pine.ULT.3.92.950124143236.22928H-100000@shiva1.cac.washington.edu>
References: <3g2ht4$6gg@pippo.sm.dsi.unimi.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g2ht4$6gg@pippo.sm.dsi.unimi.it> 


The current Pine 3.91 release includes an "hpp" port for HP/UX.  There 
are also pre-compiled binaries available.  Both can be found on 
ftp.cac.washington.edu in the pine directory.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 24 Jan 1995, Stefano Pisati IW2JXK wrote:

> Date: 24 JAN 1995 10:39:48 +0100 
> From: Stefano Pisati IW2JXK <pisati@pippo.sm.dsi.unimi.it>
> Newgroups: comp.mail.pine
> Subject: Where src for HP ? 
> 
> I need to compile Pine on a HP-UX server and I need the source
> ported to HP-UX... I've only found src and makefile only for
> other plataform. Where can I find src for HP ???
> 
> 		  Tnx in advance !!!
> 
>                     73 de -_ Stefano _-
> 
> PS: Please, reply via e-mail. Tnx !!!
> 
> 
>        "Stat rosa pristina nomine nomina nuda tenemus"
> ----------------------------------------------------------------
> Stefano Pisati  IW2JXK          Internet: pisati@dsi.unimi.it
> PGP:  finger pisati@ghost.dsi.unimi.it  or
>       e-mail pgp@dsi.unimi.it with Subject: GET Pisati
>      http://www.dsi.unimi.it/Users/Students/pisati/home
> ----------------------------------------------------------------
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:59:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29683;
	Thu, 26 Jan 95 20:59:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19025;
	Thu, 26 Jan 95 20:55:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19019;
	Thu, 26 Jan 95 20:55:48 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiS6-00038iC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: NG: Where is pine for term?
Date: Thu, 26 Jan 1995 08:53:10 -0800
Message-Id: <Pine.ULT.3.92.950126085156.8795C-100000@shiva1.cac.washington.edu>
References: <3g6snf$h9t@alfa.ist.utl.pt>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g6snf$h9t@alfa.ist.utl.pt> 


I very briefly used Pine with term some time ago.  It seemed to work
reasonably well without modification.... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 26 Jan 1995, Nuno Filipe M M Godinho wrote:

> Date: 26 JAN 1995 01:09:03 GMT 
> From: Nuno Filipe M M Godinho <l36867@ci.ist.utl.pt>
> Newgroups: comp.mail.pine
> Subject: NG: Where is pine for term? 
> 
> Hi.
> Is there any version of pine for term? (the linux modem multiplexer)
> I mean, there is tMosaic, tlynx, tncftp...
> Do you know of any tpine available?
> 
> thanks
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:59:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29738;
	Thu, 26 Jan 95 20:59:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19001;
	Thu, 26 Jan 95 20:55:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18993;
	Thu, 26 Jan 95 20:55:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRk-00038cC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] How can I include video attachments (.mpeg) ?
Date: Mon, 23 Jan 1995 14:19:04 -0800
Message-Id: <Pine.ULT.3.92.950123141749.22930E-100000@shiva1.cac.washington.edu>
References: <Pine.LNX.3.91.950120165657.5045A-100000@stoertebeker.zdv.uni-tuebingen.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.LNX.3.91.950120165657.5045A-100000@stoertebeker.zdv.uni-tuebingen.de> 


Pine does not currently recognize mpeg files, so it labels that
application/octet-stream.  Pine 3.92 wqill have support for a .mime-types
file, so you can add other attachment types... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 20 Jan 1995, Dierk Schwick wrote:

> Date: Fri, 20 JAN 1995 17:23:49 +0100 
> From: Dierk Schwick <zrnsc01@stoertebeker.zdv.uni-tuebingen.de>
> Newgroups: comp.mail.pine
> Subject: [Q] How can I include video attachments (.mpeg) ? 
> 
> I didn't find any answer in the FAQ's nor in documentations at
> http://www.cac.washington.edu:1180/pine/
> 
> therefore i ask here.
> 
> I want to know if and when how it's possible to include video animations
> in a normal email message with pine and have a look on them later on from 
> pine via external viewer.
> 
> When I try so have a look on the attachment it's impossible in Pine!
> Images will be shown via the image-viewer configuration in .pinerc or
> my .mailcap but .mpegs aren't recogneized. It looks like that they 
> are mime-coded as application and not as video.
> 
> Here an extract from my .mailcap:
> 
> # This maps MPEG video data to the viewer 'mpeg_play'.
> # (Mpeg_play is part of the MPEG distribution from The Berkeley Plateau
> # Research Group and is available via anonymous ftp from toe.cs.berkeley.edu.)
> video/mpeg; mpeg_play %s ; test=test -n "$DISPLAY"
> 
> # Type octet-stream (binary) data can be displayed as a hex dump before
> # you decide whether or not you want to save it to a file.  (Hd is just
> # a standard hex dump program.  You could use "od" if you don't have an
> # "hd".  Naive users may find the output from this entry confusing.)
> application/octet-stream; hd; copiousoutput; description="Hex dump of data"
> 
> There is no global mailcap only my personal here! And the global pine.conf
> looks like the personal (the viewers obviously)
> 
> INcluding postscript-files or images works really fine. When i want to 
> have a look on the attachments the external viewer (ghostview or xv) will
> be opened automatically from pine. So far so good, but why don't work my 
> animations?
> 
> I don't read ths conference regularly, therefore please post answers to my
> email address, too! 
> 
> Thanks a lot!
> 
> -- Dierk Schwick
> 
> ----------------------------------------------------------------------------
> Dierk Schwick                          |Tel.:               +49-7071-29-6957
>                                        |Fax :               +49-7071-29-5912
> Zentrum fuer Datenverarbeitung         |privat:               +49-7071-49813
> Universitaet Tuebingen                 |email: dschwick@zdv.uni-tuebingen.de
> ----------------------------------------------------------------------------
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:59:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29784;
	Thu, 26 Jan 95 20:59:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17905;
	Thu, 26 Jan 95 20:55:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17899;
	Thu, 26 Jan 95 20:55:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiSK-00038lC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: some news folders disapper !! HELP
Date: Thu, 26 Jan 1995 09:05:41 -0800
Message-Id: <Pine.ULT.3.92.950126090358.8795F-100000@shiva1.cac.washington.edu>
References: <Pine.SUN.3.90.950125232938.14792A-100000-100000-100000@trabzon>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.90.950125232938.14792A-100000-100000-100000@trabzon> 


This may be a problem with the Pine 3.90 release you are using.  Upgrade to
Pine 3.91 and it should work better... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Wed, 25 Jan 1995, Arcin Bozkurt wrote:

> Date: Wed, 25 JAN 1995 23:53:02 +0300 (EET) 
> From: Arcin Bozkurt <arcin@ug.bcc.bilkent.edu.tr>
> Newgroups: comp.mail.pine
> Subject: some news folders disapper !! HELP 
> 
> 
> 
> 	Hi,all !!
> 	I am using Pine 3.90 and I have a problem with my news folders.
> The problem is that my folders disappear after i read another folder.
> Strange isn't it ?
> 	Here is the story ...
> 	I am at the moment subscribed to comp.mail.pine and 
> comp.mail.misc. In another pine window i subscribed to sci.space read two 
> news there and deleted those two news i read. Then i pressed L to turn 
> back to folder list.
> 	What do you i see at the window? Only sci.space!! The other two 
> folders are lost. I happens all the time and i do not the way out.
> 	I also looked at my .newsrc file. It only contains the following 
> after the operation :
> 
> sci.space:
> 
> 	Can anyone with this peculiar behaviour of Pine 3.90.
> 	Thank you very much in advance .
> 
> 					Arcin Bozkurt
> 					Bilkent University
> 					EE - Junior
> 
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 20:59:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29794;
	Thu, 26 Jan 95 20:59:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17897;
	Thu, 26 Jan 95 20:55:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17891;
	Thu, 26 Jan 95 20:55:48 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiS7-00038jC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Re-Sending EMail??
Date: Thu, 26 Jan 1995 08:58:14 -0800
Message-Id: <Pine.ULT.3.92.950126085702.8795E-100000@shiva1.cac.washington.edu>
References: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> <Pine.SOL.3.91.950126012119.29923C-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SOL.3.91.950126012119.29923C-100000@hobbes> 


On 25 Jan 1995, Ed Greshko wrote:

> Date: 25 JAN 1995 09:55:25 -0800 
> From: Ed Greshko <Edward.M.Greshko@cdc.com>
> Newgroups: comp.mail.pine
> Subject: Re: Re-Sending EMail?? 
> 
> On Wed, 25 Jan 1995, Dan Mullen wrote:
> 
> > What Pine command do I use to resend a previously sent message
> > that has been returned due to Wrong Address or Server Error?
> > 
> > This has happened a couple ot times and had to retype the whole message 
> > again. Suggestion Please!!
> 
> 	Go to your "sent-mail" folder and "F"orward the message to the
> proper address.
> 

Or Bounce the message from sent-mail, or save it to postponed-msgs and resume
the composition... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Thu Jan 26 21:00:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29835;
	Thu, 26 Jan 95 21:00:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19009;
	Thu, 26 Jan 95 20:55:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19003;
	Thu, 26 Jan 95 20:55:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRs-00038eC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Mailing list with Pine?
Date: Tue, 24 Jan 1995 14:17:45 -0800
Message-Id: <Pine.ULT.3.92.950124141716.22930c-100000@shiva1.cac.washington.edu>
References: <3g2loj$ch3@tethys.otol.fi>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g2loj$ch3@tethys.otol.fi> 


The best way to do this is to upgrade to Pine 3.91 which allows global 
and shared addressbooks.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 24 Jan 1995, PeTrI pIeTiKaInEn wrote:

> Date: 24 JAN 1995 10:45:39 GMT 
> From: PeTrI pIeTiKaInEn <tecnic@tlti.tokem.fi>
> Newgroups: comp.mail.pine
> Subject: Mailing list with Pine? 
> 
> I was wondering is it possible to create a mailing list with Pine, where 
> everyone in the list can mail? I mean I created a list for our demo group 
> with address books command S CreateList... but I don't know how other 
> members could mail into it?
> 
> We have Pine v.3.87 
> 
> I hope someone could help us? Thanks in advance
> 
> --
> 
> Jay FX - member of BlacKOuT and Bitch Control  	: Be merry
> email:	tecnic@tlti.tokem.fi			:    Be bright...
> IRC:	JayFx					: - Carbon D
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:01:06 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29890;
	Thu, 26 Jan 95 21:01:06 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17861;
	Thu, 26 Jan 95 20:55:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17855;
	Thu, 26 Jan 95 20:55:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRe-00038bC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: attachments
Date: Mon, 23 Jan 1995 14:12:30 -0800
Message-Id: <Pine.ULT.3.92.950123141105.22930D-100000@shiva1.cac.washington.edu>
References: <Pine.SOL.3.91.950116125705.5703A-100000@explorer>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SOL.3.91.950116125705.5703A-100000@explorer> 


Are you using PC-Pine or telnetting to your Solaris account and using Unix
Pine?  If the latter, you need to ftp the file over to your Unix account
first... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Mon, 16 Jan 1995, Cuauhtemoc wrote:

> Date: Mon, 16 JAN 1995 17:58:19 GMT 
> From: Cuauhtemoc <gonzales@clark.net>
> Newgroups: comp.mail.pine
> Subject: attachments 
> 
> 	Pine,
> 		I have a slip account with a local Internet access 
> provider and would like to attach a document from my a:drive to an email 
> message using pine.  I can't seem to get it to work.  Is it possible?  
> 
> Thanks
> 
> 
> Enrique Gonzales
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:01:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29919;
	Thu, 26 Jan 95 21:01:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19033;
	Thu, 26 Jan 95 20:55:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19027;
	Thu, 26 Jan 95 20:55:50 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiSR-00038mC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Bug Report: Addressbook - pine
Date: Thu, 26 Jan 1995 09:07:49 -0800
Message-Id: <Pine.ULT.3.92.950126090648.8795G-100000@shiva1.cac.washington.edu>
References: <Pine.ULT.3.90.950126101259.23649A-100000@psws.uia.ac.be>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.90.950126101259.23649A-100000@psws.uia.ac.be> 


Pine 3.90 has several very serious bugs in the addressbook handling 
code.  These are fixed in the current Pine 3.91 release.  Upgrade!

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 26 Jan 1995, Bertel.DeGroote wrote:

> Date: 26 JAN 1995 01:11:40 -0800 
> From: Bertel.DeGroote <dgroote@psws.uia.ac.be>
> Newgroups: comp.mail.pine
> Subject: Bug Report: Addressbook - pine 
> 
> 
> Hallo,
> 
> I tried to create an Adressbook and to take the the adresses out of the 
> messages I received and put them in the Adressbook.
> 
> When I try  usin, updatin, renaming the Adressbook or I want to correct 
> the adresses/names, I somehow create problems.
> 
> I can't open the Adressbook
> 
> and the application blocks.
> 
> On my screen I See : Adressbook changed by another process re-syncing
> 		
> 		     Resetting Adress.book
> 	
> And I have to reset the computer (warm .start)
> 
> Can you help me and send me also some easy understandable step by 
> step information -while I'm not acquainted with computers- relating to the 
> use of the Adressbook.
> 
> Thank you in advance for your benevolent help.
> 
> 
> 
> Bertel De Groote
> 
> dgroote@uia.ac.be
> 
> 
> 
> 			  


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:02:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29971;
	Thu, 26 Jan 95 21:02:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17889;
	Thu, 26 Jan 95 20:55:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17883;
	Thu, 26 Jan 95 20:55:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiS4-00038hC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: What do I do once I download pico?
Date: Wed, 25 Jan 1995 10:57:04 -0800
Message-Id: <Pine.ULT.3.92.950125105544.22930g-100000@shiva1.cac.washington.edu>
References: <3g3rbc$ke1@nic-nac.CSU.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g3rbc$ke1@nic-nac.CSU.net> 


Rename it, move it to the appropriate bin directory and mark it 
executable, i.e.

	mv pico-bin.hpux9 /usr/local/bin/pico
	chmod +x /usr/local/bin/pico

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 24 Jan 1995, Micheal Wojciechowski wrote:

> Date: 24 JAN 1995 21:27:08 GMT 
> From: Micheal Wojciechowski <mike@newport.lib.ca.us>
> Newgroups: comp.mail.pine
> Subject: What do I do once I download pico? 
> 
> I downloaded the version for HP-UX9, because this is the operating system we
> are running, so now I have this file pico-bin.hpux9 and I don't know what 
> to do with it now.  I am not very unix literate, although I know it enoough 
> that I feel comfortable using it.  Any help would be appreciated. Thanks in 
> advance.
> 
> 
> Mike
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:02:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29992;
	Thu, 26 Jan 95 21:02:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19041;
	Thu, 26 Jan 95 20:55:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19035;
	Thu, 26 Jan 95 20:55:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiSU-00038nC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Deletion of empty folders
Date: Thu, 26 Jan 1995 11:16:44 -0800
Message-Id: <Pine.ULT.3.92.950126111622.22930R-100000@shiva1.cac.washington.edu>
References: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl> 


Pine does not have an option to auto-delete empty folders...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 26 Jan 1995, Karel Kubat wrote:

> Date: Thu, 26 JAN 1995 07:24:08 GMT 
> From: Karel Kubat <karel@bambix.icce.rug.nl>
> Newgroups: comp.mail.pine
> Subject: Deletion of empty folders 
> 
> I am afraid that I'm missing something quite obvious (but I failed to find a
> pointer in the setup menus). I at times keep mail around in temporary folders,
> 'till I get around to answering it. Then I remove the mail from the temp
> folder.
> 
> How do I get Pine to automatically remove empty folders? Or do I really have
> to run say an external shellscript to accomplish this?
> 
> Thanx in advance.. please reply by E-mail too, I might miss an answer.
> --
> Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
> From the Obscure Dictionary of Medical Terms:
> Lymph: A special Fairy.
> 
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:03:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00134;
	Thu, 26 Jan 95 21:03:20 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17869;
	Thu, 26 Jan 95 20:55:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17863;
	Thu, 26 Jan 95 20:55:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiRm-00038dC; Thu, 26 Jan 95 20:38 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: HELP....
Date: Mon, 23 Jan 1995 14:20:53 -0800
Message-Id: <Pine.ULT.3.92.950123141959.22930F-100000@shiva1.cac.washington.edu>
References: <3fpm0t$hnd@reznor.larc.nasa.gov>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fpm0t$hnd@reznor.larc.nasa.gov> 


Use
	inbox-path={fennel.cs.hamptonu.edu}INBOX

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 21 Jan 1995, ICASE System Administrator wrote:

> Date: 21 JAN 1995 00:54:53 GMT 
> From: ICASE System Administrator <icaseadm@icase.edu>
> Newgroups: comp.mail.pine
> Subject: HELP.... 
> 
> I am in the process of installing Pine 3.91 on our Sun systems as well as the PC network
> using windows.  I *think* the software has been installed correctly on the sun's as I am
> able to read/send mail without any problems...
> The PC's for some reason are not working...when I try to run pine from one of the PC's, the
> INBOX does not get opened...I am aware that the pinerc has to be changed...I am not sure as
> to what entry I need to put for the INBOX...
> our server name: fennel.cs.hamptonu.edu
> smtp-server: fennel.cs.hamptonu.edu
> imap server: fennel.cs.hamptonu.edu
> 
> this is the entry in the pinerc file currently: inbox-path=/var/spool/mail/$USER  (SUN'S)
> PC's: inbox-path={fennel.cs.hamptonu.edu}/var/spool/mail --- I know this entry is incorrect..
> 
> Any help will be greatly appreciated..... PLEASE EMAIL DIRECTLY TO ME AT:
> tm@cs.hamptonu.edu 
> 
> thanking you in advance.....
> 
> tm@cs.hamptonu.edu  PLEASE DONT POST TO THIS NEWSGROUP...email to me..
> 
> 


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:10:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00281;
	Thu, 26 Jan 95 21:10:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17919;
	Thu, 26 Jan 95 20:55:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17913;
	Thu, 26 Jan 95 20:55:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXiY6-00038TC; Thu, 26 Jan 95 20:44 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Pine Frequently Asked Questions (FAQ)
Date: Fri, 20 Jan 1995 10:42:51 -0800
Message-Id: <Pine.ULT.3.92.950120104128.7477A-820000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1726109301-790627371=:7477"
Content-Id: <Pine.ULT.3.92.950120104128.7477B@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1726109301-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477C@shiva1.cac.washington.edu>
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--0-1726109301-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477D@shiva1.cac.washington.edu>
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1635971033-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477E@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477F@shiva1.cac.washington.edu>
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477G@shiva1.cac.washington.edu>
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477H@shiva1.cac.washington.edu>
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477I@shiva1.cac.washington.edu>
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477J@shiva1.cac.washington.edu>
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477K@shiva1.cac.washington.edu>
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477L@shiva1.cac.washington.edu>
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477M@shiva1.cac.washington.edu>
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--0-1635971033-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1325855154-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477N@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477O@shiva1.cac.washington.edu>
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477P@shiva1.cac.washington.edu>
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477Q@shiva1.cac.washington.edu>
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477R@shiva1.cac.washington.edu>
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477S@shiva1.cac.washington.edu>
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477T@shiva1.cac.washington.edu>
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477U@shiva1.cac.washington.edu>
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477V@shiva1.cac.washington.edu>
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477W@shiva1.cac.washington.edu>
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477X@shiva1.cac.washington.edu>
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--0-1325855154-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1804407223-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477Y@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477Z@shiva1.cac.washington.edu>
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477a@shiva1.cac.washington.edu>
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477b@shiva1.cac.washington.edu>
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477c@shiva1.cac.washington.edu>
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

--0-1804407223-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-21832344-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477d@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-21832344-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477e@shiva1.cac.washington.edu>
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

--0-21832344-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477f@shiva1.cac.washington.edu>
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--0-21832344-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-507512823-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477g@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477h@shiva1.cac.washington.edu>
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477i@shiva1.cac.washington.edu>
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477j@shiva1.cac.washington.edu>
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477k@shiva1.cac.washington.edu>
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
--0-507512823-790627371=:7477
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1964980869-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477l@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1964980869-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477m@shiva1.cac.washington.edu>
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--0-1964980869-790627371=:7477
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="sun-to-mime.perl"; SITE="cs.utk.edu"; ACCESS-TYPE=ANON-FTP; DIRECTORY="pub/MIME"; MODE=ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477n@shiva1.cac.washington.edu>

--0-1964980869-790627371=:7477
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="sun-to-mime.c"; SITE="cs.utk.edu"; ACCESS-TYPE=ANON-FTP; DIRECTORY="pub/MIME"; MODE=ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477o@shiva1.cac.washington.edu>

--0-1964980869-790627371=:7477--
--0-507512823-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1178456012-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477p@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477q@shiva1.cac.washington.edu>
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477r@shiva1.cac.washington.edu>
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477s@shiva1.cac.washington.edu>
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477t@shiva1.cac.washington.edu>
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477u@shiva1.cac.washington.edu>
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477v@shiva1.cac.washington.edu>
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--0-1178456012-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-785766230-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477w@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-785766230-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477x@shiva1.cac.washington.edu>
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
--0-785766230-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477y@shiva1.cac.washington.edu>
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
--0-785766230-790627371=:7477
Content-Type: MULTIPART/MIXED; BOUNDARY="0-546205362-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477z@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-546205362-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477A@shiva1.cac.washington.edu>
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--0-546205362-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=elm-to-pine
Content-ID: <Pine.ULT.3.92.950120104128.7477B@shiva1.cac.washington.edu>
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--0-546205362-790627371=:7477--
--0-785766230-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-369780167-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477C@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477D@shiva1.cac.washington.edu>
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477E@shiva1.cac.washington.edu>
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477F@shiva1.cac.washington.edu>
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477G@shiva1.cac.washington.edu>
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477H@shiva1.cac.washington.edu>
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477I@shiva1.cac.washington.edu>
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--0-369780167-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-117366150-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477J@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-117366150-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477K@shiva1.cac.washington.edu>
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
--0-117366150-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477L@shiva1.cac.washington.edu>
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
--0-117366150-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477M@shiva1.cac.washington.edu>
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--0-117366150-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-656848291-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477N@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-656848291-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477O@shiva1.cac.washington.edu>
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

--0-656848291-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477P@shiva1.cac.washington.edu>
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

--0-656848291-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477Q@shiva1.cac.washington.edu>
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--0-656848291-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-456850581-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477R@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477S@shiva1.cac.washington.edu>
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477T@shiva1.cac.washington.edu>
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477U@shiva1.cac.washington.edu>
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477V@shiva1.cac.washington.edu>
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--0-456850581-790627371=:7477--
--0-1726109301-790627371=:7477--


From owner-pine-info@cac.washington.edu  Thu Jan 26 21:44:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01008;
	Thu, 26 Jan 95 21:44:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19721;
	Thu, 26 Jan 95 21:40:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19715;
	Thu, 26 Jan 95 21:40:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXjC9-00038UC; Thu, 26 Jan 95 21:26 PST
To: pine-info@cac.washington.edu
From: schueman@access.digex.net (Greg Schueman)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 26 Jan 1995 19:24:49 -0500
Message-Id: <3g9egh$s6l@access3.digex.net>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca> <3g18a5$epp@gryphon.phoenix.net>

In article <3g18a5$epp@gryphon.phoenix.net>,
Paul Flores <pflores@phoenix.phoenix.net> wrote:
>Rashid Bawa (rbawa@gbc.gbrownc.on.ca) wrote:
>: I am looking out for POP binaries (POP, POP2, POP3) that will run on
>: a SparcClassic running Solaris 2.3. If anyone has the location of a site,
>: please send me email.
>
>: Thanking you in advance.
>
>
>Please post here as well!!!!   (Or send me email as well!!!)
>
>Paul
>
>http://www.phoenix.net/USERS/pflores.html
>


Here goes, you can find a POP3 mail server, source and binaries
ported to Solaris 2.x at:

ftp://ftp.digex.net/pub/access/schueman/popper.tar.gz

This code has been subjected to constant use since April 1994 under 
Solaris 2.3.

Enjoy,

 -Greg Schueman




From owner-pine-info@cac.washington.edu  Thu Jan 26 21:54:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01219;
	Thu, 26 Jan 95 21:54:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19886;
	Thu, 26 Jan 95 21:51:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ip129179-30-16.cdc.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19880;
	Thu, 26 Jan 95 21:51:33 -0800
Received: by hobbes.twntpe.cdc.com; Fri, 27 Jan 95 13:50:01 -0800
Date: Fri, 27 Jan 1995 13:50:00 -0800 (GMT)
From: Ed Greshko <Edward.M.Greshko@cdc.com>
X-Sender: egreshko@hobbes
Reply-To: egreshko@cosmo.twntpe.cdc.com
To: David L Miller <dlm@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Re-Sending EMail??
In-Reply-To: <Pine.ULT.3.92.950126085702.8795E-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SOL.3.91.950127134437.16335F-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 26 Jan 1995, David L Miller wrote:

> 
> On 25 Jan 1995, Ed Greshko wrote:
> 
> > Date: 25 JAN 1995 09:55:25 -0800 
> > From: Ed Greshko <Edward.M.Greshko@cdc.com>
> > Newgroups: comp.mail.pine
> > Subject: Re: Re-Sending EMail?? 
> > 
> > On Wed, 25 Jan 1995, Dan Mullen wrote:
> > 
> > > What Pine command do I use to resend a previously sent message
> > > that has been returned due to Wrong Address or Server Error?
> > > 
> > > This has happened a couple ot times and had to retype the whole message 
> > > again. Suggestion Please!!
> > 
> > 	Go to your "sent-mail" folder and "F"orward the message to the
> > proper address.
> > 
> 
> Or Bounce the message from sent-mail, or save it to postponed-msgs and resume
> the composition... 

	In this particular instance I'd prefer to use forward over the
bounce command.  

	If I am correct the bounce command will leave the original To:'s
and Cc:'s attached to the message and but will add a Sender: header.

	Not all UAs will show the Sender: header....and it sometimes leave
people scratching their heads as to how an email reached them with an
incorrect email address......

	Just my opinion.....

					Ed

Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C



From owner-pine-info@cac.washington.edu  Thu Jan 26 23:29:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03457;
	Thu, 26 Jan 95 23:29:08 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19943;
	Thu, 26 Jan 95 23:26:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19937;
	Thu, 26 Jan 95 23:26:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXkpK-00038YC; Thu, 26 Jan 95 23:10 PST
To: pine-info@cac.washington.edu
From: jywong@abalone.ucsb.edu (Joyce Y. Wong)
Subject: how to set up news on pine; do i need imap?
Date: 26 Jan 1995 17:09:49 -0800
Message-Id: <3g9h4t$dng@abalone.ucsb.edu>


how do i set up my pine account so i can read news there?
which configuration item is it?

i normally read news with trn

thanks
joyce
















From owner-pine-info@cac.washington.edu  Fri Jan 27 00:06:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04395;
	Fri, 27 Jan 95 00:06:26 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21686;
	Fri, 27 Jan 95 00:02:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21680;
	Fri, 27 Jan 95 00:02:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXlQ6-00038UC; Thu, 26 Jan 95 23:48 PST
To: pine-info@cac.washington.edu
From: Roland Rosenfeld <roland@spinnaker.rhein.de>
Subject: Re: 8bit characters
Date: Thu, 26 Jan 1995 16:34:23 +0100
Message-Id: <Pine.LNX.3.91.950126162747.1720B-100000-100000@spinnaker.rhein.de>
References: <Pine.OSF.3.91a.950115053719.2190F-100000-100000-100000@saul1.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.OSF.3.91a.950115053719.2190F-100000-100000-100000@saul1.u.washington.edu> 

Hi Halldor!

On Sun, 15 Jan 1995, Halldor Arnason wrote:

> I am having trouble sending 8bit characters using pine.  I want to
> define in the header "Content-Transfer-Encoding: 8bit" and can do
> that.  The trouble is when pine finds any foreign characters in the
> text (as it will in this message), it defines it's own C-T-E header
> with QUOTED-PRINTABLE, which overwrites my header.  It does this
> just silently when sending mail, but gives a error message because
> of duplicate headers when I try to post to a news-group.  So I had
> to remove my header to be able to send this message.

I also had this problem, cause when I send messages to FidoNet there
is noch converter QP->8Bit and in FidoNet nobody can understand the
QPs.  So I got the pine-source 3.91 and added the following patch:

--------------------------- schnipp -------------------------------
--- send.c.org	Fri Dec 23 23:38:54 1994
+++ send.c	Fri Dec 23 23:53:36 1994
@@ -3942,7 +3942,7 @@
 
 	switch (body->encoding) {	/* all else needs filtering */
 	  case ENC8BIT:			/* encode 8BIT into QUOTED-PRINTABLE */
-	    gf_link_filter(gf_8bit_qp);
+	    /* gf_link_filter(gf_8bit_qp); */
 	    break;
 
 	  case ENCBINARY:		/* encode binary into BASE64 */
@@ -3998,7 +3998,7 @@
     if (body->encoding)		/* note: encoding 7BIT never output! */
       sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012",
 	       body_encodings[body->encoding == ENCBINARY ? ENCBASE64 :
-			      body->encoding == ENC8BIT ? ENCQUOTEDPRINTABLE :
+			      body->encoding == ENC8BIT ? ENC8BIT :
 			      body->encoding <= ENCMAX ? body->encoding :
 							 ENCOTHER]);
     if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012",
--------------------------- schnipp -------------------------------

With this little patch pine uses "8bit" instead of "Quoted-Printable",
if it finds any character with the 8th bit set. This solved the
problem for me, but it would be nice, if this could be configurable in
.pinerc....

Ciao

	Roland

-- 
  * Internet: roland@spinnaker.rhein.de * Fido: 2:2450/111.13 *



From owner-pine-info@cac.washington.edu  Fri Jan 27 00:13:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04615;
	Fri, 27 Jan 95 00:13:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21614;
	Fri, 27 Jan 95 00:00:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from tavor.openu.ac.il by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21608;
	Thu, 26 Jan 95 23:59:54 -0800
Received: by tavor.openu.ac.il id AA23696
     (5.67a8/IDA-1.5 for pine-Info@cac.washington.edu); Fri, 27 Jan 1995 09:59:47 +0200
Date: Fri, 27 Jan 1995 09:59:46 +0200 (IST)
From: Shimon Winerich - Open University of Israel <shimon@tavor.openu.ac.il>
To: pine-Info@cac.washington.edu
Message-Id: <Pine.SUN.3.91.950127095820.18966A-100000@tavor>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

signoff pine-info



     .__________________________________________________________.
     |                                                          |
     | Shimon Winerich       Computer Department                |
     |                       Open University Of Israel          |
     |                       16 Klauzner st. Ramat Aviv         |
     |                       Phone      : 03-6460320/1          |
     |                       Fax        : 03-6460454            |
    /)                       E-mail: Shimon@tavor.openu.ac.il   (\
   / )                                                          ( \
  ( (|__________________________________________________________|) )
(((\ \)  /,)                                               / )  / //))/
(\\\\ \_/ /                                                \ \_/ /////
 \       /                                                  \       /
  \    _/                                                    \_    /





From owner-pine-info@cac.washington.edu  Fri Jan 27 08:35:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17571;
	Fri, 27 Jan 95 08:35:24 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29121;
	Fri, 27 Jan 95 08:29:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29115;
	Fri, 27 Jan 95 08:29:07 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06334;
	Fri, 27 Jan 95 08:29:03 -0800
Date: Fri, 27 Jan 1995 08:28:36 -0800 (PST)
From: David L Miller <dlm@cac.washington.edu>
To: egreshko@cosmo.twntpe.cdc.com
Cc: pine-info@cac.washington.edu
Subject: Re: Re-Sending EMail??
In-Reply-To: <Pine.SOL.3.91.950127134437.16335F-100000@hobbes>
Message-Id: <Pine.ULT.3.92.950127082548.22930b-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 27 Jan 1995, Ed Greshko wrote:

> Date: Fri, 27 Jan 1995 13:50:00 -0800 (GMT)
> From: Ed Greshko <Edward.M.Greshko@cdc.com>
> To: David L Miller <dlm@cac.washington.edu>
> Cc: pine-info@cac.washington.edu
> Subject: Re: Re-Sending EMail??
> 
> 
> 	If I am correct the bounce command will leave the original To:'s
> and Cc:'s attached to the message and but will add a Sender: header.
> 

All of the original headers remain intact and Resent-To, Resent-From, etc,
are added. 

> 	Not all UAs will show the Sender: header....and it sometimes leave
> people scratching their heads as to how an email reached them with an
> incorrect email address......
> 

Not all UAs show the Resent-* headers either, including older versions of
Pine......


|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Fri Jan 27 09:28:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21127;
	Fri, 27 Jan 95 09:28:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00789;
	Fri, 27 Jan 95 09:19:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from cambridge.village.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00781;
	Fri, 27 Jan 95 09:18:56 -0800
Received: by cambridge.village.com; id AA06793; Fri, 27 Jan 1995 12:18:49 -0500
Date: Fri, 27 Jan 1995 12:18:48 -0500 (EST)
From: Michael Dawson <dawson@cambridge.village.com>
Subject: Capacity of Distribution Lists
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501271232.C6705-0100000@cambridge.village.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Could you please tell me how many names or addresss I can have on one 
distribution list? Is there an upper limit?
Thanks
Michael


From owner-pine-info@cac.washington.edu  Fri Jan 27 10:57:04 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24923;
	Fri, 27 Jan 95 10:57:04 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02850;
	Fri, 27 Jan 95 10:47:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02844;
	Fri, 27 Jan 95 10:47:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXvXZ-00038XC; Fri, 27 Jan 95 10:37 PST
To: pine-info@cac.washington.edu
From: l36867@ci.ist.utl.pt (Nuno Filipe M M Godinho)
Subject: NG: Where is pine for term?
Date: 26 Jan 1995 01:09:03 GMT
Message-Id: <3g6snf$h9t@alfa.ist.utl.pt>

Hi.
Is there any version of pine for term? (the linux modem multiplexer)
I mean, there is tMosaic, tlynx, tncftp...
Do you know of any tpine available?

thanks



From owner-pine-info@cac.washington.edu  Fri Jan 27 10:57:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24950;
	Fri, 27 Jan 95 10:57:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00960;
	Fri, 27 Jan 95 10:42:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00954;
	Fri, 27 Jan 95 10:42:15 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXvQ4-00038cC; Fri, 27 Jan 95 10:29 PST
To: pine-info@cac.washington.edu
From: mike@newport.lib.ca.us (Micheal Wojciechowski)
Subject: I figured out my prob. with pico!!  New Problem.
Date: 27 Jan 1995 16:47:33 GMT
Message-Id: <3gb835$el3@nic-nac.CSU.net>

I figured out what the problem is.  I am running it on a 300 series HP9000
which has a CISC processor in it.  I moved it over to a G30 which uses a RISC
processor and it works fine.  

The next question I have is, does anyone have it compiled on a CISC processor
where I might be able to get a hold of it?  It would be greatly appreciated.

Thanks in advance.

Mike


From owner-pine-info@cac.washington.edu  Fri Jan 27 11:18:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26140;
	Fri, 27 Jan 95 11:18:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01585;
	Fri, 27 Jan 95 11:10:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01579;
	Fri, 27 Jan 95 11:10:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXvoi-00038YC; Fri, 27 Jan 95 10:54 PST
To: pine-info@cac.washington.edu
From: gkindt@allserv.rug.ac.be (Geert Kindt)
Subject: Acknowledgement
Date: 27 Jan 1995 09:01:23 GMT
Message-Id: <3gacp3$c8r@infoserv.rug.ac.be>

 I have a question about Pine.
Is it possible to receive a message from the server of your recipient
when your e-mail message arrived (or has been read) at the server of your
recipient ? (perhaps customized-hdrs ????)


Thank you very much,



Geert Kindt, University Gent, Belgium, Europe.




From owner-pine-info@cac.washington.edu  Fri Jan 27 11:38:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27084;
	Fri, 27 Jan 95 11:38:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03863;
	Fri, 27 Jan 95 11:27:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03857;
	Fri, 27 Jan 95 11:27:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXw50-00038ZC; Fri, 27 Jan 95 11:11 PST
To: pine-info@cac.washington.edu
From: hartr@hedunx.hedland.edu.au (Robert Hart)
Subject: Re: 3 questions ? ? ? Mail, Unix, Internet.
Date: 17 Jan 1995 21:44:35 +0800
Message-Id: <3fghk3$ntc@hedunx.hedland.edu.au>
References: <D29rpH.Gwo@freenet.carleton.ca>

David A Hosten (ao826@FreeNet.Carleton.CA) wrote:
: I am posting this in the hope somewhere out there [over the rainbow ;) ]
: somebody will be able these three questions. I'm a Unix newbie (being very
: familiar with less tasking [get it?] systems like Windoze, OS/2, WinNT,
: etc. So here are the questions:

Suggestion - get Linux and learn how much fun a personal Unix system is!
Apart from that...

: 1. (a) How do I change my environment to enable Pico to replace the vi editor,
: for my own personal use, on the Aix system we have at school. I know Pico
: well, and have grown accoustomed to it. Vi is fine, but, to me more of a
: pain in the butt to use. I'm auto-launched into a Korn shell at login, but
: can change at will. Any suggestions?  (b) How do I edit (and where do I
: find) my .tinrc file to enable Pico as my editor for Usenet read/reply?

set the VISUAL envirnoment variable as follows in your ~/.profile file

	export VISUAL=<editor name>
In my case I use emacs, which (IMHO) is vastly superior to pico!

: 2. (a) How may I retrieve posts to Usenet groups that my Freenet/University
: accounts do not subscribe to? There must be some way of doing an FTP
: equivalent to a site that collects the postings. (b) Is there a way of uucp
: retrieving them from sites? (c) If so, is it then possible to e-mail a group
: directly from the Pine mailer...what would be put into the To:  address
: section? (d) Why is the location of usenet-news servers appear to be
: so secret and inaccessible to the regular FTP public? Reason: there are some
: alt.fan.* groups that we would like to pick up to do some research on
: media influence.

Hm, I don't know the answer to this one...

: 3. Our recalcitrant sysadmins won't respond to e-mail, so what are you
: normally do with a student aix account? I'm trying to teach myself a bit
: of Unix (am going to decide between Free/386/NetBsd, Linux or
: Solaris [apparently have a $100 educational deal] versions), so will want
: to eventually know the answers to these questions anyway.

I would suggest you poke around and learn Unix, writing shell scripts,
try the differnt shells etc.

Have fun!

-- 
Robert Hart                                  hartr@hedunx.hedland.edu.au
Voice: +61 (0)91 72 0429                     Fax:   +61 (0)91 72 3560
Hedland College, PMB 1, South Hedland WA 6722 Australia


From owner-pine-info@cac.washington.edu  Fri Jan 27 12:26:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28819;
	Fri, 27 Jan 95 12:26:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02859;
	Fri, 27 Jan 95 12:06:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [155.77.110.40] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02853;
	Fri, 27 Jan 95 12:06:45 -0800
Received: by mro41.mro.usace.army.mil (5.61/1.34) id AA04918; Fri, 27 Jan 95 14:05:58 -0600
Date: Fri, 27 Jan 1995 14:05:57 -0600 (CST)
From: DOUGLAS L HEMSLEY <c2imsdlh@mro41.mro.usace.army.mil>
To: Info Pine <pine-info@cac.washington.edu>
Subject: Can not open "sent-mail" folder
Message-Id: <Pine.BSD.3.91.950127140125.3997B-100000@mro41.mro.usace.army.mil>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I get the following message when trying to open the "sent-mail" folder.
 (some number):pine: rld: perror:unresolvable symbol in pine: memove
I can open the "INBOX" and "saved-messages" folders.  Messages are 
getting written to the sent-mail folder.  I am running pine on a CD4460 
Contol Data machine running EP\IX 2.1.1AC (unix).   Thanks for any help.

Douglas L. Hemsley :)
US Army Corps of Engineers - Omaha District
c2imsdlh@mro41.mro.usace.army.mil
Phone: (402) 221-3036
Fax:   (402) 221-7457



From owner-pine-info@cac.washington.edu  Fri Jan 27 13:35:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02921;
	Fri, 27 Jan 95 13:35:45 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05014;
	Fri, 27 Jan 95 13:30:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05005;
	Fri, 27 Jan 95 13:30:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXy19-00038dC; Fri, 27 Jan 95 13:15 PST
To: pine-info@cac.washington.edu
From: malcor@class.class.org (Dan Malcor-LA Times)
Subject: feature-list and pine.conf.fixed
Date: 27 Jan 1995 14:44:42 GMT
Message-Id: <3gb0sq$2cs@news.cerf.net>

I want to prevent the use of the "enable-mail-check-cue" feature. 
But I can't get it to work (or not work). 
What will it tell the user who tries to change that which I have said NO to? 

Are there any samples of good pine.conf.fixed files out there?

-- 
 ======================================================================
        Dan Malcor              |  Los Angeles Times - Editorial Systems
  Internet: malcor@class.org    |  Systems Analyst / Programmer 


From owner-pine-info@cac.washington.edu  Fri Jan 27 13:44:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03331;
	Fri, 27 Jan 95 13:44:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05228;
	Fri, 27 Jan 95 13:38:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05222;
	Fri, 27 Jan 95 13:38:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXyA7-00038nC; Fri, 27 Jan 95 13:24 PST
To: pine-info@cac.washington.edu
From: agostini@iroe.fi.cnr.it (Alessandro Agostini)
Subject: Pine for windows!
Date: Thu, 26 Jan 95 21:59:29 GMT
Message-Id: <3g8h10$qpb@serra.unipi.it>

I hope that pine for windows i out in brief time.
So, I'm interesting to receive the source of pine for try to convert it in a true window application.
It is possible?

Can I rewrite in Italian Language for our Research Institutes ?

Can you tell me about ?

Thank you very much.
A.Agostini
IROE-CNR (National Research Council)
Florence Italy



From owner-pine-info@cac.washington.edu  Fri Jan 27 13:44:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03354;
	Fri, 27 Jan 95 13:44:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07035;
	Fri, 27 Jan 95 13:38:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07025;
	Fri, 27 Jan 95 13:38:26 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXy9r-00038bC; Fri, 27 Jan 95 13:24 PST
To: pine-info@cac.washington.edu
From: gojensen@interlink.no (G.O. Jensen)
Subject: Incoming folders ? GO AWAY!
Date: Fri, 27 Jan 95 07:34:41 GMT
Message-Id: <3g9ink$b0p@henry.interlink.no>

HI! Just been installing procmail on my system and all works well. Then I
start pine and find that NOW I have two folder collections, one for
Incoming and one for Collections. This used to be just a list like:
INBOX    sent-mail     read-mail

Now I've got

Incoming folders: INBOX
Folder collections: sent-mail    read-mail

I want it back the way it was. Now if I try to add an incoming box created by
procmail I get it BOTH in the Incoming folders list AND the Folder collections
list. So, how do just get ONE folder list? OR how do I prevent pine from adding
the folder I've manually added to Incoming to the Folder collections?

It is like this:

Incoming folders: INBOX     MAILINGLISTS
Folder collections: sent-mail	read-mail     MAILINFLISTS

and I want it like this (or not at all!)

Incoming folders: INBOX     MAILINGLISTS
Folder collections: sent-mail	read-mail


Thanks for any help ANY of you can give!

G.O. Jensen
gojensen@interlink.no

---
          />  Alis Volat Propriis
         /<                        G.O. Jensen
O[\\\\\\(O):::<===================================-
         \<                   gojensen@interlink.no
          \>


From owner-pine-info@cac.washington.edu  Fri Jan 27 13:45:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03404;
	Fri, 27 Jan 95 13:45:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07045;
	Fri, 27 Jan 95 13:38:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07037;
	Fri, 27 Jan 95 13:38:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rXyE6-00038oC; Fri, 27 Jan 95 13:29 PST
To: pine-info@cac.washington.edu
From: una@doliolum.biology.yale.edu (Una Smith)
Subject: Re: [Q] Signature switcher
Date: 27 Jan 1995 13:49:09 GMT
Message-Id: <3gatkl$663@news.ycc.yale.edu>
References: <3ersfq$p3h@net.bio.net> <3g8edk$oh9@insosf1.infonet.net> <3ga0op$s6b@news.ycc.yale.edu> <1995Jan27.065239.7076@comp.bioz.unibas.ch>

doelz@comp.bioz.unibas.ch (Reinhard Doelz) writes:

>I just happened to count my local mailboxes recently for administrative
>purposes (phone dial-in accounting etc). I came out with 85 different 
>addresses ... the same .sig or 'From' is put in. 
>...
>I could need a 'signature switcher' on UNIX - has anyone written something
>like this to get into pine? Not only the .sig file, but the 'From' should
>be changed as well. 

I have 5 (10, counting aliases).  I use procmail (obtained from ftp.uu.net)
to spot the account to which the mail was sent, and I pre-sort everything
into separate mailboxes in one account.  I have two signature variants that
I invoke with two keystroke commands.  That's all satisfactory;  the only
problem I have is that I still re-set the Reply-to line by hand, so that
any replies go to the same administrative address that received the original
query.

Reinhard, I think you might find it works better to work from a single
account, and change the Reply-to as needed, rather than work from many
accounts and change the From to identify yourself.

But the answer to your question would still be useful:  how can I change
the Reply-to line in a more automated fashion?

-- 
	Una Smith			una.smith@yale.edu

Department of Biology, Yale University, New Haven, CT  06520-8104  USA


From owner-pine-info@cac.washington.edu  Fri Jan 27 15:53:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA10711;
	Fri, 27 Jan 95 15:53:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08450;
	Fri, 27 Jan 95 15:48:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08444;
	Fri, 27 Jan 95 15:48:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY0BW-00038cC; Fri, 27 Jan 95 15:34 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: Global Address Book (RO ??)
Date: Fri, 27 Jan 1995 17:00:34 GMT
Message-Id: <D32pwz.Ft2@ssi.edc.org>
References: <3g7qoh$iio@belfort.daimi.aau.dk>

Hans Peter (hph@vki68.aar-vki.dk) wrote:
: Our global address book in pine 3.91 SCO-UNIX in:
: /w2/bruger/pineaddr/globaddr

: The problem is, that it is set to ReadOnly within pine for all users,
: including root, althoug the permissions for the file is set to rw.

I set it to be root's personal addressbook as well.  Now, whenever I want 
to make a change to the global addressbook, I just edit the personal 
mailbox while logged in as root.  I have the following line in /.pinerc:

address-book=/usr/lib/addressbook

And in pine.conf, I also have:

global-address-book=/usr/lib/addressbook

If you need to have a real personal addressbook for root, I'm sure you 
could work out something with multiple personal addressbooks.

Gunther Anderson



From owner-pine-info@cac.washington.edu  Fri Jan 27 17:52:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15793;
	Fri, 27 Jan 95 17:52:41 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13132;
	Fri, 27 Jan 95 17:49:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13126;
	Fri, 27 Jan 95 17:49:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY28d-00038cC; Fri, 27 Jan 95 17:39 PST
To: pine-info@cac.washington.edu
From: glenn@creator.ucns.uga.edu (Glenn Leavell)
Subject: Re: several Pine suggestions
Date: 27 Jan 1995 06:53:51 GMT
Message-Id: <3ga59v$1b3@hobbes.cc.uga.edu>
References: <3g0pds$r9c@hobbes.cc.uga.edu> <Pine.SUN.3.91.950126135229.26920Y-100000@grus.cus.cam.ac.uk>

In article <Pine.SUN.3.91.950126135229.26920Y-100000@grus.cus.cam.ac.uk>,
Barry Landy  <bl10@cam.ac.uk> wrote:

>On 23 Jan 1995, Glenn Leavell wrote:
>
>> 
>> 1)  In INDEX mode, allow the 'k' and 'j' keys to be used to move the current
>>     pointer up and down (j key would only function like this if
>>     jump short cut were turned on).  This convention can be
>>     found in vi, Elm, Gopher, and other utilities, so it makes things
>>     somewhat consistent.
>> 
>I think this is a dreadful idea. It of course harks back to long dead 
>terminals which had arrows engraved on those keys, accessed, I think, in 
>ESCAPE mode. 
>
>As someone who teaches Pine, its transparency is a major virtue, and 
>those places where this breaks down (like the dreadful Y for prYnt)  
>cause problems; when teaching it is wonderful for A to be Add, C compose 
>and so on. Previous and Next are enough alternatives to up-arrow and 
>down-arrow, thanks.

  My suggestion was to ADD functionality, not to change any of the
  current keys.  Even if the terminals you mentioned are long dead,
  the fact remains that many people use those keys today to navigate,
  and many other applications support them.

  Under my suggestion, you would still be able to use the "transparent"
  keys for navigation, but you would also be able to use some others,
  if you so desired.  It seems to me that one of Pine's virtues
  is the fact that it supports a lot of advanced functions, but you
  don't have to turn them all on.  My suggestions for navigational
  keys need not be the default.


-- 
Glenn Leavell, glenn@uga.edu
University of Georgia, University Computing and Networking Services


From owner-pine-info@cac.washington.edu  Fri Jan 27 18:05:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16241;
	Fri, 27 Jan 95 18:05:57 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11367;
	Fri, 27 Jan 95 18:02:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11361;
	Fri, 27 Jan 95 18:02:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY2Mk-00038cC; Fri, 27 Jan 95 17:54 PST
To: pine-info@cac.washington.edu
From: fyao@calum.csclub.uwaterloo.ca (Frank Yao)
Subject: Re: Random .sig?
Message-Id: <D3078v.88H@undergrad.math.uwaterloo.ca>
References: <3g3ogs$jkn@nic.iii.net>
Date: Thu, 26 Jan 1995 08:22:06 GMT

Steve Bernacki Jr <drown@iii1.iii.net> wrote:

>Is it possible to somehow have a random signature (out of a directory of
>signatures) be selected and pasted into pine?  If not, is there any way
>to get pine to run a program that would output such a random sig?

The only way I've thought of is to use a script of some sort which
randomly picks a file from a directory, and the pipes that file into
the editor of your choice.  I don't know all the details, but I could
find out if my comments here aren't enough to work with.

- frank


-- 
**********************************************************************
*  You may be right.  I may be crazy.  But it just may be a lunatic  *
*  you're looking for. 			- Billy Joel 		     *
*************************** Frank Yao, fyao@csclub.uwaterloo.ca ******


From owner-pine-info@cac.washington.edu  Fri Jan 27 18:13:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16405;
	Fri, 27 Jan 95 18:13:02 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13520;
	Fri, 27 Jan 95 18:10:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13514;
	Fri, 27 Jan 95 18:10:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY2Nv-00038fC; Fri, 27 Jan 95 17:55 PST
To: pine-info@cac.washington.edu
From: rubin@setinc.com (Don Rubin)
Subject: Need help hacking Pine
Date: 27 Jan 1995 16:40:42 GMT
Message-Id: <3gb7ma$225@news.cais.com>

I need to hack VMS Pine (3.89) to remove some SMTP
stuff that interferes with Reply. I am having trouble
putting in printf(... or fprintf(stderr in reply.c
whenever that code is executed Pine terminates. How
can I put some debug in so that I can examine what is
going on? (no I can't use the VMS debugger for this)
Thanks...




From owner-pine-info@cac.washington.edu  Fri Jan 27 20:06:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19009;
	Fri, 27 Jan 95 20:06:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12855;
	Fri, 27 Jan 95 19:59:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12849;
	Fri, 27 Jan 95 19:59:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY477-00038pC; Fri, 27 Jan 95 19:46 PST
To: pine-info@cac.washington.edu
From: doelz@comp.bioz.unibas.ch (Reinhard Doelz)
Subject: [Q] Signature switcher (Re: BIO-SRS/bionet.software.srs)
Message-Id: <1995Jan27.065239.7076@comp.bioz.unibas.ch>
References: <3ersfq$p3h@net.bio.net> <3g3mqs$7nd@net.bio.net> <3g3vo7$idu@news.ycc.yale.edu> <3g8edk$oh9@insosf1.infonet.net> <3ga0op$s6b@news.ycc.yale.edu>
Date: Fri, 27 Jan 1995 06:52:39 GMT

Una Smith (una@doliolum.biology.yale.edu) wrote:
: someone who will not do me the courtesy of identifying himself?  I
: think that's rather creepy, frankly.  It's a bit like getting heavy
: breathers on the telephone.  Yuck.  Oh, I sent the vote to biovote@
: net.bio.net, but the reply came from biohelp@net.bio.net.  Yuck.

I just happened to count my local mailboxes recently for administrative
purposes (phone dial-in accounting etc). I came out with 85 different 
addresses you can send mail to and soon or later I'll read it anyway. In order
to keep administration simple I happen to use accounts where the same .sig 
or 'From' is put in. 

Question -  depending on the operating system, I use pine, ean, eudora, and 
pmdf mailers. Not to mention various newsreaders to reply from. I could need
a 'signature switcher' on UNIX - has anyone written something like this 
to get into pine? Not only the .sig file,but the 'From' should be changed 
as well. 

Regards
Reinhard
-- 
 R.Doelz         Klingelbergstr.70| Tel. x41 61 267 2247  Fax x41 61 267 2078|
 Biocomputing        CH 4056 Basel| electronic Mail    doelz@ubaclu.unibas.ch|
 Biozentrum der Universitaet Basel|-------------- Switzerland ---------------|
<a href=http://beta.embnet.unibas.ch/>EMBnet Switzerland:info@ch.embnet.org</a> 


From owner-pine-info@cac.washington.edu  Fri Jan 27 20:35:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19469;
	Fri, 27 Jan 95 20:35:48 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13273;
	Fri, 27 Jan 95 20:33:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13267;
	Fri, 27 Jan 95 20:33:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY4iV-00038pC; Fri, 27 Jan 95 20:24 PST
To: pine-info@cac.washington.edu
From: robk@stack.urc.tue.nl (Rob Kouwenberg)
Subject: Re: Need to secure pine
Date: 26 Jan 1995 09:05:09 GMT
Message-Id: <3g7ok5$dob@tuegate.tue.nl>
References: <3g1e2s$5sk@case.cyberspace.com> <Pine.SUN.3.91.950124173442.24402T-100000@apus.cus.cam.ac.uk>

Barry Landy (bl10@cus.cam.ac.uk) wrote:
: We have the following set in pine.conf.fixed, and it seems to do the job:-
: no-enable-alternate-editor-cmd,
: no-always-use-alt-editor,
: no-enable-alternate-editor-implicitly,

Stupid question probably, but where to place these files ?

( yes, RTFM, but time is unfortunately not on my side always -:( )

TIA, best regards, Rob Kouwenberg

PS I placed pine in /usr/local/bin if this matters ..
--
[ robk@stack.urc.tue.nl,Gr.Adolfstraat86,5616BX,Eindhoven,The Netherlands ]


From owner-pine-info@cac.washington.edu  Fri Jan 27 20:35:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19477;
	Fri, 27 Jan 95 20:35:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15402;
	Fri, 27 Jan 95 20:33:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15396;
	Fri, 27 Jan 95 20:33:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY4fB-00038nC; Fri, 27 Jan 95 20:21 PST
To: pine-info@cac.washington.edu
From: rbawa@gbc.gbrownc.on.ca (Rashid Bawa)
Subject: POP binaries for SOLARIS 2.3
Date: 23 Jan 1995 11:49:21 -0500
Message-Id: <3g0mmh$1bg@gbc.gbrownc.on.ca>

I am looking out for POP binaries (POP, POP2, POP3) that will run on
a SparcClassic running Solaris 2.3. If anyone has the location of a site,
please send me email.

Thanking you in advance.

------------------------------------------------------------------------ 
Rashid Bawa                     George Brown College
System Administrator            146 Kendal Ave.
                                Toronto, Ontario
Phone:  (416) 944-4591          Canada
rbawa@gbrownc.on.ca
------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Fri Jan 27 20:43:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19638;
	Fri, 27 Jan 95 20:43:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15499;
	Fri, 27 Jan 95 20:40:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15493;
	Fri, 27 Jan 95 20:40:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY4md-00038sC; Fri, 27 Jan 95 20:29 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Deletion of empty folders
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl>
Mime-Version: 1.0
Date: Thu, 26 Jan 1995 07:24:08 GMT

I am afraid that I'm missing something quite obvious (but I failed to find a
pointer in the setup menus). I at times keep mail around in temporary folders,
'till I get around to answering it. Then I remove the mail from the temp
folder.

How do I get Pine to automatically remove empty folders? Or do I really have
to run say an external shellscript to accomplish this?

Thanx in advance.. please reply by E-mail too, I might miss an answer.
--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
>From the Obscure Dictionary of Medical Terms:
Lymph: A special Fairy.



From owner-pine-info@cac.washington.edu  Fri Jan 27 20:43:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19659;
	Fri, 27 Jan 95 20:43:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13373;
	Fri, 27 Jan 95 20:40:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13367;
	Fri, 27 Jan 95 20:40:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY4mG-00038kC; Fri, 27 Jan 95 20:28 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Re: Random .sig? 
In-Reply-To: <3g44kv$et4@gatecoms.gatecom.com> 
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950126081804.5530B-100000@bambix.icce.rug.nl>
References: <3g3ogs$jkn@nic.iii.net> <3g44kv$et4@gatecoms.gatecom.com> 
Mime-Version: 1.0
Date: Thu, 26 Jan 1995 07:20:04 GMT

On 25 Jan 1995, Matt Newell wrote:

> Steve Bernacki Jr (drown@iii1.iii.net) wrote:
> > Howdy y'all,
> 
> > Is it possible to somehow have a random signature (out of a directory of
> > signatures) be selected and pasted into pine?  If not, is there any way
> > to get pine to run a program that would output such a random sig?
> 
> This may not be exactly what you requested, but it works for me.
> 
> #! /sbin/sh
> mv ${HOME}/.signature ${HOME}/sig1.tmp
> mv ${HOME}/.sigb ${HOME}/sig2.tmp
> mv ${HOME}/.sigc ${HOME}/sig3.tmp
> mv ${HOME}/.sigd ${HOME}/sig4.tmp
> mv ${HOME}/.sige ${HOME}/sig5.tmp
> mv ${HOME}/sig1.tmp ${HOME}/.sige
> mv ${HOME}/sig2.tmp ${HOME}/.signature
> mv ${HOME}/sig3.tmp ${HOME}/.sigb
> mv ${HOME}/sig4.tmp ${HOME}/.sigc
> mv ${HOME}/sig5.tmp ${HOME}/.sigd
> 
> This is obviously for 5 sigs, but can be easily changed to work with more
> or less
> 
> I just have it in my .login, so that I have a different sig each time I
> login.
> 
>      Hope this helps,
>      Matt
> 
> **   Matt Newell                             mnewell@gatecoms.gatecom.com   **

Or of course grab a "cookie" program. Then have cron run the following shell
say each our:

    #!/bin/sh
    cat > ~/.signature << EOF
    --
    Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
    EOF
    cookie >> ~/.signature
    
That's at least how this below is generated..

--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
>From the Obscure Dictionary of Medical Terms:
Lymph: A special Fairy.


From owner-pine-info@cac.washington.edu  Fri Jan 27 20:44:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19681;
	Fri, 27 Jan 95 20:44:05 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15507;
	Fri, 27 Jan 95 20:40:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15501;
	Fri, 27 Jan 95 20:40:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY4mY-00038rC; Fri, 27 Jan 95 20:29 PST
To: pine-info@cac.washington.edu
From: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Re: Re-Sending EMail?? 
In-Reply-To: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> 
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.3.91.950126082026.5530C-100000@bambix.icce.rug.nl>
References: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> 
Mime-Version: 1.0
Date: Thu, 26 Jan 1995 07:21:38 GMT

On Wed, 25 Jan 1995, Dan Mullen wrote:

> Question:
> What Pine command do I use to resend a previously sent message
> that has been returned due to Wrong Address or Server Error?
> 
> This has happened a couple ot times and had to retype the whole message 
> again. Suggestion Please!!
> 
> dmullen@gate.net

Make sure that you have the "bounce" command enabled (main menu -> setup ->
config). When your get your mail back, re-check the address. Then bounce the
message to the same address or if you know of an alternative, bounce it to the
alternative address.

--
Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
>From the Obscure Dictionary of Medical Terms:
Lymph: A special Fairy.



From owner-pine-info@cac.washington.edu  Fri Jan 27 20:45:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19730;
	Fri, 27 Jan 95 20:45:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13416;
	Fri, 27 Jan 95 20:43:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13410;
	Fri, 27 Jan 95 20:43:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY4qr-00038nC; Fri, 27 Jan 95 20:33 PST
To: pine-info@cac.washington.edu
From: robk@stack.urc.tue.nl (Rob Kouwenberg)
Subject: Re: Need to secure pine
Date: 26 Jan 1995 09:44:55 GMT
Message-Id: <3g7qun$efu@tuegate.tue.nl>
References: <3g1e2s$5sk@case.cyberspace.com> <3g4g5p$7ab@news.southern.edu>

AJDevoir (ajdevoir@southern.edu) wrote:
: Have you thought about just changing the file permissions on the .pinerc 
: file?  (chmod 700 .pinerc)  Maybe i am just reading what you are after wrong,
: but is it that people are just coming in and reconfiguring pine for you?

It's no use; the user can change this value ..

I also found the pine.conf.fixed location to be : /usr/local/lib
Description in the files in the ./pine3.91/doc directory.

'Till next time, best regards, Rob Kouwenberg
--
[ robk@stack.urc.tue.nl,Gr.Adolfstraat86,5616BX,Eindhoven,The Netherlands ]


From owner-pine-info@cac.washington.edu  Fri Jan 27 20:59:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19906;
	Fri, 27 Jan 95 20:59:05 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15699;
	Fri, 27 Jan 95 20:56:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15693;
	Fri, 27 Jan 95 20:56:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY510-00038nC; Fri, 27 Jan 95 20:44 PST
To: pine-info@cac.washington.edu
From: FLAVELL@crnvma.cern.ch (Alan J Flavell)
Subject: Re: Q. about HUJI VMS Pine 3.91 beta 3
Message-Id: <17332AE2DS86.FLAVELL@cernvm.cern.ch>
References: <1732D14368S86.FLAVELL@cernvm.cern.ch> <3g4t4v$op3@blackice.winternet.com>
Date: Thu, 26 Jan 1995 12:23:01 GMT

In article <3g4t4v$op3@blackice.winternet.com>
daud@winternet.com (David Denney) writes:
 
>: What makes it think I have a postponed mail?
>
>Add 'postponed-folder=""' in pine.conf (global) or .pinerc (sys$login)
>
>: Also, can someone explain just what it means under 1. in "Restrictions"?
>: It says "the user must not switch to another folder as long as NEWMAIL
>: has items".  Does something terrible happen?
>
>That is only applicable if you map INBOX to be NEWMAIL. DO NOT DO THIS.
>Nasty things will happen. Leave INBOX = INBOX, ignore it completely, and
>make a few extra keystrokes to open NEWMAIL instead.
 
Many thanks for your helpful reply.  In the meantime, I find that
there is a more serious (!) problem: it doesn't seem to understand
MIME encoded mail.  I think this is because the incoming mail gets
an additional set of headers added ahead of the RFC822 headers.
Presumably this is a result of the way we have MULTINET configured,
and it allows MAIL to handle both SMTP and DECNET mail transparently.
 
The same situation probably explains why it does not compose
REPLY addresses properly: it seems to be using the added
headers rather than the RFC822 headers, so (when replying to
incoming SMTP mail) we get a reply address like this:
 
   "SMTP%a.user@some.domain.edu"@our.own.domain.name
 
I think our existing MAIL users would be upset if we were to change
the format of incoming mail, if they lost the ability to reply to
incoming DECNET mail.  Is there anything we can do to live with
this situation, and still use PINE (so as to be able to use MIME)?
 
(And again the question, "is there a better place for discussing
this VMS version"?).
 
best regards


From owner-pine-info@cac.washington.edu  Fri Jan 27 21:28:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20467;
	Fri, 27 Jan 95 21:28:57 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13897;
	Fri, 27 Jan 95 21:25:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13891;
	Fri, 27 Jan 95 21:25:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY5T1-00038tC; Fri, 27 Jan 95 21:12 PST
To: pine-info@cac.washington.edu
From: tgpt_ltd@uhura.cc.rochester.edu (Thomas Guptill)
Subject: Re: Pine/VMS
Message-Id: <1995Jan27.032538.11696@galileo.cc.rochester.edu>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu> <1995Jan14.220520@cchs.su.edu.au> <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au> <ellis.791123917@gmi.edu>
Date: Fri, 27 Jan 95 03:25:38 GMT

In <ellis.791123917@gmi.edu> ellis@nova.gmi.edu (R. Stewart Ellis) writes:

> >Is there a known difficulty in connecting to lenin.cc.rochester.edu?

OK, folks.  I've managed to patch poor old Lenin back together & get
everything up & running with a temporary disk.  ftp should be working ok
now, but will be down briefly when I find a long-term replacement for the
second disk.  In the meantime, Pine/VMS is back in the original location.

	Tom
	(acting as archive@lenin.cc.rochester.edu)
-- 
| Tom Guptill            I don't speak for UCC from this account. |
| tgpt_ltd@UORDBV                                                 |
| Temporary LARVA-ED resident                                     |


From owner-pine-info@cac.washington.edu  Fri Jan 27 21:45:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20806;
	Fri, 27 Jan 95 21:45:46 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16280;
	Fri, 27 Jan 95 21:41:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16274;
	Fri, 27 Jan 95 21:40:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY5er-00038kC; Fri, 27 Jan 95 21:25 PST
To: pine-info@cac.washington.edu
From: gkindt@allserv.rug.ac.be (Geert Kindt)
Subject: Acknowledgement
Date: 27 Jan 1995 09:01:23 GMT
Message-Id: <3gacp3$c8r@infoserv.rug.ac.be>

 I have a question about Pine.
Is it possible to receive a message from the server of your recipient
when your e-mail message arrived (or has been read) at the server of your
recipient ? (perhaps customized-hdrs ????)


Thank you very much,



Geert Kindt, University Gent, Belgium, Europe.




From owner-pine-info@cac.washington.edu  Fri Jan 27 23:01:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21958;
	Fri, 27 Jan 95 23:01:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15104;
	Fri, 27 Jan 95 22:58:37 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15098;
	Fri, 27 Jan 95 22:58:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY6vU-00038qC; Fri, 27 Jan 95 22:46 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Pine/VMS
Date: 26 Jan 95 12:38:37 GMT
Message-Id: <ellis.791123917@gmi.edu>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu> <1995Jan14.220520@cchs.su.edu.au> <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au>

Alan Agnew <agnew@maize.qut.edu.au> writes:

 >In a previous posting it was stated that PINE 3.91  for VMS is available
 >from lenin.cc.rochester.edu.

 >I have been attempting to connect to lenin.cc.rochester.edu from Australia
 >for several days now, but have never suceeded.

 >A ping shows 100% packet loss.

 >A traceroute gets as far as taylor4-bbgw.utd.rochester.edu and then nothing.

 >Is there a known difficulty in connecting to lenin.cc.rochester.edu?

I just tried it with ncftp.

nova_ellis_~/> ncftp lenin.cc.rochester.edu

******************************
LENIN.CC.ROCHESTER.EDU IS DOWN
******************************

        Lenin's second hard disk (the one that contains "/usr") has failed. 
All non-critical network services (including ftp) have been suspended until
the drive can be replaced.  There is no ETA for repair completion.  We
apologize for any inconvenience this may cause.  Please contact
tgpt_ltd@cc.rochester.edu for further details.

        Tom Guptill
        archive@lenin
        acting as root@lenin
User anonymous access denied.
Login failed.


 >Does anyone else have this version of PINE on an anonymous FTP  server?


 >	Alan Agnew
 >	Network Services
 >	Computing Services
 >	Queensland University of Technology

 >	Phone: (07) 864 1703		E-Mail: A.Agnew@qut.edu.au
-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Fri Jan 27 23:01:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21979;
	Fri, 27 Jan 95 23:01:30 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17196;
	Fri, 27 Jan 95 22:58:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17190;
	Fri, 27 Jan 95 22:58:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY6y0-00038uC; Fri, 27 Jan 95 22:49 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: I renamed and made PICO an executable but still no luck
Date: 26 Jan 95 12:41:06 GMT
Message-Id: <ellis.791124066@gmi.edu>
References: <3g6sbn$fet@nic-nac.CSU.net>

mike@newport.lib.ca.us (Micheal Wojciechowski) writes:

 >As the subject header says I renamed pico-bin.hpux9 and made it an executable
 >but I get a message back that says "ksh: pico: cannot execute"  Does anyone have
 >any clue as to what I need to do.  Does it need to be compiled?

Did you 'chmod 755 pico'?

 >Thanks in advance.

 >Mike
-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Fri Jan 27 23:15:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22209;
	Fri, 27 Jan 95 23:15:54 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15312;
	Fri, 27 Jan 95 23:13:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15306;
	Fri, 27 Jan 95 23:13:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY7AF-00038qC; Fri, 27 Jan 95 23:01 PST
To: pine-info@cac.washington.edu
From: decello@cpp.msu.edu (Joseph P DeCello III)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 27 Jan 1995 22:14:35 GMT
Message-Id: <3gbr8b$1dc9@msunews.cl.msu.edu>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca>

ftp.qualcomm.com, look for qpopper, it works great with Eudora clients.


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joseph P. DeCello III             | Opinions expressed here are mine
Computer Assistant                | alone and do not reflect those of 
Michigan State University         | MSU and/or Campus Park and Planning.




From owner-pine-info@cac.washington.edu  Fri Jan 27 23:28:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22419;
	Fri, 27 Jan 95 23:28:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17516;
	Fri, 27 Jan 95 23:26:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17510;
	Fri, 27 Jan 95 23:26:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY7M7-00038qC; Fri, 27 Jan 95 23:13 PST
To: pine-info@cac.washington.edu
From: cs3mh3aw@maccs.dcss.McMaster.CA (Dyck        NH)
Subject: Filtering in Pine
Message-Id: <1995Jan27.091046.26224@mcshub.dcss.mcmaster.ca>
Date: Fri, 27 Jan 1995 09:10:46 GMT

Just wondering how to filter in Pine based on  the From: Header.


From owner-pine-info@cac.washington.edu  Sat Jan 28 00:02:32 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23181;
	Sat, 28 Jan 95 00:02:32 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15895;
	Fri, 27 Jan 95 23:59:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15889;
	Fri, 27 Jan 95 23:59:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY7tr-00038uC; Fri, 27 Jan 95 23:48 PST
To: pine-info@cac.washington.edu
From: hph@vki68.aar-vki.dk (Hans Peter)
Subject: Global Address Book (RO ??)
Date: 26 Jan 1995 09:41:37 GMT
Message-Id: <3g7qoh$iio@belfort.daimi.aau.dk>

I have a small problem:

Our global address book in pine 3.91 SCO-UNIX in:
/w2/bruger/pineaddr/globaddr

The problem is, that it is set to ReadOnly within pine for all users,
including root, althoug the permissions for the file is set to rw.

So how do I maintain this file?

best regards, Hans Peter
----------------------------------------------------------------
*  Hans Peter Hansen            |  VKI-Water Quality Institute *
*  E-mail: hph@aar-vki.dk       |  Science Park Aarhus         *
*  Phone: +45 86 20 20 00 /2124 |  10, Gustav Wiedsvej         *
*  Fax:   +45 86 19 75 11       |  DK 8000 Aarhus C, Denmark   *
----------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Sat Jan 28 01:44:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25591;
	Sat, 28 Jan 95 01:44:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19325;
	Sat, 28 Jan 95 01:41:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19319;
	Sat, 28 Jan 95 01:41:12 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rY9Sa-00038uC; Sat, 28 Jan 95 01:28 PST
To: pine-info@cac.washington.edu
From: mike@newport.lib.ca.us (Micheal Wojciechowski)
Subject: I need CISC version of PICO on HP-UX9
Date: 27 Jan 1995 23:40:18 GMT
Message-Id: <3gc092$4sd@nic-nac.CSU.net>



I figured out what the problem is.  I am running pico on a 300 series HP9000
which has a CISC processor in it.  I moved it over to a G30 which uses a RISC
processor and it works fine.  

The next question I have is, does anyone have it compiled on a CISC processor
where I might be able to get a hold of it?  It would be greatly appreciated.

Thanks in advance.

Mike


From owner-pine-info@cac.washington.edu  Sat Jan 28 02:23:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26299;
	Sat, 28 Jan 95 02:23:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17813;
	Sat, 28 Jan 95 02:20:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17807;
	Sat, 28 Jan 95 02:20:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYA3q-000390C; Sat, 28 Jan 95 02:07 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Re-Sending EMail??
Date: Thu, 26 Jan 1995 13:47:58 +0000
Message-Id: <Pine.SUN.3.91.950126134613.26920X-100000@grus.cus.cam.ac.uk>
References: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> 

On Wed, 25 Jan 1995, Dan Mullen wrote:

> Question:
> What Pine command do I use to resend a previously sent message
> that has been returned due to Wrong Address or Server Error?

You save the Fcc copy to your postponed-msgs folder (or whatever name you 
have called the folder where postponed messages go), then type C (ompose) 
and respond Yes (or select the message if you have more than one 
postponed), edit it totaste, and away you go.

> 
> This has happened a couple ot times and had to retype the whole message 
> again. Suggestion Please!!

The above avoids retyping (and I use it frequently!)

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Sat Jan 28 03:03:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26953;
	Sat, 28 Jan 95 03:03:29 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20118;
	Sat, 28 Jan 95 03:00:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20112;
	Sat, 28 Jan 95 03:00:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYAiG-00038SC; Sat, 28 Jan 95 02:49 PST
To: pine-info@cac.washington.edu
From: ccurtis@ee.fit.edu (Christopher W. Curtis)
Subject: Re: Non-standard INBOX locations and pine
Message-Id: <ccurtis.791079010@ee.fit.edu>
References: <vzvzD2w73C.1M9@netcom.com>
Date: Thu, 26 Jan 1995 00:10:10 GMT

In <vzvzD2w73C.1M9@netcom.com> vzvz@netcom.com (Philip Zeyliger) writes:

>Some users are reporting that pine doesn't see their INBOX'es.
>The inboxes are located at $HOME/.mailbox/inbox.

We have the same problem here, but it only materializes when using PINE.
Elm sees the real INBOX without any troubles whatsoever, I guess further
showing that "Pine Is Not Elm".  It is annoyong when this happens and we do
not wish to dedicaate the resources to rewriting everyone's login script to
alleviate the problem.  Perhaps the PINE developers should look how Elm
handles the situation and copy it; or at least parse the /etc/alias file to
find the REAL inbox.  Just a suggestion...
--
T |        Christopher Curtis       |  There are two rules to follow   | O
E |   Sun Lab System Administrator  |  to ensure success in life:      | S
A | Florida Institute of Technology |  Rule 1:  Don't tell people      | /
M |       Melbourne, Florida       N|N          everything you know.   | 2


From owner-pine-info@cac.washington.edu  Sat Jan 28 03:44:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28005;
	Sat, 28 Jan 95 03:44:47 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20687;
	Sat, 28 Jan 95 03:41:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20681;
	Sat, 28 Jan 95 03:41:32 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYBJX-00038XC; Sat, 28 Jan 95 03:27 PST
To: pine-info@cac.washington.edu
From: Dan <df@hopper.unh.edu>
Subject: Where Joe?
Date: Wed, 25 Jan 1995 17:44:47 -0500
Message-Id: <Pine.OSF.3.91a.950125174230.18110F-100000@hopper.unh.edu>
References: <3fkosh$ouc@j51.com> <3fuu8e$7de@news.primenet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fuu8e$7de@news.primenet.com> 


Okay. I got Joe, I installed it (I think), and if I load Pine from the 
joe directory I can actually use it. (I am trying to emulate WordStar so 
I don't use the wrong commands in word processing and email letter 
writing, as now happens.)

I don't understand. Should I put joe in my main directory? Or can I 
somehow tell Pine where to find joe?

                 - Dan    <dan.ford@unh.edu>



From owner-pine-info@cac.washington.edu  Sat Jan 28 03:49:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28083;
	Sat, 28 Jan 95 03:49:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18741;
	Sat, 28 Jan 95 03:35:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18735;
	Sat, 28 Jan 95 03:35:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYBDY-00038QC; Sat, 28 Jan 95 03:21 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Pine Frequently Asked Questions (FAQ)
Date: Fri, 20 Jan 1995 10:42:51 -0800
Message-Id: <Pine.ULT.3.92.950120104128.7477A-820000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1726109301-790627371=:7477"
Content-Id: <Pine.ULT.3.92.950120104128.7477B@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1726109301-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477C@shiva1.cac.washington.edu>
Content-Description: Current Version of this Document

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Current Version of this Document

The most up-to-date version of this FAQ can be found at either of these
places: 

   http://www.cac.washington.edu/pine/faq/
   ftp://ftp.cac.washington.edu/pine/docs/faq

Last updated: 940106
Current release: Pine 3.91, Pico 2.5

 Pine and Pico are registered trademarks of the University of Washington.
 Copyright 1995 by the University of Washington.

--0-1726109301-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477D@shiva1.cac.washington.edu>
Content-Description: Contents

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Contents

                        PINE FREQUENTLY ASKED QUESTIONS
                                       
   The following questions have been compiled from questions asked on the
   comp.mail.pine newsgroup and the pine-info and pine-bugs mailing lists.
   
General

     * What is Pine? 
     * What is MIME? 
     * What is IMAP? 
     * How can I get a copy of Pine? 
     * What documentation is available?
     * What mailing lists and newsgroups are there dealing with Pine? 
     * What are all these funny names in your examples? 
     * How many sites use Pine? 
     * Can we use Pine source code in commercial products?

Basic usage problems

     * Why doesn't Pine's cancel/postpone/etc key work?
     * How do I keep all of the names from showing up at the top of the
       message?
     * How do I use Ispell with Pine and Pico?
     * How can I have a signature automatically appended to my mail
       messages? 
     * How can I filter messages into different incoming folders? 
     * How do I define my own headers like Reply-To and Organization?
     * Can I use Pine non-interactively, e.g., in a shell script?
     * Can I execute Pine from a shell script so I can use my
       addressbook? 
     * xbiff lets me know about new mail, but pine doesn't know about it.
     * How can I read a ROT13 encoded message? 
     * Can I eliminate the @host.domain from local addresses?

Printing

     * Why doesn't printing work?
     * What PC comm software works with the "Print to ANSI" print option?
     * What Mac comm software works with the "Print to ANSI" print option? 
     * What Amiga comm software works with the "Print to ANSI" print option? 

Newsreading and posting

     * How do I read News with Pine? 
     * Can I post news with Pine? 

Attachments

     * Why does Pine encode text attachments?
     * How can someone without Pine decipher an attachment? 
     * How can I send a text file without it being encoded?
     * Why does Pine use Base64 instead of UUENCODE?
     * How do I convert a Sun Mailtool attachment to MIME format? 
       
Folder Problems

     * If I postpone a Reply, Pine never marks it as answered.
     * "Folder Format Invalidated (consult an expert), aborted" 
     * What is folder locking and how does it work? 
     * What happens when two Pine sessions access the same mailbox
       simultaneously? 
     * Why did I get the message "locked, override in XXX sec"? 
     * Why doesn't Pine recognize Content-Length header field?

Addressbook Usage and Conversions
    
     * How do I "paste" an address from the addressbook into the text of
       a message? 
     * How do I convert Berkeley Mail aliases to Pine Addressbook? 
     * How do I convert Elm aliases to Pine Addressbook? 
       
Installation and Configuration

     * Can Kerberos or AFS authentication be used with Pine? 
     * Can PC-Pine be used with a POP server? 
     * What is a Tenex mailbox and why should I use it? 
     * Where does Unix Pine look for configuration information? 
     * Where does PC-Pine look for configuration information? 
     * How do I make Pine work with my older terminal? 
     * How do I configure Pine to not leave mail in /usr/spool/mail? 
       
Platform Specific

     * To what platforms has Pine been ported? 
     * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I
       try to open a folder. 
     * I cannot compile under SCO unix, why not?

Bug Reports

     * Why should I use the builtin Bug Report command?
     * Why does the bug report screen come up when I didn't ask for it?
     * I have found a bug in Pine 3.05. Could you please fix it? 

Development Info

     * What are the current versions of Pine and related software? 
     * What is new in this version of Pine? 
     * When is the next release of Pine (tentatively) scheduled? 
     * What new features will the next release of Pine include? 
       
   
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1635971033-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477E@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477F@shiva1.cac.washington.edu>
Content-Description: What is Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is Pine?

Pine(tm) --a Program for Internet News & Email-- is a tool for reading,
sending, and managing electronic messages.  It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of power users as well.  Pine uses Internet message protocols
(e.g. RFC822, SMTP, MIME, IMAP, and NNTP) and runs on Unix, MS-DOS, and
MS Windows. 
  
The guiding principles for Pine's user-interface were:  careful limitation
of features, one-character mnemonic commands, always-present command
menus, immediate user feedback, and high tolerance for user mistakes.  It
is intended that Pine can be learned by exploration rather than reading
manuals.  It has the ability to perform full screen editing of messages,
include and extract attachments (such as Word or Excel files), and other
advanced message system features. 

Pine uses IMAP for accessing message folders on remote computers and MIME
for sending multimedia or other binary files as attachments to normal
messages. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477G@shiva1.cac.washington.edu>
Content-Description: What is MIME?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is MIME?

MIME (RFC1521) stands for "Multipurpose Internet Mail Extensions". It is
an Internet standard which allows transfer of binary files
(word-processing documents, spreadsheets, images, sounds, etc) between any
compliant mailers. You can get technical information about MIME from the
RFC. Ongoing discussion on MIME takes place in the newsgroup
comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that
is posted regularly to comp.mail.mime, comp.answers and news.answers. 
If you have a Web browser you can access it through:

http://www.cis.ohio-state.edu/hypertext/faq/bngusenet/comp/mail/mime/top.html

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477H@shiva1.cac.washington.edu>
Content-Description: What is IMAP?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is IMAP?

IMAP stands for "Internet Message Access Protocol". An IMAP client program
on any platform at any location on the Internet can access email folders
on an IMAP server. While the messages appear to be local, they reside on
the server until the client explicitly moves or deletes them.  The IMAP
protocol is a functional (but incompatible) superset of POP. A principal
advantage of IMAP over POP is that it permits using more than one computer
to access your mail.  Using multiple computers with POP typically results
in your mail ending up scattered across all of those computers. Another
key advantage is IMAP's ability to selectively access parts of messages,
e.g. you don't have to wait for a 2MB audio attachment to be retrieved
until you specifically ask for it.  This is a big win over low-speed (e.g.
dialup) connections.  For a detailed comparison of IMAP and POP, see the
paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." 
It is available from: 

	ftp://ftp.cac.washington.edu/mail/imap.vs.pop
  
IMAP is what allows Pine (or any other IMAP client) to access email on a
remote mail server, usually one that is shared (central or departmental). 
The current IMAP4 Proposed Standard is described in RFC1730.  Additional
information is included in RFC1731, RFC1732, and RFC1733. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477I@shiva1.cac.washington.edu>
Content-Description: How can I get a copy of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I get a copy of Pine?

Pine is available via anonymous ftp from the pine directory of
ftp.cac.washington.edu. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477J@shiva1.cac.washington.edu>
Content-Description: What documentation is available?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What documentation is available?

The Pine program itself includes extensive online help.  Additional
documentation may be found via anonymous FTP or via World-Wide-Web at the
following locations: 

  ftp://ftp.cac.washington.edu/pine/docs
  http://www.cac.washington.edu/pine

The following contributed documentation is also available:

  http://www.math.utah.edu/~calfeld/creations/ca_pine_guide.html
  http://www.math.utah.edu/~calfeld/creations/PineIntroduction
  http://www.math.utah.edu/~calfeld/creations/PineIntermediate

If you have documentation that you would like to share, please mail
pine@cac.washington.edu a pointer to them and we'll include it here. 
   
--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477K@shiva1.cac.washington.edu>
Content-Description: What mailing lists and newsgroups are there dealing with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What mailing lists and newsgroups are there dealing with Pine?

The "comp.mail.pine" newsgroup is devoted to Pine.  It is bi-directionally
gatewayed to the "pine-info" mailing list described below. 

   The following mailing lists deal with Pine and related topics: 
   
   Pine-Info@cac.washington.edu 
          Pine-Info is a mailing list for the email program Pine. The
          mailing list includes discussion of Pine features, bugs,
          tricks, etc. Often technical and installation questions appear
          on the list. New releases, fixes and version of Pine are
          announced on the pine-info mailing list.  For official 
          announcements only, you may wish to see pine-announce instead 
          of this list.
          
          To subscribe to pine-info, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-info
 	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-info@cac.washington.edu. 
          
   Pine-Announce@cac.washington.edu 
          Pine-Announce is a announcement list for the email program
          Pine. When new Pine products are released and old ones updated,
          a message goes out to this group describing the development. It
          is a very low volume list and includes no discussion
          whatsoever.
          
          NOTE: All messages to this list are automatically forwarded to
          pine-info, so it is not necessary to subscribe to both lists!
          
          To subscribe to pine-announce, send a message to
          majordomo@cac.washington.edu with 
                  subscribe pine-announce
	  in the body of the message.
          
          Owners of this mailing list can be contacted at
          owner-pine-announce@cac.washington.edu.
          
   IMAP@CAC.Washington.EDU 
          This is the official mailing list for the IETF IMAP working
          group and other interested parties. Discussion of the evolving
          IMAP standard and related issues is conducted on this list.
          
          To subscribe to IMAP, send a message to
          imap-request@cac.washington.edu.
          
   C-Client@CAC.Washington.EDU 
          This list is for discussion of the C-Client library which is
          used by Pine and various other mail and IMAP clients and
          servers.
          
          To subscribe to C-Client, send any message to
          c-client-request@cac.washington.edu.

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477L@shiva1.cac.washington.edu>
Content-Description: How many sites use Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How many sites use Pine?

Based on the number of people getting copies of Pine and its
documentation, we know for sure that Pine is used at over 12,000 sites in
60 different countries.  We do not have any way to count the exact number
of sites using Pine or the total number of users, but we estimate that 
well over one million people use Pine right now (12/94).  People are still
jumping on the Pine bandwagon -- about 4,000 new users each day -- so any
guess about the number of people who use Pine today will surely be too
small tomorrow. 

--0-1635971033-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477M@shiva1.cac.washington.edu>
Content-Description: Can we use Pine source code in commercial products?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can we use Pine source code in commercial products?


Pine and C-client source code is copyright by the University of
Washington, however it may be used without fee to the University of
Washington, even for commercial purposes, subject to the terms of the
copyright notice in the code.  

If you want to use Pine code in commercial products, you must retain the
indication of UW trademark and copyright and we ask that you also
"explicitly and conspiciously" indicate that there is no business
relationship of any kind between you and the University of Washington. 
Note that the copyright restrictions may not be the same in all versions
of the code, but the general information above pertains to all versions of
Pine up to and including the current 3.91 release. 

A related issue concerns use of the name Pine...

 "Pine and Pico are registered trademarks of the University of Washington.
  No commercial use of these trademarks may be made without prior
  written permission of the University of Washington."

If you have any doubts about what you need to do to use Pine commercially,
write to the Pine Development Team <pine@cac.washington.edu> and ask. 

--0-1635971033-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1325855154-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477N@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477O@shiva1.cac.washington.edu>
Content-Description: Why doesn't Pine's cancel/postpone/etc key work?

On some systems, certain control characters are intercepted before they
get to Pine.  This is usually a problem with the communication software
running on a Mac or PC, but terminal servers sometimes intercept certain
control characters as well.

Control-C and Control-O seem to be two of the most common problem cases.
As a work-around, you can press the ESCAPE key twice followed by the
desired key.  For example, if Control-O (^O) does not work on your system,
try typing "ESC ESC O".  This trick will work for any control character.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477P@shiva1.cac.washington.edu>
Content-Description: How do I send a message to lots people without showing all the names?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I send a message to lots people without showing all the names?

Put addresses and/or list from your address book in the Bcc: (blind carbon
copy) header field. You will see all the names and addresses as you
compose the message, but they are erased before arriving in other people's
INBOXes. The Bcc: header is not displayed automatically in the default
Pine configuration, so you may need to use the rich headers command
(Ctrl-R) while the cursor is in the header to expose it. 
   
--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477Q@shiva1.cac.washington.edu>
Content-Description: How do I use Ispell with Pine and Pico?

From: Mike Ramey <mramey@u.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How do I use Ispell with Pine and Pico?

If you use ispell and have an ispell custom dictionary (usually ispell.words
or .ispell_words in your home directory, which contains a list of words, one 
word to a line) then it is nice to also use ispell for spell checking your 
outgoing mail messages.  There are two methods for setting this up.  

METHOD 1
========
If you always use Pine's default composer, Pico, then you can use ispell
as your "alternate editor."  In your .pinerc set enable-alternate-editor
and set the editor variable like this:

   editor=/usr/local/bin/ispell

(See step 1 of Method 2 below for instruction for finding the full path
to ispell on your machine.)

Then, when you are composing a message you can type ^_ to run ispell on your 
message and display the output in Pine's viewer.  In the viewer you can use
ispell's usual commands. While in ispell you can type ? for help on  ipell's 
commands.  One useful command is ``I'' which inserts the current word in your 
custom dictionary.


METHOD 2
========
If you use an alternate editor, such as vi or emacs, then you need to fool 
Pine into thinking that ispell is spell.  Here's how to set this up:

1] Determine what directory ispell is in by using one of these commands:

     which ispell
     type ispell
     whereis ispell
     where ispell

2] In your bin directory, e.g., $HOME/bin, link spell to ispell with:

     ln -s /usr/local/bin/ispell $HOME/bin/spell

   Replace ``/usr/local/bin'' with ispell's path (see #1).


3] If you use the csh or tcsh set the SPELL environment variable by
   putting a line like this in your .cshrc:

     setenv SPELL "$HOME/bin/spell"

   If you use the Bourne shell set the SPELL environment variable by
   putting a line like this in your .profile:

     SPELL="$HOME/bin/spell"
     export SPELL

4] In your home directory create a file called ispell.words that
   contains your private dictionary of words that should pass the
   spell check.  This will probably include your name, email address, etc.

5] Logout and log back in to make sure that your new settings are in
   place.

6] Test that this is set up correctly by using Pine to compose a message
   and include words, like your name,  that are in your custom dictionary.  
   Spellcheck the message with ^T.  If your name passes the spellcheck (and
   your name isn't in regular dictionaries) then it is set up correctly.

With Method 2 you cannot use many of ispell's features, for example, ``I'',
which inserts a word in your dictionary doesn't work.


--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477R@shiva1.cac.washington.edu>
Content-Description: How can I have a signature automatically appended to my mail messages?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I have a signature automatically appended to my mail messages?


Using your favorite text editor (e.g. Pico), create a file in your home
directory called .signature containing the text you want appended to each
message.
   
PC-Pine users should put their signatures in the file \PINE\PINE.SIG. 
   
For more details see Nancy McGough's Signature and Finger FAQ.  The 
hypertext version is at:

http://www.cis.ohio-state.edu/hypertext/faq/usenet/signature_finger_faq/faq.html

The plain text version is at:

ftp://ftp.halcyon.com/pub/ii/internet/signature_finger_faq

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477S@shiva1.cac.washington.edu>
Content-Description: How can I filter messages into different incoming folders?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>, Nancy McGough <nancym@ii.com>
Subject: How can I filter messages into different incoming folders?

                                       

Pine does not do delivery filtering. That function is done by other
programs, such as "procmail" or "filter" or "deliver" or "mailagent." 
   
Once you have set-up your delivery filtering, e.g. via the "procmail"
program, then you will have new mail arriving in several different
mailboxes/folders, in addition to your INBOX. 
   
So then the question becomes, how do you access those new "incoming
message" folders that your favorite delivery filter program has created?

One solution is to just access them the same way you access your other
mail folders.  If they are in your default folder directory (usually
$HOME/mail) then just type L to list your folders and select the folder
you'd like to view.  If they are in a different directory, for example
$HOME/mail/IN, add that directory to your folder-collections by putting
this into your .pinerc: 

folder-collections=mail/[],
        mail/IN/[],

And then when you list your folders by typing L the mail/IN directory will
be in your list. 

Another solution is to use Pine's incoming-folders variable.  With this
method you can use the Tab key to tab through new messages in all your
incoming folders.  When you are at the last new message in one incoming
folder pressing the Tab key will move you to the next incoming folder with
a new message. 

Here is part of a sample .pinerc for setting up incoming folders: 
 
incoming-folders=Art151           {warhol.art.nowhere.edu}IN/art151,
                 Art-L            {warhol.art.nowhere.edu}IN/Art-L,
                 Old-Student-Acct {fozzie.elsewhere.edu}INBOX

In this case, the pinerc entries presume that your delivery filtering
program has been configured to put mail relating to the Art151 class into
the folder "IN/art151" and mail relating to the Art-L mailing list into
"IN/Art-L". 
   
>From the Folders List screen, you can then easily access those folders.
Eventually we will have a way to indicate which of these may have new mail
waiting for you, so that you don't forget that you have more than one
place to look for new mail. 
   
For a more detailed treatment of filtering, see the Filtering Mail FAQ and
the Procmail FAQ.  The hypertext version of these are available at: 

http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/procmail-faq/faq.html

The plain text versions are available at:

ftp://ftp.halcyon.com/pub/ii/internet/filtering_mail_faq
ftp://ftp.halcyon.com/pub/ii/internet/procmail_faq

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477T@shiva1.cac.washington.edu>
Content-Description: How do I define my own headers like Reply-To and Organization?

From: Nancy McGough <nancym@ii.com>
Subject: How do I define my own headers like Reply-To and Organization?

                                       

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers by 
typing h.  If h does not work you need to go to your configuration menu and 
set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the cursor
in the header region and typing ^R (view rich headers).

Customized headers are not available in Pine 3.89 and earlier.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477U@shiva1.cac.washington.edu>
Content-Description: Can I use Pine non-interactively, e.g., in a shell script?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I use Pine non-interactively, e.g., in a shell script?

This is not currently possible.  If it were possible you could use Pine,
and your Pine addressbook, to mail people from within a shell script, at 
the end of a pipeline, etc.

   
--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477V@shiva1.cac.washington.edu>
Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it.

                                       

There are currently two ways to force a new mail check. 
     * Press `Ctrl-L' (Refresh Display). 
     * At the last message in a folder, press 'N' 4-5 times. 
       
   
   
--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477W@shiva1.cac.washington.edu>
Content-Description: How can I read a ROT13 encoded message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I read a ROT13 encoded message?

                                       

When viewing the message, use the '|' (Pipe) command and give it the
following: 

        tr '[A-Za-z]' '[N-ZA-Mn-za-m]'

You could also write a script, maybe called unrot, that does this and then
pipe the message to the script. 

In order for the pipe command to work you need to be using Pine 3.90 or 
higher and have the enable-unix-pipe-cmd variable set.

--0-1325855154-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477X@shiva1.cac.washington.edu>
Content-Description: Can I eliminate the @host.domain from local addresses?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I eliminate the @host.domain from local addresses?

This is not a new idea.  It's a very old idea, in fact, and just about
everyone who has ever dealt with email has had it at one time or another. 
Regretably, it has come to be recognized as a bad idea.  Here's why: 

An email address without a host name is not syntactically valid according
to RFC822.  Now, it is true that RFC822 only specifies what must be done
in messages which are transmitted over the network, and that strictly
local messages are not under RFC822's dictates. 

This means that there are two formats of email, one that conforms to
RFC822 and one that does not.  Careful efforts must be made to ensure that
the non-conforming mail format never escapes the local system onto the
network. Twenty years' of experience has shown that it is impossible to
guarantee that the non-conforming format does not escape into the network,
even in the face of traps to catch such messages on their way out and
convert them to RFC822 conforming format.  Indeed, such traps have often
contributed additional problems on their own. 

The non-conforming format is ambiguous as to what host is intended.
Although the off-the-cuff solution (and the one that everyone implements)
is ``use the local host'', numerous examples have occurred in which this
leads to wrong behavior.  For example, it may be the ``local mail center''
instead of the ``local machine which is a single-user workstation''.  Or,
if a one of the non-conforming messages escaped on to the network, it's
some remote system and we have no idea at all what system that may be! 
There's no way for the mail reader to tell; a human may infer from context
but often does so by using information that is not available to the
program. 

The Pine team has spent long (and at times heated) meetings reviewing this
issue, before coming to the conclusion (as other email groups have
independently done) that it's a no-win situation.  The policy of the email
development community for 15 years (since the RFC733 discussions) has been
to exterminate the non-conforming format by not implementing it in modern
mail tools. 

It may be feasible to implement a feature in a future version of Pine that
would suppress the display of the local host name in email addresses. That
is, the host name would still be in the file on disk, but would not show
up on the screen.  We'll consider it, but we have a large list of very
high priority tasks which must be done first. 
 
--0-1325855154-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1804407223-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477Y@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477Z@shiva1.cac.washington.edu>
Content-Description: Why doesn't "attached-to-ansi" printing work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject:  Why doesn't "attached-to-ansi" printing work?

So-called "attached-to-ansi" printing relies on the communication software
you are using to interpret certain special characater sequences that tell
it to divert the incoming stream of characters to your printer, and then
back to your screen.  Perhaps 99% of "pine printing problems" are either
due to PC or Mac communications software that doesn't understand ANSI
escape sequences for printing, *or* (in the dialin case) softare flow-
control problems. 

We didn't understand how big a problem software flow control was 
until 3.90 came out... we changed pine to intercept flow control 
characters so that users would not see Pine "wedge" mysteriously if a 
mis-type or noise generated a control-S, but that did bad things when 
printers, modems, or comm software was depending on s/w flow control.

So in 3.91 we added the "preserve-start-stop-characters" feature, so that
Pine could be configured to respect s/w flow control characters (if the
operating system did) for those folks who needed them.  Enabling this feature
should make Pine 3.91 behave the same way as earlier versions. 

Then we discovered that some operating systems don't enable software flow
control by default.  So in 3.92, the "preserve-start-stop-characters" 
feature will do more than simply "not ignoring" them, it will try to force
the OS to pay attention to them.

So here's the sequence of things to try if you have pine printing 
problems:

 1. CHECK FOR SOFTWARE FLOW-CONTROL PROBLEMS:
    A. Try enabling "preserve-start-stop-characters"  <- requires 3.91
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global 
       .login script, or as a worst case, wrap pine in a script that does 
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS 
       will not be needed in 3.92).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. CHECK YOUR COMM SOFTWARE FOR ANSI PRINTING CAPABILITY
    A. After ruling out s/w flow control problems, if printing still 
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.  
    B. The "ansiprt" utility included in the pine distribution can also 
       be used for testing.  It simply sends the specified text file to 
       user's terminal device, bracketed with the ANSI escape sequences 
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. POSSIBLE OTHER PRINTING PROBLEMS
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using 
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example, 
       whether or not the printer needs a trailing formfeed to eject the 
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print 
       command option and "ansiprt".


--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477a@shiva1.cac.washington.edu>
Content-Description: What PC comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What PC comm software works with the "Print to ANSI" print option?

The attached-to-ansi option works on most PC communication packages. In
particular, Kermit, NCSA Telnet, and WinQVT have been tested. 
   
Brent Blumenstein <brentb@orca.fhcrc.org> reports "It works in under OS/2
using IBM's TCP/IP for OS/2 telnet capabilities (provided you have updated
to the latest corrective service diskettes - readily available). I do this
using both a token ring network connection and SLIP from home."
   
Ryan <draziw@netcom.com> reports "Works great with QmodemPro for DOS."
   
Ben Cacace <benc@pipeline.com> reports "I'm using ProComm Plus for Windows
ver 1.02: I can print E-Mail if it is *not* a large memo (memos of 48K or
larger give me a ProComm error message)."
   
Nancy McGough <nancym@ii.com> reports "It works with Delrina's WinComm. 

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

IMPORTANT NOTE
==============
If you have a postscript printer and you are printing from a MS Windows 
Comm program you need to use a non-postscript printer driver.

   
--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477b@shiva1.cac.washington.edu>
Content-Description: What Mac comm software works with the "Print to ANSI" print option?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What Mac comm software works with the "Print to ANSI" print option?

The UW modified versions of Kermit and NCSA Telnet are known to work with
the attached-to-ansi print option. Versaterm Pro is also reported to work. 
   
Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 
   
--0-1804407223-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477c@shiva1.cac.washington.edu>
Content-Description: What Amiga comm software works with the "Print to ANSI" print option?

From: David Miller <dlm@cac.washington.edu>
Subject: What Amiga comm software works with the "Print to ANSI" print option?

David Miller <dlm@cac.washington.edu> reports "Term 3.2 starts printing,
but misses the sequence to stop printing.  Term 4.1 printing is garbled."

Other packages will be listed as reports come in.  Please send reports to
pine@cac.washington.edu. 

--0-1804407223-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-21832344-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477d@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-21832344-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477e@shiva1.cac.washington.edu>
Content-Description: How do I read News with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I read News with Pine?


Beginning with version 3.91, it is usually sufficient to set the
nntp-server variable, via the Setup/Config menu. This will automatically 
define a default news-collection.  In case the default is not appropriate 
for your site, the following details may help...

Three ways to access news via Pine: 

    1. Via NNTP. Your .newsrc file must be on the machine where Pine is
       running. Assuming news is stored on the machine news.nowhere.edu,
       a typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu/nntp}[*]
   
       Note that if the nntp-server variable is set, your
       news-collections will default to NNTP access from that same server.
       

    2. Via IMAP. Your .newsrc file must be on the machine where news is
       stored. Assuming news is stored on the machine news.nowhere.edu, a
       typical .pinerc entry would be: 
       
           news-collections = News *{news.nowhere.edu}[*]


    3. Local News. If news is stored on the same machine you run Pine on,
       you can specify: 
       
           news-collections = News *[*]


The advantage of IMAP newsreading is that the same .newsrc can be used for
both Unix Pine and PC-Pine. The disadvantage is that you must have an
account on the machine that stores the news and runs the NNTP server. 

--0-21832344-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477f@shiva1.cac.washington.edu>
Content-Description: Can I post news with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can I post news with Pine?

                                       

Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90
and later you can enter a list of newsgroups on the Newsgrps: header to
post a message.  If the Newsgrps: header is not displayed when you are
composing you can view it by putting your cursor in the header and typing
^R to view rich headers.
   
--0-21832344-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-507512823-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477g@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477h@shiva1.cac.washington.edu>
Content-Description: Why does Pine encode text attachments?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine encode text attachments?


Pine uses MIME's Base64 encoding for *all* attachments, including text, in
order to assure that they are not modified in transit. The goal is make
sure that sending file attachments in Pine is as dependable as using FTP.

Although it may seem like encoding is unnecessary for files that are
plain text, certain email gateway, trasport, and delivery agents pose
a threat to the integrity of even text files (much less binary files).
For example, long lines may be wrapped, trailing spaces deleted, tabs
turned into spaces, lines beginning with "From " modified, etc.
Pmay there are actually several potential sources of corruption

--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477i@shiva1.cac.washington.edu>
Content-Description: How can someone without a MIME-aware mail program decipher an attachment?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can someone without Pine decipher an attachment?
                                       
   
Pine uses the MIME Internet standard for attaching files to email messages.
Any MIME-capable mailer should be able to understand Pine's attachments.

If you use Pine's attachment feature, your recipient needs to have either
a MIME-capable mail reader or software that can decode MIME. Fortunately,
these are not hard to find. The major proprietary mail vendors have
committed to MIME support, but some of their upgraded products are some
months away.  One freely-available program which can decipher a MIME
attachment is munpack from Carnegie Mellon. It is available at: 
   ftp://ftp.andrew.cmu.edu//pub/mpack
   
--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477j@shiva1.cac.washington.edu>
Content-Description: How can I send a text file without it being encoded?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How can I send a text file without it being encoded?


This is easily done by using Pine's "file inclusion" key (Control-R).
Instead of entering the file name on the Attchmnt header line, move
the cursor to the bottom of your messaage, and press Control-R, then
enter the name of the text file.  It will be included at the end of 
your message without any encoding (unless the file contains 8bit or
binary characters, in which case the entire message becomes subject
to MIME encoding rules.)

--0-507512823-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477k@shiva1.cac.washington.edu>
Content-Description: Why does Pine use Base64 instead of UUENCODE?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does Pine use Base64 instead of UUENCODE?


Pine uses the Internet MIME (Multipurpose Internet Mail Extensions)
standard for all attachments.  MIME uses "Base64" encoding rather than
uuencode, because uuencode uses characters that are transformed by some
email gateways, and there are also several incompatible versions of
uuencode.  However, if needed, you can certainly uuencode a file outside
of Pine, then use the Composer's Ctrl-R (file inclusion) command to insert
the uuencoded file into the message. 
   
--0-507512823-790627371=:7477
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1964980869-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477l@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1964980869-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477m@shiva1.cac.washington.edu>
Content-Description: How do I convert a Sun Mailtool attachment to MIME format?

From: Keith Moore <moore@cs.utk.edu>
Subject: How do I convert a Sun Mailtool attachment to MIME format?
                                       

A perl script (and conversion to C of same) that converts OpenWindows mail
to MIME. Body parts currently supported are: text, gif, Sun rasterfile
(converted to image/gif), postscript, and audio. Other types default to
application/octet-stream. It's easy to extend the set of types supported
and to add conversions, if necessary. 
   
The script requires uuencode, uudecode, zcat (aka uncompress), and the
"convert" program from ImageMagick. If you don't have ImageMagick you can
probably substitute the pbm stuff with little fuss. 

If you are reading this with a MIME browser, the the script and program
should be included in the next two attachments. 

--0-1964980869-790627371=:7477
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="sun-to-mime.perl"; SITE="cs.utk.edu"; ACCESS-TYPE=ANON-FTP; DIRECTORY="pub/MIME"; MODE=ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477n@shiva1.cac.washington.edu>

--0-1964980869-790627371=:7477
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="sun-to-mime.c"; SITE="cs.utk.edu"; ACCESS-TYPE=ANON-FTP; DIRECTORY="pub/MIME"; MODE=ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477o@shiva1.cac.washington.edu>

--0-1964980869-790627371=:7477--
--0-507512823-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-1178456012-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477p@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477q@shiva1.cac.washington.edu>
Content-Description: If I postpone a Reply, Pine never marks it as answered.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: If I postpone a Reply, Pine never marks it as answered.



This is a known limitation of the current release of Pine. When you
postpone a composition, Pine does not have any way to keep track of which
message was being replied to (or that it was a reply at all). This
limitation will be removed in a future release. 
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477r@shiva1.cac.washington.edu>
Content-Description: "Folder Format Invalidated (consult an expert), aborted"

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: "Folder Format Invalidated (consult an expert), aborted"

                                       

The message "Folder Format Invalidated (consult an expert), aborted" means
that Pine was reading your mail folder, and at the point in which it
expected a start-of-message header line, it found something else. 
   
The ``format invalidated'' condition can happen in one of three ways: 
    1. bad data exists at the beginning of the folder. 
    2. data was appended to the folder after Pine initially read it, and
       the new data did not begin with a start-of-message-header. 
    3. the folder was modified without Pine being aware of it. 
       
All three problems are generally caused by software external to Pine. 
   
Condition (1) can be determined by whether or not the problem repeats
itself after restarting Pine. If restarting Pine does not make the problem
go away, then you need to look at the actual file for the folder and see
what is wrong with the very first line. In particular, make sure that
there are no blank lines at the beginning of the file and that the first
character of the folder file is a capital ``F'' , the second an ``r'', the
third an ``o'', etc.  In the case of an INBOX, you may want to rename the
folder so that new mail can be delivered while repairs on the corrupt
folder are being done. 
   
Condition (2) may be caused by a mail delivery process (e.g. /bin/mail)
which writes some characters other than ``From '' at the beginning of the
new data. 
   
Condition (3) is caused by another program manipulating the mail folder
without following the normal folder locking protocols.  This is a general
problem on UNIX. 
   
Conditions (2) and (3) have also been known to occur when accessing
folders via NFS, if the information returned by the stat() and read()
system calls do not correspond with each other as a result of NFS
attribute caching. 
   
Restarting Pine on that folder always clears conditions (2) and (3). If
the problem is chronic, it may be worth an investigation to determine its
cause. Usually, it is due to the misbehavior of some external software.
The reason why Pine gives up with conditions (2) and (3) is that it does
not want to risk damaging user data by guessing what is right. Pine never
writes to the folder unless it is absolutely sure it knows what it is
doing. 
   
There are some steps which can be taken to reduce the risk of these
conditions coming up. Some of these steps may require the assistance of
your system adminstrator (or whomever it was that built and installed Pine
on your system): 
    1. Use IMAP instead of NFS to access remote folders. Problems with
       locking over NFS are perhaps the single most important cause of
       user difficulties.  Using IMAP eliminates this class of problem.
    2. Consider enabling the mbox driver in Pine. If the mbox driver is
       enabled, mail is transferred from the /usr/spool/mail mail into a
       file called mbox in your home directory, if mbox exists. The home
       directory mbox file is then your INBOX. This has the advantage
       that Pine and the mail delivery system are less often in
       contention for the INBOX, and never both trying to update it.
       Pine only empties the /usr/spool/mail file, it never tries
       updating it. 
    3. Be careful not to run other programs that modify your folders
       while you are running Pine. Such programs may change the folder
       out from under Pine, and lead Pine to conclude that there is a
       problem with its view of the file. 
       
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477s@shiva1.cac.washington.edu>
Content-Description: What is folder locking and how does it work?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is folder locking and how does it work?

                                       

Locks are used by Pine and other mail programs to prevent damage from
occurring to the mail file when multiple programs try to write to the file
at the same time. 
   
Because there are many different schemes of mail file locking used on
UNIX, Pine implements all of them. The result is a lot of complexity. 
   
There are several reasons why locking needs to be done:
   
    1. If you want to read the mail file, you want to make sure that no
       other process will modify the mail file while you are reading it.
       
    2. If you want to write to the mail file, you want to make sure that
       no other process is accessing the mail file while you are writing
       it.
       
    3. If you have the mail file open, you want to make sure that no
       other process can alter any of the internal contents of the mail
       file that you have read, but it is OK if another process appends
       new data to the mail file.
       
    4. If you want to alter any of the internal contents of the mail
       file, you want to make sure that no other process has the mail
       file open.
       
There are several mechanisms of locking:
   
     * The creation of a file which has the same name as the mail file,
       but with a suffix of ".lock" (for example, this lock for
       /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This
       file accomplishes locks (1) and (2) above. This is an exclusive
       lock. 
     * The use of an flock() with LOCK_SH on the mail file. This
       accomplishes lock (1), and prevents lock (2). Multiple processes
       can do this. 
     * The use of an flock() with LOCK_EX on the mail file. This
       accomplishes lock (2), and prevents lock (1). This is an exclusive
       lock. 
     * The use of an flock() with LOCK_EX on a file on /tmp. The file
       name used depends upon the version of Pine. This accomplishes
       locks (3) and (4). This is an exclusive lock. 
       
On SVR4-based systems, the lockf() subroutine or fcntl() system call it
used instead of flock(). It is rumored that this creates a kind of lock
file as well, but this has not been directly verified. 
   
_NOTE: flock() on BSD systems does not work over NFS, so only the most
basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4
systems, fcntl() locking attempts to work over NFS, but there are known
problems in the rpc.lockd daemon which have caused hangs if an application
beats on the mechanism too much (and Pine beats on it). All of the above
mechanisms work reliably over IMAP connections._
   
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477t@shiva1.cac.washington.edu>
Content-Description: What happens when two Pine sessions access the same mailbox at the same time?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What happens when two Pine sessions access the same mailbox at the same time?

                                       

This varies depending on what format your folders are stored in. With the
default Berkeley format, the last session to open a folder will get full
access to the folder and the previous session(s) will be changed to
read-only access. When a folder is read-only, you will not see any further
updates to that folder until it is reopened with full access. Currently
the INBOX cannot be reopened without exiting and restarting Pine. With the
Tenex format, any number of sessions can simultaneously have full access
to a folder, with the exception that expunging is disabled. See "What is a
Tenex mailbox and why should I use it?" for more information. 
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477u@shiva1.cac.washington.edu>
Content-Description: Why did I get the message "locked, override in _XXX_ sec"?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why did I get the message "locked, override in _XXX_ sec"?

                                       

The message "locked, will override in _xxx_ seconds" occurs when Pine has
discovered that some other mail program claims to be accessing your mail
folder (i.e. _folder_.lock exists). This is a very low-level lock used by
programs such as the system mailer in delivering mail, and by certain
programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only
to be acquired and held for a very short period of time (less than a
second). 
   
It starts with 285 seconds, retries every second, and issues that message
every 15 seconds. The total period of time, 5 minutes, is the time that it
will keep on trying before it concludes that the lock is false -- that is,
that whatever program locked the folder forgot to unlock it (perhaps it
crashed) -- and Pine will go ahead and claim the lock for itself. 
   
This is not due to a conflict between two copies of Pine, since Pine
interlocks against itself in a higher-level fashion. 
   
_NOTE: On some systems with 14 character filename limits, attempting to
open a folder with a 14 character name (e.g. saved-messages) will trigger
this sequence. Folder names should be limited to 9 characters or less on
those systems._
   
--0-1178456012-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477v@shiva1.cac.washington.edu>
Content-Description: Why doesn't Pine recognize Content-Length header field?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why doesn't Pine recognize Content-Length header field?


It would be a significant detriment to the performance of the Berkeley
format mailbox parsing code, as well as to Pine's behavior on normal
systems which do not use the Content-Length: header, if any attempt were
made to implement Content-Length:. 

There are many serious technical problems with the Content-Length: 
header, and we do not recommend its use.  Furthermore, we recommend that a
mail delivery agent such as our sendit or tmail tool be used that applies
smart quoting, as opposed to the ordinary BSD /bin/mail quoting of all
lines that begin with "From ".  We have installed such tools on all of our
systems. 

For example, one problem is that a system whose mailer does not implement
Content-Length: will also not enforce its validity should that header
appear. This offers significant potential for mischief.  Another problem
is that Berkeley format mailbox files which use the Content-Length: header
can not be edited with an editor such as emacs or vi without invalidating
the Content-Length: field.  If this problem is not a consideration at your
site, we recommend the use of the tenex format (mail.txt), which is also
length tagged but in a much more efficient fashion. 

>From our perspective, these problems outweigh any possible benefit of
supporting Content-Length: in Berkeley format mailbox files.  At the
present time there are no plans to do so. 
 
--0-1178456012-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-785766230-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477w@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-785766230-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477x@shiva1.cac.washington.edu>
Content-Description: How do I "paste" an address from the addressbook into the text of a message?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I "paste" an address from the addressbook into the text of a message?

                                       

Pine does not currently support this directly, but here is a work-around: 
    1. Move the cursor to the Cc: line. 
    2. Enter the nickname or press Ctrl-T to search the addressbook and
       select the entry. 
    3. Use Ctrl-K to delete that address from the Cc: line. 
    4. Move the cursor where you want it in the body of the message. 
    5. Press Ctrl-U to insert the address. 
       
   This is a round-about way to get the job done, but it works...
   
--0-785766230-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477y@shiva1.cac.washington.edu>
Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I convert Berkeley Mail aliases to Pine Addressbook?
                                       

The Pine source distribution includes a shell script to do this in the
contrib/utils directory. It is called brk2pine.sh. 
   
--0-785766230-790627371=:7477
Content-Type: MULTIPART/MIXED; BOUNDARY="0-546205362-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477z@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-546205362-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477A@shiva1.cac.washington.edu>
Content-Description: How do I convert Elm aliases to Pine Addressbook?

From: Klaus Wacker <wacker@Physik.Uni-Dortmund.DE>
Subject: How do I convert Elm aliases to Pine Addressbook?

                                       
I wrote my own perl script, which I claim digests everything elm accepts
and converts it into something pine accepts. Please tell me if you find
otherwise. I intend to use this script regularly to keep system-wide
aliases and addressbooks in synch. It is archived at:

  http://www.Physik.Uni-Dortmund.DE/wacker/elm-to-pine

A copy is below. 

--0-546205362-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=elm-to-pine
Content-ID: <Pine.ULT.3.92.950120104128.7477B@shiva1.cac.washington.edu>
Content-Description: elm-to-pine: Convert elm aliases file to Pine Addressbook

#!/usr/local/bin/perl
# 
# elm-to-pine: Convert elm aliases file to pine address book
# Author: Klaus Wacker (wacker@Physik.Uni-Dortmund.DE)
#
# Usage e.g.
# elm-to-pine ~/.elm/aliases.text >~/.addressbook
#

# get a line, combining continuation lines
#  that start with whitespace
# (taken from the perl man page and modified)
sub get_line {
    return 0 if eof();
    $thisline = $lookahead;
  line: while ($lookahead = <>) {
      if ($lookahead =~ /^[ \t]/) {
	  $thisline .= $lookahead;
      }
      else {
	  last line;
      }
  }
    $thisline;
}

$lookahead = <>;	# get first line
while ($_ = do get_line()) {
    next if /^\#/;		# Skip comments
    chop;
    s/\t/ /g;			# Lets not get confused by any tabs in the file
    ($nicks,$name,$address)=split(/ *= */,$_,3);
    @nick=split(/ *, */,$nicks);
    ($fullname,$remark)=split(/ *, */,$name,2);
    $fullname =~ s/;/,/;	# Lastname[;,] Firstname
    if ($address =~ /,/ ) {$address="(".$address.")";} # Its a list
    foreach $nicki (@nick) {	# Pine doesn't allow multiple nicknames
	printf "%s\t%s\t%s\t\t%s\n",
	$nicki, $fullname, $address, $remark;
	$address = $nick[0];	# Let additional nicks point to the first one
    }
}

--0-546205362-790627371=:7477--
--0-785766230-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-369780167-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477C@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477D@shiva1.cac.washington.edu>
Content-Description: Can Kerberos or AFS authentication be used with Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can Kerberos or AFS authentication be used with Pine?

                                       
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. 
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477E@shiva1.cac.washington.edu>
Content-Description: Can PC-Pine be used with a POP server?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Can PC-Pine be used with a POP server?

                                       

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. 
    
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477F@shiva1.cac.washington.edu>
Content-Description: What is a Tenex mailbox and why should I use it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is a Tenex mailbox and why should I use it?



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. 
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477G@shiva1.cac.washington.edu>
Content-Description: Where does Pine look for configuration information?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Where does Pine look for configuration information?

                                     
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".
   
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477H@shiva1.cac.washington.edu>
Content-Description: How do I make Pine work with my older terminal?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: How do I make Pine work with my older terminal?

                                       

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. 
   
--0-369780167-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477I@shiva1.cac.washington.edu>
Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail?

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?
                                       

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. 
       
   
--0-369780167-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-117366150-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477J@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-117366150-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477K@shiva1.cac.washington.edu>
Content-Description: To what platforms has Pine been ported?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: To what platforms has Pine been ported?

The Pine distribution includes binaries for AIX 3.2 (on RS/6000), HP/UX
9.0, Linux 1.1, NeXTStep (on NeXT hardware), SunOS 4.1 (on SPARCStations),
Solaris 2.2, Ultrix 4.1 and 4.2 (on DECStations), MS-DOS (PC-Pine) and
MS-Windows (PC-Pine for Windows). 
   
PC-Pine is available for the following TCP/IP stacks: FTP's PC/TCP,
University of Waterloo's WATTCP stack with packet drivers, Novell's LAN
Workplace, Sun's PC/NFS, and Winsock. 
   
Pine has been compiled on other UNIX platforms (4.3 Berkeley UNIX, DEC
OSF/1 V1.2A, Dynix/PTX V1.4.0, VAX Ultrix 4.1, A/UX 3.0, BSD/386 Gamma
4.1, Convex, Dynix 3.0 and 3.1 on Sequent Symmetry, Interactive Systems
Corporation UNIX, Silicon Graphics IRIS with IRIX 4.0.1, SCO Unix, System
V release 4) as well. 
   
--0-117366150-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477L@shiva1.cac.washington.edu>
Content-Description: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder.

Some AIX distributions apparently include a compiler that does not
correctly compile certain constructs used in Pine 3.89 and earlier. We
think that Pine 3.90 works around the problems but it is difficult for us
to confirm this since there is considerable variation among AIX systems.
We have also not been able to identify a particular version or patch of
AIX or the compiler that is the culprit. 
   
--0-117366150-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477M@shiva1.cac.washington.edu>
Content-Description: I cannot compile under SCO unix, why not?

From: Gunther Anderson <gunther@ssi.edc.org>
Subject: I cannot compile under SCO unix, why not?


Pine has been tested and compiles just fine on a suitably equipped SCO
Unix 3.2.4, and probably works on the whole 3.2 series (testing has not
been as extensive).  It handles both MMDF and sendmail mailboxes without
needing recompilation.  It should be sufficient just to unpack the source
tree and run "sh build sco" at the top level.  You need to own the
complete Development System, and the Developer's Versions of the other
packages.  Pine will not compile without TCP/IP support. 

The most common problem is when people own the Development System, but
keep getting missing header files (netbd.h is one) in their builds.  This
is a common problem on SCO systems because of the great fragmentation SCO
enjoys in the marketing of system components.  It is easy to get confused
about just what you've bought.  And in this case, haven't bought. What you
need is the "Developer's Version" of the TCP/IP product.  The normal
version just supports the TCP/IP protocol, but doesn't include tools
(including header files) to compile TCP/IP-specific programs.  Alas, the
only remedies available to you are to pick up a pre-compiled version (mine
is on odi.cwc.whecn.edu, ftp.celestial.com has their own, which prefers
Bezerk mailboxes, though it supports MMDF too), or to buy the Developer's
Version of TCP/IP.  If you intend to do any serious compiling of Internet-
available programs, I'd recommend the latter, though many of the most
useful ones are available precompiled on other FTP sites.

--0-117366150-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-656848291-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477N@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-656848291-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477O@shiva1.cac.washington.edu>
Content-Description: Why should I use the builtin Bug Report command?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why should I use the builtin Bug Report command?

Using the built-in Bug Report command (B on the Main Menu or any Help
screen) is useful because it will automatically include configuration
information that may be essential to determining the cause of the problem
you are experiencing.  It also gives you the opportunity to conveniently
include the current message as an attachment in case you believe that 
the problem is specific to that message.

--0-656848291-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477P@shiva1.cac.washington.edu>
Content-Description: Why does the Bug Report Screen come up when I didn't ask for it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: Why does the Bug Report Screen come up when I didn't ask for it?


We don't know yet.

--0-656848291-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477Q@shiva1.cac.washington.edu>
Content-Description: I have found a bug in Pine 3.05. Could you please fix it?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: I have found a bug in Pine 3.05. Could you please fix it?

                                       
When a bug is identified in an old release, there is a very strong
possibility that the associated code has been re-written to the point that
a fix will not apply to the current release.  Hence, if we can't reproduce
the problem in the current version, our standard response will be to ask
you to upgrade. 

--0-656848291-790627371=:7477--
--0-1726109301-790627371=:7477
Content-Type: MULTIPART/DIGEST; BOUNDARY="0-456850581-790627371=:7477"
Content-ID: <Pine.ULT.3.92.950120104128.7477R@shiva1.cac.washington.edu>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477S@shiva1.cac.washington.edu>
Content-Description: What are the current versions of Pine and related software?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What are the current versions of Pine and related software?

                                       

The current version of Pine is 3.91. The current version of Pico is 2.5. 

--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477T@shiva1.cac.washington.edu>
Content-Description: What is new in this version of Pine?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What is new in this version of Pine?

                                       

These are the changes and improvements since Pine 3.89: 
     * Finished all the "Not implemented yet" commands: 
          + Bounce (Remail) 
          + Flag (Set message status) 
          + Pipe (Pipe msg to external cmd; Unix only) 
          + Select,Apply,Zoom (Aggregate operations) 
          + Setup/Config (Pinerc configuration screen) 
     * News posting 
     * News subscription/unsubscription 
     * Multiple address books 
     * Postpone multiple messages 
     * Customizable headers for Composer 
     * Mailcap support 
     * Improved support for multiple incoming message folders 
     * enable-alternate-editor-implicitly feature (except for editing
       headers) 
     * All .pinerc features now settable from command line 
     * Way to control which options are user-configurable (Unix only)
     * Way to have Save *not* implicitly delete 
     * Way to use current-working-directory for Export, Read File, etc. 
     * A _preliminary_ version of PC-Pine for Windows/Winsock (but not 
       OS/2) 
       
--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477U@shiva1.cac.washington.edu>
Content-Description: When is the next release of Pine (tentatively) scheduled?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: When is the next release of Pine (tentatively) scheduled?

                                       
We don't know right now.  3.92 is under active development, but no dates
yet.  Besides, our track-record on meeting projected release schedules is
terrible, so you shouldn't believe any dates we are foolish enough to
suggest anyway. 
   
--0-456850581-790627371=:7477
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.ULT.3.92.950120104128.7477V@shiva1.cac.washington.edu>
Content-Description: What new features will the future releases of Pine include?

From: The Pine Development Team <pine-faq@docserver.cac.washington.edu>
Subject: What new features will future releases of Pine include?

The list for 3.92 is not frozen yet.  This release will have a number of
bug fixes, but it will also introduce several new features.  Some of
the things we know will be there include:

 o Fix for some pine.conf variables not working (e.g. local bug address).
 o Delete flag will no longer be preserved on Save.
 o Bky mbox format performance bug fixed.
 o Reply prompt will change if there is a Newsgroups header present.
 o Improvements in software flow-control handling.
 o Improvements in bug report command.
 o Ability to specify an alternative to the sendmail MTA.
 o Support for negotiating 8BITMIME with an ESMTP server.
 o Mouse support for use with X terminals.
 o Pull-down command menus in the Windows version.
 o Feature to disable capture of pipe command output.
 o Ability to use mailcap viewer for attachments of type TEXT.
 o Support for .mime.types file to specify attachment types.

After 3.92 is released, here are a few of the things that we plan to 
work on:

     * Additional MIME support, esp. controlling file TYPING 
     * PEM and/or PGP support 
     * External directory services access 
     * Kerberos support 
     * RFC1522 header encoding for 8bit character sets 
     * Location independence of support files 
     * Offline support 
     * Hierarchy support (awaits IMAP4) 
     * Answered flag not set if reply is postponed (awaits IMAP4) 
     * Faster detection of folders with Recent messages (awaits IMAP4) 
     * Faster fetching of headers (awaits IMAP4) 
     * Determination of which flags are permanent (awaits IMAP4) 
   
--0-456850581-790627371=:7477--
--0-1726109301-790627371=:7477--


From owner-pine-info@cac.washington.edu  Sat Jan 28 06:49:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01820;
	Sat, 28 Jan 95 06:49:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21121;
	Sat, 28 Jan 95 06:45:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21115;
	Sat, 28 Jan 95 06:45:57 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYEDL-00038pC; Sat, 28 Jan 95 06:33 PST
To: pine-info@cac.washington.edu
From: Clif Daniel <cdaniel@tyrell.net>
Subject: PINE-Win DLL and/or Code ?
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SUN.3.91.950125164015.15472C-100000@tyrell.net>
Mime-Version: 1.0
Date: Wed, 25 Jan 1995 22:49:48 GMT

 I run a Windows network which supports a multi-node BBS based on PowerBBS
for Windows. 
 I really like PCPine and use it personally whether over SLIP/PPP or logged
on to a providers UNIX system.
 PowrBBS for Windows has the capability of calling Windows Apps when they
are compiled as *.DLL. There are Telnet,FTP,and a few database and BBS door
type *.DLL apps available, well back to the real purpose for posting :

 I would love to be able to allow the dial-up BBS users to use PCPine for
a news / mail reader while on-line .... I'm sure that other PowerBBS
for Windows Administrators would be interested. 


From owner-pine-info@cac.washington.edu  Sat Jan 28 07:14:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02228;
	Sat, 28 Jan 95 07:14:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23279;
	Sat, 28 Jan 95 07:11:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23273;
	Sat, 28 Jan 95 07:11:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYEZl-00039IC; Sat, 28 Jan 95 06:56 PST
To: pine-info@cac.washington.edu
From: jywong@abalone.ucsb.edu (Joyce Y. Wong)
Subject: Fcc:  interactive possible?
Date: 26 Jan 1995 16:46:31 -0800
Message-Id: <3g9fp7$dgi@abalone.ucsb.edu>


Is there a way to configure pine such that it will ask you
if you want to send a copy to Fcc: rather than doing it
automatically?  I know that you can turn it on and off, but
is there a way so you can interactively use it?

thanks

joyce


From owner-pine-info@cac.washington.edu  Sat Jan 28 08:03:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03099;
	Sat, 28 Jan 95 08:03:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21960;
	Sat, 28 Jan 95 08:00:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21954;
	Sat, 28 Jan 95 08:00:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYFNc-00038nC; Sat, 28 Jan 95 07:48 PST
To: pine-info@cac.washington.edu
From: cellsys@earthlink.net
Subject: cmsg cancel <3g9j6p$c61@moon.earthlink.net>
Control: cancel <3g9j6p$c61@moon.earthlink.net>
Date: Fri, 27 Jan 1995 14:49:39 GMT
Message-Id: <cancel.3g9j6p$c61@moon.earthlink.net>




From owner-pine-info@cac.washington.edu  Sat Jan 28 08:08:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03202;
	Sat, 28 Jan 95 08:08:45 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23882;
	Sat, 28 Jan 95 08:05:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23876;
	Sat, 28 Jan 95 08:05:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYFUS-00039LC; Sat, 28 Jan 95 07:55 PST
To: pine-info@cac.washington.edu
From: cellsys@earthlink.net
Subject: cmsg cancel <3g9j6i$c61@moon.earthlink.net>
Control: cancel <3g9j6i$c61@moon.earthlink.net>
Date: Fri, 27 Jan 1995 14:50:07 GMT
Message-Id: <cancel.3g9j6i$c61@moon.earthlink.net>




From owner-pine-info@cac.washington.edu  Sat Jan 28 08:33:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03585;
	Sat, 28 Jan 95 08:33:39 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22312;
	Sat, 28 Jan 95 08:30:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22306;
	Sat, 28 Jan 95 08:30:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYFp8-00038nC; Sat, 28 Jan 95 08:16 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Fcc:  interactive possible?
Date: 28 Jan 1995 15:33:26 GMT
Message-Id: <3gdo46$nd7@cronkite.ocis.temple.edu>

Comes here Mr. Joyce Y. Wong with this opinion in the "comp.mail.pine" group in
this article on 26 Jan 1995 16:46:31 -0800:

 +   Is there a way to configure pine such that it will ask you
 +   if you want to send a copy to Fcc: rather than doing it
 +   automatically?  I know that you can turn it on and off, but
 +   is there a way so you can interactively use it?

Turn the default option to off, then while composing you can set the value
to the Fcc: header to whichever folder you want by using ^R for rich
headers.

Ofcourse if you want that header to appear by default for every composition
just add that in the default-composer-hdrs option in the Setup/Config screen.

default-composer-hdrs = Fcc,
                       Subject,
                       Bcc,
                       Cc,
                       To

Hope this helps.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Sat Jan 28 08:33:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03606;
	Sat, 28 Jan 95 08:33:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22345;
	Sat, 28 Jan 95 08:31:11 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22339;
	Sat, 28 Jan 95 08:31:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYFs9-00039QC; Sat, 28 Jan 95 08:19 PST
To: pine-info@cac.washington.edu
From: schueman@access.digex.net (Greg Schueman)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 26 Jan 1995 19:24:49 -0500
Message-Id: <3g9egh$s6l@access3.digex.net>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca> <3g18a5$epp@gryphon.phoenix.net>

In article <3g18a5$epp@gryphon.phoenix.net>,
Paul Flores <pflores@phoenix.phoenix.net> wrote:
>Rashid Bawa (rbawa@gbc.gbrownc.on.ca) wrote:
>: I am looking out for POP binaries (POP, POP2, POP3) that will run on
>: a SparcClassic running Solaris 2.3. If anyone has the location of a site,
>: please send me email.
>
>: Thanking you in advance.
>
>
>Please post here as well!!!!   (Or send me email as well!!!)
>
>Paul
>
>http://www.phoenix.net/USERS/pflores.html
>


Here goes, you can find a POP3 mail server, source and binaries
ported to Solaris 2.x at:

ftp://ftp.digex.net/pub/access/schueman/popper.tar.gz

This code has been subjected to constant use since April 1994 under 
Solaris 2.3.

Enjoy,

 -Greg Schueman




From owner-pine-info@cac.washington.edu  Sat Jan 28 08:34:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03627;
	Sat, 28 Jan 95 08:34:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24174;
	Sat, 28 Jan 95 08:30:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24168;
	Sat, 28 Jan 95 08:30:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYFpE-00039RC; Sat, 28 Jan 95 08:16 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: how to set up news on pine; do i need imap?
Date: 28 Jan 1995 15:37:02 GMT
Message-Id: <3gdoau$nd7@cronkite.ocis.temple.edu>

Comes here Mz. Joyce Y. Wong with this opinion in the "comp.mail.pine" group in
this article on 26 Jan 1995 17:09:49 -0800:

 +   how do i set up my pine account so i can read news there?
 +   which configuration item is it?

nntp-server = here goes your newsserver address.

Set the above option in the Setup/Config screen. Exit and Quit, restart Pine to
read/post news.

Hope this helps

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________













--
--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Sat Jan 28 10:52:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06568;
	Sat, 28 Jan 95 10:52:31 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25952;
	Sat, 28 Jan 95 10:49:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25946;
	Sat, 28 Jan 95 10:49:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYHzB-00039gC; Sat, 28 Jan 95 10:35 PST
To: pine-info@cac.washington.edu
From: blumer@panix.com (Ronald Blumer)
Subject: HELP ME GET RID OF MY [17;3H's PLEASE!!!
Date: 27 Jan 1995 21:29:18 -0500
Message-Id: <3gca5u$t1c@panix.com>

Here is one that seems to have stumped everyone. I have Procomm for DOS 
(version 2.0l) on a 386sx DOS 4.01 (go ahead laugh) running into a 
Practical Perpherals pm14400fxmt modem and I use Pine and Pico on my 
internet provider PANIX.

The problem started a few days ago when I had to reconfig Procomm because 
of a problem I am having. Now when ever I am in PINE or PICO I see these 
strange things like [5;41H whenever I backspace use my arrow keys. Odd 
things also keep happening on the very top and bottom lines of the 
screen. Where I see bit of the text appearing. Sometimes as well the 
cursor seems to get stuck on a line.  Everything clears up when I ^L 
(refresh the screen.)

Easy you say, a terminal emulation problem. That is what the staff at 
PANIX kept telling me.  Procomm is set to one terminal and PANIX is set 
to another. But it wasn't true alas. I kept reconfiguring both and 
checking my "termtype" file as they told me to and the status line on 
Procomm and they are the same. I tried VT100, VT102, VT220. Same problems.

So I call Procomm. I am on the telephone with them for of an hour (at my 
expense of course) They tried everything. Me calling them via modem etc., 
etc. And they can't figure it out either.

When I use another crummy communications program I have (QL2FAX) I don't 
get this problem at all so it has to be Procomm. But what?

If anyone can figure this out I would be grateful forever... I sent you 
an original copy of DOS 1.1 ...I'd name your price. 

Help I am seeing [20;12H's in my sleep.

Ronald Blumer
New York City
blumer@panix.com


From owner-pine-info@cac.washington.edu  Sat Jan 28 11:01:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06835;
	Sat, 28 Jan 95 11:01:52 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24143;
	Sat, 28 Jan 95 10:59:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24137;
	Sat, 28 Jan 95 10:59:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYI6L-00039iC; Sat, 28 Jan 95 10:42 PST
To: pine-info@cac.washington.edu
From: FLAVELL@crnvma.cern.ch (Alan J Flavell)
Subject: Re: Pine/VMS
Message-Id: <17333ECA9S86.FLAVELL@cernvm.cern.ch>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu> <1995Jan14.220520@cchs.su.edu.au> <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au>
Date: Fri, 27 Jan 1995 16:49:31 GMT

In article <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au>
Alan Agnew <agnew@maize.qut.edu.au> writes:
 
>In a previous posting it was stated that PINE 3.91  for VMS is available
>from lenin.cc.rochester.edu.
>
>I have been attempting to connect to lenin.cc.rochester.edu from Australia
>for several days now, but have never suceeded.
 
Try Yehavi's own home site, VMS.HUJI.AC.IL - from an anonymous FTP
do a CD LOCAL, all should then be clear.
 
(I called it from a MULTINET-based VMS system, used BINARY and
STRUCT VMS, and successfully retrieved the UNZIP.EXE and the
PINExxxx.ZIP).
 
Keep in touch: I'm trying to get this working for my users, but with
apparently so few people using it on VMS it's difficult to get
advice.  (This forum is overwhelmed by un*x-based people, and
the rest seem to be PC-based.  There are very few references to
VMS, and some of those seem to refer to a commercial port of PINE).


From owner-pine-info@cac.washington.edu  Sat Jan 28 11:05:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06898;
	Sat, 28 Jan 95 11:05:37 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26173;
	Sat, 28 Jan 95 11:03:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26167;
	Sat, 28 Jan 95 11:03:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYIEt-00039SC; Sat, 28 Jan 95 10:51 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: several Pine suggestions
Date: Thu, 26 Jan 1995 13:55:24 +0000
Message-Id: <Pine.SUN.3.91.950126135229.26920Y-100000@grus.cus.cam.ac.uk>
References: <3g0pds$r9c@hobbes.cc.uga.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g0pds$r9c@hobbes.cc.uga.edu> 

On 23 Jan 1995, Glenn Leavell wrote:

> 
> 1)  In INDEX mode, allow the 'k' and 'j' keys to be used to move the current
>     pointer up and down (j key would only function like this if
>     jump short cut were turned on).  This convention can be
>     found in vi, Elm, Gopher, and other utilities, so it makes things
>     somewhat consistent.
> 
I think this is a dreadful idea. It of course harks back to long dead 
terminals which had arrows engraved on those keys, accessed, I think, in 
ESCAPE mode. 

As someone who teaches Pine, its transparency is a major virtue, and 
those places where this breaks down (like the dreadful Y for prYnt)  
cause problems; when teaching it is wonderful for A to be Add, C compose 
and so on. Previous and Next are enough alternatives to up-arrow and 
down-arrow, thanks.


=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Sat Jan 28 12:14:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08209;
	Sat, 28 Jan 95 12:14:50 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25047;
	Sat, 28 Jan 95 12:12:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25036;
	Sat, 28 Jan 95 12:12:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYJDV-00039jC; Sat, 28 Jan 95 11:53 PST
To: pine-info@cac.washington.edu
From: cwgan@einstein.technet.sg (Cheong Weei Gan)
Subject: Re: pine to cc:Mail
Date: 24 Jan 1995 02:40:44 GMT
Message-Id: <3g1pbc$ams@raffles.technet.sg>
References: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>


I think ccMail's SMTP gateway currently does not support MIME but I 
think Lotus working on a version that is faster and
will support MIME




In article <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu>, Judd Deaver <jdeaver@u.washington.edu> says:
>
>I am trying to attach a file to a message in Pine to be sent to a cc:Mail 
>network. I sent a Binary attachment but it did not seem to make it. Could 
>this be because his network does not support MIME or because the way pine 
>attaches files is different then cc:mail? If it is because they don't 
>supprt MIME would an ASCII file attachment make it down or does pine 
>automatically MIME encrypt all attachments?
>


From owner-pine-info@cac.washington.edu  Sat Jan 28 15:17:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11778;
	Sat, 28 Jan 95 15:17:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29336;
	Sat, 28 Jan 95 15:14:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29330;
	Sat, 28 Jan 95 15:14:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYM4r-0003A8C; Sat, 28 Jan 95 14:57 PST
To: pine-info@cac.washington.edu
From: openway@CERF.NET (LIOCS Corporation)
Subject: pc-pine attachments >32k fail
Date: 28 Jan 1995 14:33:01 -0800
Message-Id: <3gegmt$g3@nic.cerf.net>

I'm currently using pc-pine3.91 and experience problems sending
attachments greater than 32k.  No errors are reported but the
message is never sent.  I tested Pine on the host running imapd
and its sendmail doesnt have a problem.  Any ideas?

Thanks
dave@liocs.com



From owner-pine-info@cac.washington.edu  Sat Jan 28 15:46:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12465;
	Sat, 28 Jan 95 15:46:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27761;
	Sat, 28 Jan 95 15:43:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27755;
	Sat, 28 Jan 95 15:43:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYMZS-00039iC; Sat, 28 Jan 95 15:28 PST
To: pine-info@cac.washington.edu
From: valko@cyberspace.com (Jack Valko)
Subject: Re: Need to secure pine
Date: 26 Jan 1995 16:39:01 -0800
Message-Id: <3g9fb5$gvo@case.cyberspace.com>
References: <3g1e2s$5sk@case.cyberspace.com> <Pine.SUN.3.91.950124173442.24402T-100000@apus.cus.cam.ac.uk>

Barry Landy (bl10@cus.cam.ac.uk) wrote:
: On 23 Jan 1995, Jack Valko wrote:

: > I would like to know if there is some way to set a configuration in pine 
: > so that users can't change it from the Setup menu.  Specifically, I want 
: > to restrict the alternate editor feature.  I have specified 
: > 'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
: > doesn't seem to do it.  Can anyone help?
: > 
: We have the following set in pine.conf.fixed, and it seems to do the job:-

: no-enable-alternate-editor-cmd,
: no-always-use-alt-editor,
: no-enable-alternate-editor-implicitly,

This seems to have fixed the problem.  Thanks to all who responded.

==================================================
Jack Valko           |       - Cyberspace -
System Administrator | 300 Queen Anne Ave. N. #396 
cyberspace.com       |   Seattle, WA 98109-4599 
cyberspace.net       |       (206) 281-5397 
==================================================


From owner-pine-info@cac.washington.edu  Sat Jan 28 16:31:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13430;
	Sat, 28 Jan 95 16:31:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28318;
	Sat, 28 Jan 95 16:28:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28312;
	Sat, 28 Jan 95 16:28:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYNFg-00039zC; Sat, 28 Jan 95 16:12 PST
To: pine-info@cac.washington.edu
From: Alan Agnew <agnew@maize.qut.edu.au>
Subject: Re: Pine/VMS
Date: Wed, 25 Jan 1995 10:33:46 +1000
Message-Id: <Pine.ULT.3.91.950125102702.14486A-100000@maize.qut.edu.au>
References: <1995Jan7.184624.17081@galileo.cc.rochester.edu> <Pine.OSF.3.91.950112090206.6683A-100000@alpha.loyno.edu> <1995Jan14.220520@cchs.su.edu.au>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <1995Jan14.220520@cchs.su.edu.au> 

In a previous posting it was stated that PINE 3.91  for VMS is available
from lenin.cc.rochester.edu.

I have been attempting to connect to lenin.cc.rochester.edu from Australia
for several days now, but have never suceeded.

A ping shows 100% packet loss.

A traceroute gets as far as taylor4-bbgw.utd.rochester.edu and then nothing.

Is there a known difficulty in connecting to lenin.cc.rochester.edu?

Does anyone else have this version of PINE on an anonymous FTP  server?


	Alan Agnew
	Network Services
	Computing Services
	Queensland University of Technology

	Phone: (07) 864 1703		E-Mail: A.Agnew@qut.edu.au


From owner-pine-info@cac.washington.edu  Sat Jan 28 19:13:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17021;
	Sat, 28 Jan 95 19:13:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03045;
	Sat, 28 Jan 95 19:09:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03039;
	Sat, 28 Jan 95 19:09:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYPcW-0003AWC; Sat, 28 Jan 95 18:44 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: [Q] How can I include video attachments (.mpeg) ?
Date: 28 Jan 1995 15:23:41 GMT
Message-Id: <3gdnht$nd7@cronkite.ocis.temple.edu>

Mr. David L Miller writes:

 +   Pine does not currently recognize mpeg files, so it labels that
 +   application/octet-stream.  Pine 3.92 wqill have support for a .mime-types
 +   file, so you can add other attachment types... 

Yet another Pine related ".*" file.
In future releases is it possible to direct them all Pine related .files to
a directory (.pine or something similar) that way it will be easy to tell
what are all the dot files that Pine looks up by default without having to
modify that in the os-xxx.h file and rebuild.

As of now we have:
pinerc
addressbook
addressbook.lu
pine-debug*
pine-interrupted
pine-interrupted-lock
soon .mime-type,....

Thanks

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________




From owner-pine-info@cac.washington.edu  Sat Jan 28 19:51:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17668;
	Sat, 28 Jan 95 19:51:41 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03541;
	Sat, 28 Jan 95 19:49:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03535;
	Sat, 28 Jan 95 19:49:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYQQC-0003A8C; Sat, 28 Jan 95 19:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Changing From: header
Date: Thu, 19 Jan 1995 16:13:21 -0800
Message-Id: <Pine.ULT.3.92.950119161233.6255A-100000@shiva1.cac.washington.edu>
References: <ii.790481918@shell1.best.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ii.790481918@shell1.best.com> 


Your system administrator can rebuild Pine with the "#define
ALLOW_CHANGING_FROM" line uncommented in the pine/os-???.h file... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 18 Jan 1995, Nancy McGough wrote:

> Date: 18 JAN 1995 18:22:18 -0800 
> From: Nancy McGough <ii@best.com>
> Newgroups: comp.mail.pine
> Subject: Changing From: header 
> 
> I'd like to change the From: header in mail I send from Pine
> by putting something like this in my .pinerc:
> 
> customized-hdrs=Organization: $ORGANIZATION,
>         From: Nancy McGough <nancym@ii.com>
> 
> 
> Unfortunately, when I try this Pine gives a message that says
> I can't change the From header.  Is there any way around this?
> E.g., could the system admins reset something to allow this?
> 
> Thanks for any info,
> Nancy
> 
> -- 
>  /\_/\   DUE TO EMAIL PROBLEMS, PLEASE SEND MAIL TO ME TO EITHER:   /\_/\
> ( o.o )                                                            ( o.o )
>  > ~ <           nancym@halcyon    -OR-    ii@best.com              > o <
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 19:51:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17689;
	Sat, 28 Jan 95 19:51:55 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01531;
	Sat, 28 Jan 95 19:48:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01525;
	Sat, 28 Jan 95 19:48:58 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYQQ2-00039zC; Sat, 28 Jan 95 19:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: PC-Pine & POP
Date: Thu, 19 Jan 1995 09:48:18 -0800
Message-Id: <Pine.ULT.3.92.950119094730.22532B-100000@shiva1.cac.washington.edu>
References: <jsweet.3.00002905@cory.eecs.berkeley.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <jsweet.3.00002905@cory.eecs.berkeley.edu> 


PC-Pine does not use POP, but it does require IMAP service from your mail
server. 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 19 Jan 1995, Julian Sweet wrote:

> Date: Thu, 19 JAN 1995 00:09:41 
> From: Julian Sweet <jsweet@cory.eecs.berkeley.edu>
> Newgroups: comp.mail.pine
> Subject: PC-Pine & POP 
> 
> Does my mail server have to be POP for PC-Pine to work? I got SLIP running no 
> problem....
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 19:52:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17710;
	Sat, 28 Jan 95 19:52:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03549;
	Sat, 28 Jan 95 19:49:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03543;
	Sat, 28 Jan 95 19:49:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYQQJ-0003AHC; Sat, 28 Jan 95 19:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Welcome to pine-info
Date: Fri, 20 Jan 1995 08:55:23 -0800
Message-Id: <Pine.ULT.3.92.950120085110.511B-100000@shiva1.cac.washington.edu>
References: <9501192250.AA10637@shivams.cac.washington.edu> <3fmt02$r46@newsreader.wustl.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fmt02$r46@newsreader.wustl.edu> 


On 19 Jan 1995, Lori Fox wrote:

> Date: 19 JAN 1995 23:35:30 GMT 
> From: Lori Fox <lef@wuacn.wustl.edu>
> Newgroups: comp.mail.pine
> Subject: Re: Welcome to pine-info 
> 
> Majordomo@cac.washington.edu wrote:
> : Welcome to the pine-info mailing list!
> 
> 
> Forgive this novice, but may I assume that everything that goes to this 
> mailing list will also go to comp.mail.pine ?
> 

Yes, psg.com runs a bi-directional gateway between comp.mail.pine and the
pine-info mailing list.  Note that it is operated by Randy Bush
<randy@psg.com>, not by the Pine Team.  Due to some lost messages that I 
just noticed a couple days ago the subscription address for the gateway 
was changed.  Hopefully that will improve performance and reliability of 
the gateway.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Sat Jan 28 19:52:17 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17731;
	Sat, 28 Jan 95 19:52:17 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01557;
	Sat, 28 Jan 95 19:49:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01551;
	Sat, 28 Jan 95 19:49:10 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYQQL-0003AOC; Sat, 28 Jan 95 19:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Pine Pipe to Zmodem
Date: Fri, 20 Jan 1995 08:57:52 -0800
Message-Id: <Pine.ULT.3.92.950120085613.511C-100000@shiva1.cac.washington.edu>
References: <3e7qmc$rod@little-miami.iac.net> <1995Jan4.005256.10505@math.utah.edu> <3eeni5$t36@wabash.iac.net> <ellis.789325031@gmi.edu>  <Pine.NXT.3.91.950106012216.22917A-100000@lipschitz> <3emev0$o7a@wabash.iac.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3emev0$o7a@wabash.iac.net> 


On 7 Jan 1995, Carl Jolley wrote:

> Date: 7 JAN 1995 11:19:44 -0500 
> From: Carl Jolley <cjolley@iac.net>
> Newgroups: comp.mail.pine
> Subject: Re: Pine Pipe to Zmodem 
> 
[...]
> Pine's pipe, i.e. pipe to a command and capture the output back into
> a viewer, does not seem to be documented in either the man pages or in
> Pine's help screens. I thought that something was broken, but now I
> understand that the operation of Pine's pipe is a "feature". It would be
> nice if in addition to the current operation of Pine's pipe there was an
> option to do a pipe without capturing the command's stdout.
> 

Pine 3.92 will allow this...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Sat Jan 28 19:52:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17760;
	Sat, 28 Jan 95 19:52:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01549;
	Sat, 28 Jan 95 19:49:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01543;
	Sat, 28 Jan 95 19:49:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYQQH-0003AEC; Sat, 28 Jan 95 19:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: "pico -w" and long lines
Date: Thu, 19 Jan 1995 09:41:08 -0800
Message-Id: <Pine.ULT.3.92.950119093948.22532A-100000@shiva1.cac.washington.edu>
References: <ii.790460725@shell1.best.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ii.790460725@shell1.best.com> 


Pico can only read lines of 256 or less characters.  It can create lines
of any (?) length though... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 18 Jan 1995, Nancy McGough wrote:

> Date: 18 JAN 1995 12:26:52 -0801 
> From: Nancy McGough <nancym@ii.com>
> Newgroups: comp.mail.pine, comp.editors
> Subject: "pico -w" and long lines 
> 
> If you use "pico -w" to edit a file, what are the longest lines
> it can deal with?  I know vi has a problem with long lines and
> I'm wondering if Pico does too.
> 
> Thanks,
> Nancy
> 
> -- 
>  /\_/\    Nancy McGough
> ( o.o )   Infinite Ink
>  > ~ <    http://www.jazzie.com/ii/  -OR-  http://www.best.com/~ii/
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:32:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21377;
	Sat, 28 Jan 95 23:32:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06118;
	Sat, 28 Jan 95 23:29:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06112;
	Sat, 28 Jan 95 23:29:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYTlf-0003AMC; Sat, 28 Jan 95 23:09 PST
To: pine-info@cac.washington.edu
From: marlman@netcom.com (Andrew Halvorsen)
Subject: Attribute Line..change?
Message-Id: <marlmanD32w3E.L6F@netcom.com>
Date: Fri, 27 Jan 1995 19:14:02 GMT


	Is there a way to change the attribute line in pine?
Thanks in Advance...


-- 
-ttyl
-andyh

______________________________________________________________________________
     Fans of Scott Ferrall, check out the alt.ferrall-vision newsgroup,
				or contact:
------------------------------------------------------------------------------
	 	 marlman@netcom.com = Andrew W. Halvorsen
			Voicemail = 510.328.5399
		 NHL = Novice Hockey League, you cake-eaters
______________________________________________________________________________


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:46:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21639;
	Sat, 28 Jan 95 23:46:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04202;
	Sat, 28 Jan 95 23:44:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04196;
	Sat, 28 Jan 95 23:44:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU6a-0003AMC; Sat, 28 Jan 95 23:31 PST
To: pine-info@cac.washington.edu
From: chengman@umich.edu (Dennis Cheng)
Subject: VMS Pine problems
Date: 27 Jan 1995 01:41:17 GMT
Message-Id: <3g9ivu$9ga@lastactionhero.rs.itd.umich.edu>

I have been trying to install PINE for VMS for a while now. We are 
running VMS 6.1 with DEC's UCX services. I obtained the PINE code from 
Israel and tried to compile it for the UCX service with little luck. Pine 
for VMS is a fairly important project for my organization so we are 
looking for help in getting PINE up from people who have done it before. 
We are even considering commercial sources for software that utilizes 
IMAP access.


Thanks in advance,

Dennis Cheng
University of Michigan, Ann Arbor MI.
Systems Consultant, Wayne Memorial Hospital-Health System, Honesdale PA.


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:47:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21660;
	Sat, 28 Jan 95 23:47:13 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06328;
	Sat, 28 Jan 95 23:44:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06322;
	Sat, 28 Jan 95 23:44:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU7I-0003A6C; Sat, 28 Jan 95 23:32 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: External Pagers
Date: Fri, 20 Jan 1995 14:46:37 -0800
Message-Id: <Pine.ULT.3.92.950120144130.511f-100000@shiva1.cac.washington.edu>
References: <3f1e2t$ovp@solaris.cc.vt.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3f1e2t$ovp@solaris.cc.vt.edu> 


Pine 3.92 will allow interactive programs to be used with the pipe
command.  

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 11 Jan 1995, matthew c. mead wrote:

> Date: 11 JAN 1995 20:12:13 GMT 
> From: matthew c. mead <mmead@goof.com>
> Newgroups: comp.mail.pine
> Subject: External Pagers 
> 
> 
> 	Well, I've built pine now, and got a nice pgp system going with it
> (which works well with elm, as well, btw).  The only problem is reading
> encrypted messages.  I don't like that you have to reply to them to decrypt and
> read them.  In elm, I have a script which will test to see if input is
> encrypted, and decrypt it prior to viewing if it is.  I'd like to fully switch
> to pine, but the lack of support for external pagers is the only thing holding
> me back.  Does anyone know of a hack anywhere that adds this support?
> Otherwise it's off to the pine source code with an axe I go...  :-)  Thanks in
> advance!
> 
> 
> 
> 
> 
> 
> 
> -matt
> 
> 
> -- 
> Matthew C. Mead -- System/Network Administration, User Support, Software Devel.
> Virginia Tech Center for Transportation Research
> Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com
> WWW: http://www.goof.com:/~mmead
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:53:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21774;
	Sat, 28 Jan 95 23:53:37 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06390;
	Sat, 28 Jan 95 23:50:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06384;
	Sat, 28 Jan 95 23:50:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU87-0003ARC; Sat, 28 Jan 95 23:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [ killfile ]
Date: Sat, 21 Jan 1995 14:51:11 -0800
Message-Id: <Pine.ULT.3.92.950121145037.22172I-100000@shiva2.cac.washington.edu>
References: <3eqd71$hgt@xcalibur.IntNet.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3eqd71$hgt@xcalibur.IntNet.net> 


Pine does not currently support killfiles.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 8 Jan 1995, Jonathan Cooper wrote:

> Date: 8 JAN 1995 23:14:25 -0500 
> From: Jonathan Cooper <entropy@news.IntNet.net>
> Newgroups: comp.mail.pine
> Subject: [ killfile ] 
> 
> How would I kill all mail that comes from a certain address using
> pine itself?  Does pine support killfiles?
> 
> Yes, I know I could just make a procmail recipe, but I'd like to
> use just pine.
> 
> -jon
> -- 
> ( --------[ Jonathan D. Cooper ]--------[ entropy@intnet.net ]-------- )
> ( PGP 2.6.2 keyprint: 31 50 8F 82 B9 79 ED C4  5B 12 A0 35 E0 9B C0 01 )
> ( home page: http://taz.hyperreal.com/~entropy/ ]---[ Key-ID: 4082CCB5 )
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:53:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21795;
	Sat, 28 Jan 95 23:53:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04270;
	Sat, 28 Jan 95 23:50:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04258;
	Sat, 28 Jan 95 23:50:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU7n-0003AQC; Sat, 28 Jan 95 23:32 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: why not bounce in Apply?
Date: Fri, 20 Jan 1995 16:27:45 -0800
Message-Id: <Pine.ULT.3.92.950120162735.22534n-100000@shiva1.cac.washington.edu>
References: <puchoD2AEvE.9F1@netcom.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <puchoD2AEvE.9F1@netcom.com> 


It is on our to-do list to add...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 12 Jan 1995, Marcos Rubinstein wrote:

> Date: Thu, 12 JAN 1995 10:09:14 GMT 
> From: Marcos Rubinstein <pucho@netcom.com>
> Newgroups: comp.mail.pine
> Subject: why not bounce in Apply? 
> 
> Is there any reason why you didn't include bounce in Apply?...
> 
> sometimes I bounce several messages from a mail-list to a friend, and for 
> her it's better to receive them as individual pieces of mail than as 
> attachements...
> 
> or did I miss something?
> 
> BTW.... thanks for pine... I do help a lot of people to deal with their 
> mail... and pine, by far, is the easiest to learn and use...
> 
> Pucho
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:53:45 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21801;
	Sat, 28 Jan 95 23:53:45 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04278;
	Sat, 28 Jan 95 23:50:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04272;
	Sat, 28 Jan 95 23:50:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU8i-0003ATC; Sat, 28 Jan 95 23:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: attachments
Date: Mon, 23 Jan 1995 14:12:30 -0800
Message-Id: <Pine.ULT.3.92.950123141105.22930D-100000@shiva1.cac.washington.edu>
References: <Pine.SOL.3.91.950116125705.5703A-100000@explorer>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SOL.3.91.950116125705.5703A-100000@explorer> 


Are you using PC-Pine or telnetting to your Solaris account and using Unix
Pine?  If the latter, you need to ftp the file over to your Unix account
first... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Mon, 16 Jan 1995, Cuauhtemoc wrote:

> Date: Mon, 16 JAN 1995 17:58:19 GMT 
> From: Cuauhtemoc <gonzales@clark.net>
> Newgroups: comp.mail.pine
> Subject: attachments 
> 
> 	Pine,
> 		I have a slip account with a local Internet access 
> provider and would like to attach a document from my a:drive to an email 
> message using pine.  I can't seem to get it to work.  Is it possible?  
> 
> Thanks
> 
> 
> Enrique Gonzales
> 
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21837;
	Sat, 28 Jan 95 23:54:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06406;
	Sat, 28 Jan 95 23:50:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06400;
	Sat, 28 Jan 95 23:50:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU8x-0003AVC; Sat, 28 Jan 95 23:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: HELP....
Date: Mon, 23 Jan 1995 14:20:53 -0800
Message-Id: <Pine.ULT.3.92.950123141959.22930F-100000@shiva1.cac.washington.edu>
References: <3fpm0t$hnd@reznor.larc.nasa.gov>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fpm0t$hnd@reznor.larc.nasa.gov> 


Use
	inbox-path={fennel.cs.hamptonu.edu}INBOX

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 21 Jan 1995, ICASE System Administrator wrote:

> Date: 21 JAN 1995 00:54:53 GMT 
> From: ICASE System Administrator <icaseadm@icase.edu>
> Newgroups: comp.mail.pine
> Subject: HELP.... 
> 
> I am in the process of installing Pine 3.91 on our Sun systems as well as the PC network
> using windows.  I *think* the software has been installed correctly on the sun's as I am
> able to read/send mail without any problems...
> The PC's for some reason are not working...when I try to run pine from one of the PC's, the
> INBOX does not get opened...I am aware that the pinerc has to be changed...I am not sure as
> to what entry I need to put for the INBOX...
> our server name: fennel.cs.hamptonu.edu
> smtp-server: fennel.cs.hamptonu.edu
> imap server: fennel.cs.hamptonu.edu
> 
> this is the entry in the pinerc file currently: inbox-path=/var/spool/mail/$USER  (SUN'S)
> PC's: inbox-path={fennel.cs.hamptonu.edu}/var/spool/mail --- I know this entry is incorrect..
> 
> Any help will be greatly appreciated..... PLEASE EMAIL DIRECTLY TO ME AT:
> tm@cs.hamptonu.edu 
> 
> thanking you in advance.....
> 
> tm@cs.hamptonu.edu  PLEASE DONT POST TO THIS NEWSGROUP...email to me..
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21839;
	Sat, 28 Jan 95 23:54:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04294;
	Sat, 28 Jan 95 23:50:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04288;
	Sat, 28 Jan 95 23:50:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU92-0003AWC; Sat, 28 Jan 95 23:34 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Mailing list with Pine?
Date: Tue, 24 Jan 1995 14:17:45 -0800
Message-Id: <Pine.ULT.3.92.950124141716.22930c-100000@shiva1.cac.washington.edu>
References: <3g2loj$ch3@tethys.otol.fi>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g2loj$ch3@tethys.otol.fi> 


The best way to do this is to upgrade to Pine 3.91 which allows global 
and shared addressbooks.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 24 Jan 1995, PeTrI pIeTiKaInEn wrote:

> Date: 24 JAN 1995 10:45:39 GMT 
> From: PeTrI pIeTiKaInEn <tecnic@tlti.tokem.fi>
> Newgroups: comp.mail.pine
> Subject: Mailing list with Pine? 
> 
> I was wondering is it possible to create a mailing list with Pine, where 
> everyone in the list can mail? I mean I created a list for our demo group 
> with address books command S CreateList... but I don't know how other 
> members could mail into it?
> 
> We have Pine v.3.87 
> 
> I hope someone could help us? Thanks in advance
> 
> --
> 
> Jay FX - member of BlacKOuT and Bitch Control  	: Be merry
> email:	tecnic@tlti.tokem.fi			:    Be bright...
> IRC:	JayFx					: - Carbon D
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21879;
	Sat, 28 Jan 95 23:54:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04304;
	Sat, 28 Jan 95 23:50:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04298;
	Sat, 28 Jan 95 23:50:58 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU9M-0003AZC; Sat, 28 Jan 95 23:34 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: Wed, 25 Jan 1995 10:02:25 -0800
Message-Id: <Pine.ULT.3.92.950125095928.10586H-100000@shiva1.cac.washington.edu>
References: <3g4bkq$49c@cronkite.ocis.temple.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g4bkq$49c@cronkite.ocis.temple.edu> 


On 25 Jan 1995, Wet-Sprocket wrote:

> Date: 25 JAN 1995 02:05:14 GMT 
> From: Wet-Sprocket <shrim@worf.ocis.temple.edu>
> Newgroups: comp.mail.pine
> Subject: Re: [Q] pine-debug* files -- Make it *STOP* 
> 
[...]
>         #define NUMDEBUGFILES 4
> 
> You can also re-define the number of debug files pine produces.
> 

FYI, we are investigating setting this to 0 in future releases.  Doing so in
Pine 3.91, you will not get any .pine-debug files saved, but you will
(should) get a .pine-crash if Pine crashes....

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21907;
	Sat, 28 Jan 95 23:54:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04341;
	Sat, 28 Jan 95 23:51:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04335;
	Sat, 28 Jan 95 23:51:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYUAf-0003AgC; Sat, 28 Jan 95 23:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Deletion of empty folders
Date: Thu, 26 Jan 1995 11:16:44 -0800
Message-Id: <Pine.ULT.3.92.950126111622.22930R-100000@shiva1.cac.washington.edu>
References: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl> 


Pine does not have an option to auto-delete empty folders...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Thu, 26 Jan 1995, Karel Kubat wrote:

> Date: Thu, 26 JAN 1995 07:24:08 GMT 
> From: Karel Kubat <karel@bambix.icce.rug.nl>
> Newgroups: comp.mail.pine
> Subject: Deletion of empty folders 
> 
> I am afraid that I'm missing something quite obvious (but I failed to find a
> pointer in the setup menus). I at times keep mail around in temporary folders,
> 'till I get around to answering it. Then I remove the mail from the temp
> folder.
> 
> How do I get Pine to automatically remove empty folders? Or do I really have
> to run say an external shellscript to accomplish this?
> 
> Thanx in advance.. please reply by E-mail too, I might miss an answer.
> --
> Karel Kubat (karel@icce.rug.nl, karel@bambix.icce.rug.nl).
> From the Obscure Dictionary of Medical Terms:
> Lymph: A special Fairy.
> 
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21911;
	Sat, 28 Jan 95 23:54:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06398;
	Sat, 28 Jan 95 23:50:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06392;
	Sat, 28 Jan 95 23:50:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU8M-0003ASC; Sat, 28 Jan 95 23:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: AIX Pine v3.9?
Date: Mon, 23 Jan 1995 13:56:55 -0800
Message-Id: <Pine.ULT.3.92.950123135519.22930C-100000@shiva1.cac.washington.edu>
References: <3fdcj2$nrv@lastactionhero.rs.itd.umich.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fdcj2$nrv@lastactionhero.rs.itd.umich.edu> 


A pre-compiled binary of Pine 3.91 for AIX 3.2 is available in

	ftp://ftp.cac.washington.edu/pine/unix-bin/pine-bin.a32

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 16 Jan 1995, Dennis Cheng wrote:

> Date: 16 JAN 1995 09:00:18 GMT 
> From: Dennis Cheng <chengman@umich.edu>
> Newgroups: comp.mail.pine
> Subject: AIX Pine v3.9? 
> 
> 
> Is Pine v 3.9 or 3.91 out and compiled for AIX yet?
> 
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21916;
	Sat, 28 Jan 95 23:54:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06451;
	Sat, 28 Jan 95 23:51:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06445;
	Sat, 28 Jan 95 23:51:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYUA7-0003AcC; Sat, 28 Jan 95 23:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Re-Sending EMail??
Date: Thu, 26 Jan 1995 08:58:14 -0800
Message-Id: <Pine.ULT.3.92.950126085702.8795E-100000@shiva1.cac.washington.edu>
References: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net> <Pine.SOL.3.91.950126012119.29923C-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SOL.3.91.950126012119.29923C-100000@hobbes> 


On 25 Jan 1995, Ed Greshko wrote:

> Date: 25 JAN 1995 09:55:25 -0800 
> From: Ed Greshko <Edward.M.Greshko@cdc.com>
> Newgroups: comp.mail.pine
> Subject: Re: Re-Sending EMail?? 
> 
> On Wed, 25 Jan 1995, Dan Mullen wrote:
> 
> > What Pine command do I use to resend a previously sent message
> > that has been returned due to Wrong Address or Server Error?
> > 
> > This has happened a couple ot times and had to retype the whole message 
> > again. Suggestion Please!!
> 
> 	Go to your "sent-mail" folder and "F"orward the message to the
> proper address.
> 

Or Bounce the message from sent-mail, or save it to postponed-msgs and resume
the composition... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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 owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21955;
	Sat, 28 Jan 95 23:54:34 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06414;
	Sat, 28 Jan 95 23:50:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06408;
	Sat, 28 Jan 95 23:50:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU97-0003AYC; Sat, 28 Jan 95 23:34 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Where src for HP ?
Date: Tue, 24 Jan 1995 14:33:43 -0800
Message-Id: <Pine.ULT.3.92.950124143236.22928H-100000@shiva1.cac.washington.edu>
References: <3g2ht4$6gg@pippo.sm.dsi.unimi.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g2ht4$6gg@pippo.sm.dsi.unimi.it> 


The current Pine 3.91 release includes an "hpp" port for HP/UX.  There 
are also pre-compiled binaries available.  Both can be found on 
ftp.cac.washington.edu in the pine directory.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 24 Jan 1995, Stefano Pisati IW2JXK wrote:

> Date: 24 JAN 1995 10:39:48 +0100 
> From: Stefano Pisati IW2JXK <pisati@pippo.sm.dsi.unimi.it>
> Newgroups: comp.mail.pine
> Subject: Where src for HP ? 
> 
> I need to compile Pine on a HP-UX server and I need the source
> ported to HP-UX... I've only found src and makefile only for
> other plataform. Where can I find src for HP ???
> 
> 		  Tnx in advance !!!
> 
>                     73 de -_ Stefano _-
> 
> PS: Please, reply via e-mail. Tnx !!!
> 
> 
>        "Stat rosa pristina nomine nomina nuda tenemus"
> ----------------------------------------------------------------
> Stefano Pisati  IW2JXK          Internet: pisati@dsi.unimi.it
> PGP:  finger pisati@ghost.dsi.unimi.it  or
>       e-mail pgp@dsi.unimi.it with Subject: GET Pisati
>      http://www.dsi.unimi.it/Users/Students/pisati/home
> ----------------------------------------------------------------
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21982;
	Sat, 28 Jan 95 23:54:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06461;
	Sat, 28 Jan 95 23:51:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06455;
	Sat, 28 Jan 95 23:51:09 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYUAL-0003AeC; Sat, 28 Jan 95 23:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: some news folders disapper !! HELP
Date: Thu, 26 Jan 1995 09:05:41 -0800
Message-Id: <Pine.ULT.3.92.950126090358.8795F-100000@shiva1.cac.washington.edu>
References: <Pine.SUN.3.90.950125232938.14792A-100000-100000-100000@trabzon>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.90.950125232938.14792A-100000-100000-100000@trabzon> 


This may be a problem with the Pine 3.90 release you are using.  Upgrade to
Pine 3.91 and it should work better... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Wed, 25 Jan 1995, Arcin Bozkurt wrote:

> Date: Wed, 25 JAN 1995 23:53:02 +0300 (EET) 
> From: Arcin Bozkurt <arcin@ug.bcc.bilkent.edu.tr>
> Newgroups: comp.mail.pine
> Subject: some news folders disapper !! HELP 
> 
> 
> 
> 	Hi,all !!
> 	I am using Pine 3.90 and I have a problem with my news folders.
> The problem is that my folders disappear after i read another folder.
> Strange isn't it ?
> 	Here is the story ...
> 	I am at the moment subscribed to comp.mail.pine and 
> comp.mail.misc. In another pine window i subscribed to sci.space read two 
> news there and deleted those two news i read. Then i pressed L to turn 
> back to folder list.
> 	What do you i see at the window? Only sci.space!! The other two 
> folders are lost. I happens all the time and i do not the way out.
> 	I also looked at my .newsrc file. It only contains the following 
> after the operation :
> 
> sci.space:
> 
> 	Can anyone with this peculiar behaviour of Pine 3.90.
> 	Thank you very much in advance .
> 
> 					Arcin Bozkurt
> 					Bilkent University
> 					EE - Junior
> 
> 
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22000;
	Sat, 28 Jan 95 23:54:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04333;
	Sat, 28 Jan 95 23:51:03 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04327;
	Sat, 28 Jan 95 23:51:02 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU9w-0003AbC; Sat, 28 Jan 95 23:34 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: NG: Where is pine for term?
Date: Thu, 26 Jan 1995 08:53:10 -0800
Message-Id: <Pine.ULT.3.92.950126085156.8795C-100000@shiva1.cac.washington.edu>
References: <3g6snf$h9t@alfa.ist.utl.pt>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g6snf$h9t@alfa.ist.utl.pt> 


I very briefly used Pine with term some time ago.  It seemed to work
reasonably well without modification.... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 26 Jan 1995, Nuno Filipe M M Godinho wrote:

> Date: 26 JAN 1995 01:09:03 GMT 
> From: Nuno Filipe M M Godinho <l36867@ci.ist.utl.pt>
> Newgroups: comp.mail.pine
> Subject: NG: Where is pine for term? 
> 
> Hi.
> Is there any version of pine for term? (the linux modem multiplexer)
> I mean, there is tMosaic, tlynx, tncftp...
> Do you know of any tpine available?
> 
> thanks
> 
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22021;
	Sat, 28 Jan 95 23:54:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04349;
	Sat, 28 Jan 95 23:51:13 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04343;
	Sat, 28 Jan 95 23:51:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYUAQ-0003AfC; Sat, 28 Jan 95 23:35 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Bug Report: Addressbook - pine
Date: Thu, 26 Jan 1995 09:07:49 -0800
Message-Id: <Pine.ULT.3.92.950126090648.8795G-100000@shiva1.cac.washington.edu>
References: <Pine.ULT.3.90.950126101259.23649A-100000@psws.uia.ac.be>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.ULT.3.90.950126101259.23649A-100000@psws.uia.ac.be> 


Pine 3.90 has several very serious bugs in the addressbook handling 
code.  These are fixed in the current Pine 3.91 release.  Upgrade!

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 26 Jan 1995, Bertel.DeGroote wrote:

> Date: 26 JAN 1995 01:11:40 -0800 
> From: Bertel.DeGroote <dgroote@psws.uia.ac.be>
> Newgroups: comp.mail.pine
> Subject: Bug Report: Addressbook - pine 
> 
> 
> Hallo,
> 
> I tried to create an Adressbook and to take the the adresses out of the 
> messages I received and put them in the Adressbook.
> 
> When I try  usin, updatin, renaming the Adressbook or I want to correct 
> the adresses/names, I somehow create problems.
> 
> I can't open the Adressbook
> 
> and the application blocks.
> 
> On my screen I See : Adressbook changed by another process re-syncing
> 		
> 		     Resetting Adress.book
> 	
> And I have to reset the computer (warm .start)
> 
> Can you help me and send me also some easy understandable step by 
> step information -while I'm not acquainted with computers- relating to the 
> use of the Adressbook.
> 
> Thank you in advance for your benevolent help.
> 
> 
> 
> Bertel De Groote
> 
> dgroote@uia.ac.be
> 
> 
> 
> 			  


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22044;
	Sat, 28 Jan 95 23:54:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06434;
	Sat, 28 Jan 95 23:51:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06416;
	Sat, 28 Jan 95 23:50:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU9n-0003AaC; Sat, 28 Jan 95 23:34 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: What do I do once I download pico?
Date: Wed, 25 Jan 1995 10:57:04 -0800
Message-Id: <Pine.ULT.3.92.950125105544.22930g-100000@shiva1.cac.washington.edu>
References: <3g3rbc$ke1@nic-nac.CSU.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g3rbc$ke1@nic-nac.CSU.net> 


Rename it, move it to the appropriate bin directory and mark it 
executable, i.e.

	mv pico-bin.hpux9 /usr/local/bin/pico
	chmod +x /usr/local/bin/pico

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 24 Jan 1995, Micheal Wojciechowski wrote:

> Date: 24 JAN 1995 21:27:08 GMT 
> From: Micheal Wojciechowski <mike@newport.lib.ca.us>
> Newgroups: comp.mail.pine
> Subject: What do I do once I download pico? 
> 
> I downloaded the version for HP-UX9, because this is the operating system we
> are running, so now I have this file pico-bin.hpux9 and I don't know what 
> to do with it now.  I am not very unix literate, although I know it enoough 
> that I feel comfortable using it.  Any help would be appreciated. Thanks in 
> advance.
> 
> 
> Mike
> 
> 


From owner-pine-info@cac.washington.edu  Sat Jan 28 23:54:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22055;
	Sat, 28 Jan 95 23:54:51 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04286;
	Sat, 28 Jan 95 23:50:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04280;
	Sat, 28 Jan 95 23:50:48 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYU8t-0003AUC; Sat, 28 Jan 95 23:33 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: [Q] How can I include video attachments (.mpeg) ?
Date: Mon, 23 Jan 1995 14:19:04 -0800
Message-Id: <Pine.ULT.3.92.950123141749.22930E-100000@shiva1.cac.washington.edu>
References: <Pine.LNX.3.91.950120165657.5045A-100000@stoertebeker.zdv.uni-tuebingen.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.LNX.3.91.950120165657.5045A-100000@stoertebeker.zdv.uni-tuebingen.de> 


Pine does not currently recognize mpeg files, so it labels that
application/octet-stream.  Pine 3.92 wqill have support for a .mime-types
file, so you can add other attachment types... 

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Fri, 20 Jan 1995, Dierk Schwick wrote:

> Date: Fri, 20 JAN 1995 17:23:49 +0100 
> From: Dierk Schwick <zrnsc01@stoertebeker.zdv.uni-tuebingen.de>
> Newgroups: comp.mail.pine
> Subject: [Q] How can I include video attachments (.mpeg) ? 
> 
> I didn't find any answer in the FAQ's nor in documentations at
> http://www.cac.washington.edu:1180/pine/
> 
> therefore i ask here.
> 
> I want to know if and when how it's possible to include video animations
> in a normal email message with pine and have a look on them later on from 
> pine via external viewer.
> 
> When I try so have a look on the attachment it's impossible in Pine!
> Images will be shown via the image-viewer configuration in .pinerc or
> my .mailcap but .mpegs aren't recogneized. It looks like that they 
> are mime-coded as application and not as video.
> 
> Here an extract from my .mailcap:
> 
> # This maps MPEG video data to the viewer 'mpeg_play'.
> # (Mpeg_play is part of the MPEG distribution from The Berkeley Plateau
> # Research Group and is available via anonymous ftp from toe.cs.berkeley.edu.)
> video/mpeg; mpeg_play %s ; test=test -n "$DISPLAY"
> 
> # Type octet-stream (binary) data can be displayed as a hex dump before
> # you decide whether or not you want to save it to a file.  (Hd is just
> # a standard hex dump program.  You could use "od" if you don't have an
> # "hd".  Naive users may find the output from this entry confusing.)
> application/octet-stream; hd; copiousoutput; description="Hex dump of data"
> 
> There is no global mailcap only my personal here! And the global pine.conf
> looks like the personal (the viewers obviously)
> 
> INcluding postscript-files or images works really fine. When i want to 
> have a look on the attachments the external viewer (ghostview or xv) will
> be opened automatically from pine. So far so good, but why don't work my 
> animations?
> 
> I don't read ths conference regularly, therefore please post answers to my
> email address, too! 
> 
> Thanks a lot!
> 
> -- Dierk Schwick
> 
> ----------------------------------------------------------------------------
> Dierk Schwick                          |Tel.:               +49-7071-29-6957
>                                        |Fax :               +49-7071-29-5912
> Zentrum fuer Datenverarbeitung         |privat:               +49-7071-49813
> Universitaet Tuebingen                 |email: dschwick@zdv.uni-tuebingen.de
> ----------------------------------------------------------------------------
> 
> 


From owner-pine-info@cac.washington.edu  Sun Jan 29 00:34:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23040;
	Sun, 29 Jan 95 00:34:38 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06932;
	Sun, 29 Jan 95 00:28:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06926;
	Sun, 29 Jan 95 00:28:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYUki-0003ASC; Sun, 29 Jan 95 00:12 PST
To: pine-info@cac.washington.edu
From: tfore@st6000.sct.edu (Troy Fore)
Subject: Serious BUG in Pine???
Date: 29 Jan 1995 01:06:09 GMT
Message-Id: <3gepm2$fsb@news-feed-1.PeachNet.EDU>

Our SysAdmin was forced to remove access to Pine on our system, and to 
tell us to stop using our own copies.  According to him, when executed, Pine 
creates a ~2Meg temporary file in the /tmp directory.  However, it 
doesn't always delete this file when the user finishes.  Since the file's 
ownership is set to the mailer daemon, the user cannot manually delete this 
file.  After a while, the /tmp directory is filled with numerous ~2Meg 
files.  He said he's even tried the newest version of Pine, and this 
problem persisted.

I tried it out, to see if I could see what he was talking about.  My 
roommate ran Pine, then checked the /tmp directory, and there was a new
mailer daemon file, created about the time he executed Pine.  (It had some 
randomly generated name, like MX8AFJ or some such.)  He couldn't remove 
it, and it sat there unchanged for days.  *I* ran Pine, and looked for a 
temp file, but there wasn't one -- however, notably I didn't compose a 
message, whereas my roommate did.  {We haven't tried anything beyond this, 
because we don't want to provoke the ire of our SysAdmin.)

Anyone know what's going on??

               />
             \/<    /       Troy Fore
 -{\\\\<>\\\\(*)XXX<:::<=====================================================-
             /\<    \       tfore@st6000.sct.edu
               \>


From owner-pine-info@cac.washington.edu  Sun Jan 29 02:15:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25401;
	Sun, 29 Jan 95 02:15:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06169;
	Sun, 29 Jan 95 02:12:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06163;
	Sun, 29 Jan 95 02:12:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYWSv-00038OC; Sun, 29 Jan 95 02:02 PST
To: pine-info@cac.washington.edu
From: unger@raindrop.seaslug.org (Tom Unger)
Subject: Re: Pine for windows!
Date: Sun, 29 Jan 1995 06:16:36 GMT
Message-Id: <1995Jan29.061636.15603@raindrop.seaslug.org>
References: <3g8h10$qpb@serra.unipi.it>

In article <3g8h10$qpb@serra.unipi.it>,
Alessandro Agostini <agostini@iroe.fi.cnr.it> wrote:
>I hope that pine for windows i out in brief time.
>So, I'm interesting to receive the source of pine for try to convert it in a true window application.
>It is possible?

The PC-Pine source comes as part of the standard pine source
distribution.  However, we never intended for others to modify or
compile PC-Pine so you will pretty much be on your own in getting it
to compile.

As for converting to a true windows application -- of course it's
possible, it's just a matter of programming.  

Thomas Unger
Networks and Distributed Computing
University of Washington, Seattle




-- 
--  Tom Unger
    WWC



From owner-pine-info@cac.washington.edu  Sun Jan 29 02:53:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26228;
	Sun, 29 Jan 95 02:53:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08618;
	Sun, 29 Jan 95 02:48:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08612;
	Sun, 29 Jan 95 02:48:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYWwL-00038QC; Sun, 29 Jan 95 02:33 PST
To: pine-info@cac.washington.edu
From: kford@crash.cts.com (Kelly Ford)
Subject: Marking Multiple News posts Deleted
Date: Sun, 29 Jan 1995 08:26:15 GMT
Message-Id: <D35rFs.G2C@crash.cts.com>


Can anyone tell me how to mark multiple news messages as deleted with 
Pine 3.91.  I love the ability to jump from group to group with the Tab 
key but would like to know how to mark all the messages of a group as 
deleted before leaving the group.  I'd like to not have to press the "d" 
key multiple times to do this.




From owner-pine-info@cac.washington.edu  Sun Jan 29 03:00:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26422;
	Sun, 29 Jan 95 03:00:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08712;
	Sun, 29 Jan 95 02:58:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08706;
	Sun, 29 Jan 95 02:58:13 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYX6D-00038CC; Sun, 29 Jan 95 02:43 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Fcc:  interactive possible?
Date: 28 Jan 1995 16:52:35 GMT
Message-Id: <3gdsoj$nd7@cronkite.ocis.temple.edu>

I accidently wrote:

 +   Comes here Mr. Joyce Y. Wong with this opinion in the "comp.mail.pine"
 +   group in this article on 26 Jan 1995 16:46:31 -0800:

Apologies for accidently using Mr. when it should have been Mz.
Sorry about that.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Sun Jan 29 03:01:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26467;
	Sun, 29 Jan 95 03:01:23 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06650;
	Sun, 29 Jan 95 02:58:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06644;
	Sun, 29 Jan 95 02:58:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYX2f-00038SC; Sun, 29 Jan 95 02:39 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: HELP ME GET RID OF MY [17;3H's PLEASE!!!
Date: 28 Jan 1995 16:45:41 GMT
Message-Id: <3gdsbl$nd7@cronkite.ocis.temple.edu>

Comes here Mr. Ronald Blumer with this opinion in the "comp.mail.pine" group in
this article on 27 Jan 1995 21:29:18 -0500:

 +   The problem started a few days ago when I had to reconfig Procomm because 
 +   of a problem I am having. Now when ever I am in PINE or PICO I see these 
 +   strange things like [5;41H whenever I backspace use my arrow keys. Odd 
 +   things also keep happening on the very top and bottom lines of the 
 +   screen. Where I see bit of the text appearing. Sometimes as well the 
 +   cursor seems to get stuck on a line.  Everything clears up when I ^L 
 +   (refresh the screen.)

 +   Help I am seeing [20;12H's in my sleep.

On the face of it, it looks like you have to reset your modem's flow control.
Try setting XON/XOFF off. If that doesn't work, try positing to comp.*.modems
you probabaly will get better help than before. :-)

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Sun Jan 29 04:47:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29230;
	Sun, 29 Jan 95 04:47:05 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08138;
	Sun, 29 Jan 95 04:44:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08132;
	Sun, 29 Jan 95 04:44:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYYk4-00038KC; Sun, 29 Jan 95 04:28 PST
To: pine-info@cac.washington.edu
From: parastat@alpha.it.teithe.gr (Savas Parastatidis)
Subject: Re: Handling Return Receipts within PINE
Date: 28 Jan 1995 21:31:57 GMT
Message-Id: <3ged4d$pj1@kronos.it.teithe.gr>
References: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu>

Steve Lowe (slowe@admin.aurora.edu) wrote:

:...

: What I was hoping for was that the receipt would appear to have come from 
: the message reader, not the mailer-daemon.

:...

Steve, 

I think this is the way that sendmail works. At page 583 of the sendmail
handbook (by Bryan Costales) you can find a description for the receipt
header.

When sendmail finds that header in a message, it sends the receipt. It
does so just after the message is delivered. So the mail user agent
(pine in our case) isn't involved at all.

In my opinion, what you are looking for, is a mail user agent with a X- 
(user defined header) to do your work. Sendmail ignores such headers.
It passes such headers to the user agent as they are. Does anyone know a
user agent supporting a feature like this? Or, does pine support this 
feature?

Savas.

--
          ___
        _|___|_   /--------\
         /o o\   | It's me! |
        |  +  | / \--------/
         \ ~ /
+-----oooO---Oooo-----+  +--------------------------------------+
|.Savas  Parastatidis.|--| TEI of Thessaloniki, GREECE          |
|parastat@it.teithe.gr|--| Department of Information Technology |
+---------------------+  +--------------------------------------+


From owner-pine-info@cac.washington.edu  Sun Jan 29 05:46:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00410;
	Sun, 29 Jan 95 05:46:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10836;
	Sun, 29 Jan 95 05:43:33 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10830;
	Sun, 29 Jan 95 05:43:31 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYZgf-00038MC; Sun, 29 Jan 95 05:29 PST
To: pine-info@cac.washington.edu
From: root@wndrsvr.la.ca.us (Master of Wonder)
Subject: Pine and fax?
Message-Id: <D34roz.5GF@wndrsvr.la.ca.us>
Date: Sat, 28 Jan 1995 19:34:09 GMT


Does or will Pine display fax files?  I'd love to have that...
3.90 doesn't seem to understand them...

Thanks!

-  Andy 


From owner-pine-info@cac.washington.edu  Sun Jan 29 05:52:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00508;
	Sun, 29 Jan 95 05:52:40 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08849;
	Sun, 29 Jan 95 05:50:10 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08843;
	Sun, 29 Jan 95 05:50:08 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYZmI-00038OC; Sun, 29 Jan 95 05:34 PST
To: pine-info@cac.washington.edu
From: hirshaut@yu1.yu.edu
Subject: Printing Pine Messages
Message-Id: <Pine.A32.3.91.950122220907.29370A-100000@yu1.yu.edu>
Date: 23 Jan 95 03:16:04 GMT
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I am using a Lynx 125 terminal (in the VT100 emulation mode) to connect 
to an AIX version of pine.  I have a NEC Pinwriter P5XL printer attached 
to the terminal via a parallel port.  While using a similar setup permits 
me to print successfully from a CD-ROM based Medline system at our 
hospital's library, it does not seem to respond properly either to the 
PC or lprint mode of printing from pine.  Without buying a home computer 
and a communication package, is there any way of printing directly in 
this terminal-parallel printer configuration from pine?

Your reply is much appreciated.  










From owner-pine-info@cac.washington.edu  Sun Jan 29 08:15:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02869;
	Sun, 29 Jan 95 08:15:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12587;
	Sun, 29 Jan 95 08:12:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12581;
	Sun, 29 Jan 95 08:12:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYbxx-00038RC; Sun, 29 Jan 95 07:55 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: 29 Jan 95 15:54:58 GMT
Message-Id: <ellis.791394898@gmi.edu>
References: <3g4bkq$49c@cronkite.ocis.temple.edu> <Pine.ULT.3.92.950125095928.10586H-100000@shiva1.cac.washington.edu>

David L Miller <dlm@cac.washington.edu> writes:


 >On 25 Jan 1995, Wet-Sprocket wrote:

 >> Date: 25 JAN 1995 02:05:14 GMT 
 >> From: Wet-Sprocket <shrim@worf.ocis.temple.edu>
 >> Newgroups: comp.mail.pine
 >> Subject: Re: [Q] pine-debug* files -- Make it *STOP* 
 >> 
 >[...]
 >>         #define NUMDEBUGFILES 4
 >> 
 >> You can also re-define the number of debug files pine produces.
 >> 

 >FYI, we are investigating setting this to 0 in future releases.  Doing so in
 >Pine 3.91, you will not get any .pine-debug files saved, but you will
 >(should) get a .pine-crash if Pine crashes....

For those cases where there are problems, are you planning on having a
-debug commandline flag?

 >|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Sun Jan 29 08:32:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03130;
	Sun, 29 Jan 95 08:32:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10639;
	Sun, 29 Jan 95 08:29:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10633;
	Sun, 29 Jan 95 08:29:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcI5-00038RC; Sun, 29 Jan 95 08:15 PST
To: pine-info@cac.washington.edu
From: kehres@hk.net (Tim Kehres)
Subject: Re: pine to cc:Mail
Date: 29 Jan 1995 15:56:48 GMT
Message-Id: <3ggds0$brs@news.hk.net>
References: <3g1pbc$ams@raffles.technet.sg> <3ge7ps$21q@little-miami.iac.net>

In article <3ge7ps$21q@little-miami.iac.net>,
Carl Jolley <cjolley@iac.net> wrote:
>A company called Internation Messaging Associates has a product called
>Internet Exchange that supports Mime. email: sales@ima.com
> 
>The last time I tried to e-mail them, I wasn't able to get through.
>When I called them, they said that their ISP had messed them up.
>If you need their phone number, send me e-mail.

Yes, in early January, Netcom, which is currently handling our DNS 
entries for us, made a real mess out of things, resulting in total mail
loss for approximately 3 days.  Needless to say, we're working on 
changing this situation so that their apparent sloppy administration 
doesn't burn us again.

If you in North America, our North American distributor, IMA Technologies
can be contacted at the following numbers:

Tel: +1 (415) 871-4045
Fax: +1 (415) 871-7392

All other inquires should be sent directly to us in Hong Kong at the
following numbers:

Tel: +852 2649-0135
Fax: +852 2648-5913

Email inquiries can be sent to either info@ima.com or sales@ima.com.

Best Regards,

Tim Kehres
International Messaging Associates Ltd


From owner-pine-info@cac.washington.edu  Sun Jan 29 08:32:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03138;
	Sun, 29 Jan 95 08:32:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12772;
	Sun, 29 Jan 95 08:29:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12766;
	Sun, 29 Jan 95 08:29:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcFG-00038QC; Sun, 29 Jan 95 08:12 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Marking Multiple News posts Deleted
Date: 29 Jan 95 16:16:16 GMT
Message-Id: <ellis.791396176@gmi.edu>
References: <D35rFs.G2C@crash.cts.com>

kford@crash.cts.com (Kelly Ford) writes:


 >Can anyone tell me how to mark multiple news messages as deleted with 
 >Pine 3.91.  I love the ability to jump from group to group with the Tab 
 >key but would like to know how to mark all the messages of a group as 
 >deleted before leaving the group.  I'd like to not have to press the "d" 
 >key multiple times to do this.


Look at the select (;) and (a)pply commands.



-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Sun Jan 29 08:32:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03161;
	Sun, 29 Jan 95 08:32:48 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10631;
	Sun, 29 Jan 95 08:29:16 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10625;
	Sun, 29 Jan 95 08:29:15 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcCr-00038WC; Sun, 29 Jan 95 08:10 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: e-mail addresses
Date: 29 Jan 95 16:05:28 GMT
Message-Id: <ellis.791395528@gmi.edu>
References: <3gdr2r$nd7@cronkite.ocis.temple.edu>

shrim@worf.ocis.temple.edu (Wet-Sprocket) writes:

 >Comes here Mr. Brad with this opinion in the "comp.mail.pine" group in this
 >article on Fri, 27 Jan 1995 19:54:51 +0000:

 > +   	Could someone who knows more than I about non-Internet e-mail
 > +   translate this address into something I could use: 

 > +   	cso-unix!dbradley%c6@cso2.uucp@britain.eu.net

I haven't hacked sendmail.cf for a couple of years, but I am not sure most
rule sets will be able to handle this.  Most people have been throwing bang
addresses on the floor for several years.  I also think having two 'ats' will
be confusing.  The first chore is to get it to britain.eu.net, which needs
to be at the right following and @.  Then it looks like the next machine to
get it to is cso2.uucp.  Therefore cso2.uucp@britain.eu.net should be OK.  I
believe the rest of the address should be with %'s.  Therefore

  dbradley%cso-unix%c6%cso2.uucp@britain.eu.net

MIGHT get there.

It would be a lot easier if everyone was at a registered domain, hiding
behind a chain of MX records.

 >That will be the form of the e-mail address, from such sites which don't
 >have direct internet connection, instead use UUCP or other mail routers.
 >Usually replying to such addressess will work but with a delivery lag.

 >--
 >---.                                ,    ,
 >\___                                ("\''/").___..--''"`-._
 >    \                                `9_ 9  )   `-.  (     ).`-.__.`)
 >`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
 >Computer Svcs                      _..`--'_..-_/  /--'_.' .
 >Temple Univ.                      (il).-''  ((i).'  ((!.-'
 >__________________________________________________________________________


-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Sun Jan 29 08:35:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03231;
	Sun, 29 Jan 95 08:35:59 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10703;
	Sun, 29 Jan 95 08:32:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from pennet.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10697;
	Sun, 29 Jan 95 08:32:56 -0800
Received:  by pennet.com (5.65/1.2-eef)
	id AA09002; Sun, 29 Jan 95 11:31:38 -0500
Date: Sun, 29 Jan 1995 11:31:38 -0500 (EST)
From: Chuck Baugh <crbaugh@pennet.com>
To: pine-info@cac.washington.edu
Message-Id: <Pine.SCO.3.91.950129113118.8998A-100000@pennet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

unsubscribe



From owner-pine-info@cac.washington.edu  Sun Jan 29 08:59:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03741;
	Sun, 29 Jan 95 08:59:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10997;
	Sun, 29 Jan 95 08:57:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10985;
	Sun, 29 Jan 95 08:57:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcgk-00038RC; Sun, 29 Jan 95 08:41 PST
To: pine-info@cac.washington.edu
From: jdulaney@crl.com (John Dulaney)
Subject: Loop prog. staggers mail but needs help, please
Date: 29 Jan 1995 16:31:46 GMT
Message-Id: <3ggfti$1pi@nntp.crl.com>

	I have a prog. that sends E-mails to my distrib. list one at a
time so as not to clog the system BUT....
	1) It also sends E-mail to the nickname and the fullname as well 
as the address so the wrong people are getting my mail and are POed about 
it (how? If the only fullname I have for someone is "Paul", say, it sends 
my file to Paul@crl.com by default). How can I get the prog. to send mail 
only to the line with the @ sign in it? Can't be the 3rd section of each 
line as some line have no fullname name at all and therefore only 2 parts.
	2) After sending 500 e-mails my access provider times out and 
logs me off.
	What can I do to produce the odd action so I'm not timed off?
	Thanks for all help. It is MUCH appreciated! Best, John in Concord, Cal.

* * * * * * * * * * ** * * * * * * * * * * * * * * * * * * * * * * * * *
*FREE shareware & ICONS & CD-ROM disks/hardware/PAL/SECAM video catalog*
*at my WWW HOME PAGE http://xmission.com/~wwwads/mind/logic.html Or ask*
*for E-mailed catalog as text, zipped, UUEncoded. OR get catalog + more*
*from our ftp site: xmission.com /pub/users/wwwads/logic.zip WORLDWIDE *
*SHIPPING VISA/MC/AMEX Wholesale/Retail jdulaney@crl.com - A nice guy  *
*in California. WIN $500 (Canad.) vote 4 UR fav. URL! E-mail 4 details *
*Plug for friend:Blind or seeing impaired? Ask for a free Scatalog.exe *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 


From owner-pine-info@cac.washington.edu  Sun Jan 29 09:00:23 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03765;
	Sun, 29 Jan 95 09:00:23 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13131;
	Sun, 29 Jan 95 08:57:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13125;
	Sun, 29 Jan 95 08:57:46 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcfA-00038QC; Sun, 29 Jan 95 08:39 PST
To: pine-info@cac.washington.edu
From: gsutter@gss115.rh.psu.edu (Gregory S. Sutter)
Subject: Pine and Reply-To: environment var
Date: 29 Jan 1995 03:59:32 GMT
Message-Id: <3gf3r4$tas@hearst.cac.psu.edu>

Is there a way to get Pine 3.91 to read my environment variable 'Reply-To'?
I have been manually inserting the Reply-To line in _each_ letter I write, 
and it is gettting quite annoying.

Pine 3.91, Linux 1.1.85, bash.

Please reply by email.

Thanks --

Greg
--
Gregory S. Sutter    gsutter@psu.edu    http://gss115.rh.psu.edu/~gsutter
GCS/E d H- s+: !g p? au- !a w+ v-(+) C++++ UL++++ P+ L++ 3- E--- N+ K+ r+ 
W---/!W M-- V-- -po+ Y+ t+ 5 j R G+++ tv-- b+++ D++ B--- e+(*) u+(*) h- f+ 
      I once tried to commit suicide by jumping off a building... I
     changed my mind at the last minute, so I just flipped over and
   landed on my feet. Two little kittens nearby saw what happened and
     one turned to the other and said, "See, that's how it's done."
:q :q :q! :wq :w! :wq! :quit :help help :helpquit quit quitnow :dammit ZZ 
:quitplease :quitnow :leave :shit ^X^C^Q^Q^Q QUITDAMMIT :grrrrr ^[:q


From owner-pine-info@cac.washington.edu  Sun Jan 29 09:00:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03794;
	Sun, 29 Jan 95 09:00:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13139;
	Sun, 29 Jan 95 08:57:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13133;
	Sun, 29 Jan 95 08:57:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcll-00038SC; Sun, 29 Jan 95 08:46 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Changing From: header
Date: Mon, 23 Jan 1995 09:22:15 +0000
Message-Id: <Pine.SUN.3.91.950123092105.26876C-100000@grus.cus.cam.ac.uk>
References: <Pine.OSF.3.91.950120111207.28526C-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.OSF.3.91.950120111207.28526C-100000@osfb.aber.ac.uk> 

On Fri, 20 Jan 1995, Brad wrote:

> 	Yep indeedy! You have to uncomment the following line in
> pine/osdep/os-xxx.h: 
> 
> /* #define ALLOW_CHANGING_FROM  /* comment out to not allow changing From */
> 
> Then you should be able to change your From address. However, I've never
> tried doing it via the Customized-hdrs... 
> 

Some of our customers have done this and it works fine.

> 
> On 18 Jan 1995, Nancy McGough wrote:
> 
> > I'd like to change the From: header in mail I send from Pine
> > by putting something like this in my .pinerc:
> > 
> > customized-hdrs=Organization: $ORGANIZATION,
> >         From: Nancy McGough <nancym@ii.com>
> > 

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Sun Jan 29 09:05:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03940;
	Sun, 29 Jan 95 09:05:08 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11067;
	Sun, 29 Jan 95 09:02:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11061;
	Sun, 29 Jan 95 09:02:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYcoT-00038PC; Sun, 29 Jan 95 08:49 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Pine for OS/2 (!)
Date: Mon, 23 Jan 1995 09:24:43 +0000
Message-Id: <Pine.SUN.3.91.950123092405.26876D-100000@grus.cus.cam.ac.uk>
References: <5f8_9501200953@dialis.xs4all.nl> <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org> 

On 20 Jan 1995, Brent Blumenstein wrote:

> Now that is good news.  When?  And are beta testers needed.  I volunteer.

I volunteer also.

> On 19 Jan 1995, Geert Bosch wrote:
> 
> > For those interested, I read that Steve Willer is currently porting the Pine
> > reader to OS/2. At least there are some developments now...
> > 

=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Sun Jan 29 09:30:08 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04449;
	Sun, 29 Jan 95 09:30:08 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13499;
	Sun, 29 Jan 95 09:27:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13493;
	Sun, 29 Jan 95 09:27:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYd7I-00038XC; Sun, 29 Jan 95 09:08 PST
To: pine-info@cac.washington.edu
From: Brad <syb3@aber.ac.uk>
Subject: e-mail addresses
Date: Fri, 27 Jan 1995 19:54:51 +0000
Message-Id: <Pine.OSF.3.91.950127195228.16118A-100000@osfb.aber.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

	Could someone who knows more than I about non-Internet e-mail
translate this address into something I could use: 

	cso-unix!dbradley%c6@cso2.uucp@britain.eu.net

	Many thanks to anyone who can help! 

 ___  _                     _a' /(   <.  Simon Bradley, Knight Protector!
/ __><_>._ _ _  ___ ._ _ ~~ _}\ \(  _  ) E-mail: syb3@aber.ac.uk
\__ \| || ' ' |/ . \| ' |      \(._(.)'  Finger: syb3@osfb.aber.ac.uk
<___/|_||_|_|_|\___/|_|_|     ._>. _>.   WWW: http://www.aber.ac.uk/~syb3/


From owner-pine-info@cac.washington.edu  Sun Jan 29 09:31:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04519;
	Sun, 29 Jan 95 09:31:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11351;
	Sun, 29 Jan 95 09:28:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from linknet.kitsap.lib.wa.us by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11345;
	Sun, 29 Jan 95 09:28:47 -0800
Received: (from michael@localhost) by linknet.kitsap.lib.wa.us (8.6.9/8.6.9) id JAA03980; Sun, 29 Jan 1995 09:26:51 -0800
Date: Sun, 29 Jan 1995 09:26:51 -0800 (PST)
From: Michael Schuyler <michael@linknet.kitsap.lib.wa.us>
To: pine-info@cac.washington.edu
Subject: screen clearing
Message-Id: <Pine.SUN.3.91.950129092039.3343K-100000@linknet.kitsap.lib.wa.us>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Out of 2500 users a few are reporting that when in Pine their screens 
won't clear. They wind up typing over previous screens or messages. It 
looks as if the messages themselves are okay, but, of course, it;s pretty 
difficult to type over old messages or menu screens. 

At first I thought this was a simple terminal emulation problem. Change 
to VT-100 and reboot. Then I thought it must be certain comm packages, 
like old Telix, that can't quite cut it. 

But upon investigation I can't find a common element. For some people it 
even happens with Procomm, our favorite around here. 

Anybody got a clue? I don't!

  :::::;     . ,             Michael Schuyler               ..,     `::::::
  :::;' /)  - * -    michael@linknet.kitsap.lib.wa.us      - + -  (\ `:::::
  ::'  / )   ':`  Kitsap Regional Library, 1301 Sylvan Way  ':`   ( \_ `  :
  :' _( (_    _     Bremerton, WA  98310 (360) 405-9139       _    ) )\ />:




From owner-pine-info@cac.washington.edu  Sun Jan 29 09:36:10 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04685;
	Sun, 29 Jan 95 09:36:10 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11447;
	Sun, 29 Jan 95 09:33:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11441;
	Sun, 29 Jan 95 09:32:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYdIR-00038PC; Sun, 29 Jan 95 09:20 PST
To: pine-info@cac.washington.edu
From: Rahul Dhesi <dhesi@rahul.net>
Subject: Re: Handling Return Receipts within PINE
Date: 23 Jan 1995 10:10:04 GMT
Message-Id: <3fvv9s$ivj@hustle.rahul.net>
References: <Pine.3.89.9501221046.A543209766-0100000@INNOSOFT.COM> <Pine.SUN.3.91.950122141406.22083C-100000@lab19.cs.purdue.edu>

In <Pine.SUN.3.91.950122141406.22083C-100000@lab19.cs.purdue.edu>
simmonmt@cs.purdue.edu (Matt Simmons) writes:

>How hard would it be to just have Pine start supporting read receipts?

It would cause a serious invasion of privacy, so it would ideally
be a user-settable option.
-- 
Rahul Dhesi <dhesi@rahul.net>


From owner-pine-info@cac.washington.edu  Sun Jan 29 11:18:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06541;
	Sun, 29 Jan 95 11:18:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12793;
	Sun, 29 Jan 95 11:15:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12787;
	Sun, 29 Jan 95 11:15:43 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA12240; Sun, 29 Jan 1995 14:15:21 +0500
Date: Sun, 29 Jan 1995 14:15:20 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: Re-Sending EMail??
In-Reply-To: <Pine.A32.3.90.950125030307.83502I-100000@seminole.gate.net>
Message-Id: <Pine.SOL.3.91.950129140713.12150B-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1142

On Wed, 25 Jan 1995, Dan Mullen wrote:

> What Pine command do I use to resend a previously sent message
> that has been returned due to Wrong Address or Server Error?
> 
> This has happened a couple ot times and had to retype the whole message 
> again. Suggestion Please!!
 
You got a _lot_ of suggestions on this one, all of them viable.  IMHO, 
going to your sent-mail folder, viewing the message, and forwarding it to 
the correct address is the least labor intensive.  Once you hit "f" for 
forward, Pine puts the message into a compose window where you can 
quickly enter the correct address, edit out the "(fwd)" appended to the 
subject (don't want it to be obvious that you goofed!), and edit out the 
original header stuff that now appears in the message text (same reason, 
plus all that extra junk will just annoy the recipient).

--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA



From owner-pine-info@cac.washington.edu  Sun Jan 29 12:22:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08002;
	Sun, 29 Jan 95 12:22:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13603;
	Sun, 29 Jan 95 12:18:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13597;
	Sun, 29 Jan 95 12:18:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYftY-00038QC; Sun, 29 Jan 95 12:06 PST
To: pine-info@cac.washington.edu
From: the mole <markusg@darkwing.uoregon.edu>
Subject: Re: Pine and Reply-To: environment var
Date: Sun, 29 Jan 1995 01:08:26 -0800
Message-Id: <Pine.SOL.3.91.950129005846.2056E-100000@darkwing>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3gf3r4$tas@hearst.cac.psu.edu> 

On 29 Jan 1995, Gregory S. Sutter wrote:

> Is there a way to get Pine 3.91 to read my environment variable 'Reply-To'?
> I have been manually inserting the Reply-To line in _each_ letter I write, 
> and it is gettting quite annoying.
> 
> Pine 3.91, Linux 1.1.85, bash.
> 
> Please reply by email.
> 
> Thanks --
> 
> Greg
> --
> Gregory S. Sutter    gsutter@psu.edu    http://gss115.rh.psu.edu/~gsutter
> [sig]

Under Setup/Config (Main Menu) at the 'default-composer-hdrs' option add
  Reply-To: gsutter@psu.edu   
and all other headers (without values) you wish to see. (Only 'From:' 
won't be shown in the composition mode, I wish it would - I like to 
change my real name once in a while without having to change the setup. 
Suggestions anybody?)

ll&p,

tm
--
      /               . . . . . . . . . . . . . . . . . . . . . . . . . . .
__  __/   __  __     . . . . . . . . . . . . . . . . . . . . . .  the mole
   /     /   /   /  . . . . . . . . . . . .  markusg@darkwing.uoregon.edu
__/   __/ __/ __/  . . . . . . . . http://darkwing.uoregon.edu/~markusg/





From owner-pine-info@cac.washington.edu  Sun Jan 29 12:29:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08077;
	Sun, 29 Jan 95 12:29:20 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15727;
	Sun, 29 Jan 95 12:26:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15721;
	Sun, 29 Jan 95 12:26:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYfwm-00038SC; Sun, 29 Jan 95 12:10 PST
To: pine-info@cac.washington.edu
From: sysop@mome-raths.iac.net (March Hare)
Subject: Re: Pine for OS/2 (!)
Message-Id: <2f22a733.4d4f4d45@mome-raths.iac.net>
Date: Sun, 22 Jan 1995 13:42:59 -0500
References: <5f8_9501200953@dialis.xs4all.nl> <Pine.A32.3.91.950120074333.49562B-100000@orca.fhcrc.org>

Brent Blumenstein (brentb@orca.fhcrc.org) wrote:
: Now that is good news.  When?  And are beta testers needed.  I volunteer.


: > For those interested, I read that Steve Willer is currently porting the Pine
: > reader to OS/2. At least there are some developments now...
: > 

Hi, I just got onto this list.  I'm told there is a general belief
that there's no interest in a Pine port for OS/2.  I'm here to
state that it's more likely that few OS/2 users know about this
newsgroup/mailing-list.

BTW - I picked up on the OS/2 groups that a port of pico is 
available ftp, which I'm using right now to write this message.
It works pretty well.  I'm planning on using it for accessing
UUCP news through my BBS.  Now, I just have to work out extracting
the user name, which shouldn't be too difficult.  Pico will be
ideal for this, since I don't have to worry about [Esc] or
function keys or any of that other junk that DOS & OS/2 programs
seem to rely on.

I also noticed in the docs that Pine was written with NNTP
in mind (please correct me if I read wrong).  Will it work
with UUCP (esp. UUPC from Clarkson)?

John

--
Mome Raths BBS                          General Pix, Adult Pix, Messages,
(513)523-7887                           DOS, Windows and OS/2 programs,
Oxford, Ohio                            12 Step echos and much more


From owner-pine-info@cac.washington.edu  Sun Jan 29 12:42:24 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08367;
	Sun, 29 Jan 95 12:42:24 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13885;
	Sun, 29 Jan 95 12:40:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13879;
	Sun, 29 Jan 95 12:39:55 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA12425; Sun, 29 Jan 1995 15:39:26 +0500
Date: Sun, 29 Jan 1995 15:39:25 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
In-Reply-To: <Pine.ULT.3.92.950125095928.10586H-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SOL.3.91.950129153723.12306B@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 693

On Wed, 25 Jan 1995, David L Miller wrote:

> > You can also re-define the number of debug files pine produces.
> 
> FYI, we are investigating setting this to 0 in future releases.  Doing so in
> Pine 3.91, you will not get any .pine-debug files saved, but you will
> (should) get a .pine-crash if Pine crashes....
 
Why not make it user-configurable in .pinerc (via Setup in the Main Menu)?
 
--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA




From owner-pine-info@cac.washington.edu  Sun Jan 29 12:57:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08693;
	Sun, 29 Jan 95 12:57:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14045;
	Sun, 29 Jan 95 12:54:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from netcom13.netcom.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14039;
	Sun, 29 Jan 95 12:53:59 -0800
From: jinny@netcom.com
Received: by netcom13.netcom.com (8.6.9/Netcom)
	id MAA09398; Sun, 29 Jan 1995 12:52:56 -0800
Date: Sun, 29 Jan 1995 12:52:54 -0800 (PST)
Subject: 
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501291235.A8565-0100000@netcom13>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII






From owner-pine-info@cac.washington.edu  Sun Jan 29 13:41:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09590;
	Sun, 29 Jan 95 13:41:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16629;
	Sun, 29 Jan 95 13:38:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from ha11.eng.ua.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16623;
	Sun, 29 Jan 95 13:38:43 -0800
Received: by ha11.eng.ua.edu (AIX 3.2/UCB 5.64/4.03)
          id AA02785; Sun, 29 Jan 1995 15:34:00 -0600
Date: Sun, 29 Jan 1995 15:33:59 -0600 (CST)
From: "Michael E. Shmoulevich" <mshmoule@buster.eng.ua.edu>
To: pine-info@cac.washington.edu
Subject: Pine receipt return...
Message-Id: <Pine.A32.3.91.950129152854.15565B-100000-100000-100000@ha11.eng.ua.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


	Please, can anybody tell me how I can reqest receipt return in 
Pine? The version I'm using is 3.91 for Unix. 

	Thank you for attention.
	Misha.

[ My email addresses : 	mshmoule@buster.eng.ua.edu]
[			  mshmoule@bamaed.ua.edu  ]



From owner-pine-info@cac.washington.edu  Sun Jan 29 15:17:38 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11431;
	Sun, 29 Jan 95 15:17:38 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15904;
	Sun, 29 Jan 95 15:14:50 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15898;
	Sun, 29 Jan 95 15:14:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYidT-00038RC; Sun, 29 Jan 95 15:02 PST
To: pine-info@cac.washington.edu
From: the mole <markusg@darkwing.uoregon.edu>
Subject: Suggestion for Pine 3.9x: ';aad' in one Keystroke
Date: Sun, 29 Jan 1995 13:37:53 -0800
Message-Id: <Pine.SOL.3.91.950129132906.16131A-100000@darkwing>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi.

For me and probably for many others the sequence ';aad' (followed by TAB)
is the most commonly used (catching up all postings in one newsgroup and 
skipping to the next). It is also the answer to every other question 
posted comp.mail.pine. Why not dedicating *one* key to this (keeping the 
other aggregated commands)?

Just my $2/100.

tm
--
      /               . . . . . . . . . . . . . . . . . . . . . . . . . . .
__  __/   __  __     . . . . . . . . . . . . . . . . . . . . . .  the mole
   /     /   /   /  . . . . . . . . . . . .  markusg@darkwing.uoregon.edu
__/   __/ __/ __/  . . . . . . . . http://darkwing.uoregon.edu/~markusg/




From owner-pine-info@cac.washington.edu  Sun Jan 29 16:36:02 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13220;
	Sun, 29 Jan 95 16:36:02 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18913;
	Sun, 29 Jan 95 16:32:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18907;
	Sun, 29 Jan 95 16:32:36 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYjo5-00038PC; Sun, 29 Jan 95 16:17 PST
To: pine-info@cac.washington.edu
From: glenn@creator.ucns.uga.edu (Glenn Leavell)
Subject: several Pine suggestions
Date: 23 Jan 1995 17:35:56 GMT
Message-Id: <3g0pds$r9c@hobbes.cc.uga.edu>

I really enjoy using Pine, and I appreciate the work that the authors have
put into developing and supporting it.  Here are a few suggestions for
future releases of Pine that the developers can "take or leave".  Thanks!

1)  In INDEX mode, allow the 'k' and 'j' keys to be used to move the current
    pointer up and down (j key would only function like this if
    jump short cut were turned on).  This convention can be
    found in vi, Elm, Gopher, and other utilities, so it makes things
    somewhat consistent.

2)  When reading a message with the builtin Pine pager, the spacebar
    scrolls the message down one page.  Add a feature such that the
    RETURN key can be used to scroll down one line.  This convention
    is used with the Unix more and less commands, as well as some
    other pagers.

3)  Add a special Quit-type command that will exit Pine without making
    any changes to the current folder.  For example, when this command
    is used, all messages marked for deletion will NOT be deleted, and
    all messages that were marked as new ('N') when the folder was
    opened will still be marked as such when the folder is opened 
    the next time.

4)  Add an option that makes the 'n' (NextMsg) command in the INDEX skip
    over messages marked for deletion.

-- 
Glenn Leavell, glenn@uga.edu
University of Georgia, University Computing and Networking Services



From owner-pine-info@cac.washington.edu  Sun Jan 29 16:50:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13467;
	Sun, 29 Jan 95 16:50:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17218;
	Sun, 29 Jan 95 16:47:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17212;
	Sun, 29 Jan 95 16:47:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYk1m-00038MC; Sun, 29 Jan 95 16:31 PST
To: pine-info@cac.washington.edu
From: gunther@ssi.edc.org (Gunther Anderson)
Subject: Re: Need Pine Binaries
Date: Mon, 23 Jan 1995 17:24:14 GMT
Message-Id: <D2vCCE.5p4@ssi.edc.org>
References: <3fphid$a38@garlic.com> <Pine.SUN.3.91.950121124836.6023A-100000@kelly.teleport.com>

Knute Snortum (knute@teleport.com) wrote:
: On 20 Jan 1995, Robert Mann Packaging Co. wrote:

: > I am still trying to find someone out there who can tell me where I can ftp 
: > Pine binaries for SCO  ...
: > 
: I have been told there are some at celestial.com, but I have yet to find 
: them.  

They're definitely there.  However, frp.celestial.com recently changes 
its IP address, and a lot of sites still don't know about it.  The change 
happened a couple of months ago, but my site (for instance) still finds 
the old address.  I've just looked at the real site, and there are two 
files which you are looking for:

-rw-rw-r--   1 jwc      4217275 Nov 25 11:10 pine-3.91.tar.gz
-rw-rw-r--   1 jwc      1065011 Nov 28 17:47 pine3.91.sco.bins.tar.gz

The first has both source and binaries.  The second, binaries only.

The new information for ftp.celestial.com is that it's an alias for 
camco1.celestial.com, 192.136.111.2.  Go there directly.

Gunther Anderson


From owner-pine-info@cac.washington.edu  Sun Jan 29 17:17:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14120;
	Sun, 29 Jan 95 17:17:16 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17586;
	Sun, 29 Jan 95 17:12:56 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17580;
	Sun, 29 Jan 95 17:12:54 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA12995; Sun, 29 Jan 1995 20:12:31 +0500
Date: Sun, 29 Jan 1995 20:12:31 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Cc: Karel Kubat <karel@bambix.icce.rug.nl>
Subject: Re: Deletion of empty folders
In-Reply-To: <Pine.LNX.3.91.950126082213.5530D-100000@bambix.icce.rug.nl>
Message-Id: <Pine.SOL.3.91.950129200801.12802F@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 705

On Thu, 26 Jan 1995, Karel Kubat wrote:

> How do I get Pine to automatically remove empty folders? Or do I really have
> to run say an external shellscript to accomplish this?
 
There is no autodelete feature for empty folders.  On the other hand,
there's no need for a shell script, either.  In the folder list ("L" from
the main menu), select the folder you want to delete and press "d" to 
delete it.

--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA




From owner-pine-info@cac.washington.edu  Sun Jan 29 17:36:51 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14434;
	Sun, 29 Jan 95 17:36:51 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19692;
	Sun, 29 Jan 95 17:33:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19686;
	Sun, 29 Jan 95 17:33:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYkhg-00038PC; Sun, 29 Jan 95 17:14 PST
To: pine-info@cac.washington.edu
From: peckc@ios.com (charles peck)
Subject: Off Line Reader/Poster
Date: 27 Jan 1995 21:52:17 GMT
Message-Id: <3gbpuh$dv2@ankh.iia.org>




From owner-pine-info@cac.washington.edu  Sun Jan 29 17:45:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14610;
	Sun, 29 Jan 95 17:45:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17968;
	Sun, 29 Jan 95 17:43:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17962;
	Sun, 29 Jan 95 17:43:19 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA13073; Sun, 29 Jan 1995 20:42:53 +0500
Date: Sun, 29 Jan 1995 20:42:53 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: David L Miller <dlm@cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Welcome to pine-info
In-Reply-To: <Pine.ULT.3.92.950120085110.511B-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.SOL.3.91.950129204034.12802G-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 883

On Fri, 20 Jan 1995, David L Miller wrote:

> Yes, psg.com runs a bi-directional gateway between comp.mail.pine and the
> pine-info mailing list.  Note that it is operated by Randy Bush
> <randy@psg.com>, not by the Pine Team.  Due to some lost messages that I 
> just noticed a couple days ago the subscription address for the gateway 
> was changed.  Hopefully that will improve performance and reliability of 
> the gateway.
 
Yep, double the performance!  <g>  I've been receiving two copies of 
every pine-info message for the past few days.  Is this a bug or a 
feature?  :-)
 
--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA




From owner-pine-info@cac.washington.edu  Sun Jan 29 19:10:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15980;
	Sun, 29 Jan 95 19:10:44 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18977;
	Sun, 29 Jan 95 19:07:58 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18971;
	Sun, 29 Jan 95 19:07:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYmCs-00038fC; Sun, 29 Jan 95 18:51 PST
To: pine-info@cac.washington.edu
From: raider@mail.utexas.edu (Philip Odom)
Subject: UNIX Pine and POP/SMTP
Date: Sun, 29 Jan 1995 00:56:08 -0600
Message-Id: <raider-2901950056080001@slip-14-10.ots.utexas.edu>

I am trying to configure PINE on a PC running Linux and am having a
problem. Is there any way to set up pine to check and send mail using a
remote server? My problem basically is that I want to be able to check my
mail on mail.utexas.edu using pine and also send mail through this server.


If this is not possible using pine (i.e., if pine will only use sendmail
and work for local e-mail), can someone recommend a good mail program (an
X program would be nice) that would be a good alternative to PINE?

Thanks. If you wouldn't mind replying via e-mail, that would be great.

Philip Odom
raider@mail.utexas.edu


From owner-pine-info@cac.washington.edu  Sun Jan 29 19:39:55 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16495;
	Sun, 29 Jan 95 19:39:55 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21186;
	Sun, 29 Jan 95 19:36:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21180;
	Sun, 29 Jan 95 19:36:48 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYmhN-00038YC; Sun, 29 Jan 95 19:22 PST
To: pine-info@cac.washington.edu
From: cjolley@iac.net (Carl Jolley)
Subject: Re: pine to cc:Mail
Date: 28 Jan 1995 15:01:00 -0500
Message-Id: <3ge7ps$21q@little-miami.iac.net>
References: <Pine.OSF.3.91a.950112104530.3760B-100000@saul2.u.washington.edu> <3g1pbc$ams@raffles.technet.sg>

A company called Internation Messaging Associates has a product called
Internet Exchange that supports Mime. email: sales@ima.com
 
The last time I tried to e-mail them, I wasn't able to get through.
When I called them, they said that their ISP had messed them up.
If you need their phone number, send me e-mail.

Cheong Weei Gan (cwgan@slip.technet.sg) wrote:

: I think ccMail's SMTP gateway currently does not support MIME but I 
: think Lotus working on a version that is faster and
: will support MIME


-- 
**** cjolley@iac.net <Carl Jolley>
**** All opinions are my own and not necessarily those of my employer ****


From owner-pine-info@cac.washington.edu  Sun Jan 29 21:08:29 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18317;
	Sun, 29 Jan 95 21:08:29 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20694;
	Sun, 29 Jan 95 21:05:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20688;
	Sun, 29 Jan 95 21:05:07 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYo2z-00038RC; Sun, 29 Jan 95 20:49 PST
To: pine-info@cac.washington.edu
From: "Amy L. Lauderdale" <laall@cotton.vislab.olemiss.edu>
Subject: Re: screen clearing
Date: Sun, 29 Jan 1995 13:56:12 -0600 (CST)
Message-Id: <Pine.SUN.3.90.950129135225.25645B-100000@cotton.vislab.olemiss.edu>
References: <Pine.SUN.3.91.950129092039.3343K-100000@linknet.kitsap.lib.wa.us>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.91.950129092039.3343K-100000@linknet.kitsap.lib.wa.us> 


> Out of 2500 users a few are reporting that when in Pine their screens 
> won't clear. They wind up typing over previous screens or messages. It 
> looks as if the messages themselves are okay, but, of course, it;s pretty 
> difficult to type over old messages or menu screens. 
> 
> At first I thought this was a simple terminal emulation problem. Change 
> to VT-100 and reboot. Then I thought it must be certain comm packages, 
> like old Telix, that can't quite cut it. 
> 
> But upon investigation I can't find a common element. For some people it 
> even happens with Procomm, our favorite around here. 
> 
> Anybody got a clue? I don't!

I don't have a clue, but wanted to say I have seen the same thing.  It
isn't a major problem but is very annoying. I have seen it using both
Procomm and Telix.  Usually ^L will clear the extra stuff out of the
way.  For me, it is  usually the last line on the screen when using
the reply mode that doesn't clear.

************************************************************
Amy Lauderdale/Math Teacher
Lafayette High School/Northwest Community College
Oxford, MS          laall@cotton.vislab.olemiss.edu
************************************************************



From owner-pine-info@cac.washington.edu  Sun Jan 29 21:08:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18346;
	Sun, 29 Jan 95 21:08:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20702;
	Sun, 29 Jan 95 21:05:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [198.76.200.3] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20696;
	Sun, 29 Jan 95 21:05:10 -0800
Received: by mail (5.0/SMI-SVR4)
	id AA13692; Mon, 30 Jan 1995 00:04:43 +0500
Date: Mon, 30 Jan 1995 00:04:43 -0500 (EST)
From: Chip Old <fold@mail.bcpl.lib.md.us>
To: pine-info@cac.washington.edu
Subject: Re: feature-list and pine.conf.fixed
In-Reply-To: <3gb0sq$2cs@news.cerf.net>
Message-Id: <Pine.SOL.3.91.950130000053.13609A-100000@mail>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 499

On 27 Jan 1995, Dan Malcor-LA Times wrote:

> I want to prevent the use of the "enable-mail-check-cue" feature. 

Why?  The mail check cue seems relatively harmless.  Inquiring minds want
to know... 

--------------------------------------------------------------------
Francis E. Old (Chip Old)         Internet: fold@mail.bcpl.lib.md.us
Internetworking Administrator     Voice:    (410) 887-6180
Baltimore County Public Library   FAX:      (410) 887-2091
320 York Road
Towson, Maryland 21204 USA



From owner-pine-info@cac.washington.edu  Sun Jan 29 21:14:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18467;
	Sun, 29 Jan 95 21:14:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22374;
	Sun, 29 Jan 95 21:11:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22367;
	Sun, 29 Jan 95 21:10:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYo39-00038TC; Sun, 29 Jan 95 20:49 PST
To: pine-info@cac.washington.edu
From: "Amy L. Lauderdale" <laall@cotton.vislab.olemiss.edu>
Subject: Re: Marking Multiple News posts Deleted
Date: Sun, 29 Jan 1995 13:59:05 -0600 (CST)
Message-Id: <Pine.SUN.3.90.950129135703.25645C-100000@cotton.vislab.olemiss.edu>
References: <D35rFs.G2C@crash.cts.com> <ellis.791396176@gmi.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <ellis.791396176@gmi.edu> 

> 
> Look at the select (;) and (a)pply commands.

since joining this newsgroup I have seen several references to using
the select (;) command.  I have tried it in various screens and it
always tells me it is an unknown command.  I am using version
3.90 on one account and 3.91 on another.

Can someone provide further information on this command?

************************************************************
Amy Lauderdale/Math Teacher
Lafayette High School/Northwest Community College
Oxford, MS          laall@cotton.vislab.olemiss.edu
************************************************************



From owner-pine-info@cac.washington.edu  Sun Jan 29 23:03:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20546;
	Sun, 29 Jan 95 23:03:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23701;
	Sun, 29 Jan 95 22:59:09 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rip.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23695;
	Sun, 29 Jan 95 22:59:07 -0800
Received: by rip.psg.com (Smail3.1.29.1 #3)
	id m0rYq4j-00031RC; Sun, 29 Jan 95 22:59 PST
Message-Id: <m0rYq4j-00031RC@rip.psg.com>
Date: Sun, 29 Jan 95 22:59 PST
From: randy@psg.com (Randy Bush)
To: Chip Old <fold@mail.bcpl.lib.md.us>
Cc: David L Miller <dlm@cac.washington.edu>, pine-info@cac.washington.edu
Subject: Re: Welcome to pine-info
References: <Pine.ULT.3.92.950120085110.511B-100000@shiva1.cac.washington.edu>
	<Pine.SOL.3.91.950129204034.12802G-100000@mail>

> Yep, double the performance!  <g>  I've been receiving two copies of 
> every pine-info message for the past few days.  Is this a bug or a 
> feature?  :-)

Feature, of course.  And we are not even charging extra for the first trial
weeks.  :-)

David, please check for double subscription up there.

randy


From owner-pine-info@cac.washington.edu  Sun Jan 29 23:16:05 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20734;
	Sun, 29 Jan 95 23:16:05 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22318;
	Sun, 29 Jan 95 23:12:06 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AB22312;
	Sun, 29 Jan 95 23:12:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYq3v-00038SC; Sun, 29 Jan 95 22:58 PST
To: pine-info@cac.washington.edu
From: thomask@hubcap.clemson.edu (Thomas Eugene King)
Subject: FAQ?
Date: 29 Jan 95 20:41:53 GMT
Message-Id: <thomask.791412113@hubcap>

I would like the FAQ please let me know a FTP site that I might be able
to find it at.


From owner-pine-info@cac.washington.edu  Sun Jan 29 23:37:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21015;
	Sun, 29 Jan 95 23:37:56 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24059;
	Sun, 29 Jan 95 23:32:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24052;
	Sun, 29 Jan 95 23:32:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYqO2-00038SC; Sun, 29 Jan 95 23:18 PST
To: pine-info@cac.washington.edu
From: jchrysler@PROBLEM_WITH_INEWS_DOMAIN_FILE (Zachariah Baum)
Subject: Pine patch for security on BBSes
Date: 30 Jan 1995 06:16:23 GMT
Message-Id: <3gi07n$352@kadath.zeitgeist.net>


I created a patch in order to have a '-s' secure option.  We are running
a BBS, and didn't want users below a certain level to be able to send
mail outside of the local BBS.  So this patch, from the pine3.91
directory made from the tar file using the -p1 option, adds a command   
line argument '-s' so that the user can't compose, reply to, or forward  
messages.  If they attempt to, they get a message saying that they don't
have write-mail privileges.

Inside our BBS, we have it check the level of the user, and if they
attempt to call pine, we call it with or without the '-s' option.  The
BBS software checks if they're trying to put people's names to send to on
the commandline, and if they are, checks if it's an external user (I
check for '@' and '.'s).  It won't let users of a lesser security
clearance send mail from the commandline to the outside world.

This, for us, allows the public to connect without us having to worry if
they're sending death threats to the president, or whatever, until we
have their address or whatever we require of them.

Here you go...

---------CUT HERE----------
diff -U 2 pine3.91/pine/args.c pine3.91.secure/pine/args.c
--- pine3.91/pine/args.c        Thu Aug 18 10:19:47 1994
+++ pine3.91.secure/pine/args.c Sun Jan 29 21:05:43 1995
@@ -101,4 +101,5 @@
     struct variable *vars     = pine_state->vars;

+    secure = 0;

     ac = argc;
@@ -160,4 +161,7 @@
            }else{
               switch(c = **av) {
+     case 's':
+       secure = 1;
+       break;
                 case 'h':
                   do_help = 1;
Only in pine3.91.secure/pine: date.c
diff -U 2 pine3.91/pine/headers.h pine3.91.secure/pine/headers.h
--- pine3.91/pine/headers.h     Wed Aug  3 19:20:35 1994
+++ pine3.91.secure/pine/headers.h      Sun Jan 29 19:49:24 1995
@@ -106,4 +106,6 @@
 extern char         tmp_20k_buf[];

+extern int          secure;
+
 #ifdef DEBUG
 extern FILE        *debugfile;         /* file for debug output          */
diff -U 2 pine3.91/pine/mailcmd.c pine3.91.secure/pine/mailcmd.c
--- pine3.91/pine/mailcmd.c     Tue Oct 11 09:37:59 1994
+++ pine3.91.secure/pine/mailcmd.c      Sun Jan 29 20:56:59 1995
@@ -437,10 +437,14 @@
         case PF11:
         case 'r':
-          if(state->anonymous && command == PF11) {
-           if(in_index)
-             goto do_sortindex;
-           else
-             goto do_index;
-         }
+          if (secure)
+            q_status_message(0,2,3,"You do not have write-mail privileges.");
+          else {  
+            if(state->anonymous && command == PF11) {
+                   if(in_index)
+                     goto do_sortindex;
+                   else
+                     goto do_index;
+
+                   }

           if(state->nr_mode && command == PF11)
@@ -451,4 +455,5 @@
          cmd_reply(state, msgmap, 0);
          cur_msgno = mn_get_cur(msgmap);
+    }
           break;

@@ -458,4 +463,7 @@
         case 'f':   
 do_forward:
+      if (secure)
+        q_status_message(0,2,3,"You do not have write-mail privileges.");
+      else {
           if(command == PF12) {
            if(state->anonymous)
@@ -467,4 +475,5 @@
          cmd_forward(state, msgmap, 0);
          cur_msgno = mn_get_cur(msgmap);
+  }
           break;

@@ -484,4 +493,7 @@
         case OPF4:
         case 'c':
+          if (secure)
+            q_status_message(0,2,3,"You do not have write-mail privileges.");
+          else {
           if(state->anonymous)
             goto bogus;
@@ -493,4 +505,5 @@
           compose_screen(state);
           state->mangled_screen = 1;
+          }
           break; 

@@ -3731,9 +3744,16 @@

       case 'r' :                       /* reply */
-       cmd_reply(state, msgmap, 1);
+ if (secure) q_status_message(0,2,3,"You do not have write-mail privileges.");
+       else {
+               cmd_reply(state, msgmap, 1);
+               }
        break;    

       case 'f' :                       /* Forward */
+        if (secure)
+          q_status_message(0,2,3,"You do not have write-mail privileges.");
+        else {
        cmd_forward(state, msgmap, 1);
+  }
        break;

diff -U 2 pine3.91/pine/makefile.lnx pine3.91.secure/pine/makefile.lnx
--- pine3.91/pine/makefile.lnx  Tue Oct 11 15:24:30 1994
+++ pine3.91.secure/pine/makefile.lnx   Sun Jan 29 21:12:09 1995
@@ -58,7 +58,7 @@   
 LN=          ln -s
 MAKE=        make
-OPTIMIZE=    # -O2
+OPTIMIZE=    -O2
 IMAPDIR=     ../c-client
Only in pine3.91.secure/pine: os.c
Common subdirectories: pine3.91/pine/osdep and pine3.91.secure/pine/osdep
Only in pine3.91.secure/pine: pine
diff -U 2 pine3.91/pine/pine.c pine3.91.secure/pine/pine.c
--- pine3.91/pine/pine.c        Mon Oct 10 17:27:18 1994
+++ pine3.91.secure/pine/pine.c Sun Jan 29 21:06:04 1995
@@ -70,4 +70,5 @@
 char       *pine_version = PINE_VERSION;       /* version string */
 int          timeout     = NEW_MAIL_TIME;      /* referenced in pico */
+int          secure;


@@ -1091,5 +1092,8 @@
          case OPF4:
          case 'c':
-           pine_state->next_screen = compose_screen;   
+      if (secure) q_status_message(0,2,3,"You do not have write-mail privileges.");
+                       else {
+             pine_state->next_screen = compose_screen;
+                               }
            return;

--------CUT HERE---------

PS... It also adds to the Linux makefile the -O2 option instead of the
-O, and removes the -g.  You can remove this, and it won't effect the
patch's functioning.

                Jesus Chrysler
                        jchrysler@catch22.com

--



From owner-pine-info@cac.washington.edu  Mon Jan 30 01:15:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23384;
	Mon, 30 Jan 95 01:15:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23860;
	Mon, 30 Jan 95 01:10:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23854;
	Mon, 30 Jan 95 01:10:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYrrQ-00038RC; Mon, 30 Jan 95 00:53 PST
To: pine-info@cac.washington.edu
From: schueman@access.digex.net (Greg Schueman)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 23 Jan 1995 16:16:23 -0500
Message-Id: <3g16b7$r06@access1.digex.net>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca>

In article <3g0mmh$1bg@gbc.gbrownc.on.ca>,
Rashid Bawa <rbawa@gbc.gbrownc.on.ca> wrote:
>I am looking out for POP binaries (POP, POP2, POP3) that will run on
>a SparcClassic running Solaris 2.3. If anyone has the location of a site,

Look at ftp://ftp.digex.net/pub/access/schueman/popper.tar.gz.

This contains source + binaries for a POP3 server. It was compiled under
Solaris 2.3 on a Sparc 10.

Enjoy,
  -Greg


From owner-pine-info@cac.washington.edu  Mon Jan 30 01:36:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23950;
	Mon, 30 Jan 95 01:36:03 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24090;
	Mon, 30 Jan 95 01:27:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from gateway1.DHL.COM by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24084;
	Mon, 30 Jan 95 01:27:06 -0800
Received: from lhrsys1.lhr-sys.bru-ro.DHL.COM by gateway1.DHL.COM id aa14515;
          30 Jan 95 2:13 PST
Received: from lhroas1.lhr-sys.bru-ro.DHL.COM by lhrsys1.lhr-sys.bru-ro.DHL.COM with SMTP
	(1.36.108.7/2.03-DSI) id AA22152; Mon, 30 Jan 1995 09:28:59 GMT
Received: (from stares@localhost) by lhroas1.lhr-sys.bru-ro.DHL.COM (8.6.9/8.6.9) id OAA02393; Mon, 30 Jan 1995 14:26:42 GMT
Date: Mon, 30 Jan 1995 14:26:42 +0000 (GMT)
From: Stuart.Tares@lhr-sys.bru-ro.DHL.COM
X-Sender: stares@lhroas1.lhr-sys.bru-ro.DHL.COM
To: "Gregory S. Sutter" <gsutter@gss115.rh.psu.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Pine and Reply-To: environment var
In-Reply-To: <3gf3r4$tas@hearst.cac.psu.edu>
Message-Id: <Pine.LNX.3.91.950130142414.2376A-100000@lhroas1.lhr-sys.bru-ro.DHL.COM>
X-Disclaimer: The opinions expressed are my own and not my employers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 29 Jan 1995, Gregory S. Sutter wrote:

> Is there a way to get Pine 3.91 to read my environment variable 'Reply-To'?
> I have been manually inserting the Reply-To line in _each_ letter I write, 
> and it is gettting quite annoying.
> 
> Pine 3.91, Linux 1.1.85, bash.
> 

Gregory,  

The easiest thing to do is to enter the Reply-To entry as a customised 
header to PINE.  This is what I do on my Linux box.  

To to this, simply press S (setup) from the main menu and then C for 
config.  Now move down to Customised Headers and add the Reply-To field.

Stuart

----
Stuart Tares			Email : Stuart.Tares@lhr-sys.bru-ro.DHL.COM
Senior Network Analyst		Voice : +44 181 742 4060
DHL Systems Ltd, CSG Europe & Africa Region



From owner-pine-info@cac.washington.edu  Mon Jan 30 04:01:12 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26872;
	Mon, 30 Jan 95 04:01:12 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27208;
	Mon, 30 Jan 95 03:49:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27202;
	Mon, 30 Jan 95 03:49:01 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYuFZ-00038UC; Mon, 30 Jan 95 03:26 PST
To: pine-info@cac.washington.edu
From: rubin@setinc.com (Don Rubin)
Subject: Re: Q. about HUJI VMS Pine 3.91 beta 3
Date: 29 Jan 1995 21:15:17 GMT
Message-Id: <3gh0h5$min@news.cais.com>
References: <17332AE2DS86.FLAVELL@cernvm.cern.ch>

In article FLAVELL@cernvm.cern.ch, FLAVELL@cernvm.cern.ch (Alan J Flavell) writes:
   stuff deleted....
> Many thanks for your helpful reply.  In the meantime, I find that
> there is a more serious (!) problem: it doesn't seem to understand
> MIME encoded mail.  I think this is because the incoming mail gets
> an additional set of headers added ahead of the RFC822 headers.
> Presumably this is a result of the way we have MULTINET configured,
> and it allows MAIL to handle both SMTP and DECNET mail transparently.
>  
> The same situation probably explains why it does not compose
> REPLY addresses properly: it seems to be using the added
> headers rather than the RFC822 headers, so (when replying to
> incoming SMTP mail) we get a reply address like this:
>  
>    "SMTP%a.user@some.domain.edu"@our.own.domain.name
>  
> I think our existing MAIL users would be upset if we were to change
> the format of incoming mail, if they lost the ability to reply to
> incoming DECNET mail.  Is there anything we can do to live with
> this situation, and still use PINE (so as to be able to use MIME)?
>  
I am having this trouble ie. malformed return addresses (we are using UCX not
multinet), I am trying to hack the reply.c source to parse out the appropriate
stuff (unless someone can come up with a more elegent solution :). The problem
I am having is that I put a few printf( or fprintf(stderr.. into the code and
it compiles OK but blows up when that statement is hit. Any suggestions how
to debug this?


Don Rubin                             Voice: 301-588-8010
Systems Engineering Technology Inc.   Fax:   301-588-0154
9703 Forest Glen Court                rubin@setinc.com
Silver Spring, MD 20910-1121          http://www.setinc.com
                                      finger for PGP public key











From owner-pine-info@cac.washington.edu  Mon Jan 30 04:24:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27750;
	Mon, 30 Jan 95 04:24:13 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26232;
	Mon, 30 Jan 95 04:12:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26226;
	Mon, 30 Jan 95 04:11:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYud9-00038KC; Mon, 30 Jan 95 03:50 PST
To: pine-info@cac.washington.edu
From: Dave Saville <savild@gatwick.sgp.slb.com>
Subject: Re: Marking Multiple News posts Deleted
Date: Mon, 30 Jan 1995 11:07:16 +0000
Message-Id: <Pine.SUN.3.91.950130110506.3881F-100000@nuthatch>
References: <D35rFs.G2C@crash.cts.com> <ellis.791396176@gmi.edu> <Pine.SUN.3.90.950129135703.25645C-100000@cotton.vislab.olemiss.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.90.950129135703.25645C-100000@cotton.vislab.olemiss.edu> 

On Sun, 29 Jan 1995, Amy L. Lauderdale wrote:

> > 
> > Look at the select (;) and (a)pply commands.
> 
> since joining this newsgroup I have seen several references to using
> the select (;) command.  I have tried it in various screens and it
> always tells me it is an unknown command.  I am using version
> 3.90 on one account and 3.91 on another.
> 
> Can someone provide further information on this command?
> 
> ************************************************************
> Amy Lauderdale/Math Teacher
> Lafayette High School/Northwest Community College
> Oxford, MS          laall@cotton.vislab.olemiss.edu
> ************************************************************
> 
> 
> 

when in the INDEX of a news group press

;aadTABENTER

This will:
mark all items in news group as deleted ;aad
TAB to folder list
ENTER index of next newsgroup

Hope this helps

David C. Saville  savild@gatwick.Geco-Prakla.slb.com
Geco-Prakla, Schlumberger House, Buckingham Gate,
Gatwick Airport, West Sussex. RH6 0NZ UK. Tel: +44 1293 556326
Happyness is a binary state. 



From owner-pine-info@cac.washington.edu  Mon Jan 30 04:24:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27756;
	Mon, 30 Jan 95 04:24:15 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27699;
	Mon, 30 Jan 95 04:12:01 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27693;
	Mon, 30 Jan 95 04:11:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYudD-00038QC; Mon, 30 Jan 95 03:50 PST
To: pine-info@cac.washington.edu
From: Dave Saville <savild@gatwick.sgp.slb.com>
Subject: OS/2 port anyone?
Date: Mon, 30 Jan 1995 11:16:11 +0000
Message-Id: <Pine.SUN.3.91.950130111446.3881H-100000@nuthatch>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Anyone fancy doing an OS/2 port? Pine development say its often asked 
for but they do not have the funding.

David C. Saville  savild@gatwick.Geco-Prakla.slb.com
Geco-Prakla, Schlumberger House, Buckingham Gate,
Gatwick Airport, West Sussex. RH6 0NZ UK. Tel: +44 1293 556326
Happyness is a binary state. 



From owner-pine-info@cac.washington.edu  Mon Jan 30 05:23:22 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29101;
	Mon, 30 Jan 95 05:23:22 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26952;
	Mon, 30 Jan 95 05:13:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA26946;
	Mon, 30 Jan 95 05:13:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYvfR-00038SC; Mon, 30 Jan 95 04:57 PST
To: pine-info@cac.washington.edu
From: pflores@phoenix.phoenix.net (Paul Flores)
Subject: Re: POP binaries for SOLARIS 2.3
Date: 23 Jan 1995 21:49:57 GMT
Message-Id: <3g18a5$epp@gryphon.phoenix.net>
References: <3g0mmh$1bg@gbc.gbrownc.on.ca>

Rashid Bawa (rbawa@gbc.gbrownc.on.ca) wrote:
: I am looking out for POP binaries (POP, POP2, POP3) that will run on
: a SparcClassic running Solaris 2.3. If anyone has the location of a site,
: please send me email.

: Thanking you in advance.


Please post here as well!!!!   (Or send me email as well!!!)

Paul

http://www.phoenix.net/USERS/pflores.html



From owner-pine-info@cac.washington.edu  Mon Jan 30 06:40:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01052;
	Mon, 30 Jan 95 06:40:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29325;
	Mon, 30 Jan 95 06:28:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29319;
	Mon, 30 Jan 95 06:28:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYwnu-00038SC; Mon, 30 Jan 95 06:10 PST
To: pine-info@cac.washington.edu
From: aa274@cfn.cs.dal.ca (Fred Bulger)
Subject: Print result
Message-Id: <D377FC.3nu@cs.dal.ca>
Date: Mon, 30 Jan 1995 03:09:11 GMT


   What does the following mean when using the 'Y' print command in Pine:

 [Print result: getwd: can't open ...]

    Thanks...

      -Fred.

--

-----------------------
Fred Bulger  aa274@cfn.cs.dal.ca
             (902)-889-3024

Looking for new sig ... please send suggestions

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


From owner-pine-info@cac.washington.edu  Mon Jan 30 06:43:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01128;
	Mon, 30 Jan 95 06:43:42 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27962;
	Mon, 30 Jan 95 06:33:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27956;
	Mon, 30 Jan 95 06:33:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYwug-00038UC; Mon, 30 Jan 95 06:17 PST
To: pine-info@cac.washington.edu
From: offsite@crl.com (Lee (not F) Bailey)
Subject: [Q] pine-debug* files -- Make it *STOP*
Date: 23 Jan 1995 22:58:40 GMT
Message-Id: <3g1cb0$dgd@nntp.crl.com>

What have I done to my pine program to make it hate me? I was toolin along
just fine for weeks, then suddenly pine starts makeing these files in my
$HOME. They are of the form pine-debug1, 2, ... 
  
How do I make it stop??? I have 'whereis'd everything I could find, but 
nothing about these files.
  
Please help. Thanks

--
______________________________________________________________________________
Lee Bailey	|  E-Mail:   offsite@crl.com
	User of Geoworks Ensemble instead of M$ Windoze
	Try the demo at ftp://arginine.umdnj.edu/pub/geos/publish
		     or ftp://ftp.mcs.com/mcsnet.users/jbarr/GeoPublish	


From owner-pine-info@cac.washington.edu  Mon Jan 30 07:32:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02281;
	Mon, 30 Jan 95 07:32:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00216;
	Mon, 30 Jan 95 07:11:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00210;
	Mon, 30 Jan 95 07:11:54 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYxSL-00038gC; Mon, 30 Jan 95 06:51 PST
To: pine-info@cac.washington.edu
From: penev@pisa.Rockefeller.edu (Penio Penev)
Subject: Re: Abort signal
Message-Id: <D2vBy3.EDL@rockyd.rockefeller.edu>
References: <3fno24$38e@almaak.usc.edu>
Date: Mon, 23 Jan 1995 17:15:39 GMT

On 19 Jan 1995 23:17:24 -0800 [Howard Gillman] (gillman@almaak.usc.edu) wrote:
| I asked a new listserv to send me mail in digest format.  When I received 
| the message the index indicated that it was 43,810 characters.  When I 
| opened the file I received a blank screen with a note 
| "Parts/Attachments"; at the bottom of the blank screen it said "All of 
| message text."  I tried to View the attachments, but the attachment index 
| had nothing on it.  When I press [V]iew anyway pine quick with the 
| message "But in Pine detected:  'Received abort signal.'  Exiting pine."  
| So, what the heck is the problem with the message I received, and why 
| can't I get access to it?  Thanks in advance.

Something similar happened to me. Pine reports the right length, but
does not display the message. After I looked in my mailbox with emacs
(or any other text editor, capable of displaying control codes), I saw
a block of 4096 zeroes in the file. 4096=4K and is exactly one virtual
memory page. Pine does not display the rest of the text, probably it
is treating the message as a zero-delimited string by the C convention :-( 
The problem is caused most probably by an incoherency in the NSF
mounting of the mail directory :-(

--
Penio Penev <Penev@venezia.Rockefeller.edu> 1-212-327-7423


From owner-pine-info@cac.washington.edu  Mon Jan 30 08:13:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04012;
	Mon, 30 Jan 95 08:13:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29305;
	Mon, 30 Jan 95 07:58:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29299;
	Mon, 30 Jan 95 07:58:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYyEn-00038dC; Mon, 30 Jan 95 07:41 PST
To: pine-info@cac.washington.edu
From: sravi@newton.cs.jhu.edu (Felix the Cat)
Subject: Listservs and pine
Date: 30 Jan 1995 04:44:20 GMT
Message-Id: <3ghqr4$ms6@blaze.cs.jhu.edu>

-- 
------------------------------------------------------------------------------
       _/_/_/_/_/    _/_/_/_/_/ | JOIN THE ARMY!  Travel to exotic, distant
     _/            _/      _/   | lands; meet exciting, unusual people --
   _/_/_/_/_/    _/_/_/_/_/     | and kill them


From owner-pine-info@cac.washington.edu  Mon Jan 30 08:23:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04334;
	Mon, 30 Jan 95 08:23:48 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29769;
	Mon, 30 Jan 95 08:14:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from buaxp1.barry.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29763;
	Mon, 30 Jan 95 08:14:00 -0800
Date: Mon, 30 Jan 1995 11:13:38 -0500 (EST)
From: Nina Ricardi <RICARDI@BUAXP1.BARRY.EDU>
To: pine-info@cac.washington.edu
Message-Id: <950130111338.3b3@BUAXP1.BARRY.EDU>
Subject: PINE 3.07 too slow

PINE 3.07 was installed about one year ago, is used internally by some users
on our system, and has worked beautifully until last week.

Since last Friday we are having problem using it. After executing the command 
'pine' it takes from two to three minutes for the menu to come up. It then 
displays '0 messages' when I know that there are several messages old and new. 
Whatever the next command is it takes another two to three minutes again but 
then the number of messages is displayed correctly. From then on everything 
pops up immediately (the way it's supposed to) like cancel out of a message,
go to the Main or Other menu, quit, etc. 

I've tried searching for information on the tech-notes and README files with 
no success. I've tried to use PINE while nobody else was on the system to 
eliminate the possibility that there was an overload of processes on the 
system (as suggested by a Sequent technician), I've re-booted the system to 
make sure there wasn't anything 'hanging' that I didn't know of. All other
softwares are working as usual. 

Any suggestions are greatly appreciated!

Nina Ricardi		DYNIX/ptx V2.0.3
Barry University
ricardi@buaxp1.barry.edu
(305)899-3152




From owner-pine-info@cac.washington.edu  Mon Jan 30 08:28:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04627;
	Mon, 30 Jan 95 08:28:00 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01304;
	Mon, 30 Jan 95 08:07:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01298;
	Mon, 30 Jan 95 08:07:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rYyJ2-00038eC; Mon, 30 Jan 95 07:46 PST
To: pine-info@cac.washington.edu
From: valko@cyberspace.com (Jack Valko)
Subject: Need to secure pine
Date: 23 Jan 1995 15:28:28 -0800
Message-Id: <3g1e2s$5sk@case.cyberspace.com>

I would like to know if there is some way to set a configuration in pine 
so that users can't change it from the Setup menu.  Specifically, I want 
to restrict the alternate editor feature.  I have specified 
'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
doesn't seem to do it.  Can anyone help?

==================================================
Jack Valko           |       - Cyberspace -
System Administrator | 300 Queen Anne Ave. N. #396 
cyberspace.com       |   Seattle, WA 98109-4599 
cyberspace.net       |       (206) 281-5397 
==================================================



From owner-pine-info@cac.washington.edu  Mon Jan 30 08:42:15 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05070;
	Mon, 30 Jan 95 08:42:15 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00101;
	Mon, 30 Jan 95 08:23:54 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29995;
	Mon, 30 Jan 95 08:23:52 -0800
Received: from localhost by shiva1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13129;
	Mon, 30 Jan 95 08:23:44 -0800
Date: Mon, 30 Jan 1995 08:22:58 -0800 (PST)
From: David L Miller <dlm@cac.washington.edu>
To: Randy Bush <randy@psg.com>
Cc: Chip Old <fold@mail.bcpl.lib.md.us>, pine-info@cac.washington.edu
Subject: Re: Welcome to pine-info
In-Reply-To: <m0rYq4j-00031RC@rip.psg.com>
Message-Id: <Pine.ULT.3.92.950130082241.22930d-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


grep psg ~majordomo/lists/*
/usr/users/majordom/lists/pine-info:pine-list@rain.psg.com

only one...

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Sun, 29 Jan 1995, Randy Bush wrote:

> Date: Sun, 29 Jan 95 22:59 PST
> From: Randy Bush <randy@psg.com>
> To: Chip Old <fold@mail.bcpl.lib.md.us>
> Cc: David L Miller <dlm@cac.washington.edu>, pine-info@cac.washington.edu
> Subject: Re: Welcome to pine-info
> 
> > Yep, double the performance!  <g>  I've been receiving two copies of 
> > every pine-info message for the past few days.  Is this a bug or a 
> > feature?  :-)
> 
> Feature, of course.  And we are not even charging extra for the first trial
> weeks.  :-)
> 
> David, please check for double subscription up there.
> 
> randy
> 


From owner-pine-info@cac.washington.edu  Mon Jan 30 08:59:48 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05854;
	Mon, 30 Jan 95 08:59:48 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02173;
	Mon, 30 Jan 95 08:49:49 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from asl-labs.bc.ca by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02165;
	Mon, 30 Jan 95 08:49:44 -0800
Received: by asl3.asl-labs.bc.ca (5.4R3.10/200.2.1.5)
	id AA25447; Mon, 30 Jan 1995 08:48:58 -0800
Date: Mon, 30 Jan 1995 08:48:57 -0800 (PST)
From: "Brian P. Hampson" <brian@asl3.asl-labs.bc.ca>
Subject: Re: Pine patch for security on BBSes
To: Zachariah Baum <jchrysler@PROBLEM_WITH_INEWS_DOMAIN_FILE.asl-labs.bc.ca>
Cc: pine-info@cac.washington.edu
In-Reply-To: <3gi07n$352@kadath.zeitgeist.net>
Message-Id: <Pine.3.89.9501300855.A25369-0100000@asl3>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 30 Jan 1995, Zachariah Baum wrote:

> 
> I created a patch in order to have a '-s' secure option.  We are running
> a BBS, and didn't want users below a certain level to be able to send
> mail outside of the local BBS.  So this patch, from the pine3.91
> directory made from the tar file using the -p1 option, adds a command   
> line argument '-s' so that the user can't compose, reply to, or forward  
> messages.  If they attempt to, they get a message saying that they don't
> have write-mail privileges.
> 
> Inside our BBS, we have it check the level of the user, and if they
> attempt to call pine, we call it with or without the '-s' option.  The
> BBS software checks if they're trying to put people's names to send to on
> the commandline, and if they are, checks if it's an external user (I
> check for '@' and '.'s).  It won't let users of a lesser security
> clearance send mail from the commandline to the outside world.
> 
> This, for us, allows the public to connect without us having to worry if
> they're sending death threats to the president, or whatever, until we
> have their address or whatever we require of them.
> 

How do you keep people from simply cursoring up and changing the "To: " 
field?

B.

   ------------------------------------------------------------------------
   |Brian P. Hampson                  Internet: brian@asl-labs.bc.ca      |
   |System Administration,                      			  |
   |Analytical Service Labs           Fidonet : Brian Hampson 1:153/733   |
   |Vancouver, BC                                                         |
   |                                                                      |
   |               Specialists in Environmental Chemistry                 | 
   |                                                                      |
   ------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Mon Jan 30 10:18:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11001;
	Mon, 30 Jan 95 10:18:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04325;
	Mon, 30 Jan 95 10:04:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04317;
	Mon, 30 Jan 95 10:04:41 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ0AO-00038UC; Mon, 30 Jan 95 09:45 PST
To: pine-info@cac.washington.edu
From: h9397584@hkusub (Michael Agelasto)
Subject: import address list?
Message-Id: <D2vtrK.23K@hkuxb.hku.hk>
Date: Mon, 23 Jan 1995 23:40:31 GMT

How do I import a file that contains addresses and then transfer them to 
the ADDRESS book, or to a list inside ADDRESS book?  

I want to avoid having to retype the entire list within PINE.  

Thanks. 
--
=====================================================================
Michael Agelasto                       Phone: (852) 2858-1914
Department of Education                       (852) 2549-5678 (res)
University of Hong Kong                  Fax: (852) 2858-5649
Hong Kong                              email: h9397584@hkucc.hku.hk
                                       email: h9397584@hkusub.hku.hk
=====================================================================


From owner-pine-info@cac.washington.edu  Mon Jan 30 10:21:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11116;
	Mon, 30 Jan 95 10:21:26 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02486;
	Mon, 30 Jan 95 09:57:18 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02480;
	Mon, 30 Jan 95 09:57:17 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ08x-00038TC; Mon, 30 Jan 95 09:44 PST
To: pine-info@cac.washington.edu
From: kmt@moose.uvm.edu (Kevin M. Turner)
Subject: Pine 3.91 zero-length file bug
Message-Id: <1995Jan30.154726.10716@emba.uvm.edu>
Date: Mon, 30 Jan 1995 15:47:26 GMT

  Like many other folks running AIX 3.2, we've been dealing with the
ever-annoying Pine 3.91 interrupted mail bug.  The bug whenever a
user has a zero-length ~/.pine-interrupted-mail or
~/mail/postponed-msgs file and tries to compose a new message.  The
following is a patch to send.c in the pine code (use 'patch <
send.c.patch' in the pine3.91/pine/ directory to apply the patch).
This is a very small patch, but has proven quite effective in curing
this particular problem for us.

  Disclaimer:  We make no promises that this will work for you, we only
know it works for us under AIX 3.2.5....

Regards,

Kevin


------------------------- send.c.patch -------------------------------
*** send.c.preuvm	Fri Jan 27 15:01:52 1995
--- send.c	Fri Jan 27 15:03:32 1995
*************** redraft(cntxt, mbox, outgoing, body, fcc
*** 463,471 ****
  	if(!stream->nmsgs){
  	    q_status_message(0, 2, 5,
  			   "\007Empty folder.  No messages really postponed!");
! 	    if(stream != ps_global->mail_stream)
  	      mail_close(stream);
! 	    else{
  		q_status_message1(0, 3, 3,
  			 "Returning to \"%s\"", ps_global->inbox_name);
  		mail_close(stream);
--- 463,472 ----
  	if(!stream->nmsgs){
  	    q_status_message(0, 2, 5,
  			   "\007Empty folder.  No messages really postponed!");
! 	    if(stream != ps_global->mail_stream) {
! 	      context_delete(c_string, stream, mbox);
  	      mail_close(stream);
! 	     } else {
  		q_status_message1(0, 3, 3,
  			 "Returning to \"%s\"", ps_global->inbox_name);
  		mail_close(stream);
*************** redraft(cntxt, mbox, outgoing, body, fcc
*** 474,483 ****
  				 ps_global->context_list);
  		ps_global->next_screen = mail_index_screen;
  		stream = ps_global->mail_stream;
  	    }
- 
- 	    context_delete(c_string, stream, mbox);
- 
  	    return(0);
  	}
  	else if(stream == ps_global->mail_stream){
--- 475,482 ----
  				 ps_global->context_list);
  		ps_global->next_screen = mail_index_screen;
  		stream = ps_global->mail_stream;
+ 		context_delete(c_string, stream, mbox);
  	    }
  	    return(0);
  	}
  	else if(stream == ps_global->mail_stream){


.....................................................................
Kevin M. Turner	                                kmt@moose.uvm.edu
Computing and Information Technology            kevin.turner@uvm.edu
University of Vermont                           phone: (802)656-2012




From owner-pine-info@cac.washington.edu  Mon Jan 30 10:25:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11425;
	Mon, 30 Jan 95 10:25:20 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02916;
	Mon, 30 Jan 95 10:13:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02910;
	Mon, 30 Jan 95 10:13:16 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ0MU-00038TC; Mon, 30 Jan 95 09:58 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Handling Return Receipts within PINE (fwd)
Date: 23 Jan 1995 23:59:53 GMT
Message-Id: <3g1ftq$pff@cronkite.ocis.temple.edu>

Comes here Mr. Steve Lowe with this opinion in the "comp.mail.pine" group in
this article on 22 Jan 1995 23:55:04 -0800:

 +   I prompted this discussion with how could I send mail messages 
 +   registered.  Is there a simple way to do this within PINE 3.91?

What do you mean by registered?

 +   > Many, *many* people consider read-receipts to be an invasion of privacy
 +   > would refuse to use any tool that "offered" such a facility.  I would not
 +   > look for this feature in Pine anytime soon...
 +
 +   So just have an option (settable from the setup menu) that turns receipts
 +   on.  (ie have it default to off)  This is a feature available on cc:Mail,
 +   and was used extensively where I last worked -- it can be a great help

We have cc:Mail for inter-office email over a LAN and I (many others) *HATE*
it when someone sends me a mail requesting reciept.

Nowadays mail from "i will always ask for recpt" types don't get read at all.
I just forward them to myself and then read it and if it is worth i will reply
else i will let the sender wonder why I haven't read the "reciept reqd. mail"

Please do not include this feature(or bug i should say) in Pine. I don't want
the system spend precious CPU time sending stupid reciept mail back and forth.

For such extreme cases Return-Receipt-To: works just fine.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 30 11:05:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13568;
	Mon, 30 Jan 95 11:05:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03881;
	Mon, 30 Jan 95 10:50:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from beauty.mcl.ucsb.edu by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03875;
	Mon, 30 Jan 95 10:50:00 -0800
Received: (setspike@localhost) by beauty.mcl.ucsb.edu (MCL.UCSB.EDU-HPUX-1.0-b) id KAA18228; Mon, 30 Jan 1995 10:49:56 -0800
Date: Mon, 30 Jan 1995 10:49:56 -0800 (PST)
From: Jason Pascual <setspike@beauty.mcl.ucsb.edu>
To: pine-info@cac.washington.edu
Message-Id: <Pine.HPP.3.91.950130104945.18185A-100000@beauty.mcl.ucsb.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


unsubscribe


From owner-pine-info@cac.washington.edu  Mon Jan 30 12:46:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17933;
	Mon, 30 Jan 95 12:46:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07837;
	Mon, 30 Jan 95 12:32:52 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07831;
	Mon, 30 Jan 95 12:32:51 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ2X1-00038TC; Mon, 30 Jan 95 12:17 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 95 00:25:25 GMT
Message-Id: <ellis.790907125@gmi.edu>
References: <Pine.ULT.3.92.950122121002.21432W-100000@shiva1.cac.washington.edu> <Pine.SUN.3.91.950122151411.22083G-100000@lab19.cs.purdue.edu>

simmonmt@cs.purdue.edu (Matt Simmons) writes:

 >On Sun, 22 Jan 1995, Terry Gray wrote:
 >> If and when an Internet standard emerges for Read receipt requests and
 >> responses, we would certainly consider such an option... and you can
 >> definitely bank on the fact that the default would be OFF! 

 >Which leaves us with the chicken and the egg problem -- the standard won't
 >be created until programs support it, and programs won't support it until
 >there's a standard. That's why I suggested what I did in my first post --
 >that Pine take the lead, create a standard, and let the world follow.

Give up.  Most people who have thought about it do not want it, and would
turn off the option anyway.  If it is important for you as a recipient to
let people know you have received it, 'r' and tell them.  If you only want
to know as a sender, then many people consider this to be snooping.


-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Mon Jan 30 12:47:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17971;
	Mon, 30 Jan 95 12:47:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06299;
	Mon, 30 Jan 95 12:33:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from cpmt2.cyberport.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06293;
	Mon, 30 Jan 95 12:33:32 -0800
Received: from localhost (pthomas@localhost) by cpmt2.cyberport.net (8.6.5/8.6.5) id NAA06109; Mon, 30 Jan 1995 13:36:03 -0700
Date: Mon, 30 Jan 1995 13:35:58 -0700 (MST)
From: Phillip Thomas <pthomas@cyberport.net>
To: pine-info@cac.washington.edu
Subject: exporting multiple mesgs.
Message-Id: <Pine.BSI.3.90.950130132658.5903B-100000@cpmt2.cyberport.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I can "export" and "append" many messages (one at a time) to a single file.

What I want to do is "export" several messages all at once, to a single file.
A 'block' of messages, if you will.

I hope that this isn't embarrassingly simple.

thanking you, pthomas@cyberport.net


From owner-pine-info@cac.washington.edu  Mon Jan 30 12:54:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18181;
	Mon, 30 Jan 95 12:54:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06442;
	Mon, 30 Jan 95 12:37:46 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06436;
	Mon, 30 Jan 95 12:37:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ2ci-00038VC; Mon, 30 Jan 95 12:22 PST
To: pine-info@cac.washington.edu
From: ellis@nova.gmi.edu (R. Stewart Ellis)
Subject: Re: Handling Return Receipts within PINE (fwd)
Date: 24 Jan 95 00:29:09 GMT
Message-Id: <ellis.790907349@gmi.edu>
References: <Pine.ULT.3.91.950122140551.28499A-100000@admin.aurora.edu>

slowe@admin.aurora.edu (Steve Lowe) writes:


 >Terry --

 >The VMS mail package that we replaced with PINE offered the user the 
 >option of sending mail messages registered.  If I wanted to send a 
 >specific mail message registered, I could do that.

 >I prompted this discussion with how could I send mail messages 
 >registered.  Is there a simple way to do this within PINE 3.91?

Simply put the line:

Please reply when you receive this.

in the message.

 > - Steve Lowe
 >   Aurora University


 >---------- Forwarded message ----------
 >Date: Sun, 22 Jan 1995 15:02:29 -0500 (EST)
 >From: Matt Simmons <simmonmt@cs.purdue.edu>
 >To: Terry Gray <gray@cac.washington.edu>
 >Cc: Portia Shao <PORTIA@INNOSOFT.COM>, Steve Lowe <slowe@admin.aurora.edu>,
 >    Pine Information List <pine-info@cac.washington.edu>
 >Subject: Re: Handling Return Receipts within PINE

 >On Sun, 22 Jan 1995, Terry Gray wrote:
 >> Many, *many* people consider read-receipts to be an invasion of privacy and 
 >> would refuse to use any tool that "offered" such a facility.  I would not 
 >> look for this feature in Pine anytime soon...
 >So just have an option (settable from the setup menu) that turns receipts
 >on.  (ie have it default to off)  This is a feature available on cc:Mail,
 >and was used extensively where I last worked -- it can be a great help

-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /


From owner-pine-info@cac.washington.edu  Mon Jan 30 12:55:13 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18248;
	Mon, 30 Jan 95 12:55:13 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06265;
	Mon, 30 Jan 95 12:32:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06259;
	Mon, 30 Jan 95 12:32:49 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ2Rh-00038RC; Mon, 30 Jan 95 12:11 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 1995 00:09:29 GMT
Message-Id: <3g1gfp$pff@cronkite.ocis.temple.edu>

Comes here Mr. Rahul Dhesi with this opinion in the "comp.mail.pine" group in
this article on 23 Jan 1995 10:10:04 GMT:

 +   >How hard would it be to just have Pine start supporting read receipts?

 +   It would cause a serious invasion of privacy, so it would ideally
 +   be a user-settable option.

This will become such an nightmare, I may have to set it OFF premanently
in pine.conf.fixed atleast here.

That is when and if at all Pine *does* have that feature.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 30 13:37:52 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20425;
	Mon, 30 Jan 95 13:37:52 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09446;
	Mon, 30 Jan 95 13:28:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09440;
	Mon, 30 Jan 95 13:28:55 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ3Nx-00038UC; Mon, 30 Jan 95 13:11 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: several Pine suggestions
Date: 24 Jan 1995 00:46:47 GMT
Message-Id: <3g1iln$pff@cronkite.ocis.temple.edu>

Comes here Mr. Glenn Leavell with this opinion in the "comp.mail.pine" group in
this article on 23 Jan 1995 17:35:56 GMT:

 +   1)  In INDEX mode, allow the 'k' and 'j' key to be used to move the current
 +       pointer up and down (j key would only function like this if
 +       jump short cut were turned on).  This convention can be
 +       found in vi, Elm, Gopher, and other utilities, so it makes things
 +       somewhat consistent.

While personally I wouldn't mind using h,j,k&l keys for navigation I can
almost think of all the new users stopping to use Pine if that is implemented
as one of the main reasons why they think VI is eVIl is because if h,j,k&l.

What would be nice is the use of "/" forward slash for Search instead of W,
as most of all the other utilities make use of that.

 +   2)  When reading a message with the builtin Pine pager, the spacebar
 +       scrolls the message down one page.  Add a feature such that the
 +       RETURN key can be used to scroll down one line.  This convention
 +       is used with the Unix more and less commands, as well as some
 +       other pagers.

Up and Down Arrow keys again function very well in this regard.

What would be nice is if there's an option for the user to set the default
action for Return key. One would choose Return to Page Down, while the other
would set it to Advance by one line while the third (me) would set it to
select the body of the message without the headers and print it to the attchd.
printer. Basically what I'm driving at is "user defined key" macros.

 +   3)  Add a special Quit-type command that will exit Pine without making
 +       any changes to the current folder.  For example, when this command
 +       is used, all messages marked for deletion will NOT be deleted, and
 +       all messages that were marked as new ('N') when the folder was
 +       opened will still be marked as such when the folder is opened 
 +       the next time.

Yes, an X for eXit with an Abandon Changes to mailbox prompt will be ideal.

Again here an option for the user to set X to either eXit or Expunge,
whichever he finds useful as I for one almost never use the Expunge feature
but that doesn't mean others aren't. So to strike an balance...!

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 30 13:58:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21297;
	Mon, 30 Jan 95 13:58:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08478;
	Mon, 30 Jan 95 13:48:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08470;
	Mon, 30 Jan 95 13:48:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ3fp-00038RC; Mon, 30 Jan 95 13:30 PST
To: pine-info@cac.washington.edu
From: penev@pisa.Rockefeller.edu (Penio Penev)
Subject: Re: IMAP in this week's Communications Week
Message-Id: <D37AGM.LvI@rockyd.rockefeller.edu>
References: <3g2qiv$gf8@terminator.ncts.navy.mil> <Pine.ULT.3.92.950124090123.17268C-100000@shiva2.cac.washington.edu>
Date: Mon, 30 Jan 1995 04:14:45 GMT

On 24 Jan 1995 09:15:14 -0800 Terry Gray (gray@cac.washington.edu) wrote:
| On 24 Jan 1995, Paul Everitt wrote:

| Still, it's nice to see that one of the best kept secrets in the email 
| world is finally getting some press coverage.

I don't know how IMAP is the best.

Pine/IMAP handle particlarly bad mailboxes of 2M+, and especially bad
15M+ mailboxex.

IMAP is virtually over SLIP lines with great latency of the resonces.

I'm not saying, that elm is better -- just, that there are either some
inherent design flaws, or sloppy implementations, or both.

--
Penio Penev <Penev@venezia.Rockefeller.edu> 1-212-327-7423


From owner-pine-info@cac.washington.edu  Mon Jan 30 14:39:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22751;
	Mon, 30 Jan 95 14:39:43 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10842;
	Mon, 30 Jan 95 14:31:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10836;
	Mon, 30 Jan 95 14:31:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ4Re-00038CC; Mon, 30 Jan 95 14:19 PST
To: pine-info@cac.washington.edu
From: lawrld@law.lawlib.emory.edu (Richard L. Doernberg)
Subject: Pcpine/keyboard freeze
Date: Mon, 23 Jan 1995 22:22:15 +1000
Message-Id: <lawrld.12.00168042@law.emory.edu>

Has anybody had any trouble with the keyboard freezing while using pcpine with 
trumpet winsock? This happens to me regularly, but when it does, the mouse 
works fine.

Any ideas?
Richard L. Doernberg
Emory University School of Law
Atlanta, GA 30322
Phone: 404 727 6836
Fax:   404 727 6850
Email: lawrld@law.emory.edu


From owner-pine-info@cac.washington.edu  Mon Jan 30 14:54:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA23466;
	Mon, 30 Jan 95 14:54:01 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09706;
	Mon, 30 Jan 95 14:38:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09700;
	Mon, 30 Jan 95 14:38:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ4V6-00038RC; Mon, 30 Jan 95 14:23 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: 24 Jan 1995 01:00:35 GMT
Message-Id: <3g1jfj$pff@cronkite.ocis.temple.edu>

Comes here Mr. Lee (not F) Bailey with this opinion in the "comp.mail.pine"
group in this article on 23 Jan 1995 22:58:40 GMT:

 +   What have I done to my pine program to make it hate me? I was toolin along
 +   just fine for weeks, then suddenly pine starts makeing these files in my
 +   $HOME. They are of the form pine-debug1, 2, ... 
 +   How do I make it stop??? I have 'whereis'd everything I could find, but 
 +   nothing about these files.

Invoke Pine with the -d 0 flag to suppress Pine producing debug-level files.
Usage:

% pine -d 0   (0 as in zero and not as in "OhMyGosh, Pine hates me") :-)

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Mon Jan 30 15:52:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26330;
	Mon, 30 Jan 95 15:52:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12727;
	Mon, 30 Jan 95 15:44:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12721;
	Mon, 30 Jan 95 15:44:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ5Vv-00038RC; Mon, 30 Jan 95 15:28 PST
To: pine-info@cac.washington.edu
From: roger@alex.ptc.org (Roger A. Wolcott)
Subject: Pine, Pegasus, and Folder lock
Date: Mon, 30 Jan 1995 12:01:20 UNDEFINED
Message-Id: <roger.3.008F393A@alex.ptc.org>

Fellow Pine Users,

I have a Linux box on my network that takes care of 
all outgoing mail using Sendmail.  However, when
I run the Windows version of Pegasus, and if  you're
not root, you cannot fetch your messages.  I says:
"Invalid Password" even when I know it is correct.
This may have something to do with the fact that when I 
bring up Pine on the Linux box,  there is a message
that "Can't open folder lock"and that it is readonly.

Thank you in advance for and light shed on this
predicament.

Roger Wolcott



From owner-pine-info@cac.washington.edu  Mon Jan 30 16:41:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28953;
	Mon, 30 Jan 95 16:41:49 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14022;
	Mon, 30 Jan 95 16:34:23 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14016;
	Mon, 30 Jan 95 16:34:20 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02670;
	Mon, 30 Jan 95 16:34:13 -0800
Date: Mon, 30 Jan 1995 16:34:11 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Penio Penev <penev@pisa.Rockefeller.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: IMAP in this week's Communications Week
In-Reply-To: <D37AGM.LvI@rockyd.rockefeller.edu>
Message-Id: <Pine.ULT.3.92.950130161708.14914N-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 30 Jan 1995, Penio Penev wrote:

> On 24 Jan 1995 09:15:14 -0800 Terry Gray (gray@cac.washington.edu) wrote:
> | On 24 Jan 1995, Paul Everitt wrote:
> 
> | Still, it's nice to see that one of the best kept secrets in the email 
> | world is finally getting some press coverage.
> 
> I don't know how IMAP is the best.

I said "best kept secret"... but anyway, I don't know of anything else 
that provides equivalent functionality.

If this comment is in comparison to POP, then the following comment applies:
IMAP is a functional superset of POP, therefore it can do anything that 
POP can do, plus many things POP cannot do.

> Pine/IMAP handle particlarly bad mailboxes of 2M+, and especially bad
> 15M+ mailboxex.

I suspect this observation is largely a question of mailbox format rather
than access protocol.  If you use the CMU Cyrus server, with its highly
tuned (but incompatible with most mail tools) mailbox format, you would
have a very different comment.  (By the way, we know that Pine 3.91 on
Suns and a few other platforms has a performance bug when *opening* Bky
mbox format mailboxes.)

If you compare different access methods, e.g. IMAP, POP, NFS, they all 
have different performance characteristics.  In general I find IMAP 
preferable to the others both in terms of functionality and performance 
profile, but I look forward to when we will have a speedier mailbox 
format available.  (Tenex format is usually better than Bky mbox, but
there is still room for significant improvement.)
 
> IMAP is virtually over SLIP lines with great latency of the resonces.

"is virtually... " what?

I've used it over SLIP/PPP without complaint, but not often with 15MB 
mailboxes :)

Again, the dialup performance depends upon several implementation issues,
including your SLIP parameters.  In addition, IMAP4 has a number of
additions to permit more efficient access over slow links. 
 
> I'm not saying, that elm is better -- just, that there are either some
> inherent design flaws, or sloppy implementations, or both.

There is sometimes a price to be paid for compatibility with other 
tools.  If you can use a mailbox format that other tools do not 
understand, you can make things go much faster.

-teg


From owner-pine-info@cac.washington.edu  Mon Jan 30 17:35:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01693;
	Mon, 30 Jan 95 17:35:57 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14162;
	Mon, 30 Jan 95 17:24:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14153;
	Mon, 30 Jan 95 17:24:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ6zi-00038ZC; Mon, 30 Jan 95 17:02 PST
To: pine-info@cac.washington.edu
From: bfiltz@grits (Bill Filtz)
Subject: Mac 7100 and Pine
Date: 30 Jan 1995 16:59:43 GMT
Message-Id: <3gj5tv$mce@catfish.valdosta.peachnet.edu>


Anyone having success with dialing into an internet site using a Mac 7100
and a hayes compatible modem to emulate the VT100/102 keyboard and use
Pine? I've tried it with the ClarisWorks comm package and the Mac Comm  
Center software that came with the modem.

I have ^G, ^C, ^X, and ^T working. The cursor pad, delete, and some
others don't. Also, the screen doesn't always clear, particularly when going 
from the menu to the inbox folder index.

Thanks,

--
Bill Filtz                    Internet: bfiltz@grits.valdosta.peachnet.edu


From owner-pine-info@cac.washington.edu  Mon Jan 30 18:02:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02449;
	Mon, 30 Jan 95 18:02:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15915;
	Mon, 30 Jan 95 17:55:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15909;
	Mon, 30 Jan 95 17:55:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ7XU-00038VC; Mon, 30 Jan 95 17:37 PST
To: pine-info@cac.washington.edu
From: vzvz@netcom.com (Philip Zeyliger)
Subject: Non-standard INBOX locations and pine
Message-Id: <vzvzD2w73C.1M9@netcom.com>
Date: Tue, 24 Jan 1995 04:28:24 GMT


Recently, I have been trying to setup Pine here at Netcom and have run
into a problem:

Some users are reporting that pine doesn't see their INBOX'es.
The inboxes are located at $HOME/.mailbox/inbox.
This is unlike the unix standard /usr/local/spool/mail/$USER (or whatever).
I searched through the makefile and could not see any reference to this.
I did not want to modify the source code since I might not change the right
things.  So I tried to make a general config file.

I made the file setting "inbox-path=" line to whatever I need.
Then i try to execute the following script:

---
#!/bin/sh
#
# Script to launch pine

exec /u3/vzvz/pub/pine/pine -P /u3/vzvz/pub/pine/pine.conf $*
	
---
This gives me the following:

{The pine main menu screen}
[Opening "INBOX"...]
Bug in Pine detected: "Received abort signal".
Exiting pine.

I don't understand why this wouldn't work.  Also if someone could help
with what source code I should change.  I am also interested in what
pine looks to to find INBOX.  So far, i have found that if we set
the $MAIL variable it works.  Even though the MAIL thing is OK I would
like to figure out something in the sense of getting a general config file.

Thanks for all your help! and a great product too!

-- 
   |\__      ----------------------------------------------------      __/| 
  /   o\__                                                          __/o   \
 |    ___='                      Philip Zeyliger                   `=___    |
 |    \                          vzvz@netcom.com                       /    |
  \    \                                                              /    /
   >    \                  ---------> KOHb <---------                /    <
 _| KOHb |_               on the Internet Chess Server             _|      |_
|  ______  |                telnet chess.lm.com 5000              |  ______  |
|__________| ==================================================== |__________|


From owner-pine-info@cac.washington.edu  Mon Jan 30 18:15:41 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02940;
	Mon, 30 Jan 95 18:15:41 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15051;
	Mon, 30 Jan 95 18:11:17 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15045;
	Mon, 30 Jan 95 18:11:15 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ7kt-00038TC; Mon, 30 Jan 95 17:51 PST
To: pine-info@cac.washington.edu
From: "Mark E. Crane" <psu01055@odin.cc.pdx.edu>
Subject: Re: Filtering in Pine?
Date: Mon, 23 Jan 1995 19:45:21 -0800
Message-Id: <Pine.PTX.3.91.950123194405.1443D-100000@odin.cc.pdx.edu>
References: <3fgc5a$kh@sun0.urz.uni-heidelberg.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3fgc5a$kh@sun0.urz.uni-heidelberg.de> 

You can filter mail with a separate program, like procmail or filter, 
which may be onn your machine.  Look around for Nancy McGough's excellent 
filtering faq.  I only have a print copy, but it is at her WWW site, 
which you can get from her signature.


On 17 Jan 1995, Nina Kirchner wrote:

> Hello,
> 1. I don't know if it's FAQ, but I'm interested to filter my mail messages in special Folder when I get one.
> 
> How does that work?
> 
> 2. Is it possible to send bcc (blind carbon copy) in pine?
> 
> Thanx alot 
> 
> Cheers Nina
> 
> 


Mark Crane
psu01055@odin.cc.pdx.edu



From owner-pine-info@cac.washington.edu  Mon Jan 30 19:03:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04710;
	Mon, 30 Jan 95 19:03:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17127;
	Mon, 30 Jan 95 18:58:42 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17121;
	Mon, 30 Jan 95 18:58:40 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ8a3-00038TC; Mon, 30 Jan 95 18:44 PST
To: pine-info@cac.washington.edu
From: "Amy L. Lauderdale" <laall@cotton.vislab.olemiss.edu>
Subject: Re: Marking Multiple News posts Deleted
Date: Mon, 30 Jan 1995 19:35:24 -0600 (CST)
Message-Id: <Pine.SUN.3.90.950130193215.11447D-100000@cotton.vislab.olemiss.edu>
References: <D35rFs.G2C@crash.cts.com> <ellis.791396176@gmi.edu> <Pine.SUN.3.90.950129135703.25645C-100000@cotton.vislab.olemiss.edu> <Pine.SUN.3.91.950130110506.3881F-100000@nuthatch>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SUN.3.91.950130110506.3881F-100000@nuthatch> 

> > since joining this newsgroup I have seen several references to using
> > the select (;) command.  I have tried it in various screens and it
> > always tells me it is an unknown command.  I am using version
> > 3.90 on one account and 3.91 on another.
> > Can someone provide further information on this command?
> > 

> 
> when in the INDEX of a news group press
> ;aadTABENTER
> 
> This will:
> mark all items in news group as deleted ;aad
> TAB to folder list
> ENTER index of next newsgroup
> 
> Hope this helps
> 

I had tried this but it didn't work.  However, another kind soul (who I
would name but I already deleted the message) mailed me that I needed
to go in Setup and enable the aggregrate-command-set.  I did and the
above sequence works fine now.  

Thought I would share it on the list in case another lost soul is
confused as to why it won't work for them.


From owner-pine-info@cac.washington.edu  Mon Jan 30 19:17:59 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05137;
	Mon, 30 Jan 95 19:17:59 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17344;
	Mon, 30 Jan 95 19:11:27 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17338;
	Mon, 30 Jan 95 19:11:25 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ8ks-00038CC; Mon, 30 Jan 95 18:55 PST
To: pine-info@cac.washington.edu
From: roger@alex.ptc.org (Roger A. Wolcott)
Subject: Pine and Pegasus
Date: Mon, 30 Jan 1995 11:53:46 UNDEFINED
Message-Id: <roger.2.00884C2D@alex.ptc.org>


Fellow Pine Users,

I have a Linux box on my network that takes care of 
all outgoing mail using Sendmail.  However, when
I run the Windows version of Pegasus, and if  you're
not root, you cannot fetch your messages.  I says:
"Invalid Password" even when I know it is correct.
This may have something to do with the fact that when I 
bring up Pine on the Linux box,  there is a message
that "Can't open folder lock"and that it is readonly.

Thank you in advance for and light shed on this
predicament.

Roger Wolcott


From owner-pine-info@cac.washington.edu  Mon Jan 30 19:18:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05158;
	Mon, 30 Jan 95 19:18:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16234;
	Mon, 30 Jan 95 19:14:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16228;
	Mon, 30 Jan 95 19:14:00 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ8of-00038TC; Mon, 30 Jan 95 18:59 PST
To: pine-info@cac.washington.edu
From: Ray McAllister <mcallist@gate.net>
Subject: Re: Print result
Date: Mon, 30 Jan 1995 17:23:36 -0500 (EST)
Message-Id: <Pine.A32.3.90.950130172214.26183E-100000@hopi.gate.net>
References: <D377FC.3nu@cs.dal.ca>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D377FC.3nu@cs.dal.ca> 

What does the following mean when I hit the prYnt command in pine?
	mcallist print queue and print: null  null
				Thank you in advance

Ray McAllister, Prof (Emeritus) Ocean Eng., FAU, Boca Raton, FL 33064
Diving Dinosaur, Geologist/Oceanographer/Ocean Engineer, 43 years SCUBA
mcallist@gate.net (305) 426-0808, Author Diving Locations, Boynton/Dania




From owner-pine-info@cac.washington.edu  Mon Jan 30 19:18:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05179;
	Mon, 30 Jan 95 19:18:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16200;
	Mon, 30 Jan 95 19:11:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16194;
	Mon, 30 Jan 95 19:11:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ8hE-00038bC; Mon, 30 Jan 95 18:52 PST
To: pine-info@cac.washington.edu
From: dewing@gasou.edu (David Ewing)
Subject: Message sends over and over
Date: Mon, 30 Jan 1995 16:38:10
Message-Id: <dewing.25.0010A35C@gasou.edu>

I am running pine 3.05a on a ibm RS6000 with Aix 3.2.5.  One of our teachers 
sent mail to his students, and it appears that the mail is being sent over and 
over.  He may have used a dist list, I am not sure.  I have tried killing 
sendmail and restarting, but that does not appear to be working.  Thanks in 
advance.


From owner-pine-info@cac.washington.edu  Mon Jan 30 20:11:28 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06536;
	Mon, 30 Jan 95 20:11:28 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18222;
	Mon, 30 Jan 95 20:06:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18216;
	Mon, 30 Jan 95 20:06:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZ9Yr-00038YC; Mon, 30 Jan 95 19:47 PST
To: pine-info@cac.washington.edu
From: hfalken@x4u2.desy.de (Harald Falkenberg)
Subject: help: moving from elm to pine ?
Date: 30 Jan 1995 16:30:26 GMT
Message-Id: <HFALKEN.95Jan30173026@x4u2.desy.de>

I like to switch from elm to pine by useing an existing mail dircetory which 
is organized by elm. What have i to do that this old mails can be 
read within pine? What must be changed for the aliases etc?

Exist there any converter programs?

Please mail me your hints to
hfalken@x4u.desy.de

thank you all in advance

Harald 



From owner-pine-info@cac.washington.edu  Mon Jan 30 20:58:56 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07740;
	Mon, 30 Jan 95 20:58:56 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17786;
	Mon, 30 Jan 95 20:53:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17780;
	Mon, 30 Jan 95 20:53:28 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZAOW-00038WC; Mon, 30 Jan 95 20:40 PST
To: pine-info@cac.washington.edu
From: Ray McAllister <mcallist@gate.net>
Subject: Re: Home directory
Date: Mon, 30 Jan 1995 23:26:20 -0500 (EST)
Message-Id: <Pine.A32.3.90.950130232428.16326J-100000@hopi.gate.net>
References: <3dt0gr$8b2@cronkite.ocis.temple.edu>  <Pine.A32.3.91.950105093453.21569A-100000@smail.hrz.uni-giessen.de>  <Pine.A32.3.90.950110021643.36940A-100000@seminole.gate.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: QUOTED-PRINTABLE
In-Reply-To: <Pine.A32.3.90.950110021643.36940A-100000@seminole.gate.net>

This is a repost. I did not get any answers. Hope it isnt too much to=20
ask. Will appreciate any help for a newcomer (2=AB months on the net).
Thank you.

On Tue, 10 Jan 1995, Ray McAllister wrote:

> =09Question 1, Please help! How can I access or see what is in my "Home=
=20
> Directory"? I cannot seem to find it anywhere on either hard drive, to se=
e
> what is in it; to use it, or to delete it. Thanks a million.
> =09Question 2, Where or how can I get a manual for Pine?
> =09Question 3, When I go into rz to bring a pre-existing file into=20
> my home directory I sometimes end up with the Procom 2 screen telling me=
=20
> Port in use, yet I have hung up. How can I get rid of Port in use and=20
> continue with Procom and pine without closing everything back to C:?
> =09Ray McAllister  mcallist@gate.net
>=20


From owner-pine-info@cac.washington.edu  Mon Jan 30 21:28:54 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08561;
	Mon, 30 Jan 95 21:28:54 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19295;
	Mon, 30 Jan 95 21:18:28 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from tavor.openu.ac.il by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19289;
	Mon, 30 Jan 95 21:18:23 -0800
Received: by tavor.openu.ac.il id AA19435
     (5.67a8/IDA-1.5 for pine-info@cac.washington.edu); Tue, 31 Jan 1995 07:18:18 +0200
Date: Tue, 31 Jan 1995 07:18:17 +0200 (IST)
From: Shimon Winerich - Open University of Israel <shimon@tavor.openu.ac.il>
To: pine-info@cac.washington.edu
Subject: help signoff
Message-Id: <Pine.SUN.3.91.950131071731.18779D-100000@tavor>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Help ! how do I signoff this mailing list ?

Thank's in advance 

	Shimon



     .__________________________________________________________.
     |                                                          |
     | Shimon Winerich       Computer Department                |
     |                       Open University Of Israel          |
     |                       16 Klauzner st. Ramat Aviv         |
     |                       Phone      : 03-6460320/1          |
     |                       Fax        : 03-6460454            |
    /)                       E-mail: Shimon@tavor.openu.ac.il   (\
   / )                                                          ( \
  ( (|__________________________________________________________|) )
(((\ \)  /,)                                               / )  / //))/
(\\\\ \_/ /                                                \ \_/ /////
 \       /                                                  \       /
  \    _/                                                    \_    /





From owner-pine-info@cac.washington.edu  Tue Jan 31 00:03:01 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12448;
	Tue, 31 Jan 95 00:03:01 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21532;
	Mon, 30 Jan 95 23:58:00 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21526;
	Mon, 30 Jan 95 23:57:59 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZDFL-00038MC; Mon, 30 Jan 95 23:43 PST
To: pine-info@cac.washington.edu
From: hurtta@dionysos.fmi.fi (Kari E. Hurtta)
Subject: Re: Why Message-ID error???
Date: 25 Jan 1995 07:47:54 GMT
Message-Id: <3g4vna$jqu@kronos.fmi.fi>
References: <3g23sv$bq3@mars.mahidol.ac.th>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: Article <3g23sv$bq3@mars.mahidol.ac.th> of Tangsripairoj

ccsts@mucc.mahidol.ac.th (Songsri Tangsripairoj - CC) writes in 
comp.mail.sendmail:

»	I have just compile and config Sendmail8.6.9 for my host which 
»run on Solaris2.3. During this two days, I have tested it and I confront 
»with the problem that why the Message-ID is error.

»Message-ID: <Pine.SOL.3.91.950124122131.554A-100000@earth>

This Message-ID is generated by Pine -- it isn't generated by sendmail.

[ I will add comp.mail.pine as receiver. Perhaps Pine folks tell how to solve
  this error. ]

So your test mail don't indicate error in sendmail. 
--
- Kari E. Hurtta                             /  Elämä on monimutkaista
  Kari.Hurtta@Fmi.FI			     puh. (90) 1929 658
  {hurtta,root,Postmaster}@dionysos.fmi.fi


From owner-pine-info@cac.washington.edu  Tue Jan 31 00:35:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13057;
	Tue, 31 Jan 95 00:35:14 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20788;
	Tue, 31 Jan 95 00:30:14 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from is1.hk.super.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA20782;
	Tue, 31 Jan 95 00:30:12 -0800
Received: by is1.hk.super.net id AA22444
  (5.67b/IDA-1.5 for pine-info@cac.washington.edu); Tue, 31 Jan 1995 16:30:03 +0800
Date: Tue, 31 Jan 1995 16:30:03 +0800 (HKT)
From: Mr Kevin Yeung <keviny@HK.Super.NET>
To: Bill Filtz <bfiltz%grits@mx1.cac.washington.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: Mac 7100 and Pine
In-Reply-To: <3gj5tv$mce@catfish.valdosta.peachnet.edu>
Message-Id: <Pine.SUN.3.91.950131162744.22106A-100000@is1.hk.super.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 30 Jan 1995, Bill Filtz wrote:

> Anyone having success with dialing into an internet site using a Mac 7100
> and a hayes compatible modem to emulate the VT100/102 keyboard and use
> Pine? I've tried it with the ClarisWorks comm package and the Mac Comm  
> Center software that came with the modem.
> 
> I have ^G, ^C, ^X, and ^T working. The cursor pad, delete, and some
> others don't. Also, the screen doesn't always clear, particularly when going 
> from the menu to the inbox folder index.

I used Telix for Windows on a PC and had similar problem.  ^X, ^C and 
another few control codes worked, but not the cursor keys.  I emailed the 
people at TFW and they said they had no idea.  Procomm Plus for Windows 
works fine, though.  Any idea?  Thank you.

--
Kevin Yeung
email: keviny@hk.super.net




From owner-pine-info@cac.washington.edu  Tue Jan 31 03:18:26 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17065;
	Tue, 31 Jan 95 03:18:26 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22821;
	Tue, 31 Jan 95 03:00:26 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22815;
	Tue, 31 Jan 95 03:00:24 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZG0Q-00038PC; Tue, 31 Jan 95 02:40 PST
To: pine-info@cac.washington.edu
From: tecnic@tlti.tokem.fi (PeTrI pIeTiKaInEn)
Subject: Mailing list with Pine?
Date: 24 Jan 1995 10:45:39 GMT
Message-Id: <3g2loj$ch3@tethys.otol.fi>

I was wondering is it possible to create a mailing list with Pine, where 
everyone in the list can mail? I mean I created a list for our demo group 
with address books command S CreateList... but I don't know how other 
members could mail into it?

We have Pine v.3.87 

I hope someone could help us? Thanks in advance

--

Jay FX - member of BlacKOuT and Bitch Control  	: Be merry
email:	tecnic@tlti.tokem.fi			:    Be bright...
IRC:	JayFx					: - Carbon D


From owner-pine-info@cac.washington.edu  Tue Jan 31 03:57:00 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18118;
	Tue, 31 Jan 95 03:57:00 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24520;
	Tue, 31 Jan 95 03:41:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24514;
	Tue, 31 Jan 95 03:41:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZGfK-00038CC; Tue, 31 Jan 95 03:22 PST
To: pine-info@cac.washington.edu
From: nancym@ii.com (Nancy McGough)
Subject: Re: Pine and Reply-To: environment var
Message-Id: <ii.791482892@shell1.best.com>
Date: 30 Jan 95 16:23:51 GMT
References: <3gf3r4$tas@hearst.cac.psu.edu>

gsutter@gss115.rh.psu.edu (Gregory S. Sutter) writes:
>Is there a way to get Pine 3.91 to read my environment variable 'Reply-To'?
>I have been manually inserting the Reply-To line in _each_ letter I write, 
>and it is gettting quite annoying.

Here's an excerpt of the Pine FAQ about this.

------------
Subject: How do I define my own headers like Reply-To and Organization?

In Pine 3.90, and later versions, you can set Reply-To, Organization,
and other headers using the customized-hdrs variable.

1. From the Main Menu type s for Setup
2. Type c for Configuration
3. To change the value of the customized-hdrs variable:
   a) To use the Where command type: w
   b) At the prompt type: customized-hdrs
   c) To Add a value type: a
   d) At the prompt type: Organization: Your Organization Name
   e) Repeat steps c and d for other headers such ast Reply-To

   Note that Pine understands environment variables so you
   can use lines like the following (if the variables are set):
      Organization: $ORGANIZATION
      Reply-To: $REPLYTO

While reading a message that you've received you can view all headers
by typing h.  If h does not work you need to go to your configuration
menu and set the enable-full-header-cmd variable.

While composing a message you can view all the headers by placing the
cursor in the header region and typing ^R (view rich headers).

Note that customized headers are not available in Pine 3.89 and earlier.

------------
-- 
 /\_/\                     /\_/\                                     /\_/\
( o.o )  Nancy McGough    ( o.o )   http://www.jazzie.com/ii        ( @.@ )
 > ~ <   Infinite Ink      > ^ <    ftp://ftp.halcyon.com/pub/ii     > " <


From owner-pine-info@cac.washington.edu  Tue Jan 31 04:11:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19327;
	Tue, 31 Jan 95 04:11:33 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23435;
	Tue, 31 Jan 95 03:45:34 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA23429;
	Tue, 31 Jan 95 03:45:33 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZGjV-00038OC; Tue, 31 Jan 95 03:26 PST
To: pine-info@cac.washington.edu
From: brennan@cchs.su.edu.au (Luke Brennan)
Subject: Re: Q. about HUJI VMS Pine 3.91 beta 3
Date: 31 Jan 95 21:24:03 +1000
Message-Id: <1995Jan31.212403@cchs.su.edu.au>
References: <1732D14368S86.FLAVELL@cernvm.cern.ch>

In article <1732D14368S86.FLAVELL@cernvm.cern.ch>, FLAVELL@cernvm.cern.ch (Alan J Flavell) writes:
> Is there a better place for discussing the HUJI port of VMS Pine?

	This would be the best place, wouldn't it?

> I see some discussions here (and some where it is not clear whether
> the HUJI port is meant, or the one associated with PMDF), but
> perhaps there is a mailing list specifically for this package?

	The PMDF people (InnoSoft, is the company) are red-hot
	e-mail gurus. I can only assume they took 3.89 or whatever
	and worked it over into something robust.

	Yehavi@vms.huji.ac.il is the guy who's been porting to VMS.
	The HUJI port is simply like the rest of the net - he's
	trying to take the unix-oriented internet releases PINE
	and fit it into VMS.
	I've pointed out various things I've found, and the guy
	will probably look at it if/when he gets a chance.
	(just like the rest of us, he has real job :-})

> I am just starting to investigate the HUJI port.  I acquired
> PINE_3_91_BETA_3.ZIP to our VMS system, which uses Multinet, and
> built it with the Multinet option.  Everything seemed to go well.

	Yes, it'll compile cleanly. (the build script was still
	slightly yukko, but it's no big deal to fix up, and in 99% of
	cases it'll work straight out of the box)

	The NETLIB suite would probably be a good idea, yes?
	(that would mean it would work with any TCP/IP suite
	under VMS). I suppose if you (or anyone else) is fiddling
	with VMSisms, that'd be something to target.

  
> Problem I am having is that whenever I try to compose a message,
> it asks if I want to continue the postponed one.  If I say no, it
> works OK.  If I say yes or take the default, it crashes.  The
> README.VMS _says_ that "messages cannot be postponed".

	There are a number of 'gotchas', and Yehavi already knows
	about some of them. If you can fix them, then it saves
	him doing it :-) I suppose you could post to the net,
	or refer them to Yehavi directly. (but hey, if the PINE
	people see VMS patches, maybe they'll get integrated
	more readily in future versions, no?)
  
> What makes it think I have a postponed mail?

	I don't know - the PINE hackers here may be able to
	tell you, though :-)
  
> Also, can someone explain just what it means under 1. in "Restrictions"?
> It says "the user must not switch to another folder as long as NEWMAIL
> has items".  Does something terrible happen?

	No idea, but at least people are aware that VMS users are
	using it. My PINE users are swooning over it, despite the
	problems they've encountered.

	(one of the annoying ones is the ^C handling leaves a fair
	bit to be desired.. seems like it gets lost sometimes...)

	PINE continues to develop - so.. it's a Good Thing!

	Luke.



From owner-pine-info@cac.washington.edu  Tue Jan 31 04:14:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19396;
	Tue, 31 Jan 95 04:14:36 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24685;
	Tue, 31 Jan 95 03:55:20 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24679;
	Tue, 31 Jan 95 03:55:18 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZGvK-00038RC; Tue, 31 Jan 95 03:39 PST
To: pine-info@cac.washington.edu
From: md2jakob@mdstud.chalmers.se (Jakob Schlyter)
Subject: Take addr to dist list?
Date: 24 Jan 1995 11:32:51 GMT
Message-Id: <3g2oh3$d5b@nyheter.chalmers.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Is it possible to do a TakeAddr but add the address to a distribution
list instead? If not, this would be a nice function to add (3.92?).

/Jakob

-- 
Email:      jakob@cs.chalmers.se
Snailmail:  Jakob Schlyter, Ejdergatan 5, S-416 68 Gothenburg
Phone:      +46-31-707 08 36, +46-70-595 07 94, +46-74-010 86 31
URL:        http://www.mdstud.chalmers.se/~md2jakob/


From owner-pine-info@cac.washington.edu  Tue Jan 31 04:51:49 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20417;
	Tue, 31 Jan 95 04:51:49 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24212;
	Tue, 31 Jan 95 04:24:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24206;
	Tue, 31 Jan 95 04:24:11 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZHLd-00038RC; Tue, 31 Jan 95 04:06 PST
To: pine-info@cac.washington.edu
From: walterc@eccomp.icu.eushc.org (Walter C. Cooksey)
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 1995 12:23:47 GMT
Message-Id: <3g2rgj$h9h@moe.cc.emory.edu>
References: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu>

I find the easies thing to do is assume that it has been read within a
reasonable time after delivery -- just like paper inter-office mail.
I hold them responsible and act accordingly.  It would be a nice safety
feature (for them) if I knew it had/had not been read, but they are
responsible.  It will happen as it seems to be a feature in most pc email
systems.  I'd certainly rather bet my job on email than US Mail.





From owner-pine-info@cac.washington.edu  Tue Jan 31 04:52:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20446;
	Tue, 31 Jan 95 04:52:20 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25363;
	Tue, 31 Jan 95 04:26:39 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25357;
	Tue, 31 Jan 95 04:26:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZHOr-00038SC; Tue, 31 Jan 95 04:09 PST
To: pine-info@cac.washington.edu
From: bill@gilroy (Bill Hudson)
Subject: Re: Marking Multiple News posts Deleted
Message-Id: <Pine.SCO.3.91.950130091840.19060B-100000@gilroy>
Date: 30 Jan 95 17:19:34 GMT
References: <D35rFs.G2C@crash.cts.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D35rFs.G2C@crash.cts.com>

On Sun, 29 Jan 1995, Kelly Ford wrote:

> 
> Can anyone tell me how to mark multiple news messages as deleted with 
> Pine 3.91.  I love the ability to jump from group to group with the Tab 
> key but would like to know how to mark all the messages of a group as 
> deleted before leaving the group.  I'd like to not have to press the "d" 
> key multiple times to do this.

Use the ';' (Select) key, select (A)ll messages, (A)pply a command, (D)elete.


============================================================================
Bill Hudson; System Administrator; Robert Mann Packaging INC, Gilroy, CA USA 
bill@rmp.com rmp@garlic.com BHudson@ix.netcom.com 
Tel: 1.408.848.5440   Fax: 1.408.848.2063


From owner-pine-info@cac.washington.edu  Tue Jan 31 05:03:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20812;
	Tue, 31 Jan 95 05:03:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25600;
	Tue, 31 Jan 95 04:43:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25594;
	Tue, 31 Jan 95 04:43:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZHiy-00038QC; Tue, 31 Jan 95 04:30 PST
To: pine-info@cac.washington.edu
From: bill@gilroy (Bill Hudson)
Subject: Re: Pine Hiding domain name
Message-Id: <Pine.SCO.3.91.950130093515.24512A-100000@gilroy>
Date: 30 Jan 95 17:35:42 GMT
References: <Pine.SCO.3.91.950130092612.19060C-100000@gilroy>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SCO.3.91.950130092612.19060C-100000@gilroy>

On Mon, 30 Jan 1995, Bill Hudson wrote:

> Looks like PINE is hiding my domain name in the header of my messages.  
> It's coming over as 'bill@gilroy' instead of 'bill@rmp.com' like I 
> wanted. 
> 

TEST. 

============================================================================
Bill Hudson; System Administrator; Robert Mann Packaging INC, Gilroy, CA USA 
bill@rmp.com rmp@garlic.com BHudson@ix.netcom.com 
Tel: 1.408.848.5440   Fax: 1.408.848.2063


From owner-pine-info@cac.washington.edu  Tue Jan 31 05:07:47 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21046;
	Tue, 31 Jan 95 05:07:47 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24453;
	Tue, 31 Jan 95 04:43:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24447;
	Tue, 31 Jan 95 04:43:50 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZHiv-00038PC; Tue, 31 Jan 95 04:30 PST
To: pine-info@cac.washington.edu
From: bill@gilroy (Bill Hudson)
Subject: Pine Hiding domain name
Message-Id: <Pine.SCO.3.91.950130092612.19060C-100000@gilroy>
Date: 30 Jan 95 17:28:20 GMT
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hmm ... 

Looks like PINE is hiding my domain name in the header of my messages.  
It's coming over as 'bill@gilroy' instead of 'bill@rmp.com' like I 
wanted. 

Any idea how this happened?

============================================================================
Bill Hudson; System Administrator; Robert Mann Packaging INC, Gilroy, CA USA 
bill@rmp.com rmp@garlic.com BHudson@ix.netcom.com 
Tel: 1.408.848.5440   Fax: 1.408.848.2063


From owner-pine-info@cac.washington.edu  Tue Jan 31 06:17:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22981;
	Tue, 31 Jan 95 06:17:57 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25502;
	Tue, 31 Jan 95 05:53:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA25496;
	Tue, 31 Jan 95 05:53:56 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZInR-00038CC; Tue, 31 Jan 95 05:39 PST
To: pine-info@cac.washington.edu
From: dunk@liverpool.ac.uk (Mr D.A. Rose)
Subject: Re: 3 questions ? ? ? Mail, Unix, Internet.
Message-Id: <D38EsH.DIJ@liverpool.ac.uk>
Date: 30 Jan 95 18:45:52 GMT
References: <D29rpH.Gwo@freenet.carleton.ca> <3fghk3$ntc@hedunx.hedland.edu.au>

Robert Hart (hartr@hedunx.hedland.edu.au) wrote:
: David A Hosten (ao826@FreeNet.Carleton.CA) wrote:
: : I am posting this in the hope somewhere out there [over the rainbow ;) ]

[snip]

: : 2. (a) How may I retrieve posts to Usenet groups that my Freenet/University
: : accounts do not subscribe to? There must be some way of doing an FTP
: : equivalent to a site that collects the postings. (b) Is there a way of uucp
: : retrieving them from sites? (c) If so, is it then possible to e-mail a group
: : directly from the Pine mailer...what would be put into the To:  address
: : section? (d) Why is the location of usenet-news servers appear to be
: : so secret and inaccessible to the regular FTP public? Reason: there are some
: : alt.fan.* groups that we would like to pick up to do some research on
: : media influence.

: Hm, I don't know the answer to this one...

With tin, set the NNTPSERVER environment variable to the new news server
and start tin with the -r option. The problem now is finding out what news
server to connect to.

Check the tin man page for more info.

[snip]

: -- 
: Robert Hart                                  hartr@hedunx.hedland.edu.au
: Voice: +61 (0)91 72 0429                     Fax:   +61 (0)91 72 3560
: Hedland College, PMB 1, South Hedland WA 6722 Australia

Was it really necessary to crosspost to so many groups? I'd suggest not.
In that case, add to answer to (3), above.

Learn some netiquette.

Duncan
--
Your conscience never stops you from doing anything.  It just stops you
from enjoying it.


From owner-pine-info@cac.washington.edu  Tue Jan 31 07:09:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA24264;
	Tue, 31 Jan 95 07:09:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27616;
	Tue, 31 Jan 95 07:00:32 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27610;
	Tue, 31 Jan 95 07:00:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZJol-00038OC; Tue, 31 Jan 95 06:44 PST
To: pine-info@cac.washington.edu
From: jduche@creighton.edu (Joe Ducharme)
Subject: LINES env var and pico
Message-Id: <Pine.HPP.3.91.950130142818.19284A-100000@bluejay.creighton.edu>
Date: 30 Jan 95 20:31:14 GMT
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

If I set the LINES var to indicate more/less lines (ie: export LINES=30) 
pine seems to know this but pico goes back to the regular 24 lines page. 
My question, to those who have tried this, is how do I get pico to also 
acknowledge the new LINES variable? Thanx!...laters....

*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*
*:  Joe Ducharme                 jduche@creighton.edu      :* 
*:  Creighton University         Omaha, NE USA  68178      :*  
*:           << Joe's Roadside Attraction >>               :*
*:     << http://bluejay.creighton.edu/~jduche/ >>         :*
*: "Time flies like an arrow, Fruit flies like a banana."  :*
*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*


From owner-pine-info@cac.washington.edu  Tue Jan 31 08:02:19 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA25945;
	Tue, 31 Jan 95 08:02:19 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28501;
	Tue, 31 Jan 95 07:50:19 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from uu11.psi.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA28495;
	Tue, 31 Jan 95 07:50:15 -0800
Received: from morgana.pubserv.com by uu11.psi.com (5.65b/4.0.940727-PSI/PSINet) via UUCP;
        id AA08842 for ; Tue, 31 Jan 95 10:46:15 -0500
Received: by morgana.pubserv.com id AA28705
  (5.64+/IDA-1.3.3 for penev@pisa.Rockefeller.edu); Tue, 31 Jan 95 09:21:27 -0600
Date: Tue, 31 Jan 1995 09:21:24 -0600 (CST)
From: Brian Larkin <brianl@morgana.pubserv.com>
Subject: Re: IMAP in this week's Communications Week
To: Terry Gray <gray@cac.washington.edu>
Cc: Penio Penev <penev@pisa.Rockefeller.edu>, pine-info@cac.washington.edu
In-Reply-To: <Pine.ULT.3.92.950130161708.14914N-100000@shiva1.cac.washington.edu>
Message-Id: <Pine.3.89.9501310908.B27617-0100000@morgana.pubserv.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 30 Jan 1995, Terry Gray wrote:

> 
> Again, the dialup performance depends upon several implementation issues,
> including your SLIP parameters.  In addition, IMAP4 has a number of
> additions to permit more efficient access over slow links. 
>  

Has the IMAP4 specification been release yet? If so, can someone point me 
to a copy?  

-- Brian

Brian D. Larkin
Programming Supervisor
Publication Services, Inc.
brianl@pubserv.com


From owner-pine-info@cac.washington.edu  Tue Jan 31 08:10:37 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26351;
	Tue, 31 Jan 95 08:10:37 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27453;
	Tue, 31 Jan 95 07:51:55 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA27447;
	Tue, 31 Jan 95 07:51:53 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZKhB-00038CC; Tue, 31 Jan 95 07:40 PST
To: pine-info@cac.washington.edu
From: gerland@acsu.buffalo.edu (Jim Gerland)
Subject: My problems with the HUJI PINE 3.91 for VMS.
Message-Id: <D39y48.3wJ@acsu.buffalo.edu>
Date: Tue, 31 Jan 1995 14:40:56 GMT


Maybe some of these problems have been reported (or even hopefully fixed),
but here goes.

These are my notes in building/using PINE/PICO 3.91:

Everything built "OK" under Multinet (just ignored the few 'undefined'
messages).

BUGS:

PINE

  - When you get a message broadcast the line on the screen where the 
    broadcast is gets erased

  - Screen layout forces certain lines to wrap, such as the words (local)
    and (remote) on the Folders screen.

  - In response to answering "yes" to the message:

       Folder "sent-mail" in <[]> doesn't exist. Create?

    I receive the following error message:

       Can't create mailbox sent-mail: mailbox already exists]

  - eXpunge from INBOX goives the following message:

       No messages expunged from folder "INBOX"

  - Replying to email puts the following line in the message of the
    reply:

      On -1 xxx -1 V080GDK3@UBVMS wrote:

    Not converting Date and Time correctly when the mail is from someone 
    on the local node.

  - Same is true when doing an 'i'ndex of a folder.  The display looks like
    this:

       +   17  Jul  7 winer@ubvms.cc.buf    (538) Business Plan
       +   18  Jul 18 winer@ubvms.cc.buf    (539) Business Plan
           19  Aug  3 Jim Gerland - Netw    (603) Invoices - OUP & NPTN
           20  Aug 18 Jim Gerland - Netw    (714) Re: Business Plan
       +   21  xxx -1 V080GDK3@UBVMS        (124)
       +   22  xxx -1 V080GDK3@UBVMS         (71)

  - Also the Subject does not show up in the above 'i'ndex listing.

  - 'C'omposing a message gives the following message:

      Continue postponed composition (answering "No" won't erase it)?

    Answering 'Y'es does not continue

  - From the Main Menu, using the 'g'o command brings up the following
    prompt:

      GOTO folder in <Incoming Message Fol> :

    and responding with: []MAIL

    gives the following message:

      [No folder opened]

  - After reading and deleting a message in []MAIL, then choosing 'm'ain,
    the 'l'ist folders, then INBOX, I received the following program abort:

      %MAIL-I-RECLPLSWAIT, reclaiming deleted file space.  Please wait... R Rename
       GetMessage header failed, status=8290642 NextPage    A Add
      %MAIL-E-ILLCTXADR, illegal context block address

========================================================================

PICO

  - Prompts at bottom of screen on exit, read file, and confirm don't appear

  - Highlighted prompts start in column 80 and wrap to next line.

========================================================================

Migration Notes (collected while testing HUJI PINE 3.91 after using the 
  PMDF PINE 3.89:

  - PINERC.PINE needs to be renamed to .PINERC
  - PINE.ADDRESSBOOK needs to be renamed to .ADDRESSBOOK
  - XX.NEWSRC needs to be renamed to .NEWSRC
  - PRINT needs to be set in .pinerc
  - Default saved messages folder needs to be set to = (nothing)

Jim...
-- 
Jim Gerland  - Manager, Network Information Services    University at Buffalo
Academic Services, Computing & Information Technology   Buffalo, NY 14260
716.645.3557 Work                                       716.645.3734 FAX
gerland@acsu.buffalo.edu            URL: http://www.acsu.buffalo.edu/~gerland


From owner-pine-info@cac.washington.edu  Tue Jan 31 09:07:14 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29286;
	Tue, 31 Jan 95 09:07:14 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29697;
	Tue, 31 Jan 95 08:39:31 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA29691;
	Tue, 31 Jan 95 08:39:30 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZLPU-00038QC; Tue, 31 Jan 95 08:26 PST
To: pine-info@cac.washington.edu
From: IAN@MARS.SENECAC.ON.CA (IAN VAZ)
Subject: VMS Pine and MAIL.MAI
Message-Id: <1995Jan31.095122.160@venus.senecac.on.ca>
Date: 31 Jan 95 09:51:21 -0500


Hi Ya'll,

I have Pine running on a VMS system.  Works fine as long as you have
an existing MAIL.MAI file.  If you are a new VMS user who has does not have 
a MAIL.MAI file and then invokes PINE,...., craaassssshhh.  It dumps its
stack because no MAIL.MAI file is found.  
Does anybody have a workaround for this?  Thanks in advance.
Regards,
Ian


From owner-pine-info@cac.washington.edu  Tue Jan 31 09:22:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29981;
	Tue, 31 Jan 95 09:22:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00547;
	Tue, 31 Jan 95 09:04:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA00541;
	Tue, 31 Jan 95 09:04:44 -0800
Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13429;
	Tue, 31 Jan 95 09:04:32 -0800
Date: Tue, 31 Jan 1995 09:04:29 -0800 (PST)
From: Terry Gray <gray@cac.washington.edu>
To: Brian Larkin <brianl@morgana.pubserv.com>
Cc: Penio Penev <penev@pisa.Rockefeller.edu>, pine-info@cac.washington.edu
Subject: Re: IMAP in this week's Communications Week
In-Reply-To: <Pine.3.89.9501310908.B27617-0100000@morgana.pubserv.com>
Message-Id: <Pine.ULT.3.92.950131090302.11209C-100000@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

 
> Has the IMAP4 specification been release yet? If so, can someone point me 
> to a copy?  

Yes... The current docs that have been published are RFC-1730 thru 1733,
available from all the usual Internet RFC repositories or from 
ftp.cac.washington.edu in the /mail directory.

-teg


From owner-pine-info@cac.washington.edu  Tue Jan 31 10:45:11 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03522;
	Tue, 31 Jan 95 10:45:11 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02570;
	Tue, 31 Jan 95 10:36:08 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02564;
	Tue, 31 Jan 95 10:36:07 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZNI4-00038MC; Tue, 31 Jan 95 10:27 PST
To: pine-info@cac.washington.edu
From: offsite@crl.com (Lee (not F) Bailey)
Subject: Re: [Q] pine-debug* files -- Make it *STOP*
Date: 24 Jan 1995 15:34:15 GMT
Message-Id: <3g36ln$aua@nntp.crl.com>
References: <3g1cb0$dgd@nntp.crl.com> <Pine.SOL.3.91.950124025500.5514A-100000@mail>

Chip Old (fold@mail.bcpl.lib.md.us) wrote:
> On 23 Jan 1995, Lee (not F) Bailey wrote:

> > [snip]  
>  
> Pine creates those ".pine-debug..." files automatically each time it is 
> used.  The most recent is always .pine-debug1, the one previous to that 
> .pine-debug2, and so on up to .pine-debug4.  Obviously each time a new 
> .pine-debug1 is created, the old 1, 2, & 3 are renamed 2, 3, & 4 and the 
> old 4 is deleted.
>  
> You can suppress the creation of a .pine-debug file by using "pine -d 0"
> to start Pine, instead of just "pine", but why bother?  Those files don't
> take up much space and can be a useful diagnostic tool if Pine does
> something stupid. 
>  
> I had something strange happen a couple of times back when Pine 3.89 was
> the latest and greatest, where the number of .pine-debug files grew to
> well over the limit of four.  That was a long time ago and I don't
> remember what the total grew to, but it was a lot.  This was supposedly
> impossible, but there they were in my home directory.  Anyone else ever
> see this?  It hasn't happened to me with 3.90 or 3.91. 

I admit these files could be useful, but they clutter up my dir listing. 
Is there a way to redirect them to a folder?

--
______________________________________________________________________________
Lee Bailey	|  E-Mail:   offsite@crl.com
	User of Geoworks Ensemble instead of M$ Windoze
	Try the demo at ftp://arginine.umdnj.edu/pub/geos/publish
		     or ftp://ftp.mcs.com/mcsnet.users/jbarr/GeoPublish	


From owner-pine-info@cac.washington.edu  Tue Jan 31 10:48:53 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03613;
	Tue, 31 Jan 95 10:48:53 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01579;
	Tue, 31 Jan 95 10:36:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01573;
	Tue, 31 Jan 95 10:36:04 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZNAK-00038KC; Tue, 31 Jan 95 10:19 PST
To: pine-info@cac.washington.edu
From: vgabriel@gandalf.rutgers.edu (Vladimir Gabrielescu)
Subject: bug: readonly mailbox
Date: 31 Jan 1995 05:16:05 -0500
Message-Id: <3gl2l5$2t2@gandalf.rutgers.edu>

hey all

i've using (and supporting for my friends) pine 3.91 for a while now and i 
ran into a small problem which i have not encounter before. 

at start up i get :

Can't open mailbox lock, access is readonly. 

all myfiles have the right permissions and i have no other copies of pine 
running. oh yeah ... is a SunOS 4.1.3 machine .

any help would be appreciated

vlad


From owner-pine-info@cac.washington.edu  Tue Jan 31 10:51:20 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03747;
	Tue, 31 Jan 95 10:51:20 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01778;
	Tue, 31 Jan 95 10:41:48 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from is1.hk.super.net by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA01772;
	Tue, 31 Jan 95 10:41:45 -0800
Received: by is1.hk.super.net id AA00883
  (5.67b/IDA-1.5 for pine-info@cac.washington.edu); Wed, 1 Feb 1995 02:41:40 +0800
Date: Wed, 1 Feb 1995 02:41:39 +0800 (HKT)
From: Mr Kevin Yeung <keviny@HK.Super.NET>
To: pine-info@cac.washington.edu
Subject: Fcc problem
Message-Id: <Pine.SUN.3.91.950201021852.29742A-100000@is1.hk.super.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi all,

I have several entries in my addressbook whose fcc's aren't sent-mail. 
When I use the (C)ompose command to send a new message, the out-going mail
is correctly copied to the corresponding fcc.  But if I use the (R)eply
command to reply messages FROM these people, the out-going messages will
still go to sent-mail, which is not what I want.  I have to manually edit
the header everytime and I find this really troublesome.  Is there a way
to get things work (I'm using Pine 3.91)?  Or will Pine 3.92(?) checks the
addresses of all out-going mails, compare them with the entries in
addressbook and copy them to the correct folders?  Thank you.

--
Kevin Yeung
email: keviny@hk.super.net




From owner-pine-info@cac.washington.edu  Tue Jan 31 11:22:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05001;
	Tue, 31 Jan 95 11:22:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02395;
	Tue, 31 Jan 95 11:08:59 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA02389;
	Tue, 31 Jan 95 11:08:58 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZNd4-00038OC; Tue, 31 Jan 95 10:48 PST
To: pine-info@cac.washington.edu
From: chengman@umich.edu (Dennis Cheng)
Subject: Compiling PINE for VMS
Date: 31 Jan 1995 18:29:29 GMT
Message-Id: <3glvi9$6k3@lastactionhero.rs.itd.umich.edu>

Has anyone been able to compile PINE 3.91 for VMS using gcc? If so, could 
you send me a copy of the modified config and Makefiles?

Thanks.

Dennis Cheng


From owner-pine-info@cac.washington.edu  Tue Jan 31 12:11:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07461;
	Tue, 31 Jan 95 12:11:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03511;
	Tue, 31 Jan 95 11:56:25 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from lupine.nsi.nasa.gov by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA03505;
	Tue, 31 Jan 95 11:56:23 -0800
Received: (from mnewell@localhost) by lupine.nsi.nasa.gov (8.6.9/8.6.9) id OAA04561; Tue, 31 Jan 1995 14:55:14 -0500
Date: Tue, 31 Jan 1995 14:55:00 -0500 (EST)
From: "Michael C. Newell" <mnewell@lupine.nsi.nasa.gov>
To: Vladimir Gabrielescu <vgabriel@gandalf.rutgers.edu>
Cc: pine-info@cac.washington.edu
Subject: Re: bug: readonly mailbox
In-Reply-To: <3gl2l5$2t2@gandalf.rutgers.edu>
Message-Id: <Pine.SUN.3.91.950131145252.3565k-100000@lupine.nsi.nasa.gov>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 31 Jan 1995, Vladimir Gabrielescu wrote:

> i've using (and supporting for my friends) pine 3.91 for a while now and i 
> ran into a small problem which i have not encounter before. 
> 
> at start up i get :
> 
> Can't open mailbox lock, access is readonly. 

I've gotten that on occasion when I've had a suspended instance of Pine 
running that I forgot about.  The new Pine asks the old one for the lock, 
but the old one is suspended so it can't reply; hence the new Pine can't 
get the lock.  You might try

  $ ps -auxww | grep pine | grep yourname

where "yourname" is your username to see if there are any other Pine jobs 
running in your account.

Thanks,

Mike

+--------------------------------------+------------------------------------+
|Mike Newell                           | The opinions expressed herein are  |
|NASA Science Internet Network Systems | my own, and do not necessarily     |
|Sterling Software, Inc.               | reflect those of the NSI program,  |
|MNewell@nsipo.nasa.gov                | Sterling Software, NASA, or anyone |
|+1-202-434-8954                       | else.                              |
+--------------------------------------+------------------------------------+



From owner-pine-info@cac.washington.edu  Tue Jan 31 12:13:50 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07594;
	Tue, 31 Jan 95 12:13:50 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04436;
	Tue, 31 Jan 95 11:59:44 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04430;
	Tue, 31 Jan 95 11:59:43 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZOTx-00038MC; Tue, 31 Jan 95 11:43 PST
To: pine-info@cac.washington.edu
From: rhahm@aol.com (RHahm)
Subject: Questions about Pine and USENET
Date: 31 Jan 1995 08:20:17 -0500
Message-Id: <3gldeh$g4@newsbf02.news.aol.com>

Sorry for the dumb question but I have to ask since I do not know enough
about nntp and how Pine interacts with nntp.  But in Pine how do you mark
articles as being read?  Do you mark them for deletion then expunge the
folder?  Does this really delete the article from the nntp server disk or
does just mark the article as being read in the local user's .newsrc ??


Ronald Hahm
EMail: RHahm@aol.com


From owner-pine-info@cac.washington.edu  Tue Jan 31 12:35:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08437;
	Tue, 31 Jan 95 12:35:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04264;
	Tue, 31 Jan 95 12:26:29 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA04258;
	Tue, 31 Jan 95 12:26:27 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZOtr-00038KC; Tue, 31 Jan 95 12:10 PST
To: pine-info@cac.washington.edu
From: John Furman <johnf@sparc.nic.bc.ca>
Subject: Full Domain Name in 'From:' field
Message-Id: <Pine.SV4.3.91.950130155039.2549A-100000@sparc>
Date: Mon, 30 Jan 1995 16:01:23 -0800
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I posted a message awhile back asking for help with Pine not giving a fully 
qualified domain name in the 'From:' field of an outgoing message.  I 
received e-mail From: Barry Cornelius <Barry.Cornelius@durham.ac.uk>

In his message Mr. Cornelius related his experience with the 
'gethostbyname' function of SunOS 5.3 (a part of Solaris 2.3) not 
returning a FQDN.

This turned out to be the case on our system as well.  I then patched the 
appropriate routines in the Pine code.  It still didn't work.  As a last 
resort I changed the 'user-domain' field in my local '.pinerc'.  I had 
obtained the desired result.

My understanding is that the settings in the 'pine.conf.fixed' file 
over-ride both the 'pine.conf' and the '.pinerc' settings.

The 'user-domain' field was set in the 'pine.conf.fixed' file.  In fact 
that is when all this started.  My question is has anyone else had this 
problem?  Pine is working very well for us but I am curious as to why 
this is happening?

--
John Furman                       |
Computing Science (2nd Year)      |
North Island College              |
Comox, British Columbia, CA       |  E-mail: johnf@sparc.nic.bc.ca





From owner-pine-info@cac.washington.edu  Tue Jan 31 12:43:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08727;
	Tue, 31 Jan 95 12:43:58 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05226;
	Tue, 31 Jan 95 12:29:38 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05220;
	Tue, 31 Jan 95 12:29:37 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZOxw-00038PC; Tue, 31 Jan 95 12:14 PST
To: pine-info@cac.washington.edu
From: dewing@gasou.edu (David Ewing)
Subject: Changing the from line
Date: Tue, 31 Jan 1995 09:22:35
Message-Id: <dewing.26.000960B0@gasou.edu>

Pine 3.05 on AIX 3.2.5.   Several students at our institution are changing 
the FROM line in their outgoing mail.   For some reason, the sender line is 
not showing up either.   They are changing the address to GOD@UNIVERSE.
Needless to say, the teacher who is receiving most of the mail is curious who 
God really is.  Is there a way to insure that the sender will be correctly 
identified.  Thanks in advance.


From owner-pine-info@cac.washington.edu  Tue Jan 31 14:01:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA12804;
	Tue, 31 Jan 95 14:01:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07369;
	Tue, 31 Jan 95 13:52:36 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from asl-labs.bc.ca by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07363;
	Tue, 31 Jan 95 13:52:30 -0800
Received: by asl3.asl-labs.bc.ca (5.4R3.10/200.2.1.5)
	id AA04476; Tue, 31 Jan 1995 13:51:21 -0800
Date: Tue, 31 Jan 1995 13:51:20 -0800 (PST)
From: "Brian P. Hampson" <brian@asl3.asl-labs.bc.ca>
Subject: Re: Changing the from line
To: David Ewing <dewing@gasou.edu>
Cc: pine-info@cac.washington.edu
In-Reply-To: <dewing.26.000960B0@gasou.edu>
Message-Id: <Pine.3.89.9501311306.A4180-0100000@asl3>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 31 Jan 1995, David Ewing wrote:

> Pine 3.05 on AIX 3.2.5.   Several students at our institution are changing 
> the FROM line in their outgoing mail.   For some reason, the sender line is 
> not showing up either.   They are changing the address to GOD@UNIVERSE.
> Needless to say, the teacher who is receiving most of the mail is curious who 
> God really is.  Is there a way to insure that the sender will be correctly 
> identified.  Thanks in advance.

In later versions (we're up to 3.91 now I think), there IS no FROM line 
handed to you, and there is greater control for the system adminstrator.

B.

   ------------------------------------------------------------------------
   |Brian P. Hampson                  Internet: brian@asl-labs.bc.ca      |
   |System Administration,                      			  |
   |Analytical Service Labs           Fidonet : Brian Hampson 1:153/733   |
   |Vancouver, BC                                                         |
   |                                                                      |
   |               Specialists in Environmental Chemistry                 | 
   |                                                                      |
   ------------------------------------------------------------------------



From owner-pine-info@cac.washington.edu  Tue Jan 31 14:10:34 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13371;
	Tue, 31 Jan 95 14:10:34 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06826;
	Tue, 31 Jan 95 14:04:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06820;
	Tue, 31 Jan 95 14:04:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZQRa-00038WC; Tue, 31 Jan 95 13:49 PST
To: pine-info@cac.washington.edu
From: jbryans@csulb.edu (Jack Bryans)
Subject: How to get NOOP out of pine?
Date: 31 Jan 1995 21:46:12 GMT
Message-Id: <JBRYANS.95Jan31134612@tern.csulb.edu>

Is there any way to build pine so that it doesn't send "NOOP" out the nntp
port?

Jack


From owner-pine-info@cac.washington.edu  Tue Jan 31 14:22:03 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14216;
	Tue, 31 Jan 95 14:22:03 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07818;
	Tue, 31 Jan 95 14:11:12 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from email.ir.miami.edu by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07812;
	Tue, 31 Jan 95 14:11:10 -0800
Received: by email.ir.miami.edu id AA14585
  (5.65c+/IDA-1.4.4 for pine-info@cac.washington.edu); Tue, 31 Jan 1995 17:08:28 -0500
Date: Tue, 31 Jan 1995 17:08:28 -0500 (EST)
From: "Robyn T. Steiner" <rsteiner@students.miami.edu>
Subject: help
To: pine-info@cac.washington.edu
Message-Id: <Pine.3.89.9501311756.N13232-0100000@email.ir.miami.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

how do you change a password?



From owner-pine-info@cac.washington.edu  Tue Jan 31 14:42:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA15539;
	Tue, 31 Jan 95 14:42:09 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08523;
	Tue, 31 Jan 95 14:35:40 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08517;
	Tue, 31 Jan 95 14:35:38 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZQrp-00038QC; Tue, 31 Jan 95 14:16 PST
To: pine-info@cac.washington.edu
From: Barry Landy <bl10@cus.cam.ac.uk>
Subject: Re: Need to secure pine
Date: Tue, 24 Jan 1995 17:35:17 +0000
Message-Id: <Pine.SUN.3.91.950124173442.24402T-100000@apus.cus.cam.ac.uk>
References: <3g1e2s$5sk@case.cyberspace.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g1e2s$5sk@case.cyberspace.com> 

On 23 Jan 1995, Jack Valko wrote:

> I would like to know if there is some way to set a configuration in pine 
> so that users can't change it from the Setup menu.  Specifically, I want 
> to restrict the alternate editor feature.  I have specified 
> 'no-enable-alternate-editor' in pine.conf and pine.conf.fixed but this 
> doesn't seem to do it.  Can anyone help?
> 
We have the following set in pine.conf.fixed, and it seems to do the job:-

no-enable-alternate-editor-cmd,
no-always-use-alt-editor,
no-enable-alternate-editor-implicitly,


=======================================================================
Barry Landy, Head of Systems and Development,
University of Cambridge Computing Service
Barry.Landy@ucs.cam.ac.uk      0-1223-334713   +44-1223-334713



From owner-pine-info@cac.washington.edu  Tue Jan 31 15:13:46 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA17534;
	Tue, 31 Jan 95 15:13:46 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08396;
	Tue, 31 Jan 95 15:01:02 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08371;
	Tue, 31 Jan 95 15:00:58 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZRL4-00038QC; Tue, 31 Jan 95 14:46 PST
To: pine-info@cac.washington.edu
From: hobbs@uofport.edu (Eric A. Hobbs)
Subject: Pine Bug?
Date: 24 Jan 1995 10:29:10 -0800
Message-Id: <3g3gtm$g9e@wally.uofport.edu>

I don't know if this is in the documentation or in a FAQ, but I've found 
a way to crash Pine (I've tried v3.89 and v3.91).

A few users and I were able to crash Pine by simply changing the 
capitalization of the first letter of an address book nickname.  We're 
running SunOS 4.1.3_U1 and 4.1.4.  

Is this a documented thing? 

--Eric Hobbs

-- 
------------------------------------------------------------------------------
  Eric A. Hobbs          (hobbs@uofport.edu)    - -- ---=- -===-====(-: 
  UNIX System Manager,   University of Portland      :-o===-==--=--- -- - 
------------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Tue Jan 31 15:40:33 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18801;
	Tue, 31 Jan 95 15:40:33 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10245;
	Tue, 31 Jan 95 15:34:51 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10239;
	Tue, 31 Jan 95 15:34:50 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZRlS-00038KC; Tue, 31 Jan 95 15:13 PST
To: pine-info@cac.washington.edu
From: pisati@pippo.sm.dsi.unimi.it (Stefano Pisati IW2JXK)
Subject: Where src for HP ?
Date: 24 Jan 1995 10:39:48 +0100
Message-Id: <3g2ht4$6gg@pippo.sm.dsi.unimi.it>

I need to compile Pine on a HP-UX server and I need the source
ported to HP-UX... I've only found src and makefile only for
other plataform. Where can I find src for HP ???

		  Tnx in advance !!!

                    73 de -_ Stefano _-

PS: Please, reply via e-mail. Tnx !!!


       "Stat rosa pristina nomine nomina nuda tenemus"
----------------------------------------------------------------
Stefano Pisati  IW2JXK          Internet: pisati@dsi.unimi.it
PGP:  finger pisati@ghost.dsi.unimi.it  or
      e-mail pgp@dsi.unimi.it with Subject: GET Pisati
     http://www.dsi.unimi.it/Users/Students/pisati/home
----------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Tue Jan 31 15:41:31 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18911;
	Tue, 31 Jan 95 15:41:31 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09337;
	Tue, 31 Jan 95 15:34:53 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09331;
	Tue, 31 Jan 95 15:34:52 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZRmD-00038MC; Tue, 31 Jan 95 15:14 PST
To: pine-info@cac.washington.edu
From: Soren Larsen <larsen@imada.ou.dk>
Subject: Sorting vs. new mail info
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.SUN.3.91.950131172403.26921A-100000@berlioz>
Mime-Version: 1.0
Date: Tue, 31 Jan 1995 16:33:11 GMT

When new mail arrives Pine will inform me by beeping and listing pertinent
information near the bottom of the screen.  However, since I have
configured the program to sort letters by date, the first message is
almost immediately overwritten by a rather useless confirmation that the
mail box has indeed been sorted.  It seems the two pieces of information do
not have the same level of interest.  Any way I can get rid of the latter? 

(Pine 3.91 under SunOS 4.1)

Apart from this minor problem it is a brilliant program.

--
Soren Larsen                        URL: http://www.imada.ou.dk/~larsen/
Dept. of Math. & Computer Science   Email:            larsen@imada.ou.dk 
Odense University, Campusvej 55     phone:    +45 66 15 86 00, ext. 2312 
DK-5230 Odense M, Denmark           fax  :    +45 65 93 26 91



From owner-pine-info@cac.washington.edu  Tue Jan 31 16:16:42 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA20602;
	Tue, 31 Jan 95 16:16:42 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10952;
	Tue, 31 Jan 95 16:06:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10946;
	Tue, 31 Jan 95 16:06:56 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZSJY-00038KC; Tue, 31 Jan 95 15:48 PST
To: pine-info@cac.washington.edu
From: pjh@mccc.edu (Pete Holsberg)
Subject: Re: Script as printer command ???
Message-Id: <D2x8x1.57w@mccc.edu>
Date: Tue, 24 Jan 1995 18:05:24 GMT
References: <D2CwB4.498@tecoma.mccc.edu> <Pine.SUN.3.91.950115170653.22858A-100000@linda.teleport.com>

Knute Snortum (knute@teleport.com) wrote:

: On Fri, 13 Jan 1995, Pete Holsberg wrote:

: > I would like to use the following script as my printer command,
: > with <???> representing the name of the current email message.
: > How do I specify the name???
: > 
: > cat <????> | jetpr -h <???> | lp -dlj
: > 

: I'm no expert, but I don't think you need the file name at all.  In fact, 
: I would try just:

:   jetpr -h | lpr -dlj

: and see what happens.

"jetpr | lp -dlj" (without quotes) worked.


From owner-pine-info@cac.washington.edu  Tue Jan 31 16:25:30 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21342;
	Tue, 31 Jan 95 16:25:30 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10395;
	Tue, 31 Jan 95 16:16:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from [141.206.9.110] by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10389;
	Tue, 31 Jan 95 16:16:03 -0800
Received: from hostsw7.ElSegundoCA.NCR.COM (hostsw7.ElSegundoCA.ATTGIS.COM) by mailhost.ElSegundoCA.ATTGIS.COM (4.1/SMI-4.1)
	id AA05417; Tue, 31 Jan 95 16:15:17 PST
Received: by hostsw7.ElSegundoCA.NCR.COM (4.1/SMI-4.1)
	id AA13937; Tue, 31 Jan 95 16:15:25 PST
Date: Tue, 31 Jan 1995 16:15:22 -0800 (PST)
From: Steven Feinholz <sf3@ElSegundoCA.ATTGIS.COM>
X-Sender: sf3@hostsw7
To: pine-info@cac.washington.edu
Subject: Signature files at bottom
Message-Id: <Pine.SUN.3.91.950131161053.13826K-100000@hostsw7>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have set the signature-at-bottom in my Configuration Setup and
have experienced the following:

1) When Replying to an email message while including the original
   text, the signature file gets appended to the end of the
   email.

2) When Forwarding an email to another destination, the signature
   file gets placed BEFORE the included text, instead of at the
   bottom of the entire email message.

Is this the normal operation of "signature-at-bottom" or is this
a bug?

________________________________________________________________________
 ====  AT&T        | Steven Feinholz        | VOICEplus: 427-5945
=--=== Global      | Client Software        | Phone:     (310) 524-5945
=--=== Information | 100 N. Sepulveda Blvd. | FAX:       (310) 524-5515
 ====  Solutions   | El Segundo, Ca  90245  | sf3@ElSegundoCA.ATTGIS.com
________________________________________________________________________




From owner-pine-info@cac.washington.edu  Tue Jan 31 16:30:09 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA21772;
	Tue, 31 Jan 95 16:30:09 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10638;
	Tue, 31 Jan 95 16:25:15 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA10632;
	Tue, 31 Jan 95 16:25:14 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZSgD-00038KC; Tue, 31 Jan 95 16:12 PST
To: pine-info@cac.washington.edu
From: dhollis@clark.net (Miracle Man)
Subject: PC-PINE->Solaris 2.3 Prob
Date: 31 Jan 1995 18:10:35 GMT
Message-Id: <3gluer$le5@clarknet.clark.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

I have a Sparc 2 running Solaris 2.3, the IMAP binary from
cac.washington.edu and Pine 3.91 (works great).  I am using it as a server
for PC-Pine (workstations running WFW 3.11, MS TCP/IP 32 stack) but
PC-Pine likes to give me trouble.  What happens with the PC-Pine is I can
usually (not always though) connect to the server and open the INBOX. 
Then, when I go to read messages, the system freezes (well, Pine, not the
whole system) and after every 15 secs or so, I get a "no reply from server
for x seconds" and after a minute or so, I can break the IMAP connection. 
This is a very consistent problem, thogh when/where it shows up is
somewhat random.  If anyone has any suggestions on how to fix this
problem, please let me know. 



From owner-pine-info@cac.washington.edu  Tue Jan 31 17:23:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA27560;
	Tue, 31 Jan 95 17:23:35 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13154;
	Tue, 31 Jan 95 17:11:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13148;
	Tue, 31 Jan 95 17:11:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZTJn-00038SC; Tue, 31 Jan 95 16:53 PST
To: pine-info@cac.washington.edu
From: pjh@mccc.edu (Pete Holsberg)
Subject: Re: Need HELP! BinHEX conversion?
Message-Id: <D2x9pI.5KE@mccc.edu>
Date: Tue, 24 Jan 1995 18:22:30 GMT
References: <3fmv6r$86n@kaiwan009.kaiwan.com> <Pine.A32.3.91.950120100755.27547B-100000@rzserv2.fh-lueneburg.de>

Ralf Matthies (matthies@rzserv2.fh-lueneburg.de) wrote:
: On 19 Jan 1995, Richard Hsiung wrote:

: > I got a mail from someone with an attachment (supposedly), well, in the 
: > message, it tells me I need BinHex 4.0 to convert it?!  Where do I find 
: > BinHex and how do I get this attachment back into file form?

: you will find BinHex on the following aFTP servers:

:               ftp.demon.co.uk     /simtel20/msdos/mac/binhex13.zip
:               micros.hensa.ac.uk  /mirrors/simtel/msdos/mac/binhex13.zip

: PS: Ask me, if you have more questions... ;-)


OK. Where is BINHEX for Unix?





From owner-pine-info@cac.washington.edu  Tue Jan 31 17:42:36 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28206;
	Tue, 31 Jan 95 17:42:36 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12795;
	Tue, 31 Jan 95 17:35:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12789;
	Tue, 31 Jan 95 17:35:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZTim-00038SC; Tue, 31 Jan 95 17:19 PST
To: pine-info@cac.washington.edu
From: rick@helix.nih.gov (Rick Troxel)
Subject: Re: several Pine suggestions
In-Reply-To: glenn@uga.edu's message of 23 Jan 1995 13: 52:12 -0800
Message-Id: <RICK.95Jan31132347@helix.nih.gov>
References: <Pine.OSF.3.91a.950123112810.21590B-100000@saul4.u.washington.edu>
Date: Tue, 31 Jan 1995 18:23:47 GMT

In article
<Pine.A32.3.91.950123162021.34575E-100000@creator.ucns.uga.edu>
glenn@uga.edu (Glenn Leavell) writes:

   > > 4)  Add an option that makes the 'n' (NextMsg) command in the
   > >     INDEX skip over messages marked for deletion.
   > 
   > Try the [TAB] key. You might need to set some options in your 
   > configuration. Basically, it will cause you to jump to the next 
   > new/unread message.

   Yes, I use it regularly.  But, it only goes to the next new/unread
   message.  Several new Pine users here have mentioned to me that they
   would like to be able to quickly be able to get to the next message
   that has not been marked for deletion.  Maybe that's being too picky,
   though.

With the delete-skips-deleted feature selected, the above task can be
performed in 1 to 2 keypresses: Just press N to advance to the very next
message.  If it's marked for deletion (check the upper right corner),
press D and you're there; otherwise you're _already_ there.
--
Rick Troxel     Rick_Troxel@nih.gov     rick@helix.nih.gov     301/496-4823
///////////////////////////////////////////////////////////////////////////
     All effort and exertion put forth by man from the fullness of his
     heart is worship, if it  is prompted  by the  highest motives and
     the will to do service to humanity.                 --Abdu'l-Baha


From owner-pine-info@cac.washington.edu  Tue Jan 31 17:55:40 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28639;
	Tue, 31 Jan 95 17:55:40 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14189;
	Tue, 31 Jan 95 17:50:41 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14183;
	Tue, 31 Jan 95 17:50:39 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZTw5-00038VC; Tue, 31 Jan 95 17:32 PST
To: pine-info@cac.washington.edu
From: Leigh A Johnson <ljohnso9@osf1.gmu.edu>
Subject: Re: how to set up news on pine; do i need imap?
Date: Fri, 27 Jan 1995 15:41:40 -0500
Message-Id: <Pine.OSF.3.91.950127153831.25451C-100000@osf1.gmu.edu>
References: <3g9h4t$dng@abalone.ucsb.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3g9h4t$dng@abalone.ucsb.edu> 


On 26 Jan 1995, Joyce Y. Wong wrote:

> 
> how do i set up my pine account so i can read news there?
> which configuration item is it?
> 
> i normally read news with trn
> 
> thanks
> joyce

from Pine main menu, go into setup, then into configuration.  On the 
first page of the config stuff, enter news.gmu.edu where it asks for news 
server (nntp-site).  exit all the way out of pine, then go back in and 
look at your folder lists.  this will pull in all of the news groups, so 
you'll have to go and unsubscribe to any you've already unsubscribed to 
in tin.  Also, they'll be listed in alpha order.  I'm still working on 
how to rearrange the order they're listed in ... if anyone knows, feel 
free (please!) to fill me in.



From owner-pine-info@cac.washington.edu  Tue Jan 31 18:24:43 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA29693;
	Tue, 31 Jan 95 18:24:43 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13509;
	Tue, 31 Jan 95 18:18:30 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA13503;
	Tue, 31 Jan 95 18:18:29 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZURF-00038PC; Tue, 31 Jan 95 18:04 PST
To: pine-info@cac.washington.edu
From: the mole <markusg@darkwing.uoregon.edu>
Subject: Re: Pine and procmail
Date: Tue, 31 Jan 1995 17:01:48 -0800
Message-Id: <Pine.SOL.3.91.950131165631.11008D-100000@darkwing>
References: <3gmjgo$oht@blaze.cs.jhu.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3gmjgo$oht@blaze.cs.jhu.edu> 

On 1 Feb 1995, Felix the Cat wrote:

> Well, I've been wanting to sort my mail into different inboxs for a long 
> time. And then I heard about "procmail" I found myself a copy and have it 
> compiled on my acc't. My question is ... how in the world do you 
> configure it to work with pine? how would i sort my mail by person and 
> listserv? i've read the documentation, but i'm not sure how all of these 
> examples given apply to pine itself.
> any help would be appreciated. please em'l your suggestions to me at 
> felix@jhu.edu
> 
> -- 
> ------------------------------------------------------------------------------
> Why do babies starve when there's ====--| Shreyas Ravishankar is
> enough food to feed the world? =======--| Felix@JHU.edu
> Why when there's so many of us are ===--| finger : sravi@newton.cs.jhu.edu

procmail doesn't care what reader you use. You just have to set the 
variable MAILDIR to point at your mail directory (which in the case of 
pine is $HOME/mail). And besides, a simple procmail recipe doesn't sort 
mail to inboxes but to folders.

hth,

tm
--
      /               . . . . . . . . . . . . . . . . . . . . . . . . . . .
__  __/   __  __     . . . . . . . . . . . . . . . . . . . . . .  the mole
   /     /   /   /  . . . . . . . . . . . .  markusg@darkwing.uoregon.edu
__/   __/ __/ __/  . . . . . . . . http://darkwing.uoregon.edu/~markusg/



From owner-pine-info@cac.washington.edu  Tue Jan 31 18:58:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA00815;
	Tue, 31 Jan 95 18:58:25 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15215;
	Tue, 31 Jan 95 18:54:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15209;
	Tue, 31 Jan 95 18:54:06 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZV1j-00038SC; Tue, 31 Jan 95 18:42 PST
To: pine-info@cac.washington.edu
From: harmonr@coho.halcyon.com (robert harmon)
Subject: PICO & SPELL checker
Date: 24 Jan 1995 18:29:06 GMT
Message-Id: <3g3gti$d38@news.halcyon.com>

For some time now I've been frustrated by the spell checker in PICO. I 
use a lot of words that are not in SPELL's default dictionary and wanted 
a better way of bypassing these words than pressing the space bar. After 
some digging I've come up with the following. If it's already common 
knowledge pardon the redundancy. If it's not it might make life a bit 
easier. BTW - I tried ISPELL as a substitute for SPELL but found it klunky 
and confusing.

The following works for those who use PICO as their default editor and 
SPELL as their spell checker. I haven't checked this for other editors.

To create a custom dictionary for SPELL:
- Two files will be created in your HOME directory:

  1 - New words; an ascii file - sorted one word per line - caps 
      don't seem to matter (I named mine .newwords).

  2 - New dictionary; a hashed file (I named mine .newhlista).

- From the UNIX prompt key: 
  cat .newwords | spellin /usr/dict/hlista > .newhlista
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  (The above creates a new custom dictionary.)

  cat .newwords | spellout .newhlista
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  (The above compares new words to words in custom dictionary.)

- Edit your .login file to include:
  setenv SPELL 'spell -d .newhlista'
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Logoff & log back into the system to enable changes made to .login 
environment variables. Now when you use the ^T within PICO SPELL will 
check for your custom dictionary as specified in .login file.

Hope this helps,
	Robert H. Harmon (halcyon.com)
--
	Chris Harmon & Associates
	Management & Training Consultants
	PO Box 2756,  Kirkland, WA 98083-2756
	(206) 820-3204 Vox (206) 820-4807 Fax





From owner-pine-info@cac.washington.edu  Tue Jan 31 19:09:35 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA01240;
	Tue, 31 Jan 95 19:09:35 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14296;
	Tue, 31 Jan 95 19:04:45 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14290;
	Tue, 31 Jan 95 19:04:44 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZV4K-00038TC; Tue, 31 Jan 95 18:45 PST
To: pine-info@cac.washington.edu
From: Rahul Dhesi <dhesi@rahul.net>
Subject: Re: Handling Return Receipts within PINE
Date: 24 Jan 1995 19:55:14 GMT
Message-Id: <3g3lv2$i90@hustle.rahul.net>
References: <Pine.ULT.3.91.950121103238.4008D-100000@admin.aurora.edu> <3g2rgj$h9h@moe.cc.emory.edu>

In <3g2rgj$h9h@moe.cc.emory.edu> walterc@eccomp.icu.eushc.org (Walter
C. Cooksey) writes:

>I find the easies thing to do is assume that it has been read within a
>reasonable time after delivery -- just like paper inter-office mail.

Read receipts are a common enough question among my users that I have a
standard reply.  The hint in the last paragraph is much more reliable
than any automatic mechanism ever will be.  Automated read receipts do
not tell you whether your message was read by the user, only if it was
read by his software.

   There is currently no universal mechanism for getting verification
   of email delivery.  One method that almost works is to include a
   header in your message:

	Return-Receipt-To: username@rahul.net

   IF the recipient's system uses 'sendmail' for mail transport, it
   will send back an automated reply saying it received the message.
   But it doesn't guarantee that it reached the recipient's mailbox,
   only that it reached the recipient's host.

   A requirement to get confirmation of mail actually being read by the
   recipient is that sending and receiving hosts have a common protocol
   for this.  This is not the case on the Internet, as sites are
   autonomous and use a variety of software.  The chances of it
   happening in the future is also small:  many people consider it a
   violation of their privacy.

   The best way to find out if somebody read your mail is to send a
   brief follow-up message saying "Hi, I was just wondering if my
   previous message reached...I can't tell if my email is getting
   out."  This will usually result in a quick reply.

-- 
Rahul Dhesi <dhesi@rahul.net>


From owner-pine-info@cac.washington.edu  Tue Jan 31 20:00:25 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02615;
	Tue, 31 Jan 95 20:00:25 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15103;
	Tue, 31 Jan 95 19:55:22 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15097;
	Tue, 31 Jan 95 19:55:21 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZVvq-00038QC; Tue, 31 Jan 95 19:40 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Changing the from line
Date: Tue, 31 Jan 1995 13:10:45 -0800
Message-Id: <Pine.ULT.3.92.950131130823.18634E-100000@shiva1.cac.washington.edu>
References: <dewing.26.000960B0@gasou.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <dewing.26.000960B0@gasou.edu>


Are you sure they are actually doing it with Pine?  There is a very easy hack
to send fake mail that has nothing to do with Pine.  I seem to remember that
you could play some games with postponed messages too.  The current Pine 3.91
release should do a better job of identifying outgoing mail, but there is
only so much we can do... :(

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On Tue, 31 Jan 1995, David Ewing wrote:

> Date: Tue, 31 JAN 1995 09:22:35
> From: David Ewing <dewing@gasou.edu>
> Newgroups: comp.mail.pine
> Subject: Changing the from line
> 
> Pine 3.05 on AIX 3.2.5.   Several students at our institution are changing 
> the FROM line in their outgoing mail.   For some reason, the sender line is 
> not showing up either.   They are changing the address to GOD@UNIVERSE.
> Needless to say, the teacher who is receiving most of the mail is curious who 
> God really is.  Is there a way to insure that the sender will be correctly 
> identified.  Thanks in advance.
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan 31 20:00:44 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA02640;
	Tue, 31 Jan 95 20:00:44 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16254;
	Tue, 31 Jan 95 19:55:21 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16248;
	Tue, 31 Jan 95 19:55:19 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZVvh-00038MC; Tue, 31 Jan 95 19:40 PST
To: pine-info@cac.washington.edu
From: David L Miller <dlm@cac.washington.edu>
Subject: Re: Questions about Pine and USENET
Date: Tue, 31 Jan 1995 13:07:25 -0800
Message-Id: <Pine.ULT.3.92.950131130637.18634D-100000@shiva1.cac.washington.edu>
References: <3gldeh$g4@newsbf02.news.aol.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <3gldeh$g4@newsbf02.news.aol.com>


Use Delete and eXpunge.  It does not actually delete the messages and you 
can get them back with '&'.

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (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

On 31 Jan 1995, RHahm wrote:

> Date: 31 JAN 1995 08:20:17 -0500
> From: RHahm <rhahm@aol.com>
> Newgroups: comp.mail.pine
> Subject: Questions about Pine and USENET
> 
> Sorry for the dumb question but I have to ask since I do not know enough
> about nntp and how Pine interacts with nntp.  But in Pine how do you mark
> articles as being read?  Do you mark them for deletion then expunge the
> folder?  Does this really delete the article from the nntp server disk or
> does just mark the article as being read in the local user's .newsrc ??
> 
> 
> Ronald Hahm
> EMail: RHahm@aol.com
> 
> 


From owner-pine-info@cac.washington.edu  Tue Jan 31 20:17:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03141;
	Tue, 31 Jan 95 20:17:21 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16539;
	Tue, 31 Jan 95 20:13:04 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16533;
	Tue, 31 Jan 95 20:13:02 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZWE1-00038KC; Tue, 31 Jan 95 19:59 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Signature files at bottom
Date: 1 Feb 1995 01:42:36 GMT
Message-Id: <3gmouc$42o@cronkite.ocis.temple.edu>

Comes here Mr. Steven Feinholz with this opinion in the "comp.mail.pine" group
in this article on 31 Jan 1995 16:22:13 -0800:

 +   I have set the signature-at-bottom in my Configuration Setup and
 +   have experienced the following:

 +   1) When Replying to an email message while including the original
 +      text, the signature file gets appended to the end of the
 +      email.

 +   2) When Forwarding an email to another destination, the signature
 +      file gets placed BEFORE the included text, instead of at the
 +      bottom of the entire email message.

 +   Is this the normal operation of "signature-at-bottom" or is this
 +   a bug?

No it is not a bug. Here's the order..

For Reply, the order is reply-header, quoted text, your response and then your
sig

For Forward, the order is your quick_note, your .sig, reply-header, quoted text,quoted .sig

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Tue Jan 31 20:18:58 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03190;
	Tue, 31 Jan 95 20:18:58 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15433;
	Tue, 31 Jan 95 20:13:07 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15427;
	Tue, 31 Jan 95 20:13:05 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZWEe-00038MC; Tue, 31 Jan 95 20:00 PST
To: pine-info@cac.washington.edu
From: shrim@worf.ocis.temple.edu (Wet-Sprocket)
Subject: Re: Pine and procmail
Date: 1 Feb 1995 01:46:44 GMT
Message-Id: <3gmp64$42o@cronkite.ocis.temple.edu>

Comes here Mr. Felix the Cat with this opinion in the "comp.mail.pine" group in
this article on 1 Feb 1995 00:10:00 GMT:

 +   Well, I've been wanting to sort my mail into different inboxs for a long 
 +   time. And then I heard about "procmail" I found myself a copy and have it 
 +   compiled on my acc't. My question is ... how in the world do you 
 +   configure it to work with pine? how would i sort my mail by person and 
 +   listserv? i've read the documentation, but i'm not sure how all of these 
 +   examples given apply to pine itself.
 +   any help would be appreciated. please em'l your suggestions to me at 
 +   felix@jhu.edu

Pl. read the well written Filtering FAQ, which gives you a step-by-step
instruction frequently posted in this and other relevant newsgroups or
ftp from anon ftp sites.

--
---.                                ,    ,
\___                                ("\''/").___..--''"`-._
    \                                `9_ 9  )   `-.  (     ).`-.__.`)
`___/riram NCV                       (_Y_.)'  ._   )  `._ `. ``-..-'
Computer Svcs                      _..`--'_..-_/  /--'_.' .
Temple Univ.                      (il).-''  ((i).'  ((!.-'
__________________________________________________________________________


From owner-pine-info@cac.washington.edu  Tue Jan 31 20:45:16 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03963;
	Tue, 31 Jan 95 20:45:16 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16936;
	Tue, 31 Jan 95 20:40:05 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16930;
	Tue, 31 Jan 95 20:40:03 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZWad-00038MC; Tue, 31 Jan 95 20:22 PST
To: pine-info@cac.washington.edu
From: drown@iii1.iii.net (Steve Bernacki Jr)
Subject: Random .sig?
Date: 24 Jan 1995 20:38:33 GMT
Message-Id: <3g3ogs$jkn@nic.iii.net>

Howdy y'all,

Is it possible to somehow have a random signature (out of a directory of
signatures) be selected and pasted into pine?  If not, is there any way
to get pine to run a program that would output such a random sig?

Thanks!
-S
--
Steve Bernacki, Jr.  | unix programmer/ moxie drinker
Email: drown@iii.net | http://www.iii.net/users/drown.html


From owner-pine-info@cac.washington.edu  Tue Jan 31 21:04:21 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA04363;
	Tue, 31 Jan 95 21:04:21 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16129;
	Tue, 31 Jan 95 20:58:43 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16123;
	Tue, 31 Jan 95 20:58:42 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZWvX-00038KC; Tue, 31 Jan 95 20:44 PST
To: pine-info@cac.washington.edu
From: Jace Crouch <jcrouch@gmi.edu>
Subject: Re: IGNORING SIGNATURE IN SPELL CHECKER???
Date: Tue, 31 Jan 1995 17:02:23 -0500
Message-Id: <Pine.SUN.3.91.950131165448.12550A-100000@nova.gmi.edu>
References: <D3A9Gq.3zL@watserv2.uwaterloo.ca>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <D3A9Gq.3zL@watserv2.uwaterloo.ca> 

On Tue, 31 Jan 1995, Mike Simmons - DCS wrote:

> 	My question...is there a way to have the spell checker in pine 
> ignore my signature (from the .signature file)

Mike,

My solution is brute force rather than automated, but it works. I don't 
always use a .signature file, and like to jump between several of them 
based on the phase of the moon, Clinton's haircut, and various other 
considerations. See below for one example (and a spell-check nightmare).

Rename your .signature file to my-sig or whatever, write your message, 
spell check it (too few folks do this!), use ^R ^T S to select the file 
you want to use as a signature, and bang away!

There are probably more elegant solutions, including spell-checking a 
text-based .signature file before saving it in the first place.

Jace

-----------------------jcrouch@nova.gmi.edu------------------------
Ave Maria, gratia plena, Dominus tecum. Benedicta tu in mulieribus, 
et benedictus fructus ventris tui, Iesus. Sancta Maria, Mater Dei, 
ora pro nobis peccatoribus, nunc, et in hora mortis nostrae. Amen.



From owner-pine-info@cac.washington.edu  Tue Jan 31 22:05:39 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA05766;
	Tue, 31 Jan 95 22:05:39 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18166;
	Tue, 31 Jan 95 21:59:57 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA18160;
	Tue, 31 Jan 95 21:59:56 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZXtT-00038VC; Tue, 31 Jan 95 21:46 PST
To: pine-info@cac.washington.edu
From: oecheruo@gnat.syr.EDU (Okechukwu Chima Echeruo)
Subject: Re: IMAP in this week's Communications Week
Date: 31 Jan 1995 22:11:01 GMT
Message-Id: <3gmchl$sp6@newstand.syr.edu>
References: <Pine.3.89.9501310908.B27617-0100000@morgana.pubserv.com> <Pine.ULT.3.92.950131090302.11209C-100000@shiva1.cac.washington.edu>

Terry Gray (gray@cac.washington.edu) wrote:
:  
: > Has the IMAP4 specification been release yet? If so, can someone point me 
: > to a copy?  

: Yes... The current docs that have been published are RFC-1730 thru 1733,
: available from all the usual Internet RFC repositories or from 
: ftp.cac.washington.edu in the /mail directory.

: -teg

--
--------------------------------------------------------------------------
This is not a .sig
--------------------------------------------------------------------------


From owner-pine-info@cac.washington.edu  Tue Jan 31 22:14:27 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA06020;
	Tue, 31 Jan 95 22:14:27 -0800
Received: by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17271;
	Tue, 31 Jan 95 22:10:24 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx1.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA17265;
	Tue, 31 Jan 95 22:10:23 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZY42-00038MC; Tue, 31 Jan 95 21:57 PST
To: pine-info@cac.washington.edu
From: mike@newport.lib.ca.us (Micheal Wojciechowski)
Subject: What do I do once I download pico?
Date: 24 Jan 1995 21:27:08 GMT
Message-Id: <3g3rbc$ke1@nic-nac.CSU.net>

I downloaded the version for HP-UX9, because this is the operating system we
are running, so now I have this file pico-bin.hpux9 and I don't know what 
to do with it now.  I am not very unix literate, although I know it enoough 
that I feel comfortable using it.  Any help would be appreciated. Thanks in 
advance.


Mike


From owner-pine-info@cac.washington.edu  Tue Jan 31 23:39:57 1995
Return-Path: <owner-pine-info@cac.washington.edu>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA07951;
	Tue, 31 Jan 95 23:39:57 -0800
Received: by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19604;
	Tue, 31 Jan 95 23:35:47 -0800
Errors-To: owner-pine-info@cac.washington.edu
Sender: owner-pine-info@cac.washington.edu
Received: from rain.psg.com by mx2.cac.washington.edu
	(5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19598;
	Tue, 31 Jan 95 23:35:45 -0800
Received: by rain.psg.com (Smail3.1.29.1 #3)
	id m0rZZMw-00038KC; Tue, 31 Jan 95 23:20 PST
To: pine-info@cac.washington.edu
From: rmp@garlic.com (Robert Mann Packaging Co.)
Subject: Wyse60 Support
Date: 24 Jan 1995 12:34:40 -0800
Message-Id: <3g3o90$lt9@garlic.com>

Ok ... I finally got pine, and I've been playing around with it, and I 
suddenly realize that the cursor keys on our Wyse60 terminals are not 
working inside Pine ... 

It looks like the cursor keys send ^K, ^J, ^H, and ^L, which Pine uses
for other purposes.  Is there a way to remap these keys inside Pine, or 
do I initialize the terminal to a different type going in??? 

Anybody ever run into this?

============================================================================
Bill Hudson: System Administrator: Robert Mann Packaging, Inc: Gilroy CA
bill@rmp.com   rmp@garlic.com   408/848-5440


