From [email protected] Sat Nov  1 10:09:32 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 1 Nov 2003 10:09:32 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1I9VlU032233;
       Sat, 1 Nov 2003 10:09:31 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1I9QOA023243
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sat, 1 Nov 2003 10:09:27 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA1I9HlZ012872;
       Sat, 1 Nov 2003 10:09:17 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1I7tnM019734
       for <[email protected]>; Sat, 1 Nov 2003 10:07:56 -0800
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1I7sQP003405
       for <[email protected]>; Sat, 1 Nov 2003 10:07:54 -0800
Received: from server1.messagingengine.com (server1.internal [10.202.2.132])
       by mail.messagingengine.com (Postfix) with ESMTP id 41DC239B398
       for <[email protected]>; Sat,  1 Nov 2003 13:07:51 -0500 (EST)
Received: by server1.messagingengine.com (Postfix, from userid 99)
       id 962E93FC80; Sat,  1 Nov 2003 13:07:50 -0500 (EST)
Message-Id: <[email protected]>
Date: Sat, 01 Nov 2003 10:07:50 -0800
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Cloids" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: folders showing # of unread messages?
In-Reply-To: <[email protected]>
References: <[email protected]>
  <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-To: "Pine Discussion Forum" <[email protected]>
X-Sasl-Enc: KgDfkK2oJl84Nl6JrlY7sQ 1067710070
X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='FROM_ENDS_IN_NUMS, IN_REP_TO, MAILTO_TO_SPAM_ADDR, REFERENCES, SIGNATURE_LONG_SPARSE, __CD, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Can this be displayed? I have about 4 folders, it would be more
convienient if Pine displayed how many messages are unread in each folder
in the Folders screen.
--
 Cloids
 [email protected]

--
http://www.fastmail.fm - Or how I learned to stop worrying and
                         love email again
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sat Nov  1 11:21:34 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 1 Nov 2003 11:21:34 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1JLYlU001257;
       Sat, 1 Nov 2003 11:21:34 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1JLVqm016430
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sat, 1 Nov 2003 11:21:32 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA1JLMlZ012750;
       Sat, 1 Nov 2003 11:21:22 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1JKZnM017260
       for <[email protected]>; Sat, 1 Nov 2003 11:20:35 -0800
Received: from eth0.b.smtp.sonic.net (eth0.b.smtp.sonic.net [64.142.19.4])
       by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1JKYK5029833
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Sat, 1 Nov 2003 11:20:34 -0800
Received: from localhost.localdomain (03-172.140.popsite.net [66.248.50.172])
       (authenticated bits=0)
       by eth0.b.smtp.sonic.net (8.12.10/8.12.7) with ESMTP id hA1JKVue006955
       for <[email protected]>; Sat, 1 Nov 2003 11:20:32 -0800
Message-Id: <[email protected]>
Date: Sat, 1 Nov 2003 02:21:50 -0700
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bob Holtzman <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Sending problem
Content-Type: text/plain;
 charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-To: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=III, Probability=3%, Report='DATE_IN_PAST_06_12, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

----- Message Text -----
On Thu, 30 Oct 2003, Gopi Sundaram wrote:
=20
> On Thu, 30 Oct 2003, Bob Holtzman wrote:
>
> > [Mail not sent: <[email protected]>... Relaying denied. Proper=20
authenticatio]
>
> That error message is truncated. Check the message journal to see if yo=
u
> can get the entire error message, or check your pine-debug file.

The message doesn't show up in /var/log/messages and there is no pine-deb=
ug=20
file.

>
> My guess is, your SMTP server is in a different domain than your From:
> header. So it will deny relaying unless you authenticate. Try
> authenticated SMTP.

