From pinedev@shiva0.cac.washington.edu Wed Sep 1 04:19:09 1999 -0700

From [email protected] Wed Sep 1 04:19:09 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Sep 1999 04:19:09 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA14903
for <[email protected]>; Wed, 1 Sep 1999 04:19:08 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA24173;
Wed, 1 Sep 1999 04:19:06 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA27249;
Wed, 1 Sep 1999 04:18:32 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA27148
for <[email protected]>; Wed, 1 Sep 1999 04:14:58 -0700
Received: from hal9k.org (PPP3-69.bom.vsnl.net.in [202.54.3.69])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA11029
for <[email protected]>; Wed, 1 Sep 1999 04:14:49 -0700
Received: from localhost (satyap@localhost)
by hal9k.org (8.9.3/8.8.7) with ESMTP id QAA00659
for <[email protected]>; Wed, 1 Sep 1999 16:37:43 +0530
Message-Id: <[email protected]>
Date: Wed, 1 Sep 1999 16:37:42 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Changing the reply-to address
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: hal9k.org: satyap owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Aug 26, 1999 at 09:04, Jeff wrote:

[i was asking about changing the From: address automatically so I reply to
an address other than the From: address (Reply-to: is not an issue in this
case)]

> > Apologies if this is in the wrong place:
> It is; procmail will come closer to doing what you want.

Thanks, but I don't have time to rtfm procmail right now. I had linuxconf
change sendmail's rewrite rule, and that works quite well for this case.

Gotta learn procmail... ::peers at the overflowing INBOX::

--
Satya.
http://satyaonline.cjb.net/

