From pinedev@shivax2.cac.washington.edu Mon Jul  1 06:10:55 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 1 Jul 2002 06:10:55 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g61DAt2P010963
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 1 Jul 2002 06:10:55 -0700
Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 01 06:10:54 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g61DAYGL029370
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 1 Jul 2002 06:10:34 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g61D8lqt019334;
	Mon, 1 Jul 2002 06:08:47 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g61D60w3034158
	for <pine-info@reallists.u.washington.edu>; Mon, 1 Jul 2002 06:06:00 -0700
Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 01 06:06:00 2002 -0700
Received: from mail.bellhow.com (fw.bellhow.com [63.121.54.5])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g61D5xbq030992
	for <pine-info@u.washington.edu>; Mon, 1 Jul 2002 06:05:59 -0700
Received: from autopub.psc.bellhow.com (autopub.psc.bellhow.com [165.215.212.16])
	by mail.bellhow.com (8.9.3/8.9.3) with ESMTP id JAA12379
	for <pine-info@u.washington.edu>; Mon, 1 Jul 2002 09:05:52 -0400 (EDT)
Received: from localhost (herrick@localhost)
	by autopub.psc.bellhow.com (8.8.8+Sun/8.8.8) with ESMTP id JAA14994
	for <pine-info@u.washington.edu>; Mon, 1 Jul 2002 09:05:53 -0400 (EDT)
Message-Id: <Pine.GSO.4.21.0207010835520.27176-100000@autopub.psc.bellhow.com>
Date: Mon, 1 Jul 2002 09:05:51 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: daniel lance herrick <dan.herrick@pbs.proquest.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: slow marking messages deleted
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: autopub.psc.bellhow.com: herrick owned process doing -bs
X-Sender: herrick@autopub.psc.bellhow.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


I'm running Pine 4.21 on Solaris.

There is a monthly production process that sends
me several hundred e-mail messages. Pine rules
sort them into a couple local (my directories, not
on the imap server) mail folders, and I leaf
through them with the "n" key looking for
exceptions, speed is entirely satisfactory.

Now, with 1599 messages in the mailbox, I want to
get rid of last month's messages. In the folder
index, I type ahead many "d"s and it takes them
about one per second, or a little slower.

That speed was satisfactory when I was leafing
through the messages with "n", but now I just want
to get rid of the dead past.

Is there any way short of renaming the mailbox
files that would get rid of the old messages at a
suitable speed?

Maybe I should create a rule that would move
anything 45 days old out of those mailboxes into
/dev/null. At least that would run without me
having to shepherd a thousand cycles at one Hertz.

dan


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

From pinedev@shivax2.cac.washington.edu Mon Jul  1 06:44:44 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 1 Jul 2002 06:44:44 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g61Dii2P011634
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 1 Jul 2002 06:44:44 -0700
Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 01 06:44:43 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g61DibGL030002
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 1 Jul 2002 06:44:37 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g61DhllZ033076;
	Mon, 1 Jul 2002 06:43:47 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g61DgVw3050360
	for <pine-info@reallists.u.washington.edu>; Mon, 1 Jul 2002 06:42:31 -0700
Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 01 06:42:26 2002 -0700
Received: from berlin.atlantic.net (berlin.atlantic.net [209.208.0.20])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g61DgPR8009020
	for <pine-info@u.washington.edu>; Mon, 1 Jul 2002 06:42:26 -0700
Received: from localhost (orldfl-agg-1-ip-20.atlantic.net [209.208.86.83])
	by berlin.atlantic.net (8.11.6/8.11.0) with ESMTP id g61DlRa27774;
	Mon, 1 Jul 2002 09:47:27 -0400
