From pinedev@shivax2.cac.washington.edu Thu Jan  2 08:48:53 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 08:48:53 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Gmq2U016701;
	Thu, 2 Jan 2003 08:48:52 -0800
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.12) with ESMTP id h02GmnHh015605
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 08:48:49 -0800
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.12) with SMTP id h02Gm3ll014092;
	Thu, 2 Jan 2003 08:48:04 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Gj9CK031042
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 08:45:09 -0800
Received: from amos.gf.gospelcom.net (jabbok.gospelcom.net [204.253.132.4])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Gj4IO001846
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 08:45:05 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
	by amos.gf.gospelcom.net (8.11.6/8.11.6) with ESMTP id h02GfTu02662;
	Thu, 2 Jan 2003 11:41:30 -0500
Message-Id: <Pine.LNX.4.44.0301021134560.27334-100000@amos.gf.gospelcom.net>
Date: Thu, 2 Jan 2003 11:41:28 -0500 (EST)
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: Sorting ignores square brackets?
In-Reply-To: <Pine.GSU.4.21.0212271208190.20043-100000@garcia.efn.org>
References: <Pine.GSU.4.21.0212271208190.20043-100000@garcia.efn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Seth Cohn, EFN General Manager" <gm@efn.org>
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

> We're using RT (Request Tracker) and it uses [ticket #123] as part of the
> subject to track tickets.
>
> Using either subject or ordered subject _ignores_ the square bracketed
> words.
>
> This means that instead of sorting all of the [ticket #123] together and
> then sorting [ticket #124] next, it sorts only based on the remainder of
> the subject line, which can change.
>
> Mutt correctly works (sorting all of the tickets in numbered order).
> But we're a PINE shop from way back, and I don't want to tell everyone to
> have to switch to Mutt.
>
> Is there a way (without munging the brackets - which RT is looking for)
> to fix the sort?   I'd be glad to recompile PINE to do so.
> Googling didn't find anything like an answer.

In my experience with RT, pine threading will still thread properly,
even if the subject line differs.  Sorting by subject, as you well know,
doesn't work too well.

I should mention that I'm not using 4.51 threading; I'm using Eduardo's
threading patch.  However, I think the threading algorithm
behind-the-scenes is the same; it's just the display that differs.

Would convincing users to use threads work?  Eduardo's patch:

  http://www.math.washington.edu/~chappa/pine/info/fancy.html

Another helpful thing for RT/pine users might be Eduardo's "rules"
patch:

  http://www.math.washington.edu/~chappa/pine/info/rules.html

He added a _REXTRIM_ token that lets you use regular expressions to
munge the *display* of the subject, thus letting things like this:

  [ticket #123]

not show up in an index listing, but still be there so that RT is happy.
Depending on how you work, this may be helpful or harmful.  For me it
was a lifesaver...

Joel

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



From pinedev@shivax2.cac.washington.edu Thu Jan  2 08:53:45 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 08:53:45 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Gri2U016887;
	Thu, 2 Jan 2003 08:53:44 -0800
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.12) with ESMTP id h02GrYqe024960
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 08:53:34 -0800
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.12) with SMTP id h02GqlDb084088;
	Thu, 2 Jan 2003 08:52:47 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02GqTCK038204
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 08:52:29 -0800
Received: from boondoggle.office.aol.com (x98A3A3F6.pix.aol.com [152.163.163.246])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02GqRIO003617
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 08:52:28 -0800
Received: (from harvell@localhost)
	by boondoggle.office.aol.com (8.11.6/8.11.6) id h02GqGr05726;
	Thu, 2 Jan 2003 11:52:16 -0500 (EST)
Message-Id: <Pine.GSO.4.51.0301021151150.5684@boondoggle.office.aol.com>
Date: Thu, 2 Jan 2003 11:52:16 -0500 (EST)
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: Brian Harvell <harvell@aol.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: manual expunge all folders
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: harvell@boondoggle.office.aol.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=XIII, Probability=13%, Report="MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_00_01, USER_AGENT_PINE"


Is there a way to manually expunge all folders at once? I don't like the auto expunge but
I don't want to have to go into each folder to tell it to expunge.

Thanks
Brian

-- 

Brian Harvell                harvell@aol.net             http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc


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

From pinedev@shivax2.cac.washington.edu Thu Jan  2 09:36:58 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 09:36:58 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Hav2U018517;
	Thu, 2 Jan 2003 09:36:57 -0800
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.12) with ESMTP id h02Harqe026306
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 09:36:54 -0800
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.12) with SMTP id h02Ha109031644;
	Thu, 2 Jan 2003 09:36:01 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02HZNCK031598
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 09:35:23 -0800
Received: from ccaix.jsums.edu (www.jsums.edu [143.132.1.13])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02HZLRN029178
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 09:35:21 -0800
Received: from cronos ([10.20.8.15])
	by ccaix.jsums.edu (8.11.6/8.11.6) with SMTP id h02HTCK02516
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 11:29:12 -0600
Message-Id: <001001c2b285$7a940270$0f08140a@cronos>
Date: Thu, 2 Jan 2003 11:36:27 -0600
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: "Rafael Mahecha" <mahecha@jsums.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: .forward not working on RHL 8?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000D_01C2B253.2FDFA1D0"
X-To: <pine-info@u.washington.edu>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Uwash-Spam: Gauge=XXXI, Probability=31%, Report="PRIORITY_NO_NAME, SPAM_PHRASE_05_08, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY"
X-Uwash-Spam: Gauge=XX, Probability=20%, Report="NOSPAM_INC, SPAM_PHRASE_05_08, USER_AGENT_OE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C2B253.2FDFA1D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Happy new years, to all.
once up on a time (up to rhl 7.3), it used to be that to forward your =
emails to another email address all you needed to do was to create =
".forward" file containing the final address for emails...

I upgraded/installed rhl 8, and now, the .forwarding doesn't work!!!

is this a pine thing? rhl? i checked the sendmail.cf and there is a line =
for .forward that is uncommented, so that it can be seen by daemons...

how to get pine to .forward emails when running rhl 8?

Thanks.
------=_NextPart_000_000D_01C2B253.2FDFA1D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Happy new years, to all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>once up on a time (up to rhl 7.3), it =
used to be=20
that to forward your emails to another email address all you needed to =
do was to=20
create ".forward" file containing the final address for =
emails...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I upgraded/installed rhl 8, and now, =
the=20
.forwarding doesn't work!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>is this a pine thing? rhl? i checked =
the=20
sendmail.cf and there is a line for .forward that is uncommented, so =
that it can=20
be seen by daemons...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>how to get pine to .forward emails when =
running rhl=20
8?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks.</FONT></DIV></BODY></HTML>

------=_NextPart_000_000D_01C2B253.2FDFA1D0--

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

From pinedev@shivax2.cac.washington.edu Thu Jan  2 13:19:18 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 13:19:17 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LJH2U027361;
	Thu, 2 Jan 2003 13:19:17 -0800
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.12) with ESMTP id h02LJDqe001438
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 13:19:13 -0800
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.12) with SMTP id h02LII09033156;
	Thu, 2 Jan 2003 13:18:18 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LHDCK032102
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 13:17:13 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LH9Bg022305
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 13:17:11 -0800
Received: from localhost (dufberg@localhost)
	by aslan.narnia.pp.se (8.11.3/8.11.3) with ESMTP id h02LH0P89602;
	Thu, 2 Jan 2003 22:17:01 +0100 (CET)
	(envelope-from dufberg@narnia.pp.se)
Message-Id: <20030102185208.M87892-100000@aslan.narnia.pp.se>
Date: Thu, 2 Jan 2003 22:17:00 +0100 (CET)
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: Mats Dufberg <dufberg@narnia.pp.se>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: .forward not working on RHL 8?
In-Reply-To: <001001c2b285$7a940270$0f08140a@cronos>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Rafael Mahecha <mahecha@jsums.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Jan 2, 2003, 11:36 (-0600) Rafael Mahecha <mahecha@jsums.edu> wrote:

> once up on a time (up to rhl 7.3), it used to be that to forward your
> emails to another email address all you needed to do was to create
> ".forward" file containing the final address for emails...
>
> I upgraded/installed rhl 8, and now, the .forwarding doesn't work!!!

Well, I don't know what rhl is, but .forward is something for sendmail.

> how to get pine to .forward emails when running rhl 8?

The purpose of .forward is to do something with the mail before it ends up
in the spool file (inbox). When you start pine it's too late. Pine will
never read .forward.

Your question should be sent to a sendmail list, or list relevant for your
MTA of your server, but let me give you some suggestions.

You can test adress with the following command,

$ sendmail -v -bv USER

Sendmail will refuse to consider a .forward with write access for anyone
but the user. Set permission 644. The .forward file must be owned by the
user itself or by root.



Mats

-----------------------------------------------------------------
Mats Dufberg                                 dufberg@narnia.pp.se
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588



From pinedev@shivax2.cac.washington.edu Thu Jan  2 13:41:41 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 13:41:41 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Lff2U028220;
	Thu, 2 Jan 2003 13:41:41 -0800
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.12) with ESMTP id h02LfbHh025019
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 13:41:37 -0800
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.12) with SMTP id h02Leqll010558;
	Thu, 2 Jan 2003 13:40:52 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LeHCK019066
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 13:40:17 -0800
Received: from ccaix.jsums.edu (www.jsums.edu [143.132.1.13])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LeFBf028961
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 13:40:16 -0800
Received: from cronos ([10.20.8.15])
	by ccaix.jsums.edu (8.11.6/8.11.6) with SMTP id h02LYBK26779;
	Thu, 2 Jan 2003 15:34:11 -0600
Message-Id: <001001c2b2a7$b21701d0$0f08140a@cronos>
Date: Thu, 2 Jan 2003 15:41:23 -0600
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: "Rafael Mahecha" <mahecha@jsums.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: .forward not working on RHL 8?
References: <20030102185208.M87892-100000@aslan.narnia.pp.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: "Mats Dufberg" <dufberg@narnia.pp.se>,
   "Pine Discussion Forum" <pine-info@u.washington.edu>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, REFERENCES, SPAM_PHRASE_05_08, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY"
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="NOSPAM_INC, QUOTED_EMAIL_TEXT, REFERENCES, SPAM_PHRASE_05_08, USER_AGENT_OE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

that did it!
Thanks a bunch.
=========================================
=========================================
Rafael Mahecha
Technical Assistant - Meteorologist
Jackson State University (http://www.jsums.edu)
Meteorology Program (http://weather.jsums.edu)

1400 J. R. Lynch Street
Jackson, MS 39217

Ph: 601 979 3617
Fax: 601 979 3630

mahecha@jsums.edu
mahecha@twister.jsums.edu
========================================
========================================
----- Original Message -----
From: "Mats Dufberg" <dufberg@narnia.pp.se>
To: "Pine Discussion Forum" <pine-info@u.washington.edu>
Sent: Thursday, January 02, 2003 3:17 PM
Subject: Re: .forward not working on RHL 8?


> On Jan 2, 2003, 11:36 (-0600) Rafael Mahecha <mahecha@jsums.edu> wrote:
>
> > once up on a time (up to rhl 7.3), it used to be that to forward your
> > emails to another email address all you needed to do was to create
> > ".forward" file containing the final address for emails...
> >
> > I upgraded/installed rhl 8, and now, the .forwarding doesn't work!!!
>
> Well, I don't know what rhl is, but .forward is something for sendmail.
>
> > how to get pine to .forward emails when running rhl 8?
>
> The purpose of .forward is to do something with the mail before it ends up
> in the spool file (inbox). When you start pine it's too late. Pine will
> never read .forward.
>
> Your question should be sent to a sendmail list, or list relevant for your
> MTA of your server, but let me give you some suggestions.
>
> You can test adress with the following command,
>
> $ sendmail -v -bv USER
>
> Sendmail will refuse to consider a .forward with write access for anyone
> but the user. Set permission 644. The .forward file must be owned by the
> user itself or by root.
>
>
>
> Mats
>
> -----------------------------------------------------------------
> Mats Dufberg                                 dufberg@narnia.pp.se
> Blaoarvsgraend 42                                  +46-8-38 48 59
> SE-162 45 Vaellingby, Sweden                      +46-70-258 2588
>


From pinedev@shivax2.cac.washington.edu Thu Jan  2 13:45:48 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 13:45:48 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02Ljl2U028375;
	Thu, 2 Jan 2003 13:45:47 -0800
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.12) with ESMTP id h02Ljiqe002155
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 13:45:44 -0800
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.12) with SMTP id h02LivDb076946;
	Thu, 2 Jan 2003 13:44:57 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LibCK030376
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 13:44:37 -0800
Received: from ccaix.jsums.edu (www.jsums.edu [143.132.1.13])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h02LiZRN008880
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 13:44:36 -0800
Received: from cronos ([10.20.8.15])
	by ccaix.jsums.edu (8.11.6/8.11.6) with SMTP id h02LcWK27205;
	Thu, 2 Jan 2003 15:38:32 -0600
Message-Id: <001701c2b2a8$4d70c080$0f08140a@cronos>
Date: Thu, 2 Jan 2003 15:45:44 -0600
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: "Rafael Mahecha" <mahecha@jsums.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: .forward not working on RHL 8?
References: <20030102185208.M87892-100000@aslan.narnia.pp.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: "Mats Dufberg" <dufberg@narnia.pp.se>,
   "Pine Discussion Forum" <pine-info@u.washington.edu>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, REFERENCES, SPAM_PHRASE_05_08, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY"
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="NOSPAM_INC, QUOTED_EMAIL_TEXT, REFERENCES, SPAM_PHRASE_05_08, USER_AGENT_OE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

PS: rhl = Red Hat Linux (oops...)
=========================================
=========================================
Rafael Mahecha
Technical Assistant - Meteorologist
Jackson State University (http://www.jsums.edu)
Meteorology Program (http://weather.jsums.edu)

1400 J. R. Lynch Street
Jackson, MS 39217

Ph: 601 979 3617
Fax: 601 979 3630

mahecha@jsums.edu
mahecha@twister.jsums.edu
========================================
========================================
----- Original Message -----
From: "Mats Dufberg" <dufberg@narnia.pp.se>
To: "Pine Discussion Forum" <pine-info@u.washington.edu>
Sent: Thursday, January 02, 2003 3:17 PM
Subject: Re: .forward not working on RHL 8?


> On Jan 2, 2003, 11:36 (-0600) Rafael Mahecha <mahecha@jsums.edu> wrote:
>
> > once up on a time (up to rhl 7.3), it used to be that to forward your
> > emails to another email address all you needed to do was to create
> > ".forward" file containing the final address for emails...
> >
> > I upgraded/installed rhl 8, and now, the .forwarding doesn't work!!!
>
> Well, I don't know what rhl is, but .forward is something for sendmail.
>
> > how to get pine to .forward emails when running rhl 8?
>
> The purpose of .forward is to do something with the mail before it ends up
> in the spool file (inbox). When you start pine it's too late. Pine will
> never read .forward.
>
> Your question should be sent to a sendmail list, or list relevant for your
> MTA of your server, but let me give you some suggestions.
>
> You can test adress with the following command,
>
> $ sendmail -v -bv USER
>
> Sendmail will refuse to consider a .forward with write access for anyone
> but the user. Set permission 644. The .forward file must be owned by the
> user itself or by root.
>
>
>
> Mats
>
> -----------------------------------------------------------------
> Mats Dufberg                                 dufberg@narnia.pp.se
> Blaoarvsgraend 42                                  +46-8-38 48 59
> SE-162 45 Vaellingby, Sweden                      +46-70-258 2588
>


From pinedev@shivax2.cac.washington.edu Thu Jan  2 17:33:58 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 17:33:58 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h031Xw2U003877;
	Thu, 2 Jan 2003 17:33:58 -0800
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.12) with ESMTP id h031Xqqe009043
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 17:33:52 -0800
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.12) with SMTP id h031X109023648;
	Thu, 2 Jan 2003 17:33:01 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h031WHCK041402
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 17:32:17 -0800
Received: from clavin.efn.org (clavin.efn.org [66.178.136.10])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h031WFAo016273
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 17:32:15 -0800
Received: from garcia.efn.org (daemon@garcia.efn.org [66.178.136.5])
	by clavin.efn.org (8.11.6/8.11.6) with ESMTP id h031WEN12799;
	Thu, 2 Jan 2003 17:32:14 -0800 (PST)
Received: from localhost (gm@localhost)
	by garcia.efn.org (8.11.6/8.11.6) with ESMTP id h031WDf05650;
	Thu, 2 Jan 2003 17:32:13 -0800 (PST)
Message-Id: <Pine.GSU.4.21.0301021725130.3730-100000@garcia.efn.org>
Date: Thu, 2 Jan 2003 17:32:11 -0800 (PST)
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: "Seth Cohn, EFN General Manager" <gm@efn.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Sorting ignores square brackets?
In-Reply-To: <Pine.LNX.4.44.0301021134560.27334-100000@amos.gf.gospelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Joel Boonstra <jboonstra@gospelcom.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: garcia.efn.org: gm owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Jan 2003, Joel Boonstra wrote:

> > We're using RT (Request Tracker) and it uses [ticket #123] as part of the
> > subject to track tickets.

I neglected to mention we were using an older version of Pine (4.21) but I
just installed 4.51 and it's doing the same thing... mostly.

> >
> > Using either subject or ordered subject _ignores_ the square bracketed
> > words.
> >
> > This means that instead of sorting all of the [ticket #123] together and
> > then sorting [ticket #124] next, it sorts only based on the remainder of
> > the subject line, which can change.

Ordered subject now (4.51) does _half_ the job.  It will respect the
[ticket #123] then [ticket #124] EXCEPT with subject line changes.
If the subject matches a previous subject used (ie Help!) it will fold
into the wrong ticket number.  If the subject changes, it won't sort that
subject into the rest of the ticket, but starts a new (later) thread.  Not
much better.

> >
> > Is there a way (without munging the brackets - which RT is looking for)
> > to fix the sort?   I'd be glad to recompile PINE to do so.
> > Googling didn't find anything like an answer.
> 
> In my experience with RT, pine threading will still thread properly,
> even if the subject line differs.  Sorting by subject, as you well know,
> doesn't work too well.

Doesn't work.  RT isn't giving pine the thread info it needs at
all.  Threading is nearly flat.  Ordered subject was closer to correct.

> Another helpful thing for RT/pine users might be Eduardo's "rules"
> patch:
> 
>   http://www.math.washington.edu/~chappa/pine/info/rules.html
> 
> He added a _REXTRIM_ token that lets you use regular expressions to
> munge the *display* of the subject, thus letting things like this:
> 
>   [ticket #123]
> 
> not show up in an index listing, but still be there so that RT is happy.
> Depending on how you work, this may be helpful or harmful.  For me it
> was a lifesaver...

I really really like this.  I'm hoping (I'll be installing this) that I
can remove from index view the "[ticket #", which will allow sorting to
work, I hope. 

I still think pine needs a 'don't ignore brackets for sorting' option.
Developers?

-- 
## Seth Cohn, General Manager of Eugene Free Community Network gm@efn.org
## Businesses planned for service are apt to succeed;  Phone 541-484-9637
## Businesses planned for profit are apt to fail. - N. Butler


From pinedev@shivax2.cac.washington.edu Thu Jan  2 18:51:36 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 18:51:36 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h032pZ2U005392;
	Thu, 2 Jan 2003 18:51:35 -0800
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.12) with ESMTP id h032pVHh000726
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 18:51:31 -0800
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.12) with SMTP id h032oill027576;
	Thu, 2 Jan 2003 18:50:44 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h032o8CK010952
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 18:50:08 -0800
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.12) with SMTP id h032o6RN013695
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 18:50:07 -0800
Received: (qmail 15696 invoked by uid 1828); 3 Jan 2003 02:50:06 -0000
Message-Id: <Pine.GSO.4.33.0301021847340.14494-100000@vax.hanford.org>
Date: Thu, 2 Jan 2003 18:50:06 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Issue with base64 email
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXXIIIIIII, Probability=37%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXXXI, Probability=41%, Report="NO_MX_FOR_FROM, UPPERCASE_25_50, USER_AGENT_PINE, __UPPERCASE_25_50"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


I *think* I'm essentially now complaining about the
enable-full-header-and-text
feature which I normally like..

Anyway, the one type of mail that this feature has a problem with seems
to be base64 email..

So I view full headers, try to reply, now I get a big chunk of text
like:
PGh0bWw+DQo8Ym9keQ0KPGJyPg0KSGkgLCBtYXR0YWNrPGJyPg0KPGJyPg0KSU48IS0tbWF0
dGFjay0tPlRFPCEtLW1hdHRhY2stLT5STkE8IS0tbWF0dGFjay0tPlRJT048IS0tbWF0dGFj
ay0tPkFMIERSPCEtLW1hdHRhY2stLT5JVjwhLS1tYXR0YWNrLS0+RVInUyBMPCEtLW1hdHRh
Y2stLT5JQzwhLS1tYXR0YWNrLS0+RU48IS0tbWF0dGFjay0tPlNFPGJyPg0KPGJyPg0KTmU8


Is there some way I can quickly/easily toggle this single pref for an
individual message, or maybe for all base64 messages?




mattack@vax.hanford.org

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

From pinedev@shivax2.cac.washington.edu Thu Jan  2 20:08:25 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 20:08:25 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0348O2U006855;
	Thu, 2 Jan 2003 20:08:24 -0800
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.12) with ESMTP id h0348Lqe012353
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 20:08:21 -0800
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.12) with SMTP id h0347Ojm014670;
	Thu, 2 Jan 2003 20:07:24 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0346dCK027124
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 20:06:39 -0800
Received: from clavin.efn.org (clavin.efn.org [66.178.136.10])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0346bIO007872
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 20:06:37 -0800
Received: from garcia.efn.org (daemon@garcia.efn.org [66.178.136.5])
	by clavin.efn.org (8.11.6/8.11.6) with ESMTP id h0346TN18318;
	Thu, 2 Jan 2003 20:06:29 -0800 (PST)
Received: from localhost (gm@localhost)
	by garcia.efn.org (8.11.6/8.11.6) with ESMTP id h0346Sb09470;
	Thu, 2 Jan 2003 20:06:28 -0800 (PST)
Message-Id: <Pine.GSU.4.21.0301021952160.8362-100000@garcia.efn.org>
Date: Thu, 2 Jan 2003 20:06:25 -0800 (PST)
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: "Seth Cohn, EFN General Manager" <gm@efn.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Sorting ignores square brackets?
In-Reply-To: <Pine.GSU.4.21.0301021725130.3730-100000@garcia.efn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Cc: MRC@CAC.Washington.EDU
X-Authentication-Warning: garcia.efn.org: gm owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Jan 2003, Seth Cohn, EFN General Manager wrote:

> On Thu, 2 Jan 2003, Joel Boonstra wrote:
> 
> > > We're using RT (Request Tracker) and it uses [ticket #123] as part of the
> > > subject to track tickets.
> > >
> > > Using either subject or ordered subject _ignores_ the square bracketed
> > > words.

It turns out, after reading the pine source, and seeing that all of the
sorts passed back to c-client, that it's in fact the c-client code that is
the source of the problem.

mail_strip_subject (or more specifically: mail_strip_subject_aux) in
mail.c explicitly strips everything between brackets.  No option for not
stripping exists.

This is NOT _always_ wanted.  My example is far from the only time a true
'sort based on exactly what you see' is needed.  It would be very very
nice if a 'raw subject sort' existed.

> > >
> > > This means that instead of sorting all of the [ticket #123] together and
> > > then sorting [ticket #124] next, it sorts only based on the remainder of
> > > the subject line, which can change.
> 
> 
> > >
> > > Is there a way (without munging the brackets - which RT is looking for)
> > > to fix the sort?   I'd be glad to recompile PINE to do so.
> > > Googling didn't find anything like an answer.
> > 
> > In my experience with RT, pine threading will still thread properly,
> > even if the subject line differs.  Sorting by subject, as you well know,
> > doesn't work too well.
> 
> Doesn't work.  RT isn't giving pine the thread info it needs at
> all.  Threading is nearly flat.  Ordered subject was closer to correct.
> 
> > Another helpful thing for RT/pine users might be Eduardo's "rules"
> > patch:
> > 
> >   http://www.math.washington.edu/~chappa/pine/info/rules.html
> > 
> > He added a _REXTRIM_ token that lets you use regular expressions to
> > munge the *display* of the subject, thus letting things like this:
> > 
> >   [ticket #123]
> > 
> > not show up in an index listing, but still be there so that RT is happy.
> > Depending on how you work, this may be helpful or harmful.  For me it
> > was a lifesaver...
> 
> I really really like this.  I'm hoping (I'll be installing this) that I
> can remove from index view the "[ticket #", which will allow sorting to
> work, I hope. 

Doesn't help.  While I can strip the _view_, the sorting still uses the
true subject line... so I can remove all I want, but can't sort correctly.

> 
> I still think pine needs a 'don't ignore brackets for sorting' option.
> Developers?

Ok, so let's change this to:  Developers at UW?  Raw Subject Sort?  I
realize the IMAP specs say sorts should ignore [bracketed] stuff in
subjects, but a raw sort is still useful at times.  Mutt does this
correctly, Pine doesn't.

-- 
## Seth Cohn, General Manager of Eugene Free Community Network gm@efn.org
## Businesses planned for service are apt to succeed;  Phone 541-484-9637
## Businesses planned for profit are apt to fail. - N. Butler


From pinedev@shivax2.cac.washington.edu Thu Jan  2 21:16:30 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Jan 2003 21:16:30 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h035GT2U008183;
	Thu, 2 Jan 2003 21:16:29 -0800
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.12) with ESMTP id h035GNqe013770
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 2 Jan 2003 21:16:24 -0800
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.12) with SMTP id h035FbDb092294;
	Thu, 2 Jan 2003 21:15:37 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h035ExCK036482
	for <pine-info@reallists.u.washington.edu>; Thu, 2 Jan 2003 21:14:59 -0800
Received: from clavin.efn.org (clavin.efn.org [66.178.136.10])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h035ErRN001453
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 21:14:53 -0800
Received: from garcia.efn.org (daemon@garcia.efn.org [66.178.136.5])
	by clavin.efn.org (8.11.6/8.11.6) with ESMTP id h035ErN19821
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 21:14:53 -0800 (PST)
Received: from localhost (gm@localhost)
	by garcia.efn.org (8.11.6/8.11.6) with ESMTP id h035Eqn11190
	for <pine-info@u.washington.edu>; Thu, 2 Jan 2003 21:14:52 -0800 (PST)
Message-Id: <Pine.GSU.4.21.0301022110230.10749-100000@garcia.efn.org>
Date: Thu, 2 Jan 2003 21:14:50 -0800 (PST)
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: "Seth Cohn, EFN General Manager" <gm@efn.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Sorting ignores square brackets?
In-Reply-To: <Pine.GSU.4.21.0301021952160.8362-100000@garcia.efn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: garcia.efn.org: gm owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> It turns out, after reading the pine source, and seeing that all of the
> sorts passed back to c-client, that it's in fact the c-client code that is
> the source of the problem.
> 
> mail_strip_subject (or more specifically: mail_strip_subject_aux) in
> mail.c explicitly strips everything between brackets.  No option for not
> stripping exists.

Never let it be said that a little hacking can't go a long way.

I modded the libc-client mail.c to ignore { and } instead, figuring that
was unlikely to cause trouble... and recompiled it, installed it, and then
recompiled pine too... and it still didn't sort right... then I realized I
was trying to sort an IMAP folder which doesn't use mail.c ... I copied my
tickets over to a local file (select all, save) and behold, it
works.  Local folder sorting is fine for what I need. Ordered subjects
don't work right still, but plain subject sort does...

Unlikely to break anything else, so I'm happy.  For now, it's does what I
want.

Seth