From [email protected] Wed Sep 1 10:58:01 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Sep 1999 10:58:00 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15924
for <[email protected]>; Wed, 1 Sep 1999 10:57:59 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA06209;
Wed, 1 Sep 1999 10:57:58 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA24076;
Wed, 1 Sep 1999 10:56:59 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA35840
for <[email protected]>; Wed, 1 Sep 1999 10:52:34 -0700
Received: from usc.edu (usc.edu [128.125.253.136])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20130
for <[email protected]>; Wed, 1 Sep 1999 10:52:34 -0700
Received: from Law.USC.EDU (law.usc.edu [128.125.42.6])
by usc.edu (8.8.8/8.8.8/usc) with SMTP
id KAA21104 for <[email protected]>; Wed, 1 Sep 1999 10:52:31 -0700 (PDT)
Received: from l2122.usc.edu by Law.USC.EDU (4.1/SMI-4.1)
id AA11445; Wed, 1 Sep 1999 10:51:27 PDT
Message-Id: <[email protected]>
Date: Wed, 1 Sep 1999 10:51:24 -0700 (Pacific Daylight Time)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Robert Larmon <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: recovering lost email
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have a question re: crashing Win98 systems :(

We recently have had 2 people lose long emails in PC-Pine 4.10 when their
PC freezes. They had postponed the message once or twice before
continuing the email, and then in the middle of typing, the PC crashes
(possibly something other than Pine, but nothing conclusive yet). When
they open PC-Pine again, the message is gone - no dead letter file,
nothing. The files for PC-Pine are mostly on the PC, but we could put it
on the server if that is possible or if that would help. If anyone has
any help, suggestions, etc I would be grateful. (fyi, I'm not running
imap 4 yet, only 3, but I will be testing it soon)

Thanks,

Robert

```````````````````````````````````````````````````````````````````````
` Robert Larmon `
` PC Systems Analyst `
` USC Law School Computing Services `
` [email protected] `
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

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

From [email protected] Wed Sep 1 15:15:48 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Sep 1999 15:15:48 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA28063
for <[email protected]>; Wed, 1 Sep 1999 15:15:46 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA07231;
Wed, 1 Sep 1999 15:15:45 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA22847;
Wed, 1 Sep 1999 15:14:24 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA28820
for <[email protected]>; Wed, 1 Sep 1999 15:10:55 -0700
Received: from q4.quik.com (q4.quik.com [216.176.28.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA26952
for <[email protected]>; Wed, 1 Sep 1999 15:10:54 -0700
Received: from q4.quik.com (root@localhost)
by q4.quik.com (8.9.3/8.9.3) with SMTP id PAA59926
for <[email protected]>; Wed, 1 Sep 1999 15:10:54 -0700
Message-Id: <[email protected]>
Date: Wed, 1 Sep 1999 15:10:54 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Colin J. Raven" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: recovering lost email
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> I have a question re: crashing Win98 systems :(
I have an answer re: crashing Win98 systems.....install Linux.

Tell your users to open ssh sessions and use Pine on the server. Secure
CRT works really nicely in the Win98 world, and would simply avoid the
problem. Deploy it as a trial on the 2 machines where the users
experienced the problem.

> We recently have had 2 people lose long emails in PC-Pine 4.10 when their
> PC freezes. They had postponed the message once or twice before
> continuing the email, and then in the middle of typing, the PC crashes
> (possibly something other than Pine, but nothing conclusive yet). When
> they open PC-Pine again, the message is gone - no dead letter file,
> nothing.
If you're gonna put PC-Pine files on the server, you may as well have
users log on to the server and use Pine from their home dir. It
accomplishes the same end result, but more elegantly. Putting PC-Pine
files on the server is a bit kludgy IMHO.
> The files for PC-Pine are mostly on the PC, but we could put it
> on the server if that is possible or if that would help. If anyone has
> any help, suggestions, etc I would be grateful. (fyi, I'm not running
> imap 4 yet, only 3, but I will be testing it soon)
-Colin
--
Colin J. Raven
VP Operations, DDF Lab, Inc.
Costa Mesa, CA | Harrison, NY
"Failure to adequately maintain the release gear on your M203 Grenade
Launcher could cause it to fire when you least expect it. This would make
you quite unpopular with what remains of your unit"

From [email protected] Wed Sep 1 16:09:07 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Sep 1999 16:09:07 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA29520
for <[email protected]>; Wed, 1 Sep 1999 16:09:06 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA08731;
Wed, 1 Sep 1999 16:09:04 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA08911;
Wed, 1 Sep 1999 16:08:20 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA11342
for <[email protected]>; Wed, 1 Sep 1999 16:03:36 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA01779
for <[email protected]>; Wed, 1 Sep 1999 16:03:36 -0700
Received: from mail.cc.duq.edu (mail.cc.duq.edu [165.190.8.217])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA08585
for <[email protected]>; Wed, 1 Sep 1999 16:03:35 -0700
Received: from localhost (worthin5033@localhost)
by mail.cc.duq.edu (8.9.0/8.9.0) with ESMTP id TAA15007
for <[email protected]>; Wed, 1 Sep 1999 19:11:19 -0400 (EDT)
Message-Id: <[email protected]>
Date: Wed, 1 Sep 1999 19:11:18 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jim Worthington <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [delete-me]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

For some reason, every time I try to save a message from my inbox, it
always prompts to save it by default to the folder "[delete-me]", nothing
in the setup configuration seems to change this. Any suggestions?

--
Jim Worthington
D/Chemistry and Biochemistry
Duquesne University
Pittsburgh, PA 15282-1530

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

From [email protected] Thu Sep 2 10:18:59 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Sep 1999 10:18:59 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA13197
for <[email protected]>; Thu, 2 Sep 1999 10:18:58 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA00832;
Thu, 2 Sep 1999 10:18:56 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA16060;
Thu, 2 Sep 1999 10:18:05 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA57714
for <[email protected]>; Thu, 2 Sep 1999 10:13:37 -0700
Received: from rook.ecs.soton.ac.uk (rook.ecs.soton.ac.uk [152.78.71.4])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA11949
for <[email protected]>; Thu, 2 Sep 1999 10:13:36 -0700
Received: from stork.ecs.soton.ac.uk (stork [152.78.71.1])
by rook.ecs.soton.ac.uk (8.9.1a/8.9.1) with ESMTP id SAA09521
for <[email protected]>; Thu, 2 Sep 1999 18:14:56 +0100 (BST)
Received: from soolin.ecs.soton.ac.uk (IDENT:rwb197@soolin [152.78.71.19])
by stork.ecs.soton.ac.uk (8.9.3/8.9.3) with SMTP id SAA23702
for <[email protected]>; Thu, 2 Sep 1999 18:13:34 +0100 (BST)
Message-Id: <[email protected]>
Date: Thu, 2 Sep 1999 18:13:33 +0100 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Robert Brady <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Filtering
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello.

I am currently trying to add a feature to pine (multibyte
character set support, and automatic conversion between character sets). I
have already got rfc2047 decoding working properly, by enchancing the
function in strings.c so it can actually convert between charsets.

It's decoding message bodies that I am stuck on.

I believe that the right place to change is in mailview.c:decode_text, and
should be done by inserting the appropriate filter in the filter queue?

However, I can't figure out how the filters work... can someone show how
me to write a "null", filter, which just passes through stuff unchanged?,
and I will be able to pick up the ball from there?

Thanks,
Robert

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

From [email protected] Thu Sep 2 15:16:27 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Sep 1999 15:16:27 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA19913
for <[email protected]>; Thu, 2 Sep 1999 15:16:26 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA03126;
Thu, 2 Sep 1999 15:16:24 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA14962;
Thu, 2 Sep 1999 15:15:33 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA49016
for <[email protected]>; Thu, 2 Sep 1999 15:12:06 -0700
Received: from gort.office.aol.com (pix-fw.wan.aol.com [152.163.190.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA07475
for <[email protected]>; Thu, 2 Sep 1999 15:12:05 -0700
Received: from DBPETE ([10.2.110.102]) by gort.office.aol.com with ESMTP (8.7.1/8.7.1) id SAA02647 for <[email protected]>; Thu, 2 Sep 1999 18:12:01 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 2 Sep 1999 18:12:02 -0400 (Eastern Daylight Time)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Dan Peterson <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Replying to html mail
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I've noticed that sometimes Pine seems to use the "Content-type:" header
of the original mail message when replying. Is this the way it should be?

The problem is, the "Content-type" is "text/html", but the actual content
is really "text/plain". So when the message is viewed, all the text is
wrapped together.

--
------------------------------------------------------------------------
Dan Peterson Senior Software Engineer AOL
Email: [email protected] Phone: 703-265-0226 FAX: 703-265-2405
------------------------------------------------------------------------

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

From [email protected] Thu Sep 2 22:37:55 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Sep 1999 22:37:55 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA23880
for <[email protected]>; Thu, 2 Sep 1999 22:37:54 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA10996;
Thu, 2 Sep 1999 22:37:52 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA10330;
Thu, 2 Sep 1999 22:37:17 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA37764
for <[email protected]>; Thu, 2 Sep 1999 22:33:33 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA02456
for <[email protected]>; Thu, 2 Sep 1999 22:33:32 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA00724 for [email protected]; Fri, 3 Sep 1999 05:40:10 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Thu, 2 Sep 99 22:40 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA05475
for <[email protected]>; Thu, 2 Sep 1999 22:27:26 -0700
Message-Id: <Pine.LNX.4.05.9909022225500.4697-100000@ArmispianSystems.Rossland.bc.ca>
Date: Thu, 2 Sep 1999 22:27:24 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Editing resent messages?
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is there a way that you can edit messages (in Pine), and have it
produce proper Resent- headers? Apparently there is only one ``known''
mail package that does this (only available on VMS). Anyone have any
ideas?

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

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

From [email protected] Fri Sep 3 12:21:36 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Sep 1999 12:21:35 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA07516
for <[email protected]>; Fri, 3 Sep 1999 12:21:34 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA27450;
Fri, 3 Sep 1999 12:21:33 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA03696;
Fri, 3 Sep 1999 12:20:35 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA18308
for <[email protected]>; Fri, 3 Sep 1999 12:16:08 -0700
Received: from franklin.wrl.org (IDENT:[email protected] [209.96.177.100])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04822
for <[email protected]>; Fri, 3 Sep 1999 12:16:08 -0700
Received: from localhost (jpayne@localhost)
by franklin.wrl.org (8.8.7/8.8.5) with ESMTP id PAA01929
for <[email protected]>; Fri, 3 Sep 1999 15:16:06 -0400
Message-Id: <[email protected]>
Date: Fri, 3 Sep 1999 15:16:06 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jennifer Payne <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Header Help Needed Please...
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi there. I'm new to the list so please be patient with me. :)

After some changes made to my configuration options, I no longer can see
headers on incoming mails. I was trying to change the configuration so
that I could see *full* headers, but I've done something terribly wrong.

Here's where I think the problems are:

customized-hdrs <Empty Value>
viewer-hdrs <Empty Value>

They used to say <No Value Set>.

Any ideas on how I can get my headers back?
THANKS> Jenny

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

From [email protected] Fri Sep 3 12:58:11 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Sep 1999 12:58:11 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA08786
for <[email protected]>; Fri, 3 Sep 1999 12:58:10 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA00683;
Fri, 3 Sep 1999 12:58:08 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA11415;
Fri, 3 Sep 1999 12:55:40 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA55190
for <[email protected]>; Fri, 3 Sep 1999 12:51:23 -0700
Received: from mailhub2.liv.ac.uk (mailhub2.liv.ac.uk [138.253.100.95])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA09539
for <[email protected]>; Fri, 3 Sep 1999 12:51:22 -0700
Received: from ajtpc.liv.ac.uk ([138.253.253.66])
by mailhub2.liv.ac.uk with esmtp (Exim 2.12 #1)
id 11MzMm-0007Rl-00; Fri, 3 Sep 1999 20:51:20 +0100
Received: (from qq11@localhost)
by ajtpc.liv.ac.uk (8.9.3/8.9.3) id UAA28274;
Fri, 3 Sep 1999 20:51:03 +0100
Message-Id: <[email protected]>
Date: Fri, 3 Sep 1999 20:51:03 +0100 (BST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Alan Thew <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Replying to html mail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Dan Peterson <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

we've seen this before. It's a bug IMO.

--
Alan Thew [email protected]
Computing Services,University of Liverpool Fax: +44 151 794-4442

On Thu, 2 Sep 1999 18:12 , Dan Peterson <[email protected]> said:

> I've noticed that sometimes Pine seems to use the "Content-type:" header
> of the original mail message when replying. Is this the way it should be?
>
> The problem is, the "Content-type" is "text/html", but the actual content
> is really "text/plain". So when the message is viewed, all the text is
> wrapped together.
>
> --
> ------------------------------------------------------------------------
> Dan Peterson Senior Software Engineer AOL
> Email: [email protected] Phone: 703-265-0226 FAX: 703-265-2405
> ------------------------------------------------------------------------
>
>

From [email protected] Fri Sep 3 14:08:32 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Sep 1999 14:08:32 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA10204
for <[email protected]>; Fri, 3 Sep 1999 14:08:31 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA30284;
Fri, 3 Sep 1999 14:08:29 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA07428;
Fri, 3 Sep 1999 14:07:30 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA62408
for <[email protected]>; Fri, 3 Sep 1999 14:03:48 -0700
Received: from tao.agoron.com ([email protected] [206.181.233.66])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA31463
for <[email protected]>; Fri, 3 Sep 1999 14:03:47 -0700
Received: from tao.agoron.com (rem14.agoron.com [207.86.97.145])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id RAA10365;
Fri, 3 Sep 1999 17:03:44 -0400 (EDT)
Message-Id: <[email protected]>
Date: Fri, 03 Sep 1999 17:02:48 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Header Help Needed Please...
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Jennifer Payne <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

what your problem is most likely this:

by default PINE doesn't display header info, so what you need to do is go into
setup/config. Scroll down and find the "enable-full-header-cmd" and mark it
with an 'x'. Quit and restart PINE, go into your inbox or wherever you store
your mail and view a message, the message headers will not display by themselves
you need to press 'H' then you headers should show.

Hope that helps,

---Andy

Andy Malato
Agora Online / CompuSol Consulting, INC.
Systems Administrator
Bayonne, NJ
201-437-6440

Jennifer Payne wrote:
>
> Hi there. I'm new to the list so please be patient with me. :)
>
> After some changes made to my configuration options, I no longer can see
> headers on incoming mails. I was trying to change the configuration so
> that I could see *full* headers, but I've done something terribly wrong.
>
> Here's where I think the problems are:
>
> customized-hdrs <Empty Value>
> viewer-hdrs <Empty Value>
>
> They used to say <No Value Set>.
>
> Any ideas on how I can get my headers back?
> THANKS> Jenny
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------

From [email protected] Fri Sep 3 14:46:53 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Sep 1999 14:46:53 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA10736
for <[email protected]>; Fri, 3 Sep 1999 14:46:51 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA31381;
Fri, 3 Sep 1999 14:46:49 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA08571;
Fri, 3 Sep 1999 14:46:11 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA37726
for <[email protected]>; Fri, 3 Sep 1999 14:42:26 -0700
Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA24831
for <[email protected]>; Fri, 3 Sep 1999 14:42:26 -0700
Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP (
WorldSecure Server SMTP Relay(WSS) v3.6); Fri, 03 Sep 99 15:42:20 -0600
Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190])
by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id PAA19320 for
<[email protected]>; Fri, 3 Sep 1999 15:42:24 -0600 (MDT)
Message-Id: <[email protected]>
Date: Fri, 3 Sep 1999 15:42:22 -0600
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Daniel Sands" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Header Help Needed Please...
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: "Pine Discussion Forum" <[email protected]>
X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c
X-WSS-ID: 1BCE9F3634828-01-01
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> customized-hdrs <Empty Value>
> viewer-hdrs <Empty Value>

Move your cursor to the line to remove the value of, then press D.

From [email protected] Sun Sep 5 22:16:05 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 5 Sep 1999 22:16:05 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA04770
for <[email protected]>; Sun, 5 Sep 1999 22:16:04 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA13346;
Sun, 5 Sep 1999 22:16:02 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA25395;
Sun, 5 Sep 1999 22:14:19 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA63740
for <[email protected]>; Sun, 5 Sep 1999 22:10:14 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA29034
for <[email protected]>; Sun, 5 Sep 1999 22:10:14 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA13264
for <[email protected]>; Sun, 5 Sep 1999 22:10:14 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.1/8.9.1) with ESMTP id AAA00529
for <[email protected]>; Mon, 6 Sep 1999 00:09:52 -0500 (CDT)
Message-Id: <[email protected]>
Date: Mon, 6 Sep 1999 00:09:52 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: grepmail
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <[email protected]>
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

A guy named Kevin Fonda <[email protected]> (thanks, Kevin!) wrote to me
off line in reply to my posting (appended below). Kevin recommended
grepmail, a perl script that I had not heard of before. I have now tried
it and I find it very useful. Grepmail will search multiple folders for
messages meeting certain criteria and it will send them to stdout, which
can be piped through grepmail again (if needed), and/or to a file which
can then be read in pine. It's very nice.

The author of grepmail is a software engineering grad student named David
Coppit. You can download grepmail from his web site:

http://www.cs.virginia.edu/~dwc3q/

Grepmail requires perl, and you have to alter the first line of the
grepmail script(s) to tell them where perl is. For example, my first line
reads as follows:

#!/usr/local/bin/perl

Without changing the first line, the script won't run.

If you don't have perl, you can get it from www.perl.org

To get the man page for grepmail, run "pod2man" on the grepmail program
itself. You can also try "pod2text" and "perldoc grepmail".

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

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

On Thu, 5 Aug 1999, Mike Miller wrote:

> I like the pine Select feature (using the semi-colon) and wish I could
> make even better use of it. My problem is that I often have to find a
> collection of messages that are in different folders. I end up having to
> reapply the same command in one folder after another. If only PINE could
> search across multiple folders simultaneously!
>
> Someone told that Pine 4.00 would implement this feature, and he directed
> me this docoment ("Changes from Pine 3.96 to 4.00"):
> http://www.washington.edu/pine/changes/3.96-to-4.00.html
> Where it says, "Select can search multiple folders."
>
> >From what I see in using pine, this is not a very helpful feature. It
> does allow me to identify folders that contain a certain string. Of
> course, I could do essentially the same thing using "grep -il". With grep
> commands I have more options (e.g., case-sensitivity).
>
> What I want is something different. I want to be able to do the same kind
> of Select (;) searching across folders that I can now do only within
> folders. For example, I want to find every message with "Bob Thomas" in
> the "To:" field in the mail folders "199904", "199905", "199906" and
> "199907". Right now I'd do it this way:
>
> cat mail/19990[4567] > mail/findbob
>
> Then I'd go into pine, make findbob my default folder, and do the select
> operation:
>
> ;ttBob Thomas
>
> It would be fabulous if Pine could give me the same result without having
> to create the mail/findbob folder. Maybe it could show a pseudo-folder
> with listings like this:
>
>
> 199904:
> 1 Apr 22 Bob Thomas (1,699) You owe me big for this one
>
> 199905:
> 2 May 28 Bob Thomas (2,524) I'll accept only cash
>
> 199906:
> + 3 Jun 7 Bob Thomas (2,040) Meet me in the lobby
> 4 Jun 29 Bob Thomas (456) Where's my money?
>
> 199907:
> + 5 Jul 8 Bob Thomas (1,616) Pay me or you'll be sorry
>
>
> If I could then Select, Apply, etc. from there, that would be superb. If
> pine will never do this for me, does anyone know of a program that does
> this now?
>
> Regards,
>
> Mike
>
>

--
Kevin Fonda Email: [email protected]
5 Main St. Phone: (732) 223-2013
Manasquan, NJ 08736 Fax : (732) 223-3431
LINUX, the choice of a GNU generation

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

From [email protected] Wed Sep 8 04:12:13 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Sep 1999 04:12:13 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA24129
for <[email protected]>; Wed, 8 Sep 1999 04:12:12 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA02902;
Wed, 8 Sep 1999 04:12:10 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA07315;
Wed, 8 Sep 1999 04:03:37 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA52686
for <[email protected]>; Wed, 8 Sep 1999 03:59:27 -0700
Received: from gfanrend.fishpool.fi ([email protected] [62.236.124.189])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA31406
for <[email protected]>; Wed, 8 Sep 1999 03:59:25 -0700
Received: from hal.fishpool.fi [62.236.124.188] (mail)
by gfanrend.fishpool.fi with esmtp (Exim 2.05 #1 (Debian))
for [email protected]
id 11OfRk-0005FQ-00; Wed, 8 Sep 1999 13:59:24 +0300
Received: from q-funk by hal.fishpool.fi with local-esmtp (Exim 2.05 #1)
id 11OfRi-0000D3-00 (Debian); Wed, 8 Sep 1999 13:59:22 +0300
Message-Id: <[email protected]>
Date: Wed, 8 Sep 1999 13:59:22 +0300 (EEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Martin-Eric Racine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Error Messages Appendix??
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Sender: Martin-Eric Racine <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello,

Here is one that nobody has yet answered on comp.mail.pine:
-----

Often, after my ISP changes upstream newssource, I get this type=20
of error message:

[No state for newsgroup comp.sys.atari.st found, reading as new]

In this particular message's case, I suspect it means that the
newsgroup is empty, but since there is no Error Message Appendix
anywhere in the Pine archive, I cannot tell for sure...

Was there ever such an appendix?

The point is, ISPs are often quick to dismiss any error on their
part, when a newsgroup is missing, and blame the customer's news
reader. It would be nice if I could point them to a proper Pine
documentation that confirms the above as a server error, not the
result of a user misconfiguration...

Thanks to whoever can clarify this particular message as well, btw.

Regards,
--=20
----------------------------------------------------------------
Martin-=C9ric Racine The Atari Stacy and TT030 Homepage
Lappeenranta, Finland http://members.tripod.com/~TT030/
----------------------------------------------------------------
"When the time comes, I will know and I shall be." Q-Funk=20

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

From [email protected] Wed Sep 8 07:19:01 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Sep 1999 07:19:01 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA26953
for <[email protected]>; Wed, 8 Sep 1999 07:19:00 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA06122;
Wed, 8 Sep 1999 07:18:58 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA11433;
Wed, 8 Sep 1999 07:17:44 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA52500
for <[email protected]>; Wed, 8 Sep 1999 07:13:41 -0700
Received: from federation.addy.com (federation.addy.com [207.239.68.2])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA26119
for <[email protected]>; Wed, 8 Sep 1999 07:13:40 -0700
Received: from localhost (jim@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id KAA19855 for <[email protected]>; Wed, 8 Sep 1999 10:13:39 -0400 (EDT)
Message-Id: <[email protected]>
Date: Wed, 8 Sep 1999 10:13:38 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jim Sander <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: pine.conf.fixed file(s)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Envision this: there are two classes of users on a system. Some have
normal shells and I'd like them to be able to avoid placing unnecessary
restrictions on them. Others are "email only" with pine as their login
shell and I don't want them getting sneaky on me and changing that, or
doing assorted other things that would be a pain.

I can "lock down" things pretty effectively using pine.conf.fixed, but
this is inconvenient for a few people- specifically me. The only way I can
find around this is a fair amount of work. (compile a special version of
pine with options to use a different location for pine.conf.fixed and use
*that* executable for the restricted users)

My ideal solution would be a way to use a different .fixed file for
each unix group. Maybe in my copious spare time (ha!) I'll hack pine to do
this, but I'm not energetic enough to start learning the intricacies of
the source code at this time. So, I'm looking for alternatives...

Maybe I can remove access to the .pinerc files for the restricted users
and lock them down that way? To be effective that would of course require
changes to the modes of the users' home directories though. (can o' worms)

Before I go to all the effort (and possibly miss something obvious)
I'd appreciate any ideas and/or suggestions. Perhaps I'm missing something
in the docs?

-=Jim=-

From [email protected] Wed Sep 8 12:12:07 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Sep 1999 12:12:07 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01249
for <[email protected]>; Wed, 8 Sep 1999 12:12:06 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA14965;
Wed, 8 Sep 1999 12:12:03 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id MAA16019;
Wed, 8 Sep 1999 12:10:35 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA20980
for <[email protected]>; Wed, 8 Sep 1999 12:06:57 -0700
Received: from noella.mindsec.com (IDENT:[email protected] [209.172.192.12])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01008
for <[email protected]>; Wed, 8 Sep 1999 12:06:56 -0700
Received: from localhost (IDENT:simple@localhost [127.0.0.1])
by noella.mindsec.com (8.9.3/8.9.3a) with ESMTP id NAA32227
for <[email protected]>; Wed, 8 Sep 1999 13:07:01 -0600
Message-Id: <[email protected]>
Date: Wed, 8 Sep 1999 13:07:01 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Erik Parker <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Content-Type: text/html; charset=US-ASCII
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I don't know if this is fairly simple or not, I read
about the filters, however it didn't really make very much
sense to me..

I need to send E-mail out,
and have the content type be text/html, HOWEVER, everything
I tried, unless I edit the spoof file, and use the bounce command,
it will always send text/plain.

I am inserting into the body (ctrl-R) a file.html, and sending it.
It is going out daily to a HTML version of a mailing list. Eudora Pro
reads it fine, but things like Netscape, and Outlook, and IE, can't
read it, because they see the content as being plain text.

I have also tried attaching the file, and having a .mime.types in my Home
dir, reading:

text/html htm html

which also doesn't work.

Any help is GREATLY appreciated.

Erik Parker
[email protected]

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

From [email protected] Wed Sep 8 12:29:42 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Sep 1999 12:29:42 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01668
for <[email protected]>; Wed, 8 Sep 1999 12:29:41 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA19388;
Wed, 8 Sep 1999 12:29:39 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id MAA03906;
Wed, 8 Sep 1999 12:27:58 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA38808
for <[email protected]>; Wed, 8 Sep 1999 12:25:07 -0700
Received: from noella.mindsec.com (IDENT:[email protected] [209.172.192.12])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA03986
for <[email protected]>; Wed, 8 Sep 1999 12:25:07 -0700
Received: from localhost (IDENT:simple@localhost [127.0.0.1])
by noella.mindsec.com (8.9.3/8.9.3a) with ESMTP id NAA32400
for <[email protected]>; Wed, 8 Sep 1999 13:25:11 -0600
Message-Id: <[email protected]>
Date: Wed, 8 Sep 1999 13:25:11 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Erik Parker <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Content-Type: text/html; charset=US-ASCII
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

To reply to my own message.. I tried adding:

sending-filters=_CHARSET(US-ASCII)_,
_MIMETYPE(text/html)_

however, as you can see in the headers of this messag, that did not work
either.

On Wed, 8 Sep 1999, Erik Parker wrote:

> I don't know if this is fairly simple or not, I read
> about the filters, however it didn't really make very much
> sense to me..
>
> I need to send E-mail out,
> and have the content type be text/html, HOWEVER, everything
> I tried, unless I edit the spoof file, and use the bounce command,
> it will always send text/plain.
>
> I am inserting into the body (ctrl-R) a file.html, and sending it.
> It is going out daily to a HTML version of a mailing list. Eudora Pro
> reads it fine, but things like Netscape, and Outlook, and IE, can't
> read it, because they see the content as being plain text.
>
> I have also tried attaching the file, and having a .mime.types in my Home
> dir, reading:
>
> text/html htm html
>
> which also doesn't work.
>
> Any help is GREATLY appreciated.
>
>
> Erik Parker
> [email protected]
>
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

Erik Parker
[email protected]

From [email protected] Wed Sep 8 22:58:18 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Sep 1999 22:58:18 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA12715
for <[email protected]>; Wed, 8 Sep 1999 22:58:17 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA00850;
Wed, 8 Sep 1999 22:58:15 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id WAA23107;
Wed, 8 Sep 1999 22:57:25 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id WAA11056
for <[email protected]>; Wed, 8 Sep 1999 22:53:47 -0700
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA01925
for <[email protected]>; Wed, 8 Sep 1999 22:53:47 -0700
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id WAA07028;
Wed, 8 Sep 1999 22:53:45 -0700 (PDT)
Message-Id: <Pine.OSF.4.10.9909082225030.5422-100000@goedel3.math.washington.edu>
Date: Wed, 8 Sep 1999 22:53:45 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Content-Type: text/html; charset=US-ASCII
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Erik Parker <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Erik Parker ([email protected]) wrote Today:

:) I don't know if this is fairly simple or not, I read
:) about the filters, however it didn't really make very much
:) sense to me..
:)
:) I need to send E-mail out,
:) and have the content type be text/html, HOWEVER, everything
:) I tried, unless I edit the spoof file, and use the bounce command,
:) it will always send text/plain.
:)
Here's the way to do it. You have to follow several steps in order to make
this work.

First you have to create a script, say we call it mime_types. Your file
mime_types should say something like this:

#!/bin/sh
echo "Content-Type:text/html > $2"

remember to give yourself execution permission for this file.

Then you should go to your configuration file, and where it says
sending-filters it should say:

sending-filters=/full/path/to/myme_types _TMPFILE_ _MIMETYPE_

This is enough to accomplish the task, but you should continue to the next
step anyway.

After you do this take a look at the following configuration option:

[ ] compose-send-offers-first-filter

and read its help in order to understand what it does. I have it checked.
Somehow, I could not change Charset to iso-8859-1, which was something I
wanted, it always uses US-ASCII

Eduardo
http://www.math.washington.edu/~chappa/pine

From [email protected] Wed Sep 8 23:08:57 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Sep 1999 23:08:57 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA12873
for <[email protected]>; Wed, 8 Sep 1999 23:08:56 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA30130;
Wed, 8 Sep 1999 23:08:54 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA05724;
Wed, 8 Sep 1999 23:08:05 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA11314
for <[email protected]>; Wed, 8 Sep 1999 23:05:26 -0700
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA15120
for <[email protected]>; Wed, 8 Sep 1999 23:05:25 -0700
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id XAA21303;
Wed, 8 Sep 1999 23:05:25 -0700 (PDT)
Message-Id: <Pine.OSF.4.10.9909082302280.5422-100000@goedel3.math.washington.edu>
Date: Wed, 8 Sep 1999 23:05:24 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Content-Type: text/html; charset=US-ASCII (correction)
In-Reply-To: <Pine.OSF.4.10.9909082225030.5422-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Cc: Erik Parker <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Eduardo Chappa L. ([email protected]) wrote Today:

:)
:) #!/bin/sh
:) echo "Content-Type:text/html > $2"
:) ^
Oops, now I realize that I misplaced the quotes, it should say

echo "Content-Type:text/html" > $2

instead. Sorry about that.

Eduardo
http://www.math.washington.edu/~chappa/pine/

From [email protected] Thu Sep 9 06:25:41 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 06:25:41 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA21793
for <[email protected]>; Thu, 9 Sep 1999 06:25:39 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA07919;
Thu, 9 Sep 1999 06:25:38 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id GAA10702;
Thu, 9 Sep 1999 06:24:42 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id GAA05394
for <[email protected]>; Thu, 9 Sep 1999 06:21:32 -0700
Received: from gort.office.aol.com (pix-fw.wan.aol.com [152.163.190.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA25840
for <[email protected]>; Thu, 9 Sep 1999 06:21:31 -0700
Received: from DBPETE ([10.2.110.102]) by gort.office.aol.com with ESMTP (8.7.1/8.7.1) id JAA26670 for <[email protected]>; Thu, 9 Sep 1999 09:21:28 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 9 Sep 1999 09:21:27 -0400 (Eastern Daylight Time)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Dan Peterson <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Pine's handling of HTML PRE tag
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm not sure if this is bug or not... I _know_ it's very annoying. :)

I often receive HTML mail that, in my option, contains improperly
formatted HTML. One of the cases is the use of the HTML "PRE" tag... or
to be more specific, the use of certain tags (ie. "BR", "P", etc) within a
"PRE" tag.

What is the correct behavior when a "BR" tag is inside a "PRE" tag...
should it be rendered or ignored?

>From observation using Netscape and IE, it appears it should be ignored.

Problem is, Pine doesn't ignore it. So, a mail message that contains a
"BR" tag for every line AND the entire message is enclosed in a "PRE" tag,
appears as though everything is double spaced.

Is this a bug in Pine? Is there any way around it?

--
------------------------------------------------------------------------
Dan Peterson Senior Software Engineer AOL
Email: [email protected] Phone: 703-265-0226 FAX: 703-265-2405
------------------------------------------------------------------------

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

From [email protected] Thu Sep 9 06:40:46 1999 -0700
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 06:40:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA21927
for <[email protected]>; Thu, 9 Sep 1999 06:40:45 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA08186;
Thu, 9 Sep 1999 06:40:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id GAA11156;
Thu, 9 Sep 1999 06:39:53 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id GAA08950
for <[email protected]>; Thu, 9 Sep 1999 06:37:16 -0700
Received: from tao.agoron.com ([email protected] [206.181.233.66])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA31692
for <[email protected]>; Thu, 9 Sep 1999 06:37:15 -0700
Received: from tao.agoron.com (andy.agoron.com [206.181.233.74])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id JAA01559;
Thu, 9 Sep 1999 09:37:01 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 09 Sep 1999 09:39:16 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine's handling of HTML PRE tag
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Dan Peterson <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

All tags inside of a "PRE" should be ignored. A "PRE" tag is used to Preserve
the orginal text and whitespace characters. I don't know however if this is a
bug in PINE itself, but it sure does seem to me that PINE doesn't know how to
handel <PRE> tags, but then again, PINE was not built with HTML in mind, but
rather ANSI text.

---Andy

Dan Peterson wrote:

> I'm not sure if this is bug or not... I _know_ it's very annoying. :)
>
> I often receive HTML mail that, in my option, contains improperly
> formatted HTML. One of the cases is the use of the HTML "PRE" tag... or
> to be more specific, the use of certain tags (ie. "BR", "P", etc) within a
> "PRE" tag.
>
> What is the correct behavior when a "BR" tag is inside a "PRE" tag...
> should it be rendered or ignored?
>
> >From observation using Netscape and IE, it appears it should be ignored.
>
> Problem is, Pine doesn't ignore it. So, a mail message that contains a
> "BR" tag for every line AND the entire message is enclosed in a "PRE" tag,
> appears as though everything is double spaced.
>
> Is this a bug in Pine? Is there any way around it?
>
> --
> ------------------------------------------------------------------------
> Dan Peterson Senior Software Engineer AOL
> Email: [email protected] Phone: 703-265-0226 FAX: 703-265-2405
> ------------------------------------------------------------------------
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 07:58:41 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA22802
for <[email protected]>; Thu, 9 Sep 1999 07:58:40 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA09763;
Thu, 9 Sep 1999 07:58:38 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id HAA17181;
Thu, 9 Sep 1999 07:57:06 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id HAA28480
for <[email protected]>; Thu, 9 Sep 1999 07:53:22 -0700
Received: from gort.office.aol.com (pix-fw.wan.aol.com [152.163.190.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA02273
for <[email protected]>; Thu, 9 Sep 1999 07:53:22 -0700
Received: from DBPETE ([10.2.110.102]) by gort.office.aol.com with ESMTP (8.7.1/8.7.1) id KAA27353; Thu, 9 Sep 1999 10:53:17 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 9 Sep 1999 10:53:18 -0400 (Eastern Daylight Time)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Dan Peterson <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine's handling of HTML PRE tag
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Andy Malato <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Actually, I'm pretty sure most tags inside a "PRE" tag _should_ be
rendered... but I _think_ there are exceptions for things like "BR" and
"P".

The O'Reilly Dynamic HTML Reference says "Unlike the deprecated PLAINTEXT
element, the PRE element doesn't ignore HTML tags." It doesn't say
specifically anything about ignoring "BR" and "P", but I _thought_ I read
that somewhere.

Perhaps I was just assuming "BR" and "P" should be ignored because that's
what Netscape and IE do.

--
------------------------------------------------------------------------
Dan Peterson Senior Software Engineer AOL
Email: [email protected] Phone: 703-265-0226 FAX: 703-265-2405
------------------------------------------------------------------------

On Thu, 9 Sep 1999, Andy Malato wrote:

> All tags inside of a "PRE" should be ignored. A "PRE" tag is used to Preserve
> the orginal text and whitespace characters. I don't know however if this is a
> bug in PINE itself, but it sure does seem to me that PINE doesn't know how to
> handel <PRE> tags, but then again, PINE was not built with HTML in mind, but
> rather ANSI text.
>
> ---Andy
>
>
> Dan Peterson wrote:
>
> > I'm not sure if this is bug or not... I _know_ it's very annoying. :)
> >
> > I often receive HTML mail that, in my option, contains improperly
> > formatted HTML. One of the cases is the use of the HTML "PRE" tag... or
> > to be more specific, the use of certain tags (ie. "BR", "P", etc) within a
> > "PRE" tag.
> >
> > What is the correct behavior when a "BR" tag is inside a "PRE" tag...
> > should it be rendered or ignored?
> >
> > >From observation using Netscape and IE, it appears it should be ignored.
> >
> > Problem is, Pine doesn't ignore it. So, a mail message that contains a
> > "BR" tag for every line AND the entire message is enclosed in a "PRE" tag,
> > appears as though everything is double spaced.
> >
> > Is this a bug in Pine? Is there any way around it?
> >
> > --
> > ------------------------------------------------------------------------
> > Dan Peterson Senior Software Engineer AOL
> > Email: [email protected] Phone: 703-265-0226 FAX: 703-265-2405
> > ------------------------------------------------------------------------
> >
> > --
> > -----------------------------------------------------------------
> > For information about this mailing list, and its archives, see:
> > http://www.washington.edu/pine/pine-info/
> > -----------------------------------------------------------------
>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 08:36:41 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA23478
for <[email protected]>; Thu, 9 Sep 1999 08:36:40 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA06890;
Thu, 9 Sep 1999 08:36:37 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id IAA14851;
Thu, 9 Sep 1999 08:35:32 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id IAA37696
for <[email protected]>; Thu, 9 Sep 1999 08:31:45 -0700
Received: from rrzs2.rz.uni-regensburg.de (rrzs2.rz.uni-regensburg.de [132.199.1.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA12741
for <[email protected]>; Thu, 9 Sep 1999 08:31:43 -0700
Received: from localhost.localdomain (rrzras2-67.rz.uni-regensburg.de [132.199.209.67])
by rrzs2.rz.uni-regensburg.de (8.8.8/8.8.8) with ESMTP id RAA22266
for <[email protected]>; Thu, 9 Sep 1999 17:31:37 +0200 (MET DST)
Received: from localhost (claus@localhost)
by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA01501
for <[email protected]>; Thu, 9 Sep 1999 16:23:43 +0200
Message-Id: <[email protected]>
Date: Thu, 9 Sep 1999 16:23:42 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Claus Atzenbeck <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: role and Lcc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: pine-info <[email protected]>
X-Authentication-Warning: localhost.localdomain: claus owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I need to define a role with a specified Lcc field. Can I do this? I
couldn't find a Lcc entry field by adding new roles.

Thanks a lot for your help!

Best regards,
Claus.

--
Claus Atzenbeck, stud. phil.
seminar papers: http://homepages.uni-regensburg.de/~atc16247/
[This mail was created on a 100% Micro$oft-free computer.]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 12:03:49 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA28545
for <[email protected]>; Thu, 9 Sep 1999 12:03:48 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA13301;
Thu, 9 Sep 1999 12:03:46 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id MAA28570;
Thu, 9 Sep 1999 12:01:25 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id LAA31460
for <[email protected]>; Thu, 9 Sep 1999 11:57:41 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA08714
for <[email protected]>; Thu, 9 Sep 1999 11:57:39 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id UAA03952
for <[email protected]>; Thu, 9 Sep 1999 20:57:38 +0200
Message-Id: <[email protected]>
Date: Thu, 9 Sep 1999 20:57:37 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: BUG reports
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

Does anyone know where to post bugreports about pine?

TTYL
--
Press every key to continue.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 14:29:32 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA31811
for <[email protected]>; Thu, 9 Sep 1999 14:29:31 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA17577;
Thu, 9 Sep 1999 14:29:29 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id OAA01039;
Thu, 9 Sep 1999 14:28:02 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id OAA22378
for <[email protected]>; Thu, 9 Sep 1999 14:24:23 -0700
Received: from roper.uwyo.edu ([email protected] [129.72.10.8])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA10912
for <[email protected]>; Thu, 9 Sep 1999 14:24:22 -0700
Received: from asuwlink.uwyo.edu (asuwlink.uwyo.edu [129.72.60.2])
by ROPER.UWYO.EDU (PMDF V5.2-32 #33749)
with ESMTP id <[email protected]> for [email protected];
Thu, 9 Sep 1999 15:24:06 -0600 (MDT)
Received: from localhost (jimkirk@localhost) by asuwlink.uwyo.edu (8.8.8/8.8.7)
with ESMTP id PAA16376 for <[email protected]>; Thu,
09 Sep 1999 15:24:06 -0600 (MDT)
Message-Id: <[email protected]>
Date: Thu, 09 Sep 1999 15:24:06 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Kirkpatrick <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Pine and read-only folders
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-warning: asuwlink.uwyo.edu: jimkirk owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I've noticed an unfortunate change in Pine 4.10 versus 3.96. In the older
Pine, if I started Pine from two different sessions the second one would
detect the first one, and attempt to "hijack" the folders and force the
older session to read-only. In 4.10 the behavior is reversed in a sense:
the newer Pine detects the older one and leaves itself in read-only mode.

I consider this unfortunate because of a common problem: A student logs
in and is using Pine to read mail. He then loses the session (power
failure, reboot, whatever) but the UNIX server doesn't know anything has
happened. He then logs in again and now has read-only access (unless he
knows enough to find and kill his other process). Thus, the new behavior
is less desirable than the old behavior.

Is this intentional, and/or can it be made to behave in the older manner
via a config variable?

Jim Kirkpatrick
[email protected] (the "other" UW :-)

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 17:00:39 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02246
for <[email protected]>; Thu, 9 Sep 1999 17:00:38 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA23702;
Thu, 9 Sep 1999 17:00:36 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id QAA24838;
Thu, 9 Sep 1999 16:57:48 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id QAA49390
for <[email protected]>; Thu, 9 Sep 1999 16:54:44 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA30659
for <[email protected]>; Thu, 9 Sep 1999 16:54:43 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id SAA13450
for <[email protected]>; Thu, 9 Sep 1999 18:54:18 -0500 (CDT)
Message-Id: <[email protected]>
Date: Thu, 9 Sep 1999 18:54:18 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 9 Sep 1999, James Kirkpatrick wrote:

> I've noticed an unfortunate change in Pine 4.10 versus 3.96. In the older
> Pine, if I started Pine from two different sessions the second one would
> detect the first one, and attempt to "hijack" the folders and force the
> older session to read-only. In 4.10 the behavior is reversed in a sense:
> the newer Pine detects the older one and leaves itself in read-only mode.

I agree 100%. Changing it was a bad choice, wasn't it? I don't
understand the reasoning.

> Jim Kirkpatrick
> [email protected] (the "other" UW :-)

I went to University of Wisconsin, yet another UW!

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 17:17:32 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02568
for <[email protected]>; Thu, 9 Sep 1999 17:17:31 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA24346;
Thu, 9 Sep 1999 17:17:29 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id RAA12090;
Thu, 9 Sep 1999 17:15:23 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id RAA51116
for <[email protected]>; Thu, 9 Sep 1999 17:11:52 -0700
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id RAA25973
for <[email protected]>; Thu, 9 Sep 1999 17:11:47 -0700
Received: (qmail 7730 invoked from network); 10 Sep 1999 10:10:14 +1000
Received: from trowel.geac.com.au (203.1.26.189)
by caveman.geac.com.au with SMTP; 10 Sep 1999 10:10:14 +1000
Received: (qmail 3854 invoked from network); 10 Sep 1999 10:25:02 +1000
Received: from fgh.geac.com.au (202.6.67.163)
by trowel.geac.com.au with SMTP; 10 Sep 1999 10:25:02 +1000
Received: from localhost (dave@localhost)
by fgh.geac.com.au?r with ESMTP id KAA01076
for <[email protected]>; Fri, 10 Sep 1999 10:09:57 +1000
Message-Id: <Pine.GSO.4.10.9909101006380.410-100000@fgh>
Date: Fri, 10 Sep 1999 10:09:56 +1000 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Dave Horsfall <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion List <[email protected]>
X-Authentication-Warning: fgh.geac.com.au: dave owned process doing -bs
X-Sender: dave@fgh
X-No-Archive: Yes
X-Witty-Saying: "Tesseract - Enter at own risk"
X-Disclaimer: "Me, speak for us?"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 9 Sep 1999, James Kirkpatrick wrote:

> I've noticed an unfortunate change in Pine 4.10 versus 3.96. In the older
> Pine, if I started Pine from two different sessions the second one would
> detect the first one, and attempt to "hijack" the folders and force the
> older session to read-only. In 4.10 the behavior is reversed in a sense:
> the newer Pine detects the older one and leaves itself in read-only mode.

Yes, I prefer this behaviour, in fact. Occasionally I forget I have
a session running, and start up another one.

> I consider this unfortunate because of a common problem: A student logs
> in and is using Pine to read mail. He then loses the session (power
> failure, reboot, whatever) but the UNIX server doesn't know anything has
> happened. He then logs in again and now has read-only access (unless he
> knows enough to find and kill his other process). Thus, the new behavior
> is less desirable than the old behavior.

They'll soon learn to find and kill the other process...

> Is this intentional, and/or can it be made to behave in the older manner
> via a config variable?

A config switch would be nice: [ ] hijack-old-session :-)

--
Dave Horsfall VK2KFU [email protected] Ph: +61 2 9978-7493 Fx: +61 2 9978-7422
Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 20:36:04 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA04484
for <[email protected]>; Thu, 9 Sep 1999 20:36:03 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA27773;
Thu, 9 Sep 1999 20:36:01 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id UAA00465;
Thu, 9 Sep 1999 20:31:56 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id UAA13542
for <[email protected]>; Thu, 9 Sep 1999 20:24:48 -0700
Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147] (may be forged))
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id UAA25350
for <[email protected]>; Thu, 9 Sep 1999 20:22:57 -0700
Received: from peak.org [207.141.129.64] by 1stpc.org with ESMTP
(SMTPD32-4.04) id A81A3CA503F4; Thu, 09 Sep 1999 23:16:42 EST
Received: by peak.org (8.9.3/8.9.0) id XAA25144
for [email protected]; Thu, 9 Sep 1999 23:07:45 -0400 (EDT)
Message-Id: <199909100307.XAA25144@ocalhost>
Date: Thu, 9 Sep 1999 23:07:43 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Timothy J Luoma <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <Pine.GSO.4.10.9909101006380.410-100000@fgh>
References: <Pine.GSO.4.10.9909101006380.410-100000@fgh>
Content-Type: text/plain
MIME-Version: 1.0
X-To: Pine Discussion Forum <[email protected]>
X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff
X-Organization: http://www.peak.org/~luomat/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Replying to message of Fri, 10 Sep 1999 10:09:56 +1000 (EST)
from Dave Horsfall <[email protected]>
regarding ``Re: Pine and read-only folders''

> Yes, I prefer this behaviour, in fact. Occasionally I forget I have
> a session running, and start up another one.

As do I... but I also have the other experience of a dropped connection.

> > I consider this unfortunate because of a common problem: A student logs
> > in and is using Pine to read mail. He then loses the session (power
> > failure, reboot, whatever) but the UNIX server doesn't know anything has
> > happened. He then logs in again and now has read-only access (unless he
> > knows enough to find and kill his other process). Thus, the new behavior
> > is less desirable than the old behavior.
>
> They'll soon learn to find and kill the other process...

You assume that they __can__ login as kill other processes.

I had an account very recently which was made 'pine only'

> > Is this intentional, and/or can it be made to behave in the older manner
> > via a config variable?
>
> A config switch would be nice: [ ] hijack-old-session :-)

That does seem to be the best "option" here (pun intended)

TjL

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 20:50:37 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA04233
for <[email protected]>; Thu, 9 Sep 1999 20:50:36 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA31685;
Thu, 9 Sep 1999 20:50:34 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id UAA23811;
Thu, 9 Sep 1999 20:49:22 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id UAA53150
for <[email protected]>; Thu, 9 Sep 1999 20:46:24 -0700
Received: from tao.agoron.com ([email protected] [206.181.233.66])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA27662
for <[email protected]>; Thu, 9 Sep 1999 20:46:24 -0700
Received: from tao.agoron.com (rem04.agoron.com [207.86.97.135])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id XAA05072;
Thu, 9 Sep 1999 23:46:21 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 09 Sep 1999 23:45:54 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
References: <Pine.GSO.4.10.9909101006380.410-100000@fgh> <199909100307.XAA25144@ocalhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Timothy J Luoma <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Timothy J Luoma wrote:
>
> Replying to message of Fri, 10 Sep 1999 10:09:56 +1000 (EST)
> from Dave Horsfall <[email protected]>
> regarding ``Re: Pine and read-only folders''
>
> > Yes, I prefer this behaviour, in fact. Occasionally I forget I have
> > a session running, and start up another one.

yeah that happens often.

>
> As do I... but I also have the other experience of a dropped connection.
>
> > > I consider this unfortunate because of a common problem: A student logs
> > > in and is using Pine to read mail. He then loses the session (power
> > > failure, reboot, whatever) but the UNIX server doesn't know anything has
> > > happened. He then logs in again and now has read-only access (unless he
> > > knows enough to find and kill his other process). Thus, the new behavior
> > > is less desirable than the old behavior.
> >
> > They'll soon learn to find and kill the other process...
>
> You assume that they __can__ login as kill other processes.
> I had an account very recently which was made 'pine only'

'pine only' -- what in the world were they thinking?

Someone should write a script, that detects for idle time, when pine is running
as
a process, and finds that you have been idle for 5 minutes, that PS-ID should
be killed, therefore making the possibility of starting a second session of pine
less likely, I'll take a look into a script and see what I can do.

---Andy

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 20:59:17 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA04140
for <[email protected]>; Thu, 9 Sep 1999 20:59:16 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA31827;
Thu, 9 Sep 1999 20:59:13 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id UAA24130;
Thu, 9 Sep 1999 20:58:07 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id UAA10622
for <[email protected]>; Thu, 9 Sep 1999 20:55:28 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA15080
for <[email protected]>; Thu, 9 Sep 1999 20:55:28 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id EAA05913; Fri, 10 Sep 1999 04:02:01 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Thu, 9 Sep 99 21:02 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id UAA07022;
Thu, 9 Sep 1999 20:44:05 -0700
Message-Id: <Pine.LNX.4.05.9909092037140.6457-100000@ArmispianSystems.Rossland.bc.ca>
Date: Thu, 9 Sep 1999 20:44:03 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine's handling of HTML PRE tag
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Dan Peterson <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 9 Sep 1999, Dan Peterson wrote:

> Actually, I'm pretty sure most tags inside a "PRE" tag _should_ be
> rendered... but I _think_ there are exceptions for things like "BR" and
> "P".

This seems to be my reading of the HTML 4.0 spec. That most tags
should be accepted. What I do see in the spec is that the
IMG|OBJECT|BIG|SMALL|SUB|SUP tags are listed as .exclusions. So, by
rights shouldn't occur, but to be ``safe'' should be ignored.

> The O'Reilly Dynamic HTML Reference says "Unlike the deprecated PLAINTEXT
> element, the PRE element doesn't ignore HTML tags." It doesn't say
> specifically anything about ignoring "BR" and "P", but I _thought_ I read
> that somewhere.
>
> Perhaps I was just assuming "BR" and "P" should be ignored because that's
> what Netscape and IE do.

What SHOULD be done, isn't listed at least in the portion of the
spec that I have read regarding this. But my personal feeling is that
what Pine is doing is ``right'' and what IE, and Netscape are doing is
``wrong''. There is nothing clear as to what is the way it is SUPOSED to
be rendered...

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 22:18:25 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA05574
for <[email protected]>; Thu, 9 Sep 1999 22:18:24 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA29392;
Thu, 9 Sep 1999 22:18:22 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id WAA15636;
Thu, 9 Sep 1999 22:17:18 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id WAA28806
for <[email protected]>; Thu, 9 Sep 1999 22:14:45 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA21938
for <[email protected]>; Thu, 9 Sep 1999 22:14:44 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id HAA17149
for <[email protected]>; Fri, 10 Sep 1999 07:14:43 +0200
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 07:14:43 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] Resuming postponed + RULE
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

If you compose a msg and postpone it and later resume your composition the
RULE you used is not shown.
The rule seems however been saved in the postponed msg as you can see it
again when you type ^R [Rich Hdr].
This is a bug!

BTW: Is that RULE used or not?

TTYL.
--
There's no place like ~

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 22:26:34 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA05681
for <[email protected]>; Thu, 9 Sep 1999 22:26:33 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA00523;
Thu, 9 Sep 1999 22:26:31 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id WAA15793;
Thu, 9 Sep 1999 22:25:39 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id WAA47192
for <[email protected]>; Thu, 9 Sep 1999 22:23:05 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA22571
for <[email protected]>; Thu, 9 Sep 1999 22:23:04 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id HAA20014
for <[email protected]>; Fri, 10 Sep 1999 07:23:03 +0200
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 07:23:03 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG?] Composing with ROLE
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

Could the ROLE meganism be changed so that when you compose a new msg to
someone or more the ROLE's will be checked also?
This would be desirable for people like me posting to several mailing
lists.

If it already is been checked then there is a BUG because it doesn't work.
The ROLE is selected when replying though.

TTYL.
--
The computer revolution is over. The computers won.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 22:36:34 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA05845
for <[email protected]>; Thu, 9 Sep 1999 22:36:33 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA00751;
Thu, 9 Sep 1999 22:36:31 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id WAA20677;
Thu, 9 Sep 1999 22:35:37 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id WAA09690
for <[email protected]>; Thu, 9 Sep 1999 22:33:07 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA23320
for <[email protected]>; Thu, 9 Sep 1999 22:33:06 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id HAA23375;
Fri, 10 Sep 1999 07:32:50 +0200
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 07:32:50 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Andy Malato <[email protected]>
X-Cc: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 9 Sep 1999, Andy Malato wrote:

> Timothy J Luoma wrote:
> > > They'll soon learn to find and kill the other process...
> >
> > You assume that they __can__ login as kill other processes.
> > I had an account very recently which was made 'pine only'
>
> 'pine only' -- what in the world were they thinking?
>
> Someone should write a script, that detects for idle time, when pine is running
> as
> a process, and finds that you have been idle for 5 minutes, that PS-ID should
> be killed, therefore making the possibility of starting a second session of pine
> less likely, I'll take a look into a script and see what I can do.

Why should you?
That way someone isn't permited to stare at his mail.
Said diferently someone must be able to read his mail in his own tempo,
some mails are long or difficult to understand quickly...

BTW: I think droped connection detection is something for the OS/shell and
not to a userland application.

TTYL.
--
Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 23:07:28 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA06155
for <[email protected]>; Thu, 9 Sep 1999 23:07:27 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA01275;
Thu, 9 Sep 1999 23:07:25 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA21393;
Thu, 9 Sep 1999 23:06:26 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA30288
for <[email protected]>; Thu, 9 Sep 1999 23:03:40 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA02293
for <[email protected]>; Thu, 9 Sep 1999 23:03:40 -0700
Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id XAA01195
for <[email protected]>; Thu, 9 Sep 1999 23:03:39 -0700
Received: from peak.org [207.141.129.64] by 1stpc.org with ESMTP
(SMTPD32-4.04) id A14E8058010A; Fri, 10 Sep 1999 02:12:30 EST
Received: by peak.org (8.9.3/8.9.0) id CAA00666
for [email protected]; Fri, 10 Sep 1999 02:03:35 -0400 (EDT)
Message-Id: <199909100603.CAA00666@ocalhost>
Date: Fri, 10 Sep 1999 02:03:32 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Timothy J Luoma <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: How do I put my roles in another file?
Content-Type: text/plain
MIME-Version: 1.0
X-To: [email protected]
X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff
X-Organization: http://www.peak.org/~luomat/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I know I need to goto

setup
roles
other commands
include file

but how do figure out the correct format for putting the roles in that file?

how do I take the roles that are currently in my .pinerc and move them to
the other file instead?

(my goal is simply to have the roles not defined in .pinerc, which I often
will share with folks who ask for it)

Thanks for any help... didn't find anything in the FAQ

TjL

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Sep 1999 23:26:11 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA06353
for <[email protected]>; Thu, 9 Sep 1999 23:26:10 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA30483;
Thu, 9 Sep 1999 23:26:08 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA17057;
Thu, 9 Sep 1999 23:24:44 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA27146
for <[email protected]>; Thu, 9 Sep 1999 23:22:13 -0700
Received: from mbox-3.inet.fi (mbox-3.inet.fi [192.89.123.195])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA27113
for <[email protected]>; Thu, 9 Sep 1999 23:22:12 -0700
Received: from qn-lpr1-99.quicknet.inet.fi ([194.251.105.99]:1226 "EHLO qn-lpr1-99.quicknet.inet.fi" ident: "NO-IDENT-SERVICE") by mbox-3.inet.fi with ESMTP id <49234-25486>; Fri, 10 Sep 1999 09:23:50 +0300
Message-Id: <Pine.MNT.4.10.9909100919400.125-100000@rakastaja>
Date: Fri, 10 Sep 1999 09:21:57 +0300
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Martin-Eric Racine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG?] Composing with ROLE
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: unlisted-recipients:; (no To-header on input)
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: q-funk@rakastaja
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 10 Sep 1999, Osman%Pine wrote:
> Could the ROLE meganism be changed so that when you compose a new msg
> to someone or more the ROLE's will be checked also?

Do you mean like, equating the Role to which server/Inbox you are
currently using? Yes, that would be desirable. This way, I would
not always have to manually select which Role I wanna use to write
a brand new message (responses are already handled automatically).

--
----------------------------------------------------------------
Martin-�ric Racine The Atari Stacy and TT030 Homepage
Lappeenranta, Finland http://members.tripod.com/~TT030/
----------------------------------------------------------------
"When the time comes, I will know and I shall be." Q-Funk

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 10 Sep 1999 01:27:20 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA07944
for <[email protected]>; Fri, 10 Sep 1999 01:27:19 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA32463;
Fri, 10 Sep 1999 01:27:17 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id BAA29331;
Fri, 10 Sep 1999 01:26:07 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id BAA13320
for <[email protected]>; Fri, 10 Sep 1999 01:23:29 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA10819
for <[email protected]>; Fri, 10 Sep 1999 01:23:28 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id KAA15518;
Fri, 10 Sep 1999 10:23:25 +0200
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 10:23:25 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG?] Composing with ROLE
In-Reply-To: <Pine.MNT.4.10.9909100919400.125-100000@rakastaja>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Martin-Eric Racine <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 10 Sep 1999, Martin-Eric Racine wrote:

> On Fri, 10 Sep 1999, Osman%Pine wrote:
> > Could the ROLE meganism be changed so that when you compose a new msg
> > to someone or more the ROLE's will be checked also?
>
> Do you mean like, equating the Role to which server/Inbox you are
> currently using? Yes, that would be desirable. This way, I would
> not always have to manually select which Role I wanna use to write
> a brand new message (responses are already handled automatically).

Well I have setup several folders wich get "filled" by procmail.
They are for different mailing lists and I just want pine to automaticaly
pick the right ROLE for it when composing a brand new msg.
If that is what you meant with incoming folders; YES, that's what I mean.
Otherwise that would also be nice to have...
not for me because I'm running my own mailserver so I have 1 real
incomming mailbox per user, and not several servers with mailboxes...

TTYL
--
Speak softly and carry a cellular phone.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 10 Sep 1999 08:13:01 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA16694
for <[email protected]>; Fri, 10 Sep 1999 08:13:00 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA10279;
Fri, 10 Sep 1999 08:12:58 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id IAA06553;
Fri, 10 Sep 1999 08:11:00 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id IAA41058
for <[email protected]>; Fri, 10 Sep 1999 08:07:40 -0700
Received: from pilsener.srv.ualberta.ca (pilsener.srv.ualberta.ca [129.128.5.19])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA08041
for <[email protected]>; Fri, 10 Sep 1999 08:07:39 -0700
Received: from altair.ucs.ualberta.ca (altair.ucs.ualberta.ca [129.128.5.41])
by pilsener.srv.ualberta.ca (8.9.3/8.9.3) with ESMTP id JAA01976
for <[email protected]>; Fri, 10 Sep 1999 09:07:38 -0600 (MDT)
Received: from gpu2.srv.ualberta.ca (gpu2.srv.ualberta.ca [129.128.98.12])
by altair.ucs.ualberta.ca (8.9.3/8.9.3) with ESMTP id JAA10888
for <[email protected]>; Fri, 10 Sep 1999 09:07:37 -0600 (MDT)
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 09:07:37 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Lea <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: another Pine 4.10 wierdness
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Something else we found after installing 4.10 was that the first-unseen
selection in the Incoming-startup-rule causes Pine to open at the first
message in the user's inbox rather than at the first unread message.
Changing the default selection from first-unseen to first-recent works
better - it opens the inbox at the first message marked new that has
arrived since the last time you opened Pine - but why doesn't first-unseen
work? I ran this past the sysadmin here who installed the software. He
says it's a bug. Is it? Or is there something he could tweak that would
fix first-unseen's behavior?

Lea

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 10 Sep 1999 13:39:06 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA25346
for <[email protected]>; Fri, 10 Sep 1999 13:39:05 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA20144;
Fri, 10 Sep 1999 13:39:03 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id NAA23670;
Fri, 10 Sep 1999 13:36:59 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id NAA41666
for <[email protected]>; Fri, 10 Sep 1999 13:32:27 -0700
Received: from chinet.com ([email protected] [209.219.112.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21317
for <[email protected]>; Fri, 10 Sep 1999 13:32:27 -0700
Received: from localhost (ahk@localhost)
by chinet.com (8.9.3/8.9.3) with ESMTP id PAA31201
for <[email protected]>; Fri, 10 Sep 1999 15:32:26 -0500
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 15:32:25 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Adam H. Kerman" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

>From: James Kirkpatrick <[email protected]>
>Date: Thu, 09 Sep 1999 15:24:06 -0600 (MDT)

>I've noticed an unfortunate change in Pine 4.10 versus 3.96. In the older
>Pine, if I started Pine from two different sessions the second one would
>detect the first one, and attempt to "hijack" the folders and force the
>older session to read-only. In 4.10 the behavior is reversed in a sense:
>the newer Pine detects the older one and leaves itself in read-only mode.

There's no difference in how the newer session is handled between the two
versions. In 3.96, a new session that opened a folder already in use would also
display that folder as read only.

>I consider this unfortunate because of a common problem: A student logs
>in and is using Pine to read mail. He then loses the session (power
>failure, reboot, whatever) but the UNIX server doesn't know anything has
>happened. He then logs in again and now has read-only access (unless he
>knows enough to find and kill his other process). Thus, the new behavior
>is less desirable than the old behavior.

Hardly. The user must be taught to kill zombie processes if need be.

Sometimes I can lose carrier while telnetting during a ppp session. If I
haven't sent any additional keystrokes, it's possible to suspend the telnet
session and restore the connection and then resume the telnet session as if
nothing had happened.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 10 Sep 1999 13:59:31 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA25707
for <[email protected]>; Fri, 10 Sep 1999 13:59:30 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA17247;
Fri, 10 Sep 1999 13:59:28 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id NAA01458;
Fri, 10 Sep 1999 13:56:49 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id NAA47144
for <[email protected]>; Fri, 10 Sep 1999 13:48:46 -0700
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA23726
for <[email protected]>; Fri, 10 Sep 1999 13:48:46 -0700
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id NAA29473;
Fri, 10 Sep 1999 13:48:44 -0700 (PDT)
Message-Id: <Pine.OSF.4.10.9909101335310.32490-100000@goedel3.math.washington.edu>
Date: Fri, 10 Sep 1999 13:48:43 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: another Pine 4.10 wierdness
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Lea <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Lea ([email protected]) wrote Today:

:)
:) Something else we found after installing 4.10 was that the first-unseen
:) selection in the Incoming-startup-rule causes Pine to open at the first
:) message in the user's inbox rather than at the first unread message.
:) Changing the default selection from first-unseen to first-recent works
:) better - it opens the inbox at the first message marked new that has
:) arrived since the last time you opened Pine - but why doesn't first-unseen
:) work? I ran this past the sysadmin here who installed the software. He
:) says it's a bug. Is it? Or is there something he could tweak that would
:) fix first-unseen's behavior?

It's not a bug, but a feature. The point is that there are two kind of new
messages. Imagine that you have your INBOX empty and then exit pine,
assume further that when you read your e-mail next time you have two new
messages. Checking "first-unseen" or "first-recent" will have the same
effect. Assume that you read the first message but *DO NOT OPEN* the
second one and quit pine. Next assume that a third message arrives to your
INBOX, then the next pine that you use pine the message that you did not
read will be called "UNSEEN" and the one we called third will be called
"NEW". If you have set "first-unseen" set then you will open INBOX in the
UNSEEN message, but if you have it in "first-recent" it will open it in
the real "NEW" message. It depends on how you display your index if you
are able to distinguish this by reading it. The default in pine is that
"UNSEEN" messages and "NEW" messages are both displayed with a "N" in the
index, but you can change this so that "UNSEEN" messages have a "U" in
front of them and "NEW" messages have a "N" in front of them. If you want
to do this you will have to go to your configuration, check "index-format"
and use "IMAPSTATUS" instead of "STATUS", which is the default.

I hope this clarifies the point you made. Maybe the help in pine should
include a pointer to "index-format" and/or "IMAPSTATUS" from the
incoming-startup-rule help.

Eduardo
http://www.math.washington.edu/~chappa/personal.html

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 10 Sep 1999 14:55:03 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27275
for <[email protected]>; Fri, 10 Sep 1999 14:55:02 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA19063;
Fri, 10 Sep 1999 14:55:01 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id OAA27727;
Fri, 10 Sep 1999 14:53:39 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id OAA66808
for <[email protected]>; Fri, 10 Sep 1999 14:50:10 -0700
Received: from federation.addy.com (federation.addy.com [207.239.68.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA00420
for <[email protected]>; Fri, 10 Sep 1999 14:50:08 -0700
Received: from localhost (jim@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id RAA07655 for <[email protected]>; Fri, 10 Sep 1999 17:50:07 -0400 (EDT)
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 17:50:07 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jim Sander <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: pine.conf.fixed file(s)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Quick recap on the problem: I want to restrict *some* users of pine
from doing "dangerous" things, but still allow everyone else to take full
advantage of the nifty features. Using pine.conf.fixed allows lots of
restrictions, but there is no way to selectively enforce these rules.

Quick thanks to the people who responded to me privately: your ideas
were helpfull, but in the end I decided to do things "the hard way" - but
not as hard as a couple of you were trying to make it. :)

Just for future reference, here's what I did...

1. Compile pine like normal (in FreeBSD, I used the ports collection)
2. Install pine like normal
3. copy the pine4 port directory to say "rpine4"
4. modify the patches so that pine.conf.fixed is changed to what I want
(this took about 3 minutes to find, 30 seconds to modify)
5. remake the port, rename the binary pine to "rpine"
6. install rpine into /usr/local
7. set rpine as the login shell for email only people

This means I made *minimal* changes, got what I needed done, and the
few regular pine users will be much happier. No wrappers, read-only files,
or anything of that sort required.

-=Jim=-

P.S. If anyone sees any problems with this setup, please do tell...

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 10 Sep 1999 16:10:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA29017
for <[email protected]>; Fri, 10 Sep 1999 16:10:44 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA21227;
Fri, 10 Sep 1999 16:10:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id QAA06585;
Fri, 10 Sep 1999 16:09:17 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id QAA18368
for <[email protected]>; Fri, 10 Sep 1999 16:05:46 -0700
Received: from darwin.helios.nd.edu ([email protected] [129.74.250.114])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA08567
for <[email protected]>; Fri, 10 Sep 1999 16:05:45 -0700
Received: from localhost (klaberte@localhost)
by darwin.helios.nd.edu (8.9.2/8.9.2) with ESMTP id SAA04701
for <[email protected]>; Fri, 10 Sep 1999 18:05:42 -0500 (EST)
Message-Id: <[email protected]>
Date: Fri, 10 Sep 1999 18:05:41 -0500 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Ken Laberteaux <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: nickname for folder
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: darwin.helios.nd.edu: klaberte owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have a couple of collections of folders. Sometimes I would like to move
a bunch of messages from one folder on one collection to another folder on
another collection.

Often I must move mail from {host1}INBOX to {host2}INBOX.IN.foo,
where foo is a subfolder of IN and IN is a subfolder of INBOX.

It would be nice if I could somehow ascribe a nickname to
{host2}INBOX.IN.foo (e.g. foo2) that would be recognized when I am
looking at messages in {host1}INBOX so I wouldn't need to type it out all
the time. Is there any way to give a nickname to a folder (in this case,
a subfolder on a different collection)?

Ken

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 11 Sep 1999 09:47:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA13609
for <[email protected]>; Sat, 11 Sep 1999 09:47:45 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA04926;
Sat, 11 Sep 1999 09:47:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id JAA17509;
Sat, 11 Sep 1999 09:46:31 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id JAA59760
for <[email protected]>; Sat, 11 Sep 1999 09:41:50 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA08921
for <[email protected]>; Sat, 11 Sep 1999 09:41:49 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id SAA22518
for <[email protected]>; Sat, 11 Sep 1999 18:41:43 +0200
Message-Id: <[email protected]>
Date: Sat, 11 Sep 1999 18:41:43 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] Sort criteria
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi it's me again,

Actualy this post isn't about a BUG but about an ENHANCEMENT request.
I just did it so those developers read it, I haven't read/found any of
them here yet...

Why can't we choose to sort the messages in folders accoarding to their
MSG-ID's?

That would be a REALY GOOD option me thinks!
Think of all the people who use mailing lists...

TTYL.
--
It's not a bug, it's tradition!

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 11 Sep 1999 17:48:56 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA19070
for <[email protected]>; Sat, 11 Sep 1999 17:48:55 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA11682;
Sat, 11 Sep 1999 17:48:54 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id RAA19746;
Sat, 11 Sep 1999 17:47:39 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id RAA05606
for <[email protected]>; Sat, 11 Sep 1999 17:43:52 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA19918
for <[email protected]>; Sat, 11 Sep 1999 17:43:49 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id AAA23329; Sun, 12 Sep 1999 00:50:29 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sat, 11 Sep 99 17:50 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id RAA24601;
Sat, 11 Sep 1999 17:34:12 -0700
Message-Id: <Pine.LNX.4.05.9909111731340.24569-100000@ArmispianSystems.Rossland.bc.ca>
Date: Sat, 11 Sep 1999 17:34:09 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] Sort criteria
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Osman%Pine <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sat, 11 Sep 1999, Osman%Pine wrote:

> Why can't we choose to sort the messages in folders accoarding to their
> MSG-ID's?

What do you mean? Straight by message ids? Or a more complete
threading than the ``ordered subject''? I'd like something like
``threaded'' as a sort option, but it COULD be a high processor use
feature. The other feature, I can understand when looking for a message
by message id (as I find myself doing about once a month (if not more
often) lately), but can't we search for that?

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 08:45:31 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA24748
for <[email protected]>; Mon, 13 Sep 1999 06:20:34 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA13170;
Mon, 13 Sep 1999 06:20:32 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id GAA16384;
Mon, 13 Sep 1999 06:18:24 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id GAA53480
for <[email protected]>; Mon, 13 Sep 1999 06:13:54 -0700
Received: from mail.minerva.net (smtp.minerva.net [206.55.47.252])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA17360
for <[email protected]>; Mon, 13 Sep 1999 06:13:53 -0700
Received: from cr398485-a.lndn1.on.wave.home.com ([24.114.15.13])
by mail.minerva.net (Post.Office MTA v3.5.3 release 223
ID# 0-55980U5000L500S0V35) with SMTP id net
for <[email protected]>; Mon, 13 Sep 1999 09:09:58 -0400
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 09:12:29 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: [email protected] (Mark Aaron Polger)
To: Pine Discussion Forum <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I just would like to know if you know of any reviews of the Pine email client.
I am doing a research paper on the Pine email client.

Please let me know.
Thank you.
Sincerely,
Mark Polger
[email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 08:54:38 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA08296
for <[email protected]>; Sun, 12 Sep 1999 21:15:43 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA05226;
Sun, 12 Sep 1999 21:15:42 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id VAA09320;
Sun, 12 Sep 1999 21:14:35 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id VAA49354
for <[email protected]>; Sun, 12 Sep 1999 21:11:36 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA06111
for <[email protected]>; Sun, 12 Sep 1999 21:11:35 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id XAA06185
for <[email protected]>; Sun, 12 Sep 1999 23:11:05 -0500 (CDT)
Message-Id: <[email protected]>
Date: Sun, 12 Sep 1999 23:11:05 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <199909130356.XAA01821@ocalhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

What did Pine 3.96 do when the first open session was in the process of
editing a message? If the first session was subsequently killed, the
incomplete message should have been saved, but would it be saved if the
session was 'read-only'? What if the user returned to the first session
somehow and finished composing the message and mailed it out--would the
Fcc be saved properly? (If the session is read-only, can it write the
Fcc?)

If any of these scenarios caused problems in 3.96, it might explain why
the pine team made the change in 4.10. If they don't cause problems, I
don't understand the need for the change.

Regards,

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 08:55:06 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA07946
for <[email protected]>; Sun, 12 Sep 1999 21:03:15 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA02014;
Sun, 12 Sep 1999 21:03:13 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id VAA20216;
Sun, 12 Sep 1999 21:00:30 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id UAA49394
for <[email protected]>; Sun, 12 Sep 1999 20:56:40 -0700
Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id UAA22206
for <[email protected]>; Sun, 12 Sep 1999 20:56:40 -0700
Received: from peak.org [207.141.129.64] by 1stpc.org with ESMTP
(SMTPD32-4.04) id A81967FB0212; Mon, 13 Sep 1999 00:05:45 EST
Received: by peak.org (8.9.3/8.9.0) id XAA01821
for [email protected]; Sun, 12 Sep 1999 23:56:32 -0400 (EDT)
Message-Id: <199909130356.XAA01821@ocalhost>
Date: Sun, 12 Sep 1999 23:56:29 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Timothy J Luoma <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
References: <[email protected]>
Content-Type: text/plain
MIME-Version: 1.0
X-To: Pine Discussion Forum <[email protected]>
X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff
X-Organization: http://www.peak.org/~luomat/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Replying to message of Fri, 10 Sep 1999 15:32:25 -0500 (CDT)
from "Adam H. Kerman" <[email protected]>
regarding ``Re: Pine and read-only folders''

> There's no difference in how the newer session is handled between
> the two versions. In 3.96, a new session that opened a folder
> already in use would also display that folder as read only.

Not so, at least not here.

I opened a mailbox with 3.96.
I then started a second session with 3.96
I saw this in the original session:

[Another Pine is accessing folder. Session now Read-Only.]

And I see this in the 2nd PINE session

[Trying to get mailbox lock from process 1630]
and then
[Folder "test" opened with 2 messages]

I did the same thing with pine 4.10 and immediately get this message

[Mailbox is open by another process, access is readonly]
and then
[Folder "test" opened with 2 messages READONLY]

> Hardly. The user must be taught to kill zombie processes if need be.

__IF___ that option is even available to them (there are menu-driven shell
accounts which give access to PINE but not to commandline)

Even if it is, I'm not sure why this behavior was changed, and why it is
"better" when it is easy to see when it could become a problem.

TjL

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 08:55:43 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA05296
for <[email protected]>; Sun, 12 Sep 1999 18:01:56 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA32042;
Sun, 12 Sep 1999 18:01:54 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id SAA05344;
Sun, 12 Sep 1999 18:00:36 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id RAA21314
for <[email protected]>; Sun, 12 Sep 1999 17:56:53 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA19415
for <[email protected]>; Sun, 12 Sep 1999 17:56:52 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id CAA30614;
Mon, 13 Sep 1999 02:56:49 +0200
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 02:56:49 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: nickname for folder
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Ken Laberteaux <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 10 Sep 1999, Ken Laberteaux wrote:

> I have a couple of collections of folders. Sometimes I would like to move
> a bunch of messages from one folder on one collection to another folder on
> another collection.
>
> Often I must move mail from {host1}INBOX to {host2}INBOX.IN.foo,
> where foo is a subfolder of IN and IN is a subfolder of INBOX.
>
> It would be nice if I could somehow ascribe a nickname to
> {host2}INBOX.IN.foo (e.g. foo2) that would be recognized when I am
> looking at messages in {host1}INBOX so I wouldn't need to type it out all
> the time. Is there any way to give a nickname to a folder (in this case,
> a subfolder on a different collection)?

There is a way to do this easy:
Select the messages you want to copy with ";" then "a" to apply to the
selected msg's, then "^T" to browse your folders and 2x<enter>.

TTYL.
--
The dark ages were caused by the Y1K problem.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 08:55:47 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA05190
for <[email protected]>; Sun, 12 Sep 1999 17:55:27 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02248;
Sun, 12 Sep 1999 17:55:25 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id RAA22379;
Sun, 12 Sep 1999 17:53:48 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id RAA21456
for <[email protected]>; Sun, 12 Sep 1999 17:48:16 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA12869
for <[email protected]>; Sun, 12 Sep 1999 17:48:15 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id CAA26471;
Mon, 13 Sep 1999 02:44:36 +0200
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 02:44:36 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] Sort criteria
In-Reply-To: <Pine.LNX.4.05.9909111731340.24569-100000@ArmispianSystems.Rossland.bc.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jessica Rasku <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sat, 11 Sep 1999, Jessica Rasku wrote:
> On Sat, 11 Sep 1999, Osman%Pine wrote:
> > Why can't we choose to sort the messages in folders accoarding to their
> > MSG-ID's?
> What do you mean? Straight by message ids? Or a more complete
> threading than the ``ordered subject''? I'd like something like
> ``threaded'' as a sort option, but it COULD be a high processor use
> feature. The other feature, I can understand when looking for a message
> by message id (as I find myself doing about once a month (if not more
> often) lately), but can't we search for that?

Yes I mean threaded.
You must use their "Message-Id:" for that...
In conjuction with "In-Reply-To:" ofcourse.
And a slithly different folder listing.

TTYL.
--
Intel: where Quality is job number 0.9998782345!

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 09:06:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA31259
for <[email protected]>; Mon, 13 Sep 1999 09:06:23 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA13828;
Mon, 13 Sep 1999 09:06:21 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id JAA04213;
Mon, 13 Sep 1999 09:04:39 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id JAA51158
for <[email protected]>; Mon, 13 Sep 1999 09:01:10 -0700
Received: from mbox-1.inet.fi (mbox-1.inet.fi [192.89.123.189])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA18698
for <[email protected]>; Mon, 13 Sep 1999 09:01:09 -0700
Received: from qn-lpr1-99.quicknet.inet.fi ([194.251.105.99]:1526 "EHLO qn-lpr1-99.quicknet.inet.fi") by mbox-1.inet.fi with ESMTP id <S206837AbPIMQA4>; Mon, 13 Sep 1999 19:00:56 +0300
Message-Id: <Pine.MNT.4.10.9909131851480.311-100000@rakastaja>
Date: Mon, 13 Sep 1999 19:00:50 +0300
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Martin-Eric Racine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: design changes 3.96 -> 4.10
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine List <[email protected]>
X-Sender: q-funk@rakastaja
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello,

One really annoying change between Pine 3.96 and 4.10:

every time one enters the Folder List, Pine 4.10 immediately
tries to connect the news server.

Previously, in 3.96, it would only initiate a connection to the
news server if/when the cursor entered the News Collection
section of the Folder List.

The problem with that is, on a slow connection, it takes second or
even minutes before the connection is made. When someone only wanted
access to their saved-messages (or whichever else), this gets really
annoying to wait for Pine to connect to news.

Is there any compile option to revert to the old behavior?

--
----------------------------------------------------------------
Martin-�ric Racine The Atari Stacy and TT030 Homepage Lappeenranta,
Finland http://members.tripod.com/~TT030/
----------------------------------------------------------------
"When the time comes, I will know and I shall be." Q-Funk

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 10:04:42 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA00374
for <[email protected]>; Mon, 13 Sep 1999 10:04:40 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15596;
Mon, 13 Sep 1999 10:04:38 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id KAA07785;
Mon, 13 Sep 1999 10:02:16 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id JAA16890
for <[email protected]>; Mon, 13 Sep 1999 09:57:25 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA21299
for <[email protected]>; Mon, 13 Sep 1999 09:57:24 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id LAA25902
for <[email protected]>; Mon, 13 Sep 1999 11:56:53 -0500 (CDT)
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 11:56:53 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: design changes 3.96 -> 4.10
In-Reply-To: <Pine.MNT.4.10.9909131851480.311-100000@rakastaja>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I second the nomination to change this behavior. There have actually been
several occasions where I had to telnet into a different session and kill
pine because I couldn't get it to stop trying to access the news server.
And this happened when I was connecting to the news server by accident
(it's easy to hit ^N accidentally when you are navigating mail
collections).

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

On Mon, 13 Sep 1999, Martin-Eric Racine wrote:

> Hello,
>
> One really annoying change between Pine 3.96 and 4.10:
>
> every time one enters the Folder List, Pine 4.10 immediately
> tries to connect the news server.
>
> Previously, in 3.96, it would only initiate a connection to the
> news server if/when the cursor entered the News Collection
> section of the Folder List.
>
> The problem with that is, on a slow connection, it takes second or
> even minutes before the connection is made. When someone only wanted
> access to their saved-messages (or whichever else), this gets really
> annoying to wait for Pine to connect to news.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 10:59:47 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01614
for <[email protected]>; Mon, 13 Sep 1999 10:59:46 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20714;
Mon, 13 Sep 1999 10:59:44 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id KAA16980;
Mon, 13 Sep 1999 10:57:48 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id KAA13404
for <[email protected]>; Mon, 13 Sep 1999 10:54:06 -0700
Received: from desh.cse.iitd.ernet.in (IDENT:[email protected] [202.141.68.3])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA30927
for <[email protected]>; Mon, 13 Sep 1999 10:54:02 -0700
Received: from hindol.cse.iitd.ernet.in ([email protected] [10.20.13.15])
by desh.cse.iitd.ernet.in (8.8.7/8.8.7) with ESMTP id XAA03888
for <[email protected]>; Mon, 13 Sep 1999 23:25:47 +0530
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 23:25:52 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Raghavendra Kulkarni <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: BCC: field in the compose form.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I dont get the "BCC:" field in the compose form.
Looking into settings doesnt seem to help.

I would greatly appreciate if I can get this info:

Can I modify my pine settings to get bcc field.
Or does it depend on the mail server.

I am using a linux box with my home area mounted via nfs.

Thanks!
RLK

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 11:13:04 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA01947
for <[email protected]>; Mon, 13 Sep 1999 11:13:03 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA17773;
Mon, 13 Sep 1999 11:13:01 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id LAA12301;
Mon, 13 Sep 1999 11:10:54 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id LAA23604
for <[email protected]>; Mon, 13 Sep 1999 11:07:24 -0700
Received: from bonjour.cc.columbia.edu (IDENT:[email protected] [128.59.59.133])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27817
for <[email protected]>; Mon, 13 Sep 1999 11:07:23 -0700
Received: from localhost by bonjour.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id OAA14542;
Mon, 13 Sep 1999 14:07:21 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 14:07:21 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Freda B Birnbaum <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: BCC: field in the compose form.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Cc: Freda B Birnbaum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 13 Sep 1999, Raghavendra Kulkarni wrote:

> I dont get the "BCC:" field in the compose form.
> Looking into settings doesnt seem to help.

Have you tried typing ^R (for "rich header") when you're in the header
area?

Freda Birnbaum, [email protected]
"Call on God, but row away from the rocks"

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 11:47:18 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02912
for <[email protected]>; Mon, 13 Sep 1999 11:47:16 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA18970;
Mon, 13 Sep 1999 11:47:14 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id LAA20063;
Mon, 13 Sep 1999 11:45:41 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id LAA43500
for <[email protected]>; Mon, 13 Sep 1999 11:39:15 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA31120
for <[email protected]>; Mon, 13 Sep 1999 11:39:14 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id UAA01335
for <[email protected]>; Mon, 13 Sep 1999 20:39:13 +0200
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 20:39:13 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] Composing with ROLE
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

Another bug is:
The role's selection is not done correctly.
When you have selected an adress out-of your address book in the TO field,
the fullname is included.
That's OK but...
The selection should only take in account the email address and discard
the fullname.
As an example take the fullname I've gave to this list.
If I would select this as a TO creterion it will not match.

And I would realy like an option to override the receipient list when a
role is been selected.
Now I have to manualy delete the receipients and select new ones.
TTYL.
--
It is easier to fix Unix than to live with NT.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 13:05:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05558
for <[email protected]>; Mon, 13 Sep 1999 13:05:09 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21392;
Mon, 13 Sep 1999 13:05:07 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id NAA12987;
Mon, 13 Sep 1999 13:03:22 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA13402
for <[email protected]>; Mon, 13 Sep 1999 12:59:53 -0700
Received: from mm01snlnto.sandia.gov (mm01snlnto.sandia.gov [132.175.109.20])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA12430
for <[email protected]>; Mon, 13 Sep 1999 12:59:53 -0700
Received: from 132.175.109.1 by mm01snlnto.sandia.gov with ESMTP (
WorldSecure Server SMTP Relay(WSS) v3.6); Mon, 13 Sep 99 13:59:51 -0600
Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190])
by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id NAA18902 for
<[email protected]>; Mon, 13 Sep 1999 13:59:51 -0600 (MDT)
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 13:59:47 -0600
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Daniel Sands" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <199909130356.XAA01821@ocalhost>
MIME-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: "Pine Discussion Forum" <[email protected]>
X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c
X-WSS-ID: 1BC3883D22826-01-01
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

>
> > Hardly. The user must be taught to kill zombie processes if need be.
>
> __IF___ that option is even available to them (there are menu-driven shell
> accounts which give access to PINE but not to commandline)
>
> Even if it is, I'm not sure why this behavior was changed, and why it is
> "better" when it is easy to see when it could become a problem.

Why doesn't Pine detect when the TTY is dead and kill itself? Since it's
supposed to be an interactive mailer, it makes no sense to keep going when no
more input can be given.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 13:18:12 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05990
for <[email protected]>; Mon, 13 Sep 1999 13:18:11 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21726;
Mon, 13 Sep 1999 13:18:09 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id NAA13605;
Mon, 13 Sep 1999 13:16:02 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id NAA61924
for <[email protected]>; Mon, 13 Sep 1999 13:11:59 -0700
Received: from nimbus.anzio.com (IDENT:[email protected] [204.201.253.34])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA28186
for <[email protected]>; Mon, 13 Sep 1999 13:11:58 -0700
Received: from localhost (ras@localhost)
by nimbus.anzio.com (8.8.7/8.8.7) with ESMTP id NAA24202
for <[email protected]>; Mon, 13 Sep 1999 13:11:47 -0700
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 13:11:47 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bob Rasmussen <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I believe someone on this thread suggested that when a process was orphaned,
it was possible to reattach to it. Is that true? I've never been able to
figure out a way to do that. Please explain.

Simple case: I'm using a modem to access Unix. The modem line drops, and the
Unix is configured to not quit on a SIGHUP. I dial back in. a 'ps' shows the
process still running. How can I reattach to it?

--
Regards,
...Bob Rasmussen, President, Rasmussen Software, Inc.

personal e-mail: [email protected]
company e-mail: [email protected] or [email protected] or [email protected]
ftp://ftp.anzio.com voice: 503-624-0360
http://www.anzio.com fax: 503-624-0760

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 20:25:21 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA18800
for <[email protected]>; Mon, 13 Sep 1999 20:25:20 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA02930;
Mon, 13 Sep 1999 20:25:18 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id UAA03985;
Mon, 13 Sep 1999 20:23:37 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id UAA65792
for <[email protected]>; Mon, 13 Sep 1999 20:20:04 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA09831
for <[email protected]>; Mon, 13 Sep 1999 20:20:03 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA02832
for <[email protected]>; Mon, 13 Sep 1999 20:20:03 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id WAA06938
for <[email protected]>; Mon, 13 Sep 1999 22:19:32 -0500 (CDT)
Message-Id: <[email protected]>
Date: Mon, 13 Sep 1999 22:19:31 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: perl, grepmail
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Pine Development Team (and others):

What do you think about adding an interface to external perl scripts in
the next release of pine (at least for Unix). It could work like this:
Users could enable a feature like grepmail...

[x] enable perl
[x] enable grepmail
[x] enable MHonArc

and pine could present an interface for the user to perform various tasks.
Programs like perl, grepmail, MHonArc, etc. would not be bundled with pine
and would have to be installed by the user or sysadmin. Would that be a
good way to extend pine functionality without bloating pine itself too
much? If pine could call other programs in the system to perform tasks,
it could do a lot more for us.

I especially like grepmail and I can see how that could be added to pine.

Regards,

Mike

--
Michael B. Miller, M.S., Ph.D., M.P.E.
Department of Psychology
210 McAlester Hall
University of Missouri--Columbia
Columbia, MO 65211
Phone: (573) 882-5671
Fax: (573) 882-7710
e-mail: [email protected]
web: http://taxa.psyc.missouri.edu/~mbmiller/

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 21:31:11 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA19356
for <[email protected]>; Mon, 13 Sep 1999 21:31:10 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA00748;
Mon, 13 Sep 1999 21:31:08 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id VAA28122;
Mon, 13 Sep 1999 21:30:07 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id VAA36266
for <[email protected]>; Mon, 13 Sep 1999 21:26:13 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA08872
for <[email protected]>; Mon, 13 Sep 1999 21:26:12 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id GAA07463
for <[email protected]>; Tue, 14 Sep 1999 06:26:11 +0200
Message-Id: <[email protected]>
Date: Tue, 14 Sep 1999 06:26:11 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] Alternative addresses
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

The "Alternative addresses" option is case-sensitive,
FQ-email-addresses are case-INsensitive.

Is this know?
If so; Why is it not fixed yet in 4.10 ?

TTYL.
--
The three Rs of Microsoft support: Retry, Reboot, Reinstall.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 22:57:54 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA20483
for <[email protected]>; Mon, 13 Sep 1999 22:57:52 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA05571;
Mon, 13 Sep 1999 22:57:51 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id WAA13428;
Mon, 13 Sep 1999 22:57:00 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id WAA18370
for <[email protected]>; Mon, 13 Sep 1999 22:53:49 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA22757
for <[email protected]>; Mon, 13 Sep 1999 22:53:48 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id GAA14639; Tue, 14 Sep 1999 06:00:32 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Mon, 13 Sep 99 23:00 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA05642;
Mon, 13 Sep 1999 22:43:34 -0700
Message-Id: <Pine.LNX.4.05.9909132236080.3175-100000@ArmispianSystems.Rossland.bc.ca>
Date: Mon, 13 Sep 1999 22:43:34 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] Alternative addresses
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Osman%Pine <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 14 Sep 1999, Osman%Pine wrote:

> The "Alternative addresses" option is case-sensitive,
> FQ-email-addresses are case-INsensitive.

Can you clarify. I know that the domain portion of the e-mail
address, is case insesitive, but the user portion can be case sensitive.
And, as such, I would think it would be ``wrong'' to make the user portion
case sensitive. It may be ``nice'' to be able to turn on, or off case
sensitivity in terms of the user portion, but I'd think it would be wrong
to assume case insensitivity, even though in most cases the user portion
is also case insesitive.

> Is this know?

I'm sure that the Pine development team is well aware of the
appropriate standards, they may not know that the domain name portion is
case sensitive, if that is the case.

> If so; Why is it not fixed yet in 4.10 ?

Well, if it is a ``violation'' of the standard, then yes it should
be fixed, and probably hasn't been because they are not aware that it is.
If, it is in the user name portion that MAY be case insesitive (but isn't
required to be), then it is simply a lack of a way to turn on that
insesitivity.

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Sep 1999 23:32:43 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA20767
for <[email protected]>; Mon, 13 Sep 1999 23:32:41 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA02783;
Mon, 13 Sep 1999 23:32:40 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA14090;
Mon, 13 Sep 1999 23:31:53 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA53352
for <[email protected]>; Mon, 13 Sep 1999 23:28:54 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA16959
for <[email protected]>; Mon, 13 Sep 1999 23:28:53 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id IAA17045;
Tue, 14 Sep 1999 08:28:44 +0200
Message-Id: <[email protected]>
Date: Tue, 14 Sep 1999 08:28:43 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] Alternative addresses
In-Reply-To: <Pine.LNX.4.05.9909132236080.3175-100000@ArmispianSystems.Rossland.bc.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jessica Rasku <[email protected]>
X-Cc: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 13 Sep 1999, Jessica Rasku wrote:

> On Tue, 14 Sep 1999, Osman%Pine wrote:
>
> > The "Alternative addresses" option is case-sensitive,
> > FQ-email-addresses are case-INsensitive.
>
> Can you clarify. I know that the domain portion of the e-mail
> address, is case insesitive, but the user portion can be case sensitive.
> And, as such, I would think it would be ``wrong'' to make the user portion
> case sensitive. It may be ``nice'' to be able to turn on, or off case
> sensitivity in terms of the user portion, but I'd think it would be wrong
> to assume case insensitivity, even though in most cases the user portion
> is also case insesitive.
>
> > Is this know?
>
> I'm sure that the Pine development team is well aware of the
> appropriate standards, they may not know that the domain name portion is
> case sensitive, if that is the case.
>
> > If so; Why is it not fixed yet in 4.10 ?
>
> Well, if it is a ``violation'' of the standard, then yes it should
> be fixed, and probably hasn't been because they are not aware that it is.
> If, it is in the user name portion that MAY be case insesitive (but isn't
> required to be), then it is simply a lack of a way to turn on that
> insesitivity.

Sorry was my fault, well partialy at least!
It seems to work on the next start-up of pine.
This is odd cause there is no msg stating that clearly as far as I
remember.

Sorry for the wrong posting.

BUT...!
It doesn't handle single names.
I can't use just "osman" and get:
"[email protected]" and
"[email protected]" and
"[email protected]" etc...
recognized, they all point to me on the SAME machine...

Is there a way?
TTYL.
--
Intel: where Quality is job number 0.9998782345!

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 04:49:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA28364
for <[email protected]>; Tue, 14 Sep 1999 04:49:08 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA07946;
Tue, 14 Sep 1999 04:49:06 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id EAA22809;
Tue, 14 Sep 1999 04:48:08 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id EAA52586
for <[email protected]>; Tue, 14 Sep 1999 04:43:59 -0700
Received: from rrzs2.rz.uni-regensburg.de (rrzs2.rz.uni-regensburg.de [132.199.1.2])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA32610
for <[email protected]>; Tue, 14 Sep 1999 04:43:34 -0700
Received: from localhost.localdomain (rrzras2-93.rz.uni-regensburg.de [132.199.209.93])
by rrzs2.rz.uni-regensburg.de (8.8.8/8.8.8) with ESMTP id NAA21215
for <[email protected]>; Tue, 14 Sep 1999 13:43:25 +0200 (MET DST)
Received: from localhost (claus@localhost)
by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA00818
for <[email protected]>; Tue, 14 Sep 1999 13:27:30 +0200
Message-Id: <[email protected]>
Date: Tue, 14 Sep 1999 13:27:30 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Claus Atzenbeck <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Role with Lcc
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: pine-info <[email protected]>
X-Authentication-Warning: localhost.localdomain: claus owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is it true that I cannot create a role with entries for "Lcc"? (Only "To",
"Cc", and "Fcc" can be used!?)

Please let me know...

Gruss,
Claus.

--
Claus Atzenbeck, stud. phil.
seminar papers: http://homepages.uni-regensburg.de/~atc16247/
[This mail was created on a 100% Micro$oft-free computer.]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 08:47:47 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31512
for <[email protected]>; Tue, 14 Sep 1999 08:47:46 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA12529;
Tue, 14 Sep 1999 08:47:44 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id IAA25871;
Tue, 14 Sep 1999 08:45:50 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id IAA17022
for <[email protected]>; Tue, 14 Sep 1999 08:42:18 -0700
Received: from roper.uwyo.edu ([email protected] [129.72.10.8])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31007
for <[email protected]>; Tue, 14 Sep 1999 08:42:18 -0700
Received: from asuwlink.uwyo.edu (asuwlink.uwyo.edu [129.72.60.2])
by ROPER.UWYO.EDU (PMDF V5.2-32 #33749)
with ESMTP id <[email protected]> for [email protected];
Tue, 14 Sep 1999 09:41:28 -0600 (MDT)
Received: from localhost (jimkirk@localhost) by asuwlink.uwyo.edu (8.8.8/8.8.7)
with ESMTP id JAA20889; Tue, 14 Sep 1999 09:41:27 -0600 (MDT)
Message-Id: <[email protected]>
Date: Tue, 14 Sep 1999 09:41:27 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Kirkpatrick <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-To: Bob Rasmussen <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-warning: asuwlink.uwyo.edu: jimkirk owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is rather easy to do on VMS, one of the supported operating systems
for Pine. On UNIX (Solaris) I'd like to know ...

Jim

On Mon, 13 Sep 1999, Bob Rasmussen wrote:

> I believe someone on this thread suggested that when a process was orphaned,
> it was possible to reattach to it. Is that true? I've never been able to
> figure out a way to do that. Please explain.
>
> Simple case: I'm using a modem to access Unix. The modem line drops, and the
> Unix is configured to not quit on a SIGHUP. I dial back in. a 'ps' shows the
> process still running. How can I reattach to it?
>
> --
> Regards,
> ....Bob Rasmussen, President, Rasmussen Software, Inc.
>
> personal e-mail: [email protected]
> company e-mail: [email protected] or [email protected] or [email protected]
> ftp://ftp.anzio.com voice: 503-624-0360
> http://www.anzio.com fax: 503-624-0760

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 08:51:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31658
for <[email protected]>; Tue, 14 Sep 1999 08:51:45 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA15946;
Tue, 14 Sep 1999 08:51:42 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id IAA00813;
Tue, 14 Sep 1999 08:49:09 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id IAA65930
for <[email protected]>; Tue, 14 Sep 1999 08:42:19 -0700
Received: from roper.uwyo.edu ([email protected] [129.72.10.8])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31011
for <[email protected]>; Tue, 14 Sep 1999 08:42:18 -0700
Received: from asuwlink.uwyo.edu (asuwlink.uwyo.edu [129.72.60.2])
by ROPER.UWYO.EDU (PMDF V5.2-32 #33749)
with ESMTP id <[email protected]> for [email protected];
Tue, 14 Sep 1999 09:40:19 -0600 (MDT)
Received: from localhost (jimkirk@localhost) by asuwlink.uwyo.edu (8.8.8/8.8.7)
with ESMTP id JAA20504; Tue, 14 Sep 1999 09:40:19 -0600 (MDT)
Message-Id: <[email protected]>
Date: Tue, 14 Sep 1999 09:40:18 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Kirkpatrick <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-To: Daniel Sands <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-warning: asuwlink.uwyo.edu: jimkirk owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Define "dead". If a PC powers off, the host can't tell if it's dead or if
the user simply hasn't typed something for a while. Then, define "a
while". Some systems kill idle processes, but only after several hours or
days (or not at all); the user might want to get at their mail NOW, not in
a few hours.

Jim

On Mon, 13 Sep 1999, Daniel Sands wrote:

> >
> > > Hardly. The user must be taught to kill zombie processes if need be.
> >
> > __IF___ that option is even available to them (there are menu-driven shell
> > accounts which give access to PINE but not to commandline)
> >
> > Even if it is, I'm not sure why this behavior was changed, and why it is
> > "better" when it is easy to see when it could become a problem.
>
> Why doesn't Pine detect when the TTY is dead and kill itself? Since it's
> supposed to be an interactive mailer, it makes no sense to keep going when no
> more input can be given.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 09:33:13 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA32577
for <[email protected]>; Tue, 14 Sep 1999 09:33:12 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA17270;
Tue, 14 Sep 1999 09:33:08 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id JAA15574;
Tue, 14 Sep 1999 09:31:44 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id JAA18310
for <[email protected]>; Tue, 14 Sep 1999 09:28:23 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA31958
for <[email protected]>; Tue, 14 Sep 1999 09:28:23 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id LAA00481
for <[email protected]>; Tue, 14 Sep 1999 11:27:51 -0500 (CDT)
Message-Id: <[email protected]>
Date: Tue, 14 Sep 1999 11:27:51 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm using Solaris. I think that it is not possible to run a process in
foreground if it was started by another shell. Maybe I'm wrong, but I've
never seen it done and I've tried to find a way and I've failed.

There is a program called 'screen' that might allow you to reconnect to a
process from a new shell, but screen has to have been called in advance, I
think. I don't know much about screen, but in Solaris OS you can get info
as follows:

man screen

Regards,

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

On Tue, 14 Sep 1999, James Kirkpatrick wrote:

> This is rather easy to do on VMS, one of the supported operating systems
> for Pine. On UNIX (Solaris) I'd like to know ...
>
> Jim
>
> On Mon, 13 Sep 1999, Bob Rasmussen wrote:
>
> > I believe someone on this thread suggested that when a process was orphaned,
> > it was possible to reattach to it. Is that true? I've never been able to
> > figure out a way to do that. Please explain.
> >
> > Simple case: I'm using a modem to access Unix. The modem line drops, and the
> > Unix is configured to not quit on a SIGHUP. I dial back in. a 'ps' shows the
> > process still running. How can I reattach to it?

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 12:35:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05289
for <[email protected]>; Tue, 14 Sep 1999 12:35:09 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA23154;
Tue, 14 Sep 1999 12:35:07 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id MAA23783;
Tue, 14 Sep 1999 12:32:48 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA50640
for <[email protected]>; Tue, 14 Sep 1999 12:23:58 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01949
for <[email protected]>; Tue, 14 Sep 1999 12:23:57 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id TAA07577; Tue, 14 Sep 1999 19:30:33 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 14 Sep 99 12:30 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id MAA13099;
Tue, 14 Sep 1999 12:14:47 -0700
Message-Id: <Pine.LNX.4.05.9909141213580.9932-100000@ArmispianSystems.Rossland.bc.ca>
Date: Tue, 14 Sep 1999 12:14:45 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: James Kirkpatrick <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 14 Sep 1999, James Kirkpatrick wrote:

> This is rather easy to do on VMS, one of the supported operating systems
> for Pine. On UNIX (Solaris) I'd like to know ...

Ah, maybe that's where I got this idea from. My experience with
VMS. Thanks. Maybe it's not possible, but it should be somehow...

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 18:50:39 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA13849
for <[email protected]>; Tue, 14 Sep 1999 18:50:38 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA02575;
Tue, 14 Sep 1999 18:50:36 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id SAA12512;
Tue, 14 Sep 1999 18:49:20 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id SAA43614
for <[email protected]>; Tue, 14 Sep 1999 18:46:02 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA11345
for <[email protected]>; Tue, 14 Sep 1999 18:46:01 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id DAA25108;
Wed, 15 Sep 1999 03:45:59 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 03:45:59 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Role with Lcc
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Claus Atzenbeck <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 14 Sep 1999, Claus Atzenbeck wrote:

> Is it true that I cannot create a role with entries for "Lcc"? (Only "To",
> "Cc", and "Fcc" can be used!?)
>
> Please let me know...

Wll actualy you can create role's with Createria's:
"To:", "From:", "Sender:", "Cc:", "Newsgrps:" and "Subject:"

And with changing behaviour's:
"From:", "Fcc:", Signature and Template to use.

This is the total, so: No "Lcc:" changing behaviour. :-((

TTYL.
--
It is easier to fix Unix than to live with NT.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 19:19:55 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA14119
for <[email protected]>; Tue, 14 Sep 1999 19:19:54 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03045;
Tue, 14 Sep 1999 19:19:52 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id TAA13403;
Tue, 14 Sep 1999 19:18:53 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id TAA48260
for <[email protected]>; Tue, 14 Sep 1999 19:15:43 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA18973
for <[email protected]>; Tue, 14 Sep 1999 19:15:43 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id EAA02685;
Wed, 15 Sep 1999 04:15:12 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 04:15:11 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: James Kirkpatrick <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 14 Sep 1999, James Kirkpatrick wrote:

> On Mon, 13 Sep 1999, Daniel Sands wrote:
> > > > Hardly. The user must be taught to kill zombie processes if need be.
> > >
> > > __IF___ that option is even available to them (there are menu-driven shell
> > > accounts which give access to PINE but not to commandline)
> > >
> > > Even if it is, I'm not sure why this behavior was changed, and why it is
> > > "better" when it is easy to see when it could become a problem.
> >
> > Why doesn't Pine detect when the TTY is dead and kill itself? Since it's
> > supposed to be an interactive mailer, it makes no sense to keep going when no
> > more input can be given.
>
> Define "dead". If a PC powers off, the host can't tell if it's dead or if
> the user simply hasn't typed something for a while.

Well if keep-alive is been used and the line drops:
- The modem will hangup if a modem is used.
- The process attached to the connection would get a SIGHUP,
and quit. (eg: pppd if that's used.)
- The shell should get a SIGHUP and quit.
- All its child's that still are attached to the parent (the shell),
should get a SIGHUP / SIGQUIT / SIGTERM / SIGABRT or whatever,
and they should quit.

> Then, define "a while".

"A while":
Longer than a moment and shorter than forever. ;-)

> Some systems kill idle processes, but only after several hours or
> days (or not at all);

That's correct behaviour me thinks...

> the user might want to get at their mail NOW, not in a few hours.

[BOFH mode on]
Well you know: those users want all kinds of things...
[BOFH mode off]

;-))
TTYL.
--
Where do you think you're going today?

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 19:34:49 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA14265
for <[email protected]>; Tue, 14 Sep 1999 19:34:48 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03304;
Tue, 14 Sep 1999 19:34:47 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id TAA26453;
Tue, 14 Sep 1999 19:32:23 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id TAA72340
for <[email protected]>; Tue, 14 Sep 1999 19:29:17 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA15311
for <[email protected]>; Tue, 14 Sep 1999 19:29:16 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id EAA07493;
Wed, 15 Sep 1999 04:29:13 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 04:29:13 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: perl, grepmail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 13 Sep 1999, Mike Miller wrote:

> Pine Development Team (and others):
>
> What do you think about adding an interface to external perl scripts in
> the next release of pine (at least for Unix). It could work like this:
> Users could enable a feature like grepmail...
>
> [x] enable perl
> [x] enable grepmail
> [x] enable MHonArc
>
> and pine could present an interface for the user to perform various tasks.
> Programs like perl, grepmail, MHonArc, etc. would not be bundled with pine
> and would have to be installed by the user or sysadmin. Would that be a
> good way to extend pine functionality without bloating pine itself too
> much? If pine could call other programs in the system to perform tasks,
> it could do a lot more for us.
>
> I especially like grepmail and I can see how that could be added to pine.

I don't know grepmail...
But if they would impliment such behaviour they ought to do it in an
extensible way like:
[x] enable external tasks

And the system administrator should be the only one who can configure them
in "pine.conf.fixed". Otherwise it would introduce security problems.

And in that file it would be cfg'ed like eg:
external-task-menu= "<text for item #1>",
"<text for item #2>",
"<text for item #3>",
etc...
external-task-actions= "<command for menu item #1>",
"<command for menu item #2>",
"<command for menu item #3>",
etc...

And if "enable external tasks" is set you would get an option in your
screens to pop-up the defined menu.

TTYL.
--
Actually, Microsoft is sort of a mixture between the Borg and the Ferengi.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 21:28:43 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA15616
for <[email protected]>; Tue, 14 Sep 1999 21:28:42 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA05443;
Tue, 14 Sep 1999 21:28:40 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id VAA25269;
Tue, 14 Sep 1999 21:27:18 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id VAA20808
for <[email protected]>; Tue, 14 Sep 1999 21:24:06 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA16789
for <[email protected]>; Tue, 14 Sep 1999 21:24:05 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id GAA14099
for <[email protected]>; Wed, 15 Sep 1999 06:24:04 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 06:24:03 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] seclection of messages.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

If you select a number of messages using ";" and want to "Narrow" your
selection it unselects the previously selected ones and you end-up with
the ones which comply with your creterium you used to "Narrow".

This is realy broken!

The "Broaden" functionality works correct though...

TTYL.
--

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 22:38:25 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA16324
for <[email protected]>; Tue, 14 Sep 1999 22:38:24 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA06575;
Tue, 14 Sep 1999 22:38:22 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id WAA06483;
Tue, 14 Sep 1999 22:37:37 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id WAA26810
for <[email protected]>; Tue, 14 Sep 1999 22:34:27 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA09714
for <[email protected]>; Tue, 14 Sep 1999 22:34:27 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id AAA25559
for <[email protected]>; Wed, 15 Sep 1999 00:33:54 -0500 (CDT)
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 00:33:54 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 15 Sep 1999, Osman%Pine wrote:

> If you select a number of messages using ";" and want to "Narrow" your
> selection it unselects the previously selected ones and you end-up with
> the ones which comply with your creterium you used to "Narrow".
>
> This is realy broken!
>
> The "Broaden" functionality works correct though...

This is not true for me. Both narrow and broaden work fine on Solaris
using the precompiled pine. What OS are you using?

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 23:19:01 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA16687
for <[email protected]>; Tue, 14 Sep 1999 23:18:59 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA07267;
Tue, 14 Sep 1999 23:18:58 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA19359;
Tue, 14 Sep 1999 23:18:10 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA34086
for <[email protected]>; Tue, 14 Sep 1999 23:14:11 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA25378
for <[email protected]>; Tue, 14 Sep 1999 23:14:09 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id GAA12494; Wed, 15 Sep 1999 06:20:52 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 14 Sep 99 23:20 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id XAA18209;
Tue, 14 Sep 1999 23:08:14 -0700
Message-Id: <Pine.LNX.4.05.9909142306070.16930-100000@ArmispianSystems.Rossland.bc.ca>
Date: Tue, 14 Sep 1999 23:08:11 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 15 Sep 1999, Mike Miller wrote:

> On Wed, 15 Sep 1999, Osman%Pine wrote:
>
> > If you select a number of messages using ";" and want to "Narrow" your
> > selection it unselects the previously selected ones and you end-up with
> > the ones which comply with your creterium you used to "Narrow".
> >
> > This is realy broken!
> >
> > The "Broaden" functionality works correct though...
>
> This is not true for me. Both narrow and broaden work fine on Solaris
> using the precompiled pine. What OS are you using?

Both work fine for me. Work as expected. Mine is the binarry
that I compiled myself, but I didn't do much but ``ussual'' things. It
appears that he is using Linux, as I am... Wierd it wouldn't work as
expected...

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 23:45:13 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA16942
for <[email protected]>; Tue, 14 Sep 1999 23:45:12 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA03967;
Tue, 14 Sep 1999 23:45:10 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA02675;
Tue, 14 Sep 1999 23:44:21 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA22460
for <[email protected]>; Tue, 14 Sep 1999 23:41:10 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA07238
for <[email protected]>; Tue, 14 Sep 1999 23:41:09 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id IAA28664;
Wed, 15 Sep 1999 08:41:06 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 08:41:06 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 15 Sep 1999, Mike Miller wrote:

> On Wed, 15 Sep 1999, Osman%Pine wrote:
>
> > If you select a number of messages using ";" and want to "Narrow" your
> > selection it unselects the previously selected ones and you end-up with
> > the ones which comply with your creterium you used to "Narrow".
> >
> > This is realy broken!
> >
> > The "Broaden" functionality works correct though...
>
> This is not true for me. Both narrow and broaden work fine on Solaris
> using the precompiled pine. What OS are you using?

I'm using linux RedHat 6+ with pine 4.10 as distributed in
"pine-4.10-2.i386.rpm" that's the version which comes on the regular CD.

TTYL.
--
I believe the technical term is "Oops!"

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Sep 1999 23:51:57 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA17026
for <[email protected]>; Tue, 14 Sep 1999 23:51:56 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA04054;
Tue, 14 Sep 1999 23:51:54 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id XAA02810;
Tue, 14 Sep 1999 23:51:17 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id XAA22364
for <[email protected]>; Tue, 14 Sep 1999 23:48:25 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA14983
for <[email protected]>; Tue, 14 Sep 1999 23:48:24 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id IAA31125
for <[email protected]>; Wed, 15 Sep 1999 08:48:23 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 08:48:22 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [Q] About spell checking.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

How do I have to setup pine to use ISPELL for spell checking?
I know where to set it up but not what to put there.

I want to be able to see some suggestions to spelling errors...
The default is just giving the option to correct a wrongly spelled word
but no suggestions as what it should be accoarding to installed
dictionaries.

I'm using Linux, RedHat 6+ and ispell-3.1.20-20.i386.rpm
Any hints?

Thx.
--
Reboot America.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 07:38:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA29326
for <[email protected]>; Wed, 15 Sep 1999 07:38:09 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA12770;
Wed, 15 Sep 1999 07:38:07 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id HAA15033;
Wed, 15 Sep 1999 07:36:41 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id HAA14356
for <[email protected]>; Wed, 15 Sep 1999 07:33:32 -0700
Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA00183
for <[email protected]>; Wed, 15 Sep 1999 07:33:28 -0700
Received: from luomat.peak.org [207.141.129.74] by 1stpc.org with ESMTP
(SMTPD32-4.04) id A0614FB802A2; Wed, 15 Sep 1999 10:42:41 EST
Received: by luomat.peak.org (8.9.3/8.9.0) id KAA12405
for [email protected]; Wed, 15 Sep 1999 10:33:16 -0400 (EDT)
Message-Id: <199909151433.KAA12405@ocalhost>
Date: Wed, 15 Sep 1999 10:33:13 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Timothy J Luoma <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: perl, grepmail
In-Reply-To: <[email protected]>
References: <[email protected]>
Content-Type: text/plain
MIME-Version: 1.0
X-To: Pine Discussion Forum <[email protected]>
X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff
X-Organization: http://www.peak.org/~luomat/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Replying to message of Wed, 15 Sep 1999 04:29:13 +0200 (CEST)
from Osman%Pine <[email protected]> regarding ``Re: perl,
grepmail''

> I don't know grepmail... But if they would impliment such
> behaviour they ought to do it in an extensible way like:
>
> [x] enable external tasks
>
> And the system administrator should be the only one who can
> configure them in "pine.conf.fixed". Otherwise it would introduce
> security problems.

Most of the sysadmins I've dealt with wouldn't even think of allowing
something like that because of the potential someone would hold
them liable for it..... OR they wouldn't bother because they hadn't
had a chance to check it out.

I'd suggest putting a pine.conf.fixed entry that would disallow
them in general (aka "Allow Changing From") if they so desired.
But don't punish users who have sysadmins who can't be bothered
with little things that make users lives easier.

TjL

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 11:28:25 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02503
for <[email protected]>; Wed, 15 Sep 1999 11:28:23 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA23884;
Wed, 15 Sep 1999 11:28:22 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA18343;
Wed, 15 Sep 1999 11:25:36 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA52060
for <[email protected]>; Wed, 15 Sep 1999 11:10:22 -0700
Received: from mysql.respublica.de (dns1.respublica.de [195.30.94.27])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA10891
for <[email protected]>; Wed, 15 Sep 1999 11:10:20 -0700
Received: from trajan.respublica.de ([email protected] [195.30.94.38])
by mysql.respublica.de (8.9.3/8.9.3) with ESMTP id UAA17168
for <[email protected]>; Wed, 15 Sep 1999 20:10:15 +0200
Received: (from gerhard@localhost) by gerhard.zuhause.de (8.7.5/8.7.3) id UAA01223 for [email protected]; Wed, 15 Sep 1999 20:09:27 +0200
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 20:09:27 +0200 (CEST)
Reply-To: Gerhard Siegesmund <[email protected]>
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Gerhard Siegesmund <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG?] Mimetype handling
In-Reply-To: <[email protected]>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
X-Sender: [email protected]
X-Priority: 3 (Normal)
X-Face: :}&U68.!&-C;EYu6n.hDY$/mp~$#y#K>r?&gDm!=MG"zt+MwQK@on3f=\Cl4}NhEcXKEG?L
$PS<v-YYSS9sgv%v"I$K!V*u5c3nfy8Uh)f?D[:h}6j82/19y2^mm*^Y-.`E{NsY~9Vcc0Gj@=;f|Z
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello

I don't know if this is a bug, or whether it is new. I am using pine 4.10
and there seems there are { and } missing in the function
mt_srch_mime_type ()
in the file mailcap.c.
----------------
..
if(!rv)
{ missing here?
#ifdef _WINDOWS
..
#endif
} missing here?
return(rv);
..
----------------
The problem was, that pine told me correctly the mime-type of *.wav-Files
to be sound/x-wav, but nevertheless sent them as application/octet. I took
some looks into the source-code. It is rather funny. The first time the
function is called it works without problems, so pine tells me correctly
sound/x-wav. But the second time get_mime_time_by_extension is called, it
doesn't find the right mime-type. Maybe someone who nows the code could
take a look at it. After inserting the brackets (which really seem to lack
at that position) everything seems to work alright. I am using here Linux
2.2.9 and egcs 1.1.3 (gcc --version tells me egcs-2.91.66).

---
cu
--== Jerri ==--
Homepage: http://www.cip.physik.uni-muenchen.de/~siegesm/
finger [email protected] to get PGP Public Key
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 12:08:39 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA03730
for <[email protected]>; Wed, 15 Sep 1999 12:08:38 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21567;
Wed, 15 Sep 1999 12:08:36 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA20252;
Wed, 15 Sep 1999 12:07:24 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA08066
for <[email protected]>; Wed, 15 Sep 1999 12:03:58 -0700
Received: from viruswall.tc.fluke.com (viruswall.tc.fluke.com [206.138.179.196])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA30788
for <[email protected]>; Wed, 15 Sep 1999 12:03:57 -0700
Received: from 129.196.184.7 by viruswall.tc.fluke.com (InterScan E-Mail VirusWall NT); Wed, 15 Sep 1999 11:35:37 -0800
Received: from dd.tc.fluke.com ([email protected] [129.196.148.100])
by mailhub.tc.fluke.com (8.9.3/8.9.1) with ESMTP id LAA16803;
Wed, 15 Sep 1999 11:32:41 -0700 (PDT)
Received: from localhost (dcd@localhost [127.0.0.1]) by dd.tc.fluke.com (8.8.5/8.6.12) with ESMTP id LAA02989; Wed, 15 Sep 1999 11:32:42 -0700
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 11:32:42 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: David Dyck <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG?] Mimetype handling
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Gerhard Siegesmund <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

If you are using Linux, then _WINDOWS should not be defined.
(Compilers that target Microsoft Windows applications define _WINDOWS)
If _WINDOWS is not defined, then adding braces should
not change the functionality of the program.

What else changed?

On Wed, 15 Sep 1999, Gerhard Siegesmund wrote:

> I don't know if this is a bug, or whether it is new. I am using pine 4.10
> and there seems there are { and } missing in the function
> mt_srch_mime_type ()
> in the file mailcap.c.
> ----------------
> ...
> if(!rv)
> { missing here?
> #ifdef _WINDOWS
> ...
> #endif
> } missing here?
> return(rv);
> ...
> ----------------
> I am using here Linux
> 2.2.9 and egcs 1.1.3 (gcc --version tells me egcs-2.91.66).

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 12:22:21 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA03951
for <[email protected]>; Wed, 15 Sep 1999 12:22:20 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21918;
Wed, 15 Sep 1999 12:22:19 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA07848;
Wed, 15 Sep 1999 12:21:00 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA66764
for <[email protected]>; Wed, 15 Sep 1999 12:17:10 -0700
Received: from rook.ecs.soton.ac.uk (rook.ecs.soton.ac.uk [152.78.71.4])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA06123
for <[email protected]>; Wed, 15 Sep 1999 12:17:09 -0700
Received: from stork.ecs.soton.ac.uk (stork [152.78.71.1])
by rook.ecs.soton.ac.uk (8.9.1a/8.9.1) with ESMTP id UAA25915;
Wed, 15 Sep 1999 20:17:07 +0100 (BST)
Received: from servalan.ecs.soton.ac.uk (IDENT:rwb197@servalan [152.78.71.18])
by stork.ecs.soton.ac.uk (8.9.3/8.9.3) with SMTP id UAA22168;
Wed, 15 Sep 1999 20:17:07 +0100 (BST)
Message-Id: <Pine.LNX.3.96.990915195448.28423B-100000@servalan.ecs.soton.ac.uk>
Date: Wed, 15 Sep 1999 19:57:47 +0100 (GMT)
Reply-To: Robert Brady <[email protected]>
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Robert Brady <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG?] Mimetype handling
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Dyck <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 15 Sep 1999, David Dyck wrote:

> If you are using Linux, then _WINDOWS should not be defined.
> (Compilers that target Microsoft Windows applications define _WINDOWS)
> If _WINDOWS is not defined, then adding braces should
> not change the functionality of the program.

Please examine the example code very carefully. This is a tricky area.
The problem is that the code is of the form :

if (a)
#if SOMETHING
statement;
#endif
return foo;

Therefore, if SOMETHING is not defined,

if (a)
return foo;

will happen. This does not seem to be the desired effect. Either adding
the braces, or changing it to be

#if SOMETHING
if (a)
statement;
#endif

will work.

--
Robert

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 12:54:22 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04353
for <[email protected]>; Wed, 15 Sep 1999 12:54:21 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA22752;
Wed, 15 Sep 1999 12:54:19 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA09383;
Wed, 15 Sep 1999 12:52:48 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA61746
for <[email protected]>; Wed, 15 Sep 1999 12:49:00 -0700
Received: from viruswall.tc.fluke.com (viruswall.tc.fluke.com [206.138.179.196])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA16368
for <[email protected]>; Wed, 15 Sep 1999 12:49:00 -0700
Received: from 129.196.184.7 by viruswall.tc.fluke.com (InterScan E-Mail VirusWall NT); Wed, 15 Sep 1999 12:38:31 -0800
Received: from dd.tc.fluke.com ([email protected] [129.196.148.100])
by mailhub.tc.fluke.com (8.9.3/8.9.1) with ESMTP id MAA18551;
Wed, 15 Sep 1999 12:35:35 -0700 (PDT)
Received: from localhost (dcd@localhost [127.0.0.1]) by dd.tc.fluke.com (8.8.5/8.6.12) with ESMTP id MAA03145; Wed, 15 Sep 1999 12:35:36 -0700
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 12:35:36 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: David Dyck <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG?] Mimetype handling
In-Reply-To: <Pine.LNX.3.96.990915195448.28423B-100000@servalan.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Robert Brady <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