Message-Id: <Pine.WNT.4.44.0207010939100.3416-100000@Tim>
Date: Mon, 1 Jul 2002 09:42:21 -0400 (Eastern Daylight Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Timothy J. Luoma" <luomat@peak.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: slow marking messages deleted
In-Reply-To: <Pine.GSO.4.21.0207010835520.27176-100000@autopub.psc.bellhow.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: daniel lance herrick <dan.herrick@pbs.proquest.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-MSMail-Priority: Normal
X-X-Sender: luomat@mail.peak.org
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Try this instead

; d control+w mm/dd/yyyy a d x


Translation:

; = mark messages

d = based on "d"ate

control+w = change date to BEFORE (i.e. "I want to select all messages
	dated BEFORE the date that I tell you"

mm/dd/yyyy = month/date/year, ie 6/30/2002

a = apply

d = delete

x = expunge





From pinedev@shivax2.cac.washington.edu Mon Jul  1 07:29:36 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 1 Jul 2002 07:29:35 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g61ETZ2P012641
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 1 Jul 2002 07:29:35 -0700
Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 01 07:29:34 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g61ETXGL030915
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 1 Jul 2002 07:29:34 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g61ESmlZ006366;
	Mon, 1 Jul 2002 07:28:48 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g61ERNw3069088
	for <pine-info@reallists.u.washington.edu>; Mon, 1 Jul 2002 07:27:23 -0700
Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 01 07:27:23 2002 -0700
Received: from mail.bellhow.com (fw.bellhow.com [63.121.54.5])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g61ERLJX003951
	for <pine-info@u.washington.edu>; Mon, 1 Jul 2002 07:27:22 -0700
Received: from wgs.apps1.bellhow.com (wgs.apps1.bellhow.com [192.168.70.70])
	by mail.bellhow.com (8.9.3/8.9.3) with ESMTP id KAA13398;
	Mon, 1 Jul 2002 10:27:15 -0400 (EDT)
Received: from localhost (herrick@localhost) by wgs.apps1.bellhow.com (8.8.4/8.8.3) with ESMTP id KAA14775; Mon, 1 Jul 2002 10:27:15 -0400 (EDT)
Message-Id: <Pine.GSO.4.21.0207011024580.16418-100000@wgs.apps1.bellhow.com>
Date: Mon, 1 Jul 2002 10:27:14 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: daniel lance herrick <dan.herrick@pbs.proquest.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: slow marking messages deleted
In-Reply-To: <Pine.WNT.4.44.0207010939100.3416-100000@Tim>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Timothy J. Luoma" <luomat@peak.org>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: wgs.apps1.bellhow.com: herrick owned process doing -bs
X-Sender: herrick@wgs.apps1.bellhow.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Thanks.

I had to Enable_Aggregate_Commands before it would
work, but that feature does exactly what I wanted.

(Read some more help and turned on some other
"advanced" features, while I was there. Now we'll
see if I can remember to learn to use them.)

Again, thank-you Tim,
dan


On Mon, 1 Jul 2002, Timothy J. Luoma wrote:

> 
> Try this instead
> 
> ; d control+w mm/dd/yyyy a d x
> 
> 
> Translation:
> 
> ; = mark messages
> 
> d = based on "d"ate
> 
> control+w = change date to BEFORE (i.e. "I want to select all messages
> 	dated BEFORE the date that I tell you"
> 
> mm/dd/yyyy = month/date/year, ie 6/30/2002
> 
> a = apply
> 
> d = delete
> 
> x = expunge
> 
> 
> 
> 


From pinedev@shivax2.cac.washington.edu Tue Jul  2 15:21:59 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 2 Jul 2002 15:21:59 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g62MLx2P012963
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 2 Jul 2002 15:21:59 -0700
Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jul 02 15:21:58 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g62MLqGL020850
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 2 Jul 2002 15:21:53 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g62MKcR8032536;
	Tue, 2 Jul 2002 15:20:38 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g62MH3w3049132
	for <pine-info@reallists.u.washington.edu>; Tue, 2 Jul 2002 15:17:03 -0700
Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Jul 02 15:17:02 2002 -0700
Received: from parvati.colorado.edu (parvati.Colorado.EDU [128.138.113.52])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g62MH0JX022099
	for <pine-info@u.washington.edu>; Tue, 2 Jul 2002 15:17:01 -0700
Received: from localhost (dorsey@localhost)
	by parvati.colorado.edu (8.11.6/8.11.2/ITS-5.0/standard) with ESMTP id g62MH0D25565
	for <pine-info@u.washington.edu>; Tue, 2 Jul 2002 16:17:00 -0600 (MDT)
Message-Id: <Pine.GSO.4.44.0207021607430.25530-100000@parvati.colorado.edu>
Date: Tue, 2 Jul 2002 16:17:00 -0600 (MDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Susan Dorsey <dorsey@colorado.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Problem with ^J - justify
In-Reply-To: <Pine.GSO.4.21.0207011024580.16418-100000@wgs.apps1.bellhow.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hey all,

Just went from 4.40 to 4.44 yesterday and have been getting some
inconsistently strange results using control J to justify a paragraph.
Some of the time it works fine.  More often nothing happens at all,
paragraph not justified, or "ufs" gets added to the beginning of every
line, overwriting or simply deleting three characters of the line.

This never happened with previous versions of Pine.  Has anyone else seen
this?  Or know why it's occurring?

Thanks.

Susan Dorsey

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

From pinedev@shivax2.cac.washington.edu Tue Jul  2 19:50:31 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 2 Jul 2002 19:50:31 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g632oV2P020753
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 2 Jul 2002 19:50:31 -0700
Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Jul 02 19:50:30 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g632oQvm014607
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 2 Jul 2002 19:50:26 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g632nMlZ031568;
	Tue, 2 Jul 2002 19:49:22 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g632HnNn077336
	for <pine-info@reallists.u.washington.edu>; Tue, 2 Jul 2002 19:17:50 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 02 19:15:01 2002 -0700
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g632F1JY010591
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@lists.u.washington.edu>; Tue, 2 Jul 2002 19:15:01 -0700
Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17])
	by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g632F1ej026526
	for <pine-info@u.washington.edu>; Tue, 2 Jul 2002 19:15:01 -0700
Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Jul 02 19:15:01 2002 -0700
Received: from microdol1.cac.washington.edu (microdol1.cac.washington.edu [140.142.112.196])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g632F0Tb014113
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Tue, 2 Jul 2002 19:15:01 -0700
Message-Id: <Pine.LNX.4.50.0207021910250.6759-100000@microdol1.cac.washington.edu>
Date: Tue, 2 Jul 2002 19:15:00 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Jeff Franklin <jpf@cac.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Problem with ^J - justify
In-Reply-To: <Pine.GSO.4.44.0207021607430.25530-100000@parvati.colorado.edu>
References: <Pine.GSO.4.44.0207021607430.25530-100000@parvati.colorado.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Susan Dorsey <dorsey@colorado.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 2 Jul 2002, Susan Dorsey wrote:

> Hey all,
>
> Just went from 4.40 to 4.44 yesterday and have been getting some
> inconsistently strange results using control J to justify a paragraph.
> Some of the time it works fine.  More often nothing happens at all,
> paragraph not justified, or "ufs" gets added to the beginning of every
> line, overwriting or simply deleting three characters of the line.
>
> This never happened with previous versions of Pine.  Has anyone else seen
> this?  Or know why it's occurring?

Hi Susan,

There have been a couple of bugs that have been uncovered with justify in
4.44.  The bugs have been fixed for the next release, but for the
meantime, if you want to apply the patch below, then the problem you
describe should go away.

Jeff

-- 
Jeff Franklin <jpf@cac.washington.edu>
Networks and Distributed Computing   University of Washington

-----------------
--- word.c~      2001/10/18 20:13:04
+++ word.c       2002/03/05 04:01:56
@@ -372,11 +372,11 @@
 {
     register int i, n, j, qb;

+    *buf = '\0';
     if(*q == '\0')
       return(1);

-    qb = q[strlen(q)-1] == ' ' ? 1 : 0;
-    *buf = '\0';
+    qb = (strlen(q) > 1 && q[strlen(q)-1] == ' ') ? 1 : 0;
     for(n = 0, j = 0; ;){
        for(i = 0; j <= llength(l) && qb ? q[i+1] : q[i]; i++, j++)
          if(q[i] != lgetc(l, j).c)
@@ -482,7 +482,7 @@

          default :
            if(spaces){                         /* flush word? */
-               if(line_len
+               if((line_len - qlen > 0)
                   && line_len + word_len + 1 > fillcol
                   && (line_len = fpnewline(qstr)))
                  line_last = ' ';      /* no word-flush space! */
@@ -510,7 +510,7 @@

            if(word_len + 1 >= NSTRING){
                /* Magic!  Fake that we output a wrapped word */
-               if(line_len && !same_word++)
+               if((line_len - qlen > 0) && !same_word++)
                  line_len = fpnewline(qstr);

                line_len += word_len;
@@ -527,7 +527,7 @@
     }

     if(word_len){
-       if(line_len + word_len + 1 > fillcol)
+       if((line_len - qlen > 0) && (line_len + word_len + 1 > fillcol))
          (void) fpnewline(qstr);
        else if(line_len && !isspace((unsigned char) line_last))
          linsert(1, ' ');

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


From pinedev@shivax2.cac.washington.edu Wed Jul  3 10:14:37 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 3 Jul 2002 10:14:37 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g63HEb2P011234
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 3 Jul 2002 10:14:37 -0700
Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 03 10:14:37 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63HESGL023433
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 3 Jul 2002 10:14:29 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63HD4qt015022;
	Wed, 3 Jul 2002 10:13:05 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63H94Nn027510
	for <pine-info@reallists.u.washington.edu>; Wed, 3 Jul 2002 10:09:05 -0700
Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jul 03 10:09:03 2002 -0700
Received: from uranus.kevindegraaf.net (uranus.kevindegraaf.net [216.46.199.135])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g63H8wlq010559
	for <pine-info@u.washington.edu>; Wed, 3 Jul 2002 10:09:03 -0700
Received: (qmail 23580 invoked by uid 1001); 3 Jul 2002 17:08:09 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 3 Jul 2002 17:08:09 -0000
Message-Id: <Pine.LNX.4.44L0.0207031257050.11492-100000@uranus.kevindegraaf.net>
Date: Wed, 3 Jul 2002 13:08:09 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kevin DeGraaf <kevin@kevindegraaf.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Maildir issues
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

What is the status on Pine's support for Maildir?

I applied a patch [1] to a vanilla 4.44 source tree, and Pine seems
content enough to read Maildirs, but there are some issues:

1. I was forced to symlink 'mail' to 'Maildir'; I couldn't convince Pine
(short of digging into the source) to accept a user-configured
directory for the mail folders.

2. I can't (S)ave mail into Maildirs.  Attempting this yields an error
message (">Unknown flag: U (garbage)<").

3. Is there any way to have Pine recognize Courier-IMAP's Maildir
subdirectory format in a coherent way?  I.e.:

.archive.foo
.archive.bar
.incoming.xyzzy
.incoming.baz
.blah.foo

should be rendered as:

INBOX/archive/foo
INBOX/archive/bar
INBOX/incoming/xyzzy
INBOX/incoming/baz
INBOX/blah/foo

I realize that I could have Pine work via an IMAP connection to 127.0.0.1,
but I'd like to get it working natively with Maildirs.  Any comments?

[1]: http://www.kevindegraaf.net/mirror/pine4.44-Maildir.patch

--
Kevin DeGraaf


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

From pinedev@shivax2.cac.washington.edu Sat Jul  6 09:13:02 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 6 Jul 2002 09:13:01 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g66GD12P017683
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sat, 6 Jul 2002 09:13:01 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Sat Jul 06 09:13:00 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g66GCsot010727
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 6 Jul 2002 09:12:54 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g66GBolZ025314;
	Sat, 6 Jul 2002 09:11:50 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g66G9rNn081112
	for <pine-info@reallists.u.washington.edu>; Sat, 6 Jul 2002 09:09:53 -0700
Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sat Jul 06 09:09:53 2002 -0700
Received: from front2.chartermi.net (24.213.60.124.up.mi.chartermi.net [24.213.60.124])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g66G9qlq028857
	for <pine-info@u.washington.edu>; Sat, 6 Jul 2002 09:09:53 -0700
Received: from [24.196.69.180] (HELO maranatha.chartermi.net)
  by front2.chartermi.net (CommuniGate Pro SMTP 3.5.3)
  with ESMTP id 22372483 for pine-info@u.washington.edu; Sat, 06 Jul 2002 12:09:52 -0400
Received: from chomiak (helo=localhost)
	by maranatha.chartermi.net with local-esmtp (Exim 3.35 #1 (Debian))
	id 17Qs8X-0000Jb-00
	for <pine-info@u.washington.edu>; Sat, 06 Jul 2002 11:10:17 -0500
Message-Id: <Pine.LNX.4.44.0207061106570.1210-100000@maranatha.chartermi.net>
Date: Sat, 6 Jul 2002 11:10:17 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Cheryl Homiak <chomiak@chartermi.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Get rid of Pine question when going to url
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is there any way to get Pine to quit asking whether I want to view the url. Of
course, I realize all I have to do is hit enter twice instead of once, but I'm
writing a script that will allow me to decide whether to save the url to a file
or go to it, the reasoning being that once I go to it I can bookmark it if I
want so don't need to also have it saved. that extra question about whether I
want to view the url is one I'd like to eliminate.

Thanks.

Cheryl

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

From pinedev@shivax2.cac.washington.edu Sun Jul  7 03:52:12 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 7 Jul 2002 03:52:12 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g67AqC2P004814
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sun, 7 Jul 2002 03:52:12 -0700
Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Sun Jul 07 03:52:10 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g67Aq9ot031557
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 7 Jul 2002 03:52:10 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g67ApER8015158;
	Sun, 7 Jul 2002 03:51:14 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g67AmvNn049918
	for <pine-info@reallists.u.washington.edu>; Sun, 7 Jul 2002 03:48:57 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Sun Jul 07 03:48:56 2002 -0700
Received: from cheviot4.ncl.ac.uk (cheviot4.ncl.ac.uk [128.240.233.16])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g67AmtJX024015
	for <pine-info@u.washington.edu>; Sun, 7 Jul 2002 03:48:56 -0700
Received: from finan.ncl.ac.uk (nay@finan.ncl.ac.uk [128.240.233.2])
	by cheviot4.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id g67AmQB18198
	for <pine-info@u.washington.edu>; Sun, 7 Jul 2002 11:48:26 +0100
Received: (from nay@localhost)
	by finan.ncl.ac.uk (8.9.3+Sun/8.9.0) id LAA10064
	for pine-info@u.washington.edu; Sun, 7 Jul 2002 11:48:25 +0100 (BST)
Message-Id: <200207071048.LAA10064@finan.ncl.ac.uk>
Date: Sun, 7 Jul 2002 11:48:25 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: <Alex.Yakovlev@newcastle.ac.uk>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: question about PICO editor (used with ELM mailer) 
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newcastle-MailScanner: Found to be clean (of known viruses)
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello,
 
I use ELM in combination with PICO as my editor.
I prefer using all this simple ASCII stuff to anything
'more contemprorary'.

However, for a long time I have been living with the
following problem:

How to get rid of long attachments (from the
original postings to me) that stick to my reply.

The problem is that those (MIME) attachments
stick to my reply as ascii text.
On the other hand, PICO does not seem to provide
a command where I can select the whole piece of
text 'onwards till the EOF', which I could then
delete at one stroke.

So, basically the question is:

[either] how to avoid attachments to be automatically
added to the text of the message edited for reply
[this is of course concerned to ELM rather than PICO]

(or at least) how to reach the end of file in PICO without
scrolling through pages with ^V

Any help is much appreciated.

Alex Yakovlev

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

From pinedev@shivax2.cac.washington.edu Sun Jul  7 04:11:53 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 7 Jul 2002 04:11:53 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g67BBq2P005752
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sun, 7 Jul 2002 04:11:52 -0700
Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Sun Jul 07 04:11:52 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g67BBoYD018272
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 7 Jul 2002 04:11:51 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g67BAuqt029336;
	Sun, 7 Jul 2002 04:10:56 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g67B9bNn061302
	for <pine-info@reallists.u.washington.edu>; Sun, 7 Jul 2002 04:09:37 -0700
Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Sun Jul 07 04:09:37 2002 -0700
Received: from gort.cjb.net (dsl-65-184-132-241.telocity.com [65.184.132.241])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g67B9alq032617
	for <pine-info@u.washington.edu>; Sun, 7 Jul 2002 04:09:37 -0700
Received: from localhost (localhost [127.0.0.1])
	by gort.cjb.net (Postfix) with ESMTP id 0EC661B6EC
	for <pine-info@u.washington.edu>; Sun,  7 Jul 2002 04:09:36 -0700 (PDT)
Message-Id: <Pine.LNX.4.21.0207070408350.4376-100000@gort.cjb.net>
Date: Sun, 7 Jul 2002 04:09:35 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Satya <satyap@satya.virtualave.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: question about PICO editor (used with ELM mailer) 
In-Reply-To: <200207071048.LAA10064@finan.ncl.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: satyap@gort.cjb.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Jul 7, 2002 at 11:48, Alex.Yakovlev@newcastle.ac.uk wrote:

>On the other hand, PICO does not seem to provide
>a command where I can select the whole piece of
>text 'onwards till the EOF', which I could then
>delete at one stroke.

^6 (mark set)
^w (search)
^v (eobuffer)
^k (kill)

-- 
Satya. <URL:http://satya.virtualave.net/>
If it wasn't for C, we would be using BASI, PASAL and OBOL!


From pinedev@shivax2.cac.washington.edu Mon Jul  8 13:19:10 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Jul 2002 13:19:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g68KJA2P022612
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 8 Jul 2002 13:19:10 -0700
Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 08 13:19:09 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68KJ1YD029375
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 8 Jul 2002 13:19:02 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68KI4R8015254;
	Mon, 8 Jul 2002 13:18:05 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68KF1Nn012430
	for <pine-info@reallists.u.washington.edu>; Mon, 8 Jul 2002 13:15:06 -0700
Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 08 13:15:01 2002 -0700
Received: from oontz.dissonant.org (dissonant.org [207.246.139.40])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68KF0bq018320
	for <pine-info@u.washington.edu>; Mon, 8 Jul 2002 13:15:01 -0700
Received: from localhost (gse@localhost)
	by oontz.dissonant.org (8.11.6/8.11.6) with ESMTP id g68JDoL30124
	for <pine-info@u.washington.edu>; Mon, 8 Jul 2002 12:13:50 -0700
Message-Id: <Pine.LNX.4.44.0207081210580.29407-100000@oontz.dissonant.org>
Date: Mon, 8 Jul 2002 12:13:50 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Evans <gse@antisleep.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: uncontrollable delay after Xpunge
In-Reply-To: <Pine.LNX.4.50.0207021910250.6759-100000@microdol1.cac.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: gse@oontz.dissonant.org
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I've mentioned this on the list before but didn't get a response... 
it seems like there are a few pine developers reading and responding
at the moment so I figured I'd ask again.

When I hit 'x' to expunge (which I do all the time), for about 5 seconds
afterwards I can't do anything else, for instance compose a new message.
I believe this delay is because pine really wants to leave the "1 message
expunged from INBOX" message up for a given amount of time.  I've dug
through the source a few times but haven't had a lot of luck tracking
down exactly what displays this message or where the length of time
is set.  But I'd really love to see this delay go away... does anyone
have any insights for me?

Thanks.



--
 scott evans :: www.antisleep.com

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

From pinedev@shivax2.cac.washington.edu Mon Jul  8 16:50:10 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Jul 2002 16:50:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g68No92P031117
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 8 Jul 2002 16:50:10 -0700
Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 08 16:50:09 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68No6pB003955
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 8 Jul 2002 16:50:06 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68NnFR8030996;
	Mon, 8 Jul 2002 16:49:15 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68Nm1Nn067148
	for <pine-info@reallists.u.washington.edu>; Mon, 8 Jul 2002 16:48:01 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 08 16:48:01 2002 -0700
Received: from oontz.dissonant.org (dissonant.org [207.246.139.40])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68Nm0JX021234
	for <pine-info@u.washington.edu>; Mon, 8 Jul 2002 16:48:00 -0700
Received: from localhost (gse@localhost)
	by oontz.dissonant.org (8.11.6/8.11.6) with ESMTP id g68MknD30922
	for <pine-info@u.washington.edu>; Mon, 8 Jul 2002 15:46:49 -0700
Message-Id: <Pine.LNX.4.44.0207081546410.30641-100000@oontz.dissonant.org>
Date: Mon, 8 Jul 2002 15:46:48 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Evans <gse@antisleep.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: uncontrollable delay after Xpunge
In-Reply-To: <Pine.LNX.4.44.0207081210580.29407-100000@oontz.dissonant.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: gse@oontz.dissonant.org
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Gah!  I slightly misspoke.  Try expunging a message or two, then
pressing "g" right away to go to another folder.  So "x g".  
Then you'll see the delay.



scott


From pinedev@shivax2.cac.washington.edu Tue Jul  9 23:56:51 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 9 Jul 2002 23:56:51 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6A6uo2P019831
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 9 Jul 2002 23:56:50 -0700
Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Jul 09 23:56:45 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6A6uioF030085
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 9 Jul 2002 23:56:44 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6A6tOqt024564;
	Tue, 9 Jul 2002 23:55:24 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6A6p4Nn104428
	for <pine-info@reallists.u.washington.edu>; Tue, 9 Jul 2002 23:51:04 -0700
Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 09 23:51:02 2002 -0700
Received: from wasp.net.au (wasp.conceptual.net.au [203.190.192.17])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6A6oolq014781
	for <pine-info@u.washington.edu>; Tue, 9 Jul 2002 23:51:02 -0700
Received: from linux.busby.net (dialup-196-212.wasp.net.au [::ffff:203.190.196.212])
  by wasp.net.au with esmtp; Wed, 10 Jul 2002 14:50:43 +0800
Received: from bret.busby.net (unknown [192.168.1.21])
	by linux.busby.net (Postfix) with ESMTP
	id C8AAC2674B; Wed, 10 Jul 2002 14:52:59 +0800 (WST)
Message-Id: <Pine.LNX.4.21.0207101433440.752-100000@bret.busby.net>
Date: Wed, 10 Jul 2002 14:42:16 +0800 (WST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bret Busby <bret@busby.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: uncontrollable delay after Xpunge
In-Reply-To: <Pine.LNX.4.44.0207081210580.29407-100000@oontz.dissonant.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 8 Jul 2002, Scott Evans wrote:

> Date: Mon, 8 Jul 2002 12:13:50 -0700 (PDT)
> From: Scott Evans <gse@antisleep.com>
> To: Pine Discussion Forum <pine-info@u.washington.edu>
> Subject: uncontrollable delay after Xpunge
> 
> I've mentioned this on the list before but didn't get a response... 
> it seems like there are a few pine developers reading and responding
> at the moment so I figured I'd ask again.
> 
> When I hit 'x' to expunge (which I do all the time), for about 5 seconds
> afterwards I can't do anything else, for instance compose a new message.
> I believe this delay is because pine really wants to leave the "1 message
> expunged from INBOX" message up for a given amount of time.  I've dug
> through the source a few times but haven't had a lot of luck tracking
> down exactly what displays this message or where the length of time
> is set.  But I'd really love to see this delay go away... does anyone
> have any insights for me?
> 
> Thanks.
> 
> 
> 
> --
>  scott evans :: www.antisleep.com
> 
> 

I do not know what version of pine you are using, but I have (thus
far) been using 4.21 for Linux (shortly to convert to 4.33 (I think it
is), on a new system build), and I have found that when I expunge, the
filters fail, until the expunge is completed.

The filters in pine are great, but this bug with expunging, makes me too
scared to use it, as a rule. Ususally, when I forget, and, expunge a
folder, I usually regret it as soon as the filters fail, and the error
messages appear. I mainly use the expunging on the INBOX, as the other
folders expunge okay on simply switching folders, but, whenever I manually
expunge, using the x command, the problem occurs. I have somewhere around
70-80 filters, and a similar number of mail folders, and can get a
thousand or so messages in a day (mainly genealogy research and mailing
lists)

Has the bug been overcome in the latest version?

-- 
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is, 
 you'll know what the answer means."
 - Deep Thought, 
   Chapter 28 of The Hitchhiker's Guide to the Galaxy
 - Douglas Adams, 1988
.......................................





From pinedev@shivax2.cac.washington.edu Wed Jul 10 08:33:13 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 10 Jul 2002 08:33:13 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6AFXC2P002179
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 10 Jul 2002 08:33:12 -0700
Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jul 10 08:33:12 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AFXBoF008662
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 10 Jul 2002 08:33:12 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AFWKeo090100;
	Wed, 10 Jul 2002 08:32:20 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AFUaNn064672
	for <pine-info@reallists.u.washington.edu>; Wed, 10 Jul 2002 08:30:36 -0700
Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 10 08:30:36 2002 -0700
Received: from asteroid.pacifier.com (new-asteroid.pacifier.com [216.65.150.154])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AFUZR8010073
	for <pine-info@u.washington.edu>; Wed, 10 Jul 2002 08:30:35 -0700
Received: from shell.pacifier.com (IDENT:neil@shell.pacifier.com [199.2.117.66])
	by asteroid.pacifier.com (8.11.2/8.11.1) with ESMTP id g6AFUTP08837
	for <pine-info@u.washington.edu>; Wed, 10 Jul 2002 08:30:29 -0700 (PDT)
Message-Id: <Pine.BSO.4.33.0207100826490.1273-100000@shell.pacifier.com>
Date: Wed, 10 Jul 2002 08:30:34 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Neil <neil@pacifier.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Pine for news question
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


I have used Pine for mail for years but only recently switched from tin to
Pine for news. I am having a little trouble adjusting.

I cannot seem to set a group to deleted or read. The problem is that each
of my groups has months and months worth of posts and I have to scroll
down to the current day which takes quite awhile.

The instructions on the Pine Web site:
http://www.washington.edu/pine/faq/news.html#8.3

do not work for me.

Thanks.

Neil

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

From pinedev@shivax2.cac.washington.edu Wed Jul 10 09:10:26 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 10 Jul 2002 09:10:26 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6AGAQ2P003698
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 10 Jul 2002 09:10:26 -0700
Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 10 09:10:25 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AGAJoF009799
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 10 Jul 2002 09:10:19 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AG9WlZ025208;
	Wed, 10 Jul 2002 09:09:32 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AG8ANn064632
	for <pine-info@reallists.u.washington.edu>; Wed, 10 Jul 2002 09:08:10 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 10 09:08:10 2002 -0700
Received: from msgdirector1.onetel.net.uk (msgdirector1.onetel.net.uk [212.67.96.148])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AG89JX008703
	for <pine-info@u.washington.edu>; Wed, 10 Jul 2002 09:08:10 -0700
Received: from async141-19.nas.onetel.net.uk (async141-19.nas.onetel.net.uk [212.67.115.141])
	by msgdirector1.onetel.net.uk (Mirapoint)
	with ESMTP id AHZ32471;
	Wed, 10 Jul 2002 17:08:27 +0100 (BST)
Message-Id: <Pine.WNT.4.44.0207101705190.-832385@no>
Date: Wed, 10 Jul 2002 17:09:58 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Nancy McGough <nm-this-address-is-valid@no.sp.am>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine for news question
In-Reply-To: <Pine.BSO.4.33.0207100826490.1273-100000@shell.pacifier.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <pine-info@u.washington.edu>
X-Message-Flag: Worried about Outlook viruses? Switch to Mac/Unix/PC Pine! Info @ www.ii.com
X-X-Sender: nancy@imap.iecc.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 10 Jul 2002 Neil (neil@pacifier.com) wrote:
> I have used Pine for mail for years but only recently switched from tin to
> Pine for news. I am having a little trouble adjusting.
>
> I cannot seem to set a group to deleted or read. The problem is that each
> of my groups has months and months worth of posts and I have to scroll
> down to the current day which takes quite awhile.
>
> The instructions on the Pine Web site:
> http://www.washington.edu/pine/faq/news.html#8.3
>
> do not work for me.


Rather than using

 ;AA*

which is what is suggested in FAQ 8.3, try this

 ;AAD

This means "Select All Apply Delete" and should work to "catchup"
(or "mark read") all messages in a newsgroup. I have lots of tips
for using Pine as a newsreader on my Power Pine page. Especially
useful are these two sections:

 <http://www.ii.com/internet/messaging/pine/pc/#speedNNTP>

 <http://www.ii.com/internet/messaging/pine/pc/#tipsNNTP>

Good luck using Pine as a newsreader,
Nancy


-- 
       PROCMAIL  <http://www.ii.com/internet/robots/procmail/qs/>
           IMAP  <http://www.ii.com/internet/messaging/imap/isps/>
           PINE  <http://www.ii.com/internet/messaging/pine/>

--  I N F I N I T E  I N K    www.ii.com    N A N C Y  M c G O U G H  --


From pinedev@shivax2.cac.washington.edu Wed Jul 10 12:29:42 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 10 Jul 2002 12:29:42 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6AJTg2P012644
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 10 Jul 2002 12:29:42 -0700
Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jul 10 12:29:41 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AJTeoF017030
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 10 Jul 2002 12:29:41 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AJSklZ023490;
	Wed, 10 Jul 2002 12:28:46 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AJRVNn036024
	for <pine-info@reallists.u.washington.edu>; Wed, 10 Jul 2002 12:27:31 -0700
Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jul 10 12:27:30 2002 -0700
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AJRUlq006474
	for <pine-info@u.washington.edu>; Wed, 10 Jul 2002 12:27:30 -0700
Received: from localhost (valites@localhost)
	by helios.geneseo.edu (8.11.5/8.11.5) with ESMTP id g6AJRPl19340
	for <pine-info@u.washington.edu>; Wed, 10 Jul 2002 15:27:25 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207101509520.8001-100000@helios.geneseo.edu>
Date: Wed, 10 Jul 2002 15:27:25 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Mark T. Valites" <valites@geneseo.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: passwordless key-based ssh authentication to courier imapd
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I apologize for the cross posting, but this is applicable to both lists.

Word from those higher above has it that we will be going to Maildir,
using courier imapd.  This is all good & grand.  However, we have a
handfull of extremely vocal users who use pine religously (this is not
bad - I love pine.  You can't get enable-aggregate-command-set in
outlook!).  After evaluating all the unoffical maildir patches, I have
decided that none of them quite meet our demands.  Using pine as an imap
client looks like the way to go.  However, that one little password
prompt will cause our group of pine users to go beZerk with a capital Z.
So, I started looking into passwordless authentication to localhost.

I came across Scott Leibrand's post at this site below:

http://www.washington.edu/pine/pine-info/1999.12/msg00170.html

And some similar information in the pine-info archives.
No luck with the courier archives.

All these assume the uw imap daemon.  In docs/tech_notes from the pine
source, the following information appears about creating an /etc/rimapd
symlink to the actualy imapd binary:

 With this configuration, the IMAP server runs without
   pre-authentication. Each new IMAP connection requires a correct
   username and password. IMAP can also be run with pre-authentication
   based on the standard _rsh_ mechanism. To enable this, the user
   account on the IMAP server must contain a valid file which grants
   access to the client machine. Enabling _rimap_ authentication is done
   by creating a link called /etc/rimapd to imapd. Basically, what is
   happening is that _Pine_ is taking advantage of the ability that rsh
   has to use privileged TCP ports so it doesn't have to run in
   privileged mode. If the rimap authentication fails it will drop back
   to plain password authentication.

I have successfully gotten this to work to my current uw imapd.  From the
manpage for (courier) imapd (debian woody), I see the following
information:

imapd may also be invoked from the shell prompt, in  which
       case  it  issues a PREAUTH response, then changes the cur
       rent directory to either its argument, or the contents  of
       the  MAILDIR  environment  variable, then attempts to talk
       IMAP on standard input and output.

which leads me to think I might be able to get this going similarily to
the uw post by Scott Leibrand.  However, all my attempts so far have
failed.

Is it possible to get passwdless, key based ssh authentication from pine
to courier imapd?

Thanks in advance,
-Mark


>--))> >--))>
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
SUNY Geneseo
Geneseo, NY 14454
585-245-5577
585-259-3471 (Cell)
585-245-5579 (Fax)

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

From pinedev@shivax2.cac.washington.edu Wed Jul 10 12:30:47 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 10 Jul 2002 12:30:47 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6AJUl2P012716
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 10 Jul 2002 12:30:47 -0700
Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 10 12:30:46 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AJUjoF017059
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 10 Jul 2002 12:30:46 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AJTgR8031212;
	Wed, 10 Jul 2002 12:29:42 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6AJStNn036056
	for <pine-info@reallists.u.washington.edu>; Wed, 10 Jul 2002 12:28:55 -0700
Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 10 12:28:55 2002 -0700
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6AJSsbq008653
	for <pine-info@washington.edu>; Wed, 10 Jul 2002 12:28:54 -0700
Received: from localhost (valites@localhost)
	by helios.geneseo.edu (8.11.5/8.11.5) with ESMTP id g6AJSrm19826;
	Wed, 10 Jul 2002 15:28:53 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207101527410.8001-100000@helios.geneseo.edu>
Date: Wed, 10 Jul 2002 15:28:53 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Mark T. Valites" <valites@geneseo.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: passwordless key-based ssh authentication to courier imapd
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: pine-info@washington.edu, <courier-users@lists.sourceforge.net>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I apologize for the cross posting, but this is applicable to both lists.

Word from those higher above has it that we will be going to Maildir,
using courier imapd.  This is all good & grand.  However, we have a
handfull of extremely vocal users who use pine religously (this is not
bad - I love pine.  You can't get enable-aggregate-command-set in
outlook!).  After evaluating all the unoffical maildir patches, I have
decided that none of them quite meet our demands.  Using pine as an imap
client looks like the way to go.  However, that one little password
prompt will cause our group of pine users to go beZerk with a capital Z.
So, I started looking into passwordless authentication to localhost.

I came across Scott Leibrand's post at this site below:

http://www.washington.edu/pine/pine-info/1999.12/msg00170.html

And some similar information in the pine-info archives.
No luck with the courier archives.

All these assume the uw imap daemon.  In docs/tech_notes from the pine
source, the following information appears about creating an /etc/rimapd
symlink to the actualy imapd binary:

 With this configuration, the IMAP server runs without
   pre-authentication. Each new IMAP connection requires a correct
   username and password. IMAP can also be run with pre-authentication
   based on the standard _rsh_ mechanism. To enable this, the user
   account on the IMAP server must contain a valid file which grants
   access to the client machine. Enabling _rimap_ authentication is done
   by creating a link called /etc/rimapd to imapd. Basically, what is
   happening is that _Pine_ is taking advantage of the ability that rsh
   has to use privileged TCP ports so it doesn't have to run in
   privileged mode. If the rimap authentication fails it will drop back
   to plain password authentication.

I have successfully gotten this to work to my current uw imapd.  From the
manpage for (courier) imapd (debian woody), I see the following
information:

imapd may also be invoked from the shell prompt, in  which
       case  it  issues a PREAUTH response, then changes the cur
       rent directory to either its argument, or the contents  of
       the  MAILDIR  environment  variable, then attempts to talk
       IMAP on standard input and output.

which leads me to think I might be able to get this going similarily to
the uw post by Scott Leibrand.  However, all my attempts so far have
failed.

Is it possible to get passwdless, key based ssh authentication from pine
to courier imapd?

Thanks in advance,
-Mark


>--))> >--))>
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
SUNY Geneseo
Geneseo, NY 14454
585-245-5577
585-259-3471 (Cell)
585-245-5579 (Fax)



From pinedev@shivax2.cac.washington.edu Wed Jul 10 14:22:45 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 10 Jul 2002 14:22:45 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6ALMi2P017476
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 10 Jul 2002 14:22:44 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 10 14:22:43 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6ALMhoF020782
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 10 Jul 2002 14:22:43 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6ALLJqt030154;
	Wed, 10 Jul 2002 14:21:20 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6ALJkNn022248
	for <pine-info@reallists.u.washington.edu>; Wed, 10 Jul 2002 14:19:46 -0700
Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 10 14:19:45 2002 -0700
Received: from quasi.uchicago.edu (quasi.uchicago.edu [128.135.99.55])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6ALJibq008499
	for <pine-info@u.washington.edu>; Wed, 10 Jul 2002 14:19:45 -0700
Received: from anita (anita.uchicago.edu [128.135.99.35])
	by quasi.uchicago.edu (Postfix) with SMTP
	id 3D68BF402; Wed, 10 Jul 2002 16:19:44 -0500 (CDT)
Message-Id: <024c01c22857$82df8e30$23638780@uchicago.edu>
Date: Wed, 10 Jul 2002 16:19:44 -0500
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Kim Scarborough" <lists@jinx.unknown.nu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: can someone tell me how to compile pico statically
References: <Pine.BSF.4.44.0206180212150.97677-100000@pooh.ASARian.org>
X-To: "Fuzzy" <fuzzy@pooh.ASARian.org>,
   "Pine Discussion Forum" <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> I need an editor in single user, so I'd like to
> compile a copy of pico linked staticly.
>
> what do I need to do?

Too late to answer this? Try this:

cd pine-4.44/pico
make -f makefile.xxx clean
make CC="gcc -static" -f makefile.xxx

where xxx=your system, blah blah blah.

This is assuming you use gcc, of course.

------------------------------------------------------------------------------
Kim Scarborough                                     http://www.unknown.nu/kim/
------------------------------------------------------------------------------



From pinedev@shivax2.cac.washington.edu Thu Jul 11 06:30:18 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Jul 2002 06:30:18 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6BDUH2P008464
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 11 Jul 2002 06:30:17 -0700
Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 11 06:30:16 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6BDUFoF009082
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 11 Jul 2002 06:30:16 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6BDTBR8026862;
	Thu, 11 Jul 2002 06:29:11 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6BDRBNn032662
	for <pine-info@reallists.u.washington.edu>; Thu, 11 Jul 2002 06:27:12 -0700
Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Jul 11 06:27:11 2002 -0700
Received: from plum.flirble.org (plum.flirble.org [195.40.6.20])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6BDR8R8018725
	for <pine-info@u.washington.edu>; Thu, 11 Jul 2002 06:27:10 -0700
Received: from scot (helo=localhost)
	by plum.flirble.org with local-esmtp (Exim 3.20 #3)
	id 17SdyH-000Kmr-00
	for pine-info@u.washington.edu; Thu, 11 Jul 2002 14:27:01 +0100
Message-Id: <20020711142514.B77669-100000@plum.flirble.org>
Date: Thu, 11 Jul 2002 14:27:01 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scot Elliott <scot@poptart.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: reccursive malloc() calls with emails
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: scot@plum.flirble.org
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi there.

I've just tried opening a large (12M) email (uuencoded body text), and had
to kill pine from the command line.  There were messages from malloc()
about recursive calls.  Platform is: FreeBSD 4.4, Pine v 4.44.  Anyone
else experienced this?

Thanks

Scot


--
Scot Elliott      (E)scot@poptart.org      (T)07813 651654      (F)07092 010646
PGP key at http://www.poptart.org/scot.asc


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

From pinedev@shivax2.cac.washington.edu Fri Jul 12 07:57:13 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Jul 2002 07:57:13 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6CEvD2P018113
	for <mailarch+pine-info@groupms.cac.washington.edu>; Fri, 12 Jul 2002 07:57:13 -0700
Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Jul 12 07:57:12 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6CEvBoF014090
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 12 Jul 2002 07:57:12 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6CEtolZ033084;
	Fri, 12 Jul 2002 07:55:50 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6CErXNn079708
	for <pine-info@reallists.u.washington.edu>; Fri, 12 Jul 2002 07:53:33 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Jul 12 07:53:32 2002 -0700
Received: from msgdirector1.onetel.net.uk (msgdirector1.onetel.net.uk [212.67.96.148])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6CErVJX029516
	for <pine-info@u.washington.edu>; Fri, 12 Jul 2002 07:53:32 -0700
Received: from async125-17.nas.onetel.net.uk (async125-17.nas.onetel.net.uk [212.67.113.125])
	by msgdirector1.onetel.net.uk (Mirapoint)
	with ESMTP id AIA76100;
	Fri, 12 Jul 2002 15:53:13 +0100 (BST)
Message-Id: <Pine.WNT.4.44.0207121550310.-799513@no>
Date: Fri, 12 Jul 2002 15:55:00 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Nancy McGough <nm-this-address-is-valid@no.sp.am>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: passwordless key-based ssh authentication to courier imapd
In-Reply-To: <Pine.GSO.4.44.0207101527410.8001-100000@helios.geneseo.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <pine-info@u.washington.edu>
X-Message-Flag: Worried about Outlook viruses? Switch to Mac/Unix/PC Pine! Info @ www.ii.com
X-X-Sender: nancy@imap.iecc.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 10 Jul 2002 Mark T. Valites (valites@geneseo.edu) wrote:
> Is it possible to get passwdless, key based ssh authentication from pine
> to courier imapd?

It seems that DreamHost has this setup. Check out the following
DH Knowledge Base article:

 <https://kbase.newdream.net/index.cgi?area=1178>

Maybe Will (who works at DreamHost) will tell us more about the
technical details of setting this up.

I'm curious about this too...
Thanks,
Nancy


-- 
       PROCMAIL  <http://www.ii.com/internet/robots/procmail/qs/>
           IMAP  <http://www.ii.com/internet/messaging/imap/isps/>
           PINE  <http://www.ii.com/internet/messaging/pine/>

--  I N F I N I T E  I N K    www.ii.com    N A N C Y  M c G O U G H  --


From pinedev@shivax2.cac.washington.edu Fri Jul 12 08:08:30 2002 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Jul 2002 08:08:30 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6CF8T2P018468
	for <mailarch+pine-info@groupms.cac.washington.edu>; Fri, 12 Jul 2002 08:08:29 -0700
Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Jul 12 08:08:29 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6CF8PpB030956
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 12 Jul 2002 08:08:25 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6CF7Sqt033162;
	Fri, 12 Jul 2002 08:07:29 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6CF6LNn100560
	for <pine-info@reallists.u.washington.edu>; Fri, 12 Jul 2002 08:06:21 -0700
Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Jul 12 08:06:19 2002 -0700
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6CF6Ilq013240
	for <pine-info@u.washington.edu>; Fri, 12 Jul 2002 08:06:19 -0700
Received: from localhost (valites@localhost)
	by helios.geneseo.edu (8.11.5/8.11.5) with ESMTP id g6CF6Gf18900;
	Fri, 12 Jul 2002 11:06:16 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207121103130.11071-100000@helios.geneseo.edu>
Date: Fri, 12 Jul 2002 11:06:16 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Mark T. Valites" <valites@geneseo.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: passwordless key-based ssh authentication to courier imapd
In-Reply-To: <Pine.WNT.4.44.0207121550310.-799513@no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy McGough <nm-this-address-is-valid@no.sp.am>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> It seems that DreamHost has this setup. Check out the following
> DH Knowledge Base article:
>
>  <https://kbase.newdream.net/index.cgi?area=1178>
>
> Maybe Will (who works at DreamHost) will tell us more about the
> technical details of setting this up.
>

The setup from the original links I set works exactly as stated.  I'm not
too sure about the DreamHost setup, but I would guess they're not running
courier imapd from the output of imapd

(* PREAUTH hoggle.dreamhost.com IMAP4rev1 2000.281 at Thu, 28 Mar 2002
17:13:48 -0800 (PST))

Getting it to work with uw imapd was no problem.  I'd like to get it for
courier imapd though.  It looks like it *should* go, but still no luck
after two days of banging away at it...


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Jul 2002 08:22:51 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6CFMp2P019069
	for <mailarch+pine-info@groupms.cac.washington.edu>; Fri, 12 Jul 2002 08:22:51 -0700
Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Jul 12 08:22:50 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6CFMioF014854
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 12 Jul 2002 08:22:44 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6CFLllZ031560;
	Fri, 12 Jul 2002 08:21:48 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6CFKeNn079692
	for <pine-info@reallists.u.washington.edu>; Fri, 12 Jul 2002 08:20:40 -0700
Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Jul 12 08:20:39 2002 -0700
Received: from msgdirector1.onetel.net.uk (msgdirector1.onetel.net.uk [212.67.96.148])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6CFKcJX003003
	for <pine-info@u.washington.edu>; Fri, 12 Jul 2002 08:20:39 -0700
Received: from async125-17.nas.onetel.net.uk (async125-17.nas.onetel.net.uk [212.67.113.125])
	by msgdirector1.onetel.net.uk (Mirapoint)
	with ESMTP id AIA78041;
	Fri, 12 Jul 2002 16:20:58 +0100 (BST)
Message-Id: <Pine.WNT.4.44.0207121614390.-962405@no>
Date: Fri, 12 Jul 2002 16:22:50 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Nancy McGough <nm-this-address-is-valid@no.sp.am>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: passwordless key-based ssh authentication to courier imapd
In-Reply-To: <Pine.GSO.4.44.0207121103130.11071-100000@helios.geneseo.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <pine-info@u.washington.edu>
X-Message-Flag: Worried about Outlook viruses? Switch to Mac/Unix/PC Pine! Info @ www.ii.com
X-X-Sender: nancy@imap.iecc.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 12 Jul 2002 Mark T. Valites (valites@geneseo.edu) wrote:
> > It seems that DreamHost has this setup. Check out the following
> > DH Knowledge Base article:
> >
> >  <https://kbase.newdream.net/index.cgi?area=1178>
>
> The setup from the original links I set works exactly as stated.  I'm not
> too sure about the DreamHost setup, but I would guess they're not running
> courier imapd from the output of imapd
>
> (* PREAUTH hoggle.dreamhost.com IMAP4rev1 2000.281 at Thu, 28 Mar 2002
> 17:13:48 -0800 (PST))
>
> Getting it to work with uw imapd was no problem.  I'd like to get it for
> courier imapd though.  It looks like it *should* go, but still no luck
> after two days of banging away at it...


DH is using Courier IMAP. For example:

 telnet mail.dreamhost.com 143
 Trying 66.33.208.155...
 Connected to mail.dreamhost.com.
 Escape character is '^]'.
 * OK Courier-IMAP ready. Copyright 1998-2002 Double Precision,
 Inc.  See COPYING for distribution information.

But, maybe they haven't updated that Knowledge Base article. Now
I'm really curious to find out the DreamHost details...

Thanks,
Nancy
 who signed up for a DreamHost account because I too thought they
 were using UW IMAP


-- 
       PROCMAIL  <http://www.ii.com/internet/robots/procmail/qs/>
           IMAP  <http://www.ii.com/internet/messaging/imap/isps/>
           PINE  <http://www.ii.com/internet/messaging/pine/>

--  I N F I N I T E  I N K    www.ii.com    N A N C Y  M c G O U G H  --


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Jul 2002 01:23:44 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6E8Ni2P009853
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sun, 14 Jul 2002 01:23:44 -0700
Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Jul 14 01:23:43 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6E8NcoF013416
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 14 Jul 2002 01:23:39 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6E8MNR8019942;
	Sun, 14 Jul 2002 01:22:23 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6E8IbNn077292
	for <pine-info@reallists.u.washington.edu>; Sun, 14 Jul 2002 01:18:37 -0700
Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Sun Jul 14 01:18:36 2002 -0700
Received: from lodz.ptkardio.pl ([212.51.193.152])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6E8IYbq021883
	for <pine-info@u.washington.edu>; Sun, 14 Jul 2002 01:18:35 -0700
Received: (qmail 17415 invoked from network); 14 Jul 2002 08:08:42 -0000
Received: from unknown (HELO sun) (pekasz@212.51.193.152)
  by 212.51.193.152 with SMTP; 14 Jul 2002 08:08:42 -0000
Message-Id: <Pine.GSO.4.31.0207141005070.17410-100000@sun>
Date: Sun, 14 Jul 2002 10:08:40 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Piotr Kasztelowicz <pekasz@lodz.ptkardio.pl>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Problem with new version pine's compilation
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-X-Sender:  <pekasz@sun>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello

I have problem with compilation new (4.44) version of pine
on Solaris 2.7 with gcc

Such command by me has been given

"build CC=/usr/local/bin/gcc NOSSL NOLDAP so5

and such effect has been resulted:

dorota:3 ~/src/pine4.44% build CC=/usr/local/bin/gcc NOSSL NOLDAP so5
make args are  'CC=/usr/local/bin/gcc' so5

Making c-client library, imapd, and ipopd
eval make CC=/usr/local/bin/gcc SPECIALS= sol
Applying an process to sources...
tools/an "ln -s" src/c-client c-client
tools/an "ln -s" src/ansilib c-client
tools/an "ln -s" src/charset c-client
tools/an "ln -s" src/osdep/unix c-client
tools/an "ln -s" src/mtest mtest
tools/an "ln -s" src/ipopd ipopd
tools/an "ln -s" src/imapd imapd
ln -s tools/an .
make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox'
EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=none EXTRASPECIALS=''
BUILDTYPE=sol
make[1]: Entering directory `/export/home/pekasz/src/pine4.44/imap'
Building c-client for sol...
echo `cat SPECIALS`  > c-client/SPECIALS
cd c-client;make sol EXTRACFLAGS=''\
 EXTRALDFLAGS=''\
 EXTRADRIVERS='mbox'\
 EXTRAAUTHENTICATORS=''\
 PASSWDTYPE=std SSLTYPE=none\

make[2]: Entering directory
`/export/home/pekasz/src/pine4.44/imap/c-client'
make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox'
EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=none `cat SPECIALS` OS=sol \
 SIGTYPE=psx CHECKPW=psx CRXTYPE=nfs \
 SPOOLDIR=/var/spool MAILSPOOL=/var/mail \
 ACTIVEFILE=/usr/share/news/active \
 RSHPATH=/usr/bin/rsh \
 BASECFLAGS="-g -O2" \
 BASELDFLAGS="-lsocket -lnsl -lgen" \
 RANLIB=true CC=ucbcc
make[3]: Entering directory
`/export/home/pekasz/src/pine4.44/imap/c-client'
sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c
osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true'
Once-only environment setup...
echo ucbcc > CCTYPE
echo -g -O2 '' > CFLAGS
echo -DCREATEPROTO=unixproto -DEMPTYPROTO=unixproto \
 -DMAILSPOOL=\"/var/mail\" \
 -DANONYMOUSHOME=\"/var/mail/anonymous\" \
 -DACTIVEFILE=\"/usr/share/news/active\" -DNEWSSPOOL=\"/var/spool/news\" \
 -DRSHPATH=\"/usr/bin/rsh\" -DLOCKPGM=\"/etc/mlock\" > OSCFLAGS
echo -lsocket -lnsl -lgen  > LDFLAGS
echo "ar rc c-client.a mail.o misc.o newsrc.o smanager.o osdep.o utf8.o
siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o
smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o
phile.o mh.o mx.o;true c-client.a" > ARCHIVE
./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile
dummy
./mkauths  md5 pla log
make[4]: Entering directory
`/export/home/pekasz/src/pine4.44/imap/c-client'
echo -DMD5ENABLE=\"/etc/cram-md5.pwd\" >> OSCFLAGS
make[4]: Leaving directory
`/export/home/pekasz/src/pine4.44/imap/c-client'
ln -s os_sol.h osdep.h
ln -s os_sol.c osdepbas.c
ln -s log_std.c osdeplog.c
ln -s sig_psx.c siglocal.c
ln -s crx_nfs.c crexcl.c
sh -c '(test -f /usr/include/sys/statvfs.h -a sol != sc5 -a sol != sco) &&
ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c'
Standard password authentication
ln -s ckp_psx.c osdepckp.c
Building without SSL support
ln -s ssl_none.c osdepssl.c
cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c
`cat CCTYPE` -c `cat CFLAGS` mail.c
/bin/sh: ucbcc: not found
make[3]: *** [mail.o] Error 1
make[3]: Leaving directory
`/export/home/pekasz/src/pine4.44/imap/c-client'
make[2]: *** [sol] Error 2
make[2]: Leaving directory
`/export/home/pekasz/src/pine4.44/imap/c-client'
make[1]: *** [OSTYPE] Error 2
make[1]: Leaving directory `/export/home/pekasz/src/pine4.44/imap'
make: *** [sol] Error 2

The compilation goes further time, however no result with
created binaria has been achieved. Please help, how to

Piotr Kasztelowicz
---
Piotr Kasztelowicz                 <Piotr.Kasztelowicz@lodz.ptkardio.pl>
[http://www.am.torun.pl/~pekasz]

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Jul 2002 13:05:57 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6EK5v2P027258
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sun, 14 Jul 2002 13:05:57 -0700
Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Sun Jul 14 13:05:56 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6EK5jpB008463
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 14 Jul 2002 13:05:45 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6EK4keo090816;
	Sun, 14 Jul 2002 13:04:46 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6EK3UNn077248
	for <pine-info@reallists.u.washington.edu>; Sun, 14 Jul 2002 13:03:30 -0700
Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Sun Jul 14 13:03:29 2002 -0700
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6EK3TJY022257
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@lists.u.washington.edu>; Sun, 14 Jul 2002 13:03:29 -0700
Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17])
	by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6EK3TS4006268
	for <pine-info@u.washington.edu>; Sun, 14 Jul 2002 13:03:29 -0700
Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Sun Jul 14 13:03:27 2002 -0700
Received: from VAIO.dsl-verizon.net (evrtwa1-ar3-4-65-156-204.evrtwa1.dsl-verizon.net [4.65.156.204])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6EK3PCR028751
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sun, 14 Jul 2002 13:03:26 -0700
Message-Id: <Pine.WNT.4.43.0207141302470.348-100000@VAIO>
Date: Sun, 14 Jul 2002 13:03:18 -0700 (Pacific Standard Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Steve Hubert <hubert@washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Problem with new version pine's compilation
In-Reply-To: <Pine.GSO.4.31.0207141005070.17410-100000@sun>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Piotr Kasztelowicz <pekasz@lodz.ptkardio.pl>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: hubert@ndcms.cac.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Try
     build NOSSL NOLDAP gs5

-- 
Steve Hubert <hubert@washington.edu>
Networks and Distributed Computing, Univ. of Washington, Seattle

On Sun, 14 Jul 2002, Piotr Kasztelowicz wrote:

> Hello
>
> I have problem with compilation new (4.44) version of pine
> on Solaris 2.7 with gcc
>
> Such command by me has been given
>
> "build CC=/usr/local/bin/gcc NOSSL NOLDAP so5


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Jul 2002 23:01:54 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6F61r2P004843
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sun, 14 Jul 2002 23:01:53 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Jul 14 23:01:53 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6F61qpB017866
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 14 Jul 2002 23:01:52 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6F60tR8034196;
	Sun, 14 Jul 2002 23:00:56 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6F5wJNn089256
	for <pine-info@reallists.u.washington.edu>; Sun, 14 Jul 2002 22:58:19 -0700
Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Jul 14 22:58:18 2002 -0700
Received: from localhost.localdomain (ip133.164-173-207.eli-du.nwlink.com [207.173.164.133])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6F5wGlq024064
	for <pine-info@u.washington.edu>; Sun, 14 Jul 2002 22:58:17 -0700
Received: from localhost (neil@localhost)
	by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g6F5vkI01699;
	Sun, 14 Jul 2002 22:57:50 -0700
Message-Id: <Pine.LNX.4.33.0207142256360.1694-100000@localhost.localdomain>
Date: Sun, 14 Jul 2002 22:57:46 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Neil <neil@pacifier.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine for news question
In-Reply-To: <Pine.WNT.4.44.0207101705190.-832385@no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy McGough <nm-this-address-is-valid@no.sp.am>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: localhost.localdomain: neil owned process doing -bs
X-X-Sender:  <neil@localhost.localdomain>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Wed, 10 Jul 2002, Nancy McGough wrote:

> Rather than using
> 
>  ;AA*
> 
> which is what is suggested in FAQ 8.3, try this
> 
>  ;AAD
> 
> This means "Select All Apply Delete" and should work to "catchup"
> (or "mark read") all messages in a newsgroup. I have lots of tips
> for using Pine as a newsreader on my Power Pine page. Especially
> useful are these two sections:
> 
>  <http://www.ii.com/internet/messaging/pine/pc/#speedNNTP>
> 
>  <http://www.ii.com/internet/messaging/pine/pc/#tipsNNTP>
> 
> Good luck using Pine as a newsreader,

Thanks for the help Nancy, your suggestion worked.

Neil


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Jul 2002 16:55:34 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6FNtX2P008720
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 15 Jul 2002 16:55:33 -0700
Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 15 16:55:33 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6FNtSpB011958
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 15 Jul 2002 16:55:28 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6FNsXlZ017594;
	Mon, 15 Jul 2002 16:54:34 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6FNqoNn022254
	for <pine-info@reallists.u.washington.edu>; Mon, 15 Jul 2002 16:52:50 -0700
Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 15 16:52:49 2002 -0700
Received: from mail3.panix.com (mail3.panix.com [166.84.1.74])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6FNqnlq017481
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 16:52:49 -0700
Received: from eng-23.pacdigital (localhost.panix.com [127.0.0.1])
	by mail3.panix.com (Postfix) with ESMTP id ED8B9981B0
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 19:52:47 -0400 (EDT)
Message-Id: <Pine.LNX.4.44.0207151650590.1381-100000@eng-23.pacdigital>
Date: Mon, 15 Jul 2002 16:52:44 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kenneth Crudup <kenny@panix.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Including one message in the body of another?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: kenny@eng-23.pacdigital
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Let's say I want to Reply to someone's message, and intersperse bits of another
message with the quoted text of the current one. How do I do that?

	-Kenny

-- 
Kenneth R. Crudup    Sr. SW Engineer, Scott County Consulting, Los Angeles, CA
Home:	4105 E. Willow St. #246, Long Beach, CA 90815-1740
Work:	2052 Alton Parkway, Irvine, CA 92606-4905	   (949) 252-1111 X240

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Jul 2002 17:02:22 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6G02L2P008954
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 15 Jul 2002 17:02:21 -0700
Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 15 17:02:20 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G026pB012160
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 15 Jul 2002 17:02:06 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G01LR8015444;
	Mon, 15 Jul 2002 17:01:21 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G00eNn048044
	for <pine-info@reallists.u.washington.edu>; Mon, 15 Jul 2002 17:00:40 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 15 17:00:40 2002 -0700
Received: from simon.cs.cornell.edu (simon.cs.cornell.edu [128.84.154.10])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G00dJX010493
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 17:00:40 -0700
Received: from sundial.cs.cornell.edu (sundial.cs.cornell.edu [128.84.96.115])
	by simon.cs.cornell.edu (8.11.3/8.11.3/R-3.7) with ESMTP id g6G00bg02916;
	Mon, 15 Jul 2002 20:00:38 -0400 (EDT)
Received: from zinger.cs.cornell.edu (zinger.cs.cornell.edu [128.84.96.55])
	by sundial.cs.cornell.edu (8.11.3/8.11.3/M-3.10) with ESMTP id g6G00bZ20016;
	Mon, 15 Jul 2002 20:00:37 -0400 (EDT)
Received: from localhost (wkiri@localhost)
	by zinger.cs.cornell.edu (8.11.3/8.11.3/C-3.2) with ESMTP id g6G00aK11818;
	Mon, 15 Jul 2002 20:00:36 -0400 (EDT)
Message-Id: <Pine.GSO.4.33.0207151958570.21752-100000@zinger.cs.cornell.edu>
Date: Mon, 15 Jul 2002 20:00:36 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kiri Wagstaff <wkiri@CS.Cornell.EDU>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.LNX.4.44.0207151650590.1381-100000@eng-23.pacdigital>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Kenneth Crudup <kenny@panix.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Mon, 15 Jul 2002, Kenneth Crudup wrote:
> Let's say I want to Reply to someone's message, and intersperse bits of another
> message with the quoted text of the current one. How do I do that?

I don't know if Pine has a built-in facility for merging messages this
way.  However, you can <E>xport the second message to a text file, then
<R>eply to the first message and <Ctrl-R> (in Pico) to insert the saved
text file into the current response.

	Kiri

------------ Kiri Wagstaff, Ph.D. -------- wkiri@cs.cornell.edu -------------
   	     For a man to achieve all that is demanded of him,
	       he must regard himself as greater than he is.
		       -- Johann Wolfgang von Goethe
-----------------------------------------------------------------------------



From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Jul 2002 17:06:13 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6G06C2P009081
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 15 Jul 2002 17:06:12 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 15 17:06:07 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G066pB012267
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 15 Jul 2002 17:06:07 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G05Heo078694;
	Mon, 15 Jul 2002 17:05:17 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G049Nn067156
	for <pine-info@reallists.u.washington.edu>; Mon, 15 Jul 2002 17:04:09 -0700
Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 15 17:04:08 2002 -0700
Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G048bq018889
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 17:04:08 -0700
Received: from sonos ([12.235.26.15]) by rwcrmhc51.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020716000407.IHFN24728.rwcrmhc51.attbi.com@sonos>
          for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 00:04:07 +0000
Message-Id: <Pine.WNT.4.40.0207151653000.936-100000@sonos>
Date: Mon, 15 Jul 2002 17:00:42 -0700 (Pacific Daylight Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Jason Tiller <jason@sonos.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.LNX.4.44.0207151650590.1381-100000@eng-23.pacdigital>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: jtiller@www.fastmail.fm
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi, Kenny, :)

On Mon, 15 Jul 2002, Kenneth Crudup wrote:

> Let's say I want to Reply to someone's message, and intersperse bits
> of another message with the quoted text of the current one. How do I
> do that?

'Twould be nice if Pine had some facility like that, but I don't know
of any.  I simply view the "another message" in Emacs and copy it to
the kill ring, yanking it back into the "current message" for the
reply.

I'd be thrilled if there was a more Piney method because I encounter
this fairly frequently...

---Jason
Sonos Handbell Ensemble
http://www.sonos.org/

P.S. - I *sure* wish Pine had some kind of "background create" system
whereby Pine's interface would remain responsive while I edited a
message via an alternate editor.


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Jul 2002 17:09:28 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6G09R2P009251
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 15 Jul 2002 17:09:27 -0700
Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 15 17:09:27 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G09NoF029236
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 15 Jul 2002 17:09:23 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G08geo093352;
	Mon, 15 Jul 2002 17:08:42 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G07xNn092466
	for <pine-info@reallists.u.washington.edu>; Mon, 15 Jul 2002 17:08:00 -0700
Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 15 17:07:59 2002 -0700
Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G07xbq019789
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 17:07:59 -0700
Received: from pollux (pollux [129.252.130.113])
	by moultrie.cse.sc.edu (Postfix) with ESMTP id CA59C1E4C2
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 20:07:58 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207151903540.571-100000@pollux.cse.sc.edu>
Date: Mon, 15 Jul 2002 19:07:58 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.LNX.4.44.0207151650590.1381-100000@eng-23.pacdigital>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: gopalan@pollux.cse.sc.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 15 Jul 2002, Kenneth Crudup wrote:

> Let's say I want to Reply to someone's message, and intersperse bits
> of another message with the quoted text of the current one. How do I
> do that?

This is kinda clunky: you have to navigate your way to the mailbox that
has the message to be included, and remember its ordinal (for eg, msg 12
of 42).

Then, in your reply text, (^R)ead (^W)InsertMessage and type in the
message number from above (in this example, 12). Pine will add the
reply-leadin, and quote the message you inserted with the
reply-indent-string

Wish item: Pine should let the user navigate to a mailbox, browse the
message index, and pick the message to be inserted.

-- 
Gopi Sundaram
gopalan@cse.sc.edu
http://www.cse.sc.edu/~gopalan/Pine/





From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Jul 2002 17:34:14 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6G0YE2P010032
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 15 Jul 2002 17:34:14 -0700
Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 15 17:34:05 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G0Y4pB012922
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 15 Jul 2002 17:34:05 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G0XJeo093636;
	Mon, 15 Jul 2002 17:33:19 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G0WKNn100530
	for <pine-info@reallists.u.washington.edu>; Mon, 15 Jul 2002 17:32:21 -0700
Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 15 17:32:13 2002 -0700
Received: from mail3.panix.com (mail3.panix.com [166.84.1.74])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G0WDbq024806
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 17:32:13 -0700
Received: from eng-23.pacdigital (localhost.panix.com [127.0.0.1])
	by mail3.panix.com (Postfix) with ESMTP id 23B6398184
	for <pine-info@u.washington.edu>; Mon, 15 Jul 2002 20:32:12 -0400 (EDT)
Message-Id: <Pine.LNX.4.44.0207151731160.1381-100000@eng-23.pacdigital>
Date: Mon, 15 Jul 2002 17:32:10 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kenneth Crudup <kenny@panix.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.GSO.4.44.0207151903540.571-100000@pollux.cse.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: kenny@eng-23.pacdigital
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 15 Jul 2002, Gopi Sundaram wrote:

> Then, in your reply text, (^R)ead (^W)InsertMessage and type in the
> message number from above (in this example, 12).

Heh. This is a pico-specific method, eh?

	-Kenny, who uses an alt-editor (vi)

-- 
Kenneth R. Crudup    Sr. SW Engineer, Scott County Consulting, Los Angeles, CA
Home:	4105 E. Willow St. #246, Long Beach, CA 90815-1740
Work:	2052 Alton Parkway, Irvine, CA 92606-4905	   (949) 252-1111 X240


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Jul 2002 00:13:45 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6G7Dj2P018125
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 16 Jul 2002 00:13:45 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jul 16 00:13:44 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G7DdpB020662
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 16 Jul 2002 00:13:39 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G7Cheo093352;
	Tue, 16 Jul 2002 00:12:43 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6G75NNn088758
	for <pine-info@reallists.u.washington.edu>; Tue, 16 Jul 2002 00:05:23 -0700
Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 16 00:05:22 2002 -0700
Received: from msgdirector2.onetel.net.uk (msgdirector2.onetel.net.uk [212.67.96.149])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6G75Llq027778
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 00:05:21 -0700
Received: from 213-78-83-34.friaco.onetel.net.uk (213-78-83-34.friaco.onetel.net.uk [213.78.83.34])
	by msgdirector2.onetel.net.uk (Mirapoint)
	with ESMTP id AIH54423;
	Tue, 16 Jul 2002 08:04:58 +0100 (BST)
Message-Id: <Pine.WNT.4.44.0207160800440.-1017803-100000@no>
Date: Tue, 16 Jul 2002 08:07:49 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Nancy McGough <nm-this-address-is-valid@no.sp.am>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.GSO.4.44.0207151903540.571-100000@pollux.cse.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <pine-info@u.washington.edu>
X-Message-Flag: Worried about Outlook viruses? Switch to Mac/Unix/PC Pine! Info @ www.ii.com
X-X-Sender: nancy@imap.iecc.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 15 Jul 2002 Gopi Sundaram (gopalan@cs.sc.edu) wrote:
>
> Then, in your reply text, (^R)ead (^W)InsertMessage and type in the
> message number from above (in this example, 12). Pine will add the
> reply-leadin, and quote the message you inserted with the
> reply-indent-string

Another option if all the messages that you want to include in
your reply are in the same mailbox, is to go to the Message Index
of the mailbox and select each message using

 :

Then "Apply Reply" by typing

 A R

And include the original message my answering Yes to the next
question

 Y

Then answer the rest of the questions and edit the headers and
the body as you like.

HTH,
Nancy

PS - you need to enable-aggregate-command-set to be able to do
this.

-- 
       PROCMAIL  <http://www.ii.com/internet/robots/procmail/qs/>
           IMAP  <http://www.ii.com/internet/messaging/imap/isps/>
           PINE  <http://www.ii.com/internet/messaging/pine/>

--  I N F I N I T E  I N K    www.ii.com    N A N C Y  M c G O U G H  --


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Jul 2002 07:53:32 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6GErW2P029335
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 16 Jul 2002 07:53:32 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jul 16 07:53:31 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GErSpB028913
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 16 Jul 2002 07:53:28 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GEqYlZ024050;
	Tue, 16 Jul 2002 07:52:34 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GEouNn087642
	for <pine-info@reallists.u.washington.edu>; Tue, 16 Jul 2002 07:50:56 -0700
Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 16 07:50:56 2002 -0700
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GEoubq031570
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 07:50:56 -0700
Received: from sonos ([12.235.26.15]) by rwcrmhc52.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020716145055.RFZC8262.rwcrmhc52.attbi.com@sonos>
          for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 14:50:55 +0000
Message-Id: <Pine.WNT.4.40.0207160746070.1536-100000@sonos>
Date: Tue, 16 Jul 2002 07:47:30 -0700 (Pacific Daylight Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Jason Tiller <jason@sonos.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.WNT.4.44.0207160800440.-1017803-100000@no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: jtiller@www.fastmail.fm
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi, Nancy, :)

On Tue, 16 Jul 2002, Nancy McGough wrote:

> Another option if all the messages that you want to include in your
> reply are in the same mailbox, is to go to the Message Index of the
> mailbox and select each message using

>  :
>
> Then "Apply Reply" by typing
>
>  A R
>
> And include the original message my answering Yes to the next
> question
>
>  Y

Beautiful!  Thanks!  That helps a lot!  Very smooth.  Still wish I
could do something while composing, but this goes a long way towards
alleviating that need.

---Jason
Sonos Handbell Ensemble
http://www.sonos.org/


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Jul 2002 10:57:50 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6GHvo2P004508
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 16 Jul 2002 10:57:50 -0700
Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 16 10:57:49 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GHvlpB002466
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 16 Jul 2002 10:57:48 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GHubR8038352;
	Tue, 16 Jul 2002 10:56:39 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GHswNn081966
	for <pine-info@reallists.u.washington.edu>; Tue, 16 Jul 2002 10:54:58 -0700
Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Jul 16 10:54:57 2002 -0700
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6GHstbq021368
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 10:54:56 -0700
Received: (qmail 18894 invoked by uid 1828); 16 Jul 2002 17:54:55 -0000
Message-Id: <Pine.GSO.4.33.0207161052280.10511-100000@vax.hanford.org>
Date: Tue, 16 Jul 2002 10:54:55 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Matt Ackeret <mattack@area.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 1399
In-Reply-To: <200207160709.g6G79Hqt016666@list2.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender:  <mattack@vax.hanford.org>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

>From: Gopi Sundaram <gopalan@cs.sc.edu>
...
>Wish item: Pine should let the user navigate to a mailbox, browse the
>message index, and pick the message to be inserted.

Actually I wish there were a way to do something like:

1) select multiple messages through normal means
2) reply to both of them at once..