changes to mail.c (just replaced [ and ] with { and } )
case '{':                     /* leading [ */
    for (s = t + 1; s;) switch (*s) {
    case '\0': case '{':        /* end of string or nesting */
      x = s = NIL;              /* just punt */
      break;
    default:                    /* any other character */
      s++;                      /* sniff at next */
      break;
    case '}':  


> > > > This means that instead of sorting all of the [ticket #123] together and
> > > > then sorting [ticket #124] next, it sorts only based on the remainder of
> > > > the subject line, which can change.
> > 
> > > > Is there a way (without munging the brackets - which RT is looking for)
> > > > to fix the sort?   I'd be glad to recompile PINE to do so.
> > > > Googling didn't find anything like an answer.
> > > 

-- 
## Seth Cohn, General Manager of Eugene Free Community Network gm@efn.org
## Businesses planned for service are apt to succeed;  Phone 541-484-9637
## Businesses planned for profit are apt to fail. - N. Butler


From pinedev@shivax2.cac.washington.edu Fri Jan  3 10:38:21 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Jan 2003 10:38:21 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03IcH2U028078;
	Fri, 3 Jan 2003 10:38:17 -0800
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.12) with ESMTP id h03IcBHh020143
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 3 Jan 2003 10:38:11 -0800
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.12) with SMTP id h03IbDjm034850;
	Fri, 3 Jan 2003 10:37:13 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03IYYCK011960
	for <pine-info@reallists.u.washington.edu>; Fri, 3 Jan 2003 10:34:35 -0800
Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03IYSJV007920
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 10:34:30 -0800
Received: from [194.97.50.144] (helo=mx1.freenet.de)
	by mout1.freenet.de with asmtp (Exim 4.10)
	id 18UWeE-0001zo-00; Fri, 03 Jan 2003 19:34:22 +0100
Received: from p50868238.dip0.t-ipconnect.de ([80.134.130.56] helo=HAENDEL)
	by mx1.freenet.de with asmtp (ID ccnoack@freenet.de) (Exim 4.10 #1)
	id 18UWeE-0000jr-00; Fri, 03 Jan 2003 19:34:22 +0100
Message-Id: <Pine.WNT.4.50.0301031925450.-1849741-100000@haendel>
Date: Fri, 3 Jan 2003 19:31:27 +0400 (Kaukasus Normalzeit)
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: "Cornelius C. Noack" <noack@physik.uni-bremen.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: manual expunge all folders
In-Reply-To: <Pine.GSO.4.51.0301021151150.5684@boondoggle.office.aol.com>
References: <Pine.GSO.4.51.0301021151150.5684@boondoggle.office.aol.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Brian Harvell <harvell@aol.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: ccnoack@imap.freenet.de
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Jan 2003, Brian Harvell wrote:

>
> Is there a way to manually expunge all folders at once? I don't like the auto expunge but
> I don't want to have to go into each folder to tell it to expunge.
>
> Thanks
> Brian
>
go to the directory where your folders are stored and simply delete
the files with the delete command of you Operating system. This
fix for your problem is, of course, outside of pine, but works
perfectly (to me, its one of the great advantages of pine as compared
to any stupid Microsoft program that you always have access to things
on the lower level!)

ccn.
-- 
.....................................................................
    _|_
   / | \
   \_|_/    Prof.Dr. Cornelius C. Noack    Phones:
    _|_ __  Inst. f. Theor. Physik FB 1 office   : +49 (421) 218-2427
|  |   |  \ Universit"at Bremen         secretary: -2422
|__|   |__/ Otto-Hahn-Allee             Fax      : -4869
|  |   |  \ D - 28334  Bremen           home     : +49 (421) 34 22 36
|  |   |__/                                   Fax:  346 7872
   PhyHB                           E-mail: noack@physik.uni-bremen.de
                    WWW-page: www-theorie.physik.uni-bremen.de/~noack
.....................................................................

From pinedev@shivax2.cac.washington.edu Fri Jan  3 10:57:05 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Jan 2003 10:57:05 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03Iv42U028825;
	Fri, 3 Jan 2003 10:57:04 -0800
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.12) with ESMTP id h03Iv0Hh020677
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 3 Jan 2003 10:57:01 -0800
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.12) with SMTP id h03IuBll032276;
	Fri, 3 Jan 2003 10:56:11 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03IsFCK011828
	for <pine-info@reallists.u.washington.edu>; Fri, 3 Jan 2003 10:54:15 -0800
Received: from boondoggle.office.aol.com (x98A3A3F6.pix.aol.com [152.163.163.246])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03IsDIO000577
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 10:54:13 -0800
Received: (from harvell@localhost)
	by boondoggle.office.aol.com (8.11.6/8.11.6) id h03IsAQ25097;
	Fri, 3 Jan 2003 13:54:10 -0500 (EST)
Message-Id: <Pine.GSO.4.51.0301031346590.20369@boondoggle.office.aol.com>
Date: Fri, 3 Jan 2003 13:54:10 -0500 (EST)
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: Brian Harvell <harvell@aol.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: manual expunge all folders
In-Reply-To: <Pine.WNT.4.50.0301031925450.-1849741-100000@haendel>
References: <Pine.GSO.4.51.0301021151150.5684@boondoggle.office.aol.com>
 <Pine.WNT.4.50.0301031925450.-1849741-100000@haendel>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Cornelius C. Noack" <noack@physik.uni-bremen.de>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: harvell@boondoggle.office.aol.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Jan 2003, Cornelius C. Noack wrote:

> >
> go to the directory where your folders are stored and simply delete
> the files with the delete command of you Operating system. This
> fix for your problem is, of course, outside of pine, but works
> perfectly (to me, its one of the great advantages of pine as compared
> to any stupid Microsoft program that you always have access to things
> on the lower level!)
>

Yes that isn't quite what I was looking for though. This is a solution my
friend uses when he gets backed up on his email rm /var/spool/[user] :)

I found this patch which I might be able to use by setting auto expunge on
the other incoming folders. This still isn't quite what I was looking for but
it's better.

http://www.math.washington.edu/~chappa/pine/info/rules.html


So after many years of using pine I have now just started using other incoming
folders for mail sorting. One thing I have noticed is when I'm in a folder and
expunge and then hit tab it takes some time before pine is ready to move to the
next folder (3-5 seconds even for folders that only have 1 or two messages)....
Which is what brings up my expunge question I would prefer to just expunge
everything at the end of the day.


Brian

-- 

Brian Harvell                harvell@aol.net             http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc



From pinedev@shivax2.cac.washington.edu Fri Jan  3 11:41:05 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Jan 2003 11:41:05 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03Jf42U030465;
	Fri, 3 Jan 2003 11:41:04 -0800
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.12) with ESMTP id h03JeuHh022090
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 3 Jan 2003 11:40:56 -0800
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.12) with SMTP id h03JdOjm019818;
	Fri, 3 Jan 2003 11:39:24 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03JbMCK010346
	for <pine-info@reallists.u.washington.edu>; Fri, 3 Jan 2003 11:37:22 -0800
Received: from parvati.colorado.edu (parvati.Colorado.EDU [128.138.113.52])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03JbLBf016545
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 11:37:22 -0800
Received: from localhost (dorsey@localhost)
	by parvati.colorado.edu (8.11.6/8.11.2/ITS-5.0/standard) with ESMTP id h03JbLf02305
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 12:37:21 -0700 (MST)
Message-Id: <Pine.GSO.4.51.0301031227520.1660@neingv.pbybenqb.rqh>
Date: Fri, 3 Jan 2003 12:37:21 -0700 (MST)
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: 4.51 Can't delete IMAP incoming mailbox
In-Reply-To: <Pine.GSO.4.51.0301021647180.355@neingv.pbybenqb.rqh>
References: <20021225115006.Q8041-100000@aslan.narnia.pp.se>
 <Pine.GSO.4.51.0301021647180.355@neingv.pbybenqb.rqh>
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


Pine 4.40 would allow this, as would 4.50, but with all the 4.51 builds
we've done, the [d]elete command returns:

   [Deletion cancelled: folder not in editable config file]

The incoming folders work fine with SSL -- they just can't be removed once
you set them up (except by editing the .pinerc file, which most of our
users can't handle).

Bug?  Feature?  Build error?

Thanks,
Susan

Susan Dorsey
Information Technology Services
University of Colorado at Boulder
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From pinedev@shivax2.cac.washington.edu Fri Jan  3 12:15:42 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Jan 2003 12:15:42 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03KFf2U031735;
	Fri, 3 Jan 2003 12:15:41 -0800
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.12) with ESMTP id h03KFZHh023138
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 3 Jan 2003 12:15:36 -0800
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.12) with SMTP id h03KEkDb096578;
	Fri, 3 Jan 2003 12:14:47 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03KCtCK044382
	for <pine-info@reallists.u.washington.edu>; Fri, 3 Jan 2003 12:12:55 -0800
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h03KCsBf025404
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 12:12:54 -0800
Received: (qmail 29115 invoked by uid 1828); 3 Jan 2003 20:12:53 -0000
Message-Id: <Pine.GSO.4.33.0301031210440.28533-100000@vax.hanford.org>
Date: Fri, 3 Jan 2003 12:12:53 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Crashing pine pasting in To field..
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXXIIII, Probability=34%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_01_02, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXXIIIIIII, Probability=37%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


This is on 4.33 here on my personal acct (they use qmail or something else
that's "hard" to update pine for as far as I remember)..

I have one (spam, of course) message that I seem to be able to consistently
crash trying to paste addresses in the To field..  I'm also resizing the
(GUI) window and switching between screen sessions, so I haven't narrowed
it down yet.. though it looks pretty easy to repro.

Anyhow.. I'm not getting any symbols from gdb..  What am I doing wrong?

I can nm the pine binary, and I'm seeing symbol names there..

Program received signal SIGWINCH, Window size changed.
0xef5b7408 in poll ()
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0xef5a4704 in strlen ()
(gdb) bt
#0  0xef5a4704 in strlen ()
#1  0x14c7b8 in ?? ()
#2  0x147424 in ?? ()
#3  0x152f6c in ?? ()
#4  0x16a5c0 in ?? ()
#5  0x114438 in ?? ()
#6  0x101b6c in ?? ()
#7  0xa1b30 in ?? ()
#8  0x9e624 in ?? ()
#9  0xcf8b8 in ?? ()
#10 0xc3d60 in ?? ()
#11 0xfbe88 in ?? ()

Also, is there some way in gdb that I can get it to ignore the SIGWINCH
signals (i.e. not stop in gdb when that happens).

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

From pinedev@shivax2.cac.washington.edu Fri Jan  3 12:55:57 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Jan 2003 12:55:57 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03Ktu2U000808;
	Fri, 3 Jan 2003 12:55:56 -0800
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.12) with ESMTP id h03KtoHh024419
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 3 Jan 2003 12:55:51 -0800
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.12) with SMTP id h03KsUDb083808;
	Fri, 3 Jan 2003 12:54:30 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03KqTCK044996
	for <pine-info@reallists.u.washington.edu>; Fri, 3 Jan 2003 12:52:29 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03KqRAp031210
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 12:52:27 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03KqPcu002661;
	Fri, 3 Jan 2003 12:52:25 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h03KqMEo024291
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Fri, 3 Jan 2003 12:52:25 -0800
Message-Id: <Pine.LNX.4.52.0301031245480.24704@pigeon.cac.washington.edu>
Date: Fri, 3 Jan 2003 12:52:21 -0800 (PST)
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: 4.51 Can't delete IMAP incoming mailbox
In-Reply-To: <Pine.GSO.4.51.0301031227520.1660@neingv.pbybenqb.rqh>
References: <20021225115006.Q8041-100000@aslan.narnia.pp.se>
 <Pine.GSO.4.51.0301021647180.355@neingv.pbybenqb.rqh>
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 Fri, 3 Jan 2003, Susan Dorsey wrote:

> Pine 4.40 would allow this, as would 4.50, but with all the 4.51 builds
> we've done, the [d]elete command returns:
>
>    [Deletion cancelled: folder not in editable config file]
>
> The incoming folders work fine with SSL -- they just can't be removed once
> you set them up (except by editing the .pinerc file, which most of our
> users can't handle).
>
> Bug?  Feature?  Build error?

Hi Susan,

This is indeed a bug that got introduced between 4.50 and 4.51.  It will
be fixed in 4.52, which will be out in the near future.

Jeff

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

From pinedev@shivax2.cac.washington.edu Fri Jan  3 17:00:14 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Jan 2003 17:00:14 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0410D2U009274;
	Fri, 3 Jan 2003 17:00:13 -0800
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.12) with ESMTP id h04109qe010689
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 3 Jan 2003 17:00:10 -0800
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.12) with SMTP id h040xMll019000;
	Fri, 3 Jan 2003 16:59:23 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h040waCK004924
	for <pine-info@reallists.u.washington.edu>; Fri, 3 Jan 2003 16:58:36 -0800
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h040wZJV001514
	for <pine-info@u.washington.edu>; Fri, 3 Jan 2003 16:58:35 -0800
Received: (qmail 10906 invoked by uid 1828); 4 Jan 2003 00:58:35 -0000
Message-Id: <Pine.GSO.4.33.0301031655390.28533-100000@vax.hanford.org>
Date: Fri, 3 Jan 2003 16:58:34 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: select _threads_ with new messages?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXXIIIIIII, Probability=37%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXIIIIIIIII, Probability=29%, Report="NO_MX_FOR_FROM, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Is there some way I can do the analog of ";sn" but select entire threads
with new messages?  (i.e. show me entire threads, including old messages,
when the thread has at least one new message..)

This would make cleaning up old mail (i.e. discussions over several days or
more) easier..    If threads with new messages always showed up at the bottom
of the list, this would be less necessary but still useful.

This is from a person with 2018 messages in their INBOX..

mattack@vax.hanford.org

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

From pinedev@shivax2.cac.washington.edu Mon Jan  6 05:35:17 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 6 Jan 2003 05:35:17 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h06DZH2U018899;
	Mon, 6 Jan 2003 05:35:17 -0800
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.12) with ESMTP id h06DZCHh003608
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 6 Jan 2003 05:35:13 -0800
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.12) with SMTP id h06DYMDb089086;
	Mon, 6 Jan 2003 05:34:22 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h06DVUCK028016
	for <pine-info@reallists.u.washington.edu>; Mon, 6 Jan 2003 05:31:30 -0800
Received: from it.theadamsfamily.net (it.theadamsfamily.net [165.254.118.24])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h06DVSBg009378
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Mon, 6 Jan 2003 05:31:29 -0800
Received: from it.theadamsfamily.net (localhost.theadamsfamily.net [IPv6:::1])
	by it.theadamsfamily.net (8.12.2/8.12.2) with ESMTP id h06DOvPP016954
	for <pine-info@u.washington.edu>; Mon, 6 Jan 2003 05:24:57 -0800 (PST)
Received: from localhost (erek@localhost)
	by it.theadamsfamily.net (8.12.2/8.12.2/Submit) with ESMTP id h06DOve8014309
	for <pine-info@u.washington.edu>; Mon, 6 Jan 2003 08:24:57 -0500 (EST)
Message-Id: <Pine.BSO.4.51.0301060800370.10125@it.theadamsfamily.net>
Date: Mon, 6 Jan 2003 08:24:57 -0500 (EST)
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: Erek Adams <erek@theadamsfamily.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Odd behavior with remote collection/folder
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-message-flag: Outlook is evil.
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=II, Probability=2%, Report="SPAM_PHRASE_00_01, USER_AGENT_PINE"


Ok I might be crazy, but...

  I'm using roles and in that role (fred), everything w/regards to it is
working fine.  Not a problem.  But, I decided to add fred's remote INBOX
as a collection and I'm not getting the behavior that I expect.  I access
the collection and find 'INBOX.' as the only folder listed.  When I try to
access that as a regular folder, I get a listing of 'sub-folders?'
('Trash') and nothing else listed.  No messages at all.

  If I use another .pinerc with the remote foler set as my INBOX, then I
can see and access anything there.

I've read thru the FAQ, but nothing I saw there really seemed to match my
problem.

Confusion, Feature, Bug, Idiot?  ;-)

Thanks!

-----
Erek Adams
Nifty-Type-Guy
TheAdamsFamily.Net
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From pinedev@shivax2.cac.washington.edu Tue Jan  7 15:11:09 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Jan 2003 15:11:09 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07NB82U016371;
	Tue, 7 Jan 2003 15:11:08 -0800
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.12) with ESMTP id h07NAPHh028479
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 7 Jan 2003 15:10:27 -0800
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.12) with SMTP id h07N7MDb094970;
	Tue, 7 Jan 2003 15:07:23 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07N69CK044246
	for <pine-info@reallists.u.washington.edu>; Tue, 7 Jan 2003 15:06:09 -0800
Received: from julip.fcgov.com (julip.fcgov.com [198.59.47.14])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07N5qR7001473
	for <pine-info@u.washington.edu>; Tue, 7 Jan 2003 15:05:56 -0800
Received: from localhost (gyger@localhost)
	by julip.fcgov.com (8.9.3 (PHNE_25183)/8.9.3) with ESMTP id QAA14334
	for <pine-info@u.washington.edu>; Tue, 7 Jan 2003 16:05:48 -0700 (MST)
Message-Id: <Pine.HPX.4.44.0301071559290.13100-100000@julip.fcgov.com>
Date: Tue, 7 Jan 2003 16:05:48 -0700 (MST)
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: Carol Gyger <gyger@julip.fcgov.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Harvesting emails by date
In-Reply-To: <Pine.LNX.4.30.0212061640480.24973-100000@franklin.wrl.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I would like to "harvest" all my messages from all my folders based on
date.  Ideally, they would all gather into one folder so I could examine
and ultimately delete.  For example, I would like to gather up all the
messages that are at least 90 days old.

Do you have any suggestions about an efficient way to accomplish this?  I
am using Pine 4.44.

Thank you,
cg

Carol Gyger
Systems Administrator
Fort Collins Public Library
201 Peterson St.
Fort Collins CO  80524
(970)221-6716
gyger@julip.fcgov.com


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

From pinedev@shivax2.cac.washington.edu Tue Jan  7 18:04:00 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Jan 2003 18:04:00 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0823x2U021905;
	Tue, 7 Jan 2003 18:03:59 -0800
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.12) with ESMTP id h0823Gqe015323
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 7 Jan 2003 18:03:16 -0800
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.12) with SMTP id h0822909015408;
	Tue, 7 Jan 2003 18:02:09 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0821NCK018908
	for <pine-info@reallists.u.washington.edu>; Tue, 7 Jan 2003 18:01:23 -0800
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.12) with SMTP id h0821LtB021748
	for <pine-info@u.washington.edu>; Tue, 7 Jan 2003 18:01:21 -0800
Received: (qmail 25818 invoked by uid 1828); 8 Jan 2003 02:01:20 -0000
Message-Id: <Pine.GSO.4.33.0301071757350.12465-100000@vax.hanford.org>
Date: Tue, 7 Jan 2003 18:01:20 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Harvesting emails by date
In-Reply-To: <Pine.HPX.4.44.0301071559290.13100-100000@julip.fcgov.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Carol Gyger <gyger@julip.fcgov.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXIIIIIIIII, Probability=29%, Report="IN_REP_TO, NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXIIIIIIIII, Probability=29%, Report="IN_REP_TO, NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 7 Jan 2003, Carol Gyger wrote:
>I would like to "harvest" all my messages from all my folders based on
>date.  Ideally, they would all gather into one folder so I could examine
>and ultimately delete.  For example, I would like to gather up all the
>messages that are at least 90 days old.
>
>Do you have any suggestions about an efficient way to accomplish this?  I
>am using Pine 4.44.

Awesome.. your question made me learn a new feature of pine..

In the Index, you can ; (select) by Date..

At first I thought that it was only "sent since <date>".. but ^W
changes the criteria that the date is used for..

e.g.
SENT SINCE
SENT BEFORE
SENT ON
ARRIVED SINCE
ARRIVED BEFORE
ARRIVED ON

While there doesn't seem to be any easy way of selecting '90 days' (like you
can't type -90 or something), you could just manually go back a few months,
or masochistically type/paste 90 ^P chars.

Is this what you meant?


From pinedev@shivax2.cac.washington.edu Wed Jan  8 08:48:35 2003 -0800
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Jan 2003 08:48:35 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08GmY2U012446;
	Wed, 8 Jan 2003 08:48:34 -0800
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.12) with ESMTP id h08GmNHh020346
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 8 Jan 2003 08:48:24 -0800
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.12) with SMTP id h08GlVDb083292;
	Wed, 8 Jan 2003 08:47:31 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08GkYCK025300
	for <pine-info@reallists.u.washington.edu>; Wed, 8 Jan 2003 08:46:34 -0800
Received: from julip.fcgov.com (julip.fcgov.com [198.59.47.14])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08GkQ7t013958
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 08:46:26 -0800
Received: from localhost (gyger@localhost)
	by julip.fcgov.com (8.9.3 (PHNE_25183)/8.9.3) with ESMTP id JAA17597;
	Wed, 8 Jan 2003 09:45:56 -0700 (MST)
Message-Id: <Pine.HPX.4.44.0301080943580.17271-100000@julip.fcgov.com>
Date: Wed, 8 Jan 2003 09:45:56 -0700 (MST)
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: Carol Gyger <gyger@julip.fcgov.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Harvesting emails by date
In-Reply-To: <Pine.GSO.4.33.0301071757350.12465-100000@vax.hanford.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Matt Ackeret <mattack@vax.hanford.org>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Matt,

Thank you.  Yes, I find this feature quite useful.  I wondered if there
was a way to not have to go into each folder to find old emails.

Still searching for a way. :-)

cg

Carol Gyger
Systems Administrator
Fort Collins Public Library
201 Peterson St.
Fort Collins CO  80524
(970)221-6716
gyger@julip.fcgov.com

On Tue, 7 Jan 2003, Matt Ackeret wrote:

> On Tue, 7 Jan 2003, Carol Gyger wrote:
> >I would like to "harvest" all my messages from all my folders based on
> >date.  Ideally, they would all gather into one folder so I could examine
> >and ultimately delete.  For example, I would like to gather up all the
> >messages that are at least 90 days old.
> >
> >Do you have any suggestions about an efficient way to accomplish this?  I
> >am using Pine 4.44.
>
> Awesome.. your question made me learn a new feature of pine..
>
> In the Index, you can ; (select) by Date..
>
> At first I thought that it was only "sent since <date>".. but ^W
> changes the criteria that the date is used for..
>
> e.g.
> SENT SINCE
> SENT BEFORE
> SENT ON
> ARRIVED SINCE
> ARRIVED BEFORE
> ARRIVED ON
>
> While there doesn't seem to be any easy way of selecting '90 days' (like you
> can't type -90 or something), you could just manually go back a few months,
> or masochistically type/paste 90 ^P chars.
>
> Is this what you meant?
>
>


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, 8 Jan 2003 09:12:06 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08HC62U013452;
	Wed, 8 Jan 2003 09:12:06 -0800
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.12) with ESMTP id h08HBmHh021113
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 8 Jan 2003 09:11:50 -0800
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.12) with SMTP id h08HAAll014334;
	Wed, 8 Jan 2003 09:10:10 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08H9YCK017306
	for <pine-info@reallists.u.washington.edu>; Wed, 8 Jan 2003 09:09:35 -0800
Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08H9LJW013599
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 09:09:22 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08H9KOj017972
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 09:09:20 -0800
Received: from [10.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08H9KEo000834
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 09:09:20 -0800
Message-Id: <Pine.WNT.4.52.0301080907280.1836@hubertw2k2_ndc.nebula.washington.edu>
Date: Wed, 8 Jan 2003 09:09:20 -0800 (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: Harvesting emails by date
In-Reply-To: <Pine.HPX.4.44.0301071559290.13100-100000@julip.fcgov.com>
References: <Pine.HPX.4.44.0301071559290.13100-100000@julip.fcgov.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Versions of pine >= 4.50 have a new feature in Rules/Filters that will
allow you to select messages based on their age. 4.44 does not have this.
This would allow you to create rules which move old mail from one folder
to another whenever you open the folder.

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

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, 8 Jan 2003 10:06:27 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08I6Q2U015854;
	Wed, 8 Jan 2003 10:06:26 -0800
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.12) with ESMTP id h08I6DHh022806
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 8 Jan 2003 10:06:13 -0800
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.12) with SMTP id h08I4b09033142;
	Wed, 8 Jan 2003 10:04:37 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08I3nCK010064
	for <pine-info@reallists.u.washington.edu>; Wed, 8 Jan 2003 10:03:49 -0800
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.12) with ESMTP id h08I3jcO010452
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 10:03:46 -0800
Received: from 213-78-89-168.friaco.onetel.net.uk (213-78-89-168.friaco.onetel.net.uk [213.78.89.168])
	by msgdirector2.onetel.net.uk (Mirapoint)
	with ESMTP id AOH54825;
	Wed, 8 Jan 2003 18:01:32 GMT
Message-Id: <Pine.OSX.4.51.9.0301081800540.411@ybpnyubfg>
Date: Wed, 8 Jan 2003 18:04:43 +0000 (GMT)
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: Harvesting emails by date
In-Reply-To: <Pine.WNT.4.52.0301080907280.1836@hubertw2k2_ndc.nebula.washington.edu>
References: <Pine.HPX.4.44.0301071559290.13100-100000@julip.fcgov.com>
 <Pine.WNT.4.52.0301080907280.1836@hubertw2k2_ndc.nebula.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-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 8 Jan 2003 Steve Hubert (hubert@washington.edu) wrote:
>
> Versions of pine >= 4.50 have a new feature in Rules/Filters that will
> allow you to select messages based on their age. 4.44 does not have this.
> This would allow you to create rules which move old mail from one folder
> to another whenever you open the folder.


Hi Steve,

Can you explain what Age setting you use to do that? I have a lot
of filters set up to do that and currently I use this condition


 Message is Recent? =
            Set    Choose One
            ---  --------------------
            ( )  Don't care, always matches
            ( )  Yes
            (*)  No


But I'm curious to learn about alternate ways.

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 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, 8 Jan 2003 11:19:43 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08JJg2U019483;
	Wed, 8 Jan 2003 11:19:42 -0800
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.12) with ESMTP id h08JJcqe007865
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 8 Jan 2003 11:19:39 -0800
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.12) with SMTP id h08JII09024054;
	Wed, 8 Jan 2003 11:18:18 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08JGICK042974
	for <pine-info@reallists.u.washington.edu>; Wed, 8 Jan 2003 11:16:18 -0800
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.12) with ESMTP id h08JGFcO006953
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 11:16:16 -0800
Received: from rigel (rigel.cse.sc.edu [129.252.130.115])
	by moultrie.cse.sc.edu (Postfix) with ESMTP id 4A68F1E4A3
	for <pine-info@u.washington.edu>; Wed,  8 Jan 2003 14:14:30 -0500 (EST)
Message-Id: <Pine.GSO.4.51.0301081309090.3153@rigel>
Date: Wed, 8 Jan 2003 13:14:30 -0600 (CST)
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@cse.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Harvesting emails by date
In-Reply-To: <Pine.OSX.4.51.9.0301081800540.411@ybpnyubfg>
References: <Pine.HPX.4.44.0301071559290.13100-100000@julip.fcgov.com>
 <Pine.WNT.4.52.0301080907280.1836@hubertw2k2_ndc.nebula.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: gopalan@rigel
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 8 Jan 2003, Nancy McGough wrote:

> Can you explain what Age setting you use to do that?

In the Filter Setup screen,

    Age interval = 90,INF

will match any message that is 90 days or older.

-- 
Gopi Sundaram
http://www.zrox.net/Mail/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, 8 Jan 2003 12:22:36 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08KMZ2U021937;
	Wed, 8 Jan 2003 12:22:35 -0800
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.12) with ESMTP id h08KMUHh028148
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 8 Jan 2003 12:22:31 -0800
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.12) with SMTP id h08KLP09006842;
	Wed, 8 Jan 2003 12:21:26 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08KKnCK033570
	for <pine-info@reallists.u.washington.edu>; Wed, 8 Jan 2003 12:20:49 -0800
Received: from vir1.relay.fluke.com (vir1.relay.fluke.com [129.196.184.25])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h08KKjG0018143
	for <pine-info@u.washington.edu>; Wed, 8 Jan 2003 12:20:46 -0800
Received: from dd.tc.fluke.com ([129.196.148.100]) by vir1.relay.fluke.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 12:20:45 -0800
Received: (from dcd@localhost) by dd.tc.fluke.com (8.8.5/8.6.12) id MAA19261 for pine-info@u.washington.edu; Wed, 8 Jan 2003 12:20:47 -0800
Message-Id: <200301082020.MAA19261@dd.tc.fluke.com>
Date: Wed, 08 Jan 2003 04:13:12 -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: dcd@tc.fluke.com
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: pine text/html formatted when read from IMAP, but not from file
Content-type: text/html
X-OriginalArrivalTime: 08 Jan 2003 20:20:45.0570 (UTC) FILETIME=[6CD28620:01C2B753]
X-Uwash-Spam: Gauge=XXXIIII, Probability=34%, Report="CTYPE_JUST_HTML, DATE_IN_PAST_06_12, NO_REAL_NAME, SPAM_PHRASE_00_01, __CTYPE_IS_HTML"
X-Uwash-Spam: Gauge=XXIIIIII, Probability=26%, Report="CTYPE_JUST_HTML, DATE_IN_PAST_06_12, NO_REAL_NAME, __CTYPE_IS_HTML"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