oops,
I misunderstood what you said

If the makefile had set enabled compiler warnings
with -W

the following warning would have been issued:
mailcap.c: In function `mt_srch_mime_type':
mailcap.c:1131: warning: this function may return with or without a value

Even more warnings are spit out by gcc if -Wall is added

I thought everyone used -W...

On Wed, 15 Sep 1999, Robert Brady wrote:

> On Wed, 15 Sep 1999, David Dyck wrote:
>
> > If you are using Linux, then _WINDOWS should not be defined.
> > (Compilers that target Microsoft Windows applications define _WINDOWS)
> > If _WINDOWS is not defined, then adding braces should
> > not change the functionality of the program.
>
> Please examine the example code very carefully. This is a tricky area.
> The problem is that the code is of the form :
>
> if (a)
> #if SOMETHING
> statement;
> #endif
> return foo;
>
> Therefore, if SOMETHING is not defined,
>
> if (a)
> return foo;
>
> will happen. This does not seem to be the desired effect. Either adding
> the braces, or changing it to be
>
> #if SOMETHING
> if (a)
> statement;
> #endif
>
> will work.
>
> --
> Robert
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 13:20:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05116
for <[email protected]>; Wed, 15 Sep 1999 13:20:23 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA23618;
Wed, 15 Sep 1999 13:20:22 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA28626;
Wed, 15 Sep 1999 13:19:08 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA46110
for <[email protected]>; Wed, 15 Sep 1999 13:15:49 -0700
Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA14857
for <[email protected]>; Wed, 15 Sep 1999 13:15:48 -0700
Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP (
WorldSecure Server SMTP Relay(WSS) v3.6); Wed, 15 Sep 99 14:15:46 -0600
Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190])
by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id OAA16538 for
<[email protected]>; Wed, 15 Sep 1999 14:15:47 -0600 (MDT)
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 14:15:34 -0600
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Daniel Sands" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: "Pine Discussion Forum" <[email protected]>
X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c
X-WSS-ID: 1BC121F8139593-01-01
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I define "dead" as when the user's telnet connection is dropped, thus ending
the login session and freeing the PTY. It is of interest, though, that Pine
on my IP's machine will be killed by a dropped connection. This may be due to
my shell program sending it a HUP signal, though.

> Define "dead". If a PC powers off, the host can't tell if it's dead or if
> the user simply hasn't typed something for a while. Then, define "a
> while". Some systems kill idle processes, but only after several hours or
> days (or not at all); the user might want to get at their mail NOW, not in
> a few hours.
>
> Jim
>
> On Mon, 13 Sep 1999, Daniel Sands wrote:
>
> > >
> > > > Hardly. The user must be taught to kill zombie processes if need be.
> > >
> > > __IF___ that option is even available to them (there are menu-driven shell
> > > accounts which give access to PINE but not to commandline)
> > >
> > > Even if it is, I'm not sure why this behavior was changed, and why it is
> > > "better" when it is easy to see when it could become a problem.
> >
> > Why doesn't Pine detect when the TTY is dead and kill itself? Since it's
> > supposed to be an interactive mailer, it makes no sense to keep going when no
> > more input can be given.
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Sep 1999 13:48:30 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05525
for <[email protected]>; Wed, 15 Sep 1999 13:48:29 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA24406;
Wed, 15 Sep 1999 13:48:26 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA25178;
Wed, 15 Sep 1999 13:44:35 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA37626
for <[email protected]>; Wed, 15 Sep 1999 13:41:13 -0700
Received: from roper.uwyo.edu ([email protected] [129.72.10.8])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA13368
for <[email protected]>; Wed, 15 Sep 1999 13:41:12 -0700
Received: from asuwlink.uwyo.edu (asuwlink.uwyo.edu [129.72.60.2])
by ROPER.UWYO.EDU (PMDF V5.2-32 #33749)
with ESMTP id <[email protected]> for [email protected];
Wed, 15 Sep 1999 14:39:03 -0600 (MDT)
Received: from localhost (jimkirk@localhost) by asuwlink.uwyo.edu (8.8.8/8.8.7)
with ESMTP id OAA18294; Wed, 15 Sep 1999 14:39:02 -0600 (MDT)
Message-Id: <[email protected]>
Date: Wed, 15 Sep 1999 14:39:02 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Kirkpatrick <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and read-only folders
In-Reply-To: <[email protected]>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-To: Daniel Sands <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-warning: asuwlink.uwyo.edu: jimkirk owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

There are still different flavors of "dead". If you are dialed in and
drop, the modem sends a signal to that effect to whatever it's connected
to, and in many cases that propogates back to the server which then kills
the necessary processes (e.g. sends a SIGHUP to the shell).

However, if the client is a PC with an ethernet card, plugged in to the
campus network, and telnetted to the server, then things like a power
failure on the client end (or control-alt-del, or poke the reset button,
or ...) are not noticed on the server. The connection is not dropped
because nobody knows what's happened. Telnet does not include a
"heartbeat" to tell one end or the other that anything's wrong. And it's
this sort of situation that makes Pine 4.10's new behavior obnoxious
compared to that of 3.96.

Jim

On Wed, 15 Sep 1999, Daniel Sands wrote:

> I define "dead" as when the user's telnet connection is dropped, thus ending
> the login session and freeing the PTY. It is of interest, though, that Pine
> on my IP's machine will be killed by a dropped connection. This may be due to
> my shell program sending it a HUP signal, though.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 09:43:27 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA25603
for <[email protected]>; Thu, 16 Sep 1999 09:43:26 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA20074;
Thu, 16 Sep 1999 09:43:24 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA24115;
Thu, 16 Sep 1999 09:42:11 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA49314
for <[email protected]>; Thu, 16 Sep 1999 09:37:25 -0700
Received: from hawk.basinharbor.com (hawk.basinharbor.com [208.154.204.200])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA29755
for <[email protected]>; Thu, 16 Sep 1999 09:37:24 -0700
Received: from basinharbor.com ([208.154.204.213]) by hawk.basinharbor.com (AIX4.2/UCB 8.7/8.7) with ESMTP id MAA29094 for <[email protected].>; Thu, 16 Sep 1999 12:37:09 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 16 Sep 1999 12:39:06 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Brian Goodyear <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Sending delays
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

A number of years ago I was installing Pine on a RS/6000 running 4.2 and
came accross a same problem that I'm having today. Unfortunely I forgot
what the solution is.

After composing a message and sending (Ctrl-X) it will take up to 45
seconds for the mail to go through. Before, I think it had to do with
the nameserver or hostname.

Any help out there?

Brian Goodyear

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 10:04:30 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26165
for <[email protected]>; Thu, 16 Sep 1999 10:04:29 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20752;
Thu, 16 Sep 1999 10:04:26 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA03196;
Thu, 16 Sep 1999 10:02:55 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA40826
for <[email protected]>; Thu, 16 Sep 1999 09:58:43 -0700
Received: from physics.ucla.edu (physics.ucla.edu [128.97.23.13])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA30976
for <[email protected]>; Thu, 16 Sep 1999 09:58:39 -0700
Received: from yukawa.physics.ucla.edu (yukawa [128.97.22.100])
by physics.ucla.edu (8.9.3/8.9.3) with ESMTP id JAA20005
for <[email protected]>; Thu, 16 Sep 1999 09:56:41 -0700 (PDT)
Received: (from xu@localhost)
by yukawa.physics.ucla.edu (8.8.8+Sun/8.8.8) id JAA07747
for [email protected]; Thu, 16 Sep 1999 09:56:41 -0700 (PDT)
Message-Id: <[email protected]>
Date: Thu, 16 Sep 1999 09:56:41 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Lingyu Xu <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: remove
X-Sun-Charset: US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 10:21:34 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26467
for <[email protected]>; Thu, 16 Sep 1999 10:21:33 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA17251;
Thu, 16 Sep 1999 10:21:30 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA16269;
Thu, 16 Sep 1999 10:19:43 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA47026
for <[email protected]>; Thu, 16 Sep 1999 10:16:20 -0700
Received: from hal9k.org (PPP3-26.bom.vsnl.net.in [202.54.3.26])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26059
for <[email protected]>; Thu, 16 Sep 1999 10:16:14 -0700
Received: from localhost (satyap@localhost)
by hal9k.org (8.9.3/8.8.7) with ESMTP id WAA00748
for <[email protected]>; Thu, 16 Sep 1999 22:48:17 +0530
Message-Id: <[email protected]>
Date: Thu, 16 Sep 1999 22:48:17 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Sending delays
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: hal9k.org: satyap owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sep 16, 1999 at 12:39, Brian Goodyear wrote:

> After composing a message and sending (Ctrl-X) it will take up to 45
> seconds for the mail to go through. Before, I think it had to do with
> the nameserver or hostname.

Same problem here. I fiddled a lot with sendmail, finally fixed it. Will
send relevant part of sendmail.cf privately if you want, as I still don't
know how I fixed it. AFAICT, it's not a pine issue.

--
Satya.
http://satyaonline.cjb.net/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 15:13:50 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA00796
for <[email protected]>; Thu, 16 Sep 1999 15:13:49 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30375;
Thu, 16 Sep 1999 15:13:47 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA17176;
Thu, 16 Sep 1999 15:12:40 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA72380
for <[email protected]>; Thu, 16 Sep 1999 15:08:19 -0700
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA07410
for <[email protected]>; Thu, 16 Sep 1999 15:08:18 -0700
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id PAA07897;
Thu, 16 Sep 1999 15:08:17 -0700 (PDT)
Message-Id: <Pine.OSF.4.10.9909161505070.22504-100000@goedel3.math.washington.edu>
Date: Thu, 16 Sep 1999 15:08:17 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: perl, grepmail
In-Reply-To: <199909151433.KAA12405@ocalhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Timothy J Luoma <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Timothy J Luoma ([email protected]) wrote on Sep 15, 1999:

:) Replying to message of Wed, 15 Sep 1999 04:29:13 +0200 (CEST)
:) from Osman%Pine <[email protected]> regarding ``Re: perl,
:) grepmail''
:)
:) > I don't know grepmail... But if they would impliment such
:) > behaviour they ought to do it in an extensible way like:
:) >
:) > [x] enable external tasks
:) >
:) > And the system administrator should be the only one who can
:) > configure them in "pine.conf.fixed". Otherwise it would introduce
:) > security problems.
:)
:) Most of the sysadmins I've dealt with wouldn't even think of allowing
:) something like that because of the potential someone would hold
:) them liable for it..... OR they wouldn't bother because they hadn't
:) had a chance to check it out.

Actually pine can execute any external program that you want already, and
can imitate very closely what has already been suggested here. I don't see
why would anyone want to disable this behavior when it already has it and
no one has complained about it before.

Eduardo
http://www.math.washington.edu/~chappa/personal.html

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 16:36:20 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA02288
for <[email protected]>; Thu, 16 Sep 1999 16:36:19 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28232;
Thu, 16 Sep 1999 16:36:17 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA13500;
Thu, 16 Sep 1999 16:35:23 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA65076
for <[email protected]>; Thu, 16 Sep 1999 16:32:02 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA27266
for <[email protected]>; Thu, 16 Sep 1999 16:32:00 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28076
for <[email protected]>; Thu, 16 Sep 1999 16:31:59 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id SAA23917
for <[email protected]>; Thu, 16 Sep 1999 18:31:24 -0500 (CDT)
Message-Id: <[email protected]>
Date: Thu, 16 Sep 1999 18:31:24 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: perl, grepmail
In-Reply-To: <Pine.OSF.4.10.9909161505070.22504-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 16 Sep 1999, Eduardo Chappa L. wrote:

> Actually pine can execute any external program that you want already,
> and can imitate very closely what has already been suggested here. I
> don't see why would anyone want to disable this behavior when it
> already has it and no one has complained about it before.

Interesting. I'm not sure what you have in mind, there's much to pine
that I don't know but I tried the following experiment...

I was reading your message and I used the pipe command '|' then entered
the following command:

; chmod a+x ~/.chsrc

I suppose I could have entered any command that I had permission to
execute. Pine popped back saying that it had executed the command and
that there was no output. Sure enough, my .cshrc file had been affected:

-rwxr-xr-x 1 mbmiller staff 14355 Sep 7 19:00 .cshrc*

Are there other ways to execute commands from pine?

This should be of interest to people who are trying to constrain their
users to a pine shell, but maybe they have this under control already.

Regards,

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 16:45:05 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA02436
for <[email protected]>; Thu, 16 Sep 1999 16:45:04 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28522;
Thu, 16 Sep 1999 16:45:02 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA03943;
Thu, 16 Sep 1999 16:43:40 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA54440
for <[email protected]>; Thu, 16 Sep 1999 16:40:07 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA21486
for <[email protected]>; Thu, 16 Sep 1999 16:40:06 -0700
Received: from jupiter.cs.uml.edu ([email protected] [129.63.1.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28375
for <[email protected]>; Thu, 16 Sep 1999 16:40:05 -0700
Received: from localhost (svora@localhost [127.0.0.1])
by jupiter.cs.uml.edu (8.9.1a/8.9.1) with SMTP id TAA00903
for <[email protected]>; Thu, 16 Sep 1999 19:40:04 -0400 (EDT)
Message-Id: <[email protected]>
Date: Thu, 16 Sep 1999 19:40:04 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Sachin Vora <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: help me !!!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

hi
can any one help me with this problem.....
I had pine as my email application...i tried to read the mail using emacs
..emacs created a RMAIL folder in my home directory but my inbox in pine
now shows 0 messages...i want the inbox to show the messages it held...the
messages are in RMAIL folder in my home directory..can i revert the RMAIL
folder back so that my original inbox folder shows its contents....help in
this regard will be appreciated...thanks

sachin vora
please reply at [email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Sep 1999 21:02:03 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA05130
for <[email protected]>; Thu, 16 Sep 1999 21:02:02 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04482;
Thu, 16 Sep 1999 21:02:00 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id VAA27266;
Thu, 16 Sep 1999 21:00:59 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA11728
for <[email protected]>; Thu, 16 Sep 1999 20:58:19 -0700
Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id UAA20121
for <[email protected]>; Thu, 16 Sep 1999 20:58:18 -0700
Received: from luomat.peak.org [207.141.129.112] by 1stpc.org with ESMTP
(SMTPD32-4.04) id AE934AE80210; Fri, 17 Sep 1999 00:07:47 EST
Received: by luomat.peak.org (8.9.3/8.9.0) id XAA19116
for [email protected]; Thu, 16 Sep 1999 23:58:14 -0400 (EDT)
Message-Id: <199909170358.XAA19116@ocalhost>
Date: Thu, 16 Sep 1999 23:58:12 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Timothy J Luoma <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: perl, grepmail
In-Reply-To: <[email protected]>
References: <[email protected]>
Content-Type: text/plain
MIME-Version: 1.0
X-To: Pine Discussion Forum <[email protected]>
X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff
X-Organization: http://www.peak.org/~luomat/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Replying to message of Thu, 16 Sep 1999 18:31:24 -0500 (CDT)
from Mike Miller <[email protected]> regarding
``Re: perl, grepmail''

> This should be of interest to people who are trying to constrain
> their users to a pine shell, but maybe they have this under
> control already.

I believe you can disable the 'pipe command' using a pine.conf.fixed file,
but I'm not 100% sure

TjL

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 17 Sep 1999 07:09:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA15075
for <[email protected]>; Fri, 17 Sep 1999 07:09:23 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA14158;
Fri, 17 Sep 1999 07:09:21 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA04987;
Fri, 17 Sep 1999 07:08:14 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA63974
for <[email protected]>; Fri, 17 Sep 1999 07:02:27 -0700
Received: from rrzs2.rz.uni-regensburg.de (rrzs2.rz.uni-regensburg.de [132.199.1.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA13549
for <[email protected]>; Fri, 17 Sep 1999 07:02:24 -0700
Received: from localhost.localdomain (rrzras2-96.rz.uni-regensburg.de [132.199.209.96])
by rrzs2.rz.uni-regensburg.de (8.8.8/8.8.8) with ESMTP id QAA23561
for <[email protected]>; Fri, 17 Sep 1999 16:02:16 +0200 (MET DST)
Received: from localhost (claus@localhost)
by localhost.localdomain (8.9.3/8.9.3) with ESMTP id PAA01037
for <[email protected]>; Fri, 17 Sep 1999 15:36:12 +0200
Message-Id: <[email protected]>
Date: Fri, 17 Sep 1999 15:36:12 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Claus Atzenbeck <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: printing problem
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: pine-info <[email protected]>
X-Authentication-Warning: localhost.localdomain: claus owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I usually print with "lpr -Phpps". I have put this to pine's printer
setup, but I get this error message when trying to print:

sh: option `-c' requires an argument