it would quote both messages, and I guess include all o the recipients (of
course one would have to be extra careful about sending the reply to the right
people).

Heck, I wish a newsreader had this too (I use trn for news)..  It's often easier
to reply to parts of multiple messages in one reply.   (This would be only
in one thread, for news.)


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Jul 2002 11:04:09 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6GI492P004767
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 16 Jul 2002 11:04:09 -0700
Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Jul 16 11:04:08 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GI47pB002709
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 16 Jul 2002 11:04:07 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GI3SR8028358;
	Tue, 16 Jul 2002 11:03:28 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GI2lNn008458
	for <pine-info@reallists.u.washington.edu>; Tue, 16 Jul 2002 11:02:47 -0700
Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Jul 16 11:02:47 2002 -0700
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GI2klq014887
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 11:02:46 -0700
Received: from eng-23.pacdigital (localhost.panix.com [127.0.0.1])
	by mail1.panix.com (Postfix) with ESMTP id 5468448713
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 14:02:44 -0400 (EDT)
Message-Id: <Pine.LNX.4.44.0207161102220.2113-100000@eng-23.pacdigital>
Date: Tue, 16 Jul 2002 11:02:37 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kenneth Crudup <kenny@panix.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Including one message in the body of another?
In-Reply-To: <Pine.WNT.4.44.0207160800440.-1017803-100000@no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: kenny@eng-23.pacdigital
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 16 Jul 2002, Nancy McGough wrote:

> Another option if all the messages that you want to include in
> your reply are in the same mailbox, is to go to the Message Index
> of the mailbox and select each message using

Thanks! I'll try this.

	-Kenny

-- 
Kenneth R. Crudup    Sr. SW Engineer, Scott County Consulting, Los Angeles, CA
Home:	4105 E. Willow St. #246, Long Beach, CA 90815-1740
Work:	2052 Alton Parkway, Irvine, CA 92606-4905	   (949) 252-1111 X240


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Jul 2002 11:09:07 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6GI972P004980
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 16 Jul 2002 11:09:07 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jul 16 11:09:06 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GI92pB002881
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 16 Jul 2002 11:09:03 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GI8DlZ015126;
	Tue, 16 Jul 2002 11:08:13 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6GI6TNn059154
	for <pine-info@reallists.u.washington.edu>; Tue, 16 Jul 2002 11:06:29 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 16 11:06:28 2002 -0700
Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6GI6SJX010415
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 11:06:28 -0700
Received: from pollux (pollux [129.252.130.113])
	by moultrie.cse.sc.edu (Postfix) with ESMTP id BB2391E4C4
	for <pine-info@u.washington.edu>; Tue, 16 Jul 2002 14:06:27 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207161304580.868-100000@pollux.cse.sc.edu>