The SMTP server in my .pinerc file is mail.sonic.net. As I said, htere ha=
ve=20
been no changes to the configuration file in a long time. Also,=20
mail.sonic.net works in Kmail (which I'm using now) and Eudora in W95.

>
> > Bob Holtzman
> > "If you think you're getting free lunch
> >    ............check the price of the beer!"
>
> Seeing it a second time didn't make it funnier. Check your signature
> inclusion mechanism.

Sorry about the sig. It was a copy and paste screw up. Also it isn't mean=
t to=20
be funny. It's the family moto.



From [email protected] Sat Nov  1 12:37:49 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 1 Nov 2003 12:37:49 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1KbjlU003054;
       Sat, 1 Nov 2003 12:37:48 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1KbgOA026455
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sat, 1 Nov 2003 12:37:43 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA1KWlbc004938;
       Sat, 1 Nov 2003 12:32:47 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1KWDnM018932
       for <[email protected]>; Sat, 1 Nov 2003 12:32:13 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1KW9FY009190
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Sat, 1 Nov 2003 12:32:12 -0800
Received: from localhost (localhost [127.0.0.1])
       by aslan.narnia.pp.se (8.12.8p2/8.12.8) with ESMTP id hA1KW4lk075191;
       Sat, 1 Nov 2003 21:32:05 +0100 (CET)
       (envelope-from [email protected])
Message-Id: <[email protected]>
Date: Sat, 1 Nov 2003 21:32:04 +0100 (CET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mats Dufberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Sending problem
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Bob Holtzman <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Nov 1, 2003, 02:21 (-0700) Bob Holtzman <[email protected]> wrote:

> > > [Mail not sent: <[email protected]>... Relaying denied. Proper
> authenticatio]
> >
> > That error message is truncated. Check the message journal to see if you
> > can get the entire error message, or check your pine-debug file.
>
> The message doesn't show up in /var/log/messages and there is no pine-debug
> file.

You can set increased debug level when starting pine.

I would not expect anything in the message log since your are sending
direct to the SMTP server, but if you have access to the server, look in
the mail log, usually /var/log/maillog.

> > My guess is, your SMTP server is in a different domain than your From:
> > header. So it will deny relaying unless you authenticate. Try
> > authenticated SMTP.
>
> The SMTP server in my .pinerc file is mail.sonic.net. As I said, htere have
> been no changes to the configuration file in a long time. Also,
> mail.sonic.net works in Kmail (which I'm using now) and Eudora in W95.

OK, but something is different. Maybe the envelope sender? Are you sending
from the same machine with the same IP address? Are you sure that Kmail
and Eudora do not use SMTP AUTH?



Mats

-----------------------------------------------------------------
Mats Dufberg                                      [email protected]
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588

From [email protected] Sat Nov  1 13:01:36 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 1 Nov 2003 13:01:36 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1L1alU003713;
       Sat, 1 Nov 2003 13:01:36 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1L1Xqm018776
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sat, 1 Nov 2003 13:01:34 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA1L1OlZ012858;
       Sat, 1 Nov 2003 13:01:24 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1L0vnM021862
       for <[email protected]>; Sat, 1 Nov 2003 13:00:57 -0800
Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA1L0nQP023272
       for <[email protected]>; Sat, 1 Nov 2003 13:00:49 -0800
Received: from gort.cjb.net ([68.59.9.227])
         by comcast.net (sccrmhc11) with ESMTP
         id <2003110121004901100eohn7e>; Sat, 1 Nov 2003 21:00:49 +0000
Received: from localhost (localhost [127.0.0.1])
       by gort.cjb.net (Postfix) with ESMTP id 7A22DA796
       for <[email protected]>; Sat,  1 Nov 2003 16:01:27 -0500 (EST)
Message-Id: <[email protected]>
Date: Sat, 1 Nov 2003 16:01:27 -0500 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Sending problem
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Nov 1, 2003 at 02:21, Bob Holtzman wrote:

>The message doesn't show up in /var/log/messages and there is no pine-debug
>file.

Try .pine-debug*

>Sorry about the sig. It was a copy and paste screw up. Also it isn't meant to
>be funny. It's the family moto.

Did you know that you can define a signature file? That way you won't
have to copy-paste.

--
Satya. <URL:http://www.thesatya.com/>
Keyboard not found - Press F1 to continue

From [email protected] Sat Nov  1 21:40:16 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 1 Nov 2003 21:40:16 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA25eGlU013578;
       Sat, 1 Nov 2003 21:40:16 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA25cdD2028836
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sat, 1 Nov 2003 21:40:12 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA21MQnH008472;
       Sat, 1 Nov 2003 17:22:26 -0800
Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA21LcnM021442
       for <[email protected]>; Sat, 1 Nov 2003 17:21:38 -0800
Received: from eth0.a.smtp.sonic.net (eth0.a.smtp.sonic.net [64.142.16.244])
       by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA21Lbbn032511
       for <[email protected]>; Sat, 1 Nov 2003 17:21:37 -0800
Received: from 03-199.140.popsite.net (03-199.140.popsite.net [66.248.50.199])
       by eth0.a.smtp.sonic.net (8.12.10/8.12.7) with ESMTP id hA21LVts031125
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Sat, 1 Nov 2003 17:21:35 -0800
Message-Id: <[email protected]>
Date: Sat, 1 Nov 2003 18:45:11 -0700 (MST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bob Holtzman <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Sending problem
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sat, 1 Nov 2003, Satya wrote:

> On Nov 1, 2003 at 02:21, Bob Holtzman wrote:
>
> >Sorry about the sig. It was a copy and paste screw up. Also it isn't meant to
> >be funny. It's the family moto.
>
> Did you know that you can define a signature file? That way you won't
> have to copy-paste.
>
I have several. The problem was that I generated the message in Pine,
then found I couldn't send it. I copied it  to my Windows partition and
pasted it into Eudora. I inadvertently pasted the sig.

--
Bob Holtzman
"If you think you're getting free lunch,
......check the price of the beer!"


From [email protected] Sun Nov  2 06:35:38 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 2 Nov 2003 06:35:38 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2EZclU000806;
       Sun, 2 Nov 2003 06:35:38 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2EZYCk013088
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sun, 2 Nov 2003 06:35:34 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA2EZOmu012138;
       Sun, 2 Nov 2003 06:35:24 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2EYLnM018668
       for <[email protected]>; Sun, 2 Nov 2003 06:34:21 -0800
Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2EYK5I014474
       for <[email protected]>; Sun, 2 Nov 2003 06:34:20 -0800
Received: from eltanin (eltanin.cse.sc.edu [129.252.138.20])
       by moultrie.cse.sc.edu (Postfix) with ESMTP
       id 076ED1E4CE; Sun,  2 Nov 2003 09:34:18 -0500 (EST)
Message-Id: <Pine.GSO.4.58.0311020833240.2966@eltanin>
Date: Sun, 2 Nov 2003 08:34:18 -0600 (CST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Gopi Sundaram <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Sending problem
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Bob Holtzman <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: gopalan@eltanin
X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sat, 1 Nov 2003, Bob Holtzman wrote:

> The message doesn't show up in /var/log/messages and there is no
> pine-debug file.

The message journal is available from (M)ain (J)ournal

It's a .pine-debug[0-9] file.

--
Gopi Sundaram
http://www.zrox.net/Mail/Pine/

From [email protected] Sun Nov  2 14:37:21 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 2 Nov 2003 14:37:21 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2MbGlU012163;
       Sun, 2 Nov 2003 14:37:16 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2MbEhW031418
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sun, 2 Nov 2003 14:37:14 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA2Mb4bc013048;
       Sun, 2 Nov 2003 14:37:04 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2Ma5nM016746
       for <[email protected]>; Sun, 2 Nov 2003 14:36:05 -0800
Received: from pebbles.thebeachfamily.org (adsl-68-78-228-33.dsl.mdsnwi.ameritech.net [68.78.228.33])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA2MZwpX027432
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Sun, 2 Nov 2003 14:36:04 -0800
Received: (qmail 10967 invoked from network); 2 Nov 2003 22:36:05 -0000
Received: from unknown (HELO erwin) (192.168.13.69)
 by adsl-68-78-228-33.dsl.mdsnwi.ameritech.net with DES-CBC3-SHA encrypted SMTP; 2 Nov 2003 22:36:05 -0000
Message-Id: <[email protected]>
Date: Sun, 2 Nov 2003 17:35:57 -0500 (EST)
Reply-To: Steve Beach <[email protected]>
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Beach <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Filter for multipart/signed pgp messages
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='LINES_OF_YELLING, PGP_SIGNATURE, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear All;

I'm a dedicated pine user (love the interface, love the text based
system), but I'm having trouble with pgp signed messages.  pgp4pine works
fine for monolithic signed messages, but it doesn't work at all for
multipart/signed messages.  Looking over the web, it appears this is a
commonly known problem with pine itself.

Well, I've got a possible solution.  The basic idea is to run the mail
through a filter that reads the various bits of the multipart mail, and
then re-writes the mail into a monolithic signed mail.  I consider this to
be _early_ beta at this stage, but I'm releasing it to get any community
feedback I can.

I'm particularly interested in whether the community would prefer a filter
that rewrites the message so pgp4pine (or equivalent) can handle it, or
whether the filter should call pgp/gnupg directly and append the results
of that onto the mail body of the mail.

I've tried the "formail -i" mentioned in the archives, but that doesn't
seem to work for me.

If you are interested, you can get the filter at
http://www.thebeachfamily.org/software/pine_mutt_filter and
http://www.thebeachfamily.org/software/pine_mutt_filter.asc (gpg
signature).

Currently, it uses the Optik option parsing package for
python you can find at http://freshmeat.net.  If enough people hate that,
I'll get rid of it.

Thanks,

Steve Beach


[email protected],
http://www.thebeachfamily.org

- ------------------------------------------------------------
|  Can't keep my mind from the circling sky                |
|  Tongue tied and twisted, just an earth bound misfit, I  |
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQE/pYbUhfSAGXZ10F4RAg6+AJwLNR/KaSv3gSZM69O5CXCV7jxeRwCgw6av
FitQXUKbkgl1DDERwTtUMFI=
=WlYQ
-----END PGP SIGNATURE-----

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

From [email protected] Tue Nov  4 13:08:52 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 4 Nov 2003 13:08:52 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4L8plU014675;
       Tue, 4 Nov 2003 13:08:51 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4L8nhW013501
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 4 Nov 2003 13:08:49 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA4L8bmu014806;
       Tue, 4 Nov 2003 13:08:38 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4L5qnM016266
       for <[email protected]>; Tue, 4 Nov 2003 13:05:52 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4L5pQQ007905
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Tue, 4 Nov 2003 13:05:51 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4L5laZ003829;
       Tue, 4 Nov 2003 13:05:48 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4L5lSS011707
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Tue, 4 Nov 2003 13:05:47 -0800
Message-Id: <[email protected]>
Date: Tue, 4 Nov 2003 13:03:47 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: pcpine 4.58 crashes
In-Reply-To: <[email protected]>
References: <[email protected]> <Pine.OS2.4.55.0310141637450.85@barry>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Cornelius C. Noack" <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 22 Oct 2003, Cornelius C. Noack wrote:

> After updating from 4.56 to 4.58 I find that pcpine crashes
> whenever I try to open a message with an attachment of reasonable
> size, with the error message:
>          " incomplete SecBuffer exceeds maximum buffer size"

This almost certainly related to the bug in Microsoft's SSL code, which
PC-Pine makes use of.  We've added the feature called
"quell-ssl-largeblocks", where setting that tries to work around most of
the places where the bug is likely to happen, and this feature was
enhanced between 4.56 and 4.58 (though it surpises me that you get a crash
in 4.58 that you wouldn't get in 4.56, is that really the case?).

Of course, ideally Microsoft would issue a patch to fix this bug.  It's
been over two years and still no fix, but there are rumors that it might
be deemed worthy enough to grace the next service pack release.

Jeff

From [email protected] Tue Nov  4 13:17:17 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 4 Nov 2003 13:17:17 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LHGlU015023;
       Tue, 4 Nov 2003 13:17:16 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LHECk006774
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 4 Nov 2003 13:17:14 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA4LH2lZ015322;
       Tue, 4 Nov 2003 13:17:02 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LFFnM014030
       for <[email protected]>; Tue, 4 Nov 2003 13:15:16 -0800
Received: from mail3.panix.com (mail3.panix.com [166.84.1.74])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LFE5I020386
       for <[email protected]>; Tue, 4 Nov 2003 13:15:14 -0800
Received: from mailspool2.panix.com (mailspool2.panix.com [166.84.1.79])
       by mail3.panix.com (Postfix) with ESMTP id B7EDA982ED
       for <[email protected]>; Tue,  4 Nov 2003 16:15:13 -0500 (EST)
Received: from lakers.ixiacom.com (64-60-75-66.cust.telepacific.net [64.60.75.66])
       by mailspool2.panix.com (Postfix) with ESMTP id F117B2D545
       for <[email protected]>; Tue,  4 Nov 2003 16:15:12 -0500 (EST)
Message-Id: <[email protected]>
Date: Tue, 4 Nov 2003 13:15:21 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Kenneth Crudup <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: pcpine 4.58 crashes
In-Reply-To: <[email protected]>
References: <[email protected]> <Pine.OS2.4.55.0310141637450.85@barry>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Tue, 4 Nov 2003, Jeff Franklin wrote:

> This almost certainly related to the bug in Microsoft's SSL code, which
> PC-Pine makes use of.

> Of course, ideally Microsoft would issue a patch to fix this bug.

Let me guess: they've provided a workaround for it in "MS LookOut!"?

       -Kenny

--
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
H: 3801 E. Pacific Coast Hw #9, Long Beach, CA 90804-2014 (888) 454-8181
W: 26601 Agoura Road, Calabasas CA 91302-1959             (818) 444-3685

From [email protected] Tue Nov  4 13:37:27 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 4 Nov 2003 13:37:27 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LbQlU015852;
       Tue, 4 Nov 2003 13:37:26 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LbOCk007552
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 4 Nov 2003 13:37:24 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA4LbFmu013476;
       Tue, 4 Nov 2003 13:37:16 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LZ8nM017526
       for <[email protected]>; Tue, 4 Nov 2003 13:35:08 -0800
Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LZ7pX016466
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Tue, 4 Nov 2003 13:35:07 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
       by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LZ40Y029324;
       Tue, 4 Nov 2003 13:35:04 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA4LZ4x0020546
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Tue, 4 Nov 2003 13:35:04 -0800
Message-Id: <[email protected]>
Date: Tue, 4 Nov 2003 13:33:04 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: pcpine 4.58 crashes
In-Reply-To: <[email protected]>
References: <[email protected]> <Pine.OS2.4.55.0310141637450.85@barry>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Kenneth Crudup <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 4 Nov 2003, Kenneth Crudup wrote:

> On Tue, 4 Nov 2003, Jeff Franklin wrote:
>
> > This almost certainly related to the bug in Microsoft's SSL code, which
> > PC-Pine makes use of.
>
> > Of course, ideally Microsoft would issue a patch to fix this bug.
>
> Let me guess: they've provided a workaround for it in "MS LookOut!"?

Supposedly the problem still exists in MS Exchange.  I don't know why it's
not as common a problem for clients talking to an exchange server.

Jeff

From [email protected] Wed Nov  5 11:48:25 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 5 Nov 2003 11:48:25 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5JmPlU001328;
       Wed, 5 Nov 2003 11:48:25 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5JmNCk015295
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 5 Nov 2003 11:48:23 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA5JmE1r014376;
       Wed, 5 Nov 2003 11:48:14 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5JlPhW021692
       for <[email protected]>; Wed, 5 Nov 2003 11:47:25 -0800
Received: from falcon.dickinson.edu ([64.9.63.173])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5JlOrR011044
       for <[email protected]>; Wed, 5 Nov 2003 11:47:24 -0800
Received: from falcon.dickinson.edu by falcon.dickinson.edu (8.8.8/1.1.22.3/25Feb99-0911AM)
       id OAA0000005353; Wed, 5 Nov 2003 14:47:16 -0500 (EST)
Message-Id: <[email protected]>
Date: Wed, 5 Nov 2003 14:47:15 -0500 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Don Newcomer <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: HP-UX 11i
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info mailing list <[email protected]>
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm trying to compile Pine 4.58 on my new HP zx2000 workstation running
HP-UX 11i.  I'm brand new to HP-UX (that's the purpose behind getting the
workstation ) so I'm having a lot of trouble after spending years in a
Tru64 environment.  This is complicated by the fact that getting a
workstation with HP-UX pre-loaded gives you a stripped down version of the
C compiler.  At any rate, when I try a 'build hpx', it runs awhile and then
dies on the following error:


ld: Can't find library or mismatched ABI for -lnet
Fatal error.
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.
+---------------------------------------------+
| Problems building c-client                  |
|                                             |
| Please check the output above for a         |
| possible explanation for this failure       |
+---------------------------------------------+

According to the 'ld' man pages, it's looking for libnet in /usr/lib/hpux32
and /usr/llib/hpux64.  I found 'libnet.a' in /usr/conf/lib.  I even tried
setting the LPATH environment variable and included all three paths in the
definition to no avail.  The port documentation only lists HP-UX version
10.  Has anyone managed to compile Pine under HP-UX 11i and, if so, what's
the secret?  Thanks in advance.

================================================================================
Don Newcomer                                            Dickinson College
Associate Director, System and Network Services         P.O. Box 1773
[email protected]                                  Carlisle, PA  17013
                                                       Phone: (717) 245-1256
                                                         FAX: (717) 245-1690


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

From [email protected] Wed Nov  5 14:48:56 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 5 Nov 2003 14:48:56 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5MmtNL009774;
       Wed, 5 Nov 2003 14:48:55 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5MmrhW028775
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 5 Nov 2003 14:48:53 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA5MmhAk015188;
       Wed, 5 Nov 2003 14:48:43 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5MlehW030506
       for <[email protected]>; Wed, 5 Nov 2003 14:47:40 -0800
Received: from mta07-svc.ntlworld.com (mta07-svc.ntlworld.com [62.253.162.47])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA5MlcQP020460
       for <[email protected]>; Wed, 5 Nov 2003 14:47:39 -0800
Received: from MRLANDY ([81.105.237.144]) by mta07-svc.ntlworld.com
         (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP
         id <20031105224737.YPTF21570.mta07-svc.ntlworld.com@MRLANDY>
         for <[email protected]>; Wed, 5 Nov 2003 22:47:37 +0000
Message-Id: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
Date: Wed, 5 Nov 2003 22:50:08 +0000 (GMT Standard Time)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Barry Landy <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: PINE458 problem
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=XIII, Probability=13%, Report='FROM_ENDS_IN_NUMS, MAILTO_TO_SPAM_ADDR, SIGNATURE_LONG_SPARSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Using the Win32 version of Pine458 I find that it has stopped being able
to open the appropriate application for attachments. For example faced
with an octet-stream describing a .doc it says

"attachment OCTET-STREAM unrecognised. Try open by file extension
(.doc)"

When responding Y it works fine, although inconveniently Y is NOT the
default.

Reverting to Pine455 the document gets opened in the right application
(WORD in this case) without any fuss.

--
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-332058
Cambridge CB4 3PB                  Efax:        +44-870-458-0205
Email:[email protected]

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

From [email protected] Wed Nov  5 16:11:20 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 5 Nov 2003 16:11:20 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60BINL013142;
       Wed, 5 Nov 2003 16:11:18 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60BGhW031545
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 5 Nov 2003 16:11:16 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA60B61r012256;
       Wed, 5 Nov 2003 16:11:07 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60ARhW007866
       for <[email protected]>; Wed, 5 Nov 2003 16:10:27 -0800
Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166])
       by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60AQK5032439
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Wed, 5 Nov 2003 16:10:26 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60ANC2009537;
       Wed, 5 Nov 2003 16:10:23 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60AISS012079
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Wed, 5 Nov 2003 16:10:23 -0800
Message-Id: <[email protected]>
Date: Wed, 5 Nov 2003 16:08:15 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Barry Landy <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 5 Nov 2003, Barry Landy wrote:

> "attachment OCTET-STREAM unrecognised. Try open by file extension
> (.doc)"
>
> When responding Y it works fine, although inconveniently Y is NOT the
> default.

This was changed to be a little more paranoid when opening attachments.
In this particular case, since typically only the fact that
application/octet-stream is displayed without some digging, we felt it
safest to warn before reverting to the file's extension.  If the
originating client had labeled the attachment as what it actually was (as
application/msword), pine wouldn't have whined (not entirely true, it
still would have asked to view an external attachment unless the
quell-attachment-extra-prompt feature was set).

It sounds like the quell-attach... feature should also quell this extra
bit about opening by file extension.  We'll go ahead and change that
unless there is a large outcry.

Jeff

From [email protected] Wed Nov  5 16:58:21 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 5 Nov 2003 16:58:21 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60wKNL014950;
       Wed, 5 Nov 2003 16:58:20 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60wICk026978
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 5 Nov 2003 16:58:19 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA60wA1r012576;
       Wed, 5 Nov 2003 16:58:10 -0800
Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60vchW029640
       for <[email protected]>; Wed, 5 Nov 2003 16:57:39 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
       by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA60va0T030346
       for <[email protected]>; Wed, 5 Nov 2003 16:57:37 -0800
Received: from localhost (localhost [127.0.0.1])
       by aslan.narnia.pp.se (8.12.8p2/8.12.8) with ESMTP id hA60vUlk095412;
       Thu, 6 Nov 2003 01:57:30 +0100 (CET)
       (envelope-from [email protected])
Message-Id: <[email protected]>
Date: Thu, 6 Nov 2003 01:57:30 +0100 (CET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mats Dufberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Jeff Franklin <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Nov 5, 2003, 16:08 (-0800) Jeff Franklin <[email protected]> wrote:

> This was changed to be a little more paranoid when opening attachments.
> In this particular case, since typically only the fact that
> application/octet-stream is displayed without some digging, we felt it
> safest to warn before reverting to the file's extension.  If the
> originating client had labeled the attachment as what it actually was (as
> application/msword), pine wouldn't have whined (not entirely true, it
> still would have asked to view an external attachment unless the
> quell-attachment-extra-prompt feature was set).
>
> It sounds like the quell-attach... feature should also quell this extra
> bit about opening by file extension.  We'll go ahead and change that
> unless there is a large outcry.

>From a security point of view, there is now difference. If you have
configured your system to try to open every ".doc" file with MS Word is no
more unsafe than having done so for application/msword files.



Mats

-----------------------------------------------------------------
Mats Dufberg                                      [email protected]
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588

From [email protected] Wed Nov  5 17:22:06 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 5 Nov 2003 17:22:06 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA61M5NL015850;
       Wed, 5 Nov 2003 17:22:05 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA61M3Ck027703
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 5 Nov 2003 17:22:04 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA61LqFe016564;
       Wed, 5 Nov 2003 17:21:52 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA61L6hW027502
       for <[email protected]>; Wed, 5 Nov 2003 17:21:06 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA61L5FY016847
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Wed, 5 Nov 2003 17:21:05 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA61L1aZ020863;
       Wed, 5 Nov 2003 17:21:01 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA61L1SS018110
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Wed, 5 Nov 2003 17:21:01 -0800
Message-Id: <[email protected]>
Date: Wed, 5 Nov 2003 17:18:58 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mats Dufberg <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 6 Nov 2003, Mats Dufberg wrote:

> From a security point of view, there is now difference. If you have
> configured your system to try to open every ".doc" file with MS Word is no
> more unsafe than having done so for application/msword files.

You're right that there is no difference in how it is opened.  The
question is what is a sufficient level of warning that a person should get
that they are about to do something potentially dangerous.  The (recent)
default behavior is to warn any time someone is about to do something
outside of pine, which is about as much as we can do.  More sophisticated
users should have a way to turn off the nagging.

Jeff

From [email protected] Wed Nov  5 23:51:56 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 5 Nov 2003 23:51:56 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA67ptNL027320;
       Wed, 5 Nov 2003 23:51:55 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA67prhW011288
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 5 Nov 2003 23:51:54 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA67piop004900;
       Wed, 5 Nov 2003 23:51:44 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA67ochW023950
       for <[email protected]>; Wed, 5 Nov 2003 23:50:38 -0800
Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA67oa5I000880
       for <[email protected]>; Wed, 5 Nov 2003 23:50:37 -0800
Received: from cam.ac.uk ([81.105.237.144]) by mta05-svc.ntlworld.com
         (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP
         id <[email protected]>;
         Thu, 6 Nov 2003 07:50:35 +0000
Message-Id: <Pine.OS2.4.58.0311060752160.73@barry>
Date: Thu, 6 Nov 2003 07:53:07 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Barry Landy <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jeff Franklin <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='EMAIL_ATTRIBUTION, FROM_ENDS_IN_NUMS, IN_REP_TO, MAILTO_TO_SPAM_ADDR, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

For what it is worth the sender is an AOL customer, so I guess the
failure to specify application/msword is widespread.

On Wed, 5 Nov 2003, Jeff Franklin wrote:

:>On Wed, 5 Nov 2003, Barry Landy wrote:
:>
:>> "attachment OCTET-STREAM unrecognised. Try open by file extension
:>> (.doc)"
:>>
:>> When responding Y it works fine, although inconveniently Y is NOT the
:>> default.
:>
:>This was changed to be a little more paranoid when opening attachments.
:>In this particular case, since typically only the fact that
:>application/octet-stream is displayed without some digging, we felt it
:>safest to warn before reverting to the file's extension.  If the
:>originating client had labeled the attachment as what it actually was (as
:>application/msword), pine wouldn't have whined (not entirely true, it
:>still would have asked to view an external attachment unless the
:>quell-attachment-extra-prompt feature was set).
:>
:>It sounds like the quell-attach... feature should also quell this extra
:>bit about opening by file extension.  We'll go ahead and change that
:>unless there is a large outcry.
:>
:>Jeff
:>

--
Barry Landy                        Home:        +44-1223-570417
192, Gilbert Road                  College:     +44-1223-332058
Cambridge CB4 3PB                  Efax:        +44-870-458-0205
Email:[email protected]


From [email protected] Thu Nov  6 09:08:34 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 09:08:34 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6H8XNL013461;
       Thu, 6 Nov 2003 09:08:33 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6H8VCk019726
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 09:08:31 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6H8D1r014514;
       Thu, 6 Nov 2003 09:08:13 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6H7MhW028708
       for <[email protected]>; Thu, 6 Nov 2003 09:07:23 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6H7I5J009413
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Thu, 6 Nov 2003 09:07:20 -0800
Received: from localhost (localhost [127.0.0.1])
       by aslan.narnia.pp.se (8.12.8p2/8.12.8) with ESMTP id hA6H7Dlk097945;
       Thu, 6 Nov 2003 18:07:13 +0100 (CET)
       (envelope-from [email protected])
Message-Id: <[email protected]>
Date: Thu, 6 Nov 2003 18:07:13 +0100 (CET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mats Dufberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Jeff Franklin <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Nov 5, 2003, 17:18 (-0800) Jeff Franklin <[email protected]> wrote:

> > From a security point of view, there is now difference. If you have
> > configured your system to try to open every ".doc" file with MS Word is no
> > more unsafe than having done so for application/msword files.
>
> You're right that there is no difference in how it is opened.  The
> question is what is a sufficient level of warning that a person should get
> that they are about to do something potentially dangerous.  The (recent)
> default behavior is to warn any time someone is about to do something
> outside of pine, which is about as much as we can do.  More sophisticated
> users should have a way to turn off the nagging.

It should be the same warning for opening something based on content-type
or "extension". Yes, you should be able to turn it off.

*

A feature request in this area is to be able to dynamically select a
program for an attachment.


Mats

-----------------------------------------------------------------
Mats Dufberg                                      [email protected]
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588

From [email protected] Thu Nov  6 09:10:13 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 09:10:13 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6HACNL013598;
       Thu, 6 Nov 2003 09:10:12 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6HAAhW025193
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 09:10:10 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6H9xFe014840;
       Thu, 6 Nov 2003 09:09:59 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6H9XhW023974
       for <[email protected]>; Thu, 6 Nov 2003 09:09:33 -0800
Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6H9WpW017562
       for <[email protected]>; Thu, 6 Nov 2003 09:09:32 -0800
Received: from eltanin (eltanin.cse.sc.edu [129.252.138.20])
       by moultrie.cse.sc.edu (Postfix) with ESMTP
       id A176F1E4CE; Thu,  6 Nov 2003 12:09:31 -0500 (EST)
Message-Id: <Pine.GSO.4.58.0311061101560.923@eltanin>
Date: Thu, 6 Nov 2003 11:09:31 -0600 (CST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Gopi Sundaram <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jeff Franklin <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: gopalan@eltanin
X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 5 Nov 2003, Jeff Franklin wrote:

> We'll go ahead and change that unless there is a large outcry.

Here's my small outcry. I'd rather an additional config option be used
to quell this behavior. If Pine is making a decision for me, I'd like to
know about it. When I choose to open an attachment and it is of a known
mime-type, then Pine is making no decision on my behalf. But when it
infers something based on the filename, it is.

With the extra config option, I have the ability to launch attachments
of known type without question, and be prompted for attachments of
unknown type.

--
Gopi Sundaram
http://www.zrox.net/Mail/Pine/

From [email protected] Thu Nov  6 11:20:10 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 11:20:10 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JK9NL021031;
       Thu, 6 Nov 2003 11:20:09 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JK6hW030370
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 11:20:07 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6JJsop012130;
       Thu, 6 Nov 2003 11:19:54 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JJBhW018148
       for <[email protected]>; Thu, 6 Nov 2003 11:19:11 -0800
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JJAFY016053
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Thu, 6 Nov 2003 11:19:10 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JJ8hu015854;
       Thu, 6 Nov 2003 11:19:08 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JJ3SS028000
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Thu, 6 Nov 2003 11:19:07 -0800
Message-Id: <[email protected]>
Date: Thu, 6 Nov 2003 11:16:58 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <Pine.OS2.4.58.0311060752160.73@barry>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Barry Landy <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 6 Nov 2003, Barry Landy wrote:

> For what it is worth the sender is an AOL customer, so I guess the
> failure to specify application/msword is widespread.

I shouldn't have implied that the sending client was at fault.  A client's
ability to correctly label mime-type depends upon a lot of things.  For
instance, if the system itself isn't set up correctly (like a lack of some
mime-type information in the Windows registry), then the client has little
other option than to label it "octet-stream".

Webmail clients have an even harder time of it, with the web server having
to make assumptions of the attachments that get handed to it.

Jeff

From [email protected] Thu Nov  6 11:33:48 2003 -0800
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 11:33:48 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JXlNL021677;
       Thu, 6 Nov 2003 11:33:47 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JXjCk025626
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 11:33:46 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6JXYFe015476;
       Thu, 6 Nov 2003 11:33:34 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JWthW017760
       for <[email protected]>; Thu, 6 Nov 2003 11:32:55 -0800
Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20])
       by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JWsTO016733
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Thu, 6 Nov 2003 11:32:54 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
       by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JWp0Y014317;
       Thu, 6 Nov 2003 11:32:51 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JWox0004180
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Thu, 6 Nov 2003 11:32:50 -0800
Message-Id: <[email protected]>
Date: Thu, 6 Nov 2003 11:30:45 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mats Dufberg <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 6 Nov 2003, Mats Dufberg wrote:

> It should be the same warning for opening something based on content-type
> or "extension". Yes, you should be able to turn it off.

The extension warning is an extra one.   This was intended for the case
where content-type displayed to the user is an image, but the file
extension itself is something like .exe.  image/gif should always open
whatever program is supposed to handle .gif files, but if there is no
entry for image/gif, the next thing to do would be to open by file
extension, in which case we probably want to warn.

> A feature request in this area is to be able to dynamically select a
> program for an attachment.

We'll consider adding something like this.  Some changes already made in
4.60 might address this a very little bit also.

Jeff

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 11:42:28 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JgRNL022054;
       Thu, 6 Nov 2003 11:42:27 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JgPCk025949
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 11:42:26 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6JgGAk011380;
       Thu, 6 Nov 2003 11:42:16 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JfwhW028202
       for <[email protected]>; Thu, 6 Nov 2003 11:41:58 -0800
Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JfvpX028613
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Thu, 6 Nov 2003 11:41:57 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
       by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6JfoMk003734;
       Thu, 6 Nov 2003 11:41:50 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6Jfox0005288
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Thu, 6 Nov 2003 11:41:50 -0800
Message-Id: <[email protected]>
Date: Thu, 6 Nov 2003 11:39:45 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <Pine.GSO.4.58.0311061101560.923@eltanin>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Gopi Sundaram <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 6 Nov 2003, Gopi Sundaram wrote:

> On Wed, 5 Nov 2003, Jeff Franklin wrote:
>
> > We'll go ahead and change that unless there is a large outcry.
>
> Here's my small outcry. I'd rather an additional config option be used
> to quell this behavior. If Pine is making a decision for me, I'd like to
> know about it. When I choose to open an attachment and it is of a known
> mime-type, then Pine is making no decision on my behalf. But when it
> infers something based on the filename, it is.

I guess a small outcry is just as good as a large one.  We'll likely just
go ahead and make it a separate feature.  I see your point about wanting
to preserve the behavior of the quell-attach... feature as is.  That
doesn't change the point that Mats was making, which was that it is
equally unsafe to open by mime-type as it is to open by extension.
Hopefully this is a happy compromise.

Jeff

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 12:55:26 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6KrXNL025369;
       Thu, 6 Nov 2003 12:53:33 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6KrUhW001367
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 12:53:31 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6KrFFe012118;
       Thu, 6 Nov 2003 12:53:15 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6KpxhW030770
       for <[email protected]>; Thu, 6 Nov 2003 12:51:59 -0800
Received: from law.usc.edu (law.usc.edu [128.125.42.6])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6Kpw5I011540
       for <[email protected]>; Thu, 6 Nov 2003 12:51:58 -0800
Received: from L2122 (l2122 [128.125.42.67])
       by law.usc.edu (Switch-2.2.8/Switch-2.2.6) with ESMTP id hA6KpvJ05306;
       Thu, 6 Nov 2003 12:51:57 -0800 (PST)
Message-Id: <Pine.WNT.4.58.0311061250160.3024@L2122>
Date: Thu, 6 Nov 2003 12:51:57 -0800 (Pacific Standard Time)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Robert Larmon <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <[email protected]>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jeff Franklin <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 6 Nov 2003, Jeff Franklin wrote:

> On Thu, 6 Nov 2003, Gopi Sundaram wrote:
>
> > On Wed, 5 Nov 2003, Jeff Franklin wrote:
> >
> > > We'll go ahead and change that unless there is a large outcry.
> >
> > Here's my small outcry. I'd rather an additional config option be used
> > to quell this behavior. If Pine is making a decision for me, I'd like to
> > know about it. When I choose to open an attachment and it is of a known
> > mime-type, then Pine is making no decision on my behalf. But when it
> > infers something based on the filename, it is.
>
> I guess a small outcry is just as good as a large one.  We'll likely just
> go ahead and make it a separate feature.  I see your point about wanting
> to preserve the behavior of the quell-attach... feature as is.  That
> doesn't change the point that Mats was making, which was that it is
> equally unsafe to open by mime-type as it is to open by extension.
> Hopefully this is a happy compromise.
>
> Jeff
>

Jeff, we would definitely appreciate this as an additional feature as
well.  Some of our users have asked about it, and it would be nice to make
it auto-magically work for them.

Thanks!

Rob

_________________________________

Robert Larmon
Senior Systems Analyst
USC Law School Computing Services
[email protected]
_________________________________

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 6 Nov 2003 15:09:45 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6N95NL032381;
       Thu, 6 Nov 2003 15:09:05 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6N93Ck000954
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 6 Nov 2003 15:09:03 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA6N8p1r014068;
       Thu, 6 Nov 2003 15:08:51 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6N7ohW017430
       for <[email protected]>; Thu, 6 Nov 2003 15:07:50 -0800
Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6N7nrS022955
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Thu, 6 Nov 2003 15:07:49 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6N4aC2000660;
       Thu, 6 Nov 2003 15:04:37 -0800
Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA6N4aSS019322
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Thu, 6 Nov 2003 15:04:36 -0800
Message-Id: <[email protected]>
Date: Thu, 6 Nov 2003 15:02:31 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Jeff Franklin <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PINE458 problem
In-Reply-To: <Pine.WNT.4.58.0311061250160.3024@L2122>
References: <Pine.WNT.4.55.0311052243140.-1702011@mrlandy>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Robert Larmon <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 6 Nov 2003, Robert Larmon wrote:

> Jeff, we would definitely appreciate this as an additional feature as
> well.  Some of our users have asked about it, and it would be nice to make
> it auto-magically work for them.

That settles it.  We'll go ahead and make it a separate feature.

Jeff

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 7 Nov 2003 04:33:37 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7CXVNL026271;
       Fri, 7 Nov 2003 04:33:31 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7CXThW026810
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 7 Nov 2003 04:33:30 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA7CXJAk010856;
       Fri, 7 Nov 2003 04:33:19 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7CWZhW021936
       for <[email protected]>; Fri, 7 Nov 2003 04:32:35 -0800
Received: from heinz.dinsnail.net (dinsnail.net [217.160.166.159])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7CWWFY007050
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Fri, 7 Nov 2003 04:32:33 -0800
Received: from heinz.dinsnail.net (heinz.dinsnail.net [127.0.0.1])
       by heinz.dinsnail.net (8.12.10/8.12.10) with ESMTP id hA7CWQH7026257
       (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
       Fri, 7 Nov 2003 13:32:26 +0100
Received: from localhost (michael@localhost)
       by heinz.dinsnail.net (8.12.10/8.12.10/Submit) with ESMTP id hA7CWPBK026252;
       Fri, 7 Nov 2003 13:32:25 +0100
Message-Id: <[email protected]>
Date: Fri, 7 Nov 2003 13:32:25 +0100 (CET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Michael Weiser <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: outgoing connection problems with 4.58
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: heinz.dinsnail.net: michael owned process doing -bs
X-MailScanner: Found to be clean
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='SIGNATURE_SHORT_DENSE, X_AUTH_WARNING, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello all,

version 4.58 of pine doesn't seem to be able to open connections for
sending mail or news on IRIX 6.5.21f. I'm using the same version on
Linux-2.4.20 (glibc-2.1.3/2.3.2) and Solaris-2.8 without any problems.
Anything up to and including 4.55 used to work fine on IRIX as well. I've
tried compiling 4.58 using gcc-3.2.3 as well as MIPSpro cc 7.2.3.1m. It
can open connections to IMAP and NNTP servers for reading but when I try
to send a mail via SMTP or post to a group using NNTP I get something like

[Error sending: Can't connect to mailserver,25: Invalid argument]

I've tried walking the code but can't find anything. Any hints would be
greatly appreciated. Has anything related to opening of outgoing
connections changed substantially from 4.55 to 4.58?
--
bye, Micha
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 7 Nov 2003 13:01:29 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7L1SNL012829;
       Fri, 7 Nov 2003 13:01:28 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7L1QhW009829
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 7 Nov 2003 13:01:27 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA7L1I1r010814;
       Fri, 7 Nov 2003 13:01:18 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7L0GhW015110
       for <[email protected]>; Fri, 7 Nov 2003 13:00:16 -0800
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22])
       by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA7L0FTN031773
       for <[email protected]>; Fri, 7 Nov 2003 13:00:16 -0800
Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225])
       by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id hA7L0FrY012604
       for <[email protected]>; Fri, 7 Nov 2003 13:00:15 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com
(Content Technologies SMTPRS 4.2.1) with ESMTP id <[email protected]> for <[email protected]>;
Fri, 7 Nov 2003 12:59:42 -0800
Received: from ackema.apple.com (ackema.apple.com [17.202.14.80])
       by scv2.apple.com (8.12.9/8.12.9) with ESMTP id hA7KxvEW027266
       for <[email protected]>; Fri, 7 Nov 2003 12:59:57 -0800 (PST)
Message-Id: <[email protected]>
Date: Fri, 7 Nov 2003 13:00:11 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Matt Ackeret <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Filter by size
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


It'd be great if I could filter by size.  It seems like most of the
patch spams are being caught (by spamassassin or my other filters), but not
all.

If I could move anything over 100K to my suspected spam folder, that'd
be great.

--
top-posting: It's just a bad idea.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 7 Nov 2003 16:34:52 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA80YpNL022837;
       Fri, 7 Nov 2003 16:34:51 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA80YnhW017198
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 7 Nov 2003 16:34:50 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA80YRAk010974;
       Fri, 7 Nov 2003 16:34:27 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA80XNhW007862
       for <[email protected]>; Fri, 7 Nov 2003 16:33:23 -0800
Received: from smtp-4.llnl.gov (smtp-4.llnl.gov [128.115.41.84])
       by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA80XLTN023018
       for <[email protected]>; Fri, 7 Nov 2003 16:33:22 -0800
Received: from tickleme.llnl.gov (localhost [127.0.0.1])
       by smtp-4.llnl.gov (8.12.3p2-20030917/8.12.3/LLNL evision: 1.11 $) with ESMTP id hA80XKoi018304
       for <[email protected]>; Fri, 7 Nov 2003 16:33:20 -0800 (PST)
Received: from tickleme.llnl.gov (localhost [127.0.0.1])
       by tickleme.llnl.gov (8.12.3p2-20030917/8.12.3/LLNL evsion$) with ESMTP id hA80XKrD006450
       for <[email protected]>; Fri, 7 Nov 2003 16:33:20 -0800 (PST)
Received: (from domo@localhost)
       by tickleme.llnl.gov (8.12.3p2-20030917/8.12.3/Submit) id hA80XJxe006449
       for [email protected]; Fri, 7 Nov 2003 16:33:19 -0800 (PST)
Message-Id: <[email protected]>
Date: Fri, 7 Nov 2003 16:33:19 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Just Another MD Owner  <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Thread view in pine 4.58
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __HAS_MSGID, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm *very* new to pine.  I've been reading the docs, faqs, etc.  I've been
experimenting with my .pinerc, and changing the settings from within pine.

I'm still missing something about threading.  When I first start up pine,
my mailbox view is not threaded.  I have to do $ H before the threading
shows up.

What configuration am I missing so that this will be the default behavior
when I start up pine?  Here's my current thread settings:

thread-index-shows-important-color
slash-collapses-entire-thread
threading-display-style=mutt
threading-index-style=exp
threading-indicator-character=>
threading-expanded-character=-.
threading-lastreply-character=|


Maybe I've read the answer in an FAQ somewhere, but didn't recognize it for
the jewel that it was...