text/html mail viewed differently from IMAP<br><b>Is this a pine bug?</b><br>
<a href=http://www.washington.edu/pine/>http://www.washington.edu/pine/</a><br><br>
Pine's viewer seems to display content-type based email<br> in a more readable fashion when I read the email served from an IMAP server<br>
If I save the email to a folder<br> and try to view it with pine, it is no longer formatted as expected<br> but if I use pine to bounce the mail back to the imap server,<br> the same message is displayed in a readable fashion by pine again.<br> <br><br>I've tried to create a simple text message above that shows<br> the problem<br>
-- 
-----------------------------------------------------------------
 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, 9 Jan 2003 12:10:12 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09KAC2U031507;
	Thu, 9 Jan 2003 12:10:12 -0800
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.12) with ESMTP id h09KA7Hh031450
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 9 Jan 2003 12:10:07 -0800
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.12) with SMTP id h09K8Ell016718;
	Thu, 9 Jan 2003 12:08:14 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09K6YCK041260
	for <pine-info@reallists.u.washington.edu>; Thu, 9 Jan 2003 12:06:34 -0800
Received: from mail.laszlosystems.com (hosts.laszlosystems.com [66.134.142.129])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09K6XCb016013
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 12:06:33 -0800
Received: from ([])
        by mail.laszlosystems.com (Merak 4.4.2) with SMTP id LVD36896
        for <pine-info@u.washington.edu>; Thu, 09 Jan 2003 12:02:08 -0800
Message-Id: <Pine.WNT.4.51.0301091156170.220@laszlo-awolff>
Date: Thu, 9 Jan 2003 12:02:02 -0800 (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: Adam Wolff <awolff@laszlosystems.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: using select->text
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: awolff@mail.laszlosystems.com
X-Uwash-Spam: Gauge=II, Probability=2%, Report="SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi.
I'm a pine newbie using PC-Pine 4.51. I like it a lot. I'm having some
problems, though and I couldn't find help on the web or in the archives.

Right now, the biggest problem is that using select->text isn't working
for me.

If I go to my Inbox, and hit
 ;ts^X
 (select text current subject)

nothing is selected. One would think that at least the current message
would be selected. All of the other kinds of selection (date, number, size
, etc) work, but none of the text ones do.

My inbox is my imap/Inbox

Thanks in advance!
Adam Wolff
-- 
-----------------------------------------------------------------
 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, 9 Jan 2003 12:51:14 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09KpE2U000670;
	Thu, 9 Jan 2003 12:51:14 -0800
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.12) with ESMTP id h09Kp9qe016053
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 9 Jan 2003 12:51:10 -0800
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.12) with SMTP id h09KnJ09025658;
	Thu, 9 Jan 2003 12:49:19 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09KmSCK021050
	for <pine-info@reallists.u.washington.edu>; Thu, 9 Jan 2003 12:48:28 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09KmNGO029028
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 12:48:25 -0800
Received: from localhost (dufberg@localhost)
	by aslan.narnia.pp.se (8.11.3/8.11.3) with ESMTP id h09KmHa28941;
	Thu, 9 Jan 2003 21:48:18 +0100 (CET)
	(envelope-from dufberg@narnia.pp.se)
Message-Id: <20030109214703.X14571-100000@aslan.narnia.pp.se>
Date: Thu, 9 Jan 2003 21:48:17 +0100 (CET)
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: Mats Dufberg <dufberg@narnia.pp.se>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: using select->text
In-Reply-To: <Pine.WNT.4.51.0301091156170.220@laszlo-awolff>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Adam Wolff <awolff@laszlosystems.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Jan 9, 2003, 12:02 (-0800) Adam Wolff <awolff@laszlosystems.com> wrote:

> Right now, the biggest problem is that using select->text isn't working
> for me.
>
> If I go to my Inbox, and hit
>  ;ts^X
>  (select text current subject)
>
> nothing is selected. One would think that at least the current message
> would be selected. All of the other kinds of selection (date, number, size
> , etc) work, but none of the text ones do.

Could it be that ^X is taken by something else?

If you do

$ stty -a

will then something be "atached" to ^X?



Mats

-----------------------------------------------------------------
Mats Dufberg                                 dufberg@narnia.pp.se
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588


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, 9 Jan 2003 13:19:48 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09LJl2U001800;
	Thu, 9 Jan 2003 13:19:47 -0800
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.12) with ESMTP id h09LJhqe016881
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 9 Jan 2003 13:19:43 -0800
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.12) with SMTP id h09LIb09023660;
	Thu, 9 Jan 2003 13:18:37 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09LHuCK015228
	for <pine-info@reallists.u.washington.edu>; Thu, 9 Jan 2003 13:17:57 -0800
Received: from mail.laszlosystems.com (hosts.laszlosystems.com [66.134.142.129])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09LHrCh026916
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 13:17:54 -0800
Received: from ([])
        by mail.laszlosystems.com (Merak 4.4.2) with SMTP id LVD36896;
        Thu, 09 Jan 2003 13:13:28 -0800
Message-Id: <Pine.WNT.4.51.0301091312050.220@laszlo-awolff>
Date: Thu, 9 Jan 2003 13:13:22 -0800 (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: Adam Wolff <awolff@laszlosystems.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: using select->text
In-Reply-To: <20030109214703.X14571-100000@aslan.narnia.pp.se>
References: <20030109214703.X14571-100000@aslan.narnia.pp.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mats Dufberg <dufberg@narnia.pp.se>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: awolff@mail.laszlosystems.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

No, I'm afraid that's not it -- I just used ^X as an example. I can't get
text search to work no matter what I search for.

Adam

On Thu, 9 Jan 2003, Mats Dufberg wrote:

> On Jan 9, 2003, 12:02 (-0800) Adam Wolff <awolff@laszlosystems.com> wrote:
>
> > Right now, the biggest problem is that using select->text isn't working
> > for me.
> >
> > If I go to my Inbox, and hit
> >  ;ts^X
> >  (select text current subject)
> >
> > nothing is selected. One would think that at least the current message
> > would be selected. All of the other kinds of selection (date, number, size
> > , etc) work, but none of the text ones do.
>
> Could it be that ^X is taken by something else?
>
> If you do
>
> $ stty -a
>
> will then something be "atached" to ^X?
>
>
>
> Mats
>
> -----------------------------------------------------------------
> Mats Dufberg                                 dufberg@narnia.pp.se
> Blaoarvsgraend 42                                  +46-8-38 48 59
> SE-162 45 Vaellingby, Sweden                      +46-70-258 2588
>
>

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, 9 Jan 2003 16:52:03 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A0q32U010332;
	Thu, 9 Jan 2003 16:52:03 -0800
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.12) with ESMTP id h0A0pxHh008326
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 9 Jan 2003 16:52:00 -0800
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.12) with SMTP id h0A0p4ll026204;
	Thu, 9 Jan 2003 16:51:05 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A0oPCK037438
	for <pine-info@reallists.u.washington.edu>; Thu, 9 Jan 2003 16:50:25 -0800
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A0oNCc009471
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 16:50:23 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A0oMAc012273
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 16:50:22 -0800
Received: from [10.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A0oLEo001649
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 16:50:21 -0800
Message-Id: <Pine.WNT.4.52.0301091649420.11648@hubertw2k2_ndc.nebula.washington.edu>
Date: Thu, 9 Jan 2003 16:50:21 -0800 (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: using select->text
In-Reply-To: <Pine.WNT.4.51.0301091312050.220@laszlo-awolff>
References: <20030109214703.X14571-100000@aslan.narnia.pp.se>
 <Pine.WNT.4.51.0301091312050.220@laszlo-awolff>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

You might try running "pine -d9", doing the search, then check the debug
file for illuminating comments.

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

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, 9 Jan 2003 17:31:12 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1VB2U011542;
	Thu, 9 Jan 2003 17:31:11 -0800
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.12) with ESMTP id h0A1V8qe025126
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 9 Jan 2003 17:31:09 -0800
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.12) with SMTP id h0A1URDb020556;
	Thu, 9 Jan 2003 17:30:28 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1TmCK044596
	for <pine-info@reallists.u.washington.edu>; Thu, 9 Jan 2003 17:29:48 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1TUGS018490
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
	for <pine-info@u.washington.edu>; Thu, 9 Jan 2003 17:29:46 -0800
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.12) with ESMTP id h0A1TQqe025081
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 9 Jan 2003 17:29:27 -0800
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.12) with SMTP id h0A1Si09014928;
	Thu, 9 Jan 2003 17:28:44 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A16FCK013148
	for <pine-announce@reallists.u.washington.edu>; Thu, 9 Jan 2003 17:06:15 -0800
Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A16DGO012896
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-announce@u.washington.edu>; Thu, 9 Jan 2003 17:06:13 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A16COj030866
	for <pine-announce@u.washington.edu>; Thu, 9 Jan 2003 17:06:12 -0800
Received: from [10.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A16CEo002698
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <pine-announce@u.washington.edu>; Thu, 9 Jan 2003 17:06:12 -0800
Message-Id: <Pine.WNT.4.52.0301091631540.12764@hubertw2k2_ndc.nebula.washington.edu>
Date: Thu, 9 Jan 2003 17:06:12 -0800 (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: Pine 4.52 is now available
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: PINE-ANNOUNCE-owner@u.washington.edu
X-To: Pine Announcement List <pine-announce@u.washington.edu>
X-Sender: hubert@ndcms.cac.washington.edu
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="INVALID_MSGID, SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="INVALID_MSGID, SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="INVALID_MSGID, SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This note is to announce the availability of the Pine Message System
version 4.52. This release does not introduce major new functionality.
Instead, it addresses bugs found in earlier versions.

Specific information about changes can be found in the built-in release
notes ("R" off the Main Menu), or via any of:

        http://www.washington.edu/pine/

        http://www.washington.edu/pine/changes.html

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


UNIX source code for the latest Pine release is available at:

        http://www.washington.edu/pine/getpine/
or
        ftp://ftp.cac.washington.edu/pine/pine.tar.gz
              (MD5: 4828f048c6ebd60e622368cbc2ad6056)
        ftp://ftp.cac.washington.edu/pine/pine.tar.Z
              (MD5: 2b2f3e32787f2194b1261178ef9c0628)
        ftp://ftp.cac.washington.edu/pine/pine.tar.bz2
              (MD5: cbdd475ebe0cb712350e3cb15643ecea)

We are no longer distributing binaries which don't have encryption
capabilities built in. Pre-built binaries are available for a small number
of UNIX operating environments for citizens of the U.S. or Canada via:

        http://www.washington.edu/pine/getpine/

The PC-Pine distribution is also available at the above url, or at:

        ftp://ftp.cac.washington.edu/pine/pcpine/pm452w32.zip
              (MD5: 8d638557370348604083b8d14efae340)

As with all Pine releases, it is important that you carefully test and
determine for yourself that it performs suitably in your environment
before placing Pine into production use.

The Pine Development Team
-- 
-------------------------------------------------------------
 For information about this mailing list, see: 
 http://www.washington.edu/pine/pine-info/pine-announce.html
-------------------------------------------------------------
-- 
-------------------------------------------------------------
 For information about this mailing list, see: 
 http://www.washington.edu/pine/pine-info/pine-announce.html
-------------------------------------------------------------

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, 10 Jan 2003 13:50:06 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ALo52U015434;
	Fri, 10 Jan 2003 13:50:05 -0800
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.12) with ESMTP id h0ALo1qe022961
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 10 Jan 2003 13:50:02 -0800
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.12) with SMTP id h0ALnADb085984;
	Fri, 10 Jan 2003 13:49:10 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ALkTCK027432
	for <pine-info@reallists.u.washington.edu>; Fri, 10 Jan 2003 13:46:29 -0800
Received: from claven.astro.princeton.edu (claven.astro.Princeton.EDU [128.112.25.10])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ALkQGN031020
	for <pine-info@u.washington.edu>; Fri, 10 Jan 2003 13:46:27 -0800
Received: from xanadu (IDENT:huston@xanadu [128.112.24.13])
	by claven.astro.princeton.edu (8.11.6/8.11.6) with ESMTP id h0ALkQF13896
	for <pine-info@u.washington.edu>; Fri, 10 Jan 2003 16:46:26 -0500
Message-Id: <Pine.LNX.4.44.0301101639500.16920-100000@xanadu.astro.Princeton.EDU>
Date: Fri, 10 Jan 2003 16:46:26 -0500 (EST)
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 Huston <huston@astro.princeton.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: sslfailure on TLS with Cyrus
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=II, Probability=2%, Report="SPAM_PHRASE_00_01, USER_AGENT_PINE"

I'm setting up a new Cyrus IMAPD server in testing, and have an odd problem.

If I try to connect normally with Pine 4.44, it will try to escalate the
connection up with TLS, and fails with "SSL negotiation failed".  Debugging
information isn't very useful ("sslfailure: host=diomedes reason=SSL
negotiation failed").  If, however, I tell it to use SSL on port 993, it works
fine (except for the self-signed cert, which I'm not worried about on a test
server).  I can use TLS with Mozilla or Apple's "Mail" program, so I'm not
thinking it's a problem with the Cyrus setup, but I'm stumped.  I've even
setup the cert to be trusted (symlink with hash name in /usr/share/ssl/certs)
but that doesn't seem to have helped.

While I could make the global default to connect with /ssl to the new server,
we have a handful of versions of Pine on the network (oldest is 4.3x I think),
and not all of them support encryption.  Ideally I'd like to have one file on
the network which is symlinked to for all versions of pine, and I could see
this becoming as much of a headache as when we installed the self-signed cert
on our server and having to add /novalidate-cert to half the machines.

Anyone with an idea how I can get a more meaningful error than "negotiation
failed" out of Pine, or Cyrus?  

-- 
Steve Huston - Unix Systems Administrator, Dept. of Astrophysical Sciences
 Princeton University  |     ICBM Address: 40.346525   -74.651285
   126 Peyton Hall     |"On my ship, the Rocinante, wheeling through
 Princeton, NJ   08544 | the galaxies; headed for the heart of Cygnus,
   (609) 258-7375      | headlong into mystery."  -Rush, 'Cygnus X-1'

-- 
-----------------------------------------------------------------
 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, 12 Jan 2003 11:44:07 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0CJi62U014261;
	Sun, 12 Jan 2003 11:44:06 -0800
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.12) with ESMTP id h0CJi2qe016206
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 12 Jan 2003 11:44:03 -0800
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.12) with SMTP id h0CJh3Db083234;
	Sun, 12 Jan 2003 11:43:03 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0CJe8CK018832
	for <pine-info@reallists.u.washington.edu>; Sun, 12 Jan 2003 11:40:08 -0800
Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0CJe6Cb020822
	for <pine-info@u.washington.edu>; Sun, 12 Jan 2003 11:40:06 -0800
Received: from h-68-164-27-189.snvacaid.covad.net ([68.164.27.189] helo=Adam-Think)
	by granger.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 18Xnxl-0001Sj-00
	for pine-info@u.washington.edu; Sun, 12 Jan 2003 14:40:05 -0500
Message-Id: <Pine.WNT.4.52.0301121131120.1888@Adam-Think>
Date: Sun, 12 Jan 2003 11:40:11 -0800 (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: Adam Wolff <awolff@laszlosystems.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: pine instability/crash (fwd)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: awolff@mail.laszlosystems.com
X-Uwash-Spam: Gauge=XII, Probability=12%, Report="LINES_OF_YELLING, LINES_OF_YELLING_2, LINES_OF_YELLING_3, SPAM_PHRASE_00_01, SUPERLONG_LINE, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=II, Probability=2%, Report="LINES_OF_YELLING, LINES_OF_YELLING_2, LINES_OF_YELLING_3, SUPERLONG_LINE, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Using PC-Pine 4.52, I can read my mail for a while and move around my mailboxes, but at some point reading actual messages stops working.

That is, I see the list of messages fine in my inbox, but then when I go to read a message (right arrow) the body text is empty (though the headers are correct.) If I don't quit the program at this point, it'll crash soon thereafter.

I've included some logs below, annotated with *****. Any help or insight would be appreciated!
Thanks,
Adam Wolff

*****Here's the log of no message being retrieved:
 -----  MAIL VIEW  -----

09:07:03.527
busy_alarm(1, Busy, 00000000, 0)

09:07:03.527
IMAP DEBUG 09:07:03.527: 00000066 FETCH 8 (BODYSTRUCTURE FLAGS)

09:07:03.527
IMAP 09:07:03 1/12 mm_log tcp: Writing to TCP

09:07:03.527
IMAP 09:07:03 1/12 mm_log tcp: successfully wrote to TCP

09:07:03.527
IMAP 09:07:03 1/12 mm_log tcp: Reading TCP data

09:07:03.567
IMAP 09:07:03 1/12 mm_log tcp: Successfully read TCP data

09:07:03.567
IMAP DEBUG 09:07:03.567: 00000066 OK FETCH Completed

09:07:03.567
IMAP DEBUG 09:07:03.567: 00000067 FETCH 8 BODY.PEEK[HEADER.FIELDS (Resent-Date Resent-From Resent-To Resent-cc Resent-Subject)]

09:07:03.567
IMAP 09:07:03 1/12 mm_log tcp: Writing to TCP

09:07:03.567
IMAP 09:07:03 1/12 mm_log tcp: successfully wrote to TCP

09:07:03.567
IMAP 09:07:03 1/12 mm_log tcp: Reading TCP data

09:07:03.597
IMAP 09:07:03 1/12 mm_log tcp: Successfully read TCP data

09:07:03.597
IMAP DEBUG 09:07:03.597: 00000067 OK FETCH Completed

09:07:03.597
-- gf_reset line_test

09:07:03.597
-- gf_reset wrap

09:07:03.597
-- gf_pipe:
09:07:03.597
suspend_busy_alarm

09:07:03.597
resume_busy_alarm

09:07:03.597
suspend_busy_alarm

09:07:03.597
resume_busy_alarm

09:07:03.597
suspend_busy_alarm

09:07:03.597
resume_busy_alarm

09:07:03.597
suspend_busy_alarm

09:07:03.597
resume_busy_alarm

09:07:03.597
suspend_busy_alarm

09:07:03.597
resume_busy_alarm

09:07:03.597
done.

09:07:03.597
IMAP DEBUG 09:07:03.597: 00000068 FETCH 8 BODY[TEXT]

09:07:03.627
IMAP 09:07:03 1/12 mm_log tcp: Writing to TCP

09:07:03.627
IMAP 09:07:03 1/12 mm_log tcp: successfully wrote to TCP

09:07:03.627
IMAP 09:07:03 1/12 mm_log tcp: Reading TCP data

09:07:03.657
IMAP 09:07:03 1/12 mm_log tcp: Successfully read TCP data

09:07:03.657
IMAP DEBUG 09:07:03.657: 00000068 OK FETCH Completed

09:07:03.657
suspend_busy_alarm

09:07:03.657
resume_busy_alarm

09:07:03.657
-- gf_reset line_test

09:07:03.657
-- gf_reset wrap

09:07:03.657
-- gf_pipe:
09:07:03.657
done.

09:07:03.657
cancel_busy_alarm(-1)

09:07:03.657
@@@@ current:8

09:07:03.657
set_titlebar - style: 3  current message cnt:1
09:07:03.657
  current_pl: 6  total_pl: 6

09:07:03.657
new mail called (0 0 1)

09:07:03.657
- adrbk_maintenance -

09:07:03.657
check_point(GoodTime)

09:07:03.657
freq 12 tm 420 changes 2 since_1st_change 226

09:07:03.657
since_status_chg 2260 chk_cnt_ave 4 (tenths)

09:07:03.657
adj_chk_cnt_ave 200 (tenths)

09:07:03.657
Check:if changes(2)xadj_cca(200) >= freq(12)x200

09:07:03.657
      is 400 >= 2400 ?

09:07:03.657
******** new mail returning -1  ********

09:07:03.657
q_status_message(ALL of message)

09:07:03.657
output_message(ALL of message)

09:07:03.657
STATUS cmd:120, max:1, min0

09:07:03.667
cancel_busy_alarm(-1)

*****here's the log of the crash
 -----  MAIL VIEW  -----

09:10:59.035
busy_alarm(1, Busy, 00000000, 0)

09:10:59.035
IMAP DEBUG 09:10:59.035: 00000073 FETCH 3 (BODYSTRUCTURE FLAGS)

09:10:59.035
IMAP 09:10:59 1/12 mm_log tcp: Writing to TCP

09:10:59.035
IMAP 09:10:59 1/12 mm_log tcp: successfully wrote to TCP

09:10:59.035
IMAP 09:10:59 1/12 mm_log tcp: Reading TCP data

09:10:59.065
IMAP 09:10:59 1/12 mm_log tcp: Successfully read TCP data

09:10:59.065
IMAP DEBUG 09:10:59.065: * 3 FETCH (FLAGS (\Seen) BODYSTRUCTURE)
-- 
-----------------------------------------------------------------
 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, 13 Jan 2003 04:14:38 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0DCEa2U002951;
	Mon, 13 Jan 2003 04:14:36 -0800
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.12) with ESMTP id h0DCETqe002084
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 13 Jan 2003 04:14:30 -0800
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.12) with SMTP id h0DCDbll004628;
	Mon, 13 Jan 2003 04:13:37 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0DCCUCK018844
	for <pine-info@reallists.u.washington.edu>; Mon, 13 Jan 2003 04:12:31 -0800
Received: from lantana.iitm.ernet.in (lantana.tenet.res.in [202.144.28.166])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0DCCMBl010280
	for <pine-info@u.washington.edu>; Mon, 13 Jan 2003 04:12:25 -0800
Received: from localhost (bharathi@localhost)
	by lantana.iitm.ernet.in (8.11.6/8.11.6) with ESMTP id h0DCCIT08944
	for <pine-info@u.washington.edu>; Mon, 13 Jan 2003 17:42:18 +0530
Message-Id: <Pine.LNX.4.44.0301131730540.8174-100000@lantana.iitm.ernet.in>
Date: Mon, 13 Jan 2003 17:42:18 +0530 (IST)
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: Bharathi S <bharathi@lantana.TeNeT.res.in>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Add Book
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: bharathi@lantana.TeNeT.res.in
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=XIII, Probability=13%, Report="MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_00_01, USER_AGENT_PINE"

Hello All,

  I want take a backup of my address book. 
  How to do it ?

  How to align the text properly ?
  ^J will not helping me to align the line, 
  when the line get warped by a last word.

Thanks,
-- 
Bharathi S, IndLinuX Team, (__)
DONLab,     TeNeT Group,   oo /
IIT-Madras, Chennai-INDIA. (_/\


-- 
-----------------------------------------------------------------
 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, 13 Jan 2003 10:12:28 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0DICS2U015116;
	Mon, 13 Jan 2003 10:12:28 -0800
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.12) with ESMTP id h0DICMHh029454
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 13 Jan 2003 10:12:23 -0800
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.12) with SMTP id h0DIBUjm035804;
	Mon, 13 Jan 2003 10:11:31 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0DIAaCK018900
	for <pine-info@reallists.u.washington.edu>; Mon, 13 Jan 2003 10:10:36 -0800
Received: from gort.cjb.net (c-24-126-16-90.we.client2.attbi.com [24.126.16.90])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0DIAZCh023260
	for <pine-info@u.washington.edu>; Mon, 13 Jan 2003 10:10:35 -0800
Received: from localhost (localhost [127.0.0.1])
	by gort.cjb.net (Postfix) with ESMTP id EEFFBA7AC
	for <pine-info@u.washington.edu>; Mon, 13 Jan 2003 10:08:57 -0800 (PST)
Message-Id: <Pine.LNX.4.50.0301131007090.15108-100000@gort.cjb.net>
Date: Mon, 13 Jan 2003 10:08:57 -0800 (PST)
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: Add Book
In-Reply-To: <Pine.LNX.4.44.0301131730540.8174-100000@lantana.iitm.ernet.in>
References: <Pine.LNX.4.44.0301131730540.8174-100000@lantana.iitm.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: satyap@gort.cjb.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Jan 13, 2003 at 17:42, Bharathi S wrote:

>  I want take a backup of my address book.
>  How to do it ?

The file .addressbook in your home directory contains the address
book. I have another file called .addressbook.lu, you might want to
back that up as well.

>  How to align the text properly ?
>  ^J will not helping me to align the line,
>  when the line get warped by a last word.

What do you mean? ^J reflows text.

-- 
Satya. <URL:http://satya.virtualave.net/>
I can't believe my computer's on fire.

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, 14 Jan 2003 15:08:32 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0EN8V2U014584;
	Tue, 14 Jan 2003 15:08:31 -0800
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.12) with ESMTP id h0EN8R1k029240
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 14 Jan 2003 15:08:27 -0800
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.12) with SMTP id h0EN5Z09023618;
	Tue, 14 Jan 2003 15:05:36 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0EN4CCK021898
	for <pine-info@reallists.u.washington.edu>; Tue, 14 Jan 2003 15:04:12 -0800
Received: from web13003.mail.yahoo.com (web13003.mail.yahoo.com [216.136.174.13])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0EN4AHj012982
	for <pine-info@u.washington.edu>; Tue, 14 Jan 2003 15:04:10 -0800
Received: from [129.252.26.96] by web13003.mail.yahoo.com via HTTP; Tue, 14 Jan 2003 15:04:09 PST
Message-Id: <20030114230409.37694.qmail@web13003.mail.yahoo.com>
Date: Tue, 14 Jan 2003 15:04:09 -0800 (PST)
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: Darshan Jayashekar <darshan_b_j@yahoo.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Auto Response Generator in pine!
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Uwash-Spam: Gauge=XXXII, Probability=32%, Report="DEAR_SOMEBODY, DEAR_SOMETHING, SPAM_PHRASE_00_01, __EVITE_CTYPE"
X-Uwash-Spam: Gauge=XXXII, Probability=32%, Report="DEAR_SOMEBODY, DEAR_SOMETHING, SPAM_PHRASE_00_01, __EVITE_CTYPE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Dear Sir/Madame,
	I am currently using pine4.44. I am trying to add an
auto reply (auto response generator) feature to it....
i would like to know if there is already a feature
that has been implemented into pine. If not... any
documentation or guidance to help me implement this
feature will be much appreciated.
Thanking you,
Sincerely,
Darshan Jayashekar.

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com
-- 
-----------------------------------------------------------------
 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; Tue, 14 Jan 2003 18:38:33 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0F2cX2U022570;
	Tue, 14 Jan 2003 18:38:33 -0800
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.12) with ESMTP id h0F2cNHh018207
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 14 Jan 2003 18:38:23 -0800
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.12) with SMTP id h0F2bBjm034678;
	Tue, 14 Jan 2003 18:37:11 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0F2aPCK035160
	for <pine-info@reallists.u.washington.edu>; Tue, 14 Jan 2003 18:36:25 -0800
Received: from web14810.mail.yahoo.com (web14810.mail.yahoo.com [216.136.224.231])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0F2aMBl019423
	for <pine-info@u.washington.edu>; Tue, 14 Jan 2003 18:36:23 -0800
Received: from [128.193.4.98] by web14810.mail.yahoo.com via HTTP; Tue, 14 Jan 2003 18:36:22 PST
Message-Id: <20030115023622.7312.qmail@web14810.mail.yahoo.com>
Date: Tue, 14 Jan 2003 18:36:22 -0800 (PST)
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: Tom Jenkins <tomjs98@yahoo.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Accessing different email accounts from command line
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Uwash-Spam: Gauge=XXI, Probability=21%, Report="FROM_ENDS_IN_NUMS, SPAM_PHRASE_00_01, __EVITE_CTYPE"
X-Uwash-Spam: Gauge=XXI, Probability=21%, Report="FROM_ENDS_IN_NUMS, SPAM_PHRASE_00_01, __EVITE_CTYPE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is there a way to tell pine to access another user's
email account provided that the user's correct
password is supplied?