Strange... I don't have any '-c' option defined at all.
What is wrong?

Regards,
Claus.

--
Claus Atzenbeck, stud. phil.
seminar papers: http://homepages.uni-regensburg.de/~atc16247/
[This mail was created on a 100% Micro$oft-free computer.]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 17 Sep 1999 08:18:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA12395
for <[email protected]>; Fri, 17 Sep 1999 08:18:09 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA15648;
Fri, 17 Sep 1999 08:18:07 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA03840;
Fri, 17 Sep 1999 08:14:27 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA19192
for <[email protected]>; Fri, 17 Sep 1999 08:11:06 -0700
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA20720
for <[email protected]>; Fri, 17 Sep 1999 08:11:06 -0700
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id IAA19505;
Fri, 17 Sep 1999 08:11:04 -0700 (PDT)
Message-Id: <Pine.OSF.4.10.9909170752350.5932-100000@goedel3.math.washington.edu>
Date: Fri, 17 Sep 1999 08:11:04 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: perl, grepmail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello,

Ok, so here is what I was thinking of, I do not know if this could be
disabled by the sys-admin, I guess so, but since pine has had this feature
for so long and nobody has complained, I guess it must not bother
anyone...

You can use any folder that you like first, but to make it more
believable, say you create a folder called "external". What external is
going to contain are going to be 1 line messages, which you can save there
by either sending them to yourself or postponing them and saving them
there or using your forms letter folder (if you have any).