Thanks,

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 7 Nov 2003 17:15:34 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA81FXNL024538;
       Fri, 7 Nov 2003 17:15:33 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA81FVhW018305
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 7 Nov 2003 17:15:32 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA81FKop014780;
       Fri, 7 Nov 2003 17:15:21 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA81EmhW022522
       for <[email protected]>; Fri, 7 Nov 2003 17:14:48 -0800
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA81ElFX007877
       for <[email protected]>; Fri, 7 Nov 2003 17:14:47 -0800
Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225])
       by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id hA81ElrY021279
       for <[email protected]>; Fri, 7 Nov 2003 17:14:47 -0800 (PST)
Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com
(Content Technologies SMTPRS 4.2.1) with ESMTP id <[email protected]> for <[email protected]>;
Fri, 7 Nov 2003 17:14:14 -0800
Received: from ackema.apple.com (ackema.apple.com [17.202.14.80])
       by scv3.apple.com (8.12.9/8.12.9) with ESMTP id hA81EH0n006112
       for <[email protected]>; Fri, 7 Nov 2003 17:14:17 -0800 (PST)
Message-Id: <[email protected]>
Date: Fri, 7 Nov 2003 17:14:43 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Matt Ackeret <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Thread view in pine 4.58
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 7 Nov 2003, Just Another MD Owner wrote:
>What configuration am I missing so that this will be the default behavior
>when I start up pine?  Here's my current thread settings:

sort-key                      =
           Set    Sort Options
           ---  ----------------------
           ( )  Subject
           ( )  Arrival
           ( )  From
           ( )  To
           ( )  Cc
           ( )  Date
           ( )  siZe
           ( )  OrderedSubj
           ( )  scorE
           (*)  tHread
           ( )  Reverse Subject
           ( )  Reverse Arrival
           ( )  Reverse From
           ( )  Reverse To
           ( )  Reverse Cc
           ( )  Reverse Date
           ( )  Reverse siZe
           ( )  Reverse OrderedSubj
           ( )  Reverse scorE
           ( )  Reverse tHread

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 8 Nov 2003 09:46:28 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA8HkSNL019179;
       Sat, 8 Nov 2003 09:46:28 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA8HkQhW007023
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sat, 8 Nov 2003 09:46:26 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA8Hjrop011496;
       Sat, 8 Nov 2003 09:45:53 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA8HjBhW014648
       for <[email protected]>; Sat, 8 Nov 2003 09:45:11 -0800
Received: from smtp-4.llnl.gov (smtp-4.llnl.gov [128.115.41.84])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA8HjAFX010133
       for <[email protected]>; Sat, 8 Nov 2003 09:45:10 -0800
Received: from tickleme.llnl.gov (localhost [127.0.0.1])
       by smtp-4.llnl.gov (8.12.3p2-20030917/8.12.3/LLNL evision: 1.11 $) with ESMTP id hA8Hj7rG012626;
       Sat, 8 Nov 2003 09:45:07 -0800 (PST)
Received: from tickleme.llnl.gov (localhost [127.0.0.1])
       by tickleme.llnl.gov (8.12.3p2-20030917/8.12.3/LLNL evsion$) with ESMTP id hA8Hj7rD017322;
       Sat, 8 Nov 2003 09:45:07 -0800 (PST)
Received: (from domo@localhost)
       by tickleme.llnl.gov (8.12.3p2-20030917/8.12.3/Submit) id hA8Hj7EB017321;
       Sat, 8 Nov 2003 09:45:07 -0800 (PST)
Message-Id: <[email protected]>
Date: Sat, 8 Nov 2003 09:45:07 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Just Another MD Owner  <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Thread view in pine 4.58
X-To: [email protected], [email protected]
X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> sort-key

Ah!  I see.  Thanks!

d


From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 10 Nov 2003 03:24:27 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAABORNL020924;
       Mon, 10 Nov 2003 03:24:27 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAABOPhW031962
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Mon, 10 Nov 2003 03:24:25 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAABOEAk011592;
       Mon, 10 Nov 2003 03:24:15 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAABLThW028420
       for <[email protected]>; Mon, 10 Nov 2003 03:21:29 -0800
Received: from imag.imag.fr (imag.imag.fr [129.88.30.1])
       by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAABLQTO032374
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Mon, 10 Nov 2003 03:21:27 -0800
Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12])
       by imag.imag.fr (8.12.10/8.12.10) with ESMTP id hAABLLUO022309
       for <[email protected]>; Mon, 10 Nov 2003 12:21:21 +0100 (CET)
Received: from gandoliere.imag.fr ([129.88.43.136] ident=kowalski)
       by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian))
       id 1AJA6j-0006TV-00
       for <[email protected]>; Mon, 10 Nov 2003 12:21:21 +0100