Tom

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-- 
-----------------------------------------------------------------
 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, 15 Jan 2003 05:22:27 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FDMQTk008539;
	Wed, 15 Jan 2003 05:22:26 -0800
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.12) with ESMTP id h0FDMM1k016637
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 15 Jan 2003 05:22:23 -0800
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.12) with SMTP id h0FDLQDb094942;
	Wed, 15 Jan 2003 05:21:26 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FDJ4CK020152
	for <pine-info@reallists.u.washington.edu>; Wed, 15 Jan 2003 05:19:04 -0800
Received: from helios.geneseo.edu (helios.geneseo.edu [137.238.1.100])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FDJ2Q6014887
	for <pine-info@u.washington.edu>; Wed, 15 Jan 2003 05:19:02 -0800
Received: from mars.geneseo.edu (mars.geneseo.edu [137.238.1.104])
	by helios.geneseo.edu (8.12.5/8.12.5) with ESMTP id h0FDJ0HG006990;
	Wed, 15 Jan 2003 08:19:00 -0500 (EST)
Received: from mars.geneseo.edu (localhost.localdomain [127.0.0.1])
	by mars.geneseo.edu (8.12.5/8.12.5) with ESMTP id h0FDIwKM002507;
	Wed, 15 Jan 2003 08:18:58 -0500
Received: from localhost (valites@localhost)
	by mars.geneseo.edu (8.12.5/8.12.1/Submit) with ESMTP id h0FDIwFO002504;
	Wed, 15 Jan 2003 08:18:58 -0500
Message-Id: <Pine.LNX.4.44.0301150818350.2200-100000@mars.geneseo.edu>
Date: Wed, 15 Jan 2003 08:18:58 -0500 (EST)
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: Accessing different email accounts from command line
In-Reply-To: <20030115023622.7312.qmail@web14810.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Tom Jenkins <tomjs98@yahoo.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 14 Jan 2003, Tom Jenkins wrote:

> Is there a way to tell pine to access another user's
> email account provided that the user's correct
> password is supplied?

try pine -f <folder_name>

-- 
>--))> >--))>
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; Wed, 15 Jan 2003 10:51:02 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FIp1Tk019030;
	Wed, 15 Jan 2003 10:51:01 -0800
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.12) with ESMTP id h0FIoueG008856
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 15 Jan 2003 10:50:57 -0800
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.12) with SMTP id h0FInXll025638;
	Wed, 15 Jan 2003 10:49:34 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FIm8CK028456
	for <pine-info@reallists.u.washington.edu>; Wed, 15 Jan 2003 10:48:08 -0800
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.12) with SMTP id h0FIm6ZX014412
	for <pine-info@u.washington.edu>; Wed, 15 Jan 2003 10:48:07 -0800
Received: (qmail 15584 invoked by uid 1828); 15 Jan 2003 18:48:05 -0000
Message-Id: <Pine.GSO.4.33.0301151047520.12103-100000@vax.hanford.org>
Date: Wed, 15 Jan 2003 10:48:05 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Accessing different email accounts from command line
In-Reply-To: <20030115023622.7312.qmail@web14810.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Tom Jenkins <tomjs98@yahoo.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XX, Probability=20%, Report="IN_REP_TO, NO_MX_FOR_FROM, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XX, Probability=20%, Report="IN_REP_TO, NO_MX_FOR_FROM, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 14 Jan 2003, Tom Jenkins wrote:
>Is there a way to tell pine to access another user's
>email account provided that the user's correct
>password is supplied?

You could add different accounts in a 'collection list'.


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, 15 Jan 2003 17:42:06 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1g5Tk004252;
	Wed, 15 Jan 2003 17:42:05 -0800
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.12) with ESMTP id h0G1g11k008386
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 15 Jan 2003 17:42:03 -0800
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.12) with SMTP id h0G1fJll028568;
	Wed, 15 Jan 2003 17:41:19 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1eGCK044288
	for <pine-info@reallists.u.washington.edu>; Wed, 15 Jan 2003 17:40:17 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1dnHo015004
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
	for <pine-info@u.washington.edu>; Wed, 15 Jan 2003 17:40:14 -0800
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.12) with ESMTP id h0G1dd1k008333
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 15 Jan 2003 17:39:39 -0800
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.12) with SMTP id h0G1cQDb075516;
	Wed, 15 Jan 2003 17:38:27 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1GRCK043656
	for <pine-announce@reallists.u.washington.edu>; Wed, 15 Jan 2003 17:16:27 -0800
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1GPAe004392
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-announce@u.washington.edu>; Wed, 15 Jan 2003 17:16:25 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1GOhi010254
	for <pine-announce@u.washington.edu>; Wed, 15 Jan 2003 17:16:24 -0800
Received: from [10.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G1GOTZ004417
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <pine-announce@u.washington.edu>; Wed, 15 Jan 2003 17:16:24 -0800
Message-Id: <Pine.WNT.4.53.0301151151580.1336@hubertw2k2_ndc.nebula.washington.edu>
Date: Wed, 15 Jan 2003 17:16:24 -0800 (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: Pine 4.53 is now available
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: PINE-ANNOUNCE-owner@u.washington.edu
X-To: Pine Announcement List <pine-announce@u.washington.edu>
X-Sender: hubert@ndcms.cac.washington.edu
X-Uwash-Spam: Gauge=II, Probability=2%, Report="INVALID_MSGID, SPAM_PHRASE_02_03, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=II, Probability=2%, Report="INVALID_MSGID, SPAM_PHRASE_02_03, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=II, Probability=2%, Report="INVALID_MSGID, SPAM_PHRASE_02_03, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This note is to announce the availability of the Pine Message System
version 4.53. This release does not introduce any new functionality.
Instead, it addresses bugs found in earlier versions.

The reason for this quick release is a single bug which is present
in 4.50, 4.51, and 4.52:

  If a Filter Rule which does not Delete or Move a message (its Action is
  "Just Set Message Status") is followed by another Rule which does a Move
  or Delete, that second rule will be applied (if there is a match) even
  if the first rule matched.

The situation where this is most likely to come up is if you have a Filter
Rule which is a whitelist (a list of friendly From addresses) at the head
of your rules followed by other Filter Rules which Delete or Move spam.
The whitelisted mail will be incorrectly deleted or moved if it also
matches the spam criteria.

Independent of this, there was also a bug discovered in PC-Pine's MAPI
DLL. If you have not installed the pmapi32 package separately, you can
ignore the MAPI bug.

Specific information about changes can always be found in the built-in
release notes ("R" off the Main Menu), or via any of:

        http://www.washington.edu/pine/

        http://www.washington.edu/pine/changes.html

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


UNIX source code for the latest Pine release is available at:

        http://www.washington.edu/pine/getpine/
or
        ftp://ftp.cac.washington.edu/pine/pine.tar.gz
              (MD5: 17d2ae323d6012e69c33cf0168dff59b)
        ftp://ftp.cac.washington.edu/pine/pine.tar.Z
              (MD5: d0a8f459011225aeedd3b125b5b97e31)
        ftp://ftp.cac.washington.edu/pine/pine.tar.bz2
              (MD5: 8bc92fa7c03d48c2c6d042ad58221685)


We are no longer distributing binaries which don't have encryption
capabilities built in. Pre-built binaries are available for a small number
of UNIX operating environments for citizens of the U.S. or Canada via:

        http://www.washington.edu/pine/getpine/

The PC-Pine distribution is also available at the above url, or at:

        ftp://ftp.cac.washington.edu/pine/pcpine/pm453w32.zip
              (MD5: c7d2e3db33150177ac20f7f1fac4f651)

As with all Pine releases, it is important that you carefully test and
determine for yourself that it performs suitably in your environment
before placing Pine into production use. Thanks.

The Pine Development Team
-- 
-------------------------------------------------------------
 For information about this mailing list, see: 
 http://www.washington.edu/pine/pine-info/pine-announce.html
-------------------------------------------------------------
-- 
-------------------------------------------------------------
 For information about this mailing list, see: 
 http://www.washington.edu/pine/pine-info/pine-announce.html
-------------------------------------------------------------

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, 20 Jan 2003 08:36:09 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0KGa9Tk011841;
	Mon, 20 Jan 2003 08:36:09 -0800
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.12) with ESMTP id h0KGZq1k029550
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 20 Jan 2003 08:35:53 -0800
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.12) with SMTP id h0KGWN09013400;
	Mon, 20 Jan 2003 08:32:24 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0KGTkCK041076
	for <pine-info@reallists.u.washington.edu>; Mon, 20 Jan 2003 08:29:46 -0800
Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0KGTctv009788;
	Mon, 20 Jan 2003 08:29:39 -0800
Received: from [194.97.50.135] (helo=mx2.freenet.de)
	by mout0.freenet.de with asmtp (Exim 4.10)
	id 18aenk-00060Z-00; Mon, 20 Jan 2003 17:29:32 +0100
Received: from p50868a84.dip0.t-ipconnect.de ([80.134.138.132] helo=HAENDEL)
	by mx2.freenet.de with asmtp (ID ccnoack@freenet.de) (Exim 4.10 #7)
	id 18aenk-00057D-00; Mon, 20 Jan 2003 17:29:32 +0100
Message-Id: <Pine.WNT.4.53.0301201712050.-1553973@Haendel.noack.ccn>
Date: Mon, 20 Jan 2003 17:29:08 +0100 (=?iso-8859-1?Q?=28MEZ=29_Mitteleurop=E4ische_Zeit?=)
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: "Cornelius C. Noack" <noack@physik.uni-bremen.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: bug in Pine 4.53 ?
In-Reply-To: <Pine.WNT.4.53.0301151151580.1336@hubertw2k2_ndc.nebula.washington.edu>
References: <Pine.WNT.4.53.0301151151580.1336@hubertw2k2_ndc.nebula.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Stee Hubert <hubert@washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: ccnoack@imap.freenet.de
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

(I am using pcpine)

In my pinerc. I have set both
            enable-alternate-editor-cmd            and
            editor=C:\$user\Editors\TSE_2.5\e.exe  (which exists!)

Nevertheless, when I call the alternate editor, I get the
"Which alternate Editor?" window. This was not so in previous
releases.

Same thing happens a fortiori if I also set
            enable-alternate-editor-implicitly    .


ccn
-- 
............................................................

  Prof.Dr. Cornelius C. Noack    Phones:
  Inst. f. Theor. Physik FB 1 office   : +49 (421) 218-2427
  Universit"at Bremen         secretary: -2422
  Otto-Hahn-Allee             Fax      : -4869
  D - 28334  Bremen           home     : +49 (421) 34 22 36
                                             Fax:  346 7872
  E-mail: noack@physik.uni-bremen.de or ccnoack@mailaps.org
  WWW-page: www-theorie.physik.uni-bremen.de/~noack
............................................................

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, 20 Jan 2003 19:29:40 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0L3TdTk025046;
	Mon, 20 Jan 2003 19:29:39 -0800
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.12) with ESMTP id h0L3TZ1k011708
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 20 Jan 2003 19:29:36 -0800
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.12) with SMTP id h0L3RiDb092250;
	Mon, 20 Jan 2003 19:27:44 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0L3QjCK024264
	for <pine-info@reallists.u.washington.edu>; Mon, 20 Jan 2003 19:26:45 -0800
Received: from web14805.mail.yahoo.com (web14805.mail.yahoo.com [216.136.224.221])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0L3QhAd013408
	for <pine-info@u.washington.edu>; Mon, 20 Jan 2003 19:26:43 -0800
Received: from [12.225.90.54] by web14805.mail.yahoo.com via HTTP; Mon, 20 Jan 2003 19:26:43 PST
Message-Id: <20030121032643.98790.qmail@web14805.mail.yahoo.com>
Date: Mon, 20 Jan 2003 19:26:43 -0800 (PST)
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: Tom Jenkins <tomjs98@yahoo.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Accessing different email accounts from command line
In-Reply-To: <Pine.GSO.4.33.0301151047520.12103-100000@vax.hanford.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-To: Matt Ackeret <mattack@vax.hanford.org>,
   Pine Discussion Forum <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XI, Probability=11%, Report="FROM_ENDS_IN_NUMS, IN_REP_TO, SPAM_PHRASE_02_03, __EVITE_CTYPE"
X-Uwash-Spam: Gauge=XI, Probability=11%, Report="FROM_ENDS_IN_NUMS, IN_REP_TO, SPAM_PHRASE_02_03, __EVITE_CTYPE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

--- Matt Ackeret <mattack@vax.hanford.org> wrote:
> On Tue, 14 Jan 2003, Tom Jenkins wrote:
> >Is there a way to tell pine to access another
> user's
> >email account provided that the user's correct
> >password is supplied?
> 
> You could add different accounts in a 'collection
> list'.
> 

How do I go about doing that?

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.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; Tue, 21 Jan 2003 03:31:16 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LBVFTk003634;
	Tue, 21 Jan 2003 03:31:15 -0800
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.12) with ESMTP id h0LBV91k020680
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 21 Jan 2003 03:31:09 -0800
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.12) with SMTP id h0LBT909028826;
	Tue, 21 Jan 2003 03:29:09 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LBS9CK031114
	for <pine-info@reallists.u.washington.edu>; Tue, 21 Jan 2003 03:28:10 -0800
Received: from x4u2.desy.de (x4u2.desy.de [131.169.30.42])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LBS6Ad013496
	for <pine-info@u.washington.edu>; Tue, 21 Jan 2003 03:28:07 -0800
Received: from pcx1554.desy.de (pcx1554.desy.de [131.169.137.180])
	by x4u2.desy.de (SGI-8.9.3/8.9.3) with ESMTP id MAA91949
	for <pine-info@u.washington.edu>; Tue, 21 Jan 2003 12:28:04 +0100 (MET)
Message-Id: <Pine.WNT.4.52.0301211156330.202@zittest11.desy.de>
Date: Tue, 21 Jan 2003 12:28:46 +0100 (=?iso-8859-1?Q?Westeurop=E4ische_Normalzeit?=)
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: Stefan Goessling-Reisemann <stefan.goessling@desy.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Bug in 4.52 (and others)?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Info List <pine-info@u.washington.edu>
X-X-Sender: stefang@x4u2.desy.de
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=III, Probability=3%, Report="DEAR_SOMEBODY, SPAM_PHRASE_02_03, USER_AGENT_PINE"

Dear List,

I mentioned the following two problems in the newsgroup comp.mail.pine,
but got no sufficient answer. Maybe you can comment?

1) I have my .pinerc on my IMAP server (actually it is sitting there in my
home-dir). The server is an IRIX64 6.5, the simapd version I do not know,
but when startet by hand it says: IMAP4rev1 v12.264.

I start Unix-Pine (4.33 on different Unixes/Linux) and PC-Pine (4.44,
4.51, 4.52, 4.53 on Win 98, NT, XP) on different machines with the option
-p{imapserver/user=myusername/ssl}.pinerc, which always works fine.  Just
when I look at the actual .pinerc in my home-dir it tends to get bigger
and bigger over time. To be precise: in doubles in size every once in a
while, and I cannot figure out under what circumstances. If I look at the
.pinerc with Pine (opening it as a mail folder, which it actually is), I
see 5 'messages', the first one being only some general information, the
other four being configurations (3 old ones, one actual one). So far so
good. In the course of a few weeks, the size of the configurations
increased from 8 to 17 to 33 kB to .... Upon inspection, I saw that each
configuration message contained one (two, four, ..) sets of the
configuration settings appended to each other.

It is no problem to work with the multiple settings, since they seem to be
exactly identical. The problem is the file size: the whole .pinerc can get
as big as several MB (!!) which causes a significant slow down.

2) A rather small problem occurs with PC-Pine 4.52 (and 4.53) when used as
the default 'mailto:' client. We want to set up PC-Pine as the default
mailer on Windows NT 4.0 and XP. When 'i' is set as the initial command in
Pine and then one opens a mailto: link from a browser, Pine starts but
hangs indefinitely. This does not happen when sending a web-page via 'File
-> Send -> Send page via email' (i.e. using MAPI). Maybe you can provide a
solution? Otherwise we (IT department) will just write a small readme file
warning about this.

Thanks for your replies!!
Best regards,
Stefan Gößling-Reisemann
-- 
-----------------------------------------------------------------
 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; Tue, 21 Jan 2003 08:02:09 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LG29Tk010214;
	Tue, 21 Jan 2003 08:02:09 -0800
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.12) with ESMTP id h0LG26eG007284
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 21 Jan 2003 08:02:06 -0800
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.12) with SMTP id h0LFxn09014828;
	Tue, 21 Jan 2003 07:59:49 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LFwxCK020036
	for <pine-info@reallists.u.washington.edu>; Tue, 21 Jan 2003 07:58:59 -0800
Received: from postman4.mx.aol.com (postman4.mx.aol.com [205.188.157.131])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LFwvZX025819
	for <pine-info@u.washington.edu>; Tue, 21 Jan 2003 07:58:58 -0800
Received: from boondoggle.office.aol.com (boondoggle.office.aol.com [10.0.22.159])
	by postman4.mx.aol.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id KAA05659
	for <pine-info@u.washington.edu>; Tue, 21 Jan 2003 10:58:57 -0500 (EST)
Received: (from harvell@localhost)
	by boondoggle.office.aol.com (8.11.6/8.11.6) id h0LFwuG15383;
	Tue, 21 Jan 2003 10:58:56 -0500 (EST)
Message-Id: <Pine.GSO.4.51.0301211057480.14417@boondoggle.office.aol.com>
Date: Tue, 21 Jan 2003 10:58:56 -0500 (EST)
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: Brian Harvell <harvell@aol.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: auto jump to inbox
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: harvell@boondoggle.office.aol.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=XIII, Probability=13%, Report="MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_00_01, USER_AGENT_PINE"


Is there a way to disable the question of

No more incoming folders.  Return to "INBOX"?

and just make it jump to the inbox?

Brian

-- 

Brian Harvell                harvell@aol.net             http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc


-- 
-----------------------------------------------------------------
 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; Tue, 21 Jan 2003 18:54:48 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M2smTk003635;
	Tue, 21 Jan 2003 18:54:48 -0800
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.12) with ESMTP id h0M2sieG028529
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 21 Jan 2003 18:54:45 -0800
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.12) with SMTP id h0M2r409013256;
	Tue, 21 Jan 2003 18:53:04 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M2prCK033464
	for <pine-info@reallists.u.washington.edu>; Tue, 21 Jan 2003 18:51:53 -0800
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M2poaa013815
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 21 Jan 2003 18:51:50 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M2plVc023101;
	Tue, 21 Jan 2003 18:51:47 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M2plup028837
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Tue, 21 Jan 2003 18:51:47 -0800
Message-Id: <Pine.LNX.4.52.0301211817260.6132@pigeon.cac.washington.edu>
Date: Tue, 21 Jan 2003 18:51:45 -0800 (PST)
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: Bug in 4.52 (and others)?
In-Reply-To: <Pine.WNT.4.52.0301211156330.202@zittest11.desy.de>
References: <Pine.WNT.4.52.0301211156330.202@zittest11.desy.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Stefan Goessling-Reisemann <stefan.goessling@desy.de>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello again Stefan,

On Tue, 21 Jan 2003, Stefan Goessling-Reisemann wrote:

> 1) I have my .pinerc on my IMAP server (actually it is sitting there in my
> home-dir). The server is an IRIX64 6.5, the simapd version I do not know,
> but when startet by hand it says: IMAP4rev1 v12.264.
>
> I start Unix-Pine (4.33 on different Unixes/Linux) and PC-Pine (4.44,
> 4.51, 4.52, 4.53 on Win 98, NT, XP) on different machines with the option
> -p{imapserver/user=myusername/ssl}.pinerc, which always works fine.  Just
> when I look at the actual .pinerc in my home-dir it tends to get bigger
> and bigger over time. To be precise: in doubles in size every once in a
> while, and I cannot figure out under what circumstances.
...

We have definitely not encountered this problem.  One thing I notice is
that you are using a pretty old version of UW-imapd, so the problem might
be with that, but perhaps we can figure out if it's a problem with pine
itself.  Is the problem reproducible?  Try changing something in your
remote pinerc.  Does it double in size when you do that?  If so, if you
could send us some debugging information where you reproduce this, it
would be most helpful.  To do this, run 'pine -d imap=4,verbose=9' and
send us the .pine-debugN file that it creates after having reproduced the
problem and exiting.

> 2) A rather small problem occurs with PC-Pine 4.52 (and 4.53) when used as
> the default 'mailto:' client. We want to set up PC-Pine as the default
> mailer on Windows NT 4.0 and XP. When 'i' is set as the initial command in
> Pine and then one opens a mailto: link from a browser, Pine starts but
> hangs indefinitely.

We've gotten to the bottom of this one, and it looks like it has to do
with the 'i' initial command used in conjunction with a remote address
book.  It's actually prompting for a password without actually showing any
prompts, which is a rather unfortunate bug.  There are a couple of
workarounds that I can think of, but neither of them are all that pretty.
The first workaround is to edit the registry, which the more transparent
workaround.  Both keys
HKEY_LOCAL_MACHINE\Software\Clients\Mail\PC-Pine\Protocols\Mailto\shell\open\command
and HKEY_CLASSES_ROOT\mailto\shell\open\command need to have their default
string changed such that you would add the argument
"-initial-keystroke-list=" added to the list of arguments.  An example
registry entry might be the following line:

"C:\Program Files\PC-Pine\pine.exe" -url "%1" -initial-keystroke-list=

 A second workaround would be to use an exception config and store the
initial-keystroke-list only in that config (I'd certainly go with the
first workaround).

This bug will be fixed in the next version, but hopefully one these
workarounds will be sufficient until that time.

Thanks for the reports!

Jeff

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, 22 Jan 2003 01:19:31 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M9JUTk012865;
	Wed, 22 Jan 2003 01:19:30 -0800
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.12) with ESMTP id h0M9JReG003686
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 01:19:28 -0800
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.12) with SMTP id h0M9Hn09006008;
	Wed, 22 Jan 2003 01:17:50 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M9H0CK046494
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 01:17:00 -0800
Received: from server2.fastmail.fm (ny2.fastmail.fm [66.111.4.3])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M9GwYj004185
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 01:16:59 -0800
Received: from server2.fastmail.fm (localhost [127.0.0.1])
	by fastmail.fm (Postfix) with ESMTP id 792CE652D
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 04:16:57 -0500 (EST)
Received: from 127.0.0.1 ([127.0.0.1] helo=server2.fastmail.fm) by fastmail.fm
  with SMTP; Wed, 22 Jan 2003 04:16:57 -0500
Received: by server2.fastmail.fm (Postfix, from userid 99)
	id 6E73D44908; Wed, 22 Jan 2003 04:16:57 -0500 (EST)
Message-Id: <20030122091657.6E73D44908@server2.fastmail.fm>
Date: Wed, 22 Jan 2003 01:16:57 -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: "Koth Mire" <kothmire@imapmail.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: when reverse sorted, delete should go prev ?
In-Reply-To: <Pine.LNX.4.52.0301211817260.6132@pigeon.cac.washington.edu>
References: <Pine.WNT.4.52.0301211156330.202@zittest11.desy.de> <Pine.LNX.4.52.0301211817260.6132@pigeon.cac.washington.edu>
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-To: "Pine Discussion Forum" <pine-info@u.washington.edu>
X-Epoch: 1043227017
X-Sasl-enc: KfCaaMtsGyHo9VCeFuEg0g
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="IN_REP_TO, MSG_ID_ADDED_BY_MTA_3, REFERENCES, SPAM_PHRASE_00_01, __EVITE_CTYPE"

Hi, 

When using "Reverse Thread" sort order on my inbox, I expect the "delete"
to mark current message deleted and go to the "prev" message in the
thread and not the "next". This is because the first message of the
thread is at the bottom of the thread and the subsequent messages are
towards the top. Hence on reading the first message, when I say "delete",
the "prev" message should become the current message. As of now, the
"next" message becomes the current message and as a result, I move out of
the current thread !

1. Is there anyway to achive this ? (Im using 4.44 on RHLinux 8.0)
2. If not, will this be considered feature for some future release of
pine ?
3. Is there a patch to achieve this (by good ol' Eduardo or anyone else)
?

Regards,

Kothmire

-- 
http://fastmail.fm - A no graphics, no pop-ups email service
-- 
-----------------------------------------------------------------
 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, 22 Jan 2003 01:43:24 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M9hNTk013948;
	Wed, 22 Jan 2003 01:43:23 -0800
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.12) with ESMTP id h0M9hC1k024194
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 01:43:13 -0800
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.12) with SMTP id h0M9fV09027466;
	Wed, 22 Jan 2003 01:41:31 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M9etCK015050
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 01:40:55 -0800
Received: from mx03.nexgo.de (mx03.nexgo.de [151.189.8.98])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0M9eqVb014393
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 01:40:53 -0800
Received: from mx11.arcor-online.net (mx11.arcor-online.net [151.189.8.87])
	by mx03.nexgo.de (Postfix) with ESMTP id 347A82C9E2
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 10:40:51 +0100 (CET)
Message-Id: <7700587.1043228451208.JavaMail.ngmail@mx11.arcor-online.net>
Date: Wed, 22 Jan 2003 10:40:51 +0100 (MET)
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: babbelnase@arcor.de
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Custom Bounce-Header
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-ngMessageSubType: MessageSubType_MAIL
X-WebmailclientIP: : 194.246.96.102
X-Uwash-Spam: Gauge=XXIIIII, Probability=25%, Report="NO_REAL_NAME, SPAM_PHRASE_00_01, __EVITE_CTYPE"
X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="NO_REAL_NAME, __EVITE_CTYPE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello Group,

apologies for perhaps asking a dumb question but I=B4am new to the list -:)

Is there a way to create custom bounce (resent) Headers in Pine ?

In case a User bounces a mail to a different adresse I would like to have a=
 custom
resent header, e.G.

my-resent-field: Value of $variable

it doesn=B4t matter if this field may be an x-header:

x-my-resent-field: Value of $variable

Is this possible ? I vae googled for days but didn=B4t found a solution to =
this problem.

Thanks a lot in advance !

Kind regards
Sascha K=E4mpf

---------------------------------------------------------------------------=
-
Sichern Sie sich jetzt den neuen Otto Katalog mit =FCber 40.000
Artikeln auf =FCber 1.300 Seiten - kostenlos und ganz unverbindlich.
http://www.arcor.de/home/redir.php/email.otto
-----------------------------------------------------------------------

-- 
-----------------------------------------------------------------
 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, 22 Jan 2003 06:26:02 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MEQ1Tk022176;
	Wed, 22 Jan 2003 06:26:01 -0800
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.12) with ESMTP id h0MEPu1k030144
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 06:25:57 -0800
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.12) with SMTP id h0MENqjm019288;
	Wed, 22 Jan 2003 06:23:52 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MEN3CK011222
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 06:23:03 -0800
Received: from msgdirector2.onetel.net.uk (msgdirector2.onetel.net.uk [212.67.96.149])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MEN0Ad016590
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 06:23:01 -0800
Received: from 213-78-91-3.friaco.onetel.net.uk (213-78-91-3.friaco.onetel.net.uk [213.78.91.3])
	by msgdirector2.onetel.net.uk (Mirapoint)
	with ESMTP id AOS95304;
	Wed, 22 Jan 2003 14:22:56 GMT
Message-Id: <Pine.OSX.4.53.0301221405130.475@ybpnyubfg>
Date: Wed, 22 Jan 2003 14:22:46 +0000 (GMT)
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: UI suggestion for current message conditions
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-Uwash-Spam: Gauge=XIII, Probability=13%, Report="SPAM_PHRASE_05_08, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XI, Probability=11%, Report="NOSPAM_INC, SPAM_PHRASE_05_08, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Everytime I create a rule, I spend time wracking my brain trying
to remember the meaning of

 New (Unseen)
 Recent

Since I use IMAPSTATUS in my index-format, this is very confusing
because messages that are "New (Unseen)" are *not* marked with an
N and messages that are "Recent" *are* marked with an N. Here's a
table of the way I think things work:


Message is            STATUS FULLSTATUS IMAPSTATUS
==========            ====== ========== ==========
Important                *       *          *
New (Unseen)             N       N          U
Recent                   N       N        N or R
Deleted                  D       D          D
Answered                 A       A          A


To help make the rule conditions a little easier to understand,
I suggest that you do not use the word "New" because the letter N
is used in STATUS and FULLSTATUS to mean multiple things and I
bet a lot of people see the N and think "New." Here's a
suggestion for how to change the wording:

New (Unseen) ---> Unseen & Not Recent
Recent       ---> Unseen & Recent


So then the table would look like this

Message is            STATUS FULLSTATUS IMAPSTATUS
==========            ====== ========== ==========
Important                *       *          *
Unseen & Not Recent      N       N          U
Unseen & Recent          N       N        N or R
Deleted                  D       D          D
Answered                 A       A          A


and hopefully it will be a little easier to understand. And all
the confusing details could be in the Help.


Another thing to think about is the word "Unseen." Since it means
the message has not been opened or viewed, I suggest also
changing the word "unseen" to either "unopened" or "unviewed" or
"not viewed." Usually when I'm wracking my brain to try to
remember what these words mean I think "oh yeah, 'unseen' means
it wasn't in the folder the last time I was here." But that is
wrong.

What do other people think?

 -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; Wed, 22 Jan 2003 06:59:09 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MEx8Tk023091;
	Wed, 22 Jan 2003 06:59:08 -0800
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.12) with ESMTP id h0MEx41k030848
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 06:59:05 -0800
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.12) with SMTP id h0MEvCDb086042;
	Wed, 22 Jan 2003 06:57:12 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MEuaCK041620
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 06:56:36 -0800
Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MEuVZX011361
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 06:56:32 -0800
Received: from MRLANDY ([80.4.5.243]) by mta03-svc.ntlworld.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20030122145630.GKGU4699.mta03-svc.ntlworld.com@MRLANDY>
          for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 14:56:30 +0000
Message-Id: <Pine.WNT.4.53.0301221455010.-675@mrlandy>
Date: Wed, 22 Jan 2003 14:55:50 +0000 (GMT 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: Barry Landy <bl10@cam.ac.uk>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Windows Splash Screen
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bl10@imap.hermes.cam.ac.uk
X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report="FROM_ENDS_IN_NUMS, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=III, Probability=3%, Report="FROM_ENDS_IN_NUMS, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Buglet:

The Windows screen that is presented while Pine is opening says

"Univeristy of Washington"

-- 
Barry Landy                        Home:               +44-1223-570417
192, Gilbert Road                  College:            +44-1223-332058
Cambridge CB4 3PB                  Email:BL10@cam.ac.uk

-- 
-----------------------------------------------------------------
 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, 22 Jan 2003 07:57:46 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MFvjTk024495;
	Wed, 22 Jan 2003 07:57:45 -0800
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.12) with ESMTP id h0MFveeG012149
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 07:57:41 -0800
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.12) with SMTP id h0MFtbll027100;
	Wed, 22 Jan 2003 07:55:38 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MFswCK041478
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 07:54:58 -0800
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MFsuAd001661
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 07:54:56 -0800
Received: from goedel1.math.washington.edu (goedel1.math.washington.edu [128.95.224.10])
	by euler.math.washington.edu (8.11.6/8.11.6) with ESMTP id h0MFsrq154437;
	Wed, 22 Jan 2003 07:54:53 -0800 (PST)
Message-Id: <Pine.OSF.4.53.0301220720490.247070@goedel1.math.washington.edu>
Date: Wed, 22 Jan 2003 07:54:53 -0800 (PST)
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: UI suggestion for current message conditions
In-Reply-To: <Pine.OSX.4.53.0301221405130.475@ybpnyubfg>
References: <Pine.OSX.4.53.0301221405130.475@ybpnyubfg>
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

*** Nancy McGough (nm-this-address-is-valid@no.sp.am) wrote in the...:

:) Message is            STATUS FULLSTATUS IMAPSTATUS
:) ==========            ====== ========== ==========
:) Important                *       *          *
:) New (Unseen)             N       N          U
:) Recent                   N       N        N or R
:) Deleted                  D       D          D
:) Answered                 A       A          A

I think that your problem is that you are trying to use STATUS and
FULLSTATUS to understand IMAPSTATUS, when IMAPSTATUS should be understood
by itself, so I would suggest that you split the above table in two
tables. The first table should contain the same entries as the above
table, if you like, but only the first two columns, and the second table
should be:


Message is            IMAPSTATUS        STATUS        X-STATUS
==========             ====== 	       ========	     ==========
Important	          *		              F (flagged)
Recent and unread         N	     No or empty
Recent and read           R	        R
Unseen and unread         U		O (old)
read in earlier session  " " (blank)	RO (upon opening the folder)
Deleted                   D			       D
Answered                  A			       A

The last two columns are the internal codes that you find inside the
folder in the "headers" Status and X-Status. The first column translates
the second and third columns.

:) To help make the rule conditions a little easier to understand,
:) I suggest that you do not use the word "New" because the letter N
:) is used in STATUS and FULLSTATUS to mean multiple things and I
:) bet a lot of people see the N and think "New." Here's a
:) suggestion for how to change the wording:

In rule conditions, I would suggest to change

   Current text				suggested text
-----------------------------------------------------------
Message is New (Unseen)?            Message is Unseen and Old
Message is Recent 		    Message is New

What Pine is missing is a flag for "old" messages (that is to say,
messages that were present in the folder the last time it was opened). If
there was a flag for that status, everything would be easier.
Equivalently, Pine could introduce the concept of "old" messages when
explaining roles/filters/scores/etc and I'm sure rewording of the
conditions would not cause any confusion to anyone.

-- 
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; Wed, 22 Jan 2003 11:49:05 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJn4Tk001579;
	Wed, 22 Jan 2003 11:49:04 -0800
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.12) with ESMTP id h0MJn01k007978
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 11:49:00 -0800
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.12) with SMTP id h0MJksll028246;
	Wed, 22 Jan 2003 11:46:55 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJk5CK015726
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 11:46:05 -0800
Received: from shell3.lomag.net (shell3.lomag.net [64.124.180.7])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MJk3aZ031392
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 11:46:03 -0800
Received: (qmail 34149 invoked by uid 1136); 22 Jan 2003 19:46:02 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 22 Jan 2003 19:46:02 -0000
Message-Id: <Pine.BSF.4.51.0301221342430.24752@shell3.lomag.net>
Date: Wed, 22 Jan 2003 14:46:02 -0500 (EST)
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: "Nada O'Neal" <nada@lomag.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: convert PINE mailboxes to ...
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

 Someone asked me to convert their PINE mailboxes for them, to a new,
non-PINE-able email account. I no longer have access to their old PINE
account - it has been shut down. I just have the mail files. There is
about 100MB of mail, because he has 5000 messages and a bazillion freakin'
attachments.

 My first instinct was to just convert the UNIX linebreaks to DOS
linebreaks, and then open the messages in Eudora, which was fine, except
that he's the English-major type, and 75% of his messages have
attachments. Now all his messages with attachments say, "This is a MIME
message... need MIME tools... etc.".munpack works fine and all that, but
if I tell him he needs to use munpack, he'll have an epileptic fit. You
know what I mean? Does anyone know of a program/utility will essentially
munpack an entire mailbox at once?

 The other thing I tried to do is to load his mailboxes into my own PINE
account and "save" them into the INBOX, so that I could then POP the
messages down. My server can only convert in one direction, though...
spool to PINE, and not PINE to spool. However, if you can convert in one
direction, you must be able to convert in the other! Does anyone know of a
program/utility that can do this? Can be a UNIX utility. My sysadmin
hasn't gotten back to me.

ALTERNATELY, if someone could tell me how to use PC pine to move mail from
local PINE folders to an IMAP server, that would also solve all my
problems. I think.

 Thanks!

 - Nada O'Neal
-- 
-----------------------------------------------------------------
 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, 22 Jan 2003 11:53:13 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJrCTk001826;
	Wed, 22 Jan 2003 11:53:12 -0800
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.12) with ESMTP id h0MJr7eG020295
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 11:53:07 -0800
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.12) with SMTP id h0MJpAjm028116;
	Wed, 22 Jan 2003 11:51:10 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJolCK033414
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 11:50:48 -0800
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MJokYj014985
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 11:50:46 -0800
Received: (qmail 11750 invoked by uid 1828); 22 Jan 2003 19:50:45 -0000
Message-Id: <Pine.GSO.4.33.0301221148290.17280-100000@vax.hanford.org>
Date: Wed, 22 Jan 2003 11:50:45 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Can't save to INBOX?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXXIIIIIII, Probability=37%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXIIIIIIIII, Probability=29%, Report="NO_MX_FOR_FROM, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is with pine 4.33..

I had a message accidentally hit my spam filters (haven't quite figured
that out yet -- it looked like it should've hit my setscores rule to set the
score to 100 so as to not be filtered out as suspected spam)..

Anyway, I tried to save it back to my INBOX (after playing with my filters..
and I added a new entry to my From filter as another hopeful fix)..

I'm getting:
Folder "Mailbox" in <Mail> doesn't exist. Create?

when I either try to type INBOX or pick INBOX from the visual list.

What's up?

(It's still using pine 4.33 since my personal acct uses qmail AFAIK..)


mattack@vax.hanford.org

-- 
-----------------------------------------------------------------
 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, 22 Jan 2003 12:00:16 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MK0FTk002117;
	Wed, 22 Jan 2003 12:00:15 -0800
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.12) with ESMTP id h0MK0A1k008334
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 12:00:11 -0800
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.12) with SMTP id h0MJwIDb015838;
	Wed, 22 Jan 2003 11:58:18 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJvpCK039028
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 11:57:51 -0800
Received: from shell3.lomag.net (shell3.lomag.net [64.124.180.7])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MJvnAd022444
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 11:57:50 -0800
Received: (qmail 34556 invoked by uid 1136); 22 Jan 2003 19:57:49 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 22 Jan 2003 19:57:49 -0000
Message-Id: <Pine.BSF.4.51.0301221454010.24752@shell3.lomag.net>
Date: Wed, 22 Jan 2003 14:57:49 -0500 (EST)
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: "Nada O'Neal" <nada@lomag.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Can't save to INBOX?
In-Reply-To: <Pine.GSO.4.33.0301221148290.17280-100000@vax.hanford.org>
References: <Pine.GSO.4.33.0301221148290.17280-100000@vax.hanford.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

It's this way (*) on my server too - the inbox isn't technically a PINE
folder; it's actually your mail spool. So you can save from the Inbox to
a PINE folder, but not from a PINE folder back to the Inbox. You will,
however, be able to save from your spam folder to any other PINE folder,
like saved-messages.

- Nada O'Neal

(*) - note: if it's "this way", then when you use IMAP or webmail, if your
server offers it, you can probably only see your Inbox, not any of your
PINE folders.

On Wed, 22 Jan 2003, Matt Ackeret wrote:

> This is with pine 4.33..
>
> I had a message accidentally hit my spam filters (haven't quite figured
> that out yet -- it looked like it should've hit my setscores rule to set the
> score to 100 so as to not be filtered out as suspected spam)..
>
> Anyway, I tried to save it back to my INBOX (after playing with my filters..
> and I added a new entry to my From filter as another hopeful fix)..
>
> I'm getting:
> Folder "Mailbox" in <Mail> doesn't exist. Create?
>
> when I either try to type INBOX or pick INBOX from the visual list.
>
> What's up?
>
> (It's still using pine 4.33 since my personal acct uses qmail AFAIK..)
>
>
> mattack@vax.hanford.org
>
> --
> -----------------------------------------------------------------
>  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, 22 Jan 2003 12:14:56 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKEtTk002774;
	Wed, 22 Jan 2003 12:14:55 -0800
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.12) with ESMTP id h0MKEpeG021072
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 12:14:51 -0800
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.12) with SMTP id h0MKCsDb076928;
	Wed, 22 Jan 2003 12:12:54 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKCGCK012726
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 12:12:16 -0800
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MKCEYj025283
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 12:12:15 -0800
Received: (qmail 16562 invoked by uid 1828); 22 Jan 2003 20:12:14 -0000
Message-Id: <Pine.GSO.4.33.0301221210080.17280-100000@vax.hanford.org>
Date: Wed, 22 Jan 2003 12:12:13 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Can't save to INBOX?
In-Reply-To: <Pine.BSF.4.51.0301221454010.24752@shell3.lomag.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXIIIIII, Probability=26%, Report="IN_REP_TO, NO_MX_FOR_FROM, SPAM_PHRASE_01_02, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXIIIIII, Probability=26%, Report="IN_REP_TO, NO_MX_FOR_FROM, SPAM_PHRASE_01_02, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 22 Jan 2003, Nada O'Neal wrote:
>It's this way (*) on my server too - the inbox isn't technically a PINE
>folder; it's actually your mail spool. So you can save from the Inbox to
>a PINE folder, but not from a PINE folder back to the Inbox. You will,
>however, be able to save from your spam folder to any other PINE folder,
>like saved-messages.

Sorry, I actually knew this..

But on my work machine, which I have pine 4.51 running on (and at least the
client is running on OSX), I _can_ save into INBOX.

So is it that a newer pine is somehow working around the issue?

I eventually forwarded the message to myself, which worked (but added the
forward headers of course).

BTW, upon originally playing around with saving, the saved copy had the
"full headers shown" problem I described quite a long time ago (probably
years)..  Though I don't seem to be able to reproduce it.   i.e. the saved
copy is pretty heavily mangled.


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, 22 Jan 2003 12:18:43 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKIgTk002960;
	Wed, 22 Jan 2003 12:18:42 -0800
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.12) with ESMTP id h0MKIdeG021178
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 22 Jan 2003 12:18:39 -0800
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.12) with SMTP id h0MKGrll024236;
	Wed, 22 Jan 2003 12:16:53 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKGZCK020628
	for <pine-info@reallists.u.washington.edu>; Wed, 22 Jan 2003 12:16:35 -0800
Received: from shell3.lomag.net (shell3.lomag.net [64.124.180.7])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MKGYYj026966
	for <pine-info@u.washington.edu>; Wed, 22 Jan 2003 12:16:34 -0800
Received: (qmail 38132 invoked by uid 1136); 22 Jan 2003 20:16:33 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 22 Jan 2003 20:16:33 -0000
Message-Id: <Pine.BSF.4.51.0301221515090.24752@shell3.lomag.net>
Date: Wed, 22 Jan 2003 15:16:33 -0500 (EST)
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: "Nada O'Neal" <nada@lomag.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: convert PINE mailboxes to ...
In-Reply-To: <Pine.BSF.4.51.0301221342430.24752@shell3.lomag.net>
References: <Pine.BSF.4.51.0301221342430.24752@shell3.lomag.net>
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

>  Someone asked me to convert their PINE mailboxes for them, to a new,
> non-PINE-able email account. I no longer have access to their old PINE
 ...

I figured out how to use PC-PINE to move the messages up to his new server
via IMAP - it was amazingly easy and now I feel silly. I am interested,
though, if anyone has answers to my other questions. Thanks!

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, 23 Jan 2003 02:37:02 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NAb2Tk028278;
	Thu, 23 Jan 2003 02:37:02 -0800
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.12) with ESMTP id h0NAaxeG010109
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 02:37:00 -0800
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.12) with SMTP id h0NAYhll015884;
	Thu, 23 Jan 2003 02:34:47 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NAXNCK031394
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 02:33:24 -0800
Received: from ascomax.hasler.ascom.ch (ascomax.hasler.ascom.ch [139.79.135.1])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NAXLZ7025777
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 02:33:22 -0800
Received: from stva195.pbx.ascom.ch (stva195.pbxnet.ch [172.20.56.47])
	by ascomax.hasler.ascom.ch (8.11.4/8.11.4) with ESMTP id h0NAXJY25188
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 11:33:20 +0100 (MET)
Received: from stva146 (localhost [127.0.0.1])
	by stva195.pbx.ascom.ch (8.12.1/8.12.1) with ESMTP id h0NAXIGM025930
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 11:33:18 +0100 (MET)
Message-Id: <Pine.GSO.4.53.0301231125040.18953@stva146>
Date: Thu, 23 Jan 2003 11:33:18 +0100 (MET)
Reply-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
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: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: one nickname for more than one address -> how ?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: bmichm@stva146
X-Filter-Version: 1.6 (ascomax)
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

can anybody help me with this (for me) big problem in pine :

I know several persons with the same nickname: HANS MEIER,
HANS MUELLER, HANS WETTER, are all stored with the nickname "HANS"
in pines addresbook.

If you compose a new email and type "Hans" in the TO-field,
it takes one of those addressbook-entries without giving you
the possibility to select in between the three possibilities.

Netscape, e.g. pops up a selection-dialog box
where you can choose which of the possible addresses you want.

But in pine - at least it seems to me - there is no solution - ?
That would mean you have to type the complete emailaddress in those
cases ?

I could not find any hint on this either in the archives or FAQ.

Thanks for any hint or help on this.

Marc

-- 
-----------------------------------------------------------------
 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, 23 Jan 2003 03:09:27 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NB9QTk030940;
	Thu, 23 Jan 2003 03:09:27 -0800
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.12) with ESMTP id h0NB9KeG011128
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 03:09:21 -0800
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.12) with SMTP id h0NB5Ill028540;
	Thu, 23 Jan 2003 03:05:18 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NB4SCK012284
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 03:04:28 -0800
Received: from green.csi.cam.ac.uk (green.csi.cam.ac.uk [131.111.8.57])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NB4QfV026451
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 03:04:26 -0800
Received: from csfpc2.fitz.cam.ac.uk ([131.111.226.29] helo=cam.ac.uk)
	by green.csi.cam.ac.uk with esmtp (Exim 4.10)
	id 18bf9l-0007Zl-00; Thu, 23 Jan 2003 11:04:25 +0000
Message-Id: <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
Date: Thu, 23 Jan 2003 11:04:26 +0000 (GMT)
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: Barry Landy <bl10@cam.ac.uk>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.GSO.4.53.0301231125040.18953@stva146>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bl10@imap.hermes.cam.ac.uk
X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report="FROM_ENDS_IN_NUMS, IN_REP_TO, REFERENCES, SPAM_PHRASE_03_05"
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="FROM_ENDS_IN_NUMS, IN_REP_TO, REFERENCES, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_03_05"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 23 Jan 2003, Marc Michalewicz wrote:

:>Hi,
:>
:>can anybody help me with this (for me) big problem in pine :
:>
:>I know several persons with the same nickname: HANS MEIER,
:>HANS MUELLER, HANS WETTER, are all stored with the nickname "HANS"
:>in pines addresbook.
:>
:>If you compose a new email and type "Hans" in the TO-field,
:>it takes one of those addressbook-entries without giving you
:>the possibility to select in between the three possibilities.

Dont call them all hans! Have hansm, hansw, etc etc; if you cannot
recall which is which use the addressbook lookup faciity when composing
(^T).

:>
:>Netscape, e.g. pops up a selection-dialog box
:>where you can choose which of the possible addresses you want.
:>
:>But in pine - at least it seems to me - there is no solution - ?
:>That would mean you have to type the complete emailaddress in those
:>cases ?
:>
:>I could not find any hint on this either in the archives or FAQ.
:>
:>Thanks for any hint or help on this.
:>
:>Marc
:>
:>

-- 
Barry Landy                        Home:               +44-1223-570417
192, Gilbert Road                  College:            +44-1223-332058
Cambridge CB4 3PB                  Email:BL10@cam.ac.uk

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, 23 Jan 2003 05:02:53 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ND2qTk018392;
	Thu, 23 Jan 2003 05:02:52 -0800
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.12) with ESMTP id h0ND2k1k007302
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 05:02:47 -0800
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.12) with SMTP id h0ND0XDb091100;
	Thu, 23 Jan 2003 05:00:33 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NCxoCK010762
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 04:59:51 -0800
Received: from ascomax.hasler.ascom.ch (ascomax.hasler.ascom.ch [139.79.135.1])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NCxmkp013115
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 04:59:49 -0800
Received: from stva195.pbx.ascom.ch (stva195.pbxnet.ch [172.20.56.47])
	by ascomax.hasler.ascom.ch (8.11.4/8.11.4) with ESMTP id h0NCxhY16025;
	Thu, 23 Jan 2003 13:59:44 +0100 (MET)
Received: from stva146 (localhost [127.0.0.1])
	by stva195.pbx.ascom.ch (8.12.1/8.12.1) with ESMTP id h0NCxgGM015872;
	Thu, 23 Jan 2003 13:59:42 +0100 (MET)
Message-Id: <Pine.GSO.4.53.0301231349130.18953@stva146>
Date: Thu, 23 Jan 2003 13:59:42 +0100 (MET)
Reply-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
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: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Barry Landy <bl10@cam.ac.uk>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bmichm@stva146
X-Filter-Version: 1.6 (ascomax)
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Thu, 23 Jan 2003, Barry Landy wrote:

> On Thu, 23 Jan 2003, Marc Michalewicz wrote:
>
> :>Hi,
> :>
> :>can anybody help me with this (for me) big problem in pine :
> :>
> :>I know several persons with the same nickname: HANS MEIER,
> :>HANS MUELLER, HANS WETTER, are all stored with the nickname "HANS"
> :>in pines addresbook.
> :>
> :>If you compose a new email and type "Hans" in the TO-field,
> :>it takes one of those addressbook-entries without giving you
> :>the possibility to select in between the three possibilities.
>
> Dont call them all hans! Have hansm, hansw, etc etc; if you cannot
> recall which is which use the addressbook lookup faciity when composing
> (^T).

Basically, you are right, but I have already tried this out and it is
not a real solution to me, frankly spoken.

My addressbook has lots of names with ambigious and non-ambigious
nicknames and shall I each time remember if the one I currently
use is ambigous or not ?
When the addressbook contains 10-50 address this might be ok, but 500
and more - that is not managable anymore in this way.

And the lookup in the addressbook is a bit quite complicated.
You have type ^T and browse (or search with "W") through it; not
a nice solution.

It would be better to jump directly to the location of the first
of all possibilities when hitting ^T. That would be much better .

Shall I participate in the development and implement this or just
raise it as a feature-request ?

Just because this does not seem to be implemented like I experienced
now.


Thanks for this hint.

Marc

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, 23 Jan 2003 05:05:56 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ND5tTk018971;
	Thu, 23 Jan 2003 05:05:55 -0800
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.12) with ESMTP id h0ND5oeG018770
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 05:05:50 -0800
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.12) with SMTP id h0ND3f09023406;
	Thu, 23 Jan 2003 05:03:41 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ND3GCK045172
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 05:03:16 -0800
Received: from orange.csi.cam.ac.uk (orange.csi.cam.ac.uk [131.111.8.77])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0ND3DfV010685
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 05:03:14 -0800
Received: from csfpc2.fitz.cam.ac.uk ([131.111.226.29] helo=cam.ac.uk)
	by orange.csi.cam.ac.uk with esmtp (Exim 4.10)
	id 18bh0j-0003vh-00; Thu, 23 Jan 2003 13:03:13 +0000
Message-Id: <Pine.OS2.4.53.0301231300430.116@csfpc2.fitz.cam.ac.uk>
Date: Thu, 23 Jan 2003 13:03:13 +0000 (GMT)
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: Barry Landy <bl10@cam.ac.uk>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.GSO.4.53.0301231349130.18953@stva146>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bl10@imap.hermes.cam.ac.uk
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="FROM_ENDS_IN_NUMS, IN_REP_TO, REFERENCES, SPAM_PHRASE_02_03"

I also have several hundred entries in my addressbook, and find that I
routinely go ^T and W and find it quite natural.

I am not sure about a feature improvement, as with multiple address
books, looking for repeated identical nicknames is not so obvious.

Actually, now I type that, Surely Pine does not allow you to have the
same nickname repeated in one addressbook?

On Thu, 23 Jan 2003, Marc Michalewicz wrote:

:>
:>On Thu, 23 Jan 2003, Barry Landy wrote:
:>
:>> On Thu, 23 Jan 2003, Marc Michalewicz wrote:
:>>
:>> :>Hi,
:>> :>
:>> :>can anybody help me with this (for me) big problem in pine :
:>> :>
:>> :>I know several persons with the same nickname: HANS MEIER,
:>> :>HANS MUELLER, HANS WETTER, are all stored with the nickname "HANS"
:>> :>in pines addresbook.
:>> :>
:>> :>If you compose a new email and type "Hans" in the TO-field,
:>> :>it takes one of those addressbook-entries without giving you
:>> :>the possibility to select in between the three possibilities.
:>>
:>> Dont call them all hans! Have hansm, hansw, etc etc; if you cannot
:>> recall which is which use the addressbook lookup faciity when composing
:>> (^T).
:>
:>Basically, you are right, but I have already tried this out and it is
:>not a real solution to me, frankly spoken.
:>
:>My addressbook has lots of names with ambigious and non-ambigious
:>nicknames and shall I each time remember if the one I currently
:>use is ambigous or not ?
:>When the addressbook contains 10-50 address this might be ok, but 500
:>and more - that is not managable anymore in this way.
:>
:>And the lookup in the addressbook is a bit quite complicated.
:>You have type ^T and browse (or search with "W") through it; not
:>a nice solution.
:>
:>It would be better to jump directly to the location of the first
:>of all possibilities when hitting ^T. That would be much better .
:>
:>Shall I participate in the development and implement this or just
:>raise it as a feature-request ?
:>
:>Just because this does not seem to be implemented like I experienced
:>now.
:>
:>
:>Thanks for this hint.
:>
:>Marc
:>

-- 
Barry Landy                        Home:               +44-1223-570417
192, Gilbert Road                  College:            +44-1223-332058
Cambridge CB4 3PB                  Email:BL10@cam.ac.uk


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, 23 Jan 2003 05:13:59 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDDwTk021641;
	Thu, 23 Jan 2003 05:13:58 -0800
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.12) with ESMTP id h0NDDq1k008508
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 05:13:53 -0800
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.12) with SMTP id h0NDBull015936;
	Thu, 23 Jan 2003 05:11:56 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDBPCK028148
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 05:11:25 -0800
Received: from rubicon.hasler.ascom.ch (rubicon.hasler.ascom.ch [139.79.129.1])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDBMZ7013857
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 05:11:23 -0800
Received: from stva195.pbx.ascom.ch (stva195.pbxnet.ch [172.20.56.47])
	by rubicon.hasler.ascom.ch (8.11.4/8.11.4) with ESMTP id h0NDBJR01000;
	Thu, 23 Jan 2003 14:11:19 +0100 (MET)
Received: from stva146 (localhost [127.0.0.1])
	by stva195.pbx.ascom.ch (8.12.1/8.12.1) with ESMTP id h0NDBIGM017436;
	Thu, 23 Jan 2003 14:11:18 +0100 (MET)
Message-Id: <Pine.GSO.4.53.0301231406560.18953@stva146>
Date: Thu, 23 Jan 2003 14:11:18 +0100 (MET)
Reply-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
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: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.OS2.4.53.0301231300430.116@csfpc2.fitz.cam.ac.uk>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Barry Landy <bl10@cam.ac.uk>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bmichm@stva146
X-Filter-Version: 1.6 (rubicon)
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Thu, 23 Jan 2003, Barry Landy wrote:

> I also have several hundred entries in my addressbook, and find that I
> routinely go ^T and W and find it quite natural.

I will try to get used to this, because in any other point of view, pine
is the best mailclient for me.

> I am not sure about a feature improvement, as with multiple address
> books, looking for repeated identical nicknames is not so obvious.

OK, I did not think of this, probably you are right.

> Actually, now I type that, Surely Pine does not allow you to have the
> same nickname repeated in one addressbook?

Yes, it works for me (ver 4.53).

Thanks a lot for your help.

Marc