What the one line message is going to say is some kind of password, lets
say the one line says "GREPMAIL", because you want to execute grepmail (I
would use something more complicated, but I use this word just to fix
ideas). You can write in the subject of the message the program that you
want to activate.

Now go to your configuration file and where it says "display-filters"
write

_LEADING(GREPMAIL)_ /full/path/to/grepmail _TMPFILE_

NOTE: I have never used grepmail, nor intend to. I do not know if grepmail
receives parameters or is interactive with menus and so on. If it receives
parameters then I would change the line above to a path to a script which
executes grepmail and would add the parameters in the above line, this is
just a model.

The whole point is to ignore the parameter _TMPFILE_, I leave to you to
investigate why that is there.

Something to look into is that if you receive a message with the leading
word GREPMAIL, then the filter will be activated, so you should use an
unlikely word or sentence.

I do not intend to use this model for executing external programs, I
have no use for them now, but since people have been asking about them I
thought it would be useful for them to know.

Have a nice day,

Eduardo
http://www.math.washington.edu/~chappa/pine

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 18 Sep 1999 12:49:25 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA12360
for <[email protected]>; Sat, 18 Sep 1999 12:49:24 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA10704;
Sat, 18 Sep 1999 12:49:22 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA15794;
Sat, 18 Sep 1999 12:48:35 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA66794
for <[email protected]>; Sat, 18 Sep 1999 12:43:52 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA22187
for <[email protected]>; Sat, 18 Sep 1999 12:43:52 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA14855
for <[email protected]>; Sat, 18 Sep 1999 12:43:52 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id OAA04504
for <[email protected]>; Sat, 18 Sep 1999 14:43:15 -0500 (CDT)
Message-Id: <[email protected]>
Date: Sat, 18 Sep 1999 14:43:15 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: scripts for working with .addressbook
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Unix users:

I wrote a couple of scripts (tcsh for Solaris, but you can easily modify
them for your system) that have been very helpful to me and I want to
share them with the rest of you. The two scripts are appended at the end
of this message. I call the first one 'person' and I call the second one
'comment'. I put them in our system in /usr/local/bin These scripts are
used to grab records out of the ~/.addressbook database. For example:

# person Johnson

ericjohn Johnson, Eric [email protected]
from NIDA. Did item heritability analyses.

johnsonf Johnson, Fred [email protected]

johnsong Johnson, Greg [email protected]
IATS guy, does Solaris, Unix, (573) 882-5008

The command "person Johnson" found three records containing the string
'Johnson' in either the nickname, fullname or address field and it wrote
the lines showing me the full record on each person including the comments
field.

Another example:

# comment 1485

kristiej Jackson, Kristina [email protected]
office: (573) 884-1485, home: (573) 817-2940

The command "comment 1485" searched for comments containing '1485' and
returned all the fields in that record.

These commands almost always work for me, but they are not perfect. Not
all records are parsed by the rules I implicitly assume in these
simple-minded scripts.

It would be fantastic if someone could do it right! I would love to have
a perl script, or whatever, that would deal with the exact structure of
~/.addressbook and always give me what I want. It is probably a very easy
perl programming job, but I'm not competent enough to pull it off.

Regards,

Mike

Michael B. Miller, M.S., Ph.D., M.P.E.
Department of Psychology
University of Missouri--Columbia
Columbia, MO 65211
http://taxa.psyc.missouri.edu/~mbmiller/

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

The 'person' script.
To grab records with some string in another (non-comment) field:

#!/usr/local/bin/tcsh -f
foreach N ( `egrep -n "$1" ~/.addressbook | egrep -v ': ' | awk -F: '{print $1}'` )
tail +$N ~/.addressbook | head -1 | fmt -w 75
tail +$N ~/.addressbook | tail +2 | head -1 | egrep '^ ' | fmt -w 75
echo ""
end

The 'comment' script.
To grab records with some string in the comment field:

#!/usr/local/bin/tcsh -f
foreach N ( `egrep -n "$1" ~/.addressbook | egrep ': ' | awk -F: '{print $1 - 1}'` )
tail +$N ~/.addressbook | head -2 | fmt -w 75
echo ""
end

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 07:08:17 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA12494
for <[email protected]>; Mon, 20 Sep 1999 07:08:16 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA17252;
Mon, 20 Sep 1999 07:08:14 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA19632;
Mon, 20 Sep 1999 07:07:09 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA42194
for <[email protected]>; Mon, 20 Sep 1999 07:01:55 -0700
Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.74])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA29722
for <[email protected]>; Mon, 20 Sep 1999 07:01:54 -0700
Received: from preinstalledcom (user-38ldi12.dialup.mindspring.com [209.86.200.34])
by smtp6.mindspring.com (8.8.5/8.8.5) with SMTP id KAA05746
for <[email protected]>; Mon, 20 Sep 1999 10:02:07 -0400 (EDT)
Message-Id: <004a01bf0370$38dd2220$22c856d1@preinstalledcom>
Date: Mon, 20 Sep 1999 06:58:29 -0700
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Lists" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: How again to unlock the "4.10 locked by another process"
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Once again please, when you are disconnected and you re-connected, and pine
says it is "read-only" cause it is in use by "another process", how do you
fix it?

Bryan

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 07:56:36 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA13041
for <[email protected]>; Mon, 20 Sep 1999 07:56:35 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA13881;
Mon, 20 Sep 1999 07:56:33 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA03933;
Mon, 20 Sep 1999 07:50:34 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA31892
for <[email protected]>; Mon, 20 Sep 1999 07:46:31 -0700
Received: from locutus (locutus.plaidranch.org [209.151.69.20])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA23618
for <[email protected]>; Mon, 20 Sep 1999 07:46:27 -0700
Received: from localhost (localhost [127.0.0.1])
by locutus (8.9.3/8.9.3) with ESMTP id IAA15595;
Mon, 20 Sep 1999 08:55:54 -0600
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 08:55:54 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Ian Hall-Beyer <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: How again to unlock the "4.10 locked by another process"
In-Reply-To: <004a01bf0370$38dd2220$22c856d1@preinstalledcom>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Lists <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Sep 1999, Lists wrote:

> Once again please, when you are disconnected and you re-connected, and pine
> says it is "read-only" cause it is in use by "another process", how do you
> fix it?

Kill the other process.

--
<cosmo> wow, this is kinda nifty. the win98 protocol stack is
like a chinese finger puzzle, twist and turn in the right places,
and it pops right off --Seen on EFNet IRC

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 09:18:34 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA15052
for <[email protected]>; Mon, 20 Sep 1999 09:18:33 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA16248;
Mon, 20 Sep 1999 09:18:31 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA24337;
Mon, 20 Sep 1999 09:15:44 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA47096
for <[email protected]>; Mon, 20 Sep 1999 09:11:43 -0700
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA03448
for <[email protected]>; Mon, 20 Sep 1999 09:11:42 -0700
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id MAA11080
for <[email protected]>; Mon, 20 Sep 1999 12:11:41 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 12:11:40 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Well, this isn't a bug though more of a feture request:

Is it possible, in the 'Narrow' function, to allow selection of 'NOT'
things? I want to be able to select messages from a mailing list, and
then pick the ones that DON'T have 'router' in the subject. This would be
a REALLY, TRULY, useful feature! If this example doesn't convince you,
see the more detailed one below.

To explicate, what I mean is, if I have a group of messages selected
'From' some mailing list, and I want to get the messages that were not
'Cc:'ed to another mailing list, the only thing I could do at that point
would be to select messages that _were_ cc:'ed to that mailing list, and I
lose the whole point of the exercise; i.e. the messages that I want get
unselected and tossed back into the general pool of thousands of
messages... Now I could go the roundabout way and select all the messages
that I don't want, and then do a select flip, but unfortunately, sometimes
the interesections of the sets overlap, and I'm still screwed...

*sigh* This would be so much easier with Venn diagrams, but they're not
easy enough to do in ASCII to be worth it. Does anyone else see what I'm
saying and the usefulness of being able to narrow to messages that don't
match a certain criteria in your selected set? Please say yes! :)

BINO

P.S. Osman, my 'narrow' works as advertised too. Solaris V, on an
Ultra-60 with Pine 4.10...

P.P.S. Btw, just to be clear, are you saying that it _completely_
unselects the previously selected set, and then selects messages that
would not have matched the previous select criteria when you do the second
Narrow selection (i.e. using the whole index, not your smaller, selected
set)?! That would be indeed be *very* weird...

On Wed, 15 Sep 1999, Osman%Pine wrote:

> Hi,
>
> If you select a number of messages using ";" and want to "Narrow" your
> selection it unselects the previously selected ones and you end-up with
> the ones which comply with your creterium you used to "Narrow".
>
> This is realy broken!
> The "Broaden" functionality works correct though...
>
> TTYL.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 09:24:15 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA15184
for <[email protected]>; Mon, 20 Sep 1999 09:24:14 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA16434;
Mon, 20 Sep 1999 09:24:12 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA07734;
Mon, 20 Sep 1999 09:21:36 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA18730
for <[email protected]>; Mon, 20 Sep 1999 09:17:57 -0700
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA11059
for <[email protected]>; Mon, 20 Sep 1999 09:17:56 -0700
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id MAA16273
for <[email protected]>; Mon, 20 Sep 1999 12:17:55 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 12:17:53 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] Minor bug?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I thought someone had reported this before, but I couldn't find it, so I'm
just mentioning it now just in case:

When you hit 'U' in Pine, whether in message view or index view, it says

[Deletion mark removed, message won't be deleted]

whether or not the message is deleted. Not an earth-shaking problem, but
it's still a bug, as that's not the correct behavior. It's also an
annoying one, as I was sure I would NOT have deleted that message, started
wondering what other messages I might have accidentally deleted, and went
to check to make sure that I hadn't done so...this was especially
worrisome since I've removed the confirm on my expunge!

So, if this could be fixed in the next release, that would be great.
Thanks!

BINO

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 10:05:04 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16203
for <[email protected]>; Mon, 20 Sep 1999 10:05:03 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA17687;
Mon, 20 Sep 1999 10:05:01 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA09567;
Mon, 20 Sep 1999 10:02:55 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA48972
for <[email protected]>; Mon, 20 Sep 1999 09:59:19 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA11323
for <[email protected]>; Mon, 20 Sep 1999 09:59:19 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id LAA03507
for <[email protected]>; Mon, 20 Sep 1999 11:58:39 -0500 (CDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 11:58:39 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Sep 1999, Bino Gopal wrote:

> Well, this isn't a bug though more of a feture request:
>
> Is it possible, in the 'Narrow' function, to allow selection of 'NOT'
> things? I want to be able to select messages from a mailing list, and
> then pick the ones that DON'T have 'router' in the subject. This
> would be a REALLY, TRULY, useful feature! If this example doesn't
> convince you, see the more detailed one below.

Pine actually has a minimal sort of NOT facility. You can search for all
messages in the folder containing 'router' in the subject, then use ";f"
to 'flip' from what you've selected to what you have not selected. Thus,
the ";f" will give you all messages that do NOT contain 'router' in the
subject.

That said, I agree fully. I'd like to be able to do other things like
limit a search to the body of the message, etc. Pine is great and I
really love it. That's why I ask for more--I want to do everything with
Pine.

Mike

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 10:43:11 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA17521
for <[email protected]>; Mon, 20 Sep 1999 10:43:09 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA23023;
Mon, 20 Sep 1999 10:43:07 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA10973;
Mon, 20 Sep 1999 10:41:41 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA61264
for <[email protected]>; Mon, 20 Sep 1999 10:35:14 -0700
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26244
for <[email protected]>; Mon, 20 Sep 1999 10:35:13 -0700
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA06885;
Mon, 20 Sep 1999 13:34:51 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 13:34:50 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Sep 1999, Mike Miller wrote:

> On Mon, 20 Sep 1999, Bino Gopal wrote:
>
> > Well, this isn't a bug though more of a feture request:
> >
> > Is it possible, in the 'Narrow' function, to allow selection of 'NOT'
> > things? I want to be able to select messages from a mailing list, and
> > then pick the ones that DON'T have 'router' in the subject. This
> > would be a REALLY, TRULY, useful feature! If this example doesn't
> > convince you, see the more detailed one below.
>
> Pine actually has a minimal sort of NOT facility. You can search for all
> messages in the folder containing 'router' in the subject, then use ";f"
> to 'flip' from what you've selected to what you have not selected. Thus,
> the ";f" will give you all messages that do NOT contain 'router' in the
> subject.
>
> That said, I agree fully. I'd like to be able to do other things like
> limit a search to the body of the message, etc. Pine is great and I
> really love it. That's why I ask for more--I want to do everything with
> Pine.
>
> Mike

Yep, know all about the flip; it's saved my life on many an occasion, but
unfortunately, with multiple intersecting sets, it just doesn't cut the
mustard (if you're one or two levels down). What if you need to select
messages from a certain list, then find the ones that don't have router in
them?--then if you flip, and you get all the messages that aren't from
that list too, etc.

And there is a NOT--you can select NOT <status>, but not NOT
<text>...didn't realize that there was no NOT <text>--would it be that
hard to hard? I mean, how about the inverse of Narrow, something like
'Wean', where you give it a criteria, and for messages that match that
criteria in a selected set, it tosses out those messages, instead of
keeping them as Narrow does? You know, it should really be called 'Narrow
To' if you do that...

And I have to agree with your agreeing with me Mike--I love Pine too--I
just want it to do more! *grin*

Btw, in case it hasn't been said recently, BIG THANKS to the Pine team for
all the hard work and effort they put into a great program! You guys have
done a great job; it's just that some of us out here want to eat our cake
too! ;) Keep up the good work!

BINO

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 10:47:15 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA17678
for <[email protected]>; Mon, 20 Sep 1999 10:47:13 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA19274;
Mon, 20 Sep 1999 10:47:11 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA11227;
Mon, 20 Sep 1999 10:45:47 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA31784
for <[email protected]>; Mon, 20 Sep 1999 10:42:04 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25469
for <[email protected]>; Mon, 20 Sep 1999 10:42:03 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id MAA06181
for <[email protected]>; Mon, 20 Sep 1999 12:41:24 -0500 (CDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 12:41:24 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Sep 1999, Bino Gopal wrote:

> Yep, know all about the flip; it's saved my life on many an occasion,
> but unfortunately, with multiple intersecting sets, it just doesn't
> cut the mustard (if you're one or two levels down). What if you need
> to select messages from a certain list, then find the ones that don't
> have router in them?--then if you flip, and you get all the messages
> that aren't from that list too, etc.

Believe me, I agree with you. But there is a way to deal with it--not
pretty, but it works. After you do the flip, do Apply, Save and save to a
new folder name. Then go to that folder and do the next select operation.

> And there is a NOT--you can select NOT <status>, but not NOT
> <text>...didn't realize that there was no NOT <text>--would it be that
> hard to hard?

Very good point. I think we need this feature.

> And I have to agree with your agreeing with me Mike--I love Pine
> too--I just want it to do more! *grin*

I guess we're all together on this one. The pine development team would
not exist if they didn't want to make Pine better!

Mike

--
Michael B. Miller, M.S., Ph.D., M.P.E.
Department of Psychology
210 McAlester Hall
University of Missouri--Columbia
Columbia, MO 65211
Phone: (573) 882-5671
Fax: (573) 882-7710
e-mail: [email protected]
web: http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 12:49:25 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21625
for <[email protected]>; Mon, 20 Sep 1999 12:49:24 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA02848;
Mon, 20 Sep 1999 12:49:22 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA27396;
Mon, 20 Sep 1999 12:47:04 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA62632
for <[email protected]>; Mon, 20 Sep 1999 12:43:24 -0700
Received: from franklin.wrl.org (IDENT:[email protected] [209.96.177.100])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA06363
for <[email protected]>; Mon, 20 Sep 1999 12:43:23 -0700
Received: from localhost (jpayne@localhost)
by franklin.wrl.org (8.8.7/8.8.5) with ESMTP id PAA00770
for <[email protected]>; Mon, 20 Sep 1999 15:43:21 -0400
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 15:43:21 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jennifer Payne <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: IN BOX folders?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi everyone.
I'm wondering if there's a way to specify where emails are delivered into
Pine. I would like to create folders within the IN BOX so that emails
with certain subject headings will go to their specified folders. Is this
possible?

Thanks.
Jenny

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 14:42:57 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA18796
for <[email protected]>; Mon, 20 Sep 1999 14:42:55 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA25857;
Mon, 20 Sep 1999 14:42:54 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA08345;
Mon, 20 Sep 1999 14:41:19 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA66648
for <[email protected]>; Mon, 20 Sep 1999 14:36:27 -0700
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA30295
for <[email protected]>; Mon, 20 Sep 1999 14:36:27 -0700
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA26795;
Mon, 20 Sep 1999 17:36:18 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 17:36:16 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

ARGH! I didn't even want to _mention_ that possibility! *shudder* The
thought crossed my mind, and it was promptly deleted, as do you have any
idea how long that process would take on a folder of 10,000 messages?!
And what happens when you have a select two or three levels down? No
thank you!--'not pretty' is a bit of an understatement, no? *grin*

BINO

On Mon, 20 Sep 1999, Mike Miller wrote:

> On Mon, 20 Sep 1999, Bino Gopal wrote:
>
> > Yep, know all about the flip; it's saved my life on many an occasion,
> > but unfortunately, with multiple intersecting sets, it just doesn't
> > cut the mustard (if you're one or two levels down). What if you need
> > to select messages from a certain list, then find the ones that don't
> > have router in them?--then if you flip, and you get all the messages
> > that aren't from that list too, etc.
>
> Believe me, I agree with you. But there is a way to deal with it--not
> pretty, but it works. After you do the flip, do Apply, Save and save to a
> new folder name. Then go to that folder and do the next select operation.
>
> > And there is a NOT--you can select NOT <status>, but not NOT
> > <text>...didn't realize that there was no NOT <text>--would it be that
> > hard to hard?
>
> Very good point. I think we need this feature.
>
> > And I have to agree with your agreeing with me Mike--I love Pine
> > too--I just want it to do more! *grin*
>
> I guess we're all together on this one. The pine development team would
> not exist if they didn't want to make Pine better!
>
> Mike

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 15:03:59 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA24998
for <[email protected]>; Mon, 20 Sep 1999 15:03:58 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA06587;
Mon, 20 Sep 1999 15:03:55 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA04391;
Mon, 20 Sep 1999 15:02:47 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA09934
for <[email protected]>; Mon, 20 Sep 1999 14:58:40 -0700
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA00663
for <[email protected]>; Mon, 20 Sep 1999 14:58:39 -0700
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA27985;
Mon, 20 Sep 1999 17:58:34 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 17:58:33 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Jo Knox <[email protected]>
X-Cc: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Yeah, I realized that this was a bad example in terms on being able to do
it other ways. What I was thinking of was something more...evil... :)

Say you sort mail from one list into a certain folder. Then there happens
to be another list (a sub-list of the first one; same domain) that gets
cc:'ed along with that one occassionally. Now (10k messages later! :PP)
you want to select only the messages that went to that one list (some
having been deleted over time) and save them in a folder . If I select
messages that go to the sub-list, I'd want to then apply an operation to
narrow to those messages not To: or Cc: to the main list. This way I'd be
sure of getting those messages only sent to the sub-list.

Now, while an admittedly complicated and possibly avoidable situation, it
is one that has arisen for me a few times (also involving 3rd level
selections) where a NOT <text> (even just NOT <header>) would have been
very useful.

And I like Mike's suggestion of limiting a search to the body of a message
would be great too--I was thinking of it the other day--thanks for
remembering for me! ;)

BINO

On Mon, 20 Sep 1999, Jo Knox wrote:

> On Mon, 20 Sep 1999, Bino Gopal wrote:
>
> > Yep, know all about the flip; it's saved my life on many an occasion, but
> > unfortunately, with multiple intersecting sets, it just doesn't cut the
> > mustard (if you're one or two levels down). What if you need to select
> > messages from a certain list, then find the ones that don't have router in
> > them?--then if you flip, and you get all the messages that aren't from
> > that list too, etc.
>
> Actually, it'll still do that---select text "router", flip, then narrow
> selection to the certain list! If you only need one flip, do it first,
> and the rest will follow as a narrow.
>
> But I agree NOT is needed!
> jo
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 15:13:33 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA25194
for <[email protected]>; Mon, 20 Sep 1999 15:13:31 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA26774;
Mon, 20 Sep 1999 15:13:30 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA24163;
Mon, 20 Sep 1999 15:12:43 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA67052
for <[email protected]>; Mon, 20 Sep 1999 15:08:57 -0700
Received: from locutus (locutus.plaidranch.org [209.151.69.20])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA05543
for <[email protected]>; Mon, 20 Sep 1999 15:08:56 -0700
Received: from localhost (localhost [127.0.0.1])
by locutus (8.9.3/8.9.3) with ESMTP id QAA17818;
Mon, 20 Sep 1999 16:17:46 -0600
Message-Id: <[email protected]>
Date: Mon, 20 Sep 1999 16:17:16 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Ian Hall-Beyer <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: IN BOX folders?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jennifer Payne <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Sep 1999, Jennifer Payne wrote:

> I'm wondering if there's a way to specify where emails are delivered into
> Pine. I would like to create folders within the IN BOX so that emails
> with certain subject headings will go to their specified folders. Is this
> possible?

Yes, very much so, with procmail. I use it to sort my mail out to about 20
different inboxes.

-Ian

--
<cosmo> wow, this is kinda nifty. the win98 protocol stack is
like a chinese finger puzzle, twist and turn in the right places,
and it pops right off --Seen on EFNet IRC

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Sep 1999 22:29:30 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA32209
for <[email protected]>; Mon, 20 Sep 1999 22:29:29 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA15340;
Mon, 20 Sep 1999 22:29:27 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id WAA18339;
Mon, 20 Sep 1999 22:28:44 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA71410
for <[email protected]>; Mon, 20 Sep 1999 22:25:04 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA06690
for <[email protected]>; Mon, 20 Sep 1999 22:25:03 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA17352; Tue, 21 Sep 1999 05:31:46 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Mon, 20 Sep 99 22:31 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA13561;
Mon, 20 Sep 1999 22:11:47 -0700
Message-Id: <Pine.LNX.4.05.9909202207140.13502-100000@ArmispianSystems.Rossland.bc.ca>
Date: Mon, 20 Sep 1999 22:11:45 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: IN BOX folders?
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Ian Hall-Beyer <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Sep 1999, Ian Hall-Beyer wrote:

> On Mon, 20 Sep 1999, Jennifer Payne wrote:
>
> > I'm wondering if there's a way to specify where emails are delivered into
> > Pine. I would like to create folders within the IN BOX so that emails
> > with certain subject headings will go to their specified folders. Is this
> > possible?
>
> Yes, very much so, with procmail. I use it to sort my mail out to about 20
> different inboxes.

I know ``me too'' is sort of not appropriate. It would be nice if
Pine could somehow launch the procmail process (for some people), on start
or something (I've never gotten the ``initial keystrokes'' to work, but I
was probably not looking into it deep enough), as they may not be able to
do it as mail is ariving. I don't see this as a needed feature (the need
to filter with Pine in this way). Another thing that will work is to to
select (;) and then apply (a). But, procmail is the way to do it in most
cases...

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Sep 1999 06:14:04 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA08869
for <[email protected]>; Tue, 21 Sep 1999 06:14:03 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA09738;
Tue, 21 Sep 1999 06:14:01 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id GAA24817;
Tue, 21 Sep 1999 06:13:18 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA29158
for <[email protected]>; Tue, 21 Sep 1999 06:09:33 -0700
Received: from federation.addy.com (federation.addy.com [207.239.68.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA13261
for <[email protected]>; Tue, 21 Sep 1999 06:09:32 -0700
Received: from localhost (jim@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id JAA28946 for <[email protected]>; Tue, 21 Sep 1999 09:09:28 -0400 (EDT)
Message-Id: <[email protected]>
Date: Tue, 21 Sep 1999 09:09:27 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jim Sander <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: IN BOX folders?
In-Reply-To: <Pine.LNX.4.05.9909202207140.13502-100000@ArmispianSystems.Rossland.bc.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> It would be nice if Pine could somehow launch the procmail process

alias pine script-that-calls-procmail-then-pine

Why make pine do this when the shell already does it much more
effectively and efficiently? You can run procmail on an existing mailbox.
I've never done it, but it's in the docs.

-=Jim=-

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Sep 1999 06:24:38 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA08981
for <[email protected]>; Tue, 21 Sep 1999 06:24:37 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA09924;
Tue, 21 Sep 1999 06:24:35 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id GAA14465;
Tue, 21 Sep 1999 06:23:09 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA17078
for <[email protected]>; Tue, 21 Sep 1999 06:19:49 -0700
Received: from ciao.cc.columbia.edu (IDENT:[email protected] [128.59.59.11])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA05987
for <[email protected]>; Tue, 21 Sep 1999 06:19:49 -0700
Received: from localhost by ciao.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id JAA20064;
Tue, 21 Sep 1999 09:19:47 -0400 (EDT)
Message-Id: <[email protected]>
Date: Tue, 21 Sep 1999 09:19:47 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Freda B Birnbaum <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: faking out the "not" feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Cc: Freda B Birnbaum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> > > Is it possible, in the 'Narrow' function, to allow selection of 'NOT'
> > > things? I want to be able to select messages from a mailing list, and
> > > then pick the ones that DON'T have 'router' in the subject. This
> > > would be a REALLY, TRULY, useful feature! If this example doesn't
> > > convince you, see the more detailed one below.
> >
> > Pine actually has a minimal sort of NOT facility. You can search for all
> > messages in the folder containing 'router' in the subject, then use ";f"
> > to 'flip' from what you've selected to what you have not selected. Thus,
> > the ";f" will give you all messages that do NOT contain 'router' in the
> > subject.
> Yep, know all about the flip; it's saved my life on many an occasion, but
> unfortunately, with multiple intersecting sets, it just doesn't cut the
> mustard (if you're one or two levels down). What if you need to select
> messages from a certain list, then find the ones that don't have router in
> them?--then if you flip, and you get all the messages that aren't from
> that list too, etc.

How about SAVE-ing all the narrowed-down messages to a folder, getting
into the folder, and then selecting/narrowing from within that folder?

> And there is a NOT--you can select NOT <status>, but not NOT
> <text>...didn't realize that there was no NOT <text>--would it be that
> hard to hard? I mean, how about the inverse of Narrow, something like
> 'Wean', where you give it a criteria, and for messages that match that
> criteria in a selected set, it tosses out those messages, instead of
> keeping them as Narrow does? You know, it should really be called 'Narrow
> To' if you do that...

Hmmm, did you mean "weed" for "wean"?

> And I have to agree with your agreeing with me Mike--I love Pine too--I
> just want it to do more! *grin*
>
> Btw, in case it hasn't been said recently, BIG THANKS to the Pine team for
> all the hard work and effort they put into a great program! You guys have
> done a great job; it's just that some of us out here want to eat our cake
> too! ;) Keep up the good work!

Second the motion! I like it even better than I used to like VMS mail...
(showing my age, I know...)

Freda Birnbaum, [email protected]
"Call on God, but row away from the rocks"

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Sep 1999 07:53:08 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA09744
for <[email protected]>; Tue, 21 Sep 1999 07:53:07 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA11469;
Tue, 21 Sep 1999 07:53:05 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA16774;
Tue, 21 Sep 1999 07:52:01 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA17084
for <[email protected]>; Tue, 21 Sep 1999 07:46:39 -0700
Received: from franklin.wrl.org (IDENT:[email protected] [209.96.177.100])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA22459
for <[email protected]>; Tue, 21 Sep 1999 07:46:38 -0700
Received: from localhost (jpayne@localhost)
by franklin.wrl.org (8.8.7/8.8.5) with ESMTP id KAA19551
for <[email protected]>; Tue, 21 Sep 1999 10:46:33 -0400
Message-Id: <[email protected]>
Date: Tue, 21 Sep 1999 10:46:33 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jennifer Payne <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: IN BOX folders?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Everyone's suggesting I use 'procmail' to do this, yet I'm a novice and
have no idea if this is part of PINE's setup, or a completely different
program.

Can anyone give me a few more details?

Thanks. ;)
Jenny

On Tue, 21 Sep 1999, Jim Sander wrote:

> > It would be nice if Pine could somehow launch the procmail process
>
> alias pine script-that-calls-procmail-then-pine
>
> Why make pine do this when the shell already does it much more
> effectively and efficiently? You can run procmail on an existing mailbox.
> I've never done it, but it's in the docs.
>
> -=Jim=-
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Sep 1999 09:01:33 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA30897
for <[email protected]>; Tue, 21 Sep 1999 09:01:32 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA13539;
Tue, 21 Sep 1999 09:01:30 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA29659;
Tue, 21 Sep 1999 08:59:47 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA63846
for <[email protected]>; Tue, 21 Sep 1999 08:55:31 -0700
Received: from locutus (locutus.plaidranch.org [209.151.69.20])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA00032
for <[email protected]>; Tue, 21 Sep 1999 08:55:30 -0700
Received: from localhost (localhost [127.0.0.1])
by locutus (8.9.3/8.9.3) with ESMTP id KAA22664
for <[email protected]>; Tue, 21 Sep 1999 10:05:45 -0600
Message-Id: <[email protected]>
Date: Tue, 21 Sep 1999 10:05:45 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Ian Hall-Beyer <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: IN BOX folders?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 21 Sep 1999, Jennifer Payne wrote:

> Everyone's suggesting I use 'procmail' to do this, yet I'm a novice and
> have no idea if this is part of PINE's setup, or a completely different
> program.

Procmail is a third-party application, that is quite versatile. Details
can be found at www.procmail.org, along with documentation.

-Ian

--
<cosmo> wow, this is kinda nifty. the win98 protocol stack is
like a chinese finger puzzle, twist and turn in the right places,
and it pops right off --Seen on EFNet IRC

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Sep 1999 14:20:03 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA19770
for <[email protected]>; Tue, 21 Sep 1999 14:20:02 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA03255;
Tue, 21 Sep 1999 14:19:59 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA03826;
Tue, 21 Sep 1999 14:18:27 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27472
for <[email protected]>; Tue, 21 Sep 1999 14:09:37 -0700
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA22043
for <[email protected]>; Tue, 21 Sep 1999 14:09:37 -0700
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA22952;
Tue, 21 Sep 1999 17:09:35 -0400 (EDT)
Message-Id: <[email protected]>
Date: Tue, 21 Sep 1999 17:09:33 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: faking out the "not" feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Freda B Birnbaum <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 21 Sep 1999, Freda B Birnbaum wrote:

> How about SAVE-ing all the narrowed-down messages to a folder, getting
> into the folder, and then selecting/narrowing from within that folder?

Heh, Mike already suggested that and I give the same reply that I gave to
him: AHHHHHhhhh! *running away screaming* ;)

> > And there is a NOT--you can select NOT <status>, but not NOT
> > <text>...didn't realize that there was no NOT <text>--would it be that
> > hard to hard? I mean, how about the inverse of Narrow, something like
> > 'Wean', where you give it a criteria, and for messages that match that
> > criteria in a selected set, it tosses out those messages, instead of
> > keeping them as Narrow does? You know, it should really be called 'Narrow
> > To' if you do that...
>
> Hmmm, did you mean "weed" for "wean"?

Eh, oops, hehe yeah--thanks for the correction. Definitely not Wean, and
yeah, Weed works pretty well--toss out the weeds, no? *grin*

> Second the motion! I like it even better than I used to like VMS mail...
> (showing my age, I know...)
>
> Freda Birnbaum, [email protected]

All I have to say to VMSmail is "Ow!" :P

BINO

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Sep 1999 16:35:52 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA23040
for <[email protected]>; Tue, 21 Sep 1999 16:35:50 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA27814;
Tue, 21 Sep 1999 16:35:49 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA23196;
Tue, 21 Sep 1999 16:34:46 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA22328
for <[email protected]>; Tue, 21 Sep 1999 16:31:01 -0700
Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA29352
for <[email protected]>; Tue, 21 Sep 1999 16:30:52 -0700
Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id XAA05958; Tue, 21 Sep 1999 23:35:30 GMT
Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 21 Sep 99 16:35 PDT
Received: from ArmispianSystems.Rossland.bc.ca ([email protected] [172.16.0.2])
by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id QAA03533;
Tue, 21 Sep 1999 16:18:56 -0700
Message-Id: <Pine.LNX.4.05.9909211616020.1638-100000@ArmispianSystems.Rossland.bc.ca>
Date: Tue, 21 Sep 1999 16:18:55 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jessica Rasku <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: IN BOX folders?
In-Reply-To: <[email protected]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jim Sander <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 21 Sep 1999, Jim Sander wrote:

> > It would be nice if Pine could somehow launch the procmail process
>
> alias pine script-that-calls-procmail-then-pine

Yes, that would work, if you could create the script to do that.
It is often bloody frustrating when we are told that you can ``just'' only
to find out that you can't ``just'' because, whatever it is, is not
available to us for whatever reason (right now, this isn't a problem that
I have).

> Why make pine do this when the shell already does it much more
> effectively and efficiently? You can run procmail on an existing mailbox.
> I've never done it, but it's in the docs.

Yes, you have to run the mailbox through formail and get it to run
procmail (or at least that seems to be the case). Sure, the shell does do
this, and certianly ``effectively''. But my question is, would it be
something difficult and ``painful'' to implement in pine?

Jessica

--
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701,
LinuxBox: (250) 362-9668.

List manager: [email protected]
send command help ---- To get help with majordomo
or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 22 Sep 1999 12:45:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA13813
for <[email protected]>; Wed, 22 Sep 1999 12:45:45 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA19567;
Wed, 22 Sep 1999 12:45:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA16680;
Wed, 22 Sep 1999 12:44:51 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA36760
for <[email protected]>; Wed, 22 Sep 1999 12:40:15 -0700
Received: from daisy.uwaterloo.ca ([email protected] [129.97.140.58])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA29441
for <[email protected]>; Wed, 22 Sep 1999 12:40:15 -0700
Received: from localhost (eddemain@localhost)
by daisy.uwaterloo.ca (8.8.8/8.8.8) with ESMTP id PAA07980
for <[email protected]>; Wed, 22 Sep 1999 15:40:14 -0400 (EDT)
Message-Id: <[email protected]>
Date: Wed, 22 Sep 1999 15:40:14 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Erik Demaine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Feature request
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine mailing list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I just joined this mailing list, so please forgive my ignorance:
Is this the right place to send feature requests? Do the pine developers
read this mailing list?

A brief description of my request:
The ability to specify the Content-Transfer-Encoding, in particular to
allow specifying "7bit" with no encoding (the identity encoding).

I just read the tech-notes in Pine 4.10. The section "MIME: Sending a Message"
states:

MIME has two ways of encoding data-Quoted-Printable and Base64.
Quoted-Printable leaves the ASCII text alone and only changes 8-bit
characters to "=" followed by the hex digits.
[...]
All attachments are encoded using Base64 encoding. This is so that the
attachment will arrive at the other end looking exactly like it did
when it was sent. Since Base64 is completely unreadable except by
MIME-capable mailers or programs, there is an obvious tradeoff being
made here. We chose to ensure absolutely reliable transport of
attachments at the cost of requiring a MIME-capable mailer to read
them. If the user doesn't want absolute integrity he or she may always
include text (with the ^R command) in the body of a message instead of
attaching it.

This is not exactly true about MIME only having two encodings. There is
a third encoding: the identity transform. Here are details from the MIME
standard (http://www.oac.uci.edu/indiv/ehood/MIME/MIME.html, MIME Part One,
Section 6):

The Content-Transfer-Encoding values "7bit", "8bit", and "binary" all mean
that the identity (i.e. NO) encoding transformation has been performed. As
such, they serve simply as indicators of the domain of the body data, and
provide useful information about the sort of encoding that might be needed
for transmission in a given transport system. The terms "7bit data", "8bit
data", and "binary data" are all defined in Section 2.

The quoted-printable and base64 encodings transform their input from an
arbitrary domain into material in the "7bit" range, thus making it safe to
carry over restricted transports. The specific definition of the
transformations are given below. [...]

I would like to be able to use the identity transform on attachments. My
reason is this: I often want to attach a PostScript to several people, most of
which can support MIME, but occasionally someone can't. (And I can't predict
ahead of time who can.) My PostScript documents are always 7bit, and never
start with a From line. If it were encoded in text, then even someone without
a MIME-supporting mail reader could very easily extract the file.

Would it be possible to add an option to pine to switch to specifying 7bit or
8bit or binary? I can imagine several alternatives. The simplest would be to
allow specifying an option during mail composition. I have seen several mail
readers that allow specifying "text" as the encoding format, and allow
specifying the character set (iso8859-1 implies 8bit, and us-ascii implies
7bit). More interesting might be to change the encoding depending on the file;
e.g., have a config option that, when enabled, automatically uses a 7bit or
8bit encoding if the file is expected to be transferred okay (staying in a
reasonable character set, and no leading From lines).

Opinions?
Erik
--
Erik Demaine \) e-mail: [email protected] (PGP avail.)
Dept. of Computer Science \( URL: http://daisy.uwaterloo.ca/~eddemain/
University of Waterloo )\ "The world would be a much nicer place if
Waterloo, ON Canada N2L 3G1 (\ everything were convex." -Bernard Chazelle

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 22 Sep 1999 13:51:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA15487
for <[email protected]>; Wed, 22 Sep 1999 13:51:22 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21434;
Wed, 22 Sep 1999 13:51:21 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA19765;
Wed, 22 Sep 1999 13:50:26 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA48928
for <[email protected]>; Wed, 22 Sep 1999 13:47:04 -0700
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA13822
for <[email protected]>; Wed, 22 Sep 1999 13:47:04 -0700
Received: from goedel1.math.washington.edu ([email protected] [128.95.224.2])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id NAA24653;
Wed, 22 Sep 1999 13:47:01 -0700 (PDT)
Message-Id: <Pine.OSF.4.10.9909221338470.2060-100000@goedel1.math.washington.edu>
Date: Wed, 22 Sep 1999 13:47:01 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] seclection of messages.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Bino Gopal <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Bino Gopal ([email protected]) wrote on Sep 20, 1999:

:) Well, this isn't a bug though more of a feture request:
:)
:) Is it possible, in the 'Narrow' function, to allow selection of 'NOT'
:) things? I want to be able to select messages from a mailing list, and
:) then pick the ones that DON'T have 'router' in the subject. This would be
:) a REALLY, TRULY, useful feature! If this example doesn't convince you,
:) see the more detailed one below.