Message-Id: <[email protected]>
Date: Mon, 10 Nov 2003 12:21:21 +0100 (MET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Nicolas Kowalski <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: pruned-format ?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-IMAG-MailScanner: Found to be clean
X-IMAG-MailScanner-Information: Please contact the ISP for more information
X-Uwash-Spam: Gauge=III, Probability=3%, Report='SIGNATURE_SHORT_SPARSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Hello.

Is there a way to make pine rename pruned folder to something else that
<folder>-<monthname>-<year> ?

For example, I find more handy the way the pine-info archives are named
(pine-info.<year>.<monthnumber>), and it would be nice to make pruned
folder renamed like that.

Thanks.

--
Nicolas

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 11 Nov 2003 02:14:12 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABAEBNL004608;
       Tue, 11 Nov 2003 02:14:11 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABAE9pd009003
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 11 Nov 2003 02:14:09 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hABADv1r013410;
       Tue, 11 Nov 2003 02:13:58 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABACxhW030878
       for <[email protected]>; Tue, 11 Nov 2003 02:12:59 -0800
Received: from grieg.dmu.ac.uk (grieg.dmu.ac.uk [146.227.1.5])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABACupW004095
       for <[email protected]>; Tue, 11 Nov 2003 02:12:57 -0800
Received: from brains.eng.cse.dmu.ac.uk (brains.eng.cse.dmu.ac.uk [146.227.22.1])
       by grieg.dmu.ac.uk (8.12.10/8.12.10) with ESMTP id hABACPhW009800
       for <[email protected]>; Tue, 11 Nov 2003 10:12:25 GMT
Received: from neelix ([146.227.22.22])
       by brains.eng.cse.dmu.ac.uk with esmtp (Exim 3.36 #1)
       id 1AJVVW-0003OL-00
       for [email protected]; Tue, 11 Nov 2003 10:12:22 +0000
Received: from hgs (helo=localhost)
       by neelix with local-esmtp (Exim 3.36 #1)
       id 1AJVVV-0006Z2-00
       for [email protected]; Tue, 11 Nov 2003 10:12:21 +0000
Message-Id: <Pine.GSO.4.58.0311110958270.23370@neelix>
Date: Tue, 11 Nov 2003 10:12:21 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Hugh Sasse Staff Elec Eng <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: sending-filter to inhibit munged addresses?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: Hugh Sasse Staff Elec Eng <[email protected]>
X-X-Sender: hgs@neelix
X-DMU-MailScanner: Found to be clean
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Scouring the web I see there are sending-filters for pine, with
parameters which map to the temp files pine uses when creating
messages.  The docs are OK, but I was wondering if there are any
examples out there of such filters so I can get a better feel for
this.

These days there seems to be an increasing tendency for people to
munge addresses in an attempt to foil spammers.  The RFCs say this
should not happen, but they pre-date the present scale of the spam
problem.  What I want to do is to prevent myself from mailing to
addresses that contain /spam/i -- things like
[email protected], by mistake.  I don't need the filter to
correct the address, just prevent me sending when I've forgotten to
check whether the address is munged.  Clearly I need to be able to
override the block if I want to sent to anti-spam sites which
legitimately have spam in the domain name.

This needs access to the To:, CC: and BCC: headers, and I'll have to
interact with it to some extent.  If this is possible and anyone has
examples of filters that access this info then I'd be interested in
seeing them so I can be more confident about crafting something
myself.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 11 Nov 2003 11:15:14 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABJFDNL020056;
       Tue, 11 Nov 2003 11:15:13 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABJFBCk016631
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 11 Nov 2003 11:15:11 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hABJF0Ak015528;
       Tue, 11 Nov 2003 11:15:00 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABJE9hW012204
       for <[email protected]>; Tue, 11 Nov 2003 11:14:09 -0800
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABJE7FX010413
       for <[email protected]>; Tue, 11 Nov 2003 11:14:08 -0800
Received: from mailspool2.panix.com (mailspool2.panix.com [166.84.1.79])
       by mail1.panix.com (Postfix) with ESMTP id 30EF848774
       for <[email protected]>; Tue, 11 Nov 2003 14:14:07 -0500 (EST)
Received: from lakers.ixiacom.com (64-60-75-66.cust.telepacific.net [64.60.75.66])
       by mailspool2.panix.com (Postfix) with ESMTP id D44F5194701
       for <[email protected]>; Tue, 11 Nov 2003 14:14:05 -0500 (EST)
Message-Id: <[email protected]>
Date: Tue, 11 Nov 2003 11:13:39 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Kenneth Crudup <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: sending-filter to inhibit munged addresses?
In-Reply-To: <Pine.GSO.4.58.0311110958270.23370@neelix>
References: <Pine.GSO.4.58.0311110958270.23370@neelix>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


On Tue, 11 Nov 2003, Hugh Sasse Staff Elec Eng wrote:

> These days there seems to be an increasing tendency for people to
> munge addresses in an attempt to foil spammers.  The RFCs say this
> should not happen, but they pre-date the present scale of the spam
> problem.

Hrmph. If anyone *sends* me (non-spam, solicited) mail where I have to
unmunge their address to reply to 'em, they'll be waiting for hell to
freeze over before I bother to reply. While I can understand (if not
condone- that's what "procmail" is for) address munging in public fora,
having it go out that way on private E-mail is just *dumb*.

       -Kenny

--
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
H: 3801 E. Pacific Coast Hw #9, Long Beach, CA 90804-2014 (888) 454-8181
W: 26601 Agoura Road, Calabasas CA 91302-1959             (818) 444-3685

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 11 Nov 2003 12:48:52 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKmqNL023067;
       Tue, 11 Nov 2003 12:48:52 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKmoCk019161
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 11 Nov 2003 12:48:50 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hABKmfFe014016;
       Tue, 11 Nov 2003 12:48:41 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKlshW024978
       for <[email protected]>; Tue, 11 Nov 2003 12:47:54 -0800
Received: from eth0.b.smtp.sonic.net (eth0.b.smtp.sonic.net [64.142.19.4])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKlrQQ012273
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Tue, 11 Nov 2003 12:47:53 -0800
Received: from 64-48-202-193-phx-01.cvx.algx.net (64-48-202-193-phx-01.cvx.algx.net [64.48.202.193])
       by eth0.b.smtp.sonic.net (8.12.10/8.12.7) with ESMTP id hABKlmCF016304
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Tue, 11 Nov 2003 12:47:51 -0800
Message-Id: <[email protected]>
Date: Tue, 11 Nov 2003 14:13:04 -0700 (MST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Bob Holtzman <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: SMTP authorization
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_LONG_SPARSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Does pine-4.44-19.73.0 support SMTP authorization? My ISP recently
changed their leased line provider and at that point I began to get
"relaying denied" errors with a reference to authorization. It
turned out that when The ISP talked the provider into allowing
relaying the problem disappeared. The provider, however, does't
like allowing relaying and may eliminate it in the future.I looked
all over the $HOME/.pine rc file and couldn't find a reference to
SMTP authorization. Did I miss something?

Any pointers would be appreciated. Thanks.

--
Bob Holtzman
"If you think you're getting free lunch,
......check the price of the beer!"

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 11 Nov 2003 12:56:16 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKuFNL023321;
       Tue, 11 Nov 2003 12:56:15 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKuDCk019377
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 11 Nov 2003 12:56:13 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hABKu4Fe014540;
       Tue, 11 Nov 2003 12:56:04 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKtghW016456
       for <[email protected]>; Tue, 11 Nov 2003 12:55:42 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABKtcQQ013544
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Tue, 11 Nov 2003 12:55:41 -0800
Received: from localhost (localhost [127.0.0.1])
       by aslan.narnia.pp.se (8.12.8p2/8.12.8) with ESMTP id hABKtSlk054057;
       Tue, 11 Nov 2003 21:55:29 +0100 (CET)
       (envelope-from [email protected])
Message-Id: <[email protected]>
Date: Tue, 11 Nov 2003 21:55:28 +0100 (CET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mats Dufberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: SMTP authorization
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Bob Holtzman <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Nov 11, 2003, 14:13 (-0700) Bob Holtzman <[email protected]> wrote:

>
> Does pine-4.44-19.73.0 support SMTP authorization? My ISP recently
> changed their leased line provider and at that point I began to get
> "relaying denied" errors with a reference to authorization. It
> turned out that when The ISP talked the provider into allowing
> relaying the problem disappeared. The provider, however, does't
> like allowing relaying and may eliminate it in the future.I looked
> all over the $HOME/.pine rc file and couldn't find a reference to
> SMTP authorization. Did I miss something?

Goto "setup" in the main menu. Press "c" for "config", and put the cursor
over "smtp-server  =". Then press "?" to get help, and there you'll find
information.



Mats

-----------------------------------------------------------------
Mats Dufberg                                      [email protected]
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 11 Nov 2003 13:03:49 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABL3mNL023521;
       Tue, 11 Nov 2003 13:03:48 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABL3kpd024727
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 11 Nov 2003 13:03:46 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hABL3bAk005060;
       Tue, 11 Nov 2003 13:03:38 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABL3ChW012168
       for <[email protected]>; Tue, 11 Nov 2003 13:03:12 -0800
Received: from mxsf24.cluster1.charter.net (mxsf24.cluster1.charter.net [209.225.28.224])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hABL3AFX031134
       for <[email protected]>; Tue, 11 Nov 2003 13:03:11 -0800
Received: from cygnus.hemisphere (24.236.227.45.bay.mi.chartermi.net [24.236.227.45])
       by mxsf24.cluster1.charter.net (8.12.10/8.12.8) with ESMTP id hABKwlCR029215;
       Tue, 11 Nov 2003 15:58:47 -0500 (EST)
       (envelope-from [email protected])
Received: from cygnus.hemisphere (localhost [127.0.0.1])
       by cygnus.hemisphere (8.12.10/8.12.10/Debian-4) with ESMTP id hABKwke9026987;
       Tue, 11 Nov 2003 15:58:47 -0500
Received: from localhost (arthur@localhost)
       by cygnus.hemisphere (8.12.10/8.12.10/Debian-4) with ESMTP id hABKwiUr026983;
       Tue, 11 Nov 2003 15:58:45 -0500
Message-Id: <[email protected]>
Date: Tue, 11 Nov 2003 15:58:44 -0500 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Arthur H. Johnson II" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: SMTP authorization
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Bob Holtzman <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: cygnus.hemisphere: arthur owned process doing -bs
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, X_AUTH_WARNING, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Yes, for smtp-server you would put the following:

smtp.host.com/user=youruser

You should be prompted after that.

Some SMTP auth have email address as the user, in that case put:

smtp.host.com/[email protected]

You may have to escape the "@" (I don't actually remember off the top of
my head)

smtp.host.com/user=user\@host.com

On Tue, 11 Nov 2003, Bob Holtzman wrote:

>
> Does pine-4.44-19.73.0 support SMTP authorization? My ISP recently
> changed their leased line provider and at that point I began to get
> "relaying denied" errors with a reference to authorization. It
> turned out that when The ISP talked the provider into allowing
> relaying the problem disappeared. The provider, however, does't
> like allowing relaying and may eliminate it in the future.I looked
> all over the $HOME/.pine rc file and couldn't find a reference to
> SMTP authorization. Did I miss something?
>
> Any pointers would be appreciated. Thanks.
>
>

--
Arthur H. Johnson II, [email protected]
AIM:  bytor4232
YIM:  arthurjohnson
IRC:  [email protected]

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 12 Nov 2003 11:39:39 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACJdcNL008129;
       Wed, 12 Nov 2003 11:39:38 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACJdZpd029218
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 12 Nov 2003 11:39:36 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hACJdQFe012836;
       Wed, 12 Nov 2003 11:39:26 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACJcRuL014936
       for <[email protected]>; Wed, 12 Nov 2003 11:38:27 -0800
Received: from dmu.ac.uk (motown.dmu.ac.uk [146.227.1.21])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACJcO5I017964
       for <[email protected]>; Wed, 12 Nov 2003 11:38:25 -0800
Received: from brains.eng.cse.dmu.ac.uk (brains.eng.cse.dmu.ac.uk [146.227.22.1])
       by dmu.ac.uk (8.12.10/8.12.10) with ESMTP id hACJbhde004430
       for <[email protected]>; Wed, 12 Nov 2003 19:37:44 GMT
Received: from neelix ([146.227.22.22])
       by brains.eng.cse.dmu.ac.uk with esmtp (Exim 3.36 #1)
       id 1AK0oB-0007mq-00
       for [email protected]; Wed, 12 Nov 2003 19:37:43 +0000
Received: from hgs (helo=localhost)
       by neelix with local-esmtp (Exim 3.36 #1)
       id 1AK0oA-0007i5-00
       for [email protected]; Wed, 12 Nov 2003 19:37:42 +0000
Message-Id: <Pine.GSO.4.58.0311121917170.28708@neelix>
Date: Wed, 12 Nov 2003 19:37:42 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Hugh Sasse Staff Elec Eng <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: sending-filter to inhibit munged addresses?
In-Reply-To: <[email protected]>
References: <Pine.GSO.4.58.0311110958270.23370@neelix>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: Hugh Sasse Staff Elec Eng <[email protected]>
X-X-Sender: hgs@neelix
X-DMU-MailScanner-Information: Please contact the ISP for more information
X-DMU-MailScanner: Found to be clean
X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Thanks to an example from Eduardo Chappa I now have a working
script.

The script below is written in ruby.  If you are unfamiliar with
Ruby see for example http://www.ruby-lang.org/ and
http://www.rubygarden.org/


The filter is setup using the M(enu) S(etup) C(onfig) screen in
Pine.  The commandline supplied to sending-filters is described in
the comments at the script start.

Additional remarks:
When the script "fails" -- i.e. traps a munged address, the screen
clears and there is a failure message from Pine, then one is told to
hit return, before the status line (supplied in _RESULTFILE_) is
displayed.  There seems to be no way to inhibit this sequence of
events, and instead just have the message unsent with the supplied
status line displayed.  (This latter behaviour is what happens when
no recipients are specified, for example.)

The sending-filter can fail either by deleting the _TMPFILE_ or by
returning a non-zero exit status. (Actually, I have not tested what
positive values of exit status achieve, only 0 or negative.) Both of
these modes cause the screen to clear as above.

I hope this information is of use to someone else.
       Thank you,
       Hugh

#!/usr/local/bin/ruby -w

# Pine filter.  When setup with
#
# sending-filters=/full/path/to/this/filter _TMPFILE_ _RESULTFILE_ _RECIPIENTS_
#
# then ARGV[0] contains the name of the temp file holding  message
# as it is, and as it will be when filtered.  To cause this to fail
# delete this file. Deleting the file still leaves the message body
# in pine as it was. Alternatively exit with -1 instead of 0.
#
# ARGV[1] is the results file that will be created
# by this program, i.e. a status message.
#
# ARGV[2..-1] will be the recipients, including those in bcc lines
#

message = nil
ARGV[2..-1].each {|recipient|
   case recipient
   when /spam/i, /example.com$/i
       message = "#{recipient} possibly munged"
       break
   end
}

unless message.nil?
   open(ARGV[1],"w"){|fp| fp.puts message }
   File.delete(ARGV[0])
   exit(-1)
end
exit(0)


From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 14 Nov 2003 04:32:19 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAECWENL000509;
       Fri, 14 Nov 2003 04:32:14 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAECWCCk032426
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 14 Nov 2003 04:32:12 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAECW2Ak015718;
       Fri, 14 Nov 2003 04:32:02 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAECV1uL019338
       for <[email protected]>; Fri, 14 Nov 2003 04:31:01 -0800
Received: from tx0.oucs.ox.ac.uk (tx0.oucs.ox.ac.uk [129.67.1.163])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAECUx5I008330
       for <[email protected]>; Fri, 14 Nov 2003 04:31:00 -0800
Received: from scan0.oucs.ox.ac.uk ([129.67.1.162] helo=localhost)
       by tx0.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AKd6I-0000nZ-Ea
       for [email protected]; Fri, 14 Nov 2003 12:30:58 +0000
Received: from rx0.oucs.ox.ac.uk ([129.67.1.161])
by localhost (scan0.oucs.ox.ac.uk [129.67.1.162]) (amavisd-new, port 25)
with ESMTP id 02933-03 for <[email protected]>;
Fri, 14 Nov 2003 12:30:58 +0000 (GMT)
Received: from crow.linux.ox.ac.uk ([163.1.2.97])
       by rx0.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AKd6I-0000nT-1E
       for [email protected]; Fri, 14 Nov 2003 12:30:58 +0000
Message-Id: <[email protected]>
Date: Fri, 14 Nov 2003 12:30:58 +0000 (GMT)
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Cummings <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Config file not changeable, can't change options or settings
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Hiya,

Using pine4.58 whenever I try and Take something to a filter from
anything other than my INBOX (and sometimes even there)
I get the message:

[Config file not changeable, can't change options or settings]

Sometimes quiting pine entirely and restarting it solves the
problem, sometimes it doesn't.

my ~/.pinerc is user/group/other rwx.

Any suggestions?

-James

---
Dr James Cummings, Oxford Text Archive, [email protected]
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 14 Nov 2003 11:05:23 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEJ5LNL014939;
       Fri, 14 Nov 2003 11:05:21 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEJ5Jpd014490
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 14 Nov 2003 11:05:20 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAEJ5AFe012536;
       Fri, 14 Nov 2003 11:05:10 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEJ4RuL023136
       for <[email protected]>; Fri, 14 Nov 2003 11:04:28 -0800
Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100])
       by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEJ4O0n024268
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Fri, 14 Nov 2003 11:04:26 -0800
Received: from localhost (localhost [127.0.0.1])
       by aslan.narnia.pp.se (8.12.8p2/8.12.8) with ESMTP id hAEJ4Llk067882;
       Fri, 14 Nov 2003 20:04:22 +0100 (CET)
       (envelope-from [email protected])
Message-Id: <[email protected]>
Date: Fri, 14 Nov 2003 20:04:21 +0100 (CET)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Mats Dufberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: James Cummings <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/
X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Nov 14, 2003, 12:30 (-0000) James Cummings <[email protected]...:

> Using pine4.58 whenever I try and Take something to a filter from
> anything other than my INBOX (and sometimes even there)
> I get the message:
>
> [Config file not changeable, can't change options or settings]
>
> Sometimes quiting pine entirely and restarting it solves the
> problem, sometimes it doesn't.
>
> my ~/.pinerc is user/group/other rwx.

I could imagen that pine does not like the file to have such lax
permission. Try "chmod 644" or "chmod 640" on the file.


Mats

-----------------------------------------------------------------
Mats Dufberg                                      [email protected]
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 14 Nov 2003 14:54:32 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEMsVNL026029;
       Fri, 14 Nov 2003 14:54:31 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEMsSCk020241
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 14 Nov 2003 14:54:30 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAEMsCAk011680;
       Fri, 14 Nov 2003 14:54:12 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEMrRuL017334
       for <[email protected]>; Fri, 14 Nov 2003 14:53:27 -0800
Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEMrQrS018573
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Fri, 14 Nov 2003 14:53:26 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
       by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEMrP0Y009806
       for <[email protected]>; Fri, 14 Nov 2003 14:53:26 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAEMrPx0012069
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
       for <[email protected]>; Fri, 14 Nov 2003 14:53:25 -0800
Message-Id: <[email protected]>
Date: Fri, 14 Nov 2003 14:53:25 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Hubert <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Make sure the directory in which the pinerc file is contained is also
writeable.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 16 Nov 2003 10:28:22 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAGISGNL002335;
       Sun, 16 Nov 2003 10:28:16 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAGISECk016948
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Sun, 16 Nov 2003 10:28:15 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAGIS4Ak012738;
       Sun, 16 Nov 2003 10:28:04 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAGIQkuL013736
       for <[email protected]>; Sun, 16 Nov 2003 10:26:46 -0800
Received: from holly.csn.ul.ie (holly.csn.ul.ie [136.201.105.4])
       by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAGIQjTN030479
       for <[email protected]>; Sun, 16 Nov 2003 10:26:45 -0800
Received: from skynet.csn.ul.ie (skynet [136.201.105.2])
       by holly.csn.ul.ie (Postfix) with ESMTP id 1150693681
       for <[email protected]>; Sun, 16 Nov 2003 18:26:43 +0000 (Eire)
Received: by skynet.csn.ul.ie (Postfix, from userid 2542)
       id 95677E7AE; Sun, 16 Nov 2003 18:26:43 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
       by skynet.csn.ul.ie (Postfix) with ESMTP id 8A02A7950
       for <[email protected]>; Sun, 16 Nov 2003 18:26:43 +0000 (GMT)
Message-Id: <Pine.LNX.4.58.0311161825060.27594@skynet>
Date: Sun, 16 Nov 2003 18:26:43 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Shane Mitchell <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: How to make reply use appropriate role
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: fragile@skynet
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hey,

I am using Pine with multiple roles, is it possible to have Pine recognise
the appropriate role to use, based on the To: header in the mail, when
replying to a mail rather than always defaulting to the primary role.
Currently the only solution I can find is to manually change the headers
and signature!

Any ideas/suggestions would be greatly appreciated

--

Shane Mitchell fragile_at_skynet_dot_ie +353861922853 ICQ:277303018
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 17 Nov 2003 01:56:01 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAH9u0NL027320;
       Mon, 17 Nov 2003 01:56:00 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAH9twpd007343
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Mon, 17 Nov 2003 01:55:58 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAH9tmFe012140;
       Mon, 17 Nov 2003 01:55:48 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAH9rJuL016662
       for <[email protected]>; Mon, 17 Nov 2003 01:53:19 -0800
Received: from tx2.oucs.ox.ac.uk (tx2.oucs.ox.ac.uk [163.1.2.163])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAH9rHFX013419
       for <[email protected]>; Mon, 17 Nov 2003 01:53:18 -0800
Received: from scan2.oucs.ox.ac.uk ([163.1.2.162] helo=localhost)
       by tx2.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1ALg4K-00051g-Lu
       for [email protected]; Mon, 17 Nov 2003 09:53:16 +0000
Received: from rx2.oucs.ox.ac.uk ([163.1.2.161])
by localhost (scan2.oucs.ox.ac.uk [163.1.2.162]) (amavisd-new, port 25)
with ESMTP id 18968-10 for <[email protected]>;
Mon, 17 Nov 2003 09:53:16 +0000 (GMT)
Received: from crow.linux.ox.ac.uk ([163.1.2.97])
       by rx2.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1ALg4K-00051c-8Y; Mon, 17 Nov 2003 09:53:16 +0000
Message-Id: <[email protected]>
Date: Mon, 17 Nov 2003 09:53:16 +0000 (GMT)
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Cummings <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Hubert <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 14 Nov 2003, Steve Hubert wrote:

> Make sure the directory in which the pinerc file is contained is also
> writeable.
>
> Steve Hubert <[email protected]>
> Networks and Distributed Computing, Univ. of Washington, Seattle

Yup, it seems to be.  (though why I should have to make my home
directory world writeable to be able to save pine config is beyond
me.  Surely this is a security flaw??)  I still occasionally get
the error in any case.

-James

---
Dr James Cummings, Oxford Text Archive, [email protected]

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 17 Nov 2003 02:07:43 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHA7gNL027785;
       Mon, 17 Nov 2003 02:07:42 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHA7dCk005122
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Mon, 17 Nov 2003 02:07:40 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAHA7UAk005288;
       Mon, 17 Nov 2003 02:07:30 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHA6iuL028262
       for <[email protected]>; Mon, 17 Nov 2003 02:06:44 -0800
Received: from tx1.oucs.ox.ac.uk (tx1.oucs.ox.ac.uk [129.67.1.167])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHA6gpW014627
       for <[email protected]>; Mon, 17 Nov 2003 02:06:42 -0800
Received: from scan1.oucs.ox.ac.uk ([129.67.1.166] helo=localhost)
       by tx1.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1ALgHJ-0001B7-H7
       for [email protected]; Mon, 17 Nov 2003 10:06:41 +0000
Received: from rx1.oucs.ox.ac.uk ([129.67.1.165])
by localhost (scan1.oucs.ox.ac.uk [129.67.1.166]) (amavisd-new, port 25)
with ESMTP id 04238-10 for <[email protected]>;
Mon, 17 Nov 2003 10:06:41 +0000 (GMT)
Received: from crow.linux.ox.ac.uk ([163.1.2.97])
       by rx1.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1ALgHJ-0001B3-3q; Mon, 17 Nov 2003 10:06:41 +0000
Message-Id: <[email protected]>
Date: Mon, 17 Nov 2003 10:06:41 +0000 (GMT)
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Cummings <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mats Dufberg <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 14 Nov 2003, Mats Dufberg wrote:

> On Nov 14, 2003, 12:30 (-0000) James Cummings <[email protected]...:
>
> > Using pine4.58 whenever I try and Take something to a filter from
> > anything other than my INBOX (and sometimes even there)
> > I get the message:
> >
> > [Config file not changeable, can't change options or settings]
> >
> > Sometimes quiting pine entirely and restarting it solves the
> > problem, sometimes it doesn't.
> >
> > my ~/.pinerc is user/group/other rwx.
>
> I could imagen that pine does not like the file to have such lax
> permission. Try "chmod 644" or "chmod 640" on the file.

Nope, 600, 604 640 doesn't matter, still get the same error message.
Doesn't seem to matter whether I have extremely lax permissions (world
rw or rwx) or extremely tight ones (only user rw) or anywhere in
between.

-James

---
Dr James Cummings, Oxford Text Archive, [email protected]

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 17 Nov 2003 11:20:28 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJKRNL017044;
       Mon, 17 Nov 2003 11:20:27 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJKPCk021253
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Mon, 17 Nov 2003 11:20:26 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAHJKEop014776;
       Mon, 17 Nov 2003 11:20:14 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJJNuL034218
       for <[email protected]>; Mon, 17 Nov 2003 11:19:23 -0800
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJJMrR021708
       for <[email protected]>; Mon, 17 Nov 2003 11:19:22 -0800
Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225])
       by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id hAHJJMLh021999
       for <[email protected]>; Mon, 17 Nov 2003 11:19:22 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com
(Content Technologies SMTPRS 4.2.1) with ESMTP id <[email protected]> for <[email protected]>;
Mon, 17 Nov 2003 11:18:47 -0800
Received: from ackema.apple.com (ackema.apple.com [17.202.14.80])
       by scv2.apple.com (8.12.9/8.12.9) with ESMTP id hAHJJ2EW016451
       for <[email protected]>; Mon, 17 Nov 2003 11:19:02 -0800 (PST)
Message-Id: <[email protected]>
Date: Mon, 17 Nov 2003 11:19:18 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Matt Ackeret <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: A few things regarding formatting errors...
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='LINES_OF_YELLING, SIGNATURE_SHORT_DENSE, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


1) In a message I got (an announcement of a new Fink package), here's part
of what I see:

   [ The following text is in the "UTF-8" character set. ]
   [ Your display is set for the "US-ASCII" character set.  ]
   [ Some characters may be displayed incorrectly. ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

...

The fink package manager has been improved, i
  [Error: Formatting error: Non-hexadecimal character in QP encoding]


I know I had a similar problem like this with another message.  I can
view the message fine in a GUI mail program, and the message just has a plain
text part.  Even looking at the raw source of the message, I see no
'funky' chars in that sentence or near where it is showing the error.

How do I figure out what's actually wrong or fix it? If I change my character
set, will that work around the problem?


2) The particular bad message is message 2071 when my mailbox is viewed by
thread.  When I try to forward it, I get two error messages similar to the
formatting one above (one formatting one, one saying it was unable to forward).

However, the message # given is the message's *arrival* number.  i.e. it's
telling me unable to forward message 2066.  Shouldn't it really be
showing me the "virtual" message number?  I sure think it should.

I'm using pine 4.55.

--
top-posting: It's just a bad idea.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 17 Nov 2003 11:35:26 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJZPNL017867;
       Mon, 17 Nov 2003 11:35:25 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJZNpd024090
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Mon, 17 Nov 2003 11:35:24 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAHJZCFe016010;
       Mon, 17 Nov 2003 11:35:12 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJYduL036072
       for <[email protected]>; Mon, 17 Nov 2003 11:34:39 -0800
Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJYcrS026288
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Mon, 17 Nov 2003 11:34:38 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJYcC2030208
       for <[email protected]>; Mon, 17 Nov 2003 11:34:38 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHJYbSS014984
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
       for <[email protected]>; Mon, 17 Nov 2003 11:34:37 -0800
Message-Id: <[email protected]>
Date: Mon, 17 Nov 2003 11:34:37 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Hubert <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 17 Nov 2003, James Cummings wrote:

> Yup, it seems to be.  (though why I should have to make my home
> directory world writeable to be able to save pine config is beyond
> me.  Surely this is a security flaw??)  I still occasionally get
> the error in any case.
>
> -James

Sorry, I didn't mean world writeable, just writeable by you.

Are there any clues in the .pine-debug* file when this happens? If you can
reproduce at will, you could run pine with lots of debugging

  pine -d verbose=9,imap=4

and if you would send the resulting debug file to us at
[email protected], we'll take a look at it. Thanks.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 03:44:08 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIBi6NL022688;
       Tue, 18 Nov 2003 03:44:06 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIBi0pd020116
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 03:44:01 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAIBhmop005064;
       Tue, 18 Nov 2003 03:43:48 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIBgquL030206
       for <[email protected]>; Tue, 18 Nov 2003 03:42:52 -0800
Received: from tx1.oucs.ox.ac.uk (tx1.oucs.ox.ac.uk [129.67.1.167])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIBgoQP007632
       for <[email protected]>; Tue, 18 Nov 2003 03:42:50 -0800
Received: from scan1.oucs.ox.ac.uk ([129.67.1.166] helo=localhost)
       by tx1.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AM4Ft-0006TC-HR
       for [email protected]; Tue, 18 Nov 2003 11:42:49 +0000
Received: from rx1.oucs.ox.ac.uk ([129.67.1.165])
by localhost (scan1.oucs.ox.ac.uk [129.67.1.166]) (amavisd-new, port 25)
with ESMTP id 24679-06 for <[email protected]>;
Tue, 18 Nov 2003 11:42:49 +0000 (GMT)
Received: from crow.linux.ox.ac.uk ([163.1.2.97])
       by rx1.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AM4Ft-0006T6-47; Tue, 18 Nov 2003 11:42:49 +0000
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 11:42:49 +0000 (GMT)
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Cummings <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Hubert <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 17 Nov 2003, Steve Hubert wrote:

> On Mon, 17 Nov 2003, James Cummings wrote:
>
> > Yup, it seems to be.  (though why I should have to make my home
> > directory world writeable to be able to save pine config is beyond
> > me.  Surely this is a security flaw??)  I still occasionally get
> > the error in any case.
> >
> > -James
>
> Sorry, I didn't mean world writeable, just writeable by you.
>
> Are there any clues in the .pine-debug* file when this happens? If you can
> reproduce at will, you could run pine with lots of debugging
>
>    pine -d verbose=9,imap=4


I would love to but:

jamesc@crow:~$ pine -d verbose=9,imap=4
Argument Error: unknown flag "d", debugging not compiled in

so no .pine-debug* files either. :-(

Not my system so I'm unable to recompile pine either.  Sorry that
this isn't very helpful.

The various folders (inbox, read-mail, etc.) are on a remote
server using ssl if that helps...

It seems to happen more frequently when I'm 'T'aking from a
message in read-mail to a Filter... it has never happened
'T'aking to my addressbook.

Any other suggestions?

-James
---
Dr James Cummings, Oxford Text Archive, [email protected]

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 04:33:37 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAICXZNL024750;
       Tue, 18 Nov 2003 04:33:35 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAICXXpd021288
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 04:33:34 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAICXOFe013632;
       Tue, 18 Nov 2003 04:33:24 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAICWfuL030104
       for <[email protected]>; Tue, 18 Nov 2003 04:32:41 -0800
Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAICWc5J032476
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Tue, 18 Nov 2003 04:32:40 -0800
Received: from [194.97.50.144] (helo=mx1.freenet.de)
       by mout0.freenet.de with asmtp (Exim 4.24)
       id 1AM525-0004Bh-Iz
       for [email protected]; Tue, 18 Nov 2003 13:32:37 +0100
Received: from p50868563.dip0.t-ipconnect.de ([80.134.133.99] helo=localhost)
       by mx1.freenet.de with asmtp (ID [email protected]) (Exim 4.24 #2)
       id 1AM525-0001ZT-6M
       for [email protected]; Tue, 18 Nov 2003 13:32:37 +0100
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 13:32:34 +0100 (=?iso-8859-1?Q?=28MEZ=29_Mitteleurop=E4ische_Zeit?=)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Cornelius C. Noack" <[email protected]>
To: Pine Discussion Forum <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]> <Pine.OS2.4.55.0310141637450.85@barry>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, SIGNATURE_SHORT_DENSE, SUBJ_MISSING, __CT, __CTE, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __SUBJ_MISSING, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I use pcpine 4.58, and, for longer replies to messages, my usual (ASCII)
text editor (TSE) as alternate editor.

Whenever I do that (while the message I reply to is still in the INBOX)
and then send the reply, I get a (warning? error?) message:

           [Mail Folder "INBOX" closed due to access error]

But apparently the reply got sent alright. If then I decide to save the
original message, I get the error message

                      [Message to save shrank!]

(rather frightening words).
Then after closing pine and reopening it, everything is OK.


This is just a bit of a bother, nothing serious, but still:

     (i) what does that mean: "message shrank" ?

    (ii) Do I misunderstand --and hence misuse -- something ?
         (what I can think of is that I should FIRST save the message
         to some other folder and then reply from there. But that would
         be slightly unfunctional: often I only decide after answering
         the message that I would want to save it).=00=00=00


Anybody have an answer?

ccn.
--
=2E...........................................................

 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: [email protected] or [email protected]
 WWW-page: www.itp.uni-bremen.de/~noack
=2E...........................................................

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 10:50:10 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIIo9NL004842;
       Tue, 18 Nov 2003 10:50:09 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIIo7pd000542
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 10:50:08 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAIInw1r015642;
       Tue, 18 Nov 2003 10:49:58 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIInKuL035536
       for <[email protected]>; Tue, 18 Nov 2003 10:49:20 -0800
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIInJrR015278
       for <[email protected]>; Tue, 18 Nov 2003 10:49:19 -0800
Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225])
       by mail-out4.apple.com (8.12.10/8.12.9) with ESMTP id hAIInJnc014220
       for <[email protected]>; Tue, 18 Nov 2003 10:49:19 -0800 (PST)
Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com
(Content Technologies SMTPRS 4.2.1) with ESMTP id <[email protected]> for <[email protected]>;
Tue, 18 Nov 2003 10:48:44 -0800
Received: from ackema.apple.com (ackema.apple.com [17.202.14.80])
       by scv1.apple.com (8.12.9/8.12.9) with ESMTP id hAIImlwx017897
       for <[email protected]>; Tue, 18 Nov 2003 10:48:47 -0800 (PST)
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 10:49:16 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Matt Ackeret <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: pine deadlocked?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


So the first time I started up pine this morning, it ended up hung.
The status wasn't "spinning", nothing.. I left it for many minutes longer than
it normally took.

Then I sampled it.  I can't repro this, but I've seen it a few times.  I think
it's deadlocked, but I'm not sure.  Starting it up again was very
fast.

This is pine 4.55 on Mac OS X.

Analysis of sampling pid 459 every 10.000000 milliseconds
Call graph:
   573 Thread_110b
     573 start
       573 _start
         573 main
           573 do_broach_folder
             573 process_filter_patterns
               573 calculate_some_scores
                 573 match_pattern
                   573 mail_search_full
                     573 imap_search
                       573 mail_search_default
                         573 mail_search_msg
                           573 mail_search_msg
                             573 mail_search_msg
                               573 mail_search_msg
                                 573 mail_search_msg
                                   573 mail_fetch_structure
                                     573 imap_structure
                                       573 imap_send
                                         573 imap_sout
                                           573 net_sout
                                             573 tcp_sout
                                               573 mm_log
                                                 573 localtime
                                                   573 tzsetwall_basic
                                                     573 notify_check_tz
                                                       573 notify_check
                                                         573 token_table_find
                                                           573 0x900fb428
                                                             573 _sigtramp
                                                               573 alarm_signal
                                                                 573 debugjournal
                                                                   573 add_review_message
                                                                     573 debug_time
                                                                       573 ctime
                                                                         573 localtime
                                                                           573 tzsetwall_basic
                                                                             573 notify_check_tz
                                                                               573 notify_check
                                                                                 573 token_table_find
                                                                                   573 pthread_mutex_lock
                                                                                     573 semaphore_wait_signal_trap
                                                                                       573 semaphore_wait_signal_trap

Total number in stack (recursive counted multiple, when >=5):
       5       mail_search_msg

Sort by top of stack, same collapsed (when >= 5):
       semaphore_wait_signal_trap        573




--
top-posting: It's just a bad idea.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 12:04:05 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIK44NL008544;
       Tue, 18 Nov 2003 12:04:04 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIK423F004116
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 12:04:03 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAIK3l1r012970;
       Tue, 18 Nov 2003 12:03:47 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIK2uuL021724
       for <[email protected]>; Tue, 18 Nov 2003 12:02:56 -0800
Received: from naz.edu (gateway.naz.edu [204.168.82.9])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAIK2sFX004873
       for <[email protected]>; Tue, 18 Nov 2003 12:02:55 -0800
Received: by gateway.naz.edu id <336220>; Tue, 18 Nov 2003 15:02:34 -0500
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 14:59:53 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Greg Dec <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Inbox not displaying all messages
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Accept-Language: en-us, en
X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='SIGNATURE_SHORT_DENSE, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello everyone!


Here is a wierd problem I have noticed with our recent install of Pine 4.44:

A few users have complained that they log into PINE and will see a few
messages in their INBOX folder, but when they go to download the
messages using Netscape mail or other IMAP/POP clients, there are
additional messages that DID NOT show up in PINE.   Further, these "new"
messages were OLDER than the ones that managed to be displayed in PINE.
Its almost as if PINE does not display all the new messages that are
there, but evidently the messages are there as other clients seem to
pick them up.   Could somehting be moving the messages directly to the
Mbox?  I checked all the PINE config files, but nothing is sent to
auto-move or anything like that.   Again,  its just a few messages here
and there.

I am new to this version of PINE and haven't really looked into  it in
detail as of yet.   I am sure some of you on here might suggest an
upgrade to the latest version, but this seemed so odd.

_greg


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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 17:36:08 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ1a7NL024044;
       Tue, 18 Nov 2003 17:36:07 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ1a5pd016618
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 17:36:05 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJ1ZrAk014058;
       Tue, 18 Nov 2003 17:35:53 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ1Z2uL033822
       for <[email protected]>; Tue, 18 Nov 2003 17:35:02 -0800
Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ1Z1PH029523
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Tue, 18 Nov 2003 17:35:01 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
       by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ1Z00Y029306
       for <[email protected]>; Tue, 18 Nov 2003 17:35:00 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ1Z0x0017051
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
       for <[email protected]>; Tue, 18 Nov 2003 17:35:00 -0800
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 17:35:00 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Hubert <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

That ought to mean that the config file is readonly for some reason. That
should mean that Setup/Config fails the same as Take to a Filter. Take to
an address book is a little different, because it is writing into the
address book, not the config file. When you get the failure taking to a
filter you will probably also get it if you try Setup/Config.

I'm not sure how it could be failing some of the time and not other times.
It's hard to debug without further debug info.

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

On Tue, 18 Nov 2003, James Cummings wrote:

> On Mon, 17 Nov 2003, Steve Hubert wrote:
>
> > On Mon, 17 Nov 2003, James Cummings wrote:
> >
> > > Yup, it seems to be.  (though why I should have to make my home
> > > directory world writeable to be able to save pine config is beyond
> > > me.  Surely this is a security flaw??)  I still occasionally get
> > > the error in any case.
> > >
> > > -James
> >
> > Sorry, I didn't mean world writeable, just writeable by you.
> >
> > Are there any clues in the .pine-debug* file when this happens? If you can
> > reproduce at will, you could run pine with lots of debugging
> >
> >    pine -d verbose=9,imap=4
>
>
> I would love to but:
>
> jamesc@crow:~$ pine -d verbose=9,imap=4
> Argument Error: unknown flag "d", debugging not compiled in
>
> so no .pine-debug* files either. :-(
>
> Not my system so I'm unable to recompile pine either.  Sorry that
> this isn't very helpful.
>
> The various folders (inbox, read-mail, etc.) are on a remote
> server using ssl if that helps...
>
> It seems to happen more frequently when I'm 'T'aking from a
> message in read-mail to a Filter... it has never happened
> 'T'aking to my addressbook.
>
> Any other suggestions?
>
> -James
> ---
> Dr James Cummings, Oxford Text Archive, [email protected]
>

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 18:01:32 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ21VNL024859;
       Tue, 18 Nov 2003 18:01:31 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ21Tpd017380
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 18:01:30 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJ21K1r013980;
       Tue, 18 Nov 2003 18:01:20 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ20guL021676
       for <[email protected]>; Tue, 18 Nov 2003 18:00:42 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ20frS004431
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Tue, 18 Nov 2003 18:00:41 -0800
Received: from mail.aurora.edu (mail.aurora.edu [64.107.89.49])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ208pc017303
       for <[email protected]>; Tue, 18 Nov 2003 18:00:10 -0800
Received: from localhost (slowe@localhost)
       by mail.aurora.edu (8.12.1/8.12.1) with ESMTP id hAJ206eN227247
       for <[email protected]>; Tue, 18 Nov 2003 20:00:06 -0600 (CST)
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 20:00:06 -0600 (CST)
Reply-To: Steve Lowe <[email protected]>
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Lowe <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: MARK SET Not Working
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Information List <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='SIGNATURE_LONG_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



Greetings,

This may not be a PINE problem.  We are using SSH Secure Shell
to connect to our MAIL server -- emulation is VT320.

However, if you press CTRL-^, the MARK SET flag is not displayed
and therefore you cannot delete/move multiple lines in a message.

Any ideas?

Thanks in advance.

-- Steve Lowe
   Information Services
   Aurora University

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 18:06:36 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ26ZNL025003;
       Tue, 18 Nov 2003 18:06:35 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ26X3F018245
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 18:06:34 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJ26Q1r013218;
       Tue, 18 Nov 2003 18:06:26 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ260uL035916
       for <[email protected]>; Tue, 18 Nov 2003 18:06:00 -0800
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
       by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ2600m007441
       for <[email protected]>; Tue, 18 Nov 2003 18:06:00 -0800
Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10])
       by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id hAJ25unN339286;
       Tue, 18 Nov 2003 18:05:56 -0800 (PST)
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 18:05:55 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Eduardo Chappa <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: MARK SET Not Working
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Lowe <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Steve Lowe ([email protected]) wrote in the pine-info list today:

:) This may not be a PINE problem.  We are using SSH Secure Shell to
:) connect to our MAIL server -- emulation is VT320.
:)
:) However, if you press CTRL-^, the MARK SET flag is not displayed and
:) therefore you cannot delete/move multiple lines in a message.