Date: Tue, 16 Jul 2002 13:06:27 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 1399
In-Reply-To: <Pine.GSO.4.33.0207161052280.10511-100000@vax.hanford.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: gopalan@pollux.cse.sc.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 16 Jul 2002, Matt Ackeret wrote:

> Actually I wish there were a way to do something like:
>
> 1) select multiple messages through normal means
> 2) reply to both of them at once..

And it is so. Read Nancy's message yesterday.

-- 
Gopi Sundaram
gopalan@cse.sc.edu
http://www.cse.sc.edu/~gopalan/Pine/


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 17 Jul 2002 12:42:52 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6HJgp2P019600
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 17 Jul 2002 12:42:51 -0700
Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 17 12:42:51 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6HJgjoF026517
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 17 Jul 2002 12:42:46 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6HJfOR8015142;
	Wed, 17 Jul 2002 12:41:25 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6HJdTNn049850
	for <pine-info@reallists.u.washington.edu>; Wed, 17 Jul 2002 12:39:29 -0700
Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jul 17 12:39:29 2002 -0700
Received: from parvati.colorado.edu (parvati.Colorado.EDU [128.138.113.52])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6HJdSR8022863
	for <pine-info@u.washington.edu>; Wed, 17 Jul 2002 12:39:28 -0700
Received: from localhost (dorsey@localhost)
	by parvati.colorado.edu (8.11.6/8.11.2/ITS-5.0/standard) with ESMTP id g6HJdSl10198
	for <pine-info@u.washington.edu>; Wed, 17 Jul 2002 13:39:28 -0600 (MDT)
Message-Id: <Pine.GSO.4.44.0207171335430.9650-100000@parvati.colorado.edu>
Date: Wed, 17 Jul 2002 13:39:28 -0600 (MDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Susan Dorsey <dorsey@colorado.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Pine compression tool?
In-Reply-To: <Pine.GSO.4.44.0207161304580.868-100000@pollux.cse.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

A user is telling me she has in the past used some feature in Pine to
compress and move email messages, but doesn't remember how she did it.  I
can't find any commands in Pine which do this in the Help docs.  Does
anyone know of this feature?  Perhaps she was doing this at the command
line, but it seems unlikely...

Thanks,
Susan

Susan Dorsey
Information Technology Services		dorsey@colorado.edu
University of Colorado at Boulder 	303.492.4617


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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Jul 2002 09:24:29 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MGOT2P005401
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 22 Jul 2002 09:24:29 -0700
Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 22 09:24:28 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MGOOoF012364
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 22 Jul 2002 09:24:25 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MGMRqt024720;
	Mon, 22 Jul 2002 09:22:27 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MGJZeY034450
	for <pine-info@reallists.u.washington.edu>; Mon, 22 Jul 2002 09:19:35 -0700
Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 22 09:19:34 2002 -0700
Received: from msgdirector1.onetel.net.uk (msgdirector1.onetel.net.uk [212.67.96.148])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MGJXlq014932
	for <pine-info@u.washington.edu>; Mon, 22 Jul 2002 09:19:34 -0700
Received: from 213-78-75-121.friaco.onetel.net.uk (213-78-75-121.friaco.onetel.net.uk [213.78.75.121])
	by msgdirector1.onetel.net.uk (Mirapoint)
	with ESMTP id AIK82453;
	Mon, 22 Jul 2002 17:20:04 +0100 (BST)
Message-Id: <Pine.WNT.4.44.0207221712550.-815515@no>
Date: Mon, 22 Jul 2002 17:23:03 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Nancy McGough <nm-this-address-is-valid@no.sp.am>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: compiling pine for mac os x with ssl
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <pine-info@u.washington.edu>
X-Message-Flag: Worried about Outlook viruses? Switch to Mac/Unix/PC Pine! Info @ www.ii.com
X-X-Sender: ii@ii.best.vwh.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have been trying to compile pine for mac os x with ssl for over
a week and I'm finally giving up and asking for help. Could
someone please post step-by-step instructions for how to do this.
I think part of my problem is that I have downloaded and
installed Josh Larios procompiled pine for mac os x with ssl (and
it worked!) and I've also installed OpenSSL via the Mac OS X
latest upgrade and also via Fink. So I'm afraid that these 3 SSLs
are causing problems with each other (or at least Pine's build is
confused). Also, if it matters, I'm using the latest Mulberry
with SSL and so I have yet another set of Certs in the Mulberry
directory.

I can do a

 ./build osx

with no problem. It's just when I do

 ./build SSLDIR=/System/Library/OpenSSL osx

that it doesn't work.

My conclusion from all this frustration is that 1) not very many
people have compiled pine for mac os x with ssl and 2) this is
way to hard for normal human beings.

Thank you very much,
Nancy


-- 
       PROCMAIL  <http://www.ii.com/internet/robots/procmail/qs/>
           IMAP  <http://www.ii.com/internet/messaging/imap/isps/>
           PINE  <http://www.ii.com/internet/messaging/pine/>

--  I N F I N I T E  I N K    www.ii.com    N A N C Y  M c G O U G H  --


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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Jul 2002 14:18:47 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MLIl2P019952
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 22 Jul 2002 14:18:47 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 22 14:18:46 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MLIcoF022498
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 22 Jul 2002 14:18:39 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MLHaeo073550;
	Mon, 22 Jul 2002 14:17:36 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MLFgeY086926
	for <pine-info@reallists.u.washington.edu>; Mon, 22 Jul 2002 14:15:42 -0700
Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 22 14:15:42 2002 -0700
Received: from smtp.gospelcom.net (joppa.gospelcom.net [204.253.132.6])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MLFfbq005568
	for <pine-info@u.washington.edu>; Mon, 22 Jul 2002 14:15:41 -0700
Received: (qmail 2948 invoked from network); 22 Jul 2002 21:15:41 -0000
Received: from jabbok.gospelcom.net (HELO amos.gf.gospelcom.net) (204.253.132.4)
  by smtp.gospelcom.net with SMTP; 22 Jul 2002 21:15:41 -0000
Message-Id: <Pine.LNX.4.44.0207221711210.8410-100000@amos.gf.gospelcom.net>
Date: Mon, 22 Jul 2002 17:15:38 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Joel Boonstra <jboonstra@gospelcom.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: new mail notification : too long?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: joel@amos.gf.gospelcom.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hey folks,

I've had it quite a few times with pine 4.44 now that I get tricked into
thinking I have new mail, when I really don't.  Here's what happens:

I get new email.  Pine notifies me in the status line something like:

  New mail! From <someone> about <something I probably don't care about>

Something in the email piques my curiousity, and I go off to Galeon to
check it out.

When I come back (5 minutes later, give or take), the new mail
notification is still in the status line, even though I'm reading the
new mail that it's reporting, and opened it up 5 minutes ago.  Is this
expected behavior?  Shouldn't that notification disappear after a
certain time that's less than 5 minutes?

I don't remember this happening with previous versions, but I may be
forgetting.

Thanks!

-- 
[ joel boonstra | jboonstra@gospelcom.net ]

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Jul 2002 14:31:28 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MLVS2P020944
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 22 Jul 2002 14:31:28 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 22 14:31:27 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MLVQpB003044
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 22 Jul 2002 14:31:27 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MLUNlZ014790;
	Mon, 22 Jul 2002 14:30:23 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MLTOeY076776
	for <pine-info@reallists.u.washington.edu>; Mon, 22 Jul 2002 14:29:24 -0700
Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 22 14:29:24 2002 -0700
Received: from mail3.panix.com (mail3.panix.com [166.84.1.74])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MLTNR8017154
	for <pine-info@u.washington.edu>; Mon, 22 Jul 2002 14:29:23 -0700
Received: from eng-23.pacdigital (localhost.panix.com [127.0.0.1])
	by mail3.panix.com (Postfix) with ESMTP id 817C498208
	for <pine-info@u.washington.edu>; Mon, 22 Jul 2002 17:29:21 -0400 (EDT)
Message-Id: <Pine.LNX.4.44.0207221428390.1370-100000@eng-23.pacdigital>
Date: Mon, 22 Jul 2002 14:29:11 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kenneth Crudup <kenny@panix.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: new mail notification : too long?
In-Reply-To: <Pine.LNX.4.44.0207221711210.8410-100000@amos.gf.gospelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: kenny@eng-23.pacdigital
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 22 Jul 2002, Joel Boonstra wrote:

> Something in the email piques my curiousity, and I go off to Galeon to
> check it out.

Why would you use two MUAs?

	-Kenny, curious

-- 
Kenneth R. Crudup    Sr. SW Engineer, Scott County Consulting, Los Angeles, CA
Home:	4105 E. Willow St. #246, Long Beach, CA 90815-1740
Work:	2052 Alton Parkway, Irvine, CA 92606-4905	   (949) 252-1111 X240


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Jul 2002 18:44:58 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6N1iw2P028784
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 22 Jul 2002 18:44:58 -0700
Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 22 18:44:57 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6N1iupB010027
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 22 Jul 2002 18:44:57 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6N1huR8029316;
	Mon, 22 Jul 2002 18:43:56 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6N1gOeY058846
	for <pine-info@reallists.u.washington.edu>; Mon, 22 Jul 2002 18:42:24 -0700
Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 22 18:42:23 2002 -0700
Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6N1gNJY017209
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@lists.u.washington.edu>; Mon, 22 Jul 2002 18:42:23 -0700
Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18])
	by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6N1gNYu011935
	for <pine-info@u.washington.edu>; Mon, 22 Jul 2002 18:42:23 -0700
Received: FROM homer08.u.washington.edu BY mailscan-out3.cac.washington.edu ; Mon Jul 22 18:42:22 2002 -0700
Received: from localhost (jdlarios@localhost)
	by homer08.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g6N1gMDF163940;
	Mon, 22 Jul 2002 18:42:22 -0700
Message-Id: <Pine.A41.4.44.0207221837520.55506-100000@homer08.u.washington.edu>
Date: Mon, 22 Jul 2002 18:42:22 -0700 (PDT)
Reply-To: jdlarios@cac.washington.edu
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Josh Larios <jdlarios@cac.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: compiling pine for mac os x with ssl
In-Reply-To: <Pine.WNT.4.44.0207221712550.-815515@no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy McGough <nm-this-address-is-valid@no.sp.am>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: jdlarios@homer08.u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 22 Jul 2002, Nancy McGough wrote:

> I have been trying to compile pine for mac os x with ssl for over
> a week and I'm finally giving up and asking for help. Could

I took notes the last time I did this. They're now woefully out of date
(November of 2001) and I'm about to go through and do the whole thing over
again to see what's changed, but you're welcome to read what I've got
right now: http://staff.washington.edu/jdlarios/osx-pine-notes.html

I'll have new notes up for pine 4.44 and OS X 10.1.5 shortly. My problem
is that I'm never sure if the OS X powerbook I'm using has libraries and
headers installed that weren't part of the basic OS, so my instructions
work for me, but may not work for people who haven't added the same
things.

Anyway. I'll let you know when I've got a new version of that document.

--
Josh Larios                   Computing & Communications Client Services
University of Washington      Box 352830, Mary Gates Hall 011A
jdlarios@cac.washington.edu   Seattle, WA 98195-2830


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Jul 2002 02:05:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6N9592P005312
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 23 Jul 2002 02:05:09 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jul 23 02:05:07 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6N957pB018371
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 23 Jul 2002 02:05:07 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6N93rR8034230;
	Tue, 23 Jul 2002 02:03:53 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6N92peY066134
	for <pine-info@reallists.u.washington.edu>; Tue, 23 Jul 2002 02:02:51 -0700
Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jul 23 02:02:50 2002 -0700
Received: from msgdirector2.onetel.net.uk (msgdirector2.onetel.net.uk [212.67.96.149])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6N92nJX020798
	for <pine-info@u.washington.edu>; Tue, 23 Jul 2002 02:02:50 -0700
Received: from 213-78-69-234.friaco.onetel.net.uk (213-78-69-234.friaco.onetel.net.uk [213.78.69.234])
	by msgdirector2.onetel.net.uk (Mirapoint)
	with ESMTP id AIQ93662;
	Tue, 23 Jul 2002 10:02:16 +0100 (BST)