I wrote a patch for doing something very similar to this for *local
folders*, you can select messages according to not containing a specific
text (not "not containig a header", but I suppose that should be easy
after this). The patch does not work for incoming folders as I still have
to figure out how to talk to the server to do this (Anyone can explain
this to me?, I am up to the point that I do not understand yet where the
selection is done, I think I can send the correct program to the server
though).

Anyway, if this is useful for you, pick the patch from the address below
and let me know if you find any bug.

Eduardo
http://www.math.washington.edu/~chappa/pine

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 23 Sep 1999 11:28:44 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05017
for <[email protected]>; Thu, 23 Sep 1999 11:28:43 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27170;
Thu, 23 Sep 1999 11:28:39 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA08795;
Thu, 23 Sep 1999 11:27:22 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA44066
for <[email protected]>; Thu, 23 Sep 1999 11:22:06 -0700
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA25030
for <[email protected]>; Thu, 23 Sep 1999 11:22:06 -0700
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA08251;
Thu, 23 Sep 1999 11:22:06 -0700
Received: from localhost (hubert@localhost)
by shiva1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA09920;
Thu, 23 Sep 1999 11:22:05 -0700
Message-Id: <Pine.GUL.4.20.9909231119400.7932-100000@shiva1.cac.washington.edu>
Date: Thu, 23 Sep 1999 11:22:05 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Hubert <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: How do I put my roles in another file?
In-Reply-To: <199909100603.CAA00666@ocalhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Timothy J Luoma <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Timothy,
I don't know if this was already answered. Start with an empty or
non-existent file and include that. Now "Shuffle" roles into the file in
the role config screen.

--
Steve Hubert <[email protected]>
Networks and Distributed Computing, Univ. of Washington, Seattle

On Fri, 10 Sep 1999, Timothy J Luoma wrote:

>
> I know I need to goto
>
> setup
> roles
> other commands
> include file
>
> but how do figure out the correct format for putting the roles in that file?
>
> how do I take the roles that are currently in my .pinerc and move them to
> the other file instead?
>
> (my goal is simply to have the roles not defined in .pinerc, which I often
> will share with folks who ask for it)
>
> Thanks for any help... didn't find anything in the FAQ
>
> TjL
>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 23 Sep 1999 14:13:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA08307
for <[email protected]>; Thu, 23 Sep 1999 14:13:45 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA19744;
Thu, 23 Sep 1999 14:13:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA02685;
Thu, 23 Sep 1999 14:10:50 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA43442
for <[email protected]>; Thu, 23 Sep 1999 14:00:31 -0700
Received: from ruby.co.clark.nv.us (ruby.co.clark.nv.us [198.200.132.17])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA02114
for <[email protected]>; Thu, 23 Sep 1999 14:00:31 -0700
Received: by ruby.co.clark.nv.us; (5.65v4.0/1.3/10May95) id AA32084; Thu, 23 Sep 1999 14:00:31 -0700
Received: from conversion.co.clark.nv.us by mailhub.co.clark.nv.us
(PMDF V5.1-12 #29712) id <[email protected]> for
[email protected]; Thu, 23 Sep 1999 14:00:27 PDT
Received: from pyrite.co.clark.nv.us by mailhub.co.clark.nv.us
(PMDF V5.1-12 #29712) with SMTP id <[email protected]>
for [email protected]; Thu, 23 Sep 1999 14:00:25 -0700 (PDT)
Message-Id: <[email protected]>
Date: Thu, 23 Sep 1999 14:00:15 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Joseph Scanlan <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Connecting to IMAP servers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

My Pine INBOX is on our GroupWise IMAP4 server. Pine is
running on a Tru 64 Unix (aka Digital Unix) system. When I
try to read a message that has attachments, Pine 3.95 fails
to display the message attachment. It does, however display
an error for each line of the attachment at the bottom of my
screen. Not the most convenient way to read an attachment.
This started after an upgrade to GroupWise but I get the
same behavior from MailAndNews.com. Curious.

MailAndNews.com and our GroupWise IMAP server work well
enough with Netscape.

Instead of fixing the problem on an old Pine, I decided to
build Pine 4.10 from a fresh tarball from UW. Same problem
with my INBOX. Different problem with MailAndNews.com. I
can't authenticate.

I do remember some discussion about IMAP problems with Pine
4.10 but didn't find the messages in the archives. I FTPed
the imap-4.6.BETA tarball from UW but haven't had any success
with it. I did a make without trouble.

First I tried a build clean, copied c-client.a into my Pine
tree, then did a build os4. After doing this I can
authenticate but I get

Problem detected: "Bad msgno 0 in mail_elt, nmsgs = 92".

when I try an index.

Next I did another build clean and tried replacing the imap
directory with a soft link to imap-4.6.BETA, then build os4.
This gives me a compile time message of

cc: Error: signals.c, line 620: In this statement, "SET_ALARMSAVE" is not declared.
mail_parameters(NULL, SET_ALARMSAVE, (void *) (seconds ? 1L : 0L));
--------------------------^
*** Exit 1
Stop.

Any suggestions? I really like Pine and don't want to use
the client that comes with GroupWise.

------------- My opinions are mine alone, and that fact -------------
------------- provides intense relief for my coworkers. -------------
Joe Scanlan Clark County CEIT
Systems Programmer fax 702 455-4932
[email protected] (not work) PO Box 551761
[email protected] (work) Las Vegas, NV, 89155-1761, USA
-------------------- http://www.co.clark.nv.us/ ---------------------

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Sep 1999 11:19:35 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30844
for <[email protected]>; Fri, 24 Sep 1999 11:19:34 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA24073;
Fri, 24 Sep 1999 11:19:32 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA25711;
Fri, 24 Sep 1999 11:18:16 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA15914
for <[email protected]>; Fri, 24 Sep 1999 11:14:15 -0700
Received: from ruby.co.clark.nv.us (ruby.co.clark.nv.us [198.200.132.17])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA08345
for <[email protected]>; Fri, 24 Sep 1999 11:14:14 -0700
Received: by ruby.co.clark.nv.us; (5.65v4.0/1.3/10May95) id AA15788; Fri, 24 Sep 1999 11:14:14 -0700
Received: from conversion.co.clark.nv.us by mailhub.co.clark.nv.us
(PMDF V5.1-12 #29712) id <[email protected]> for
[email protected]; Fri, 24 Sep 1999 11:14:09 PDT
Received: from pyrite.co.clark.nv.us by mailhub.co.clark.nv.us
(PMDF V5.1-12 #29712) with SMTP id <[email protected]>
for [email protected]; Fri, 24 Sep 1999 11:13:57 -0700 (PDT)
Message-Id: <[email protected]>
Date: Fri, 24 Sep 1999 11:13:56 -0700 (PDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Joseph Scanlan <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: re: Connecting to IMAP servers
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Mark,

Thank you for your response.

On Thu, 23 Sep 1999, you wrote (and I SNIPPED):

> I have received repeated reports, on a nearly-daily
> basis, that indicate that the GroupWise IMAP server is
> non-compliant with the IMAP specification.
>
> The only thing that I can recommend is that you try to
> obtain an update of the GroupWise server from Novell
> that fixes these problems, and/or ask Novell to contact
> me about getting these problems fixed,

I submitted an incident to Novell Electronic Support.

> and/or replace the GroupWise server with another server
> that is compliant with the IMAP specification.

Big change for us. We have *way* to many people using
GroupWise for e-mail. The Pine / Unix people are a small
minority.

> To address your other questions:
>
> You can build Pine 4.10 with imap-4.6.BETA, although you
> will get the error message about SET_ALARMSAVE being
> undefined. Just delete the offending line:
> mail_parameters(NULL, SET_ALARMSAVE, (void *) (seconds ? 1L : 0L));
> from pine4.10/src/pine/signals.c (line 620). That line
> is not needed any more.

Thanks. That did it.

------------- My opinions are mine alone, and that fact -------------
------------- provides intense relief for my coworkers. -------------
Joe Scanlan Clark County CEIT
Systems Programmer fax 702 455-4932
[email protected] (not work) PO Box 551761
[email protected] (work) Las Vegas, NV, 89155-1761, USA
-------------------- http://www.co.clark.nv.us/ ---------------------

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Sep 1999 19:18:08 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA07807
for <[email protected]>; Fri, 24 Sep 1999 19:18:07 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03610;
Fri, 24 Sep 1999 19:18:05 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id TAA02417;
Fri, 24 Sep 1999 19:17:27 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA65948
for <[email protected]>; Fri, 24 Sep 1999 19:13:50 -0700
Received: from dimple.detroit.lib.mi.us (mail.detroit.lib.mi.us [207.74.196.6])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA10506
for <[email protected]>; Fri, 24 Sep 1999 19:13:49 -0700
Received: from localhost (xmo@localhost)
by dimple.detroit.lib.mi.us (8.8.5/8.8.5/TNG) with SMTP id WAA13620
for <[email protected]>; Fri, 24 Sep 1999 22:35:50 -0400
Message-Id: <Pine.LNX.3.95q.990924223352.13609A-100000@dimple.detroit.lib.mi.us>
Date: Fri, 24 Sep 1999 22:35:50 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Xiaoling Mo <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Deleting e-mail account
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Does anyone know how to delete an e-mail account in PINE? Any help will be
greatly appreciated.

Thanks!

--
Xiaoling Mo
Detroit Public Library
5201 Woodward Ave.
Detroit, MI 48202
(313)833-4790
[email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Sep 1999 19:51:41 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA08179
for <[email protected]>; Fri, 24 Sep 1999 19:51:40 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA24828;
Fri, 24 Sep 1999 19:51:38 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id TAA18667;
Fri, 24 Sep 1999 19:51:02 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA17254
for <[email protected]>; Fri, 24 Sep 1999 19:48:21 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA08750
for <[email protected]>; Fri, 24 Sep 1999 19:48:21 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id VAA22923;
Fri, 24 Sep 1999 21:47:34 -0500 (CDT)
Message-Id: <[email protected]>
Date: Fri, 24 Sep 1999 21:47:34 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Deleting e-mail account
In-Reply-To: <Pine.LNX.3.95q.990924223352.13609A-100000@dimple.detroit.lib.mi.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Xiaoling Mo <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 24 Sep 1999, Xiaoling Mo wrote:

> Does anyone know how to delete an e-mail account in PINE? Any help
> will be greatly appreciated.

Pine mail accounts are actually created and maintained by other software.
Maybe there is a system that I'm not aware of where pine controls
accounts, but in every system I'm aware of, pine is used only to read and
send mail. Pine doesn't create accounts, delete accounts or distribute
mail to accounts.

Regards,

Mike

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 26 Sep 1999 15:50:44 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA09538
for <[email protected]>; Sun, 26 Sep 1999 15:50:43 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA28305;
Sun, 26 Sep 1999 15:50:42 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA26661;
Sun, 26 Sep 1999 15:49:56 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA64198
for <[email protected]>; Sun, 26 Sep 1999 15:45:11 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA32126
for <[email protected]>; Sun, 26 Sep 1999 15:45:10 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA28220
for <[email protected]>; Sun, 26 Sep 1999 15:45:10 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id RAA14649;
Sun, 26 Sep 1999 17:44:22 -0500 (CDT)
Message-Id: <[email protected]>
Date: Sun, 26 Sep 1999 17:44:22 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: error in line count for Text/PLAIN attachment
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I just noticed that when I send a text attachment in pine, pine will (at
least sometimes) count the number of lines incorrectly. I am using Pine
4.10 on a Sun computer running Solaris 2.6.

Here's an example. I sent a 336-line text file called 'oz.lst' with the
comment "data file" and this is what appears in pine both for the Fcc'd
message and on the message received on the other end:

[ Part 2, "data file" Text/PLAIN (Name: "oz.lst") 260 lines. ]

The file seems to have shrunk to 260 lines, but if I save the file, it is
identical to the one I transmitted (a full 336 lines).

I suggest that if Pine cannot count the lines accurately, it should not
present a line count. It can really upset a user when they see that their
file shrank! (even though it didn't shrink).

Regards,

Mike

--
Michael B. Miller, M.S., Ph.D., M.P.E.
Department of Psychology
210 McAlester Hall
University of Missouri--Columbia
Columbia, MO 65211
Phone: (573) 882-5671
Fax: (573) 882-7710
e-mail: [email protected]
web: http://taxa.psyc.missouri.edu/~mbmiller/

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 26 Sep 1999 16:27:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA09947
for <[email protected]>; Sun, 26 Sep 1999 16:27:45 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA08403;
Sun, 26 Sep 1999 16:27:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA00424;
Sun, 26 Sep 1999 16:26:56 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA49834
for <[email protected]>; Sun, 26 Sep 1999 16:23:06 -0700
Received: from fep08.tmt.tele.fi (hank-fep8-0.inet.fi [194.251.242.203])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA05167
for <[email protected]>; Sun, 26 Sep 1999 16:23:01 -0700
Received: from qn-lpr1-99.quicknet.inet.fi ([194.251.105.99])
by fep08.tmt.tele.fi (InterMail vM.4.01.02.00 201-229-116)
with ESMTP
id <19990926232243.MWHG21978.fep08.tmt.tele.fi@qn-lpr1-99.quicknet.inet.fi>
for <[email protected]>; Mon, 27 Sep 1999 02:22:43 +0300
Message-Id: <Pine.MNT.4.10.9909270217050.176-100000@rakastaja>
Date: Mon, 27 Sep 1999 02:21:31 +0300
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Martin-Eric Racine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: error in line count for Text/PLAIN attachment
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-To: Pine Discussion Forum <[email protected]>
X-Sender: q-funk@rakastaja
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 26 Sep 1999, Mike Miller wrote:

> I just noticed that when I send a text attachment in pine, pine will (at
> least sometimes) count the number of lines incorrectly. I am using Pine
> 4.10 on a Sun computer running Solaris 2.6.

OK, so I wasn't dreaming this. =20

We have the same problem, on MiNT. Pine 3.96 handled attachments well,
but 4.10 produces buggy MIME encoding that results in corrupt files.

--=20
----------------------------------------------------------------
Martin-=C9ric Racine The Atari Stacy and TT030 Homepage
Lappeenranta, Finland http://members.tripod.com/~TT030/
----------------------------------------------------------------
"When the time comes, I will know and I shall be." Q-Funk=20

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 26 Sep 1999 16:38:06 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA09997
for <[email protected]>; Sun, 26 Sep 1999 16:38:05 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28950;
Sun, 26 Sep 1999 16:38:03 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA29764;
Sun, 26 Sep 1999 16:37:18 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA43398
for <[email protected]>; Sun, 26 Sep 1999 16:33:54 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA05816
for <[email protected]>; Sun, 26 Sep 1999 16:33:54 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id SAA18561
for <[email protected]>; Sun, 26 Sep 1999 18:33:05 -0500 (CDT)
Message-Id: <[email protected]>
Date: Sun, 26 Sep 1999 18:33:05 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: error in line count for Text/PLAIN attachment
In-Reply-To: <Pine.MNT.4.10.9909270217050.176-100000@rakastaja>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 27 Sep 1999, Martin-Eric Racine wrote:

> On Sun, 26 Sep 1999, Mike Miller wrote:
>
> > I just noticed that when I send a text attachment in pine, pine will (at
> > least sometimes) count the number of lines incorrectly. I am using Pine
> > 4.10 on a Sun computer running Solaris 2.6.
>
> OK, so I wasn't dreaming this.
>
> We have the same problem, on MiNT. Pine 3.96 handled attachments well,
> but 4.10 produces buggy MIME encoding that results in corrupt files.

I just want to be sure I was clear: The attachment was fine, it was not
corrupt. I've personally never had a problem with an attachment. The
problem for me was that pine stated the number of lines incorrectly. The
attachment really had 336 lines and there was nothing wrong with it, but
pine told me that the attachment had 260 lines.

Mike

--
Michael B. Miller
University of Missouri--Columbia
http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 27 Sep 1999 22:19:32 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA29475
for <[email protected]>; Mon, 27 Sep 1999 22:19:30 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA32280;
Mon, 27 Sep 1999 22:19:29 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id WAA21817;
Mon, 27 Sep 1999 22:18:42 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA25748
for <[email protected]>; Mon, 27 Sep 1999 22:13:53 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA03192
for <[email protected]>; Mon, 27 Sep 1999 22:13:52 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id HAA16974
for <[email protected]>; Tue, 28 Sep 1999 07:13:50 +0200
Message-Id: <[email protected]>
Date: Tue, 28 Sep 1999 07:13:50 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [BUG] Selection of subfolders
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

There is a bug with the selection of folders in pine 4.10
To experience what I mean do the following:
- In your INBOX (or maybe even others) select a msg by moving the
hilighting on it.
- Type "s" to save the msg.
- Type "^T" to goto the folder selection screen.
- Use your arrow keys to enter the first subfolder collection (Directory)
- You wont be able to enter it.
- Try again and you will be able.
Sometimes this also happens in a deeper directory selection, while you can
however enter them using [enter] all the time.
This indicates to me IMHO that the keymapping isn't initialized when
entering the selection screen, I may very well be totaly wrong about the
cause ofcourse...;-)

TTYL,
Osman
--
Actually, Microsoft is sort of a mixture between the Borg and the Ferengi.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Sep 1999 06:04:29 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA22736
for <[email protected]>; Tue, 28 Sep 1999 06:04:28 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA20745;
Tue, 28 Sep 1999 06:04:26 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id GAA13739;
Tue, 28 Sep 1999 06:03:46 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA37466
for <[email protected]>; Tue, 28 Sep 1999 05:59:23 -0700
Received: from fw.Cable.EU.org (node100c0.a2000.nl [24.132.0.192])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA01930
for <[email protected]>; Tue, 28 Sep 1999 05:59:22 -0700
Received: from localhost (osman@localhost)
by fw.Cable.EU.org (8.9.3/8.9.3/TBG/2) with ESMTP id OAA01829;
Tue, 28 Sep 1999 14:59:12 +0200
Message-Id: <[email protected]>
Date: Tue, 28 Sep 1999 14:59:12 +0200 (CEST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Osman%Pine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: [BUG] Selection of subfolders
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nick Cropper <[email protected]>
X-Cc: Mailing-List PineInfo <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Sep 1999, Nick Cropper wrote:

> Hi Osman,
> Are you sure it's a bug? Which arrow key are you trying to use. When I
> am in that screen, all my arrow keys are used for moving, so I always use
> <rtn> to enter.

Yes I'm sure.
I use the "->" key, which lets me enter subfolders.

Hope you don't mind me CC'n this to the list, so others won't be tempted
to ask the same question...
TTYL.
--
Yes, I've heard of "decaf." What's your point?

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Sep 1999 08:12:59 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA24295
for <[email protected]>; Tue, 28 Sep 1999 08:12:58 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA23111;
Tue, 28 Sep 1999 08:12:56 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA01762;
Tue, 28 Sep 1999 08:11:46 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA63158
for <[email protected]>; Tue, 28 Sep 1999 08:07:09 -0700
Received: from equake.geol.vt.edu (equake.geol.vt.edu [128.173.184.42])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA06894
for <[email protected]>; Tue, 28 Sep 1999 08:07:09 -0700
Received: from localhost (snoke@localhost) by equake.geol.vt.edu (8.6.9/8.6.9) with ESMTP id LAA00308; Tue, 28 Sep 1999 11:07:07 -0400
Message-Id: <Pine.SUN.4.05.9909281104350.295-100000@equake>
Date: Tue, 28 Sep 1999 11:07:07 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Arthur Snoke <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: disappearing attachments
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: snoke@equake
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I am running pine 4.05 on sunos v4.1.4 and just tdoay experienced a
problem: mail files with attachemnts do not tell me about the
attachemtns. That is, all I get is about three lines when I bring up the
mail file. When I use Sun's mailtool, the attachemtns are there. These
are mail files I have read the attachemtns from but are just around in my
in box.

The update date on .pinerc is September 1. I tried rebooting but no
change.

Suggestions?

Arthur Snoke

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Sep 1999 10:58:58 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA27915
for <[email protected]>; Tue, 28 Sep 1999 10:58:57 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA28308;
Tue, 28 Sep 1999 10:58:55 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA08893;
Tue, 28 Sep 1999 10:57:49 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA62048
for <[email protected]>; Tue, 28 Sep 1999 10:53:58 -0700
Received: from equake.geol.vt.edu (equake.geol.vt.edu [128.173.184.42])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA29027
for <[email protected]>; Tue, 28 Sep 1999 10:53:57 -0700
Received: from localhost (snoke@localhost) by equake.geol.vt.edu (8.6.9/8.6.9) with ESMTP id NAA00672; Tue, 28 Sep 1999 13:53:56 -0400
Message-Id: <Pine.SUN.4.05.9909281352290.596-100000@equake>
Date: Tue, 28 Sep 1999 13:53:56 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Arthur Snoke <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: reappearing attachments
In-Reply-To: <Pine.SUN.4.05.9909281104350.295-100000@equake>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Cc: John Kelso <[email protected]>
X-Sender: snoke@equake
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I was away for a couple of hours, and now I seem to have attachments
again.

Sorry for the misfire.

On Tue, 28 Sep 1999, Arthur Snoke wrote:

> I am running pine 4.05 on sunos v4.1.4 and just tdoay experienced a
> problem: mail files with attachemnts do not tell me about the
> attachemtns. That is, all I get is about three lines when I bring up the
> mail file. When I use Sun's mailtool, the attachemtns are there. These
> are mail files I have read the attachemtns from but are just around in my
> in box.
>
> The update date on .pinerc is September 1. I tried rebooting but no
> change.
>
> Suggestions?
>
> Arthur Snoke
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 03:36:59 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA19411
for <[email protected]>; Wed, 29 Sep 1999 03:36:58 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA18808;
Wed, 29 Sep 1999 03:36:56 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id DAA15072;
Wed, 29 Sep 1999 03:36:23 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA30500
for <[email protected]>; Wed, 29 Sep 1999 03:32:54 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA28109
for <[email protected]>; Wed, 29 Sep 1999 03:32:54 -0700
Received: from relay.accent.it ([194.140.230.123])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA03808
for <[email protected]>; Wed, 29 Sep 1999 03:32:53 -0700
Received: from accent.it (acc01.accent.it [194.140.230.162]) by relay.accent.it (8.8.8+Sun/8.8.8) with ESMTP id MAA25700 for <[email protected]>; Wed, 29 Sep 1999 12:34:35 +0200 (MET DST)
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 12:30:54 +0200
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: David Lucchetti <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Pine and Fetchmail
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="------------65DDD9F9D77C0526588DBD29"
X-Sender: [email protected]
X-To: [email protected]
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is a multi-part message in MIME format.
--------------65DDD9F9D77C0526588DBD29
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Everybody;

my problem is quite simple but very difficult to solve!

I WANT to use Pine (I have 3.96 on my machine) but my system (I am not
the superuser) is configurated to access the mail using Netscape.

In this way I can read the mail using Pine but I have to get the msgs
previously using Netscape since Pine can't work as Pop (or better it can

but in the way I don't like).
I don't have (and I can't ,since I'm not the superuser) installed
sendmail on my system but I have fetchmail.

I have tried to use it but without success because it leaves the msgs on

the server but I can't access it!

In a sentence; can I use Pine without passing through Netscape having
Fetchmail

Thanks.

David

--------------65DDD9F9D77C0526588DBD29
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

X-Mozilla-Status2: 00000000
Message-ID: <[email protected]>
Date: Tue, 28 Sep 1999 16:32:13 +0200
From: David Lucchetti <[email protected]>
Organization: Accent
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: [email protected]
CC: animal@NO_SPAM.mclv.net, [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: Pine and Fetchmail
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Everybody;

my problem is quite simple but very difficult to solve!

I WANT to use Pine (I have 3.96 on my machine) but my system (I am not
the superuser) is configurated to access the mail using Netscape.

In this way I can read the mail using Pine but I have to get the msgs
previously using Netscape since Pine can't work as Pop (or better it can
but in the way I don't like).
I don't have (and I can't ,since I'm not the superuser) installed
sendmail on my system but I have fetchmail.

I have tried to use it but without success because it leaves the msgs on
the server but I can't access it!

In a sentence; can I use Pine without passing through Netscape having
Fetchmail

Thanks.

David

--------------65DDD9F9D77C0526588DBD29--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 04:13:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA20526
for <[email protected]>; Wed, 29 Sep 1999 04:13:45 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA04605;
Wed, 29 Sep 1999 04:13:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id EAA15547;
Wed, 29 Sep 1999 04:13:09 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA103760
for <[email protected]>; Wed, 29 Sep 1999 04:10:00 -0700
Received: from hal9k.org (PPP3-22.bom.vsnl.net.in [202.54.3.22])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA29719
for <[email protected]>; Wed, 29 Sep 1999 04:09:03 -0700
Received: from localhost (satyap@localhost)
by hal9k.org (8.9.3/8.8.7) with ESMTP id QAA00894
for <[email protected]>; Wed, 29 Sep 1999 16:29:23 +0530
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 16:29:22 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine and Fetchmail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: hal9k.org: satyap owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sep 29, 1999 at 12:30, David Lucchetti wrote:

> I WANT to use Pine (I have 3.96 on my machine) but my system (I am not
> the superuser) is configurated to access the mail using Netscape.
[snip]
> In a sentence; can I use Pine without passing through Netscape having
> Fetchmail

Summary:
You have: fetchmail, netscape, pine (3.96)
You don't have: sendmail, root access.
You want: forget netscape, let pine read the system mailbox.

fetchmail delivers to sendmail, I don't know if you can get it to put
messages directly in your system mailbox (you know,
/usr/spool/mail/$USER).

So how does netscape get your mail? If you already have a system mailbox
from which netscape gets mail, point pine at it. Else you could create a
new pine folder that actually points to the file which netscape is using.
You'll probably lose INBOX functions that way.

What OS?

Talk to your superuser. Ask him/her to set it up for you.

--
Satya.
http://satyaonline.cjb.net/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 05:54:24 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA22518
for <[email protected]>; Wed, 29 Sep 1999 05:54:23 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA06143;
Wed, 29 Sep 1999 05:54:21 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id FAA16574;
Wed, 29 Sep 1999 05:53:49 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA118958
for <[email protected]>; Wed, 29 Sep 1999 05:50:39 -0700
Received: from julie.univ-savoie.fr (univax.univ-savoie.fr [193.48.120.32])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA02494
for <[email protected]>; Wed, 29 Sep 1999 05:50:38 -0700
Received: from fuji.univ-savoie.fr (fuji.univ-savoie.fr [193.48.120.4])
by julie.univ-savoie.fr (8.9.3/jtpda-5.3.1) with ESMTP id OAA80169
for <[email protected]>; Wed, 29 Sep 1999 14:50:39 +0200 (CEST)
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 14:50:32 +0200 (MET DST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Christophe Harbine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: PINE as unix IMAP client and return-address
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

My question is about PINE running as an IMAP client on a UNIX
machine and its behavior when composing return-address :

Running as an IMAP client on a UNIX system, PINE uses the local
username to compose the return-address when sending mail.

To my opinion, PINE should use the username entered bye the user
when loging on the IMAP server to compose his return-address.

I'm I thiking wrong ?... Is there a way to change this behavior ?

Thanks for your help and attention...

Amicalement, /\
Christophe / \/\ -----------------------------------------------
/ / \ Christophe Harbine - C.R.I.R
/\ /\ / /\/ \ Universite de Savoie - Domaine Scientifique
/ \/\ / \/\/ /\ 73376 Le Bourget du Lac Cedex - France
/\ \/ / /\ \ Tel: +33 4 79 75 87 54 - FAX: +33 4 79 75 87 23
\ \ / / \/\ -----------------------------------------------

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 06:22:46 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA10397
for <[email protected]>; Wed, 29 Sep 1999 06:22:44 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA06578;
Wed, 29 Sep 1999 06:22:42 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id GAA01030;
Wed, 29 Sep 1999 06:21:55 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA68448
for <[email protected]>; Wed, 29 Sep 1999 06:17:36 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA11917
for <[email protected]>; Wed, 29 Sep 1999 06:17:36 -0700
Received: from relay.accent.it ([194.140.230.123])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA06515
for <[email protected]>; Wed, 29 Sep 1999 06:17:31 -0700
Received: from accent.it (acc01.accent.it [194.140.230.162]) by relay.accent.it (8.8.8+Sun/8.8.8) with ESMTP id PAA27913 for <[email protected]>; Wed, 29 Sep 1999 15:19:04 +0200 (MET DST)
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 15:15:24 +0200
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: David Lucchetti <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: [Fwd: Pine and Fetchmail]
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="------------FF3BAB7CE39EE36DDA7A3556"
X-Sender: [email protected]
X-To: [email protected]
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is a multi-part message in MIME format.
--------------FF3BAB7CE39EE36DDA7A3556
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

--------------FF3BAB7CE39EE36DDA7A3556
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

X-Mozilla-Status2: 00000000
Message-ID: <[email protected]>
Date: Wed, 29 Sep 1999 14:21:19 +0200
From: David Lucchetti <[email protected]>
Organization: Accent
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Satya <[email protected]>
Subject: Re: Pine and Fetchmail
References: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Satya wrote:

> On Sep 29, 1999 at 12:30, David Lucchetti wrote:
>
> > I WANT to use Pine (I have 3.96 on my machine) but my system (I am not
> > the superuser) is configurated to access the mail using Netscape.
> [snip]
> > In a sentence; can I use Pine without passing through Netscape having
> > Fetchmail
>
> Summary:
> You have: fetchmail, netscape, pine (3.96)
> You don't have: sendmail, root access.
> You want: forget netscape, let pine read the system mailbox.
>
> fetchmail delivers to sendmail, I don't know if you can get it to put
> messages directly in your system mailbox (you know,
> /usr/spool/mail/$USER).
>
> So how does netscape get your mail? If you already have a system mailbox
> from which netscape gets mail, point pine at it. Else you could create a
> new pine folder that actually points to the file which netscape is using.
> You'll probably lose INBOX functions that way.
>
> What OS?
>
> Talk to your superuser. Ask him/her to set it up for you.
>
> --
> Satya.
> http://satyaonline.cjb.net/

I did, this is the problem: I created a new pine folder pointing the file
used by Netscape (called Inbox as well).
In this way I can access the e-mail but the problem is the following:

A new e-mail arrives on the E-mail server and stays there until "somebody"
doesn't trasfer it to Inbox folder;
now: PINE can't (it doesn't not tranfer), Netscape can (so every time I have
to open Netscape and to click on "get msgs" but in this way where is the
advantage?) sendmail can (but I don't have as well as I don't have a
/var/spool/mail/$USER file and in addition to that my system administrator
doesn't want to install it).

I tried to use fetchmail (I have this at least!) but I can't manage at
all!!!

Thanks

--------------FF3BAB7CE39EE36DDA7A3556--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 11:06:41 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA29325
for <[email protected]>; Wed, 29 Sep 1999 11:06:39 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA29852;
Wed, 29 Sep 1999 11:06:33 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA29208;
Wed, 29 Sep 1999 11:03:46 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA47874
for <[email protected]>; Wed, 29 Sep 1999 10:55:56 -0700
Received: from cd.ods.org ([email protected] [207.223.236.99])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14804
for <[email protected]>; Wed, 29 Sep 1999 10:55:53 -0700
Received: from localhost (mark@localhost)
by cd.ods.org (8.9.3/8.9.3) with ESMTP id NAA00387
for <[email protected]>; Wed, 29 Sep 1999 13:57:02 -0400
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 13:57:01 -0400 (EDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Mark G." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Email Fowarding
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi, I run Pine 4.10, and I was wondering if there is any way to have email
automatically foward from one account on my machine to another.
(Eg: [email protected] / [email protected] ->
[email protected])

Thanks.
-Mark

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 11:42:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30425
for <[email protected]>; Wed, 29 Sep 1999 11:42:09 -0700 (PDT)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA15896;
Wed, 29 Sep 1999 11:42:07 -0700
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA29072;
Wed, 29 Sep 1999 11:40:32 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA50688
for <[email protected]>; Wed, 29 Sep 1999 11:15:06 -0700
Received: from locutus.plaidranch.org ([email protected] [209.151.69.20])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA18501
for <[email protected]>; Wed, 29 Sep 1999 11:15:02 -0700
Received: from localhost (manuka@localhost [127.0.0.1])
by locutus.plaidranch.org (8.9.3/8.9.3) with ESMTP id MAA06071;
Wed, 29 Sep 1999 12:29:33 -0600
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 12:29:29 -0600 (MDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Ian Hall-Beyer <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Email Fowarding
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Mark G." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 29 Sep 1999, Mark G. wrote:

> Hi, I run Pine 4.10, and I was wondering if there is any way to have email
> automatically foward from one account on my machine to another.
> (Eg: [email protected] / [email protected] ->
> [email protected])

yes, but it's not a pine feature. Just put the address in question in your
forward file in your home directory.

-Ian

--
<cosmo> wow, this is kinda nifty. the win98 protocol stack is
like a chinese finger puzzle, twist and turn in the right places,
and it pops right off --Seen on EFNet IRC

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 11:49:54 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30532
for <[email protected]>; Wed, 29 Sep 1999 11:49:53 -0700 (PDT)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA31352;
Wed, 29 Sep 1999 11:49:51 -0700
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA01683;
Wed, 29 Sep 1999 11:47:15 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA78178
for <[email protected]>; Wed, 29 Sep 1999 11:15:27 -0700
Received: from smtp01.infoave.net (smtp01.infoave.net [165.166.0.26])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA18566
for <[email protected]>; Wed, 29 Sep 1999 11:15:26 -0700
Received: from eDivision.net ("port 4669"@[206.151.216.5])
by SMTP00.InfoAve.Net (PMDF V5.1-12 #23426)
with ESMTP id <[email protected]> for
[email protected]; Wed, 29 Sep 1999 14:14:07 EDT
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 14:17:50 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: ski <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Email Fowarding
References: <[email protected]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-To: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

mark:

as it appears you are on linux/unix, why not the .forward approach?

in the $HOME directory of the machine you want to forward, create
a an ascii file called: .forward

[yes, the dot or period is necessary]

put exactly one line in it, with where to send mail. i.e.:
ski@other_mail.com

-ski

"Mark G." wrote:
>
> Hi, I run Pine 4.10, and I was wondering if there is any way to have email
> automatically foward from one account on my machine to another.
> (Eg: [email protected] / [email protected] ->
> [email protected])

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 11:53:55 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30683
for <[email protected]>; Wed, 29 Sep 1999 11:53:54 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA31468;
Wed, 29 Sep 1999 11:53:52 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA15514;
Wed, 29 Sep 1999 11:51:56 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA52602
for <[email protected]>; Wed, 29 Sep 1999 11:22:31 -0700
Received: from hal9k.org (PPP3-124.bom.vsnl.net.in [202.54.3.124])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA28341
for <[email protected]>; Wed, 29 Sep 1999 11:22:26 -0700
Received: from localhost (satyap@localhost)
by hal9k.org (8.9.3/8.8.7) with ESMTP id XAA01168;
Wed, 29 Sep 1999 23:50:02 +0530
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 23:50:01 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Email Fowarding
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Mark G." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: hal9k.org: satyap owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sep 29, 1999 at 13:57, Mark G. wrote:

> Hi, I run Pine 4.10, and I was wondering if there is any way to have email
> automatically foward from one account on my machine to another.
> (Eg: [email protected] / [email protected] ->
> [email protected])

Set up a .forward file. This is a sendmail issue.

--
Satya.
http://satyaonline.cjb.net/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 11:57:00 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30762
for <[email protected]>; Wed, 29 Sep 1999 11:56:59 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA16413;
Wed, 29 Sep 1999 11:56:57 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA15850;
Wed, 29 Sep 1999 11:55:23 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27888
for <[email protected]>; Wed, 29 Sep 1999 11:42:18 -0700
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA32266
for <[email protected]>; Wed, 29 Sep 1999 11:42:17 -0700
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id NAA13894;
Wed, 29 Sep 1999 13:40:58 -0500 (CDT)
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 13:40:58 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Email Fowarding
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Mark G." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 29 Sep 1999, Mark G. wrote:

> Hi, I run Pine 4.10, and I was wondering if there is any way to have email
> automatically foward from one account on my machine to another.
> (Eg: [email protected] / [email protected] ->
> [email protected])

What kind of machine are you using? If unix:

man aliases

Regards,

Mike

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Sep 1999 14:21:54 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA02185
for <[email protected]>; Wed, 29 Sep 1999 14:21:53 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA20502;
Wed, 29 Sep 1999 14:21:51 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA10505;
Wed, 29 Sep 1999 14:20:28 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA32070
for <[email protected]>; Wed, 29 Sep 1999 14:17:34 -0700
Received: from doogie.aa.ans.net (doogie.aa.ans.net [147.225.33.26])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA19998
for <[email protected]>; Wed, 29 Sep 1999 14:17:34 -0700
Received: (from csmall@localhost)
by doogie.aa.ans.net (8.9.0/8.9.0) id RAA18876;
Wed, 29 Sep 1999 17:17:33 -0400 (EDT)
Message-Id: <[email protected]>
Date: Wed, 29 Sep 1999 17:17:32 -0400
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Christopher Small <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: ACAP and pine.conf
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is it going to be possible in future versions of Pine to administer
not only user level options with ACAP but be able to configure
the pine.conf?

For example, if you wanted to do load balancing of mailboxes could you use
a remote configuation server such as an ACAP server to specify that different
group of users should use different IMAP servers and be able to rearrange
which server on the fly without any client changes.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 30 Sep 1999 09:38:47 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA23437
for <[email protected]>; Thu, 30 Sep 1999 09:38:46 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA10655;
Thu, 30 Sep 1999 09:38:43 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA28472;
Thu, 30 Sep 1999 09:37:16 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA61720
for <[email protected]>; Thu, 30 Sep 1999 09:33:18 -0700
Received: from wugate.wustl.edu (wugate.wustl.edu [128.252.120.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA22057
for <[email protected]>; Thu, 30 Sep 1999 09:33:17 -0700
Received: from library.wustl.edu (library.wustl.edu [128.252.66.1])
by wugate.wustl.edu (8.8.8/8.8.5) with ESMTP id LAA16802
for <[email protected]>; Thu, 30 Sep 1999 11:33:15 -0500 (CDT)
Received: from localhost (jerryp@localhost)
by library.wustl.edu (8.9.1b+Sun/8.9.1) with ESMTP id LAA23315
for <[email protected]>; Thu, 30 Sep 1999 11:33:13 -0500 (CDT)
Message-Id: <[email protected]>
Date: Thu, 30 Sep 1999 11:33:13 -0500 (CDT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jerry Pelikan <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Sendmail and sent-mail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I recently updated the version of sendmail on my server ( a SUN Entrprise
2 running Solaris7). When I did the field, that had normally said to
whom the message had been sent, now has the sender's name. Do I need to
recompile Pine, or is there a simpler fix?

Jerry Pelikan [email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 30 Sep 1999 09:58:50 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA01434
for <[email protected]>; Thu, 30 Sep 1999 09:58:49 -0700 (PDT)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA11368;
Thu, 30 Sep 1999 09:58:47 -0700
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA17368;
Thu, 30 Sep 1999 09:57:37 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA58572
for <[email protected]>; Thu, 30 Sep 1999 09:54:17 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA24804
for <[email protected]>; Thu, 30 Sep 1999 09:54:17 -0700
Received: from mobil.surnet.ru ([email protected] [195.54.2.7])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26799
for <[email protected]>; Thu, 30 Sep 1999 09:54:13 -0700
Received: (from uucgilh@localhost)
by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id VAA20121
for [email protected]; Thu, 30 Sep 1999 21:53:55 +0500 (UST)
Received: (from uucp@localhost)
by cgilh.chel.su (8.8.7/8.8.7) with UUCP id VAA01178
for [email protected]; Thu, 30 Sep 1999 21:49:01 +0600
Received: from localhost (ilia@localhost)
by localhost.cgu.chel.su (8.9.3/8.9.2) with ESMTP id JAA00335
for <[email protected]>; Thu, 30 Sep 1999 09:07:34 +0600 (ESS)
(envelope-from [email protected])
Message-Id: <[email protected]>
Date: Thu, 30 Sep 1999 09:07:32 +0600 (ESS)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Ilia Chipitsine <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: about PGP
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=koi8-r
Content-Transfer-Encoding: 8BIT
X-To: [email protected]
X-Authentication-Warning: localhost.cgu.chel.su: ilia owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Dear All,

I installed pine-4.10, there were scripts:

pgpsign, pgpencrypt, pgpdecode.

How I can make use of them ? (How to integrate them into pine ?)

Regards, (�� )

Ilia Chipitsine (�� )

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 30 Sep 1999 21:58:57 -0700 (PDT)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA06114
for <[email protected]>; Thu, 30 Sep 1999 21:58:56 -0700 (PDT)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA29716;
Thu, 30 Sep 1999 21:58:54 -0700
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id VAA02043;
Thu, 30 Sep 1999 21:58:22 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA68536
for <[email protected]>; Thu, 30 Sep 1999 21:55:09 -0700
Received: from desh.cse.iitd.ernet.in (mailer.cse.iitd.ac.in [202.141.68.3])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA05541
for <[email protected]>; Thu, 30 Sep 1999 21:55:04 -0700
Received: from basant.cse.iitd.ernet.in ([email protected] [10.20.14.19])
by desh.cse.iitd.ernet.in (8.8.7/8.8.7) with ESMTP id KAA28621
for <[email protected]>; Fri, 1 Oct 1999 10:26:45 +0530
Message-Id: <[email protected]>
Date: Fri, 1 Oct 1999 10:26:44 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Raghavendra Kulkarni <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Can I achieve this using PINE ?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

One of my friends has an interesting problem:

Folks, please let me know if I can get answers to these.

I am working on machine X.
My mails are on machine Y.

I have pine installed only on X not on Y.

Can I use pine on X to check mails on Y assuming:

1. X and Y are not in NIS.
2. /var/spool/mail is not exported on Y and I cant mount it
locally and use pine.

3. Does "POP" apply here and if it does apply...can I "pop" using
pine.

Also,
If X and Y are in same NIS, can I see my mails on Y from X
without actually bringing the mails to X.

Thanks in advance !!

RLK.

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