Try CTR-6, that is to say do not press the shift key. If that does not
work try ESC ESC ^.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 18:13:37 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ2DZNL025189;
       Tue, 18 Nov 2003 18:13:35 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ2DXpd017764
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 18:13:33 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJ2DOFe015268;
       Tue, 18 Nov 2003 18:13:25 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ2CxuL026796
       for <[email protected]>; Tue, 18 Nov 2003 18:12:59 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ2CwcC028135
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Tue, 18 Nov 2003 18:12:58 -0800
Received: from mail.aurora.edu (mail.aurora.edu [64.107.89.49])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ2Cupc017755
       for <[email protected]>; Tue, 18 Nov 2003 18:12:56 -0800
Received: from localhost (slowe@localhost)
       by mail.aurora.edu (8.12.1/8.12.1) with ESMTP id hAJ2CtOC244906
       for <[email protected]>; Tue, 18 Nov 2003 20:12:55 -0600 (CST)
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 20:12:53 -0600 (CST)
Reply-To: Steve Lowe <[email protected]>
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Lowe <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: MARK SET Not Working (*Solution*)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Information List <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Following Eduardo's suggestion, then way to turn on MARK SET is the
following keystroke sequence:

 ESC  ESC ^ (Shift - 6)

Yes, it works!!

Thanks,

-- Steve Lowe
   Information Services
   Aurora University