Message-Id: <Pine.WNT.4.44.0207230957001.-901777@no>
Date: Tue, 23 Jul 2002 10:06:08 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Nancy McGough <nm-this-address-is-valid@no.sp.am>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: compiling pine for mac os x with ssl
In-Reply-To: <Pine.A41.4.44.0207221837520.55506-100000@homer08.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <pine-info@u.washington.edu>
X-Message-Flag: Worried about Outlook viruses? Switch to Mac/Unix/PC Pine! Info @ www.ii.com
X-X-Sender: nancy@imap.iecc.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 22 Jul 2002 Josh Larios (jdlarios@cac.washington.edu) wrote:
> On Mon, 22 Jul 2002, Nancy McGough wrote:
>
> > I have been trying to compile pine for mac os x with ssl for over
> > a week and I'm finally giving up and asking for help. Could
>
> I took notes the last time I did this. They're now woefully out of date
> (November of 2001) and I'm about to go through and do the whole thing over
> again to see what's changed, but you're welcome to read what I've got
> right now: http://staff.washington.edu/jdlarios/osx-pine-notes.html

Thank you for those notes, which I had read before I posted my
plea for help. I link to them, and your page with Pine and SSL
packaged for OS X, on my main Pine page, in this section

 <http://www.ii.com/internet/messaging/pine/#osx>

You are the first in the list! Yours, and all the other pages in
that section, are ones I that I've used to try to figure out how
to compile it myself. If anyone knows any other Pine OS X pages,
please tell me.


> I'll have new notes up for pine 4.44 and OS X 10.1.5 shortly. My problem
> is that I'm never sure if the OS X powerbook I'm using has libraries and
> headers installed that weren't part of the basic OS, so my instructions
> work for me, but may not work for people who haven't added the same
> things.
>
> Anyway. I'll let you know when I've got a new version of that document.

That would be great. If you need someone to test your newly
compiled Pine or your new notes, I'd be happy to do that. It
would be great if you could compile in the option to use a
PASSFILE -- that is the main reason that I don't want to use the
version of Pine that's on your site.

Thanks again,
Nancy


-- 
       PROCMAIL  <http://www.ii.com/internet/robots/procmail/qs/>
           IMAP  <http://www.ii.com/internet/messaging/imap/isps/>
           PINE  <http://www.ii.com/internet/messaging/pine/>

--  I N F I N I T E  I N K    www.ii.com    N A N C Y  M c G O U G H  --


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Jul 2002 06:15:26 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6NDFP2P013513
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 23 Jul 2002 06:15:25 -0700
Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Jul 23 06:15:25 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6NDFOoF011062
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 23 Jul 2002 06:15:25 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6NDEclZ014788;
	Tue, 23 Jul 2002 06:14:39 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6NDDPeY100860
	for <pine-info@reallists.u.washington.edu>; Tue, 23 Jul 2002 06:13:25 -0700
Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Jul 23 06:13:24 2002 -0700
Received: from smtp.gospelcom.net (joppa.gospelcom.net [204.253.132.6])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6NDDOlq008840
	for <pine-info@u.washington.edu>; Tue, 23 Jul 2002 06:13:24 -0700
Received: (qmail 2310 invoked from network); 23 Jul 2002 13:13:23 -0000
Received: from jabbok.gospelcom.net (HELO amos.gf.gospelcom.net) (204.253.132.4)
  by smtp.gospelcom.net with SMTP; 23 Jul 2002 13:13:23 -0000
Message-Id: <Pine.LNX.4.44.0207230911150.922-100000@amos.gf.gospelcom.net>
Date: Tue, 23 Jul 2002 09:13:21 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Joel Boonstra <jboonstra@gospelcom.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: new mail notification : too long?
In-Reply-To: <Pine.LNX.4.44.0207221428390.1370-100000@eng-23.pacdigital>
References: <Pine.LNX.4.44.0207221428390.1370-100000@eng-23.pacdigital>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Kenneth Crudup <kenny@panix.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: joel@amos.gf.gospelcom.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> > Something in the email piques my curiousity, and I go off to Galeon to
> > check it out.
>
> Why would you use two MUAs?

Galeon is my web browser (http://galeon.sf.net/).  When I say something
'piques my curiousity', that means that there some URL or whatever that
I want to read up on, so I switch over to another app (and usually
another desktop) for awhile.

Sorry for being unclear -- I was trying to get across that I leave the
email open for potentially awhile, and when get around to reading email
again, the new mail notification is still there, even though the mail
has been open for awhile.

Does that clear things up?

-- 
[ joel boonstra | jboonstra@gospelcom.net ]


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Jul 2002 20:38:35 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6O3cY2P021279
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 23 Jul 2002 20:38:34 -0700
Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Jul 23 20:38:34 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6O3cSpB020250
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 23 Jul 2002 20:38:29 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6O3YllZ025326;
	Tue, 23 Jul 2002 20:34:47 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6O3WfeY049558
	for <pine-info@reallists.u.washington.edu>; Tue, 23 Jul 2002 20:32:42 -0700
Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Jul 23 20:32:41 2002 -0700
Received: from mand.kreorg.hu (mand.kreorg.hu [193.110.58.16])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6O3Wcbq010214
	for <pine-info@u.washington.edu>; Tue, 23 Jul 2002 20:32:39 -0700
Received: from localhost (kreorg@localhost)
	by mand.kreorg.hu (8.11.2/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id g6O3NXI13310
	for <pine-info@u.washington.edu>; Wed, 24 Jul 2002 03:23:33 GMT
Message-Id: <Pine.LNX.4.33.0207240318160.13234-100000@mand.kreorg.hu>
Date: Wed, 24 Jul 2002 03:23:33 +0000 (/etc/localtime)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: <kreorg@kreorg.hu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: please advice 
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN




Hi List,
I wish sending previousle written emails to some people. I would like to
send them at various intervals. Can this process be done by Pine automated
by cron?
Pine should automatically insert text into message body from a subdir when
cron prompts for it.
Addresses should be witten into the Bcc field, the To is myself
Thanks
Kreorg





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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Jul 2002 11:08:30 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6OI8U2P021001
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 24 Jul 2002 11:08:30 -0700
Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 24 11:08:24 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OI8NoF029977
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 24 Jul 2002 11:08:23 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OI7JR8029338;
	Wed, 24 Jul 2002 11:07:19 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OI53eY078750
	for <pine-info@reallists.u.washington.edu>; Wed, 24 Jul 2002 11:05:03 -0700
Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jul 24 11:05:02 2002 -0700
Received: from Ra-Hoor.Aeon-AL.Net (dsl-63-249-19-72.zipcon.net [63.249.19.72])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OI50bq012266
	for <Pine-Info@U.Washington.EDU>; Wed, 24 Jul 2002 11:05:01 -0700
Received: from localhost (localhost [127.0.0.1])
	by Ra-Hoor.Aeon-AL.Net (8.11.6/8.11.6) with ESMTP id g6OI4NR07015
	for <Pine-Info@U.Washington.EDU>; Wed, 24 Jul 2002 11:04:23 -0700
Message-Id: <Pine.LNX.4.44.0207241100330.6215-100000@Ra-Hoor.Aeon-AL.Net>
Date: Wed, 24 Jul 2002 11:04:23 -0700 (PDT)
Reply-To: Meph Istophelse <Meph@Aeon-AL.Com>
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Meph Istopheles <meph@Aeon-AL.Com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Page Down key going to next message
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: meph@Ra-Hoor.Aeon-AL.Net
X-To: Pine <Pine-Info@U.Washington.EDU>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

  Hey,

  Can't find anything on this, but suspect it must be one of the 
features I've chosen.  I have something turned on in pine 4.44 
in RedHat 7.2.  which, when I've scrolled down near the end of a 
post & hit the Page Down key, I'm brought to the next message.  
I'd like it to just to to the end of the current message, but 
hope I won't have to lose the use of the Page Down key to do it.

  Is that a setting?  If so, which ~is~ it?

  Meph

--
  What!?  Me worry?
  -Alfred E Newman

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Jul 2002 11:22:17 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6OIMH2P021609
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 24 Jul 2002 11:22:17 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 24 11:22:16 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OIMFoF030504
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 24 Jul 2002 11:22:16 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OILCeo090176;
	Wed, 24 Jul 2002 11:21:12 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OIDNeY089914
	for <pine-info@reallists.u.washington.edu>; Wed, 24 Jul 2002 11:13:23 -0700
Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jul 24 11:13:22 2002 -0700
Received: from bp02.u.washington.edu (bp02.u.washington.edu [140.142.15.12])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OIDMbr015040
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@lists.u.washington.edu>; Wed, 24 Jul 2002 11:13:22 -0700
Received: from lisa-9h0z9d2lo0 (D-128-208-83-168.dhcp.washington.edu [128.208.83.168])
	by bp02.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g6OIDLZh228084;
	Wed, 24 Jul 2002 11:13:21 -0700
Message-Id: <Pine.CYG.4.44.0207241111460.876-100000@lisa-9h0z9d2lo0>
Date: Wed, 24 Jul 2002 11:13:34 -0700
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Page Down key going to next message
In-Reply-To: <Pine.LNX.4.44.0207241100330.6215-100000@Ra-Hoor.Aeon-AL.Net>
References: <Pine.LNX.4.44.0207241100330.6215-100000@Ra-Hoor.Aeon-AL.Net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: chappa@lisa-9h0z9d2lo0
X-To: Meph Istopheles <meph@Aeon-AL.Com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Meph Istopheles (meph@Aeon-AL.Com) wrote in the pine-info list today:

:)   Can't find anything on this, but suspect it must be one of the
:) features I've chosen.  I have something turned on in pine 4.44 in
:) RedHat 7.2.  which, when I've scrolled down near the end of a post &
:) hit the Page Down key, I'm brought to the next message.  I'd like it to
:) just to to the end of the current message, but hope I won't have to
:) lose the use of the Page Down key to do it.

You must disable [ ] enable-cruise-mode in your configuration screen.

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


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 11:51:54 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PIps2P001212
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 11:51:54 -0700
Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 25 11:51:52 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PIpmpB014206
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 11:51:49 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PIoaeo075982;
	Thu, 25 Jul 2002 11:50:36 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PIm4eY050854
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 11:48:04 -0700
Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 25 11:48:03 2002 -0700
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PIm3R8020583
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 11:48:03 -0700
Received: (qmail 29960 invoked by uid 1828); 25 Jul 2002 18:48:02 -0000
Message-Id: <Pine.GSO.4.33.0207251143590.9259-100000@vax.hanford.org>
Date: Thu, 25 Jul 2002 11:48:02 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Matt Ackeret <mattack@area.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: page down
In-Reply-To: <200207250728.g6P7Soeo076652@list4.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender:  <mattack@vax.hanford.org>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 25 Jul 2002 pine-info@u.washington.edu wrote:
>*** Meph Istopheles (meph@Aeon-AL.Com) wrote in the pine-info list today:
>
>:)   Can't find anything on this, but suspect it must be one of the
>:) features I've chosen.  I have something turned on in pine 4.44 in
>:) RedHat 7.2.  which, when I've scrolled down near the end of a post &
>:) hit the Page Down key, I'm brought to the next message.  I'd like it to
>:) just to to the end of the current message, but hope I won't have to
>:) lose the use of the Page Down key to do it.
>
>You must disable [ ] enable-cruise-mode in your configuration screen.

This reminds me of something else that slightly bugs me about pine.

I wish there were some threshhold past which page-down would
not actually cause most of the screen to be blank when you paged down at
the end of a message.

This is HIGHLY subjective so I know not everyone would like it, and that's
also why I mention a threshhold, because there are cases where I wouldn't
like it either.

What I'm talking about is this..

If you're 95% through a message, and hit space, it pages down and you end
up with 2 lines at the top of the screen and the rest a blank screen.

I'm not sure what the threshhold should be, that's why I suggest it be
configurable.

A total absolute guess is -- if the screen will be less than 1/3 full,
then just scroll down to the bottom and leave the other 2/3 of the same
page visible.

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 12:48:40 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PJme2P003504
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 12:48:40 -0700
Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Jul 25 12:48:39 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PJmZpB015854
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 12:48:36 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PJkilZ017318;
	Thu, 25 Jul 2002 12:46:44 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PJjVeY012234
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 12:45:31 -0700
Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Jul 25 12:45:30 2002 -0700
Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PJjUlq029782
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 12:45:30 -0700
Received: from pollux (pollux [129.252.130.113])
	by moultrie.cse.sc.edu (Postfix) with ESMTP id F24621E4C2
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 15:45:29 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207251441270.11909-100000@pollux.cse.sc.edu>
Date: Thu, 25 Jul 2002 14:45:29 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: page down
In-Reply-To: <Pine.GSO.4.33.0207251143590.9259-100000@vax.hanford.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: gopalan@pollux.cse.sc.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 25 Jul 2002, Matt Ackeret wrote:

> A total absolute guess is -- if the screen will be less than 1/3 full,
> then just scroll down to the bottom and leave the other 2/3 of the same
> page visible.

And what about the massive number of blank lines that may follow a
message? Do they count as part of a blank screen? What if there are 511
characters on a single line, and you have word-wrapping? Or what if
those characters are whitespace?

-- 
Gopi Sundaram
gopalan@cse.sc.edu
http://www.cse.sc.edu/~gopalan/Pine/


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 12:54:38 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PJsb2P003733
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 12:54:37 -0700
Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Jul 25 12:54:36 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PJsapB016025
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 12:54:36 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PJrkqt024640;
	Thu, 25 Jul 2002 12:53:46 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PJr8eY074168
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 12:53:08 -0700
Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 12:53:07 2002 -0700
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PJr7bq008890
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 12:53:07 -0700
Received: from venus.geneseo.edu (venus.geneseo.edu [137.238.1.102])
	by helios.geneseo.edu (8.12.5/8.12.5) with ESMTP id g6PJqrB9006721
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 15:52:53 -0400 (EDT)
Received: from venus.geneseo.edu (localhost.localdomain [127.0.0.1])
	by venus.geneseo.edu (8.12.5/8.12.5) with ESMTP id g6PJqmkx023562
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 15:52:48 -0400
Received: from localhost (valites@localhost)
	by venus.geneseo.edu (8.12.5/8.12.1/Submit) with ESMTP id g6PJqmBB023559
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 15:52:48 -0400
Message-Id: <Pine.LNX.4.44.0207251538040.13987-100000@venus.geneseo.edu>
Date: Thu, 25 Jul 2002 15:52:48 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Mark T. Valites" <valites@geneseo.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: pine-interrupted-mail with pine as imap client
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

After way way too many hours spent at work this weekend, I took the whole
campus to Maildir format.  I also set up pine to be an imap client to
localhost since I didn't like any of the unofficial patches.

For the most part, there have been very few complaints or problems.  One
complaint that I'd like to fix is that the .pine-interrupted-mail gets
created when a user's connection dies (or elsewise), but it doesn't get
read when pine starts back up.  Anyway to make pine look for this file
again?

And secondly, I've noticed some odd behavior with directories.  I can no
longer hit enter to enter a directory, but have to hit "." to enter it.
Any way to make enter work again?  Also, I cannot create directories in
pine with add(a), create directory(cntrl-x).  It appears to work, but
actually does nothing - ideas?

Lastly, I don't seem to be able to enter a folder with ">" anymore.  I
personally have always just hit enter to enter a folder, but some of my
users are (for once) used to following the directions at the bottom of the
screen & hitting ">".  Can I make this behaviour return also?

Other than that, pine has been working well as an imap client.  Users
haven't compained *too* much about the password prompt & I've been able to
lock it down well with my pine.conf.fixed.

Thanks in advance.
-Mark

>--))> >--))>
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
SUNY Geneseo
Geneseo, NY 14454
585-245-5577
585-259-3471 (Cell)
585-245-5579 (Fax)

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 15:12:43 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PMCg2P008862
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 15:12:43 -0700
Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 25 15:12:42 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PMCfpB020082
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 15:12:42 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PMBhlZ015174;
	Thu, 25 Jul 2002 15:11:43 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PM9oeY011908
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 15:09:50 -0700
Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 25 15:09:50 2002 -0700
Received: from ic.ucsb.edu (ic.ucsb.edu [128.111.151.230])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PM9nR9010757
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 15:09:50 -0700
Received: from office-internal.ic.ucsb.edu ([128.111.151.1] helo=ic.ucsb.edu)
	by ic.ucsb.edu with esmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #2)
	id 17Xqnt-000LeX-00
	for pine-info@u.washington.edu; Thu, 25 Jul 2002 15:09:49 -0700
Message-Id: <3D40772D.1040106@ic.ucsb.edu>
Date: Thu, 25 Jul 2002 15:09:49 -0700
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Lopaka Delp <lopaka@ic.ucsb.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: MySQL and pine
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Accept-Language: en-us, en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello all,

I've been trying to get pine to look into a mysql database to get users 
password instead of using the PASSFILE.  It all compiles great, but once 
I run it, it give a SIGSEGV when it calls mysql_init().

It's been driving me nuts for 6 days.  Can anyone help?  Or even direct 
me where I can get help on this?

Some info: gdb gives this:
Program received signal SIGSEGV, Segmentation fault.
0xff2dd3c0 in convert_dirname ()
    from /usr/local/services/mysql/lib/mysql/libmysqlclient.so.10


Thanks

             --> Lopaka
-- 
   Lopaka K. Delp                e-mail:  lopaka@ic.ucsb.edu
   UNIX Systems Administrator    phone :  (805)893-4561
   Instructional Computing
   University of California,     WWW   :  http://www.ic.ucsb.edu/~lopaka
      Santa Barbara

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 16:24:01 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PNO12P011437
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 16:24:01 -0700
Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 25 16:24:00 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PNNuoF011103
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 16:23:56 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PNN8R8028020;
	Thu, 25 Jul 2002 16:23:08 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PNLPeY011874
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 16:21:25 -0700
Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jul 25 16:21:25 2002 -0700
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PNLPR8030471
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 16:21:25 -0700
Received: from goedel3.math.washington.edu (goedel3.math.washington.edu [128.95.224.12])
	by euler.math.washington.edu (8.11.6/8.11.6) with ESMTP id g6PNLNZ44958;
	Thu, 25 Jul 2002 16:21:23 -0700 (PDT)