>
> On Thu, 23 Jan 2003, Marc Michalewicz wrote:
>
> :>
> :>On Thu, 23 Jan 2003, Barry Landy wrote:
> :>
> :>> On Thu, 23 Jan 2003, Marc Michalewicz wrote:
> :>>
> :>> :>Hi,
> :>> :>
> :>> :>can anybody help me with this (for me) big problem in pine :
> :>> :>
> :>> :>I know several persons with the same nickname: HANS MEIER,
> :>> :>HANS MUELLER, HANS WETTER, are all stored with the nickname "HANS"
> :>> :>in pines addresbook.
> :>> :>
> :>> :>If you compose a new email and type "Hans" in the TO-field,
> :>> :>it takes one of those addressbook-entries without giving you
> :>> :>the possibility to select in between the three possibilities.
> :>>
> :>> Dont call them all hans! Have hansm, hansw, etc etc; if you cannot
> :>> recall which is which use the addressbook lookup faciity when composing
> :>> (^T).
> :>
> :>Basically, you are right, but I have already tried this out and it is
> :>not a real solution to me, frankly spoken.
> :>
> :>My addressbook has lots of names with ambigious and non-ambigious
> :>nicknames and shall I each time remember if the one I currently
> :>use is ambigous or not ?
> :>When the addressbook contains 10-50 address this might be ok, but 500
> :>and more - that is not managable anymore in this way.
> :>
> :>And the lookup in the addressbook is a bit quite complicated.
> :>You have type ^T and browse (or search with "W") through it; not
> :>a nice solution.
> :>
> :>It would be better to jump directly to the location of the first
> :>of all possibilities when hitting ^T. That would be much better .
> :>
> :>Shall I participate in the development and implement this or just
> :>raise it as a feature-request ?
> :>
> :>Just because this does not seem to be implemented like I experienced
> :>now.
> :>
> :>
> :>Thanks for this hint.
> :>
> :>Marc
> :>
>
> --
> Barry Landy                        Home:               +44-1223-570417
> 192, Gilbert Road                  College:            +44-1223-332058
> Cambridge CB4 3PB                  Email:BL10@cam.ac.uk
>

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, 23 Jan 2003 05:17:46 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDHjTk022560;
	Thu, 23 Jan 2003 05:17:45 -0800
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.12) with ESMTP id h0NDHfeG019875
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 05:17:41 -0800
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.12) with SMTP id h0NDGBll019430;
	Thu, 23 Jan 2003 05:16:11 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDFrCK028080
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 05:15:53 -0800
Received: from orange.csi.cam.ac.uk (orange.csi.cam.ac.uk [131.111.8.77])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDFpM5013326
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 05:15:51 -0800
Received: from csfpc2.fitz.cam.ac.uk ([131.111.226.29] helo=cam.ac.uk)
	by orange.csi.cam.ac.uk with esmtp (Exim 4.10)
	id 18bhCw-0007Vw-00; Thu, 23 Jan 2003 13:15:50 +0000
Message-Id: <Pine.OS2.4.53.0301231314420.116@csfpc2.fitz.cam.ac.uk>
Date: Thu, 23 Jan 2003 13:15:51 +0000 (GMT)
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: Barry Landy <bl10@cam.ac.uk>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.GSO.4.53.0301231406560.18953@stva146>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bl10@imap.hermes.cam.ac.uk
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 23 Jan 2003, Marc Michalewicz wrote:

:>> Actually, now I type that, Surely Pine does not allow you to have the
:>> same nickname repeated in one addressbook?
:>
:>Yes, it works for me (ver 4.53).
:>

For me, it definitely faults any attempt to do that (also 4.53). Can we
have an official view as to what the intention is, please.

-- 
Barry Landy                        Home:               +44-1223-570417
192, Gilbert Road                  College:            +44-1223-332058
Cambridge CB4 3PB                  Email:BL10@cam.ac.uk


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, 23 Jan 2003 05:51:24 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDpLTk000816;
	Thu, 23 Jan 2003 05:51:22 -0800
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.12) with ESMTP id h0NDos1k012296
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 05:50:57 -0800
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.12) with SMTP id h0NDms09028368;
	Thu, 23 Jan 2003 05:48:55 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDmOCK018400
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 05:48:24 -0800
Received: from inode ([202.63.174.20])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NDmLZ7019246
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 05:48:22 -0800
Received: from localhost (mayuresh@localhost)
	by inode (8.12.7/8.12.7) with ESMTP id h0NDoEZo000465
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 19:20:14 +0530
Message-Id: <Pine.LNX.4.50.0301231916500.464-100000@inode>
Date: Thu, 23 Jan 2003 19:20:13 +0530 (IST)
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: Mayuresh Kathe <mayuresh@vsnl.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Sudo Newbie, howto...
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: inode: mayuresh owned process doing -bs
X-X-Sender: mayuresh@inode
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report="RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_00_01, USER_AGENT_PINE, X_AUTH_WARNING"

Hi all,

Though I've been using Pine for quite sometime, I've always been using it
as a stop gap arrangement (before bringing all mails to my mac).
Now I have shifted to Linux (full time :)
I wanted to know a couple of things:
1. how do I filter incoming mails to send them to different mailboxes
2. how do I get a threaded view
3. is there colour support (as with Mutt)

Thanks,

~Mayuresh

-- 
-----------------------------------------------------------------
 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, 23 Jan 2003 08:20:51 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NGKoTk009031;
	Thu, 23 Jan 2003 08:20:50 -0800
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.12) with ESMTP id h0NGKc1k024653
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 08:20:38 -0800
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.12) with SMTP id h0NGITDb014650;
	Thu, 23 Jan 2003 08:18:29 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NGHnCK010966
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 08:17:49 -0800
Received: from gort.cjb.net (c-24-126-16-90.we.client2.attbi.com [24.126.16.90])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NGHmfV018562
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 08:17:48 -0800
Received: from localhost (localhost [127.0.0.1])
	by gort.cjb.net (Postfix) with ESMTP id C741EA7AC
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 08:16:51 -0800 (PST)
Message-Id: <Pine.LNX.4.50.0301230807560.26706-100000@gort.cjb.net>
Date: Thu, 23 Jan 2003 08:16:51 -0800 (PST)
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: Sudo Newbie, howto...
In-Reply-To: <Pine.LNX.4.50.0301231916500.464-100000@inode>
References: <Pine.LNX.4.50.0301231916500.464-100000@inode>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: satyap@gort.cjb.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Jan 23, 2003 at 19:20, Mayuresh Kathe wrote:

>1. how do I filter incoming mails to send them to different mailboxes

msrf

main setup rules filters

Or use procmail :-)

>2. how do I get a threaded view

$z in the message index. I think you can set this to be done
automatically every time you enter a folder by going into setup (msc)
and setting the sort-key to tHread.

>3. is there colour support (as with Mutt)

Yes. As with mutt? I don't know. Personally, I don't use color
support. Try mk.

>~Mayuresh

D'oh, I read this far and only then saw the sender name. Boggle. Hi
:-)

-- 
Satya. <URL:http://satya.virtualave.net/>
It works better when you turn the brightness up.

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, 23 Jan 2003 15:24:37 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNOaTk027959;
	Thu, 23 Jan 2003 15:24:36 -0800
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.12) with ESMTP id h0NNOVWb018197
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 15:24:31 -0800
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.12) with SMTP id h0NNM9Db055904;
	Thu, 23 Jan 2003 15:22:10 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNKuCK041356
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 15:20:56 -0800
Received: from mindsec.com (noella.mindsec.com [209.172.192.12])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNKrkp003548
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 15:20:54 -0800
Received: from noella (IDENT:100@noella [209.172.192.12])
	by mindsec.com (8.8.6/8.8.6) with ESMTP id h0NNKqLW008124
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 17:20:53 -0600 (CST)
Message-Id: <0301231716440-100000@jukebox7.co.uk>
Date: Thu, 23 Jan 2003 17:20:52 -0600 (CST)
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: Erik <eparker@mindsec.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Sleep when using roles..
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: Erik Parker <eparker@mindsec.com>
X-Sender: eparker@mindsec.com
X-GPG-Key: http://www.mindsec.com/staff/eparker/gpg.txt
X-Use-Encryption: Encrypt your messages to me with PGP or GPG!
X-No-Archive: Yes
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01"


Why is it when replying to a message, pine seems to sleep for a few seconds
when telling you which role its using "Using role blah"

Sleeps for about 2 or 3 seconds. Truss seems to say it's not really doing
anything during that time, just kinda waiting. Is there an easy way to disable
this wait time? Seems wasteful



---
Erik
---


-- 
-----------------------------------------------------------------
 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, 23 Jan 2003 16:51:38 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0O0pbTk031725;
	Thu, 23 Jan 2003 16:51:37 -0800
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.12) with ESMTP id h0O0pSWb021062
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 16:51:34 -0800
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.12) with SMTP id h0O0mUDb075486;
	Thu, 23 Jan 2003 16:48:31 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNkHCK019250
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 15:46:17 -0800
Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNkEfW018870
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 15:46:15 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNkCFR003284;
	Thu, 23 Jan 2003 15:46:12 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNk2up006376
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Thu, 23 Jan 2003 15:46:12 -0800
Message-Id: <Pine.LNX.4.52.0301231542270.10133@pigeon.cac.washington.edu>
Date: Thu, 23 Jan 2003 15:46:00 -0800 (PST)
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: Windows Splash Screen
In-Reply-To: <Pine.WNT.4.53.0301221455010.-675@mrlandy>
References: <Pine.WNT.4.53.0301221455010.-675@mrlandy>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Barry Landy <bl10@cam.ac.uk>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 22 Jan 2003, Barry Landy wrote:

> Buglet:
>
> The Windows screen that is presented while Pine is opening says
>
> "Univeristy of Washington"

Hi Barry,

Thanks for pointing that out.  Apparently we're still getting the hang of
typing over here :)   We'll go ahead and fix this.

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

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, 23 Jan 2003 16:53:52 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0O0rpTk031818;
	Thu, 23 Jan 2003 16:53:51 -0800
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.12) with ESMTP id h0O0rmWb021106
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Jan 2003 16:53:49 -0800
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.12) with SMTP id h0O0oxll027946;
	Thu, 23 Jan 2003 16:51:00 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0NNnmCK019330
	for <pine-info@reallists.u.washington.edu>; Thu, 23 Jan 2003 15:49:48 -0800
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.12) with ESMTP id h0NNnjFq030760
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 15:49:46 -0800
Received: from mars.geneseo.edu (mars.geneseo.edu [137.238.1.104])
	by helios.geneseo.edu (8.12.5/8.12.5) with ESMTP id h0NNneHG011259
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 18:49:40 -0500 (EST)
Received: from mars.geneseo.edu (localhost.localdomain [127.0.0.1])
	by mars.geneseo.edu (8.12.5/8.12.5) with ESMTP id h0NNnYKM012647
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 18:49:34 -0500
Received: from localhost (valites@localhost)
	by mars.geneseo.edu (8.12.5/8.12.1/Submit) with ESMTP id h0NNnYMR012644
	for <pine-info@u.washington.edu>; Thu, 23 Jan 2003 18:49:34 -0500
Message-Id: <Pine.LNX.4.44.0301231839240.11977-100000@mars.geneseo.edu>
Date: Thu, 23 Jan 2003 18:49:34 -0500 (EST)
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: Setting the start-up messsage for non-INBOX folders
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've been having trouble figuring out which setting setting I can edit to
change the behvaior when entering a folder besides my INBOX.  I have
incoming-startup-rule set to first-unseen, but from the help below:

This value affects Pine's behavior when opening the "INBOX" or one of the
"INCOMING MESSAGE FOLDERS". It determines which message will be the
current message when the folder is first opened. The default value is
"first-unseen".

it only appears that this applies to my INBOX.  Is there a way to make the
initial message the cursor shows up on become first-unseen without using
INCOMING MESSAGE FOLDERS?

-- 
>--))> >--))>
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; Fri, 24 Jan 2003 08:28:18 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OGSHTk021466;
	Fri, 24 Jan 2003 08:28:17 -0800
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.12) with ESMTP id h0OGSCnO032285
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 24 Jan 2003 08:28:13 -0800
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.12) with SMTP id h0OGPhll025962;
	Fri, 24 Jan 2003 08:25:44 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OGOgCK014892
	for <pine-info@reallists.u.washington.edu>; Fri, 24 Jan 2003 08:24:42 -0800
Received: from mail.mtds.com (mail.mtds.com [194.204.200.6])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OGOdFq008047
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 08:24:40 -0800
Received: from pcRachid.mtds.com (pcRachid.mtds.com [194.204.200.44])
	by mail.mtds.com (Postfix) with ESMTP id B37E816358C
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 16:24:38 +0000 (WET)
Message-Id: <1043425537.4734.19.camel@pcRachid.mtds.com>
Date: 24 Jan 2003 16:25:37 +0000
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: Abdelkhalak Rachid <a.rachid@mtds.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Pine Installation problem
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SPAM_PHRASE_01_02, __EVITE_CTYPE"
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SPAM_PHRASE_01_02, __EVITE_CTYPE, __HAS_X_MAILER"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



Hello,

At first i'm sorry for my english verry bad ;-)

I'm a newbie to Mandrake9.0 and i'm using Pc Pine in Windows 2000 No
without problem, i want to use it in mandrake9.0 and i cant build it i
have everytime a error message.

I downloaded the Pine4.53.tar.gz file, extracted this file to my home
directiry, after, Logged as root i make

# cd pine4.53
#./build clean
# ./build NOSSL lnx

I test it with=20

#./build slx and "./buil NOSSL slx and he give me the same message...

I have this message in the end of the operation:

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

./mkauths  md5 pla log
make[4]: Entre dans le r=E9pertoire `/home/rachid/pine4.53/imap/c-client'
echo -DMD5ENABLE=3D\"/etc/cram-md5.pwd\" >> OSCFLAGS
make[4]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap/c-client'
ln -s os_slx.h osdep.h
ln -s os_slx.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 slx !=3D sc5 -a slx !=3D sco)
&& ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c'
Standard password authentication
ln -s ckp_psx.c osdepckp.c
Building with SSL
ln -s ssl_unix.c osdepssl.c
echo -I/usr/include/openssl/include
-I/usr/include/openssl/include/openssl
-DSSL_CERT_DIRECTORY=3D\"/usr/include/openssl/certs\" >> OSCFLAGS
echo "  ssl_onceonlyinit ();" >> linkage.c
echo -L/usr/include/openssl/lib -lssl -lcrypto  >> LDFLAGS
Building with SSL and plaintext passwords disabled unless SSL/TLS
echo "  mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >>
linkage.c
cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c
Building OS-dependent module
If you get No such file error messages for files x509.h, ssl.h,
pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL
is not installed on your system. Either install OpenSSL first
or build with command: make slx SSLTYPE=3Dnone
`cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c
/bin/sh: line 1: cc: command not found
make[3]: *** [osdep.o] Erreur 127
make[3]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap/c-client'
make[2]: *** [slx] Erreur 2
make[2]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap/c-client'
make[1]: *** [OSTYPE] Erreur 2
make[1]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap'
make: *** [slx] Erreur 2
+---------------------------------------------+
| Problems building c-client                  |
|                                             |
| Please check the output above for a         |
| possible explanation for this failure       |
+---------------------------------------------+




HELPPPPPPPPPPPPPPPPPPPPPP


thanks a lot....

Rachid

-- 
-----------------------------------------------------------------
 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; Fri, 24 Jan 2003 08:31:02 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OGV2Tk021575;
	Fri, 24 Jan 2003 08:31:02 -0800
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.12) with ESMTP id h0OGUxnO032389
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 24 Jan 2003 08:31:00 -0800
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.12) with SMTP id h0OGSmjm038722;
	Fri, 24 Jan 2003 08:28:48 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OGSWCK022130
	for <pine-info@reallists.u.washington.edu>; Fri, 24 Jan 2003 08:28:32 -0800
Received: from mail.mtds.com (mail.mtds.com [194.204.200.6])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OGSTfV011055
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 08:28:30 -0800
Received: from pcRachid.mtds.com (pcRachid.mtds.com [194.204.200.44])
	by mail.mtds.com (Postfix) with ESMTP id DE08A163590
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 16:28:23 +0000 (WET)
Message-Id: <1043425762.4734.25.camel@pcRachid.mtds.com>
Date: 24 Jan 2003 16:29:22 +0000
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: Abdelkhalak Rachid <a.rachid@mtds.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Compiled Directory, is possible ?
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01"

Hello

Can I download a compiled directory of PC Pine anywhere? because i have
a problem to compile the original directory....

thanks



-- 
-----------------------------------------------------------------
 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; Fri, 24 Jan 2003 09:10:27 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHARTk023076;
	Fri, 24 Jan 2003 09:10:27 -0800
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.12) with ESMTP id h0OHAJnO001261
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 24 Jan 2003 09:10:19 -0800
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.12) with SMTP id h0OH7EDb093430;
	Fri, 24 Jan 2003 09:07:15 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OH6LCK023264
	for <pine-info@reallists.u.washington.edu>; Fri, 24 Jan 2003 09:06:21 -0800
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.12) with ESMTP id h0OH6JfV022888
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 09:06:19 -0800
Received: from goedel2.math.washington.edu (goedel2.math.washington.edu [128.95.224.11])
	by euler.math.washington.edu (8.11.6/8.11.6) with ESMTP id h0OH6Dq05911;
	Fri, 24 Jan 2003 09:06:13 -0800 (PST)
Message-Id: <Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu>
Date: Fri, 24 Jan 2003 09:06:13 -0800 (PST)
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: Pine Installation problem
In-Reply-To: <1043425537.4734.19.camel@pcRachid.mtds.com>
References: <1043425537.4734.19.camel@pcRachid.mtds.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Abdelkhalak Rachid <a.rachid@mtds.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Abdelkhalak Rachid (a.rachid@mtds.com) wrote in the pine-info list today:

[...]
:) I have this message in the end of the operation:
:) [...]
:) /bin/sh: line 1: cc: command not found

That line says that you need to install a C compiler. If you have
installed gcc as your compiler try adding the parameter "CC=gcc", so
something like

./build NOSSL CC=gcc lnx

may work. If not, install a C compiler first.

-- 
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; Fri, 24 Jan 2003 09:40:54 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHesTk024065;
	Fri, 24 Jan 2003 09:40:54 -0800
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.12) with ESMTP id h0OHeonO002201
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 24 Jan 2003 09:40:51 -0800
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.12) with SMTP id h0OHbv09005844;
	Fri, 24 Jan 2003 09:37:57 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHbDCK042672
	for <pine-info@reallists.u.washington.edu>; Fri, 24 Jan 2003 09:37:13 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHbAkq016289
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 09:37:11 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHbAJA013733
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 09:37:10 -0800
Received: from [128.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHb3up028548
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 09:37:09 -0800
Message-Id: <Pine.WNT.4.53.0301240931490.1028@hubertw2k2_ndc.nebula.washington.edu>
Date: Fri, 24 Jan 2003 09:37:03 -0800 (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: one nickname for more than one address -> how ?
In-Reply-To: <Pine.OS2.4.53.0301231314420.116@csfpc2.fitz.cam.ac.uk>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 23 Jan 2003, Barry Landy wrote:

> On Thu, 23 Jan 2003, Marc Michalewicz wrote:
>
> :>> Actually, now I type that, Surely Pine does not allow you to have the
> :>> same nickname repeated in one addressbook?
> :>
> :>Yes, it works for me (ver 4.53).
> :>
>
> For me, it definitely faults any attempt to do that (also 4.53). Can we
> have an official view as to what the intention is, please.

I believe we try to catch attempts to add entries with identical
nicknames, and even prevent you from doing so if the other entry is in the
same address book. If the address book already has multiple entries we do
not try to fix it, but return only the first entry when the nickname is
typed in.

The intent is that each entry should have a unique nickname.

Steve

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, 24 Jan 2003 09:47:28 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHlRTk024319;
	Fri, 24 Jan 2003 09:47:27 -0800
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.12) with ESMTP id h0OHlNWb012091
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 24 Jan 2003 09:47:23 -0800
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.12) with SMTP id h0OHj7jm032720;
	Fri, 24 Jan 2003 09:45:07 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHifCK028232
	for <pine-info@reallists.u.washington.edu>; Fri, 24 Jan 2003 09:44:41 -0800
Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHidkq018566
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Fri, 24 Jan 2003 09:44:40 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHibFR014116;
	Fri, 24 Jan 2003 09:44:37 -0800
Received: from [128.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0OHibup028841
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 24 Jan 2003 09:44:37 -0800
Message-Id: <Pine.WNT.4.53.0301240943250.1028@hubertw2k2_ndc.nebula.washington.edu>
Date: Fri, 24 Jan 2003 09:44:37 -0800 (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: Setting the start-up messsage for non-INBOX folders
In-Reply-To: <Pine.LNX.4.44.0301231839240.11977-100000@mars.geneseo.edu>
References: <Pine.LNX.4.44.0301231839240.11977-100000@mars.geneseo.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
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

On Thu, 23 Jan 2003, Mark T. Valites wrote:

> it only appears that this applies to my INBOX.  Is there a way to make the
> initial message the cursor shows up on become first-unseen without using
> INCOMING MESSAGE FOLDERS?

You can do this with Setup / Rules / Other

Steve Hubert


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; Sat, 25 Jan 2003 01:44:10 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0P9i9Tk020314;
	Sat, 25 Jan 2003 01:44:09 -0800
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.12) with ESMTP id h0P9i4Wb005804
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 25 Jan 2003 01:44:05 -0800
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.12) with SMTP id h0P9Qljm041140;
	Sat, 25 Jan 2003 01:26:48 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0P9IdCK043976
	for <pine-info@reallists.u.washington.edu>; Sat, 25 Jan 2003 01:18:39 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0P9IaM6031632
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Sat, 25 Jan 2003 01:18:37 -0800
Received: from localhost (dufberg@localhost)
	by aslan.narnia.pp.se (8.11.3/8.11.3) with ESMTP id h0P9IPT81707;
	Sat, 25 Jan 2003 10:18:28 +0100 (CET)
	(envelope-from dufberg@narnia.pp.se)
Message-Id: <20030125100819.G5534-100000@aslan.narnia.pp.se>
Date: Sat, 25 Jan 2003 10:18:24 +0100 (CET)
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: Mats Dufberg <dufberg@narnia.pp.se>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Can't save to INBOX?
In-Reply-To: <Pine.GSO.4.33.0301221148290.17280-100000@vax.hanford.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Matt Ackeret <mattack@vax.hanford.org>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Jan 22, 2003, 11:50 (-0800) Matt Ackeret <mattack@vax.hanford.org> wrote:

> This is with pine 4.33..
>
> I had a message accidentally hit my spam filters (haven't quite figured
> that out yet -- it looked like it should've hit my setscores rule to set the
> score to 100 so as to not be filtered out as suspected spam)..
>
> Anyway, I tried to save it back to my INBOX (after playing with my filters..
> and I added a new entry to my From filter as another hopeful fix)..
>
> I'm getting:
> Folder "Mailbox" in <Mail> doesn't exist. Create?
>
> when I either try to type INBOX or pick INBOX from the visual list.

In one account I have the INBOX in the same folder list as the other
folders. There I can save to INBOX by just giving the name.

In another account I have the INBOX plus some other folders for incoming
mail in one folder list, and folders for saved mail in another. There I
have to select the other folder list with the help of ^P first, and then I
can save to INBOX.


Mats

-----------------------------------------------------------------
Mats Dufberg                                 dufberg@narnia.pp.se
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588



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; Sat, 25 Jan 2003 03:01:57 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PB1uTk022653;
	Sat, 25 Jan 2003 03:01:56 -0800
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.12) with ESMTP id h0PB1qWb007403
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 25 Jan 2003 03:01:52 -0800
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.12) with SMTP id h0PAcYll012610;
	Sat, 25 Jan 2003 02:38:34 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PAWHCK043948
	for <pine-info@reallists.u.washington.edu>; Sat, 25 Jan 2003 02:32:17 -0800
Received: from mail.mtds.com (mail.mtds.com [194.204.200.6])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PAW7Fq011803
	for <pine-info@u.washington.edu>; Sat, 25 Jan 2003 02:32:08 -0800
Received: from pcRachid.mtds.com (pcRachid.mtds.com [194.204.200.44])
	by mail.mtds.com (Postfix) with ESMTP
	id B1827163528; Sat, 25 Jan 2003 10:32:06 +0000 (WET)
Message-Id: <1043490788.8498.3.camel@pcRachid.mtds.com>
Date: 25 Jan 2003 10:33:08 +0000
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: Abdelkhalak Rachid <a.rachid@mtds.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine Installation problem
In-Reply-To: 
	<Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu>
References: <1043425537.4734.19.camel@pcRachid.mtds.com> 
	<Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
X-To: Eduardo Chappa <chappa@math.washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I installed gcc compiler and i have now not the same error message:
thir is the end of the new error message:

cat CCTYPE` -c `cat CFLAGS` mmdf.c
`cat CCTYPE` -c `cat CFLAGS` tenex.c
`cat CCTYPE` -c `cat CFLAGS` mtx.c
`cat CCTYPE` -c `cat CFLAGS` news.c
news.c: In function `news_open':
news.c:309: warning: passing arg 3 of `scandir' from incompatible
pointer type
`cat CCTYPE` -c `cat CFLAGS` phile.c
`cat CCTYPE` -c `cat CFLAGS` mh.c
mh.c: In function `mh_ping':
mh.c:638: warning: passing arg 3 of `scandir' from incompatible pointer
type
mh.c: In function `mh_append':
mh.c:895: warning: passing arg 3 of `scandir' from incompatible pointer
type
`cat CCTYPE` -c `cat CFLAGS` mx.c
mx.c: In function `mx_ping':
mx.c:592: warning: passing arg 3 of `scandir' from incompatible pointer
type
sh -c 'rm -rf c-client.a || true'
ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o
siglocal.o dum
my.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o
imap4r1.o po
p3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o
mx.o;ranlib c-
client.a
make[3]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap/c-client'
make[2]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap/c-client'
echo lnx > OSTYPE
touch rebuild
sh -c 'rm -rf rebuild || true'
Building bundled tools...
cd mtest;make
make[2]: Entre dans le r=E9pertoire `/home/rachid/pine4.53/imap/mtest'
gcc -I../c-client `cat ../c-client/CFLAGS`   -c -o mtest.o mtest.c
gcc -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o
../c-client/c-client                                                       =
      .a `cat ../c-client/LDFLAGS`
mtest.o: In function `prompt':
/home/rachid/pine4.53/imap/mtest/mtest.c:517: the `gets' function is
dangerous a                                                           =20
nd should not be used.
../c-client/c-client.a(osdep.o): In function `checkpw':
/home/rachid/pine4.53/imap/c-client/osdep.c:77: undefined reference to
`crypt'
collect2: ld returned 1 exit status
make[2]: *** [mtest] Erreur 1
make[2]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap/mtest'
make[1]: *** [bundled] Erreur 2
make[1]: Quitte le r=E9pertoire `/home/rachid/pine4.53/imap'
make: *** [lnx] Erreur 2
+---------------------------------------------+
| Problems building c-client                  |
|                                             |
| Please check the output above for a         |
| possible explanation for this failure       |
+---------------------------------------------+

[root@pcRachid pine4.53]#


thanks a lot...

Rachid



Le ven 24/01/2003 =E0 17:06, Eduardo Chappa a =E9crit :
> *** Abdelkhalak Rachid (a.rachid@mtds.com) wrote in the pine-info list to=
day:
>=20
> [...]
> :) I have this message in the end of the operation:
> :) [...]
> :) /bin/sh: line 1: cc: command not found
>=20
> That line says that you need to install a C compiler. If you have
> installed gcc as your compiler try adding the parameter "CC=3Dgcc", so
> something like
>=20
> ./build NOSSL CC=3Dgcc lnx
>=20
> may work. If not, install a C compiler first.
>=20
> --=20
> 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; Sat, 25 Jan 2003 12:52:46 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PKqkTk002743;
	Sat, 25 Jan 2003 12:52:46 -0800
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.12) with ESMTP id h0PKqbnO011560
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 25 Jan 2003 12:52:42 -0800
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.12) with SMTP id h0PKoEll014902;
	Sat, 25 Jan 2003 12:50:15 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PGMgCK042812
	for <pine-info@reallists.u.washington.edu>; Sat, 25 Jan 2003 08:22:42 -0800
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PGMeFq021057
	for <pine-info@u.washington.edu>; Sat, 25 Jan 2003 08:22:40 -0800
Received: from goedel1.math.washington.edu (goedel1.math.washington.edu [128.95.224.10])
	by euler.math.washington.edu (8.11.6/8.11.6) with ESMTP id h0PGMbq48152;
	Sat, 25 Jan 2003 08:22:38 -0800 (PST)
Message-Id: <Pine.OSF.4.53.0301250820260.319670@goedel1.math.washington.edu>
Date: Sat, 25 Jan 2003 08:22:37 -0800 (PST)
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: Pine Installation problem
In-Reply-To: <1043490788.8498.3.camel@pcRachid.mtds.com>
References: <1043425537.4734.19.camel@pcRachid.mtds.com> 
 <Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Abdelkhalak Rachid <a.rachid@mtds.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Abdelkhalak Rachid (a.rachid@mtds.com) wrote today:

:) I installed gcc compiler and i have now not the same error message:
:) thir is the end of the new error message:
:)
:) /home/rachid/pine4.53/imap/c-client/osdep.c:77: undefined reference to
:) `crypt'