---------- Forwarded message ----------
Date: Tue, 18 Nov 2003 18:05:55 -0800 (PST)
From: Eduardo Chappa <[email protected]>
To: Steve Lowe <[email protected]>
Cc: Pine Discussion Forum <[email protected]>
Subject: Re: MARK SET Not Working

*** Steve Lowe ([email protected]) wrote in the pine-info list today:

:) This may not be a PINE problem.  We are using SSH Secure Shell to
:) connect to our MAIL server -- emulation is VT320.
:)
:) However, if you press CTRL-^, the MARK SET flag is not displayed and
:) therefore you cannot delete/move multiple lines in a message.

Try CTR-6, that is to say do not press the shift key. If that does not
work try ESC ESC ^.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 18 Nov 2003 20:06:14 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ46ENL028126;
       Tue, 18 Nov 2003 20:06:14 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ46Cpd020550
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Tue, 18 Nov 2003 20:06:12 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJ463op011814;
       Tue, 18 Nov 2003 20:06:03 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ45LuL033870
       for <[email protected]>; Tue, 18 Nov 2003 20:05:21 -0800
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
       by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJ45K0M011194
       for <[email protected]>; Tue, 18 Nov 2003 20:05:20 -0800
Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10])
       by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id hAJ45InN347482;
       Tue, 18 Nov 2003 20:05:18 -0800 (PST)
Message-Id: <[email protected]>
Date: Tue, 18 Nov 2003 20:05:18 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Eduardo Chappa <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Inbox not displaying all messages
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Greg Dec <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Greg Dec ([email protected]) wrote in the pine-info list today:

:) A few users have complained that they log into PINE and will see a few
:) messages in their INBOX folder, but when they go to download the
:) messages using Netscape mail or other IMAP/POP clients, there are
:) additional messages that DID NOT show up in PINE.  Further, these "new"
:) messages were OLDER than the ones that managed to be displayed in PINE.
:) Its almost as if PINE does not display all the new messages that are
:) there, but evidently the messages are there as other clients seem to
:) pick them up.  Could somehting be moving the messages directly to the
:) Mbox?  I checked all the PINE config files, but nothing is sent to
:) auto-move or anything like that.  Again, its just a few messages here
:) and there.

Hi Greg,

 Here there's an idea that explains in my mind what's happening.

  Could it be that your users are using Pine on local access, but
Netscape on an IMAP server?. If so, this is what's happening.

 A user connects using Netscape to the server. The server sees a mbox
file, which contains (but may not be) a unix style folder. If this is the
case, the server transfers all the messages from the server to the mbox
file and from that moment, the access is local. The server is like a proxy
between you and mbox. Messages are moved from wherever the inbox is to
the mbox file.

 Pine is started in a local session (not through the imap server). Pine
does not see the mbox file, because either the user disabled this driver
or because Pine was compiled without support for this driver (are you
using RedHat?). In this case, pine will only see /var/spool/mail/ and use
that as the INBOX. Messages stay in /var/spool/mail.

 If a user uses Pine and later Netscape in this form, Netscape will see
all messages in the spool plus those in the mbox file, giving the user the
idea that Pine missed some messages.

 Here there are some possible solutions for you:

1. Make users use the IMAP server to read their e-mail. Pine can be
  configured to read e-mail through imap. Simply define the inbox-path
  variable as

inbox-path={your.imapserver.com/user=UserId}inbox

All messages will be in mbox when they read them.

2. Another possible solution is to build Pine from scratch. If my hunch is
  correct and you are using RedHat, the problem will be solved
  immediately by building a fresh copy of Pine. Consider upgrading to
  4.58, which solves all security holes found so far.

3. Rebuild the server and disable the mbox driver before building.
  Transfer all messages from mbox to /var/spool/mail. Future access to
  INBOX will be in /var/spool/mail, instead of mbox.

My personal advice, is consider 1, then 3 and then 2. I am strongly biased
towards 3. In my opinion the mbox driver is a bad idea, exactly because of
your problem, but that's just my opinion. Other people think differently.

Take a look at my web page

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

for some more explanation on the mbox driver and how to disable it during
compilation.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 19 Nov 2003 06:10:07 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJEA5NL017346;
       Wed, 19 Nov 2003 06:10:05 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJEA3pd004013
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 19 Nov 2003 06:10:03 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJE8TFe015648;
       Wed, 19 Nov 2003 06:08:29 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJE7cuL024580
       for <[email protected]>; Wed, 19 Nov 2003 06:07:38 -0800
Received: from tx3.oucs.ox.ac.uk (tx3.oucs.ox.ac.uk [163.1.2.167])
       by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJE7a0m010579
       for <[email protected]>; Wed, 19 Nov 2003 06:07:36 -0800
Received: from scan3.oucs.ox.ac.uk ([163.1.2.166] helo=localhost)
       by tx3.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AMSzX-0001Ac-Nb
       for [email protected]; Wed, 19 Nov 2003 14:07:35 +0000
Received: from rx3.oucs.ox.ac.uk ([163.1.2.165])
by localhost (scan3.oucs.ox.ac.uk [163.1.2.166]) (amavisd-new, port 25)
with ESMTP id 04268-06 for <[email protected]>;
Wed, 19 Nov 2003 14:07:35 +0000 (GMT)
Received: from raven.linux.ox.ac.uk ([163.1.2.96])
       by rx3.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AMSzX-0001AW-AC; Wed, 19 Nov 2003 14:07:35 +0000
Message-Id: <[email protected]>
Date: Wed, 19 Nov 2003 14:07:35 +0000 (GMT)
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Cummings <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Hubert <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __TO_MALFORMED_2, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 18 Nov 2003, Steve Hubert wrote:

> That ought to mean that the config file is readonly for some reason. That
> should mean that Setup/Config fails the same as Take to a Filter. Take to
> an address book is a little different, because it is writing into the
> address book, not the config file. When you get the failure taking to a
> filter you will probably also get it if you try Setup/Config.

Nope, the setup/config never has claimed to be unchangeable.

> I'm not sure how it could be failing some of the time and not other times.
> It's hard to debug without further debug info.

*shrug* ok, I'll send it to the support people here.  At least to see if
they can turn on debugging.

-James