Message-Id: <Pine.OSF.4.44.0207251613040.429730-100000@goedel3.math.washington.edu>
Date: Thu, 25 Jul 2002 16:21:23 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: page down
In-Reply-To: <Pine.GSO.4.44.0207251441270.11909-100000@pollux.cse.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Gopi Sundaram <gopalan@cs.sc.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Gopi Sundaram (gopalan@cs.sc.edu) wrote in the pine-info list today:

:) On Thu, 25 Jul 2002, Matt Ackeret wrote:
:)
:) > A total absolute guess is -- if the screen will be less than 1/3
:) > full, then just scroll down to the bottom and leave the other 2/3 of
:) > the same page visible.
:)
:) And what about the massive number of blank lines that may follow a
:) message? Do they count as part of a blank screen? What if there are 511
:) characters on a single line, and you have word-wrapping? Or what if
:) those characters are whitespace?

Actually Pine knows how many lines it is going to display at any time. I
have also been bothered by that type of behavior before, and there's a
simple modification (in the source code) that one can do to fix this.

Look at the function scrolltool in the file pine/mailview.c and look for
the command "MC_PAGEDN". Pine computes how many lines to scroll, and saves
that information in the "scroll_lines" variable. All you need to do, is to
make Pine recompute it again. Add the following line before the line
"cur_top_line += scroll_lines;" (do not delete anything)

                scroll_lines = min(scroll_lines, scroll_text_lines() -
                                scroll_lines - cur_top_line);

That seems to work fine for me.

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



From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 17:19:30 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q0JU2P013314
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 17:19:30 -0700
Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 25 17:19:29 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q0JSpB024221
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 17:19:28 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q0IqR8019794;
	Thu, 25 Jul 2002 17:18:52 -0700
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q0HveY076012
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 17:17:57 -0700
Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Jul 25 17:17:57 2002 -0700
Received: from mail3.panix.com (mail3.panix.com [166.84.1.74])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q0HuJX017922
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 17:17:56 -0700
Received: from eng-23.pacdigital (localhost.panix.com [127.0.0.1])
	by mail3.panix.com (Postfix) with ESMTP id 5CB22982AF
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:17:55 -0400 (EDT)
Message-Id: <Pine.LNX.4.44.0207251717350.1386-100000@eng-23.pacdigital>
Date: Thu, 25 Jul 2002 17:17:50 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Kenneth Crudup <kenny@panix.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: page down
In-Reply-To: <Pine.OSF.4.44.0207251613040.429730-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: kenny@eng-23.pacdigital
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 25 Jul 2002, Eduardo Chappa wrote:

> That seems to work fine for me.

Thanks.

	-Kenny

-- 
Kenneth R. Crudup    Sr. SW Engineer, Scott County Consulting, Los Angeles, CA
Home:	4105 E. Willow St. #246, Long Beach, CA 90815-1740
Work:	2052 Alton Parkway, Irvine, CA 92606-4905	   (949) 252-1111 X240


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 20:14:15 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q3EF2P016881
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 20:14:15 -0700
Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Jul 25 20:14:14 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3EDpB027894
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 20:14:14 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3CNqt019344;
	Thu, 25 Jul 2002 20:12:23 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3AteY042344
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 20:10:55 -0700
Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jul 25 20:10:55 2002 -0700
Received: from itsa.ucsf.edu (itsa.ucsf.edu [128.218.95.21])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3Asbq013716
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:10:55 -0700
Received: from localhost (joed@localhost) by itsa.ucsf.edu (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA97440 for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:10:54 -0700
Message-Id: <Pine.A41.4.44.0207251938560.100736-100000@itsa.ucsf.edu>
Date: Thu, 25 Jul 2002 20:10:54 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Joe DeBattista <joed@itsa.ucsf.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Passwordless key-based ssh2 authentication
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Greetings,
  I'm in the process of setting up IMAP to work with Pine 4.44 on my
client server.  Everything works fine, except that I'd like to be able to
not require my users to give a login and password to get to the IMAP
server.  I found the posting for ssh at
http://www.washington.edu/pine/pine-info/1999.12/msg00170.html
but I haven't had any luck doing the equivalent steps under SSH2.

Here's what I tried:
Under a user login, I ran ssh-keygen on the client machine, leaving the
passphrase blank. It created the private key as ~user/.ssh2/id_dsa_1024_a
and the public key as ~user/.ssh2/id_dsa_1024_a.pub

I ftp'ed the id_dsa_1024_a.pub to the IMAP server and placed it  under
~user/.ssh2/hostkeys/key_22_clientmachine.pub

According to the posting, from the client machine, I should be able to
type
  ssh (I'm trying ssh2) my.imap.server
and connect without being asked for a password, but it continues to query
me for the password.

Any help will be greatly appreciated.


                                 Joe DeBattista
                                 UCSF, ITS
                      INTERNET:  joed@itsa.ucsf.edu

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 20:19:12 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q3JC2P016990
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 20:19:12 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 20:19:11 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3J8oF016592
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 20:19:08 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3HVlZ015322;
	Thu, 25 Jul 2002 20:17:31 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3H0eY007664
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 20:17:00 -0700
Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 25 20:17:00 2002 -0700
Received: from nimbus.anzio.com (nimbus.anzio.com [66.129.212.98])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3H0JX019100
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:17:00 -0700
Received: from nimbus.anzio.com (nimbus.anzio.com [66.129.212.98])
	by nimbus.anzio.com (8.12.3/8.12.3) with ESMTP id g6Q2xjeJ015751;
	Thu, 25 Jul 2002 19:59:45 -0700
Message-Id: <Pine.LNX.4.42.0207251957490.15745-100000@nimbus.anzio.com>
Date: Thu, 25 Jul 2002 19:59:45 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bob Rasmussen <ras@anzio.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Passwordless key-based ssh2 authentication
In-Reply-To: <Pine.A41.4.44.0207251938560.100736-100000@itsa.ucsf.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Joe DeBattista <joed@itsa.ucsf.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 25 Jul 2002, Joe DeBattista wrote:

> Greetings,
>   I'm in the process of setting up IMAP to work with Pine 4.44 on my
> client server.  Everything works fine, except that I'd like to be able to
> not require my users to give a login and password to get to the IMAP
> server.  I found the posting for ssh at
> http://www.washington.edu/pine/pine-info/1999.12/msg00170.html
> but I haven't had any luck doing the equivalent steps under SSH2.
>
> Here's what I tried:
> Under a user login, I ran ssh-keygen on the client machine, leaving the
> passphrase blank. It created the private key as ~user/.ssh2/id_dsa_1024_a
> and the public key as ~user/.ssh2/id_dsa_1024_a.pub
>
> I ftp'ed the id_dsa_1024_a.pub to the IMAP server and placed it  under
> ~user/.ssh2/hostkeys/key_22_clientmachine.pub
>
> According to the posting, from the client machine, I should be able to
> type
>   ssh (I'm trying ssh2) my.imap.server
> and connect without being asked for a password, but it continues to query
> me for the password.

First, try running your ssh client with its debugging and/or logging turned
on, you can learn a lot that way.

Second, note that it is possible that the server's sshd is configured to
require both a public key and a password. Again, you'll get a glimpse of this
with the debugging output of your client.

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

personal e-mail: ras@anzio.com
 company e-mail: rsi@anzio.com
          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
            fax: (US) 503-624-0760
            web: http://www.anzio.com


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 20:29:11 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q3TB2P017170
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 20:29:11 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 20:29:09 2002 -0700
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3T6oF016743
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 20:29:07 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3RGeo095798;
	Thu, 25 Jul 2002 20:27:16 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3QCeY007644
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 20:26:12 -0700
Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jul 25 20:26:11 2002 -0700
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3QBlq002155
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:26:11 -0700
Received: from venus.geneseo.edu (venus.geneseo.edu [137.238.1.102])
	by helios.geneseo.edu (8.12.5/8.12.5) with ESMTP id g6Q3Q3B9021046;
	Thu, 25 Jul 2002 23:26:03 -0400 (EDT)
Received: from venus.geneseo.edu (localhost.localdomain [127.0.0.1])
	by venus.geneseo.edu (8.12.5/8.12.5) with ESMTP id g6Q3Pvkx031741;
	Thu, 25 Jul 2002 23:25:57 -0400
Received: from localhost (valites@localhost)
	by venus.geneseo.edu (8.12.5/8.12.1/Submit) with ESMTP id g6Q3Pv1G031738;
	Thu, 25 Jul 2002 23:25:57 -0400
Message-Id: <Pine.LNX.4.44.0207252320540.31262-100000@venus.geneseo.edu>
Date: Thu, 25 Jul 2002 23:25:57 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Mark T. Valites" <valites@geneseo.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Passwordless key-based ssh2 authentication
In-Reply-To: <Pine.A41.4.44.0207251938560.100736-100000@itsa.ucsf.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Joe DeBattista <joed@itsa.ucsf.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Joe,

You need to concatonate the public key onto a file called authorized_keys2
in the .ssh directory (or different depending on the ssh version you're
running....).  It doesn't explicity say how to do it, but it does
say you need to in the link you posted.  You can do this to make it work:

cat some_pub_key >> ~/.ssh/authorized_keys2

Check the permissions on all the ssh files though!  ssh is picky (for good
reason about the perms).  ssh -v -v -v won't pick up this problem for you,
but tailing the logs on the sshd machine will.

Once that works, the passworless ssh imapping to preauth'd imapd works
without any problem.

Now if only I could get this to go with the courier imap preauth imapd...

On Thu, 25 Jul 2002, Joe DeBattista wrote:

> Greetings,
>   I'm in the process of setting up IMAP to work with Pine 4.44 on my
> client server.  Everything works fine, except that I'd like to be able to
> not require my users to give a login and password to get to the IMAP
> server.  I found the posting for ssh at
> http://www.washington.edu/pine/pine-info/1999.12/msg00170.html
> but I haven't had any luck doing the equivalent steps under SSH2.
>
> Here's what I tried:
> Under a user login, I ran ssh-keygen on the client machine, leaving the
> passphrase blank. It created the private key as ~user/.ssh2/id_dsa_1024_a
> and the public key as ~user/.ssh2/id_dsa_1024_a.pub
>
> I ftp'ed the id_dsa_1024_a.pub to the IMAP server and placed it  under
> ~user/.ssh2/hostkeys/key_22_clientmachine.pub
>
> According to the posting, from the client machine, I should be able to
> type
>   ssh (I'm trying ssh2) my.imap.server
> and connect without being asked for a password, but it continues to query
> me for the password.
>
> Any help will be greatly appreciated.
>
>
>                                  Joe DeBattista
>                                  UCSF, ITS
>                       INTERNET:  joed@itsa.ucsf.edu
>
> --
> -----------------------------------------------------------------
>  For information about this mailing list, and its archives, see:
>  http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>
>

>--))> >--))>
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
SUNY Geneseo
Geneseo, NY 14454
585-245-5577
585-259-3471 (Cell)
585-245-5579 (Fax)


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 20:55:21 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q3tL2P017601
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 20:55:21 -0700
Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 25 20:55:20 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3tJpB028609
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 20:55:20 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3rIR8028142;
	Thu, 25 Jul 2002 20:53:19 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3qSeY102732
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 20:52:28 -0700
Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 25 20:52:28 2002 -0700
Received: from itsa.ucsf.edu (itsa.ucsf.edu [128.218.95.21])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3qRlq005433
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:52:28 -0700
Received: from localhost (joed@localhost) by itsa.ucsf.edu (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA99912; Thu, 25 Jul 2002 20:52:19 -0700
Message-Id: <Pine.A41.4.44.0207252051430.100736-100000@itsa.ucsf.edu>
Date: Thu, 25 Jul 2002 20:52:19 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Joe DeBattista <joed@itsa.ucsf.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Passwordless key-based ssh2 authentication
In-Reply-To: <Pine.LNX.4.44.0207252320540.31262-100000@venus.geneseo.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Mark T. Valites" <valites@geneseo.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Does it still use the authorized_keys file with ssh2?


                                 Joe DeBattista
                                 UCSF, ITS
                      INTERNET:  joed@itsa.ucsf.edu

On Thu, 25 Jul 2002, Mark T. Valites wrote:

> Joe,
>
> You need to concatonate the public key onto a file called authorized_keys2
> in the .ssh directory (or different depending on the ssh version you're
> running....).  It doesn't explicity say how to do it, but it does
> say you need to in the link you posted.  You can do this to make it work:
>
> cat some_pub_key >> ~/.ssh/authorized_keys2
>
> Check the permissions on all the ssh files though!  ssh is picky (for good
> reason about the perms).  ssh -v -v -v won't pick up this problem for you,
> but tailing the logs on the sshd machine will.
>
> Once that works, the passworless ssh imapping to preauth'd imapd works
> without any problem.
>
> Now if only I could get this to go with the courier imap preauth imapd...
>
> On Thu, 25 Jul 2002, Joe DeBattista wrote:
>
> > Greetings,
> >   I'm in the process of setting up IMAP to work with Pine 4.44 on my
> > client server.  Everything works fine, except that I'd like to be able to
> > not require my users to give a login and password to get to the IMAP
> > server.  I found the posting for ssh at
> > http://www.washington.edu/pine/pine-info/1999.12/msg00170.html
> > but I haven't had any luck doing the equivalent steps under SSH2.
> >
> > Here's what I tried:
> > Under a user login, I ran ssh-keygen on the client machine, leaving the
> > passphrase blank. It created the private key as ~user/.ssh2/id_dsa_1024_a
> > and the public key as ~user/.ssh2/id_dsa_1024_a.pub
> >
> > I ftp'ed the id_dsa_1024_a.pub to the IMAP server and placed it  under
> > ~user/.ssh2/hostkeys/key_22_clientmachine.pub
> >
> > According to the posting, from the client machine, I should be able to
> > type
> >   ssh (I'm trying ssh2) my.imap.server
> > and connect without being asked for a password, but it continues to query
> > me for the password.
> >
> > Any help will be greatly appreciated.
> >
> >
> >                                  Joe DeBattista
> >                                  UCSF, ITS
> >                       INTERNET:  joed@itsa.ucsf.edu
> >
> > --
> > -----------------------------------------------------------------
> >  For information about this mailing list, and its archives, see:
> >  http://www.washington.edu/pine/pine-info/
> > -----------------------------------------------------------------
> >
> >
>
> >--))> >--))>
> Mark T. Valites
> Unix Systems Analyst
> 1 College Circle - 124b1 South Hall
> SUNY Geneseo
> Geneseo, NY 14454
> 585-245-5577
> 585-259-3471 (Cell)
> 585-245-5579 (Fax)
>
>


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Jul 2002 20:57:05 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q3v52P017669
	for <mailarch+pine-info@groupms.cac.washington.edu>; Thu, 25 Jul 2002 20:57:05 -0700
Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 20:57:05 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3v2pB028637
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 25 Jul 2002 20:57:02 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3uMR8034710;
	Thu, 25 Jul 2002 20:56:22 -0700
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q3toeY092422
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 20:55:50 -0700
Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jul 25 20:55:50 2002 -0700
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q3tnJX024092
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 20:55:49 -0700
Received: from venus.geneseo.edu (venus.geneseo.edu [137.238.1.102])
	by helios.geneseo.edu (8.12.5/8.12.5) with ESMTP id g6Q3tjB9025562;
	Thu, 25 Jul 2002 23:55:45 -0400 (EDT)
Received: from venus.geneseo.edu (localhost.localdomain [127.0.0.1])
	by venus.geneseo.edu (8.12.5/8.12.5) with ESMTP id g6Q3tckx002541;
	Thu, 25 Jul 2002 23:55:38 -0400
Received: from localhost (valites@localhost)
	by venus.geneseo.edu (8.12.5/8.12.1/Submit) with ESMTP id g6Q3tc06002538;
	Thu, 25 Jul 2002 23:55:38 -0400
Message-Id: <Pine.LNX.4.44.0207252352580.31262-100000@venus.geneseo.edu>
Date: Thu, 25 Jul 2002 23:55:38 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Mark T. Valites" <valites@geneseo.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Passwordless key-based ssh2 authentication
In-Reply-To: <Pine.A41.4.44.0207252051430.100736-100000@itsa.ucsf.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Joe DeBattista <joed@itsa.ucsf.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

authorized_keys2 with openssh2.  I'm not sure about commercial ssh2 off
hand.  ssh, the Definitice Guide from O'Reilly has it in there.
Unfortuneatly, it's at work & I'm not...  I think commercial ssh uses
authorized_keys.  There's only two, so try I guess...

On Thu, 25 Jul 2002, Joe DeBattista wrote:

> Does it still use the authorized_keys file with ssh2?
>
>
>                                  Joe DeBattista
>                                  UCSF, ITS
>                       INTERNET:  joed@itsa.ucsf.edu
>
> On Thu, 25 Jul 2002, Mark T. Valites wrote:
>
> > Joe,
> >
> > You need to concatonate the public key onto a file called authorized_keys2
> > in the .ssh directory (or different depending on the ssh version you're
> > running....).  It doesn't explicity say how to do it, but it does
> > say you need to in the link you posted.  You can do this to make it work:
> >
> > cat some_pub_key >> ~/.ssh/authorized_keys2
> >
> > Check the permissions on all the ssh files though!  ssh is picky (for good
> > reason about the perms).  ssh -v -v -v won't pick up this problem for you,
> > but tailing the logs on the sshd machine will.
> >
> > Once that works, the passworless ssh imapping to preauth'd imapd works
> > without any problem.
> >
> > Now if only I could get this to go with the courier imap preauth imapd...
> >
> > On Thu, 25 Jul 2002, Joe DeBattista wrote:
> >
> > > Greetings,
> > >   I'm in the process of setting up IMAP to work with Pine 4.44 on my
> > > client server.  Everything works fine, except that I'd like to be able to
> > > not require my users to give a login and password to get to the IMAP
> > > server.  I found the posting for ssh at
> > > http://www.washington.edu/pine/pine-info/1999.12/msg00170.html
> > > but I haven't had any luck doing the equivalent steps under SSH2.
> > >
> > > Here's what I tried:
> > > Under a user login, I ran ssh-keygen on the client machine, leaving the
> > > passphrase blank. It created the private key as ~user/.ssh2/id_dsa_1024_a
> > > and the public key as ~user/.ssh2/id_dsa_1024_a.pub
> > >
> > > I ftp'ed the id_dsa_1024_a.pub to the IMAP server and placed it  under
> > > ~user/.ssh2/hostkeys/key_22_clientmachine.pub
> > >
> > > According to the posting, from the client machine, I should be able to
> > > type
> > >   ssh (I'm trying ssh2) my.imap.server
> > > and connect without being asked for a password, but it continues to query
> > > me for the password.
> > >
> > > Any help will be greatly appreciated.
> > >
> > >
> > >                                  Joe DeBattista
> > >                                  UCSF, ITS
> > >                       INTERNET:  joed@itsa.ucsf.edu
> > >
> > > --
> > > -----------------------------------------------------------------
> > >  For information about this mailing list, and its archives, see:
> > >  http://www.washington.edu/pine/pine-info/
> > > -----------------------------------------------------------------
> > >
> > >
> >
> > >--))> >--))>
> > Mark T. Valites
> > Unix Systems Analyst
> > 1 College Circle - 124b1 South Hall
> > SUNY Geneseo
> > Geneseo, NY 14454
> > 585-245-5577
> > 585-259-3471 (Cell)
> > 585-245-5579 (Fax)
> >
> >
>
>