The error is different, you need to install the crypt library.

-- 
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; Sat, 25 Jan 2003 12:55:05 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PKt5Tk002816;
	Sat, 25 Jan 2003 12:55:05 -0800
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.12) with ESMTP id h0PKt0Wb020020
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 25 Jan 2003 12:55:01 -0800
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.12) with SMTP id h0PKqw09006038;
	Sat, 25 Jan 2003 12:52:58 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PIHXCK018984
	for <pine-info@reallists.u.washington.edu>; Sat, 25 Jan 2003 10:17:33 -0800
Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0PIHUHT017966
	for <pine-info@u.washington.edu>; Sat, 25 Jan 2003 10:17:31 -0800
Received: from cam.ac.uk ([80.4.5.243]) by mta06-svc.ntlworld.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20030125181726.FMBY20174.mta06-svc.ntlworld.com@cam.ac.uk>;
          Sat, 25 Jan 2003 18:17:26 +0000
Message-Id: <Pine.OS2.4.53.0301251816170.62@barry>
Date: Sat, 25 Jan 2003 18:16:49 +0000 (GMT)
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: Barry Landy <bl10@cam.ac.uk>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.WNT.4.53.0301240931490.1028@hubertw2k2_ndc.nebula.washington.edu>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Hubert <hubert@washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bl10@imap.hermes.cam.ac.uk
X-Uwash-Spam: Gauge=III, Probability=3%, Report="FROM_ENDS_IN_NUMS, IN_REP_TO, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_01_02"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Indeed; the original poster confessed to me (private email ) that he had
edited his addressbook by hand.

On Fri, 24 Jan 2003, Steve Hubert wrote:

:>On Thu, 23 Jan 2003, Barry Landy wrote:
:>
:>> On Thu, 23 Jan 2003, Marc Michalewicz wrote:
:>>
:>> :>> Actually, now I type that, Surely Pine does not allow you to have the
:>> :>> same nickname repeated in one addressbook?
:>> :>
:>> :>Yes, it works for me (ver 4.53).
:>> :>
:>>
:>> For me, it definitely faults any attempt to do that (also 4.53). Can we
:>> have an official view as to what the intention is, please.
:>
:>I believe we try to catch attempts to add entries with identical
:>nicknames, and even prevent you from doing so if the other entry is in the
:>same address book. If the address book already has multiple entries we do
:>not try to fix it, but return only the first entry when the nickname is
:>typed in.
:>
:>The intent is that each entry should have a unique nickname.
:>
:>Steve
:>

-- 
Barry Landy                        Home:               +44-1223-570417
192, Gilbert Road                  College:            +44-1223-332058
Cambridge CB4 3PB                  Email:BL10@cam.ac.uk

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, 27 Jan 2003 01:37:32 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R9bWTk019683;
	Mon, 27 Jan 2003 01:37:32 -0800
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.12) with ESMTP id h0R9bSWb003087
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 27 Jan 2003 01:37:29 -0800
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.12) with SMTP id h0R9XGDb083078;
	Mon, 27 Jan 2003 01:33:16 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R8tCCK017372
	for <pine-info@reallists.u.washington.edu>; Mon, 27 Jan 2003 00:55:12 -0800
Received: from ascomax.hasler.ascom.ch (ascomax.hasler.ascom.ch [139.79.135.1])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R8t9Fq009222
	for <pine-info@u.washington.edu>; Mon, 27 Jan 2003 00:55:10 -0800
Received: from stva195.pbx.ascom.ch (stva195.pbxnet.ch [172.20.56.47])
	by ascomax.hasler.ascom.ch (8.11.4/8.11.4) with ESMTP id h0R8t5Y18251;
	Mon, 27 Jan 2003 09:55:06 +0100 (MET)
Received: from stva146 (localhost [127.0.0.1])
	by stva195.pbx.ascom.ch (8.12.1/8.12.1) with ESMTP id h0R8t3GM025589;
	Mon, 27 Jan 2003 09:55:03 +0100 (MET)
Message-Id: <Pine.GSO.4.53.0301270954170.20904@stva146>
Date: Mon, 27 Jan 2003 09:55:02 +0100 (MET)
Reply-To: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
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: Marc Michalewicz <Marc.Michalewicz@ascom.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: one nickname for more than one address -> how ?
In-Reply-To: <Pine.OS2.4.53.0301251816170.62@barry>
References: <Pine.GSO.4.53.0301231125040.18953@stva146>
 <Pine.OS2.4.53.0301231103330.114@csfpc2.fitz.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Barry Landy <bl10@cam.ac.uk>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: bmichm@stva146
X-Filter-Version: 1.6 (ascomax)
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Sat, 25 Jan 2003, Barry Landy wrote:

> Indeed; the original poster confessed to me (private email ) that he had
> edited his addressbook by hand.

Sorry for my mistake, I should have posted this to the list as either.
That was accidentally.

Marc


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, 27 Jan 2003 04:05:37 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RC5aTk024767;
	Mon, 27 Jan 2003 04:05:36 -0800
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.12) with ESMTP id h0RC5WWb006144
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 27 Jan 2003 04:05:33 -0800
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.12) with SMTP id h0RC1aDb089970;
	Mon, 27 Jan 2003 04:01:37 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RBwJCK043704
	for <pine-info@reallists.u.washington.edu>; Mon, 27 Jan 2003 03:58:19 -0800
Received: from mail.mtds.com (mail.mtds.com [194.204.200.6])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RBwGfV004092
	for <pine-info@u.washington.edu>; Mon, 27 Jan 2003 03:58:17 -0800
Received: from pcRachid.mtds.com (pcRachid.mtds.com [194.204.200.44])
	by mail.mtds.com (Postfix) with ESMTP
	id 054F2163504; Mon, 27 Jan 2003 11:58:15 +0000 (WET)
Message-Id: <1043668758.2166.3.camel@pcRachid.mtds.com>
Date: 27 Jan 2003 11:59:17 +0000
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: Abdelkhalak Rachid <a.rachid@mtds.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine Installation problem
In-Reply-To: 
	<Pine.OSF.4.53.0301250820260.319670@goedel1.math.washington.edu>
References: <1043425537.4734.19.camel@pcRachid.mtds.com> 
	<Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
X-To: Eduardo Chappa <chappa@math.washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Thanks for your help,
You know i'm a newbie in Linux and i dont know how to install the Crypt
library, I check in the packages list and i dont find any package with
this name, can you give me an indice please?????

thanks a lot.



Le sam 25/01/2003 =E0 16:22, Eduardo Chappa a =E9crit :
> *** Abdelkhalak Rachid (a.rachid@mtds.com) wrote today:
>=20
> :) I installed gcc compiler and i have now not the same error message:
> :) thir is the end of the new error message:
> :)
> :) /home/rachid/pine4.53/imap/c-client/osdep.c:77: undefined reference to
> :) `crypt'
>=20
> The error is different, you need to install the crypt library.
>=20
> --=20
> 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; Mon, 27 Jan 2003 04:16:03 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RCG2Tk025294;
	Mon, 27 Jan 2003 04:16:02 -0800
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.12) with ESMTP id h0RCFwWb006411
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 27 Jan 2003 04:15:59 -0800
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.12) with SMTP id h0RCCADb083452;
	Mon, 27 Jan 2003 04:12:10 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RC8uCK011884
	for <pine-info@reallists.u.washington.edu>; Mon, 27 Jan 2003 04:08:56 -0800
Received: from mail.mtds.com (mail.mtds.com [194.204.200.6])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RC8rfV005516
	for <pine-info@u.washington.edu>; Mon, 27 Jan 2003 04:08:54 -0800
Received: from pcRachid.mtds.com (pcRachid.mtds.com [194.204.200.44])
	by mail.mtds.com (Postfix) with ESMTP
	id 1AECF163599; Mon, 27 Jan 2003 12:08:53 +0000 (WET)
Message-Id: <1043669396.4802.13.camel@pcRachid.mtds.com>
Date: 27 Jan 2003 12:09:56 +0000
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: Abdelkhalak Rachid <a.rachid@mtds.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine Installation problem
In-Reply-To: <1043668758.2166.3.camel@pcRachid.mtds.com>
References: <1043425537.4734.19.camel@pcRachid.mtds.com> 
	<Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu> 
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
X-To: Abdelkhalak Rachid <a.rachid@mtds.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report="FROM_AND_TO_SAME_2, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SPAM_PHRASE_05_08, __EVITE_CTYPE, __HAS_X_MAILER"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I posted a questions too about possibility to have a compliled Directory
of Pine (Like in Windows Version) and i have just to copy it in a
specific dir for working with.... is possible?

thanks

Le lun 27/01/2003 =E0 11:59, Abdelkhalak Rachid a =E9crit :
> Thanks for your help,
> You know i'm a newbie in Linux and i dont know how to install the Crypt
> library, I check in the packages list and i dont find any package with
> this name, can you give me an indice please?????
>=20
> thanks a lot.
>=20
>=20
>=20
> Le sam 25/01/2003 =E0 16:22, Eduardo Chappa a =E9crit :
> > *** Abdelkhalak Rachid (a.rachid@mtds.com) wrote today:
> >=20
> > :) I installed gcc compiler and i have now not the same error message:
> > :) thir is the end of the new error message:
> > :)
> > :) /home/rachid/pine4.53/imap/c-client/osdep.c:77: undefined reference =
to
> > :) `crypt'
> >=20
> > The error is different, you need to install the crypt library.
> >=20
> > --=20
> > Eduardo
> > http://www.math.washington.edu/~chappa/pine/
>=20
>=20



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, 27 Jan 2003 05:07:13 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RD7CTk026420;
	Mon, 27 Jan 2003 05:07:12 -0800
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.12) with ESMTP id h0RD78nO032095
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 27 Jan 2003 05:07:09 -0800
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.12) with SMTP id h0RD2RDb015682;
	Mon, 27 Jan 2003 05:02:27 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RCwwCK036878
	for <pine-info@reallists.u.washington.edu>; Mon, 27 Jan 2003 04:58:58 -0800
Received: from smtp3.clb.oleane.net (smtp3.clb.oleane.net [213.56.31.19])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0RCwpfV010644
	for <pine-info@u.washington.edu>; Mon, 27 Jan 2003 04:58:56 -0800
Received: from cnam.fr ([217.109.163.218]) 
	by smtp3.clb.oleane.net with ESMTP id h0RCvBaP002192;
	Mon, 27 Jan 2003 13:57:11 +0100
Message-Id: <3E352D77.60304@cnam.fr>
Date: Mon, 27 Jan 2003 14:00:39 +0100
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: Erwan Becquet <becquet@cnam.fr>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine Installation problem
In-Reply-To: <1043425537.4734.19.camel@pcRachid.mtds.com>
References: <1043425537.4734.19.camel@pcRachid.mtds.com> 	<Pine.OSF.4.53.0301240903340.308236@goedel2.math.washington.edu> <1043669396.4802.13.camel@pcRachid.mtds.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
X-To: Abdelkhalak Rachid <a.rachid@mtds.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Accept-Language: en-us, en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=XX, Probability=20%, Report="IN_REP_TO, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, REFERENCES, SPAM_PHRASE_05_08, X_ACCEPT_LANG, __EVITE_CTYPE"

Hi there,

yes it is possible to install binary packages in LinuX. They are called RPM
(stand for RedHat Package Manager). Try to get a rpm file for pine at
http://rpmfind.net/ , enter 'pine' in search window.

Once you get the pine-4.xxxxxx.rpm file, type 'rpm -Uhv pine.4-xxx.rpm' as
root.

The RPM installer can complain about missing packages (crypt for example)
you can then try to get a rpm file for missing packages.

Hope this help. Erwan.

Abdelkhalak Rachid wrote:

>http://www.kde.org/download.htmlI posted a questions too about possibility to have a compliled Directory
>of Pine (Like in Windows Version) and i have just to copy it in a
>specific dir for working with.... is possible?
>
>thanks
>
>Le lun 27/01/2003 à 11:59, Abdelkhalak Rachid a écrit :
>  
>
>>Thanks for your help,
>>You know i'm a newbie in Linux and i dont know how to install the Crypt
>>library, I check in the packages list and i dont find any package with
>>this name, can you give me an indice please?????
>>
>>thanks a lot.
>>
>>
>>
>>Le sam 25/01/2003 à 16:22, Eduardo Chappa a écrit :
>>    
>>
>>>*** Abdelkhalak Rachid (a.rachid@mtds.com) wrote today:
>>>
>>>:) I installed gcc compiler and i have now not the same error message:
>>>:) thir is the end of the new error message:
>>>:)
>>>:) /home/rachid/pine4.53/imap/c-client/osdep.c:77: undefined reference to
>>>:) `crypt'
>>>
>>>The error is different, you need to install the crypt library.
>>>
>>>-- 
>>>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; Mon, 27 Jan 2003 21:00:39 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0S50cTk026881;
	Mon, 27 Jan 2003 21:00:38 -0800
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.12) with ESMTP id h0S50XnO029189
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 27 Jan 2003 21:00:34 -0800
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.12) with SMTP id h0S4u7ll010534;
	Mon, 27 Jan 2003 20:56:07 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0S4t9CK059168
	for <pine-info@reallists.u.washington.edu>; Mon, 27 Jan 2003 20:55:10 -0800
Received: from web40107.mail.yahoo.com (web40107.mail.yahoo.com [66.218.78.41])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0S4t8HT020879
	for <pine-info@u.washington.edu>; Mon, 27 Jan 2003 20:55:08 -0800
Received: from [202.62.83.75] by web40107.mail.yahoo.com via HTTP; Mon, 27 Jan 2003 20:55:08 PST
Message-Id: <20030128045508.7022.qmail@web40107.mail.yahoo.com>
Date: Mon, 27 Jan 2003 20:55:08 -0800 (PST)
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: nimit gupta <nimit_g@yahoo.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: unsubscribe
In-Reply-To: <3E352D77.60304@cnam.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

 
 

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-- 
-----------------------------------------------------------------
 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; Tue, 28 Jan 2003 07:18:46 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SFIjTk010364;
	Tue, 28 Jan 2003 07:18:45 -0800
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.12) with ESMTP id h0SFIfnO010028
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 07:18:42 -0800
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.12) with SMTP id h0SFEm09014330;
	Tue, 28 Jan 2003 07:14:48 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SFCBCK050496
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 07:12:12 -0800
Received: from cipactli.iingen.unam.mx (cipactli.iingen.unam.mx [132.248.53.1])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SFC6Z7016210
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 07:12:06 -0800
Received: (from apache@localhost)
	by cipactli.iingen.unam.mx (8.11.6/8.11.6) id h0SFGU830810
	for pine-info@u.washington.edu; Tue, 28 Jan 2003 09:16:30 -0600
Received: from 132.248.53.245 ( [132.248.53.245])
	as user alberto@pumas.iingen.unam.mx by cipactli.iingen.unam.mx with HTTP;
	Tue, 28 Jan 2003 09:16:30 -0600
Message-Id: <1043766990.3e369ece0ed2d@cipactli.iingen.unam.mx>
Date: Tue, 28 Jan 2003 09:16:30 -0600
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: Alberto Barron <alberto@pumas.iingen.unam.mx>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: unsuscribe
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: cipactli.iingen.unam.mx: apache set sender to alberto@pumas.iingen.unam.mx using -f
X-Originating-IP: 132.248.53.245
X-Uwash-Spam: Gauge=XXXXXXI, Probability=61%, Report="NO_MX_FOR_FROM, RCVD_IN_OSIRUSOFT_COM, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, X_AUTH_WARNING, X_OSIRU_DUL_FH, X_OSIRU_OPEN_RELAY, __EVITE_CTYPE"
X-Uwash-Spam: Gauge=XXXIIIIII, Probability=36%, Report="LINES_OF_YELLING, NO_MX_FOR_FROM, RCVD_IN_OSIRUSOFT_COM, SIGNATURE_SHORT_SPARSE, UPPERCASE_50_75, USER_AGENT, USER_AGENT_IMP, X_AUTH_WARNING, X_OSIRU_DUL_FH, X_OSIRU_OPEN_RELAY, __EVITE_CTYPE, __UPPERCASE_50_75"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



-- 


-------------------------------------------------
       INSTITUTO DE INGENIERÍA, U.N.A.M.
-- 
-----------------------------------------------------------------
 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; Tue, 28 Jan 2003 10:44:39 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIibTk018686;
	Tue, 28 Jan 2003 10:44:38 -0800
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.12) with ESMTP id h0SIiXnO018030
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 10:44:35 -0800
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.12) with SMTP id h0SIbaDb093368;
	Tue, 28 Jan 2003 10:37:37 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIWaCK033852
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 10:32:36 -0800
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIWVkq026692
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 10:32:31 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIWRGD015945;
	Tue, 28 Jan 2003 10:32:27 -0800
Received: from [128.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIWRup023548
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 28 Jan 2003 10:32:27 -0800
Message-Id: <Pine.WNT.4.54.0301281029340.1376@hubertw2k2_ndc.nebula.washington.edu>
Date: Tue, 28 Jan 2003 10:32:27 -0800 (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: bug in Pine 4.53 ?
In-Reply-To: <Pine.WNT.4.53.0301201712050.-1553973@Haendel.noack.ccn>
References: <Pine.WNT.4.53.0301151151580.1336@hubertw2k2_ndc.nebula.washington.edu>
 <Pine.WNT.4.53.0301201712050.-1553973@Haendel.noack.ccn>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
X-To: "Cornelius C. Noack" <noack@physik.uni-bremen.de>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 20 Jan 2003, Cornelius C. Noack wrote:

> (I am using pcpine)
>
> In my pinerc. I have set both
>             enable-alternate-editor-cmd            and
>             editor=C:\$user\Editors\TSE_2.5\e.exe  (which exists!)
>
> Nevertheless, when I call the alternate editor, I get the
> "Which alternate Editor?" window. This was not so in previous
> releases.
>
> Same thing happens a fortiori if I also set
>             enable-alternate-editor-implicitly    .
>
>
> ccn

Try putting braces around user

     editor=C:\${user}\Editors\TSE_2.5\e.exe

Pine doesn't treat \ as a special character that ends the $var word so it
is trying to find

     ${user\Editors\TSE_2.5\e.exe}

instead of

     ${user}\Editors\TSE_2.5\e.exe

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

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, 28 Jan 2003 10:50:56 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIotTk018988;
	Tue, 28 Jan 2003 10:50:55 -0800
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.12) with ESMTP id h0SIodnO018249
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 10:50:44 -0800
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.12) with SMTP id h0SIhc09028256;
	Tue, 28 Jan 2003 10:43:39 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIXqCK041764
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 10:33:52 -0800
Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIXoHU022153
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 10:33:50 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIXlAa024258;
	Tue, 28 Jan 2003 10:33:47 -0800
Received: from [128.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIXlTZ021436
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 28 Jan 2003 10:33:47 -0800
Message-Id: <Pine.WNT.4.54.0301281033200.1376@hubertw2k2_ndc.nebula.washington.edu>
Date: Tue, 28 Jan 2003 10:33:47 -0800 (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: auto jump to inbox
In-Reply-To: <Pine.GSO.4.51.0301211057480.14417@boondoggle.office.aol.com>
References: <Pine.GSO.4.51.0301211057480.14417@boondoggle.office.aol.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
X-To: Brian Harvell <harvell@aol.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 21 Jan 2003, Brian Harvell wrote:

>
> Is there a way to disable the question of
>
> No more incoming folders.  Return to "INBOX"?
>
> and just make it jump to the inbox?
>
> Brian

We'll add a feature to do that in the next version of pine. Thanks.

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


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, 28 Jan 2003 11:10:52 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SJApTk020098;
	Tue, 28 Jan 2003 11:10:51 -0800
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.12) with ESMTP id h0SJAmWb026335
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 11:10:49 -0800
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.12) with SMTP id h0SJ3S09005602;
	Tue, 28 Jan 2003 11:03:28 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIwqCK052952
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 10:58:52 -0800
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIwofW022223
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 10:58:50 -0800
Received: from hymn01.u.washington.edu (hymn01.u.washington.edu [140.142.15.155])
	by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIwnGD021593
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 10:58:49 -0800
Received: from localhost (localhost [127.0.0.1])
	by hymn01.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SIwnrt014609
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 10:58:49 -0800
Message-Id: <Pine.LNX.4.43.0301281058490.13703@hymn01.u.washington.edu>
Date: Tue, 28 Jan 2003 10:58:49 -0800 (PST)
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: Kerryanne C Tulabut <rawhoney@u.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: unsubscribe
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

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

From 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, 28 Jan 2003 11:59:38 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SJxbTk022434;
	Tue, 28 Jan 2003 11:59:37 -0800
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.12) with ESMTP id h0SJxXWb028026
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 11:59:34 -0800
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.12) with SMTP id h0SJqmDb083040;
	Tue, 28 Jan 2003 11:52:48 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SJoeCK083266
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 11:50:40 -0800
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SJocFr015012
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 11:50:38 -0800
Received: from northrelay05.pok.ibm.com (northrelay05.pok.ibm.com [9.56.224.23])
	by e3.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0SJobvr064022
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 14:50:37 -0500
Received: from newcowboy.lexington.ibm.com (newcowboy.lexington.ibm.com [9.51.92.23])
	by northrelay05.pok.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0SJoZsB199246
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 14:50:36 -0500
Received: from badlands.lexington.ibm.com (localhost [127.0.0.1])
	(authenticated (1 bits))
	by localhost (8.12.7/8.12.7/Debian-3) with ESMTP id h0SJmfVN021903
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 14:48:41 -0500
Received: (from cowboy@localhost)
	by badlands.lexington.ibm.com (8.12.7/8.12.7/Debian-3) id h0SJmfZd021902
	for pine-info@u.washington.edu; Tue, 28 Jan 2003 14:48:41 -0500
Message-Id: <200301281948.h0SJmfZd021902@badlands.lexington.ibm.com>
Date: Tue, 28 Jan 2003 14:48:41 -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: Richard A Nelson <cowboy@vnet.ibm.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: problem going from 4.51 to 4.53
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01"


After starting up 4.53 (on a profile used for 4.51 and below), I'm now 
getting this error when attempting to send mail :

Problem detected: "Botch in radio_buttons(): too many keys".
Pine Exiting.

Any clue what I can do to get that fixed ?

Thanks,
-- 
Rick
-- 
-----------------------------------------------------------------
 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; Tue, 28 Jan 2003 12:08:39 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SK8cTk022905;
	Tue, 28 Jan 2003 12:08:38 -0800
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.12) with ESMTP id h0SK8ZWb028434
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 12:08:35 -0800
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.12) with SMTP id h0SK0709027586;
	Tue, 28 Jan 2003 12:00:07 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SJwLCK016892
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 11:58:21 -0800
Received: from postman4.mx.aol.com (postman4.mx.aol.com [205.188.157.131])
	by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SJw7M5008268;
	Tue, 28 Jan 2003 11:58:08 -0800
Received: from boondoggle.office.aol.com (boondoggle.office.aol.com [10.0.22.159])
	by postman4.mx.aol.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id OAA12457;
	Tue, 28 Jan 2003 14:58:07 -0500 (EST)
Received: (from harvell@localhost)
	by boondoggle.office.aol.com (8.11.6/8.11.6) id h0SJw6s12232;
	Tue, 28 Jan 2003 14:58:06 -0500 (EST)
Message-Id: <Pine.GSO.4.53.0301281455140.12178@boondoggle.office.aol.com>
Date: Tue, 28 Jan 2003 14:58:06 -0500 (EST)
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: Brian Harvell <harvell@aol.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: auto jump to inbox
In-Reply-To: <Pine.WNT.4.54.0301281033200.1376@hubertw2k2_ndc.nebula.washington.edu>
References: <Pine.GSO.4.51.0301211057480.14417@boondoggle.office.aol.com>
 <Pine.WNT.4.54.0301281033200.1376@hubertw2k2_ndc.nebula.washington.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1804928587-1043783886=:12178"
X-To: Steve Hubert <hubert@washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: harvell@boondoggle.office.aol.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="BASE64_ENC_TEXT, IN_REP_TO, MIME_NULL_BLOCK, MSG_ID_ADDED_BY_MTA_3, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02, USER_AGENT_PINE"

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

---559023410-1804928587-1043783886=:12178
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 28 Jan 2003, Steve Hubert wrote:
>
> We'll add a feature to do that in the next version of pine. Thanks.
>

A friend of mine made this patch against the 4.53 uber patched pine at

http://www.math.washington.edu/~chappa/pine/patches/pine4.53/pine4.53.tar.gz

It works great for me.

Brian



-- 

Brian Harvell                harvell@aol.net             http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc


---559023410-1804928587-1043783886=:12178
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="pine-4.53-inbox_patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.GSO.4.53.0301281458060.12178@boondoggle.office.aol.com>
Content-Description: 
Content-Disposition: attachment; filename="pine-4.53-inbox_patch"

ZGlmZiAtciAtVSA1IHBpbmU0LjUzL3BpbmUvaW5pdC5jIHBpbmU0LjUzLWlu
Ym94X3BhdGNoL3BpbmUvaW5pdC5jDQotLS0gcGluZTQuNTMvcGluZS9pbml0
LmMJRnJpIEphbiAyNCAxMjozODowMCAyMDAzDQorKysgcGluZTQuNTMtaW5i
b3hfcGF0Y2gvcGluZS9pbml0LmMJRnJpIEphbiAyNCAxNzo1NTo0NCAyMDAz
DQpAQCAtMjU3MiwxMCArMjU3MiwxMiBAQA0KIC8qIEluZGV4IHByZWZzICov
DQogCXsiYXV0by1vcGVuLW5leHQtdW5yZWFkIiwNCiAJIEZfQVVUT19PUEVO
X05FWFRfVU5SRUFELCBoX2NvbmZpZ19hdXRvX29wZW5fdW5yZWFkLCBQUkVG
X0lORFh9LA0KICAgICAgICAgeyJlbmFibGUtY2lyY3VsYXItdGFiIiwNCiAg
ICAgICAgICBGX0FVVE9fQ0lSQ1VMQVJfVEFCLCBoX2NvbmZpZ19jaXJjdWxh
cl90YWIsIFBSRUZfSU5EWH0sDQorICAgICAgICB7InJldHVybi10by1pbmJv
eC13aXRob3V0LWNvbmZpcm0iLA0KKyAgICAgICAgIEZfUkVUVVJOX1RPX0lO
Qk9YX1dJVEhPVVRfQ09ORklSTSwgcmV0dXJuX3RvX2luYm94X3dpdGhvdXRf
Y29uZmlybSwgUFJFRl9JTkRYfSwNCiAJeyJ0aHJlYWQtaW5kZXgtc2hvd3Mt
aW1wb3J0YW50LWNvbG9yIiwNCiAJIEZfQ09MT1JfTElORV9JTVBPUlRBTlQs
IGhfY29uZmlnX2NvbG9yX3RocmRfaW1wb3J0LCBQUkVGX0lORFh9LA0KIAl7
ImVuaGFuY2VkLWZhbmN5LXRocmVhZC1zdXBwb3J0IiwNCiAJIEZfRU5IQU5D
RURfVEhSRUFELCBoX2NvbmZpZ19lbmhhbmNlZF90aHJlYWQsIFBSRUZfSU5E
WH0sDQogCXsiY29udGludWUtdGFiLXdpdGhvdXQtY29uZmlybSIsDQpkaWZm
IC1yIC1VIDUgcGluZTQuNTMvcGluZS9tYWlsY21kLmMgcGluZTQuNTMtaW5i
b3hfcGF0Y2gvcGluZS9tYWlsY21kLmMNCi0tLSBwaW5lNC41My9waW5lL21h
aWxjbWQuYwlGcmkgSmFuIDI0IDEyOjM4OjAzIDIwMDMNCisrKyBwaW5lNC41
My1pbmJveF9wYXRjaC9waW5lL21haWxjbWQuYwlGcmkgSmFuIDI0IDE3OjU4
OjE2IDIwMDMNCkBAIC05MTgsMTkgKzkxOCwyMyBAQA0KIAkJCQl7J24nLCAn
bicsICJOIiwgIk5vIn0sDQogCQkJCXtUQUIsICd6JywgIlRhYiIsICJUbyBJ
bmJveCJ9LA0KIAkJCQl7LTEsIDAsIE5VTEwsIE5VTEx9DQogCQkJICAgIH07
DQogDQotCQkJICAgIHNwcmludGYocHJvbXB0LA0KLQkJCQkgICAgIk5vIG1v
cmUgJXNzLiAgUmV0dXJuIHRvIFwiJS4qc1wiPyAiLA0KLQkJCQkgICAgKHN0
YXRlLT5jb250ZXh0X2N1cnJlbnQtPnVzZSZDTlRYVF9JTkNNTkcpDQotCQkJ
CSAgICAgID8gImluY29taW5nIGZvbGRlciIgOiAibmV3cyBncm91cCIsIA0K
LQkJCQkgICAgc2l6ZW9mKHByb21wdCktNDAsIHN0YXRlLT5pbmJveF9uYW1l
KTsNCisgICAgICAgICAgICAgICAgICAgICAgICAgICAgaWYgKCBGX09GRihG
X1JFVFVSTl9UT19JTkJPWF9XSVRIT1VUX0NPTkZJUk0sc3RhdGUpICkgew0K
KwkJCSAgICAgIHNwcmludGYocHJvbXB0LA0KKwkJCQkgICAgICAiTm8gbW9y
ZSAlc3MuICBSZXR1cm4gdG8gXCIlLipzXCI/ICIsDQorCQkJCSAgICAgIChz
dGF0ZS0+Y29udGV4dF9jdXJyZW50LT51c2UmQ05UWFRfSU5DTU5HKQ0KKwkJ
CQkgICAgICAgID8gImluY29taW5nIGZvbGRlciIgOiAibmV3cyBncm91cCIs
IA0KKwkJCQkgICAgICBzaXplb2YocHJvbXB0KS00MCwgc3RhdGUtPmluYm94
X25hbWUpOw0KIA0KLQkJCSAgICByZXQgPSByYWRpb19idXR0b25zKHByb21w
dCwgLUZPT1RFUl9ST1dTKHN0YXRlKSwNCi0JCQkJCQlpbmJveF9vcHQsICd5
JywgJ3gnLA0KLQkJCQkJCU5PX0hFTFAsIFJCX05PUk0pOw0KKwkJCSAgICAg
IHJldCA9IHJhZGlvX2J1dHRvbnMocHJvbXB0LCAtRk9PVEVSX1JPV1Moc3Rh
dGUpLA0KKwkJCSAgCQkJICBpbmJveF9vcHQsICd5JywgJ3gnLA0KKwkJCQkJ
CSAgTk9fSEVMUCwgUkJfTk9STSk7DQorICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIH0gZWxzZSB7DQorICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgcmV0ID0gJ3knOw0KKyAgICAgICAgICAgICAgICAgICAgICAgICAgICB9
DQogDQogCQkJICAgIC8qDQogCQkJICAgICAqICd6JyBpcyBhIHN5bm9ueW0g
Zm9yICd5Jy4gIEl0IGlzIG5vdCAneScNCiAJCQkgICAgICogc28gdGhhdCBp
dCBpc24ndCBkaXNwbGF5ZWQgYXMgYSBkZWZhdWx0DQogCQkJICAgICAqIGFj
dGlvbiB3aXRoIHNxdWFyZS1icmFja2V0cyBhcm91bmQgaXQNCmRpZmYgLXIg
LVUgNSBwaW5lNC41My9waW5lL3BpbmUuaCBwaW5lNC41My1pbmJveF9wYXRj
aC9waW5lL3BpbmUuaA0KLS0tIHBpbmU0LjUzL3BpbmUvcGluZS5oCUZyaSBK
YW4gMjQgMTI6Mzg6MTEgMjAwMw0KKysrIHBpbmU0LjUzLWluYm94X3BhdGNo
L3BpbmUvcGluZS5oCUZyaSBKYW4gMjQgMTc6NTY6MjYgMjAwMw0KQEAgLTEw
NzQsMTAgKzEwNzQsMTEgQEANCiAJRl9GT1JDRV9MT1dfU1BFRUQsDQogCUZf
QUxUX0VEX05PVywNCiAJRl9TSE9XX0RFTEFZX0NVRSwNCiAJRl9BVVRPX09Q
RU5fTkVYVF9VTlJFQUQsDQogCUZfQVVUT19DSVJDVUxBUl9UQUIsDQorICAg
ICAgICBGX1JFVFVSTl9UT19JTkJPWF9XSVRIT1VUX0NPTkZJUk0sDQogCUZf
U0VMRUNURURfU0hPV05fQk9MRCwNCiAJRl9RVU9URV9BTExfRlJPTVMsDQog
CUZfQVVUT19JTkNMVURFX0lOX1JFUExZLA0KIAlGX0RJU0FCTEVfQ09ORklH
X1NDUkVFTiwNCiAJRl9ESVNBQkxFX1BBU1NXT1JEX0NBQ0hJTkcsDQpkaWZm
IC1yIC1VIDUgcGluZTQuNTMvcGluZS9waW5lLmhscCBwaW5lNC41My1pbmJv
eF9wYXRjaC9waW5lL3BpbmUuaGxwDQotLS0gcGluZTQuNTMvcGluZS9waW5l
LmhscAlGcmkgSmFuIDI0IDEyOjM4OjE0IDIwMDMNCisrKyBwaW5lNC41My1p
bmJveF9wYXRjaC9waW5lL3BpbmUuaGxwCUZyaSBKYW4gMjQgMTg6MjA6NDMg
MjAwMw0KQEAgLTI1ODAsMTAgKzI1ODAsMTEgQEANCiA8bGk+PGEgaHJlZj0i
aF9jb25maWdfYWxsb3dfY2hnX2Zyb20iPkZFQVRVUkU6IGFsbG93LWNoYW5n
aW5nLWZyb208L2E+DQogPGxpPjxhIGhyZWY9ImhfY29uZmlnX2F1dG9fcmVh
ZF9tc2dzIj5GRUFUVVJFOiBhdXRvLW1vdmUtcmVhZC1tc2dzPC9hPg0KIDxs
aT48YSBocmVmPSJoX2NvbmZpZ19hdXRvX3JlYWRfbXNnc19ydWxlcyI+RkVB
VFVSRTogYXV0by1tb3ZlLXJlYWQtbXNncy11c2luZy1ydWxlczwvYT4NCiA8
bGk+PGEgaHJlZj0iaF9jb25maWdfYXV0b19vcGVuX3VucmVhZCI+RkVBVFVS
RTogYXV0by1vcGVuLW5leHQtdW5yZWFkPC9hPg0KIDxsaT48YSBocmVmPSJo
X2NvbmZpZ19jaXJjdWxhcl90YWIiPkZFQVRVUkU6IGVuYWJsZS1jaXJjdWxh
ci10YWI8L2E+DQorPGxpPjxhIGhyZWY9InJldHVybl90b19pbmJveF93aXRo
b3V0X2NvbmZpcm0iPkZFQVRVUkU6IHJldHVybi10by1pbmJveC13aXRob3V0
LWNvbmZpcm08L2E+DQogPGxpPjxhIGhyZWY9ImhfY29uZmlnX2NvbWJpbmVk
X2Fib29rX2Rpc3BsYXkiPkZFQVRVUkU6IGNvbWJpbmVkLWFkZHJib29rLWRp
c3BsYXk8L2E+DQogPGxpPjxhIGhyZWY9ImhfY29uZmlnX2NvbWJpbmVkX2Zv
bGRlcl9kaXNwbGF5Ij5GRUFUVVJFOiBjb21iaW5lZC1mb2xkZXItZGlzcGxh
eTwvYT4NCiA8bGk+PGEgaHJlZj0iaF9jb25maWdfY29tYmluZWRfc3ViZGly
X2Rpc3BsYXkiPkZFQVRVUkU6IGNvbWJpbmVkLXN1YmRpcmVjdG9yeS1kaXNw
bGF5PC9hPg0KIDxsaT48YSBocmVmPSJoX2NvbmZpZ19jb21wb3NlX3JlamVj
dHNfdW5xdWFsIj5GRUFUVVJFOiBjb21wb3NlLXJlamVjdHMtdW5xdWFsaWZp
ZWQtYWRkcnM8L2E+DQogPGxpPjxhIGhyZWY9ImhfY29uZmlnX3NlbmRfZmls
dGVyX2RmbHQiPkZFQVRVUkU6IGNvbXBvc2Utc2VuZC1vZmZlcnMtZmlyc3Qt
ZmlsdGVyPC9hPg0KQEAgLTIyNjYyLDEwICsyMjY2MywyNiBAQA0KIDxMST48
QSBIUkVGPSJoX2ZpbmRpbmdfaGVscCI+RmluZGluZyBtb3JlIGluZm9ybWF0
aW9uIGFuZCByZXF1ZXN0aW5nIGhlbHA8L0E+DQogPC9VTD48UD4NCiAmbHQ7
RW5kIG9mIGhlbHAgb24gdGhpcyB0b3BpYyZndDsNCiA8L0JPRFk+DQogPC9I
VE1MPg0KKz09PT09PSByZXR1cm5fdG9faW5ib3hfd2l0aG91dF9jb25maXJt
ID09PT09DQorPEhUTUw+DQorPEhFQUQ+DQorPFRJVExFPkZFQVRVUkU6IHJl
dHVybi10by1pbmJveC13aXRob3V0LWNvbmZpcm0gPC9USVRMRT4NCis8L0hF
QUQ+DQorPEJPRFk+DQorPEgxPkZFQVRVUkU6IHJldHVybi10by1pbmJveC13
aXRob3V0LWNvbmZpcm0gPC9IMT4NCisNCis8UD4NCitEbyBub3QgcHJvbXB0
IHRvIHJldHVybiB0byBpbmJveCBhdCB0aGUgZW5kIG9mIGluY29taW5nIGZv
bGRlcnMuDQorPFVMPg0KKzxMST48QSBIUkVGPSJoX2ZpbmRpbmdfaGVscCI+
RmluZGluZyBtb3JlIGluZm9ybWF0aW9uIGFuZCByZXF1ZXN0aW5nIGhlbHA8
L0E+DQorPC9VTD48UD4NCismbHQ7RW5kIG9mIGhlbHAgb24gdGhpcyB0b3Bp
YyZndDsNCis8L0JPRFk+DQorPC9IVE1MPg0KID09PT09PSBoX2NvbmZpZ19h
dXRvX2luY2x1ZGVfcmVwbHkgPT09PT0NCiA8SFRNTD4NCiA8SEVBRD4NCiA8
VElUTEU+RkVBVFVSRTogaW5jbHVkZS10ZXh0LWluLXJlcGx5PC9USVRMRT4N
CiA8L0hFQUQ+DQo=

---559023410-1804928587-1043783886=:12178--

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, 28 Jan 2003 12:17:04 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKH3Tk023252;
	Tue, 28 Jan 2003 12:17:03 -0800
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.12) with ESMTP id h0SKH0nO021494
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 12:17:00 -0800
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.12) with SMTP id h0SKCPjm028212;
	Tue, 28 Jan 2003 12:12:26 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKAZCK016880
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 12:10:35 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKAXkq030477
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 12:10:33 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKAWJA016429;
	Tue, 28 Jan 2003 12:10:32 -0800
Received: from [128.95.135.3] ([128.95.135.3])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKAVup028616
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 28 Jan 2003 12:10:32 -0800
Message-Id: <Pine.WNT.4.54.0301281209050.1192@hubertw2k2_ndc.nebula.washington.edu>
Date: Tue, 28 Jan 2003 12:10:31 -0800 (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 going from 4.51 to 4.53
In-Reply-To: <200301281948.h0SJmfZd021902@badlands.lexington.ibm.com>
References: <200301281948.h0SJmfZd021902@badlands.lexington.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: hubert@ndcms.cac.washington.edu
X-To: Richard A Nelson <cowboy@vnet.ibm.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Jan 2003, Richard A Nelson wrote:

> After starting up 4.53 (on a profile used for 4.51 and below), I'm now
> getting this error when attempting to send mail :
>
> Problem detected: "Botch in radio_buttons(): too many keys".
> Pine Exiting.
>
> Any clue what I can do to get that fixed ?
>
> Thanks,

If you don't mind, would you send a copy of your pine configuration file
to pine@cac.washington.edu? That will make it easier for us to figure out
where we botched it up. Thanks.

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


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, 28 Jan 2003 12:34:44 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKYiTk023792;
	Tue, 28 Jan 2003 12:34:44 -0800
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.12) with ESMTP id h0SKYfnO022103
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 12:34:41 -0800
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.12) with SMTP id h0SKUXDb075390;
	Tue, 28 Jan 2003 12:30:34 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKSgCK076010
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 12:28:42 -0800
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.103])
	by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SKSbHU030804
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Tue, 28 Jan 2003 12:28:38 -0800
Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.56.224.151])
	by e3.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0SKSavr018440;
	Tue, 28 Jan 2003 15:28:37 -0500
Received: from newcowboy.lexington.ibm.com (newcowboy.lexington.ibm.com [9.51.92.23])
	by northrelay03.pok.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0SKSYfu119968;
	Tue, 28 Jan 2003 15:28:35 -0500
Received: from localhost (IDENT:W6df7jWs7Z4Wf3ikCe45dz8g70sv/o6Z@localhost [127.0.0.1])
	(authenticated (0 bits))
	by localhost (8.12.7/8.12.7/Debian-3) with ESMTP id h0SKR8VN026370
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 28 Jan 2003 15:27:11 -0500
Message-Id: <Pine.LNX.4.53.0301281523540.25552@onqynaqf.yrkvatgba.voz.pbz>
Date: Tue, 28 Jan 2003 15:27:08 -0500 (EST)
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: Richard A Nelson <cowboy@vnet.ibm.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: problem going from 4.51 to 4.53
In-Reply-To: <Pine.WNT.4.54.0301281209050.1192@hubertw2k2_ndc.nebula.washington.edu>
References: <200301281948.h0SJmfZd021902@badlands.lexington.ibm.com>
 <Pine.WNT.4.54.0301281209050.1192@hubertw2k2_ndc.nebula.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Hubert <hubert@washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-No-Markup: yes
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Jan 2003, Steve Hubert wrote:

> > Problem detected: "Botch in radio_buttons(): too many keys".
> > Pine Exiting.
> >
> > Any clue what I can do to get that fixed ?
>
> If you don't mind, would you send a copy of your pine configuration file
> to pine@cac.washington.edu? That will make it easier for us to figure out
> where we botched it up. Thanks.

If you'd still like it, yes, but I've isolated the problem to this line:
	sending-filters=/usr/lib/pinepgp/pgp _TMPFILE_ _RECIPIENTS_
taking out that line corrects the problem !

I guess thats what I get for using outdated tools :) What's the
preferred way to go these days ? (I'm already looking at the smime,
but also need to support pgp/gpg signed mail)

-- 
Rick Nelson
I can saw a woman in two, but you won't want to look in the box when I do
'For My Next Trick I'll Need a Volunteer' -- Warren Zevon

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, 28 Jan 2003 13:17:49 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SLHmTk025787;
	Tue, 28 Jan 2003 13:17:48 -0800
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.12) with ESMTP id h0SLHjWb030848
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 13:17:45 -0800
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.12) with SMTP id h0SLDqll031398;
	Tue, 28 Jan 2003 13:13:53 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0SLAYCK016832
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 13:10:34 -0800
Received: from vax.hanford.org (vax.hanford.org [216.218.218.27])
	by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0SLAVZ7004424
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 13:10:31 -0800
Received: (qmail 12406 invoked by uid 1828); 28 Jan 2003 21:10:30 -0000
Message-Id: <Pine.GSO.4.33.0301281309510.8532-100000@vax.hanford.org>
Date: Tue, 28 Jan 2003 13:10:30 -0800 (PST)
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@vax.hanford.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: unsubscribe
In-Reply-To: <Pine.LNX.4.43.0301281058490.13703@hymn01.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Kerryanne C Tulabut <rawhoney@u.washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Uwash-Spam: Gauge=XXII, Probability=22%, Report="IN_REP_TO, NO_MX_FOR_FROM, QUOTED_EMAIL_TEXT, SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXII, Probability=22%, Report="IN_REP_TO, NO_MX_FOR_FROM, QUOTED_EMAIL_TEXT, SPAM_PHRASE_03_05, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Jan 2003, Kerryanne C Tulabut wrote:

>Date: Tue, 28 Jan 2003 10:58:49 -0800 (PST)
>From: Kerryanne C Tulabut <rawhoney@u.washington.edu>
>To: Pine Discussion Forum <pine-info@u.washington.edu>
>Subject: unsubscribe

People, sending unsubscribes to the mailing list does no good but
pollute the readers of the mailing list.

Every single message you receive from the mailing list has info on how
to unsubscribe included in it.

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

top-posting: It's just a bad idea.


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, 28 Jan 2003 22:20:41 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0T6KeTk012320;
	Tue, 28 Jan 2003 22:20:40 -0800
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.12) with ESMTP id h0T6KaWb014375
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 28 Jan 2003 22:20:37 -0800
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.12) with SMTP id h0T6ItDb075354;
	Tue, 28 Jan 2003 22:18:55 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0T6FFCK050714
	for <pine-info@reallists.u.washington.edu>; Tue, 28 Jan 2003 22:15:15 -0800
Received: from t0c.de ([217.172.180.177])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0T6FBfW020802
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Tue, 28 Jan 2003 22:15:13 -0800
Received: from pD95362CD.dip.t-dialin.net (pD95362CD.dip.t-dialin.net [217.83.98.205])
	by t0c.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id h0T6F4624485
	for <pine-info@u.washington.edu>; Wed, 29 Jan 2003 07:15:05 +0100
Message-Id: <Pine.LNX.4.53.0301290711570.23841@station>
Date: Wed, 29 Jan 2003 07:14:57 +0100 (CET)
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 Albuschat <daniel@brot.t0c.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: unsubscribe
In-Reply-To: <Pine.GSO.4.33.0301281309510.8532-100000@vax.hanford.org>
References: <Pine.GSO.4.33.0301281309510.8532-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: daniel@station
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Jan 2003, Matt Ackeret wrote:

> On Tue, 28 Jan 2003, Kerryanne C Tulabut wrote:
> 
> >Date: Tue, 28 Jan 2003 10:58:49 -0800 (PST)
> >From: Kerryanne C Tulabut <rawhoney@u.washington.edu>
> >To: Pine Discussion Forum <pine-info@u.washington.edu>
> >Subject: unsubscribe
> 
> People, sending unsubscribes to the mailing list does no good but
> pollute the readers of the mailing list.
> 
> Every single message you receive from the mailing list has info on how
> to unsubscribe included in it.

AND you have a wonderful "menu" pine generates from
these informations (at least in my version, don't know about
older), so it shouldn't be too hard to "click the right button".

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

cu, Daniel
--
eat(this); // delicious suicide

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, 30 Jan 2003 14:19:39 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0UMJdTk023475;
	Thu, 30 Jan 2003 14:19:39 -0800
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.12) with ESMTP id h0UMJUnO009867
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 30 Jan 2003 14:19:31 -0800
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.12) with SMTP id h0UMHZll030718;
	Thu, 30 Jan 2003 14:17:35 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0UMGPCK021016
	for <pine-info@reallists.u.washington.edu>; Thu, 30 Jan 2003 14:16:25 -0800
Received: from t0c.de ([217.172.180.177])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0UMGJfW029900
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <pine-info@u.washington.edu>; Thu, 30 Jan 2003 14:16:20 -0800
Received: from pD9E67A7D.dip.t-dialin.net (pD9E67A7D.dip.t-dialin.net [217.230.122.125])
	by t0c.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id h0UMGC605568
	for <pine-info@u.washington.edu>; Thu, 30 Jan 2003 23:16:13 +0100
Message-Id: <Pine.LNX.4.50L0.0301302259460.27760-100000@station>
Date: Thu, 30 Jan 2003 23:16:02 +0100 (CET)
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 Albuschat <daniel@brot.t0c.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: PGP as attachment - how?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: daniel@station
X-Uwash-Spam: Gauge=XII, Probability=12%, Report="RCVD_IN_OSIRUSOFT_COM, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_01_02, USER_AGENT_PINE, X_OSIRU_DUL, X_OSIRU_DUL_FH"
X-Uwash-Spam: Gauge=XIIIII, Probability=15%, Report="RCVD_IN_OSIRUSOFT_COM, SPAM_PHRASE_01_02, USER_AGENT_PINE, X_OSIRU_DUL, X_OSIRU_DUL_FH"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Hi,

It could be that I've ask this question already
on this list but I have problems with pine
right now related to the pgp (using gnupg) signing/
encrypting.
I've discovered that I've send mails with pgp
signature only, but without body, sometimes...

I'm using the filters created by pinepgp right
now, but that's not satisfying since it is 
the standard procedure to send the pgp signature
as an attachment and not inlined, what the pinegpg
filter does.

I've looked at the created filter and saw that it
only was a /usr/bin/gpg-sign entry... so it was clear
that i'll have to check gpg command line options for
creating an attached signature. I found the -b
switch, but it turned out that it was the opposite
of what i wanted. :-)

So, my first question is, does anybody know, how I 
can set up either gpg or pine to attach the signature?

But that not all:
I can't read mails with signatures/encrypted messages
as attachment. I only can read pgp-inlined messages,
at best created with pine.

So I need to filter the whole mail, including the
attachment... or so.

Does anybody know a solution for _clean_ gpg signing
and encrypting?

Thanks, Daniel

--
eat(this); // delicious suicide
-- 
-----------------------------------------------------------------
 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; Fri, 31 Jan 2003 03:51:33 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VBpXTk013253;
	Fri, 31 Jan 2003 03:51:33 -0800
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.12) with ESMTP id h0VBpSWb002034
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 31 Jan 2003 03:51:29 -0800
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.12) with SMTP id h0VBlLDb090250;
	Fri, 31 Jan 2003 03:47:21 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VBkJCK045592
	for <pine-info@reallists.u.washington.edu>; Fri, 31 Jan 2003 03:46:19 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VBkHFr027042
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
	for <pine-info@u.washington.edu>; Fri, 31 Jan 2003 03:46:17 -0800
Received: from mail.aurora.edu (mail.aurora.edu [64.107.89.49])
	by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VBkGnN029216
	for <pine-info@cac.washington.edu>; Fri, 31 Jan 2003 03:46:16 -0800
Received: from localhost (slowe@localhost)
	by mail.aurora.edu (8.12.1/8.12.1) with ESMTP id h0VBkFmP178075
	for <pine-info@cac.washington.edu>; Fri, 31 Jan 2003 05:46:15 -0600 (CST)
Message-Id: <Pine.OSF.4.53.0301310544530.177606@mail.aurora.edu>
Date: Fri, 31 Jan 2003 05:46:15 -0600 (CST)
Reply-To: Steve Lowe <slowe@students.aurora.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: Steve Lowe <slowe@students.aurora.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Using Pine4.53 and SSL
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Information List <pine-info@cac.washington.edu>
X-X-Sender: slowe@mail.aurora.edu
X-Uwash-Spam: Gauge=XXXI, Probability=31%, Report="NO_MX_FOR_FROM, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_01_02, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXXIIIIII, Probability=36%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Uwash-Spam: Gauge=XXXIIIIII, Probability=36%, Report="NO_MX_FOR_FROM, SPAM_PHRASE_00_01, USER_AGENT_PINE"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



We just recently upgraded to Pine4.53 with SSL - OS platform is Digital
Unix 5.1, including using the new imapd package also.  For the most part,
the secure version works well -- especially after we built the new
certificate.

However, when I use 4.53 version of PC-Pine, I receive this error (only
partially displayed to save bandwidth):



There was a failure validating the SSL/TLS certificate for the server

                    mail.aurora.edu

The reason for the failure was

                    Self-signed certificate or untrusted authority


Questions:

Should I use openssl to create a new certificate?
If I do, where do I locate the certificate?

I do know that I can bypass the checking of the certificate -- I would
prefer not to do that.

Thanks in advance.

 -- Steve Lowe
    Aurora University
-- 
-----------------------------------------------------------------
 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; Fri, 31 Jan 2003 06:55:55 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VEttTk017801;
	Fri, 31 Jan 2003 06:55:55 -0800
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.12) with ESMTP id h0VEtpWb006100
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 31 Jan 2003 06:55:52 -0800
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.12) with SMTP id h0VErLll028452;
	Fri, 31 Jan 2003 06:53:21 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VEqbCK060170
	for <pine-info@reallists.u.washington.edu>; Fri, 31 Jan 2003 06:52:37 -0800
Received: from smtp.gospelcom.net (joppa.gospelcom.net [204.253.132.6])
	by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0VEqaFq017583
	for <pine-info@u.washington.edu>; Fri, 31 Jan 2003 06:52:36 -0800
Received: (qmail 10487 invoked from network); 31 Jan 2003 14:52:35 -0000
Received: from gci.mkg.gospelcom.net (HELO jair.gf.gospelcom.net) (204.253.133.99)
  by smtp.gospelcom.net with SMTP; 31 Jan 2003 14:52:35 -0000
Message-Id: <Pine.LNX.4.53.0301310951470.8545@localhost.localdomain>
Date: Fri, 31 Jan 2003 09:52:51 -0500 (EST)
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: PGP as attachment - how?
In-Reply-To: <Pine.LNX.4.50L0.0301302259460.27760-100000@station>
References: <Pine.LNX.4.50L0.0301302259460.27760-100000@station>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Daniel Albuschat <daniel@brot.t0c.de>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: joel@localhost.localdomain
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

<snip>
> But that not all:
> I can't read mails with signatures/encrypted messages
> as attachment. I only can read pgp-inlined messages,
> at best created with pine.
>
> So I need to filter the whole mail, including the
> attachment... or so.

Try:

  http://www.washington.edu/pine/pine-info/2001.10/msg00028.html

for the second part of your question.  As to the first, I can't be of
much help there...

-- 
[ 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; Fri, 31 Jan 2003 13:58:48 -0800 (PST)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VLwlTk031648;
	Fri, 31 Jan 2003 13:58:47 -0800
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.12) with ESMTP id h0VLwhWb019637
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 31 Jan 2003 13:58:44 -0800
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.12) with SMTP id h0VLu2Db090898;
	Fri, 31 Jan 2003 13:56:02 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VLtDCK066696
	for <pine-info@reallists.u.washington.edu>; Fri, 31 Jan 2003 13:55:13 -0800
Received: from mindsec.com (noella.mindsec.com [209.172.192.12])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0VLtBfV020071
	for <pine-info@u.washington.edu>; Fri, 31 Jan 2003 13:55:11 -0800
Received: from noella (IDENT:100@noella [209.172.192.12])
	by mindsec.com (8.8.6/8.8.6) with ESMTP id h0VLt8LW005860;
	Fri, 31 Jan 2003 15:55:08 -0600 (CST)
Message-Id: <0301311553250.0@somehost.domainz.com>
Date: Fri, 31 Jan 2003 15:55:08 -0600 (CST)
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: Erik Parker <eparker@mindsec.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PGP as attachment - how?
In-Reply-To: <Pine.LNX.4.53.0301310951470.8545@localhost.localdomain>
References: <Pine.LNX.4.50L0.0301302259460.27760-100000@station>
 <Pine.LNX.4.53.0301310951470.8545@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Joel Boonstra <jboonstra@gospelcom.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: eparker@mindsec.com
X-GPG-Key: http://www.mindsec.com/staff/eparker/gpg.txt
X-Use-Encryption: Encrypt your messages to me with PGP or GPG!
X-No-Archive: Yes
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



That is the best way I've found.. I use:

:0 fw
* ^Content-Type: multipart/encrypted
| formail -i "Content-Type: text/plain; charset=US-ASCII"
##

:0 fw
* ^Content-Type: Application/PGP
| formail -i "Content-Type: text/plain; charset=US-ASCII"
##


## to handle multipart crapola from stuff
:0 fw
* ^Content-Type: application/pgp-signature
| formail -i "Content-Type: text/plain; charset=US-ASCII"
##


As for sending.. I use PinePG.. and it works fine for sending and recieving. I
send signature and messages in body. I'm not sure where you found that it is
standard to send them as an attachment.. but the only people I Email with GPG
that use attachments, are Mutt users. All the winlusers, and unix people i
send back and forth with, mostly in the security industry, use inline.

>
> Try:
>
>   http://www.washington.edu/pine/pine-info/2001.10/msg00028.html
>
> for the second part of your question.  As to the first, I can't be of
> much help there...
>
> --
> [ joel boonstra | jboonstra@gospelcom.net ]
>