>
> Steve Hubert <[email protected]>
> Networks and Distributed Computing, Univ. of Washington, Seattle
>
> On Tue, 18 Nov 2003, James Cummings wrote:
>
> > On Mon, 17 Nov 2003, Steve Hubert wrote:
> >
> > > On Mon, 17 Nov 2003, James Cummings wrote:
> > >
> > > > Yup, it seems to be.  (though why I should have to make my home
> > > > directory world writeable to be able to save pine config is beyond
> > > > me.  Surely this is a security flaw??)  I still occasionally get
> > > > the error in any case.
> > > >
> > > > -James
> > >
> > > Sorry, I didn't mean world writeable, just writeable by you.
> > >
> > > Are there any clues in the .pine-debug* file when this happens? If you can
> > > reproduce at will, you could run pine with lots of debugging
> > >
> > >    pine -d verbose=9,imap=4
> >
> >
> > I would love to but:
> >
> > jamesc@crow:~$ pine -d verbose=9,imap=4
> > Argument Error: unknown flag "d", debugging not compiled in
> >
> > so no .pine-debug* files either. :-(
> >
> > Not my system so I'm unable to recompile pine either.  Sorry that
> > this isn't very helpful.
> >
> > The various folders (inbox, read-mail, etc.) are on a remote
> > server using ssl if that helps...
> >
> > It seems to happen more frequently when I'm 'T'aking from a
> > message in read-mail to a Filter... it has never happened
> > 'T'aking to my addressbook.
> >
> > Any other suggestions?
> >
> > -James
> > ---
> > Dr James Cummings, Oxford Text Archive, [email protected]
> >
>


---
Dr James Cummings, Oxford Text Archive, [email protected]

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 19 Nov 2003 08:15:29 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJGFTNL021715;
       Wed, 19 Nov 2003 08:15:29 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJGFPpd007987
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 19 Nov 2003 08:15:25 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJGFG1r013248;
       Wed, 19 Nov 2003 08:15:16 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJGEduL015884
       for <[email protected]>; Wed, 19 Nov 2003 08:14:39 -0800
Received: from mail.astro.princeton.edu (mercury.astro.Princeton.EDU [128.112.25.50])
       by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJGEbLl027286
       for <[email protected]>; Wed, 19 Nov 2003 08:14:38 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
       by mail.astro.princeton.edu (Postfix) with ESMTP id 348FDDD156
       for <[email protected]>; Wed, 19 Nov 2003 11:14:32 -0500 (EST)
Received: from mail.astro.princeton.edu ([127.0.0.1])
by localhost (mercury.astro.princeton.edu [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 20407-04 for <[email protected]>;
Wed, 19 Nov 2003 11:14:31 -0500 (EST)
Received: from xanadu (xanadu [128.112.24.13])
       (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
       (No client certificate requested)
       by mail.astro.princeton.edu (Postfix) with ESMTP id D6D21DCD12
       for <[email protected]>; Wed, 19 Nov 2003 11:14:31 -0500 (EST)
Message-Id: <Pine.LNX.4.44.0311191109550.30269-100000@xanadu.astro.Princeton.EDU>
Date: Wed, 19 Nov 2003 11:14:31 -0500 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Huston <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Feature request
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_LONG_SPARSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __TO_MALFORMED_2, __USER_AGENT_PINE'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hey folks, just a quick feature request when someone has the time and
inclination (I doubt I will anytime soon, which is why it's not a patch being
posted instead :> )

I use Pine to connect to an IMAP server, and from home I tend to use my OS X
"Mail" program as well; we also have a webmail system setup for users here
too.  Of the three, Pine is the only one that does not offer a "Move deleted
messages to trash" type of feature, while the other two give the option as
well as a way to specify the name of the trash folder.

Would this be something easy to implement?  I searched the archives and have
not seen anyone else ask for it, so it may not be a highly requested feature,
but for someone like me who has been using Pine for many years it would be
easier to know that after marking a bunch of messages, "adx" would have the
same effect as "asTrash<CR>" and be fewer keystrokes.

Thanks!

--
Steve Huston - Unix Systems Admin, 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 [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 19 Nov 2003 09:07:54 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJH7nNL024148;
       Wed, 19 Nov 2003 09:07:49 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJH7lpd010154
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 19 Nov 2003 09:07:47 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAJH7U1r014358;
       Wed, 19 Nov 2003 09:07:30 -0800
Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJH6euL026362
       for <[email protected]>; Wed, 19 Nov 2003 09:06:40 -0800
Received: from msgdirector2.onetel.net.uk (msgdirector2.onetel.net.uk [212.67.96.149])
       by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAJH6c3N018720
       for <[email protected]>; Wed, 19 Nov 2003 09:06:39 -0800
Received: from async110-18.nas.onetel.net.uk (async110-18.nas.onetel.net.uk [212.67.114.110])
       by msgdirector2.onetel.net.uk (Mirapoint Messaging Server MOS 3.3.6-GR)
       with ESMTP id AOE99120;
       Wed, 19 Nov 2003 17:06:33 GMT
Message-Id: <[email protected]>
Date: Wed, 19 Nov 2003 17:06:50 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Nancy McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Feature request
In-Reply-To: <Pine.LNX.4.44.0311191109550.30269-100000@xanadu.astro.Princeton.EDU>
References: <Pine.LNX.4.44.0311191109550.30269-100000@xanadu.astro.Princeton.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Message-Flag: Worried about bugs & viruses? Switch to Mac/Unix/PC Pine - info @ www.ii.com
X-Uwash-Spam: Gauge=I, Probability=1%, Report='REFERENCES 0, SIGNATURE_SHORT_DENSE -0.301, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 19 Nov 2003 Steve Huston ([email protected]) wrote:
> ...
> Of the three, Pine is the only one that does not offer a "Move deleted
> messages to trash" type of feature, while the other two give the option as
> well as a way to specify the name of the trash folder.
>
> Would this be something easy to implement?  I searched the archives and have
> not seen anyone else ask for it, so it may not be a highly requested feature,
> but for someone like me who has been using Pine for many years it would be
> easier to know that after marking a bunch of messages, "adx" would have the
> same effect as "asTrash<CR>" and be fewer keystrokes.


I talk about some possible workarounds for this on my Power Pine
page in the section "Saving Your Trash" which is here:

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

Since you use multiple IMAP clients, you could set
expunge-only-manually and then let the other IMAP clients move
them to the Trash mailbox.

I have a related wish in my Pine Wish List, namely

* Support for RFC-2359, IMAP4 UIDPLUS extension, which would
 allow users to expunge some -- but not all -- messages that
 are marked for deletion in a mailbox.

This and other of my Pine wishes are here:

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

--
Nancy McGough
Infinite Ink ~ <http://www.ii.com>
Deflexion & Reflexion ~ <http://deflexion.com>

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 20 Nov 2003 02:59:16 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAKAxGNL001161;
       Thu, 20 Nov 2003 02:59:16 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAKAxE3F017632
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 20 Nov 2003 02:59:14 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAKAx3op013712;
       Thu, 20 Nov 2003 02:59:04 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAKAw2uL023750
       for <[email protected]>; Thu, 20 Nov 2003 02:58:02 -0800
Received: from msgdirector4.onetel.net.uk (msgdirector4.onetel.net.uk [212.67.96.160])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAKAvvnI004049
       for <[email protected]>; Thu, 20 Nov 2003 02:58:01 -0800
Received: from 213-78-81-235.friaco.onetel.net.uk (213-78-81-235.friaco.onetel.net.uk [213.78.81.235])
       by msgdirector4.onetel.net.uk (Mirapoint Messaging Server MOS 3.3.6-GR)
       with ESMTP id BHB75968;
       Thu, 20 Nov 2003 10:57:52 GMT
Message-Id: <[email protected]>
Date: Thu, 20 Nov 2003 10:58:10 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Nancy McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: snarfing via maildrop loses status flags - bug or feature?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Technical Discussion Forum <[email protected]>
X-Message-Flag: Worried about bugs & viruses? Switch to Mac/Unix/PC Pine - info @ www.ii.com
X-Uwash-Spam: Gauge=II, Probability=2%, Report='SIGNATURE_LONG_DENSE -3.127'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

When I use a maildrop to snarf messages, the status info (Read,
Flagged, Answered, etc.) is lost. I have not tested this with all
types of MaildropFolder/DestinationFolder combinations but I know
that this happens when both the MaildropFolder and
DestinationFolder are local mailboxes being accessed by local
file system calls (rather than POP, IMAP, or NNTP), i.e.:

local box -> local box

Before I spend time testing this with other combinations, most
notably

IMAP box -> IMAP box
IMAP box -> local box
local box -> IMAP box

I have a question: Are the status flags supposed to be preserved
during the snarf?

Thanks,
Nancy

--
Nancy McGough
Infinite Ink ~ <http://www.ii.com>
Deflexion & Reflexion ~ <http://deflexion.com>
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 20 Nov 2003 17:37:46 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1b1NL002218;
       Thu, 20 Nov 2003 17:37:01 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1ax5B010359
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 20 Nov 2003 17:37:00 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAL1aoFe010970;
       Thu, 20 Nov 2003 17:36:50 -0800
Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1WxuL030558
       for <[email protected]>; Thu, 20 Nov 2003 17:33:00 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1WwPH004504
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
       for <[email protected]>; Thu, 20 Nov 2003 17:32:58 -0800
Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1Wv3F014598
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Thu, 20 Nov 2003 17:32:57 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1WuR5003789;
       Thu, 20 Nov 2003 17:32:56 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAL1WuSS013217
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
       Thu, 20 Nov 2003 17:32:56 -0800
Message-Id: <[email protected]>
Date: Thu, 20 Nov 2003 17:32:56 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Hubert <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine News Group <[email protected]>
X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='REFERENCES 0, IN_REP_TO -0.847'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

James,
 Thanks very much for taking the time to compile it and send the debug
file. Here's a simple patch that should fix this problem. It will be
included in the next pine. Thanks!

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

*** other.c.dist        Thu Nov 20 17:22:00 2003
--- other.c.new Thu Nov 20 17:22:43 2003
***************
*** 13486,13505 ****
--- 13486,13507 ----
           if(rtype == 'f')
             defpat->patgrp->fldr_type = FLDR_SPECIFIC;

           defpat->patgrp->folder = string_to_pattern(s);
           fs_give((void **)&s);
       }
     }

     role_type_print(title, "ADD NEW %sRULE", rflags);

+     opt_screen = NULL;
+
     if(role_config_edit_screen(ps, defpat, title, rflags,
                              &newpat) == 1 && newpat){

       if(ps->never_allow_changing_from && newpat->action &&
          newpat->action->from)
           q_status_message(SM_ORDER|SM_DING, 3, 7,
       "Site policy doesn't allow changing From address so From is ignored");

       if(rflags & ROLE_DO_ROLES && newpat->patgrp && newpat->patgrp->nick){
           PAT_S *pat;

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 21 Nov 2003 04:04:22 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALC3aNL021418;
       Fri, 21 Nov 2003 04:03:36 -0800
Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALC3X3F030464
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Fri, 21 Nov 2003 04:03:34 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hALC3Nop015392;
       Fri, 21 Nov 2003 04:03:24 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALC0wuL020054
       for <[email protected]>; Fri, 21 Nov 2003 04:00:58 -0800
Received: from tx1.oucs.ox.ac.uk (tx1.oucs.ox.ac.uk [129.67.1.167])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALC0unI016427
       for <[email protected]>; Fri, 21 Nov 2003 04:00:57 -0800
Received: from scan1.oucs.ox.ac.uk ([129.67.1.166] helo=localhost)
       by tx1.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AN9y3-0001fT-IX
       for [email protected]; Fri, 21 Nov 2003 12:00:55 +0000
Received: from rx1.oucs.ox.ac.uk ([129.67.1.165])
by localhost (scan1.oucs.ox.ac.uk [129.67.1.166]) (amavisd-new, port 25)
with ESMTP id 06321-03 for <[email protected]>;
Fri, 21 Nov 2003 12:00:55 +0000 (GMT)
Received: from crow.linux.ox.ac.uk ([163.1.2.97])
       by rx1.oucs.ox.ac.uk with esmtp (Exim 4.20)
       id 1AN9y3-0001fN-5C; Fri, 21 Nov 2003 12:00:55 +0000
Message-Id: <[email protected]>
Date: Fri, 21 Nov 2003 12:00:55 +0000 (GMT)
Reply-To: [email protected]
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: James Cummings <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Config file not changeable, can't change options or settings
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Steve Hubert <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Uwash-Spam: Gauge=II, Probability=2%, Report='REFERENCES 0, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 20 Nov 2003, Steve Hubert wrote:

> James,
>   Thanks very much for taking the time to compile it and send the debug
> file. Here's a simple patch that should fix this problem. It will be
> included in the next pine. Thanks!

That change has fixed the problem (or at least I couldn't duplicated it
in about 10 attempts).  Thanks very much for the prompt help.  Those
running the systems don't want to recompile it, so I've just stuck
the binary in my own ~/bin directory and will live with that until
they upgrade.

many thanks,
-James

>
> Steve Hubert <[email protected]>
> Networks and Distributed Computing, Univ. of Washington, Seattle
>
> *** other.c.dist      Thu Nov 20 17:22:00 2003
> --- other.c.new       Thu Nov 20 17:22:43 2003
> ***************
> *** 13486,13505 ****
> --- 13486,13507 ----
>           if(rtype == 'f')
>             defpat->patgrp->fldr_type = FLDR_SPECIFIC;
>
>           defpat->patgrp->folder = string_to_pattern(s);
>           fs_give((void **)&s);
>       }
>       }
>
>       role_type_print(title, "ADD NEW %sRULE", rflags);
>
> +     opt_screen = NULL;
> +
>       if(role_config_edit_screen(ps, defpat, title, rflags,
>                              &newpat) == 1 && newpat){
>
>       if(ps->never_allow_changing_from && newpat->action &&
>          newpat->action->from)
>           q_status_message(SM_ORDER|SM_DING, 3, 7,
>         "Site policy doesn't allow changing From address so From is ignored");
>
>       if(rflags & ROLE_DO_ROLES && newpat->patgrp && newpat->patgrp->nick){
>           PAT_S *pat;
>


---
Dr James Cummings, Oxford Text Archive, [email protected]

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 24 Nov 2003 14:47:02 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOMl1NL015093;
       Mon, 24 Nov 2003 14:47:01 -0800
Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOMkx5B024593
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Mon, 24 Nov 2003 14:47:00 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAOMklAk011316;
       Mon, 24 Nov 2003 14:46:47 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOMiIuL032994
       for <[email protected]>; Mon, 24 Nov 2003 14:44:18 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOMiHnJ002948
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
       for <[email protected]>; Mon, 24 Nov 2003 14:44:18 -0800
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
       by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOMiHXT026584
       for <[email protected]>; Mon, 24 Nov 2003 14:44:17 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
       (authenticated bits=0)
       by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOMiGSS000918
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
       for <[email protected]>; Mon, 24 Nov 2003 14:44:16 -0800
Message-Id: <[email protected]>
Date: Mon, 24 Nov 2003 14:44:16 -0800 (PST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Steve Hubert <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: snarfing via maildrop loses status flags - bug or feature?
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Uwash-Spam: Gauge=III, Probability=3%, Report='REFERENCES 0, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> [...]
>
> Before I spend time testing this with other combinations, most
> notably
>
>  IMAP box -> IMAP box
>  IMAP box -> local box
>  local box -> IMAP box
>
> I have a question: Are the status flags supposed to be preserved
> during the snarf?
>
> Thanks,
> Nancy

This is working as designed. All state is lost when the copy is made. We
didn't have any strong reasons for doing it that way, it just seemed like
the right thing to do to have the messages be New after they were snarfed
from the mail drop. What is it you are doing that would make use of the
state? Thanks.

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

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 26 Nov 2003 05:27:53 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQDRrNL004604;
       Wed, 26 Nov 2003 05:27:53 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQDRp3F003740
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 26 Nov 2003 05:27:51 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAQDReFe005134;
       Wed, 26 Nov 2003 05:27:41 -0800
Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQDQduL034788
       for <[email protected]>; Wed, 26 Nov 2003 05:26:39 -0800
Received: from msgdirector1.onetel.net.uk (msgdirector1.onetel.net.uk [212.67.96.148])
       by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQDQb9s019247
       for <[email protected]>; Wed, 26 Nov 2003 05:26:38 -0800
Received: from 213-78-90-192.friaco.onetel.net.uk (213-78-90-192.friaco.onetel.net.uk [213.78.90.192])
       by msgdirector1.onetel.net.uk (Mirapoint Messaging Server MOS 3.3.6-GR)
       with ESMTP id AOL68466;
       Wed, 26 Nov 2003 13:26:31 GMT
Message-Id: <[email protected]>
Date: Wed, 26 Nov 2003 13:26:52 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Nancy McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: snarfing via maildrop loses status flags - bug or feature?
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Message-Flag: Worried about bugs & viruses? Switch to Mac/Unix/PC Pine - info @ www.ii.com
X-Uwash-Spam: Gauge=I, Probability=1%, Report='REFERENCES 0, SIGNATURE_SHORT_DENSE -0.301, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 24 Nov 2003 Steve Hubert ([email protected]) wrote:
> >
> > I have a question: Are the status flags supposed to be preserved
> > during the snarf?
>
> This is working as designed. All state is lost when the copy is made. We
> didn't have any strong reasons for doing it that way, it just seemed like
> the right thing to do to have the messages be New after they were snarfed
> from the mail drop. What is it you are doing that would make use of the
> state? Thanks.


Well I like having the messages that are snarfed marked Recent
and I'm not suggesting that you change that but I'd definitely
like to have the other status flags preserved, namely:

Read (aka Seen, sometimes aka 'Not New')
Answered
Important

I can think of a lot of scenarios where this makes sense, for
example:

1] You have a remote IMAP-accessible maildrop provided by your
mobile phone company. When you are out and about you access these
messages with your mobile phone. You reply to some, mark some
important, leave some unread. When you get back to trusty pine,
you snarf those messages to your long-term message store location
(either local or another IMAP server).

2] Your university's IMAP server does not support procmail so you
route all your messages to a machine that you've set up with
procmail, spamassassin, virus snaggers, etc. Procmail sorts the
messages into blue, green, yellow, and red mailboxes (or whatever
you call them). Then you use your local mail clients to deal with
these mailboxes (again reading, answering, and flagging some
messages). Then you use Pine's maildrop feature to snarf your
green and blue mailboxes and put them on your University's IMAP
server because they have a groovy web-based front end to their
IMAP server that can only be used with mailboxes that are on the
University's IMAP server. [Note that this is a real scenario that
I've been discussing in private email with an old-time Unix geek
that I've know (electronically) since the good old days of the
early 1990s.]

3] You like your archived mailboxes to be very large, i.e.,
thousands of messages, but you want to be able to deal with Recent
messages quickly. So you set up a two-tier snarf process that
looks like this in your incoming-folder list.

incoming-folders=whatever,
 #move -cmp =cmp
 #move {usenet.server/nntp}#news.comp.mail.pine -cmp
 etc

The first #move command moves all the messages in the -cmp
mailbox to the =cmp mailbox. The next #move command moves all the
messages in the comp.mail.pine Usenet newsgroup to the (now
empty) -cmp mailbox. You then read, reply to, and flag some these
messages. The next time you use TAB to cycle through your
incoming-folders list, this two-tiered snarf is repeated.
[BTW, I do this!]


In all three of these scenarios, it makes sense to maintain the
status flags. I actually cannot think of a scenario where you
would want to lose this information.

I hope this makes sense,
Thanks!
Nancy

--
Nancy McGough
Infinite Ink ~ <http://www.ii.com>
Deflexion & Reflexion ~ <http://deflexion.com>

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 26 Nov 2003 10:22:19 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQIMINL015655;
       Wed, 26 Nov 2003 10:22:18 -0800
Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165])
       by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQIMG5B004551
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 26 Nov 2003 10:22:16 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAQIM6Fe015246;
       Wed, 26 Nov 2003 10:22:06 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQILDuL033398
       for <[email protected]>; Wed, 26 Nov 2003 10:21:13 -0800
Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11])
       by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQILBKL014467
       for <[email protected]>; Wed, 26 Nov 2003 10:21:12 -0800
Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11])
       by lerami.lerctr.org (8.12.10/8.12.10/20030923) with ESMTP id hAQIL3Bx004638
       for <[email protected]>; Wed, 26 Nov 2003 12:21:04 -0600 (CST)
Message-Id: <[email protected]>
Date: Wed, 26 Nov 2003 12:21:03 -0600 (CST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Larry Rosenman <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: how to get PINE to go to the FIRST new message?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
X-Uwash-Spam: Gauge=II, Probability=2%, Report='SIGNATURE_LONG_DENSE -3.127'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Excuse me if this has been answered before, but I just joined the
list, and didn't see it on the FAQ list.

I use pine when I'm out of town and accessing my IMAP mailboxes.

I'd like to have pine go to the first (lowest numbered) "NEW" message
in the folder when I pick a folder.

How can I do this (if at all)?

Thanks!
(4.58 if it matters).

LER


--
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: [email protected]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ???  0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 26 Nov 2003 10:47:22 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140])
       by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQIlGNL017653;
       Wed, 26 Nov 2003 10:47:16 -0800
Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167])
       by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQIlC3F014531
       (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
       Wed, 26 Nov 2003 10:47:13 -0800
Received: from host (lists.u.washington.edu [140.142.56.13])
       by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAQIkw1r004968;
       Wed, 26 Nov 2003 10:46:59 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
       by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQIkHuL034698
       for <[email protected]>; Wed, 26 Nov 2003 10:46:18 -0800
Received: from holly.csn.ul.ie (holly.csn.ul.ie [136.201.105.4])
       by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAQIkGKC018276
       for <[email protected]>; Wed, 26 Nov 2003 10:46:17 -0800
Received: from skynet.csn.ul.ie (skynet [136.201.105.2])
       by holly.csn.ul.ie (Postfix) with ESMTP id 82B439374A
       for <[email protected]>; Wed, 26 Nov 2003 18:46:15 +0000 (Eire)
Received: by skynet.csn.ul.ie (Postfix, from userid 2542)
       id 3A5A5E7AF; Wed, 26 Nov 2003 18:46:15 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
       by skynet.csn.ul.ie (Postfix) with ESMTP id 31E467468
       for <[email protected]>; Wed, 26 Nov 2003 18:46:15 +0000 (GMT)
Message-Id: <Pine.LNX.4.58.0311261842490.21094@skynet>
Date: Wed, 26 Nov 2003 18:46:15 +0000 (GMT)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Shane Mitchell <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Collapsing / Expanding all threads in a mailbox
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info mailing list <[email protected]>
X-X-Sender: fragile@skynet
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_LONG_SPARSE -0.304'
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello,

is there a command in Pine to collapse/expand all threads in a mailbox,
when the current Sort view is threaded?

Thanks

--

Shane Mitchell -x- fragile_at_skynet_dot_ie -x- +353861922853

We all live in a state of ambitious poverty.
               -- Decimus Junius Juvenalis
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------