>--))> >--))>
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
SUNY Geneseo
Geneseo, NY 14454
585-245-5577
585-259-3471 (Cell)
585-245-5579 (Fax)


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 26 Jul 2002 00:01:54 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6Q71s2P021842
	for <mailarch+pine-info@groupms.cac.washington.edu>; Fri, 26 Jul 2002 00:01:54 -0700
Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Jul 26 00:01:52 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q71qoF020805
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 26 Jul 2002 00:01:52 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q6uYlZ010384;
	Thu, 25 Jul 2002 23:56:34 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6Q6sgeY092494
	for <pine-info@reallists.u.washington.edu>; Thu, 25 Jul 2002 23:54:42 -0700
Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 23:54:41 2002 -0700
Received: from plum.flirble.org (plum.flirble.org [195.40.6.20])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6Q6seJX014865
	for <pine-info@u.washington.edu>; Thu, 25 Jul 2002 23:54:41 -0700
Received: from scot (helo=localhost)
	by plum.flirble.org with local-esmtp (Exim 3.20 #3)
	id 17Xyzn-000PPB-00
	for pine-info@u.washington.edu; Fri, 26 Jul 2002 07:54:39 +0100
Message-Id: <20020726075056.K30971-100000@plum.flirble.org>
Date: Fri, 26 Jul 2002 07:54:39 +0100 (BST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scot Elliott <scot@poptart.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Passwordless key-based ssh2 authentication
In-Reply-To: <Pine.LNX.4.44.0207252352580.31262-100000@venus.geneseo.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: scot@flirble.org
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

If you're using DSA keys then it's authorized_keys2 in openSSH.

As an aside, there's also a useful feature that make using passphrase-less
keys a bit more secure, eg:

from="<host>",command="exec /usr/local/libexec/imapd",no-pty,no-port-forwarding,no-X11-forwarding ssh-dss AAAAB3NzaC... pine key

Which forces SSHd to run the imap server whenever a login occurs using
your PINE key.  That was if someone gets hold of the key, they can (only)
mess with my mail, not get shell access.


Scot


On Thu, 25 Jul 2002, Mark T. Valites wrote:

> authorized_keys2 with openssh2.  I'm not sure about commercial ssh2 off
> hand.  ssh, the Definitice Guide from O'Reilly has it in there.
> Unfortuneatly, it's at work & I'm not...  I think commercial ssh uses
> authorized_keys.  There's only two, so try I guess...
>
> On Thu, 25 Jul 2002, Joe DeBattista wrote:
>
> > Does it still use the authorized_keys file with ssh2?
> >
> >
> >                                  Joe DeBattista
> >                                  UCSF, ITS
> >                       INTERNET:  joed@itsa.ucsf.edu
> >
> > On Thu, 25 Jul 2002, Mark T. Valites wrote:
> >
> > > Joe,
> > >
> > > You need to concatonate the public key onto a file called authorized_keys2
> > > in the .ssh directory (or different depending on the ssh version you're
> > > running....).  It doesn't explicity say how to do it, but it does
> > > say you need to in the link you posted.  You can do this to make it work:
> > >
> > > cat some_pub_key >> ~/.ssh/authorized_keys2
> > >
> > > Check the permissions on all the ssh files though!  ssh is picky (for good
> > > reason about the perms).  ssh -v -v -v won't pick up this problem for you,
> > > but tailing the logs on the sshd machine will.
> > >
> > > Once that works, the passworless ssh imapping to preauth'd imapd works
> > > without any problem.
> > >
> > > Now if only I could get this to go with the courier imap preauth imapd...
> > >
> > > On Thu, 25 Jul 2002, Joe DeBattista wrote:
> > >
> > > > Greetings,
> > > >   I'm in the process of setting up IMAP to work with Pine 4.44 on my
> > > > client server.  Everything works fine, except that I'd like to be able to
> > > > not require my users to give a login and password to get to the IMAP
> > > > server.  I found the posting for ssh at
> > > > http://www.washington.edu/pine/pine-info/1999.12/msg00170.html
> > > > but I haven't had any luck doing the equivalent steps under SSH2.
> > > >
> > > > Here's what I tried:
> > > > Under a user login, I ran ssh-keygen on the client machine, leaving the
> > > > passphrase blank. It created the private key as ~user/.ssh2/id_dsa_1024_a
> > > > and the public key as ~user/.ssh2/id_dsa_1024_a.pub
> > > >
> > > > I ftp'ed the id_dsa_1024_a.pub to the IMAP server and placed it  under
> > > > ~user/.ssh2/hostkeys/key_22_clientmachine.pub
> > > >
> > > > According to the posting, from the client machine, I should be able to
> > > > type
> > > >   ssh (I'm trying ssh2) my.imap.server
> > > > and connect without being asked for a password, but it continues to query
> > > > me for the password.
> > > >
> > > > Any help will be greatly appreciated.
> > > >
> > > >
> > > >                                  Joe DeBattista
> > > >                                  UCSF, ITS
> > > >                       INTERNET:  joed@itsa.ucsf.edu
> > > >
> > > > --
> > > > -----------------------------------------------------------------
> > > >  For information about this mailing list, and its archives, see:
> > > >  http://www.washington.edu/pine/pine-info/
> > > > -----------------------------------------------------------------
> > > >
> > > >
> > >
> > > >--))> >--))>
> > > Mark T. Valites
> > > Unix Systems Analyst
> > > 1 College Circle - 124b1 South Hall
> > > SUNY Geneseo
> > > Geneseo, NY 14454
> > > 585-245-5577
> > > 585-259-3471 (Cell)
> > > 585-245-5579 (Fax)
> > >
> > >
> >
> >
>
> >--))> >--))>
> Mark T. Valites
> Unix Systems Analyst
> 1 College Circle - 124b1 South Hall
> SUNY Geneseo
> Geneseo, NY 14454
> 585-245-5577
> 585-259-3471 (Cell)
> 585-245-5579 (Fax)
>
>


From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 28 Jul 2002 13:03:29 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6SK3S2P011878
	for <mailarch+pine-info@groupms.cac.washington.edu>; Sun, 28 Jul 2002 13:03:28 -0700
Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Sun Jul 28 13:03:27 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6SK3RpB005699
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 28 Jul 2002 13:03:27 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6SK1gqt019430;
	Sun, 28 Jul 2002 13:01:42 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6SJxOeY023632
	for <pine-info@reallists.u.washington.edu>; Sun, 28 Jul 2002 12:59:25 -0700
Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Jul 28 12:59:24 2002 -0700
Received: from equake.geol.vt.edu (equake.geol.vt.edu [128.173.184.42])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6SJxNlq025507
	for <pine-info@u.washington.edu>; Sun, 28 Jul 2002 12:59:24 -0700
Received: from localhost (snoke@localhost)
	by equake.geol.vt.edu (8.11.4/8.11.4) with ESMTP id g6SJxN105349;
	Sun, 28 Jul 2002 15:59:23 -0400 (EDT)
Message-Id: <Pine.GSO.4.43.0207281546341.5295-100000@equake.geol.vt.edu>
Date: Sun, 28 Jul 2002 15:59:23 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Arthur Snoke <snoke@vt.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Managing Mail Folders
In-Reply-To: <Pine.GSO.4.43.0204170902130.18373-100000@equake.geol.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: equake.geol.vt.edu: snoke owned process doing -bs
X-X-Sender: snoke@equake.geol.vt.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I would like to do some mail folder maintenance.  I am hoping there is
a command sequence within PINE which would make it easier than just using
an editor.

I have several folders which are getting well over a thousand messages in
them as I have been adding to them for a couple of years.  What I want to
do is to divide a given folder into two folders so that one folder has all
the files which came prior to 2002 and the second would have all those
which cam since the end of 2001.  For example, say I have a folder named
"courses."  I would like to have two folders one named "courses01" and the
other "courses."  Next year I might divide the current "courses" into
"courses02" and "courses."

Is there a way to "S" a sequential set of messages at once?  Or "D" a set?
That would solve my problem.

I am running PINE 4.43 on Sun Solaris 2.8.  I tried Help, but did not find
anything beyond a discussion of saving individual messages.

Thanks in advance,

Arthur Snoke


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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 29 Jul 2002 07:36:39 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6TEac2P002303
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 29 Jul 2002 07:36:39 -0700
Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 29 07:36:38 2002 -0700
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6TEaboF014812
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 29 Jul 2002 07:36:37 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6TEZZlZ013180;
	Mon, 29 Jul 2002 07:35:36 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6TEY4eY058644
	for <pine-info@reallists.u.washington.edu>; Mon, 29 Jul 2002 07:34:04 -0700
Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 29 07:34:04 2002 -0700
Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6TEY3JX027351
	for <pine-info@u.washington.edu>; Mon, 29 Jul 2002 07:34:03 -0700
Received: from pollux (pollux [129.252.130.113])
	by moultrie.cse.sc.edu (Postfix) with ESMTP id 13EBB1E4C5
	for <pine-info@u.washington.edu>; Mon, 29 Jul 2002 10:34:03 -0400 (EDT)
Message-Id: <Pine.GSO.4.44.0207290931110.323-100000@pollux.cse.sc.edu>
Date: Mon, 29 Jul 2002 09:34:02 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Managing Mail Folders
In-Reply-To: <Pine.GSO.4.43.0207281546341.5295-100000@equake.geol.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: gopalan@pollux.cse.sc.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 28 Jul 2002, Arthur Snoke wrote:

> Is there a way to "S" a sequential set of messages at once?  Or "D" a
> set? That would solve my problem.

Make sure that in the config screen, you have this option set:

    [X] enable-aggregate-command-set

After that, in your folder, (;)Select (D)ate, type in the date range.
Then (A)pply (S)ave and type in the mailbox name to save your messages
to.

At each stage, look at the bottom of the screen for interesting options
you might use in other situations.

-- 
Gopi Sundaram
gopalan@cse.sc.edu
http://www.cse.sc.edu/~gopalan/Pine/



From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 29 Jul 2002 13:42:18 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6TKgI2P021813
	for <mailarch+pine-info@groupms.cac.washington.edu>; Mon, 29 Jul 2002 13:42:18 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 29 13:42:17 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6TKgHoF027763
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 29 Jul 2002 13:42:17 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6TKdvR8032530;
	Mon, 29 Jul 2002 13:40:01 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6TKb7eY085730
	for <pine-info@reallists.u.washington.edu>; Mon, 29 Jul 2002 13:37:07 -0700
Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 29 13:37:06 2002 -0700
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6TKb6JX006002
	for <pine-info@u.washington.edu>; Mon, 29 Jul 2002 13:37:06 -0700
Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 29 13:37:06 2002 -0700
Received: from mse2.com ([61.149.18.203])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6TKb2pA005420
	for <pine-info@cac.washington.edu>; Mon, 29 Jul 2002 13:37:04 -0700
Received: (qmail 12148 invoked from network); 29 Jul 2002 08:31:26 -0000
Received: from unknown (HELO relay) (165.108.154.45)
  by 0 with SMTP; 29 Jul 2002 08:31:26 -0000
Message-Id: <200207292037.g6TKb2pA005420@mx2.cac.washington.edu>
Date: Mon, 29 Jul 2002 16:33:28 +0800
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: owner-pine-info@cac.washington.edu
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: 如何在最有钱景的房地产行业找到工作
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312_CHARSET"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

您好：

    免费寻找工作、招聘专业人士－－焦点房地产网
（http://house.focus.com.cn）您最佳的选择！

    如何在最有钱景的房地产行业找到工作？
    当然去专业网站专业招聘频道！新开“人才论坛”与业内同行自由交流成才之
道！

    《精品购物指南》：“焦点房地产网（house.focus.com.cn）是全国数十家专业
房地产网站中对北京市场影响最大、覆盖力最广的网站之一。其中的BBS业内人士论
坛和社区准业主论坛也是当前北京专业房地产网站中人气最旺、影响力最大的专业论
坛，购房人及业主对于各楼盘及物业小区反映的信息也最为全面。”
    《北京晚报》 ：“业内人气最旺的焦点房地产网站，正以其不断创新的内容和
以质量及服务取胜的务实模式而深受房地产业内外朋友的喜爱和好评。”
    《财经时报》：“焦点房地产论坛在业界最火”。
    ……

    人气最旺的房地产网站——焦点房地产网 (house.focus.com.cn)正式推出面向
房地产行业的专业招聘频道，每天数万房地产专业人士光顾焦点房地产网站。

    如果您是开发商，从现在起，您还有一个月时间获得免费刊登招聘广告的机会，
通过获得焦点批准的管理帐号，您还能自己登录招聘管理公司招聘信息。

    现在就登录焦点房地产招聘频道
    http://house.focus.com.cn/job
      powered by www.mailer.com.cn                       
                                                     

                                                     

                                                     

                                                     

                                                 
                                                         



From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 30 Jul 2002 14:46:47 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6ULkl2P007049
	for <mailarch+pine-info@groupms.cac.washington.edu>; Tue, 30 Jul 2002 14:46:47 -0700
Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Jul 30 14:46:47 2002 -0700
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6ULkgpB011693
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 30 Jul 2002 14:46:43 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6ULj5qt032552;
	Tue, 30 Jul 2002 14:45:05 -0700
Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6ULg8eY011912
	for <pine-info@reallists.u.washington.edu>; Tue, 30 Jul 2002 14:42:08 -0700
Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jul 30 14:42:07 2002 -0700
Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.112.233])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6ULg6R9029519
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 30 Jul 2002 14:42:06 -0700
Received: from soda.CSUA.Berkeley.EDU (localhost [127.0.0.1])
	by soda.CSUA.Berkeley.EDU (8.12.3/8.12.3) with ESMTP id g6ULg6V0001239
	for <pine-info@u.washington.edu>; Tue, 30 Jul 2002 14:42:06 -0700 (PDT)
	(envelope-from tonytung@CSUA.Berkeley.EDU)
Received: from localhost (tonytung@localhost)
	by soda.CSUA.Berkeley.EDU (8.12.3/8.12.3/Submit) with ESMTP id g6ULg6FY001236
	for <pine-info@u.washington.edu>; Tue, 30 Jul 2002 14:42:06 -0700 (PDT)
Message-Id: <Pine.BSF.4.44.0207301431490.95492-100000@soda.csua.berkeley.edu>
Date: Tue, 30 Jul 2002 14:42:06 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Tony Tung <tonytung@CSUA.Berkeley.EDU>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: mail check interval with mbx inbox
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: soda.CSUA.Berkeley.EDU: tonytung owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

I have pine set up with a mbx inbox (I created a mailbox INBOX in my home
directory using #driver.mbx).  Sometimes I see new mail in the default
mail drop (/var/mail), but pressing the down arrow key or Ctrl-L does not
bring the new message into the INBOX.  I have to wait a while before it
automatically happens.  Is this the correct behavior?

Thanks,
Tony

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

From pinedev@shivax2.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 31 Jul 2002 16:06:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6VN6A2P031345
	for <mailarch+pine-info@groupms.cac.washington.edu>; Wed, 31 Jul 2002 16:06:10 -0700
Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jul 31 16:06:09 2002 -0700
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
	by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6VN5xpB020653
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 31 Jul 2002 16:06:00 -0700
Received: from host (lists.u.washington.edu [140.142.56.13])
	by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6VN4kR8034592;
	Wed, 31 Jul 2002 16:04:46 -0700
Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6VN0veY099230
	for <pine-info@reallists.u.washington.edu>; Wed, 31 Jul 2002 16:00:57 -0700
Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 31 16:00:57 2002 -0700
Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6VN0ulq001066
	for <pine-info@u.washington.edu>; Wed, 31 Jul 2002 16:00:56 -0700
Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 31 16:00:56 2002 -0700
Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6VN0roE010179
	for <pine-info@cac.washington.edu>; Wed, 31 Jul 2002 16:00:55 -0700
Received: from Kumszas ([208.151.246.42]) by out006.verizon.net
          (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with SMTP
          id <20020731230050.JQWI310.out006.verizon.net@Kumszas>
          for <pine-info@cac.washington.edu>;
          Wed, 31 Jul 2002 18:00:50 -0500
Message-Id: <20020731230050.JQWI310.out006.verizon.net@Kumszas>
Date: Wed, 31 Jul 2002 18:00:53 -0500
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: owner-pine-info <owner-pine-info@cac.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Footer here
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=Mq3z0AP5wK2wzvq9R7jI65294z75G132e
X-To: pine-info@cac.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello, a message sent to <pine-info@u.washington.edu>  by
<owner-pine-info@cac.washington.edu> with the subject Footer here was scanned and found to contain a virus
called "Exploit-MIME.gen" .  The infected part of the message was Cleaned and Quarantined
before delivery to user.
.

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