From pinedev@shiva0.cac.washington.edu Wed Dec 1 00:24:12 1999 -0800

From [email protected] Wed Dec 1 00:24:12 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 00:24:11 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA06643;
Wed, 1 Dec 1999 00:24:10 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA12202;
Wed, 1 Dec 1999 00:24:09 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id AAA17817;
Wed, 1 Dec 1999 00:22:36 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA23592
for <[email protected]>; Wed, 1 Dec 1999 00:19:21 -0800
Received: from linux.hicks.cz ([212.24.137.196])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id AAA27283
for <[email protected]>; Wed, 1 Dec 1999 00:19:18 -0800
Received: (qmail 27027 invoked by uid 1001); 1 Dec 1999 08:21:24 -0000
Received: from localhost ([email protected])
by localhost with SMTP; 1 Dec 1999 08:21:24 -0000
Message-Id: <[email protected]>
Date: Wed, 1 Dec 1999 09:21:24 +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: Jakub Chromy <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: /var/spool/mail must have 1777 protection
In-Reply-To: <Pine.SV4.4.21.9912010241190.7909-100000@piano.dptmaths.ens-cachan.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> since our /var/spool/mail has 2775 protection, pine tells us
> it MUST have 1777 protection, saying our mailbox would be
> "vulnerable". I can't see why.
>
> Could someone tell me ?

That's message from some of the mailer daemons.

# chmod 1777 /var/spool/mail/

BTW: This problem sometimes occurs, when moving /var/spool/mail/ directory
to new drive.

with regards

Jakub Chromy

Hosting CZ s.r.o. Tel: 0603 822 830
http://www.hosting.cz ICQ: 12017727
NEW: Miesto.sk http://www.miesto.sk
Operator: [email protected]

From [email protected] Wed Dec 1 01:07:58 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 01:07:57 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA07409;
Wed, 1 Dec 1999 01:07:56 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA16233;
Wed, 1 Dec 1999 01:07:55 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA18988;
Wed, 1 Dec 1999 01:05:22 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA56156
for <[email protected]>; Wed, 1 Dec 1999 01:00:51 -0800
Received: from ariane.ens-cachan.fr (ariane.ens-cachan.fr [138.231.176.4])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA12860
for <[email protected]>; Wed, 1 Dec 1999 01:00:47 -0800
Received: from piano.dptmaths.ens-cachan.fr (piano.dptmaths.ens-cachan.fr [138.231.32.2])
by ariane.ens-cachan.fr (8.8.8/jtpda-5.3.1) with ESMTP id KAA22432
; Wed, 1 Dec 1999 10:00:48 +0100 (MET)
Received: from localhost (markey@localhost)
by piano.dptmaths.ens-cachan.fr (8.9.3/jtpda-5.3.1/CL) with ESMTP id JAA08670
; Wed, 1 Dec 1999 09:56:04 +0100 (MET)
Message-Id: <Pine.SV4.4.21.9912010941540.8454-100000@piano.dptmaths.ens-cachan.fr>
Date: Wed, 1 Dec 1999 09:56:04 +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 Markey <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: /var/spool/mail must have 1777 protection
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Ariel <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 1 Dec 1999, Ariel wrote:

| 2775 would allow any user who can create a file in the spool to also
| delete any file in the spool even if they don't own the file so it's not
| safe. If you want new files to get the group of the directory (2000) at
| least do 3775. (i.e. also add 1000) so that you have the sticky bit set as
| well.
|
| Hopefully whatever group you have for the directory includes all your
| users who might use mail or you'll run into problems.

Well. Actually that's not the case. /var/spool/mail is owned by
root.mail, so that no user can create nor delete a file (except
root) because there is no user in the "mail" group. Only the "mailer
dameon" can create (or delete) a file there.

I agree 3775 is theoreticaly better, but my opinion is that 1777 is
not safe : with 1777 any user can create a file in /var/spool/mail,
thus any user could make the partition full and we would run into
troubles.

Thanx for your help.

-- Nico

From [email protected] Wed Dec 1 06:30:27 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 06:30: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA17926
for <[email protected]>; Wed, 1 Dec 1999 06:30:25 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA22273;
Wed, 1 Dec 1999 06:30:24 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA01561;
Wed, 1 Dec 1999 06:27:26 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA16834
for <[email protected]>; Wed, 1 Dec 1999 06:24:38 -0800
Received: from vision.ee.ethz.ch ([email protected] [129.132.2.211])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA32131
for <[email protected]>; Wed, 1 Dec 1999 06:24:37 -0800
Received: from buwaya.ee.ethz.ch ([email protected] [129.132.47.149])
by vision.ee.ethz.ch (8.9.3/8.9.3) with ESMTP id PAA24710
for <[email protected]>; Wed, 1 Dec 1999 15:24:35 +0100 (MET)
Received: from localhost (moetiker@localhost)
by buwaya.ee.ethz.ch (8.9.3/8.9.3) with ESMTP id PAA11942
for <[email protected]>; Wed, 1 Dec 1999 15:24:34 +0100 (MET)
Message-Id: <[email protected]>
Date: Wed, 1 Dec 1999 15:24:34 +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: Manuel Oetiker <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: fcc-name-rule in subfolder
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: buwaya.ee.ethz.ch: moetiker owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

I would like to configure pine to store all
sent mail in a subfolder sorted in files with
the name of the recipients.

like:
fcc-name-rule=[folder]/by-recipient.

Is there a way?

cheers Manuel

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

From [email protected] Wed Dec 1 07:05:54 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 07:05: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA16930
for <[email protected]>; Wed, 1 Dec 1999 07:05:53 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA22981;
Wed, 1 Dec 1999 07:05:51 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA00361;
Wed, 1 Dec 1999 07:02:48 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA14210
for <[email protected]>; Wed, 1 Dec 1999 06:58:28 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id GAA20080
for <[email protected]>; Wed, 1 Dec 1999 06:58:27 -0800
Received: (qmail 23807 invoked from network); 1 Dec 1999 14:58:27 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 1 Dec 1999 14:58:27 -0000
Message-Id: <[email protected]>
Date: Wed, 1 Dec 1999 07:59:49 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: /var/spool/mail must have 1777 protection
In-Reply-To: <Pine.SV4.4.21.9912010941540.8454-100000@piano.dptmaths.ens-cachan.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nicolas Markey <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

/var/spool/mail should be read only for "other" (whatever that changes the
last 7 to). This works fine with Pine.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Wed, 1 Dec 1999, Nicolas Markey wrote:

> On Wed, 1 Dec 1999, Ariel wrote:
>
> | 2775 would allow any user who can create a file in the spool to also
> | delete any file in the spool even if they don't own the file so it's not
> | safe. If you want new files to get the group of the directory (2000) at
> | least do 3775. (i.e. also add 1000) so that you have the sticky bit set as
> | well.
> |
> | Hopefully whatever group you have for the directory includes all your
> | users who might use mail or you'll run into problems.
>
> Well. Actually that's not the case. /var/spool/mail is owned by
> root.mail, so that no user can create nor delete a file (except
> root) because there is no user in the "mail" group. Only the "mailer
> dameon" can create (or delete) a file there.
>
> I agree 3775 is theoreticaly better, but my opinion is that 1777 is
> not safe : with 1777 any user can create a file in /var/spool/mail,
> thus any user could make the partition full and we would run into
> troubles.
>
> Thanx for your help.
>
> -- Nico
>
>

From [email protected] Wed Dec 1 09:03:14 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 09:03:13 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA18459
for <[email protected]>; Wed, 1 Dec 1999 09:03:12 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA22953;
Wed, 1 Dec 1999 09:03:10 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA23501;
Wed, 1 Dec 1999 08:53:30 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA48794
for <[email protected]>; Wed, 1 Dec 1999 08:47:21 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA17913
for <[email protected]>; Wed, 1 Dec 1999 08:47:19 -0800
Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2])
by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA16800;
Wed, 1 Dec 1999 08:47:17 -0800
Received: from D-140-142-110-185.dhcp2.washington.edu (D-140-142-110-185.dhcp2.washington.edu [140.142.110.185])
by mailhost2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA26111;
Wed, 1 Dec 1999 08:47:16 -0800
Message-Id: <Pine.WNT.4.21.9912010849390.-301587@tegdell-ndc>
Date: Wed, 1 Dec 1999 08:49:55 -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: Terry Gray <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: /var/spool/mail must have 1777 protection
In-Reply-To: <Pine.SV4.4.21.9912010941540.8454-100000@piano.dptmaths.ens-cachan.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nicolas Markey <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> I agree 3775 is theoreticaly better, but my opinion is that 1777 is
> not safe : with 1777 any user can create a file in /var/spool/mail,
> thus any user could make the partition full and we would run into
> troubles.

Nico,
I've always been curious why folks believe that 1777 is unsafe because
it allows anyone to create files... since you don't even have to have an
account on the system to fill up a mailspool (and those with accounts can
already use /var/spool/mail for temporary storage via mail software).

Can you elaborate on your view?

-teg

p.s. I believe there is a section in the release notes and also the FAQ on
why the spool directory needs to be 1777. Look for "Folder Locking".

From [email protected] Wed Dec 1 10:53:11 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 10:53:11 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA23620
for <[email protected]>; Wed, 1 Dec 1999 10:53:10 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA29395;
Wed, 1 Dec 1999 10:53:08 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA14151;
Wed, 1 Dec 1999 10:49:43 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA22256
for <[email protected]>; Wed, 1 Dec 1999 10:45:05 -0800
Received: from nautilus.shore.net (nautilus.shore.net [207.244.124.104])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAB28836
for <[email protected]>; Wed, 1 Dec 1999 10:45:04 -0800
Received: from shell3.shore.net [207.244.124.103]
by nautilus.shore.net with esmtp (Exim)
id 11tEhX-0001bo-00; Wed, 1 Dec 1999 13:42:03 -0500
Received: from ar by shell3.shore.net with local (Exim)
id 11tEhX-0005uo-00; Wed, 1 Dec 1999 13:42:03 -0500
Message-Id: <[email protected]>
Date: Wed, 1 Dec 1999 13:42:03 -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: Ariel <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: /var/spool/mail must have 1777 protection
In-Reply-To: <Pine.SV4.4.21.9912010941540.8454-100000@piano.dptmaths.ens-cachan.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: Ariel <[email protected]>
X-To: Nicolas Markey <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 1 Dec 1999, Nicolas Markey wrote:

> On Wed, 1 Dec 1999, Ariel wrote:

> | 2775 would allow any user who can create a file in the spool to also
> | delete any file in the spool even if they don't own the file so it's not
> | safe. If you want new files to get the group of the directory (2000) at
> | least do 3775. (i.e. also add 1000) so that you have the sticky bit set as
> | well.

> Well. Actually that's not the case. /var/spool/mail is owned by
> root.mail, so that no user can create nor delete a file (except
> root) because there is no user in the "mail" group. Only the "mailer
> dameon" can create (or delete) a file there.

If only your daemon can create files in the mail spool that you are
running a _severe_ risk of corrupting your users mail. In order to lock
the mail file the mail program must be able to create a <username>.lock
file, if it can't, then most likely your mail file is not locked when a
user saves his mail (expunge in pine). If that user should happen to get
mail by the daemon at that moment, both programs will try to write to the
mail file simultaneously causing major corruption. (The new message will
be interleaved with another message.)

There are a lot of warnings about running mail without lock files. Even
when you use kernel locking, it's not always reliable, and doesn't work
with NFS.

> I agree 3775 is theoreticaly better, but my opinion is that 1777 is
> not safe : with 1777 any user can create a file in /var/spool/mail,
> thus any user could make the partition full and we would run into
> troubles.

3775 is not theoretically better, it is better, if you have users in the
mail group. If not then use 3777. The fact that users can create files in
the mail spool is well known in unix, and there are tons of solutions.

Here are a few. Set it to 3775, and make any program that might do mail
setgid to mail. That way mail programs can create any file necessary in
the mail spool, while ordinary users can not. This is not perfect since
you can trick the mail program into writing things in the mail spool for
you, but it's harder, and unless someone explicitly wants to cause trouble
it won't happen.

You can run quota on the mail spool with some large limit.

One popular choice if to have a program that once a day looks for any file
with a length greater then 0, and if found, moves it into the users home
directory. (Not including the mail itself of course.) (Greater then zero
to avoid moving lock files.)

Some places put all mail files in ~/.mail instead of /var/spool/mail, if
you make this change you'll have to recompile all your mail readers.

And of course you can do what the majority of systems do, and not worry
about filling up space. After all a user can fill up /tmp and /var/tmp and
cause you just as much if not more trouble. There comes a point where you
have to trust users not be idiots. Also it's generally agreed that trying
to prevent DOS (denial of service) attacks usually hurt legitimate users
more then the attackers.

And becides, if they were trying to cause trouble, they could just make
their mail file very large.

-Ariel

From [email protected] Wed Dec 1 13:30:46 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 1 Dec 1999 13:30:46 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA28906
for <[email protected]>; Wed, 1 Dec 1999 13:30:45 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA31253;
Wed, 1 Dec 1999 13:30:43 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA27172;
Wed, 1 Dec 1999 13:26:06 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA31310
for <[email protected]>; Wed, 1 Dec 1999 13:22:28 -0800
Received: from mm01snlnto.sandia.gov (mm01snlnto.sandia.gov [132.175.109.20])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA01421
for <[email protected]>; Wed, 1 Dec 1999 13:22:23 -0800
Received: from 132.175.109.1 by mm01snlnto.sandia.gov with ESMTP (
WorldSecure Server SMTP Relay(WSS) v3.6); Wed, 01 Dec 99 14:22:20 -0700
Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190])
by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id OAA01554 for
<[email protected]>; Wed, 1 Dec 1999 14:22:21 -0700 (MST)
Message-Id: <77349FC5DC1CD211BAD900805FA7241A0877F23D-100000@ES01SNLNT>
Date: Wed, 1 Dec 1999 14:20:15 -0700
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: "Daniel Sands" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Small bug (annoyance) report
MIME-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: "Pine Discussion Forum" <[email protected]>
X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c
X-WSS-ID: 145B4E06125300-01-01
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

We are using a M$ IMAP server here. For each folder, it creates a directory
of the same name. Each month, it asks me if I want to move sent-mail to
sent-mail-MM-YY. No problem there. Then it asks if I want to delete the
previous month's sent mail. Still no problem. Then it asks if I want to
delete the corrosponding directory. If I said yes to deleting the folder, the
corrosponding directory no longer exists, so Pine then informs me to that
effect.

If Pine wants to delete a directory which corresponds to a folder, could it at
least make sure the directory still exists before asking?

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

From [email protected] Thu Dec 2 07:10:27 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 07:10:27 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA32538
for <[email protected]>; Thu, 2 Dec 1999 07:10:26 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA20214;
Thu, 2 Dec 1999 07:10:24 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA27831;
Thu, 2 Dec 1999 07:07:50 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA63254
for <[email protected]>; Thu, 2 Dec 1999 07:03:19 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA03801
for <[email protected]>; Thu, 2 Dec 1999 07:03:18 -0800
Received: (qmail 16307 invoked from network); 2 Dec 1999 15:03:18 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 2 Dec 1999 15:03:18 -0000
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 08:04:37 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: /var/spool/mail must have 1777 protection
In-Reply-To: <Pine.WNT.4.21.9912010849390.-301587@tegdell-ndc>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Terry Gray <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

It is true that if there were **absolutely no security holes** on the
system, then the permission issue would be moot. Unfortunately, this is
never the case. I don't want to describe existing security holes, but
they do exist, and opening up permissions in a mail related directory is
one of the most dangerous things that you can do, as email is the source
of the majority of security breaches.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Wed, 1 Dec 1999, Terry Gray wrote:

>
> > I agree 3775 is theoreticaly better, but my opinion is that 1777 is
> > not safe : with 1777 any user can create a file in /var/spool/mail,
> > thus any user could make the partition full and we would run into
> > troubles.
>
> Nico,
> I've always been curious why folks believe that 1777 is unsafe because
> it allows anyone to create files... since you don't even have to have an
> account on the system to fill up a mailspool (and those with accounts can
> already use /var/spool/mail for temporary storage via mail software).
>
> Can you elaborate on your view?
>
> -teg
>
> p.s. I believe there is a section in the release notes and also the FAQ on
> why the spool directory needs to be 1777. Look for "Folder Locking".
>
>
>

From [email protected] Thu Dec 2 09:56:11 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 09:56:11 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA02644;
Thu, 2 Dec 1999 09:56:09 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA27731;
Thu, 2 Dec 1999 09:56:09 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA15596;
Thu, 2 Dec 1999 09:52:50 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA10264
for <[email protected]>; Thu, 2 Dec 1999 09:46:11 -0800
Received: from atlantis.bus.ucf.edu (IDENT:[email protected] [132.170.121.8])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA16541
for <[email protected]>; Thu, 2 Dec 1999 09:46:10 -0800
Received: from localhost (david@localhost)
by atlantis.bus.ucf.edu (8.9.3/8.9.3) with ESMTP id MAA14136
for <[email protected]>; Thu, 2 Dec 1999 12:47:24 -0500
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 12:47:24 -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: David Collantes <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Tokens
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Howdy!

I have Pine 4.20 running (soon to be upgraded to 4.21) and I have set OM#
as the reply indent string. On the Help I saw that I could use several
tokens also. I have the allow editing of the string (^R), but when I type
_FROM_ to be used as the string, no replacement is made, in other words,
the message will read at the recipient client:

_FROM_ In here the test of the message being replied.
_FROM_ In here the test of the message being replied.
_FROM_ In here the test of the message being replied.

What I am doing wrong? Is that a bug or I am missing something? What
should I do to be able to use the tokens?

Cheers,

,----------------------------------.,-----------------------------------.
| David Collantes || email: [email protected] |
| Senior Systems Administrator, || phone: (407) 823-3418 |
| Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
`----------------------------------'`-----------------------------------'

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

From [email protected] Thu Dec 2 10:02:39 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 10:02: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01400;
Thu, 2 Dec 1999 10:02:38 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA27935;
Thu, 2 Dec 1999 10:02:37 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA16142;
Thu, 2 Dec 1999 09:58:49 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA84686
for <[email protected]>; Thu, 2 Dec 1999 09:52:44 -0800
Received: from atlantis.bus.ucf.edu (IDENT:[email protected] [132.170.121.8])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26700
for <[email protected]>; Thu, 2 Dec 1999 09:52:43 -0800
Received: from localhost (david@localhost)
by atlantis.bus.ucf.edu (8.9.3/8.9.3) with ESMTP id MAA14366
for <[email protected]>; Thu, 2 Dec 1999 12:53:57 -0500
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 12:53:57 -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: David Collantes <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Suggestion
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is a suggestion for the Pine Development group. I know I can search
the subject of messages while in a Pine "folder" but it will be great to
have a global search that will search subject and body of messages in all
your mailboxes and on an specific mailbox. Would that be a planned
feature?

Cheers,

,----------------------------------.,-----------------------------------.
| David Collantes || email: [email protected] |
| Senior Systems Administrator, || phone: (407) 823-3418 |
| Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
`----------------------------------'`-----------------------------------'

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

From [email protected] Thu Dec 2 10:18:20 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 10:18:19 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01596;
Thu, 2 Dec 1999 10:18:18 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25752;
Thu, 2 Dec 1999 10:18:18 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA17205;
Thu, 2 Dec 1999 10:14:21 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA52696
for <[email protected]>; Thu, 2 Dec 1999 10:10:43 -0800
Received: from niwot.scd.ucar.edu (niwot.scd.ucar.edu [128.117.8.223])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA19894
for <[email protected]>; Thu, 2 Dec 1999 10:10:42 -0800
Received: from sedona.scd.ucar.edu (sedona.scd.ucar.edu [128.117.8.183])
by niwot.scd.ucar.edu (8.9.1a/8.9.1) with ESMTP id LAA20869;
Thu, 2 Dec 1999 11:10:42 -0700 (MST)
Received: from localhost (era@localhost)
by sedona.scd.ucar.edu (8.9.1a/8.9.1) with ESMTP id LAA01892;
Thu, 2 Dec 1999 11:10:41 -0700 (MST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 11:10:41 -0700 (MST)
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: Ed Arnold <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Collantes <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: sedona.scd.ucar.edu: era owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Sounds like you're looking for grepmail: www.cs.virginia.edu/~dwc3q

> This is a suggestion for the Pine Development group. I know I can search
> the subject of messages while in a Pine "folder" but it will be great to
> have a global search that will search subject and body of messages in all
> your mailboxes and on an specific mailbox. Would that be a planned
> feature?
>
> Cheers,
>
>
> ,----------------------------------.,-----------------------------------.
> | David Collantes || email: [email protected] |
> | Senior Systems Administrator, || phone: (407) 823-3418 |
> | Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
> `----------------------------------'`-----------------------------------'

From [email protected] Thu Dec 2 10:21:16 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 10:21:16 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA28241;
Thu, 2 Dec 1999 10:21:14 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25865;
Thu, 2 Dec 1999 10:21:14 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA15536;
Thu, 2 Dec 1999 10:18:13 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA38868
for <[email protected]>; Thu, 2 Dec 1999 10:11:43 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA04278
for <[email protected]>; Thu, 2 Dec 1999 10:11:43 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA28187
for <[email protected]>; Thu, 2 Dec 1999 10:11:43 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id MAA24476
for <[email protected]>; Thu, 2 Dec 1999 12:11:27 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 12:11:27 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, David Collantes wrote:

> This is a suggestion for the Pine Development group. I know I can search
> the subject of messages while in a Pine "folder" but it will be great to
> have a global search that will search subject and body of messages in all
> your mailboxes and on an specific mailbox. Would that be a planned
> feature?

I started asking for that a couple of years ago. I was told that Pine
4.00 would have that feature, but it actually doesn't have it (as far as I
can tell). It looks like it lets you find folders that contain certain
strings, but it doesn't pull the messages out of the folders for you.

I've basically given up on having Pine do what I need in this regard and
I've started using a perl script called grepmail. It's working very well
for me. You can look for my earlier postings on grepmail in the archive.
Just search for "grepmail".

Regards,

Mike

--
Michael B. Miller, M.S., Ph.D., M.P.E.
Department of Psychology
210 McAlester Hall
University of Missouri--Columbia
Columbia, MO 65211

Phone: (573) 882-5671
Fax: (573) 882-7710
e-mail: [email protected]
web: http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Thu Dec 2 11:37:33 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 11:37:33 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05031;
Thu, 2 Dec 1999 11:37:32 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30711;
Thu, 2 Dec 1999 11:37:31 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA14211;
Thu, 2 Dec 1999 11:25:31 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA59744
for <[email protected]>; Thu, 2 Dec 1999 11:15:15 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA11033
for <[email protected]>; Thu, 2 Dec 1999 11:15:14 -0800
Received: from alephminus1.ii.com (alephminus1.ii.com [216.44.169.226])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id OAA20331;
Thu, 2 Dec 1999 14:15:12 -0500 (EST)
Message-Id: <Pine.WNT.4.21.9912021406290.-406189@alephminus1>
Date: Thu, 2 Dec 1999 14:15:29 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-02 David Collantes <[email protected]> wrote:
> This is a suggestion for the Pine Development group. I know I can search
> the subject of messages while in a Pine "folder" but it will be great to
> have a global search that will search subject and body of messages in all
> your mailboxes and on an specific mailbox. Would that be a planned
> feature?

Pine can already do this.

[1] To search the current mailbox type:

; T A text CR

You'll be presented with a list of *messages* that contain the
search text anywhere in the header or body.

[2] To search a group of mailboxes, first go to the Folder List
that has the group of mailboxes you want to search, then type:

; T C text CR

You'll be presented with a list of *mailbox* that contain
messages that contain the search text. You then need to go to
each individual mailbox and do step [1] there. As someone
else said, it would be great if method [2] presented you with a
virtual mailbox with all the messages from all the mailboxes that
matched your search.

HTH,
Nancy

--
For Pine links, see http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
--= Sent via PINE 4.21: Internet News & Email for Win/Unix =--

From [email protected] Thu Dec 2 11:53:58 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 11:53:57 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05325;
Thu, 2 Dec 1999 11:53:56 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA31133;
Thu, 2 Dec 1999 11:53:55 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA15298;
Thu, 2 Dec 1999 11:41:54 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA54792
for <[email protected]>; Thu, 2 Dec 1999 11:33:19 -0800
Received: from smtp.gospelcom.net (smtp.gospelcom.net [204.253.132.6])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA20953
for <[email protected]>; Thu, 2 Dec 1999 11:33:18 -0800
Received: (qmail 9950 invoked from network); 2 Dec 1999 19:37:23 -0000
Received: from jabbok.gospelcom.net (HELO tarsus.gf.gospelcom.net) (204.253.132.4)
by smtp.gospelcom.net with SMTP; 2 Dec 1999 19:37:23 -0000
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 14:37:23 -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: Topher <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.WNT.4.21.9912021406290.-406189@alephminus1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> [1] To search the current mailbox type:
>
> ; T A text CR
>
> You'll be presented with a list of *messages* that contain the
> search text anywhere in the header or body.

One last thing, you can also Zoom (if you've got it turned on in your
setup) and it'll only show the messages that have results. Unzoom to go
back to where you were.

Topher
Tech Support
[email protected]
Gospel Communications Network

From [email protected] Thu Dec 2 11:56:30 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 11:56:30 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05277;
Thu, 2 Dec 1999 11:56:27 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA28846;
Thu, 2 Dec 1999 11:56:26 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA23940;
Thu, 2 Dec 1999 11:52:04 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA48518
for <[email protected]>; Thu, 2 Dec 1999 11:43:15 -0800
Received: from atlantis.bus.ucf.edu (IDENT:[email protected] [132.170.121.8])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA16850
for <[email protected]>; Thu, 2 Dec 1999 11:43:13 -0800
Received: from localhost (david@localhost)
by atlantis.bus.ucf.edu (8.9.3/8.9.3) with ESMTP id OAA19112;
Thu, 2 Dec 1999 14:44:09 -0500
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 14:44:09 -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: David Collantes <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.WNT.4.21.9912021406290.-406189@alephminus1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Nancy this-address-is-valid McGough wrote:

OM# On 99-12-02 David Collantes <[email protected]> wrote:
OM# > This is a suggestion for the Pine Development group. I know I can search
OM# > the subject of messages while in a Pine "folder" but it will be great to
OM#
OM# Pine can already do this.
OM#
OM# [1] To search the current mailbox type:
OM#
OM# ; T A text CR
OM#
OM# You'll be presented with a list of *messages* that contain the
OM# search text anywhere in the header or body.
OM#
OM#
OM# [2] To search a group of mailboxes, first go to the Folder List
OM# that has the group of mailboxes you want to search, then type:
OM#
OM# ; T C text CR
OM#
OM# You'll be presented with a list of *mailbox* that contain

Nancy,

I do not understand. The character ";" shows as "Not defined", no matter
where I try to use it. Could you, please, elaborate more on this? As far
as for grepmail, I could do that easy in perl, but that is not the
point. I would like to have it build in, as part of pine itself.

Thanks for the help in advance.

Cheers,

,----------------------------------.,-----------------------------------.
| David Collantes || email: [email protected] |
| Senior Systems Administrator, || phone: (407) 823-3418 |
| Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
`----------------------------------'`-----------------------------------'

From [email protected] Thu Dec 2 12:09:13 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 12:09:13 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05542;
Thu, 2 Dec 1999 12:09:12 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA29194;
Thu, 2 Dec 1999 12:09:11 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA17229;
Thu, 2 Dec 1999 12:04:45 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA87616
for <[email protected]>; Thu, 2 Dec 1999 11:51:48 -0800
Received: from niwot.scd.ucar.edu (niwot.scd.ucar.edu [128.117.8.223])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA18551
for <[email protected]>; Thu, 2 Dec 1999 11:51:48 -0800
Received: from sedona.scd.ucar.edu (sedona.scd.ucar.edu [128.117.8.183])
by niwot.scd.ucar.edu (8.9.1a/8.9.1) with ESMTP id MAA24771;
Thu, 2 Dec 1999 12:51:47 -0700 (MST)
Received: from localhost (era@localhost)
by sedona.scd.ucar.edu (8.9.1a/8.9.1) with ESMTP id MAA02293;
Thu, 2 Dec 1999 12:51:47 -0700 (MST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 12:51:47 -0700 (MST)
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: Ed Arnold <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.WNT.4.21.9912021406290.-406189@alephminus1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: sedona.scd.ucar.edu: era owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

A minor clarification: use of the ";" command requires that
enable-aggregate-command-set be in .pinerc's feature-list.
Also, it isn't clear to me that "text" can be a regular expression
(as in grepmail), do you know?

> On 99-12-02 David Collantes <[email protected]> wrote:
> > This is a suggestion for the Pine Development group. I know I can search
> > the subject of messages while in a Pine "folder" but it will be great to
> > have a global search that will search subject and body of messages in all
> > your mailboxes and on an specific mailbox. Would that be a planned
> > feature?
>
> Pine can already do this.
>
> [1] To search the current mailbox type:
>
> ; T A text CR
>
> You'll be presented with a list of *messages* that contain the
> search text anywhere in the header or body.
>
>
> [2] To search a group of mailboxes, first go to the Folder List
> that has the group of mailboxes you want to search, then type:
>
> ; T C text CR
>
> You'll be presented with a list of *mailbox* that contain
> messages that contain the search text. You then need to go to
> each individual mailbox and do step [1] there. As someone
> else said, it would be great if method [2] presented you with a
> virtual mailbox with all the messages from all the mailboxes that
> matched your search.
>
> HTH,
> Nancy

From [email protected] Thu Dec 2 12:14:46 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 12:14: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05608;
Thu, 2 Dec 1999 12:14:45 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA31761;
Thu, 2 Dec 1999 12:14:45 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA09157;
Thu, 2 Dec 1999 12:11:54 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA54784
for <[email protected]>; Thu, 2 Dec 1999 11:55:05 -0800
Received: from vax.area.com (vax41.area.com [165.90.20.41])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA09485
for <[email protected]>; Thu, 2 Dec 1999 11:55:03 -0800
Received: (qmail 19409 invoked by uid 1828); 2 Dec 1999 19:54:51 -0000
Message-Id: <Pine.GSO.4.20.9912021154320.13144-100000@vax>
Date: Thu, 2 Dec 1999 11:54:51 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Collantes <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, David Collantes wrote:
>I do not understand. The character ";" shows as "Not defined", no matter
>where I try to use it. Could you, please, elaborate more on this? As far
>as for grepmail, I could do that easy in perl, but that is not the
>point. I would like to have it build in, as part of pine itself.

You have to turn on the "Enable Aggregate Command Set" in the preferences.

From [email protected] Thu Dec 2 12:19:40 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 12:19:40 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05562;
Thu, 2 Dec 1999 12:19:38 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA31865;
Thu, 2 Dec 1999 12:19:38 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA23998;
Thu, 2 Dec 1999 12:16:09 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA46572
for <[email protected]>; Thu, 2 Dec 1999 11:59:09 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA20308
for <[email protected]>; Thu, 2 Dec 1999 11:59:02 -0800
Received: (qmail 17256 invoked from network); 2 Dec 1999 19:59:00 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 2 Dec 1999 19:59:00 -0000
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 13:00:18 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Collantes <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This looks like a command line mode for Pine. I, also, don't know how to
get into this mode.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Thu, 2 Dec 1999, David Collantes wrote:

> On Thu, 2 Dec 1999, Nancy this-address-is-valid McGough wrote:
>
> OM# On 99-12-02 David Collantes <[email protected]> wrote:
> OM# > This is a suggestion for the Pine Development group. I know I can search
> OM# > the subject of messages while in a Pine "folder" but it will be great to
> OM#
> OM# Pine can already do this.
> OM#
> OM# [1] To search the current mailbox type:
> OM#
> OM# ; T A text CR
> OM#
> OM# You'll be presented with a list of *messages* that contain the
> OM# search text anywhere in the header or body.
> OM#
> OM#
> OM# [2] To search a group of mailboxes, first go to the Folder List
> OM# that has the group of mailboxes you want to search, then type:
> OM#
> OM# ; T C text CR
> OM#
> OM# You'll be presented with a list of *mailbox* that contain
>
> Nancy,
>
> I do not understand. The character ";" shows as "Not defined", no matter
> where I try to use it. Could you, please, elaborate more on this? As far
> as for grepmail, I could do that easy in perl, but that is not the
> point. I would like to have it build in, as part of pine itself.
>
> Thanks for the help in advance.
>
> Cheers,
>
>
> ,----------------------------------.,-----------------------------------.
> | David Collantes || email: [email protected] |
> | Senior Systems Administrator, || phone: (407) 823-3418 |
> | Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
> `----------------------------------'`-----------------------------------'
>
>
>

From [email protected] Thu Dec 2 12:27:22 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 12:27: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05521;
Thu, 2 Dec 1999 12:27:20 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32025;
Thu, 2 Dec 1999 12:27:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA18551;
Thu, 2 Dec 1999 12:24:17 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA11170
for <[email protected]>; Thu, 2 Dec 1999 12:14:41 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA30318
for <[email protected]>; Thu, 2 Dec 1999 12:14:40 -0800
Received: (qmail 20292 invoked from network); 2 Dec 1999 20:14:39 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 2 Dec 1999 20:14:39 -0000
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 13:15:57 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.GSO.4.20.9912021154320.13144-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: [email protected]
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Thanks, now it works.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Thu, 2 Dec 1999 [email protected] wrote:

> On Thu, 2 Dec 1999, David Collantes wrote:
> >I do not understand. The character ";" shows as "Not defined", no matter
> >where I try to use it. Could you, please, elaborate more on this? As far
> >as for grepmail, I could do that easy in perl, but that is not the
> >point. I would like to have it build in, as part of pine itself.
>
> You have to turn on the "Enable Aggregate Command Set" in the preferences.
>

From [email protected] Thu Dec 2 13:04:25 1999 -0800
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 13:04:25 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA26090;
Thu, 2 Dec 1999 13:04:24 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA30602;
Thu, 2 Dec 1999 13:04:23 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA12343;
Thu, 2 Dec 1999 13:00:57 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA16700
for <[email protected]>; Thu, 2 Dec 1999 12:56:19 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA06216
for <[email protected]>; Thu, 2 Dec 1999 12:56:18 -0800
Received: from alephminus1.ii.com (alephminus1.ii.com [216.44.169.226])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id PAA21420;
Thu, 2 Dec 1999 15:56:17 -0500 (EST)
Message-Id: <Pine.WNT.4.21.9912021552210.-406189@alephminus1>
Date: Thu, 2 Dec 1999 15:56:33 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-02 Ed Arnold <[email protected]> wrote:
> A minor clarification: use of the ";" command requires that
> enable-aggregate-command-set be in .pinerc's feature-list.
> Also, it isn't clear to me that "text" can be a regular expression
> (as in grepmail), do you know?

It's straight text like all text matching in pine (including
role, filter, and score patterns). Regular expression matching
would be great though!

-Nancy

--
For Pine links, see http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
--= Sent via PINE 4.21: Internet News & Email for Win/Unix =--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 13:27:47 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA07379;
Thu, 2 Dec 1999 13:27:46 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA31246;
Thu, 2 Dec 1999 13:27:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA22677;
Thu, 2 Dec 1999 13:23:26 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA38236
for <[email protected]>; Thu, 2 Dec 1999 13:18:53 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA02870
for <[email protected]>; Thu, 2 Dec 1999 13:18:53 -0800
Received: from goedel1.math.washington.edu ([email protected] [128.95.224.2])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id NAA26977;
Thu, 2 Dec 1999 13:18:50 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912021232260.5488-100000@goedel1.math.washington.edu>
Date: Thu, 2 Dec 1999 13:18:50 -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 L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Mike Miller ([email protected]) wrote today:

:) I started asking for that a couple of years ago. I was told that Pine
:) 4.00 would have that feature, but it actually doesn't have it (as far as I
:) can tell). It looks like it lets you find folders that contain certain
:) strings, but it doesn't pull the messages out of the folders for you.
:)
:) I've basically given up on having Pine do what I need in this regard and
:) I've started using a perl script called grepmail. It's working very well
:) for me. You can look for my earlier postings on grepmail in the archive.
:) Just search for "grepmail".
:)

I am not sure if Pine will ever be able to do something like this,
certainly I do not see how to hack the code to do something like this. It
may be possible, but it does not look obvious, not for me at least. Let's
say to put things fixed that you wanted to look for messages with certain
specific From: line in all your folders in a certain collection.

Now let us say you did the select that Nancy described before. Because
of the way Pine works today, the only possible output would be to show you
an index in a "folder index", so you would have to create a "fake" folder
with "fake" messages and open them from there (aargh, this sounds awful to
display on screen and program)

Another solution would be to make a special display, something like

[Folder1]
MSG 1 Selected
MSG 2 Selected

[Folder2]
MSG 1 Selected
MSG 2 Selected

etc, and be able to open every message from the same screen. That would be
a lot of work though. I think you would also break the stream here,
opening and closing folders without displaying the index... I really don't
see how to do it without breaking much things in pine.

Anyone has ideas of how something like this should be done, what is what
you think is the outoput pine should give, to see if it is possible to
implement it..

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 13:50:05 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA07638;
Thu, 2 Dec 1999 13:50:04 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA01459;
Thu, 2 Dec 1999 13:50:03 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA00212;
Thu, 2 Dec 1999 13:46:10 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA43064
for <[email protected]>; Thu, 2 Dec 1999 13:40:55 -0800
Received: from vax.area.com (vax117.area.com [165.90.20.117])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA07346
for <[email protected]>; Thu, 2 Dec 1999 13:40:53 -0800
Received: (qmail 29680 invoked by uid 1828); 2 Dec 1999 21:40:50 -0000
Message-Id: <Pine.GSO.4.20.9912021338100.13144-100000@vax>
Date: Thu, 2 Dec 1999 13:40:50 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: tab go to end if no new messages?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Ok, I amit this is complete laziness, but it seems to me that if
there are no new messages, TAB should just (optionally?) go to the
end of the message list.

As a person who has 1123 messages in one of my mailboxes and 867 in another,
hitting tab is more convenient than paging through a gazillion pages (out
of habit, I usually end up hitting space a bunch of times before realizing
I'm TENS of pages away from the end), or typing in the message #.

Speaking of paging, why does it take a long time sometimes? Especially when
going back a page.

--
[email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 13:58:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA07898;
Thu, 2 Dec 1999 13:58:23 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA32117;
Thu, 2 Dec 1999 13:58:23 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA24614;
Thu, 2 Dec 1999 13:55:01 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA56164
for <[email protected]>; Thu, 2 Dec 1999 13:51:13 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA17389
for <[email protected]>; Thu, 2 Dec 1999 13:51:12 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id PAA25417;
Thu, 2 Dec 1999 15:50:57 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 15:50:57 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.WNT.4.21.9912021552210.-406189@alephminus1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Nancy this-address-is-valid McGough wrote:

> On 99-12-02 Ed Arnold <[email protected]> wrote:
> > Also, it isn't clear to me that "text" can be a regular expression
> > (as in grepmail), do you know?
>
> It's straight text like all text matching in pine (including
> role, filter, and score patterns). Regular expression matching
> would be great though!

I agree. Just a clarification: By "straight text" you mean that it is
case insensitive.

If it is too hard to implement regular expression matching, maybe the Pine
team can implement a form of case-sensitivity where upper case letters in
the search string can only be matched by upper-case letters in the message
or folder, but lower case letters in the search string can be matched by
either upper or lower case. That would be a useful feature. We could
have an "Enable case sensitivity in searches" option.

Another *great* feature would be to allow searches of the message body
(excluding the message header). Here's an example: I get a bunch of
messages from an e-mail list and I don't want to read them all, but I want
to see if any of them refer to my earlier posting. If I search "Text All"
for messages containing 'miller' *all* of the messages will be selected
because all of them were sent to me (mbmiller) and 'mbmiller' is therefore
in the header of every message. If I could search the message body I
would find messages where they mention "Mike Miller" or whatever. Doesn't
that seem like it would be potentially very useful.

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 14:11:19 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA07745;
Thu, 2 Dec 1999 14:11:18 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA32484;
Thu, 2 Dec 1999 14:11:17 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA01641;
Thu, 2 Dec 1999 14:08:07 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA93830
for <[email protected]>; Thu, 2 Dec 1999 14:04:06 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA02623
for <[email protected]>; Thu, 2 Dec 1999 14:04:05 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id QAA25494
for <[email protected]>; Thu, 2 Dec 1999 16:04:04 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 16:04: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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.OSF.4.21.9912021232260.5488-100000@goedel1.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Eduardo Chappa L. wrote:

> *** Mike Miller ([email protected]) wrote today:
>
> :) I started asking for that a couple of years ago. I was told that Pine
> :) 4.00 would have that feature, but it actually doesn't have it (as far as I
> :) can tell). It looks like it lets you find folders that contain certain
> :) strings, but it doesn't pull the messages out of the folders for you.
> :)
> :) I've basically given up on having Pine do what I need in this regard and
> :) I've started using a perl script called grepmail. It's working very well
> :) for me. You can look for my earlier postings on grepmail in the archive.
> :) Just search for "grepmail".
>
> I am not sure if Pine will ever be able to do something like this,
[snip]
> Now let us say you did the select that Nancy described before. Because
> of the way Pine works today, the only possible output would be to show you
> an index in a "folder index", so you would have to create a "fake" folder
> with "fake" messages and open them from there (aargh, this sounds awful to
> display on screen and program)

My thinking was that Pine should make a fake folder. With the way things
work now, we can select within folders and 'Apply' various manipulations
(Save, Extract, Delete, etc.). I recommend that we give up on the Apply
feature for multi-folder searches (because it's probably too hard to work
it out). Let's just do a mailgrep kind of thing where we search for
messages in multiple folders, then pipe the output to a file (folder),
then go to the index of that folder. From there we can do further
Selection and Apply commands, but we are not operating on the original
messages, just on copies of those messages. The new folder could have a
name like TEMPFOLDER or maybe the user should be prompted for a name.

I recommended once before that it would be nice if Pine could run perl
scripts to do this sort of thing. It seems like it would be easy to add a
feature such as "Enable perl grepmail" and allow users to run grepmail
from within Pine. You might even add "path to perl" and "path to
grepmail" items to the pinerc.

Regards,

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 14:17:13 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA28318;
Thu, 2 Dec 1999 14:17:11 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA32663;
Thu, 2 Dec 1999 14:17:11 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA02128;
Thu, 2 Dec 1999 14:14:21 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA86870
for <[email protected]>; Thu, 2 Dec 1999 14:09:45 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA05480
for <[email protected]>; Thu, 2 Dec 1999 14:09:44 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id QAA25508
for <[email protected]>; Thu, 2 Dec 1999 16:09:43 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 16:09:43 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: tab go to end if no new messages?
In-Reply-To: <Pine.GSO.4.20.9912021338100.13144-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999 [email protected] wrote:

> Ok, I amit this is complete laziness, but it seems to me that if
> there are no new messages, TAB should just (optionally?) go to the
> end of the message list.

Sounds good.

> As a person who has 1123 messages in one of my mailboxes and 867 in
> another, hitting tab is more convenient than paging through a
> gazillion pages (out of habit, I usually end up hitting space a bunch
> of times before realizing I'm TENS of pages away from the end), or
> typing in the message #.

Do you know about Ctrl-W Ctrl-V ? That pattern of keystrokes will jump to
the end. (Hit Ctrl-W and look at the options, some are relatively new.)

> Speaking of paging, why does it take a long time sometimes? Especially when
> going back a page.

Slow computer, not enough RAM, huge attachments in messages, I don't know!
:-)

Regards,

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 14:38:01 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA08231;
Thu, 2 Dec 1999 14:37:59 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA00524;
Thu, 2 Dec 1999 14:37:59 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA27010;
Thu, 2 Dec 1999 14:32:09 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA47468
for <[email protected]>; Thu, 2 Dec 1999 14:25:25 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA16144
for <[email protected]>; Thu, 2 Dec 1999 14:25:23 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id QAA25653
for <[email protected]>; Thu, 2 Dec 1999 16:25:22 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 16:25:22 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: keybindings and "previous word"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I do love Pine and I don't mean to complain!

Anyway, am I missing something or is there still no way to move back one
word when editing messages in pine? I asked before for some emacs
keystroke options, but got no reply.

Right now I can go to "Next word" with Ctrl-@, but there is no way to go
back a word. Is that weird, or is it just me?? :-) Sometimes I go to
the beginning of the line, then going forward a word at a time!

If you can't do it with Alt-B (a la emacs), why not use Ctrl-# (it's right
next to Ctrl-@)??

Right now, control characters B, F, P, N, A, E, V, D, K (if set
accordingly), L somewhat, and sometimes H (the way I configure emacs), are
compatible in the pine editor with the emacs keybinding standard. Why not
make Y, U, @, S, and W also compatible, at least for those of us who
select "Enable emacs key bindings" or somesuch?

CURSOR MOTION KEYS |EDITING KEYS
^B (Left Arrow) Back character | ^D Delete current character
^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
^P (Up Arrow) Previous line | ^^ Set a mark
^N (Down Arrow) Next line | ^K Cut marked text or
^A Beginning of line | delete current line
^E End of line | ^U Paste text, undelete lines
^Y Previous page | cut with ^K, or unjustify
^V Next page |-------------------------------------
^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
---------------------------------------| ^W Whereis (search for string)
MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
^C Cancel | ^G Get help | ^J Justify paragraph
^O Postpone | ^Z Suspend | ^L Redraw Screen
^X Send | ^_ Alt. editor | ^R Read in a file

Regards,

Mike

--
Michael B. Miller, M.S., Ph.D., M.P.E.
Department of Psychology
210 McAlester Hall
University of Missouri--Columbia
Columbia, MO 65211

Phone: (573) 882-5671
Fax: (573) 882-7710
e-mail: [email protected]
web: http://taxa.psyc.missouri.edu/~mbmiller/

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 14:51: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA30331;
Thu, 2 Dec 1999 14:51:28 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA03244;
Thu, 2 Dec 1999 14:51:28 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA04826;
Thu, 2 Dec 1999 14:49:22 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA17490
for <[email protected]>; Thu, 2 Dec 1999 14:43:34 -0800
Received: from vax.area.com (vax128.area.com [165.90.20.128])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id OAA28718
for <[email protected]>; Thu, 2 Dec 1999 14:43:33 -0800
Received: (qmail 4984 invoked by uid 1828); 2 Dec 1999 22:39:11 -0000
Message-Id: <Pine.GSO.4.20.9912021438120.13144-100000@vax>
Date: Thu, 2 Dec 1999 14:39:10 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Mike Miller wrote:
>If you can't do it with Alt-B (a la emacs), why not use Ctrl-# (it's right
>next to Ctrl-@)??

Unless I'm missing something obvious, there's no such character as control-#.
Only control-@ and ^^ exist.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 15:19:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04648;
Thu, 2 Dec 1999 15:19:23 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA01803;
Thu, 2 Dec 1999 15:19:23 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA21368;
Thu, 2 Dec 1999 15:16:50 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA37422
for <[email protected]>; Thu, 2 Dec 1999 15:12:49 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA03136
for <[email protected]>; Thu, 2 Dec 1999 15:12:48 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id RAA25863
for <[email protected]>; Thu, 2 Dec 1999 17:12:47 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 17:12:47 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <Pine.GSO.4.20.9912021438120.13144-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999 [email protected] wrote:

> On Thu, 2 Dec 1999, Mike Miller wrote:
> >If you can't do it with Alt-B (a la emacs), why not use Ctrl-# (it's right
> >next to Ctrl-@)??
>
> Unless I'm missing something obvious, there's no such character as control-#.
> Only control-@ and ^^ exist.

Oh. Well, I guess we can't do it with Ctrl-# then! How about Ctrl-Q?
That's right next to Ctrl-@ and it isn't being used.

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 15:25: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA09875;
Thu, 2 Dec 1999 15:25:20 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04314;
Thu, 2 Dec 1999 15:25:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA09026;
Thu, 2 Dec 1999 15:23:12 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA57846
for <[email protected]>; Thu, 2 Dec 1999 15:18:31 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA04694
for <[email protected]>; Thu, 2 Dec 1999 15:18:22 -0800
Received: (qmail 1364 invoked from network); 2 Dec 1999 23:18:21 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 2 Dec 1999 23:18:21 -0000
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 16:19:39 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <Pine.GSO.4.20.9912021438120.13144-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: [email protected]
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

There certainly is a character control-#. You press shift and control and
3 all at the same time.

I have a feeling that isn't what you really meant.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Thu, 2 Dec 1999 [email protected] wrote:

> On Thu, 2 Dec 1999, Mike Miller wrote:
> >If you can't do it with Alt-B (a la emacs), why not use Ctrl-# (it's right
> >next to Ctrl-@)??
>
> Unless I'm missing something obvious, there's no such character as control-#.
> Only control-@ and ^^ exist.
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 15:38:31 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA10030;
Thu, 2 Dec 1999 15:38:29 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA02371;
Thu, 2 Dec 1999 15:38:29 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA01904;
Thu, 2 Dec 1999 15:36:27 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA43218
for <[email protected]>; Thu, 2 Dec 1999 15:30:31 -0800
Received: from dante35.u.washington.edu ([email protected] [140.142.15.195])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA20828;
Thu, 2 Dec 1999 15:30:26 -0800
Received: from localhost (leibrand@localhost)
by dante35.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA79524;
Thu, 2 Dec 1999 15:30:25 -0800
Message-Id: <Pine.A41.4.20.9912021528150.71762-100000@dante35.u.washington.edu>
Date: Thu, 2 Dec 1999 15:30: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Mike Miller wrote:

> Oh. Well, I guess we can't do it with Ctrl-# then! How about Ctrl-Q?
> That's right next to Ctrl-@ and it isn't being used.

^Q is a "start" character. See the preserve-start-stop-characters (or
whatever it's called) in Pine's Setup, Config.

I don't know what the difference is, but I always use Ctrl-Space to
advance one word. It'd be nice to have a command to go back one word,
though. I always end up doing ^A followed by lots of ^-space's.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 16:33:07 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA12066;
Thu, 2 Dec 1999 16:33:06 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA03981;
Thu, 2 Dec 1999 16:33:05 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA12865;
Thu, 2 Dec 1999 16:31:09 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA55340
for <[email protected]>; Thu, 2 Dec 1999 16:26:18 -0800
Received: from nimbus.anzio.com (IDENT:[email protected] [204.201.253.34])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA30895
for <[email protected]>; Thu, 2 Dec 1999 16:26:16 -0800
Received: from localhost (ras@localhost)
by nimbus.anzio.com (8.8.7/8.8.7) with ESMTP id QAA26136;
Thu, 2 Dec 1999 16:24:23 -0800
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 16:24:23 -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: Bob Rasmussen <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Seth Kurtzberg <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Seth Kurtzberg wrote:

> There certainly is a character control-#. You press shift and control and
> 3 all at the same time.
>
> I have a feeling that isn't what you really meant.

That would be a key combination, but not a character. Characters are 8-bit
entities (except in the Far East) that can be sent over communication links.
The "control characters" are hex 00 through hex 1F. Most of these are thought
of as control+letter; for instance control-A is "A" (hex 41) minus hex 40,
yielding hex 01. This works up through control-Z = hex 1A.

Other combinations:

Hex Key combination
---------------------
00 Ctrl-@ or ctrl-space, depending on the program managing the keyboard
..
1B Ctrl-[ or Escape
1C Ctrl-\
1D Ctrl-]
1E Ctrl-^
1F Ctrl-underline

Many key combinations have no standard character associated with them, such as
PageUp, F4, etc.

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

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 16:40:47 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA11554;
Thu, 2 Dec 1999 16:40:45 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA06456;
Thu, 2 Dec 1999 16:40:45 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA25786;
Thu, 2 Dec 1999 16:36:56 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA42376
for <[email protected]>; Thu, 2 Dec 1999 16:32:11 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA10417
for <[email protected]>; Thu, 2 Dec 1999 16:32:11 -0800
Received: (qmail 17473 invoked from network); 3 Dec 1999 00:32:09 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 3 Dec 1999 00:32:09 -0000
Message-Id: <[email protected]>
Date: Thu, 2 Dec 1999 17:33:27 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Bob Rasmussen <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

The point I was making is that the ASCII code says absolutely nothing
about key combinations, and the assignment of a key combination to an
ASCII code is completely arbitrary. ESC is an ASCII code, by the typical
key combination (as you noted, often control-[) is not part of the code at
all.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Thu, 2 Dec 1999, Bob Rasmussen wrote:

> On Thu, 2 Dec 1999, Seth Kurtzberg wrote:
>
> > There certainly is a character control-#. You press shift and control and
> > 3 all at the same time.
> >
> > I have a feeling that isn't what you really meant.
>
> That would be a key combination, but not a character. Characters are 8-bit
> entities (except in the Far East) that can be sent over communication links.
> The "control characters" are hex 00 through hex 1F. Most of these are thought
> of as control+letter; for instance control-A is "A" (hex 41) minus hex 40,
> yielding hex 01. This works up through control-Z = hex 1A.
>
> Other combinations:
>
> Hex Key combination
> ---------------------
> 00 Ctrl-@ or ctrl-space, depending on the program managing the keyboard
> ...
> 1B Ctrl-[ or Escape
> 1C Ctrl-\
> 1D Ctrl-]
> 1E Ctrl-^
> 1F Ctrl-underline
>
> Many key combinations have no standard character associated with them, such as
> PageUp, F4, etc.
>
>
> --
> Regards,
> ....Bob Rasmussen, President, Rasmussen Software, Inc.
>
> personal e-mail: [email protected]
> company e-mail: [email protected] or [email protected] or [email protected]
> ftp://ftp.anzio.com voice: 503-624-0360
> http://www.anzio.com fax: 503-624-0760
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 2 Dec 1999 18:42:48 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA13878;
Thu, 2 Dec 1999 18:42:47 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA09203;
Thu, 2 Dec 1999 18:42:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA16393;
Thu, 2 Dec 1999 18:40:21 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA93204
for <[email protected]>; Thu, 2 Dec 1999 18:36:17 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA05902
for <[email protected]>; Thu, 2 Dec 1999 18:36:17 -0800
Received: from goedel1.math.washington.edu ([email protected] [128.95.224.2])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id SAA14460;
Thu, 2 Dec 1999 18:36:15 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912021816550.26619-100000@goedel1.math.washington.edu>
Date: Thu, 2 Dec 1999 18:36: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Mike Miller ([email protected]) wrote today:

:) Why not make Y, U, @, S, and W also compatible, at least for those
:) of us who select "Enable emacs key bindings" or somesuch?
:)

Well, you have a difficult opposition here. According to the source code,
there is no way (and won't be implemented) to associate arbitrary keys
with functions. So you are out of luck here.

What I think it could be useful is to duplicate a key, kind of what like
Emacs does with ^X. ^X does not mean anything by itself, but in
combination with other keys it does. It should be possible to agree in one
key which serves the purpose of ^X in emacs but for pico/pine. I suggested
to do this with ^J, thinking of ^J as "do this to the paragraph", but it
may be thought of many other ways (you can see a patch I wrote in the
address below), no success until today, but certainly that would be a way
to get all these features that people need sometimes, and that sometimes
you can't live without. Since Pine's philosophy is not to change anything
unless the user request it explicitly, this should be configurable, but
that's again not difficult to do.

I think that adapting the source code to the needs of very advanced
users is a big task. Some features may not come out if this does not
happen, at least that is what I see from reading the source code.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 08:31: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA29265;
Fri, 3 Dec 1999 08:31:00 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA23509;
Fri, 3 Dec 1999 08:30:59 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA13057;
Fri, 3 Dec 1999 08:27:57 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA11034
for <[email protected]>; Fri, 3 Dec 1999 08:22:51 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA20510
for <[email protected]>; Fri, 3 Dec 1999 08:22:38 -0800
Received: from hix.physik.uni-bremen.de ([email protected] [134.102.160.75])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA20925
for <[email protected]>; Fri, 3 Dec 1999 08:22:36 -0800
Received: from localhost (noack@localhost)
by hix.physik.uni-bremen.de (8.8.8/8.8.8) with ESMTP id RAA14895;
Fri, 3 Dec 1999 17:21:18 +0100
Message-Id: <Pine.LNX.4.10.9912031707090.14845-100000@hix.physik.uni-bremen.de>
Date: Fri, 3 Dec 1999 17:21:17 +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: "Cornelius C. Noack" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: delete empty folders fom PINE
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-To: [email protected]
X-Cc: [email protected], [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 10 Jan 1997, Helmer Aslaksen wrote:

> I've just switched from elm to pine, and I have some problems. Is
> there some way to make pine automatically delete a folder when I have
> deleted all the messages in it?

I am now in exactly your position and want to ask the identical
question. Did you ever get an answer, or does anyone know how to do this?
ccn.
............................................................................
_|_
/ | \
_|_/ Prof.Dr. Cornelius C. Noack Phones:
_|_ ___ Inst. f. Theoret. Physik FB 1 office : +49 (421) 218-2427
| | | \ Universit"at Bremen secretary: -2422
|___| |___/ Kufsteiner Strasse Fax : -4869
| | | \ D - 28334 Bremen home : +49 (421) 34 22 36
| | |___/ Fax: 346 7873
PhyHB E-mail : [email protected]
............................................................................

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 09:24:00 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA30881;
Fri, 3 Dec 1999 09:23:59 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA25579;
Fri, 3 Dec 1999 09:23:59 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA16267;
Fri, 3 Dec 1999 09:20:41 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA31272
for <[email protected]>; Fri, 3 Dec 1999 09:15:57 -0800
Received: from atlantis.bus.ucf.edu (IDENT:[email protected] [132.170.121.8])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA30081
for <[email protected]>; Fri, 3 Dec 1999 09:15:56 -0800
Received: from localhost (david@localhost)
by atlantis.bus.ucf.edu (8.9.3/8.9.3) with ESMTP id MAA20160
for <[email protected]>; Fri, 3 Dec 1999 12:17:06 -0500
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 12:17:06 -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: David Collantes <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Ok, here I go again!
In-Reply-To: <Pine.A41.4.20.9912021528150.71762-100000@dante35.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have a question/request. Let me explain the situation first.

I use procmail (like, probably, a lot of people here) to filter my emails
and save then in diferent "folders". On of my recipies, for example, would
be:

:0
* ^From .*domain.com
$HOME/mail/domain

I do not use "[ ] enable incoming folders", since I do only have one
account. Now, to check wether I have new mail or not, I have to go to each
and every "folder". Is there any setting that will bold the "folder"
containing new emails? Coulid that be added to a future release,
Development Team?

Thanks in advance.

Cheers,

,----------------------------------.,-----------------------------------.
| David Collantes || email: [email protected] |
| Senior Systems Administrator, || phone: (407) 823-3418 |
| Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
`----------------------------------'`-----------------------------------'

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 09:44: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA31424;
Fri, 3 Dec 1999 09:44:52 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26270;
Fri, 3 Dec 1999 09:44:51 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA08325;
Fri, 3 Dec 1999 09:42:44 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA83796
for <[email protected]>; Fri, 3 Dec 1999 09:39:04 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA27417
for <[email protected]>; Fri, 3 Dec 1999 09:39:04 -0800
Received: (qmail 22923 invoked from network); 3 Dec 1999 17:38:59 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 3 Dec 1999 17:38:59 -0000
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 10:40:15 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Ok, here I go again!
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Collantes <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This isn't really an answer, but I use a utility called "fetchmail" to
gather up mail from a variety of places and put them in a single folder.
Fetchmail has an option to **not** remove the data from the mailbox, so
you might be able to set it up to do something similar to what you want.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Fri, 3 Dec 1999, David Collantes wrote:

>
> I have a question/request. Let me explain the situation first.
>
> I use procmail (like, probably, a lot of people here) to filter my emails
> and save then in diferent "folders". On of my recipies, for example, would
> be:
>
> :0
> * ^From .*domain.com
> $HOME/mail/domain
>
> I do not use "[ ] enable incoming folders", since I do only have one
> account. Now, to check wether I have new mail or not, I have to go to each
> and every "folder". Is there any setting that will bold the "folder"
> containing new emails? Coulid that be added to a future release,
> Development Team?
>
> Thanks in advance.
>
> Cheers,
>
>
> ,----------------------------------.,-----------------------------------.
> | David Collantes || email: [email protected] |
> | Senior Systems Administrator, || phone: (407) 823-3418 |
> | Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
> `----------------------------------'`-----------------------------------'
>
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:12:17 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA32481;
Fri, 3 Dec 1999 10:12:16 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA24816;
Fri, 3 Dec 1999 10:12:16 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA09684;
Fri, 3 Dec 1999 10:07:43 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA40560
for <[email protected]>; Fri, 3 Dec 1999 10:04:40 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA21159
for <[email protected]>; Fri, 3 Dec 1999 10:04:39 -0800
Received: from alephminus1.ii.com (alephminus1.ii.com [216.44.169.226])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id NAA29968;
Fri, 3 Dec 1999 13:04:37 -0500 (EST)
Message-Id: <Pine.WNT.4.21.9912031253090.-480849@alephminus1>
Date: Fri, 3 Dec 1999 13:03:35 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Ok, here I go again!
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-03 David Collantes <[email protected]> wrote:
> I use procmail (like, probably, a lot of people here) to filter my emails
> and save then in diferent "folders". On of my recipies, for example, would
> be:
>
> :0
> * ^From .*domain.com
> $HOME/mail/domain

You probably want to use a lockfile in the above recipe, i.e.,
the first line should be:

:0:

I've got lots of procmail info at the first URL in my sig.

> I do not use "[ ] enable incoming folders", since I do only have one
> account.

But you do have more than one incoming folder so setting
incoming-folders like this:

incoming-folders={your.server/user=username}mail/domain1,
{your.server/user=username}mail/domain2,
etc.

And then using TAB to move through you incoming-folders with new
messages would probably be useful to you.

> Now, to check wether I have new mail or not, I have to go to each
> and every "folder". Is there any setting that will bold the "folder"
> containing new emails?

Yes, while viewing your folder list screen type:

; P N CR

Folders with new messages will be bolded. You might want to set
auto-zoom-after-select.

HTH,
Nancy

--
For Procmail info, see www.ii.com/internet/robots/procmail/qs/
For Pine links, see http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
--= Sent via PINE 4.21: Internet News & Email for Win/Unix =--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:20:40 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA31608;
Fri, 3 Dec 1999 10:20:38 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA27300;
Fri, 3 Dec 1999 10:20:38 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA10323;
Fri, 3 Dec 1999 10:17:13 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA27818
for <[email protected]>; Fri, 3 Dec 1999 10:11:39 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01267
for <[email protected]>; Fri, 3 Dec 1999 10:11:39 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id MAA05779;
Fri, 3 Dec 1999 12:11:38 -0600 (CST)
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 12:11:38 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, David Collantes wrote:

> I use procmail (like, probably, a lot of people here) to filter my emails
> and save then in diferent "folders".
<snip>
> I do not use "[ ] enable incoming folders", since I do only have one
> account.

Well, I think that's your mistake right there. I have one account, but I
have about 10 incoming folders. Read up on it in the Pine documentation.
You can set up nicknames for folders. I give the incoming folders names
that begin with "IN.", for example, IN.pine. Then I save read messages in
a folder without the "IN." in it, for example, pine. But I have a
nickname for the incoming folder so that IN.pine is displayed as if it had
the name 'pine' without the "IN." on it. This is not confusing because
the incoming folders are stored in a different folder list. Having the
same name makes it easy: I have an Incoming 'pine' folder and a Mail
'pine' folder.

I also use a script (appended below) to tell me what new mail I have. It
tells me what messages are in my Inbox folder (~/mail/inbox) and how many
messages are in each of my other incoming mail folders. I run this script
as part of my .login file, but I also run it from the command line. I
think if you keep your mail in ~/mail, have an inbox named ~/mail/inbox,
and have other incoming folders named ~/mail/IN.*, this scirpt will work
without alteration except for one thing: the script uses tcsh and you
have to have the correct path to tcsh in the first line. On Linux
machines it is often /usr/bin/tcsh instead of /usr/local/bin/tcsh.

Note that the use of "tail +13" in the script is to avoid the first 12
lines of the Pine folder which contain the "Mail System Internal Data"
information.

Mike

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

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

#!/usr/local/bin/tcsh -f
if ( `wc ~/mail/inbox | awk '{print $1}'` == 12 ) then
echo ""
echo "No mail in Inbox"
else
echo ""
tail +13 ~/mail/inbox | egrep '^From ' | wc | awk '{print "Listing of "$1" messages in your inbox:"}'
echo ""
foreach item ( `tail +13 ~/mail/inbox | egrep -n '^From ' | awk -F: '{print $1 + 12}'` )
tail +$item ~/mail/inbox | egrep '^From: ' | head -1
tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | tail +2 | head -1 | egrep -v '^From: '
echo ""
end
endif
echo ""
echo "Messages in other inboxes:"
echo ""
foreach file ( `ls -1 ~/mail/IN.* | awk -F. '{print $NF}'` )
echo "$file `tail +13 ~/mail/IN.$file | egrep '^From ' | wc`" | awk '{print $1" has "$2" messages"}' | grep -v ' 0 '
end
echo ""

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:26:51 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA32720;
Fri, 3 Dec 1999 10:26:50 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA27486;
Fri, 3 Dec 1999 10:26:50 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA19760;
Fri, 3 Dec 1999 10:23:03 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA49166
for <[email protected]>; Fri, 3 Dec 1999 10:18:48 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA23908
for <[email protected]>; Fri, 3 Dec 1999 10:18:43 -0800
Received: (qmail 3957 invoked from network); 3 Dec 1999 18:18:42 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 3 Dec 1999 18:18:42 -0000
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 11:19:58 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Your method is definitely better for Pine. I use fetchmail because the
mailboxes are on different hosts. I don't think Pine will handle that.
Am I wrong?

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Fri, 3 Dec 1999, Mike Miller wrote:

> On Fri, 3 Dec 1999, David Collantes wrote:
>
> > I use procmail (like, probably, a lot of people here) to filter my emails
> > and save then in diferent "folders".
> <snip>
> > I do not use "[ ] enable incoming folders", since I do only have one
> > account.
>
> Well, I think that's your mistake right there. I have one account, but I
> have about 10 incoming folders. Read up on it in the Pine documentation.
> You can set up nicknames for folders. I give the incoming folders names
> that begin with "IN.", for example, IN.pine. Then I save read messages in
> a folder without the "IN." in it, for example, pine. But I have a
> nickname for the incoming folder so that IN.pine is displayed as if it had
> the name 'pine' without the "IN." on it. This is not confusing because
> the incoming folders are stored in a different folder list. Having the
> same name makes it easy: I have an Incoming 'pine' folder and a Mail
> 'pine' folder.
>
> I also use a script (appended below) to tell me what new mail I have. It
> tells me what messages are in my Inbox folder (~/mail/inbox) and how many
> messages are in each of my other incoming mail folders. I run this script
> as part of my .login file, but I also run it from the command line. I
> think if you keep your mail in ~/mail, have an inbox named ~/mail/inbox,
> and have other incoming folders named ~/mail/IN.*, this scirpt will work
> without alteration except for one thing: the script uses tcsh and you
> have to have the correct path to tcsh in the first line. On Linux
> machines it is often /usr/bin/tcsh instead of /usr/local/bin/tcsh.
>
> Note that the use of "tail +13" in the script is to avoid the first 12
> lines of the Pine folder which contain the "Mail System Internal Data"
> information.
>
> Mike
>
> --
> Michael B. Miller
> University of Missouri--Columbia
> http://taxa.psyc.missouri.edu/~mbmiller/
>
>
> --------------------------------------------------------------------------
>
> #!/usr/local/bin/tcsh -f
> if ( `wc ~/mail/inbox | awk '{print $1}'` == 12 ) then
> echo ""
> echo "No mail in Inbox"
> else
> echo ""
> tail +13 ~/mail/inbox | egrep '^From ' | wc | awk '{print "Listing of "$1" messages in your inbox:"}'
> echo ""
> foreach item ( `tail +13 ~/mail/inbox | egrep -n '^From ' | awk -F: '{print $1 + 12}'` )
> tail +$item ~/mail/inbox | egrep '^From: ' | head -1
> tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | tail +2 | head -1 | egrep -v '^From: '
> echo ""
> end
> endif
> echo ""
> echo "Messages in other inboxes:"
> echo ""
> foreach file ( `ls -1 ~/mail/IN.* | awk -F. '{print $NF}'` )
> echo "$file `tail +13 ~/mail/IN.$file | egrep '^From ' | wc`" | awk '{print $1" has "$2" messages"}' | grep -v ' 0 '
> end
> echo ""
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:34:42 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA32522;
Fri, 3 Dec 1999 10:34:41 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25494;
Fri, 3 Dec 1999 10:34:40 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA11232;
Fri, 3 Dec 1999 10:31:01 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA93708
for <[email protected]>; Fri, 3 Dec 1999 10:26:56 -0800
Received: from polaris.shore.net (polaris.shore.net [207.244.124.105])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25582
for <[email protected]>; Fri, 3 Dec 1999 10:26:50 -0800
Received: from shell3.shore.net [207.244.124.103]
by polaris.shore.net with esmtp (Exim)
id 11txPk-0004Wm-00; Fri, 3 Dec 1999 13:26:40 -0500
Received: from ar by shell3.shore.net with local (Exim)
id 11txPj-0007cx-00; Fri, 3 Dec 1999 13:26:39 -0500
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 13:26:39 -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: Ariel <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: Ariel <[email protected]>
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Mike Miller wrote:

> Another *great* feature would be to allow searches of the message body
> (excluding the message header). Here's an example: I get a bunch of
> messages from an e-mail list and I don't want to read them all, but I want
> to see if any of them refer to my earlier posting. If I search "Text All"
> for messages containing 'miller' *all* of the messages will be selected
> because all of them were sent to me (mbmiller) and 'mbmiller' is therefore
> in the header of every message. If I could search the message body I
> would find messages where they mention "Mike Miller" or whatever. Doesn't
> that seem like it would be potentially very useful.

And conversely, I would love search "header" for text, rather then a
specific header line. For example I want every message that was sent to,
from or has anything to do with "mwave" right now I need to do a CC
search, a To, a subject, and I might still be missing some if the message
was BCC'd and the mwave is in the received header.

Only problem is I'm not sure if IMAP has this feature - pine gets it's
stuff directly from IMAP, and if IMAP can't do header, or body search
neither can pine.

-Ariel

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:42: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA00350;
Fri, 3 Dec 1999 10:42:01 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA27924;
Fri, 3 Dec 1999 10:42:01 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA18156;
Fri, 3 Dec 1999 10:35:26 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA85072
for <[email protected]>; Fri, 3 Dec 1999 10:30:10 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA12216
for <[email protected]>; Fri, 3 Dec 1999 10:30:10 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id MAA05829
for <[email protected]>; Fri, 3 Dec 1999 12:30:09 -0600 (CST)
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 12:30:09 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, Seth Kurtzberg wrote:

> Your method is definitely better for Pine. I use fetchmail because the
> mailboxes are on different hosts. I don't think Pine will handle that.
> Am I wrong?

Well my script only works on local files, but Pine can handle incoming
mail on different hosts. See Nancy's last message or look at the
documentation for handling multiple incoming folders. I've used it here
on our campus and it worked great. Using tab to jump to the next folder
with new mail, when I got to a remote folder, I only had to enter a
password then pine would check for incoming mail on the remote host, it
would open the folder if there was new mail, or skip to the next folder if
there was no new mail. It's *just* like the mail is on your machine,
totally transparent, except for the password (you want it that way, of
course!).

Maybe fetchmail is a better solution, I don't know, but you still want to
put the mail fetched from different hosts into different incoming folders,
right? So you can still pine's multiple-incoming-folders feature with
fetchmail.

Mike

>
>
> On Fri, 3 Dec 1999, Mike Miller wrote:
>
> > On Fri, 3 Dec 1999, David Collantes wrote:
> >
> > > I use procmail (like, probably, a lot of people here) to filter my emails
> > > and save then in diferent "folders".
> > <snip>
> > > I do not use "[ ] enable incoming folders", since I do only have one
> > > account.
> >
> > Well, I think that's your mistake right there. I have one account, but I
> > have about 10 incoming folders. Read up on it in the Pine documentation.
> > You can set up nicknames for folders. I give the incoming folders names
> > that begin with "IN.", for example, IN.pine. Then I save read messages in
> > a folder without the "IN." in it, for example, pine. But I have a
> > nickname for the incoming folder so that IN.pine is displayed as if it had
> > the name 'pine' without the "IN." on it. This is not confusing because
> > the incoming folders are stored in a different folder list. Having the
> > same name makes it easy: I have an Incoming 'pine' folder and a Mail
> > 'pine' folder.
> >
> > I also use a script (appended below) to tell me what new mail I have. It
> > tells me what messages are in my Inbox folder (~/mail/inbox) and how many
> > messages are in each of my other incoming mail folders. I run this script
> > as part of my .login file, but I also run it from the command line. I
> > think if you keep your mail in ~/mail, have an inbox named ~/mail/inbox,
> > and have other incoming folders named ~/mail/IN.*, this scirpt will work
> > without alteration except for one thing: the script uses tcsh and you
> > have to have the correct path to tcsh in the first line. On Linux
> > machines it is often /usr/bin/tcsh instead of /usr/local/bin/tcsh.
> >
> > Note that the use of "tail +13" in the script is to avoid the first 12
> > lines of the Pine folder which contain the "Mail System Internal Data"
> > information.
> >
> > Mike
> >
> > --
> > Michael B. Miller
> > University of Missouri--Columbia
> > http://taxa.psyc.missouri.edu/~mbmiller/
> >
> >
> > --------------------------------------------------------------------------
> >
> > #!/usr/local/bin/tcsh -f
> > if ( `wc ~/mail/inbox | awk '{print $1}'` == 12 ) then
> > echo ""
> > echo "No mail in Inbox"
> > else
> > echo ""
> > tail +13 ~/mail/inbox | egrep '^From ' | wc | awk '{print "Listing of "$1" messages in your inbox:"}'
> > echo ""
> > foreach item ( `tail +13 ~/mail/inbox | egrep -n '^From ' | awk -F: '{print $1 + 12}'` )
> > tail +$item ~/mail/inbox | egrep '^From: ' | head -1
> > tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | tail +2 | head -1 | egrep -v '^From: '
> > echo ""
> > end
> > endif
> > echo ""
> > echo "Messages in other inboxes:"
> > echo ""
> > foreach file ( `ls -1 ~/mail/IN.* | awk -F. '{print $NF}'` )
> > echo "$file `tail +13 ~/mail/IN.$file | egrep '^From ' | wc`" | awk '{print $1" has "$2" messages"}' | grep -v ' 0 '
> > end
> > echo ""
> >
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:48:47 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA00664;
Fri, 3 Dec 1999 10:48:46 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25993;
Fri, 3 Dec 1999 10:48:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA18699;
Fri, 3 Dec 1999 10:42:33 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA72864
for <[email protected]>; Fri, 3 Dec 1999 10:39:03 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA06337
for <[email protected]>; Fri, 3 Dec 1999 10:39:02 -0800
Received: (qmail 9459 invoked from network); 3 Dec 1999 18:39:00 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 3 Dec 1999 18:39:00 -0000
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 11:40:15 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Thanks, I'll try it.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Fri, 3 Dec 1999, Mike Miller wrote:

> On Fri, 3 Dec 1999, Seth Kurtzberg wrote:
>
> > Your method is definitely better for Pine. I use fetchmail because the
> > mailboxes are on different hosts. I don't think Pine will handle that.
> > Am I wrong?
>
> Well my script only works on local files, but Pine can handle incoming
> mail on different hosts. See Nancy's last message or look at the
> documentation for handling multiple incoming folders. I've used it here
> on our campus and it worked great. Using tab to jump to the next folder
> with new mail, when I got to a remote folder, I only had to enter a
> password then pine would check for incoming mail on the remote host, it
> would open the folder if there was new mail, or skip to the next folder if
> there was no new mail. It's *just* like the mail is on your machine,
> totally transparent, except for the password (you want it that way, of
> course!).
>
> Maybe fetchmail is a better solution, I don't know, but you still want to
> put the mail fetched from different hosts into different incoming folders,
> right? So you can still pine's multiple-incoming-folders feature with
> fetchmail.
>
> Mike
>
>
> >
> >
> > On Fri, 3 Dec 1999, Mike Miller wrote:
> >
> > > On Fri, 3 Dec 1999, David Collantes wrote:
> > >
> > > > I use procmail (like, probably, a lot of people here) to filter my emails
> > > > and save then in diferent "folders".
> > > <snip>
> > > > I do not use "[ ] enable incoming folders", since I do only have one
> > > > account.
> > >
> > > Well, I think that's your mistake right there. I have one account, but I
> > > have about 10 incoming folders. Read up on it in the Pine documentation.
> > > You can set up nicknames for folders. I give the incoming folders names
> > > that begin with "IN.", for example, IN.pine. Then I save read messages in
> > > a folder without the "IN." in it, for example, pine. But I have a
> > > nickname for the incoming folder so that IN.pine is displayed as if it had
> > > the name 'pine' without the "IN." on it. This is not confusing because
> > > the incoming folders are stored in a different folder list. Having the
> > > same name makes it easy: I have an Incoming 'pine' folder and a Mail
> > > 'pine' folder.
> > >
> > > I also use a script (appended below) to tell me what new mail I have. It
> > > tells me what messages are in my Inbox folder (~/mail/inbox) and how many
> > > messages are in each of my other incoming mail folders. I run this script
> > > as part of my .login file, but I also run it from the command line. I
> > > think if you keep your mail in ~/mail, have an inbox named ~/mail/inbox,
> > > and have other incoming folders named ~/mail/IN.*, this scirpt will work
> > > without alteration except for one thing: the script uses tcsh and you
> > > have to have the correct path to tcsh in the first line. On Linux
> > > machines it is often /usr/bin/tcsh instead of /usr/local/bin/tcsh.
> > >
> > > Note that the use of "tail +13" in the script is to avoid the first 12
> > > lines of the Pine folder which contain the "Mail System Internal Data"
> > > information.
> > >
> > > Mike
> > >
> > > --
> > > Michael B. Miller
> > > University of Missouri--Columbia
> > > http://taxa.psyc.missouri.edu/~mbmiller/
> > >
> > >
> > > --------------------------------------------------------------------------
> > >
> > > #!/usr/local/bin/tcsh -f
> > > if ( `wc ~/mail/inbox | awk '{print $1}'` == 12 ) then
> > > echo ""
> > > echo "No mail in Inbox"
> > > else
> > > echo ""
> > > tail +13 ~/mail/inbox | egrep '^From ' | wc | awk '{print "Listing of "$1" messages in your inbox:"}'
> > > echo ""
> > > foreach item ( `tail +13 ~/mail/inbox | egrep -n '^From ' | awk -F: '{print $1 + 12}'` )
> > > tail +$item ~/mail/inbox | egrep '^From: ' | head -1
> > > tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | tail +2 | head -1 | egrep -v '^From: '
> > > echo ""
> > > end
> > > endif
> > > echo ""
> > > echo "Messages in other inboxes:"
> > > echo ""
> > > foreach file ( `ls -1 ~/mail/IN.* | awk -F. '{print $NF}'` )
> > > echo "$file `tail +13 ~/mail/IN.$file | egrep '^From ' | wc`" | awk '{print $1" has "$2" messages"}' | grep -v ' 0 '
> > > end
> > > echo ""
> > >
> >
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 10:59:18 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA00248;
Fri, 3 Dec 1999 10:59:00 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26687;
Fri, 3 Dec 1999 10:59:00 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA04185;
Fri, 3 Dec 1999 10:54:07 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA49232
for <[email protected]>; Fri, 3 Dec 1999 10:50:05 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16195
for <[email protected]>; Fri, 3 Dec 1999 10:50:04 -0800
Received: from goedel2.math.washington.edu ([email protected] [128.95.224.11])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id KAA11945;
Fri, 3 Dec 1999 10:49:58 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912031045190.12604-100000@goedel2.math.washington.edu>
Date: Fri, 3 Dec 1999 10:49: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Dear Mike,

You can have pine checking automatically for new mail in your incoming
folders. I wrote a patch that does that in any subset of the collection of
incoming folder. Check it out in the address below. All comments are
appreciated.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 11:02:15 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02310;
Fri, 3 Dec 1999 11:02:14 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA29357;
Fri, 3 Dec 1999 11:02:14 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA13121;
Fri, 3 Dec 1999 10:58:27 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA66742
for <[email protected]>; Fri, 3 Dec 1999 10:51:53 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16589
for <[email protected]>; Fri, 3 Dec 1999 10:51:52 -0800
Received: from alephminus1.ii.com (alephminus1.ii.com [216.44.169.226])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id NAA00541;
Fri, 3 Dec 1999 13:51:49 -0500 (EST)
Message-Id: <Pine.WNT.4.21.9912031342560.-480849@alephminus1>
Date: Fri, 3 Dec 1999 13:50: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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-03 Ariel <[email protected]> wrote:
> On Thu, 2 Dec 1999, Mike Miller wrote:
> > Another *great* feature would be to allow searches of the message body
> > (excluding the message header).

Yes, I'd like body-only searching too!

> And conversely, I would love search "header" for text, rather then a
> specific header line. For example I want every message that was sent to,
> from or has anything to do with "mwave" right now I need to do a CC
> search, a To, a subject, and I might still be missing some if the message
> was BCC'd and the mwave is in the received header.

You can save yourself some of the searches by searching based on
Participant (which is To, Cc, and From). Here's the prompt I get
in 4.21:

Select based on To, From, Cc, Recip, Subject fields or All message text ?
F From T To C Cc R Recipient
^C Cancel S [Subject] A All Text ! Not P Participant

Note to Pine Developers: The prompt needs to be changed so it
includes Partic, e.g., change it to:

Select based on To, From, Cc, Recip, Partic, Subject fields or All message text ?

Also, how exactly does the Not (!) command work? If I say "! P"
(Not Participant) does that search just headers (excluding
Participants) or does it search headers and body (excluding
Participants)? If it's the latter, this is a partial solution to
Mike Miller's body-only searching request.

--
For Pine links, see http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
--= Sent via PINE 4.21: Internet News & Email for Win/Unix =--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 11:18:46 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02541;
Fri, 3 Dec 1999 11:18:45 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27471;
Fri, 3 Dec 1999 11:18:44 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA05268;
Fri, 3 Dec 1999 11:15:26 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA37478
for <[email protected]>; Fri, 3 Dec 1999 11:11:55 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA20850
for <[email protected]>; Fri, 3 Dec 1999 11:11:54 -0800
Received: from goedel2.math.washington.edu ([email protected] [128.95.224.11])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id LAA13169;
Fri, 3 Dec 1999 11:11:50 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912031105030.12604-100000@goedel2.math.washington.edu>
Date: Fri, 3 Dec 1999 11:11:49 -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 L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.WNT.4.21.9912031342560.-480849@alephminus1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Nancy this-address-is-valid McGough ([email protected]) wrote today:

:) Also, how exactly does the Not (!) command work? If I say "! P"
:) (Not Participant) does that search just headers (excluding
:) Participants) or does it search headers and body (excluding
:) Participants)? If it's the latter, this is a partial solution to
:) Mike Miller's body-only searching request.
:)
This means that the Participant will not be what you specify later, so if
you want to read mails where you have not participated you would make a
search by:

; t ! P nancy CR

The advantage of this is that now you can narrow your select to say all
the ones that have the word "bug" in the subject so you would do:

; n t s bug CR

and now eliminate replies by

; n t ! s Re: CR

I hope this makes it clear...

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 11:53:02 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02769;
Fri, 3 Dec 1999 11:53:01 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA28630;
Fri, 3 Dec 1999 11:53:00 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA22774;
Fri, 3 Dec 1999 11:49:02 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA16864
for <[email protected]>; Fri, 3 Dec 1999 11:39:18 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA26113
for <[email protected]>; Fri, 3 Dec 1999 11:39:17 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id NAA06169
for <[email protected]>; Fri, 3 Dec 1999 13:39:16 -0600 (CST)
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 13:39:16 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.WNT.4.21.9912031342560.-480849@alephminus1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, Nancy this-address-is-valid McGough wrote:

> Also, how exactly does the Not (!) command work? If I say "! P"
> (Not Participant) does that search just headers (excluding
> Participants) or does it search headers and body (excluding
> Participants)? If it's the latter, this is a partial solution to
> Mike Miller's body-only searching request.

Thanks for telling us about Participant. It must be new.

It doesn't help me with my problem though. I want to find messages that
have "miller" in the text whether they have "miller" as a participant or
not. I also want to find messages that have "miller" in the message text,
whether or not "miller" is in the header. If I find all messages that do
not have "miller" as a participant, those messages still have "miller" in
the header. (That's because my e-mail address contains 'miller' and the
header includes the address in the "Received:" sections [see below].)

Mike

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

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

Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id NAA06048
for <[email protected]>; Fri, 3 Dec 1999 13:00:49 -0600 (CST)
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA13121;
Fri, 3 Dec 1999 10:58:27 -0800

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 11:59:44 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA14294;
Fri, 3 Dec 1999 11:59:43 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA31080;
Fri, 3 Dec 1999 11:59:43 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA23450;
Fri, 3 Dec 1999 11:55:56 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA85164
for <[email protected]>; Fri, 3 Dec 1999 11:41:47 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA19282
for <[email protected]>; Fri, 3 Dec 1999 11:41:46 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id NAA06177
for <[email protected]>; Fri, 3 Dec 1999 13:41:45 -0600 (CST)
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 13:41:45 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <Pine.OSF.4.21.9912031045190.12604-100000@goedel2.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, Eduardo Chappa L. wrote:

> Dear Mike,
>
> You can have pine checking automatically for new mail in your incoming
> folders. I wrote a patch that does that in any subset of the collection of
> incoming folder. Check it out in the address below. All comments are
> appreciated.
>
> Eduardo
> http://www.math.washington.edu/~chappa/pine/

Eduardo--

That looks like a great addition to pine. I won't use it though because I
have so much mail coming in from mailing lists that I don't want to hear
the bell dinging five times per minute. But if my situation were
different, I'd definitely use it. I hope they add it to pine as an
option.

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 12:12:31 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA24049;
Fri, 3 Dec 1999 12:12:29 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA29233;
Fri, 3 Dec 1999 12:12:29 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA24362;
Fri, 3 Dec 1999 12:08:38 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA23578
for <[email protected]>; Fri, 3 Dec 1999 12:04:11 -0800
Received: from vax.area.com (vax110.area.com [165.90.20.110])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA31311
for <[email protected]>; Fri, 3 Dec 1999 12:04:10 -0800
Received: (qmail 4788 invoked by uid 1828); 3 Dec 1999 20:04:08 -0000
Message-Id: <Pine.GSO.4.20.9912031203440.16538-100000@vax>
Date: Fri, 3 Dec 1999 12:04:08 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, Mike Miller wrote:
>That looks like a great addition to pine. I won't use it though because I
>have so much mail coming in from mailing lists that I don't want to hear
>the bell dinging five times per minute. But if my situation were

Look at:
quell-status-message-beeping:

It's your friend.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 12:30:50 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA03868;
Fri, 3 Dec 1999 12:30:48 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA29818;
Fri, 3 Dec 1999 12:30:48 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA27784;
Fri, 3 Dec 1999 12:25:50 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA73662
for <[email protected]>; Fri, 3 Dec 1999 12:18:29 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01405
for <[email protected]>; Fri, 3 Dec 1999 12:18:28 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id OAA06355
for <[email protected]>; Fri, 3 Dec 1999 14:18:20 -0600 (CST)
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 14:18:19 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <Pine.GSO.4.20.9912031203440.16538-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999 [email protected] wrote:

> On Fri, 3 Dec 1999, Mike Miller wrote:
> >That looks like a great addition to pine. I won't use it though because I
> >have so much mail coming in from mailing lists that I don't want to hear
> >the bell dinging five times per minute. But if my situation were
>
> Look at:
> quell-status-message-beeping:

Thanks, but I like having it ding when a new message enters Inbox, but I
don't like it to ding when a new message enters another Incoming Folder.
So I have what I want now. Selecting "quell" would turn off all beeping.

Regards,

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 12:41: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04464;
Fri, 3 Dec 1999 12:41:05 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32370;
Fri, 3 Dec 1999 12:41:04 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA26662;
Fri, 3 Dec 1999 12:36:15 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA18610
for <[email protected]>; Fri, 3 Dec 1999 12:29:48 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA03651
for <[email protected]>; Fri, 3 Dec 1999 12:29:47 -0800
Received: (qmail 13014 invoked from network); 3 Dec 1999 20:29:47 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 3 Dec 1999 20:29:47 -0000
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 13:31:02 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I accidentally erase the email send by, I believe, Eduardo about his
pine extension. Would you please resent that message?

Thanks,

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Fri, 3 Dec 1999, Mike Miller wrote:

> On Fri, 3 Dec 1999 [email protected] wrote:
>
> > On Fri, 3 Dec 1999, Mike Miller wrote:
> > >That looks like a great addition to pine. I won't use it though because I
> > >have so much mail coming in from mailing lists that I don't want to hear
> > >the bell dinging five times per minute. But if my situation were
> >
> > Look at:
> > quell-status-message-beeping:
>
>
> Thanks, but I like having it ding when a new message enters Inbox, but I
> don't like it to ding when a new message enters another Incoming Folder.
> So I have what I want now. Selecting "quell" would turn off all beeping.
>
> Regards,
>
> Mike
>
> --
> Michael B. Miller
> University of Missouri--Columbia
> http://taxa.psyc.missouri.edu/~mbmiller/
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 17:39: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA10985;
Fri, 3 Dec 1999 17:39:00 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA07869;
Fri, 3 Dec 1999 17:39:00 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA14731;
Fri, 3 Dec 1999 17:36:58 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA17672
for <[email protected]>; Fri, 3 Dec 1999 17:33:10 -0800
Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA06392
for <[email protected]>; Fri, 3 Dec 1999 17:33:09 -0800
Received: (from daemon@localhost)
by smtp02.primenet.com (8.9.3/8.9.3) id SAA11326;
Fri, 3 Dec 1999 18:32:19 -0700 (MST)
Received: from usr09.primenet.com(206.165.6.209)
via SMTP by smtp02.primenet.com, id smtpdAAA9taqew; Fri Dec 3 18:32:15 1999
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 20:32:19 -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: Catherine Thomas <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: delete empty folders fom PINE
In-Reply-To: <Pine.LNX.4.10.9912031707090.14845-100000@hix.physik.uni-bremen.de>
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-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

If there is a way of deleting empty folders automatically, the criteria
being that all messages have been removed, I would think twice about using
it. You may find yourself in some unexpected messes. Instead, when a
folder is empty and you wish to delete it, I would highlight it in list
folders and, instead of hitting the v as you would to read its contents,
check the bottom of the screen to see the remove folder command (which is
either d or r, I forget) and remove the folder that way.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 17:48:00 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02854;
Fri, 3 Dec 1999 17:47:59 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA08046;
Fri, 3 Dec 1999 17:47:58 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA16450;
Fri, 3 Dec 1999 17:46:20 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA23796
for <[email protected]>; Fri, 3 Dec 1999 17:42:24 -0800
Received: from nancy.downcity.net (nancy.downcity.net [199.105.120.3])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA07477
for <[email protected]>; Fri, 3 Dec 1999 17:42:24 -0800
Received: from usr210.downcity.net (usr210.downcity.net [209.4.146.210] (may be forged))
by nancy.downcity.net (8.8.6/8.8.6) with ESMTP id UAA16534
for <[email protected]>; Fri, 3 Dec 1999 20:51:41 -0500
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 20:41:56 -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: "David A. Desrosiers" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: delete empty folders fom PINE
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

That would definately be a very *VERY* bad thing, since I use
procmail and fetchmail to gather, sort, and batch my mail into my
40-odd-folders I keep. If I had them auto-deteleted when empty, I'd screw
up my nice clean recipies in procmail. They're not autocreated, so
auto-deleting them is not a good option. Perhaps a message counter next to
the folder in list view would be nice.

Just my 0.02c

+-----------------------------------------------------------+
| David A. Desrosiers *calloc(1,sizeof(geek)) |
| [email protected] http://www.gnu-designs.com |
| void main (void) { if (windows=="useful") hell=frozen } |
| PGP: 80F8 7FFF 8329 292F 2696 E354 3D9E 2800 5B8D ABC1 |
+-----------------------------------------------------------+

On Fri, 3 Dec 1999, Catherine Thomas wrote:

> If there is a way of deleting empty folders automatically, the criteria
> being that all messages have been removed, I would think twice about using
> it. You may find yourself in some unexpected messes. Instead, when a
> folder is empty and you wish to delete it, I would highlight it in list
> folders and, instead of hitting the v as you would to read its contents,
> check the bottom of the screen to see the remove folder command (which is
> either d or r, I forget) and remove the folder that way.
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 19:20: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA11544;
Fri, 3 Dec 1999 19:20:51 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA09501;
Fri, 3 Dec 1999 19:20:51 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA19087;
Fri, 3 Dec 1999 19:19:04 -0800
Received: from jason02.u.washington.edu ([email protected] [140.142.76.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA38114
for <[email protected]>; Fri, 3 Dec 1999 19:15:23 -0800
Received: from dante38.u.washington.edu ([email protected] [140.142.15.198])
by jason02.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA33548
for <[email protected]>; Fri, 3 Dec 1999 19:15:22 -0800
Received: from localhost (leibrand@localhost)
by dante38.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA13178
for <[email protected]>; Fri, 3 Dec 1999 19:15:21 -0800
Message-Id: <Pine.A41.4.21.9912031908000.105366-100000@dante38.u.washington.edu>
Date: Fri, 3 Dec 1999 19: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: delete empty folders fom PINE
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

But for those who don't use any mail delivery programs, you could simply
write a shell script to delete all 0-byte mail folder files. This of
course requires direct access to your mail folders, which not all IMAP
servers allow.

You can also select folders based on the number of messages they contain,
but since there's no apply command, this isn't very useful. I also
noticed when testing this that selecting folders by message count ( ; p c
from the folder list) doesn't work for Incoming Folders in 4.21. I'll
submit a bug report in a minute. :)

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Fri, 3 Dec 1999, Catherine Thomas wrote:

> If there is a way of deleting empty folders automatically, the criteria
> being that all messages have been removed, I would think twice about using
> it. You may find yourself in some unexpected messes. Instead, when a
> folder is empty and you wish to delete it, I would highlight it in list
> folders and, instead of hitting the v as you would to read its contents,
> check the bottom of the screen to see the remove folder command (which is
> either d or r, I forget) and remove the folder that way.
>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 19:39:45 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA12193;
Fri, 3 Dec 1999 19:39:44 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA09827;
Fri, 3 Dec 1999 19:39:43 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA02129;
Fri, 3 Dec 1999 19:38:03 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA25238
for <[email protected]>; Fri, 3 Dec 1999 19:35:26 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03159
for <[email protected]>; Fri, 3 Dec 1999 19:35:26 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id VAA11767
for <[email protected]>; Fri, 3 Dec 1999 21:35:25 -0600 (CST)
Message-Id: <[email protected]>
Date: Fri, 3 Dec 1999 21:35:25 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: delete empty folders fom PINE
In-Reply-To: <Pine.A41.4.21.9912031908000.105366-100000@dante38.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, Scott Leibrand wrote:

> But for those who don't use any mail delivery programs, you could simply
> write a shell script to delete all 0-byte mail folder files.

Remember that, since Pine 4.00, folders with zero messages do *not* have
zero bytes. They have 13 lines of "folder internal data."

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 3 Dec 1999 20:03:09 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA06843;
Fri, 3 Dec 1999 20:03:08 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA08008;
Fri, 3 Dec 1999 20:03:08 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA02727;
Fri, 3 Dec 1999 20:01:56 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA53040
for <[email protected]>; Fri, 3 Dec 1999 19:59:18 -0800
Received: from dante18.u.washington.edu ([email protected] [140.142.15.68])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA16774;
Fri, 3 Dec 1999 19:59:17 -0800
Received: from localhost (leibrand@localhost)
by dante18.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA60220;
Fri, 3 Dec 1999 19:59:17 -0800
Message-Id: <Pine.A41.4.21.9912031958210.39768-100000@dante18.u.washington.edu>
Date: Fri, 3 Dec 1999 19:59:17 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: delete empty folders fom PINE
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Ok. That shouldn't be too hard to take into account. It would be better
if we could apply commands to multiple selected folders, though, IMO.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Fri, 3 Dec 1999, Mike Miller wrote:

> On Fri, 3 Dec 1999, Scott Leibrand wrote:
>
> > But for those who don't use any mail delivery programs, you could simply
> > write a shell script to delete all 0-byte mail folder files.
>
>
> Remember that, since Pine 4.00, folders with zero messages do *not* have
> zero bytes. They have 13 lines of "folder internal data."
>
> Mike
>
> --
> Michael B. Miller
> University of Missouri--Columbia
> http://taxa.psyc.missouri.edu/~mbmiller/
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 4 Dec 1999 10:02:25 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA23333;
Sat, 4 Dec 1999 10:02:23 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20671;
Sat, 4 Dec 1999 10:02:23 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA18371;
Sat, 4 Dec 1999 09:59:21 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA57688
for <[email protected]>; Sat, 4 Dec 1999 09:55:11 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA30568
for <[email protected]>; Sat, 4 Dec 1999 09:55:10 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id LAA16608
for <[email protected]>; Sat, 4 Dec 1999 11:55:09 -0600 (CST)
Message-Id: <[email protected]>
Date: Sat, 4 Dec 1999 11:55:09 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I sent a script to the list yesterday that can be used to check incoming
mail folders. For me it was a little tricky to figure out how to make the
script show 'From:' and 'Subject:' fields for messages in the inbox. To
grab Subject lines, I wrote the following line of code:

tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | tail +2 | head -1 | egrep -v '^From: '

That worked pretty well as long as the 'Subject:' line followed (and did
not precede) the 'From:' line in every message. Unfortunately, 'Subject:'
lines sometimes precede 'From:' lines, and when they do, the script will
not display the 'Subject:' line. So I rewrote that one line of code as
follows:

tail +$item ~/mail/inbox | egrep '^From |^From: |^Subject: ' | head -3 | egrep '^Subject: '

This can only fail if a message has no true 'Subject:' line, but it has a
line beginning with 'Subject: ' in the message body. This can happen
(e.g., if a message with a Subject is forwarded within a message that
doesn't have a Subject), but it won't be a common problem.

The full revised script is appended. Let me know if you have any
suggestions for improvement.

Regards,

Mike

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

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

#!/usr/local/bin/tcsh -f
if ( `wc ~/mail/inbox | awk '{print $1}'` == 12 ) then
echo ""
echo "No mail in Inbox"
else
echo ""
tail +13 ~/mail/inbox | egrep '^From ' | wc | awk '{print "Listing of "$1" messages in your inbox:"}'
echo ""
foreach item ( `tail +13 ~/mail/inbox | egrep -n '^From ' | awk -F: '{print $1 + 12}'` )
tail +$item ~/mail/inbox | egrep '^From: ' | head -1
tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | head -2 | egrep '^Subject: '
echo ""
end
endif
echo ""
echo "Messages in other inboxes:"
echo ""
foreach file ( `ls -1 ~/mail/IN.* | awk -F. '{print $NF}'` )
echo "$file `tail +13 ~/mail/IN.$file | egrep '^From ' | wc`" | awk '{print $1" has "$2" messages"}' | grep -v ' 0 '
end
echo ""

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 4 Dec 1999 10:21:59 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA24188;
Sat, 4 Dec 1999 10:21:58 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA22551;
Sat, 4 Dec 1999 10:21:57 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA06425;
Sat, 4 Dec 1999 10:20:17 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA73658
for <[email protected]>; Sat, 4 Dec 1999 10:15:26 -0800
Received: from nancy.downcity.net (nancy.downcity.net [199.105.120.3])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16564
for <[email protected]>; Sat, 4 Dec 1999 10:15:25 -0800
Received: from usr031.downcity.net (usr031.downcity.net [209.4.146.31])
by nancy.downcity.net (8.8.6/8.8.6) with ESMTP id NAA17948
for <[email protected]>; Sat, 4 Dec 1999 13:24:55 -0500
Message-Id: <[email protected]>
Date: Sat, 4 Dec 1999 13:14:53 -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: "David A. Desrosiers" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I actually prefer the more strict regex as follows:

if ($line =~ /^From \S+ \w{3} \w{3} [ \d]\d \d{2}:\d{2}:\d{2} \d{4}/) {
do something;
}

+-----------------------------------------------------------+
| David A. Desrosiers *calloc(1,sizeof(geek)) |
| [email protected] http://www.gnu-designs.com |
| void main (void) { if (windows=="useful") hell=frozen } |
| PGP: 80F8 7FFF 8329 292F 2696 E354 3D9E 2800 5B8D ABC1 |
+-----------------------------------------------------------+

On Sat, 4 Dec 1999, Mike Miller wrote:

> I sent a script to the list yesterday that can be used to check incoming
> mail folders. For me it was a little tricky to figure out how to make the
> script show 'From:' and 'Subject:' fields for messages in the inbox. To
> grab Subject lines, I wrote the following line of code:
>
> tail +$item ~/mail/inbox | egrep '^From: |^Subject: ' | tail +2 | head -1 | egrep -v '^From: '
>
> That worked pretty well as long as the 'Subject:' line followed (and did
> not precede) the 'From:' line in every message. Unfortunately, 'Subject:'
> lines sometimes precede 'From:' lines, and when they do, the script will
> not display the 'Subject:' line. So I rewrote that one line of code as
> follows:
>
> tail +$item ~/mail/inbox | egrep '^From |^From: |^Subject: ' | head -3 | egrep '^Subject: '
>
> This can only fail if a message has no true 'Subject:' line, but it has a
> line beginning with 'Subject: ' in the message body. This can happen
> (e.g., if a message with a Subject is forwarded within a message that
> doesn't have a Subject), but it won't be a common problem.
>
> The full revised script is appended. Let me know if you have any
> suggestions for improvement.
>
> Regards,
>
> Mike
>
> --
> Michael B. Miller
> University of Missouri--Columbia
> http://taxa.psyc.missouri.edu/~mbmiller/

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 4 Dec 1999 22:32:19 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA32627;
Sat, 4 Dec 1999 22:32:18 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA31550;
Sat, 4 Dec 1999 22:32:17 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA18266;
Sat, 4 Dec 1999 22:29:35 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA30886
for <[email protected]>; Sat, 4 Dec 1999 22:24:42 -0800
Received: from stargate.kersur.net (stargate.kersur.net [199.79.199.128])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA30515
for <[email protected]>; Sat, 4 Dec 1999 22:24:42 -0800
Received: from localhost (nagilum@localhost)
by stargate.kersur.net (8.8.7/8.8.7) with SMTP id BAA27708
for <[email protected]>; Sun, 5 Dec 1999 01:24:45 -0500
Message-Id: <[email protected]>
Date: Sun, 5 Dec 1999 01:24:45 -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: Nagilum <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: bringing back an old thread Re: X-Sender
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi, before I pose my question I want to first mention that this was
already the subject of a message I found in the list archives:

http://www.washington.edu/pine/pine-info/1998.07/msg00150.html

My question is the same: is it possible to remove the X-Sender line from
outbound messages?

I believe the conclusion reached in that thread to be incorrect: I don't
think the MTA is putting that line in there, but rather the MUA (Pine) is,
and I'm looking for a way to prevent this. :)

I've done enough testing with different settings and toying with my MTA to
be reasonably confident that Pine is inserting this line. However, my
reasons for wanting to remove it are different from those of the original
poster's.

It could be considered an issue of security in a sense. Also of
convenience. Putting the X-Sender of the local userid who runs pine
basically nullifies all the reason I have for appreciating Pine's Role
support. Using a single instance of Pine for multiple accounts, and
replying to them with different roles, is a great concept but your base
username (and hence, your *other* e-mail address, which you may not want
others to see) is exposed in the current implementation.

This can also be a problem for sites which use an intermediary MTA to
perform address-to-user translation, for instance, the
'Jim.Breton=nagilum' scheme is foiled by the X-Sender (or Sender) line in
the headers.

I've looked at the source a bit and tried a few variations, but I always
end up breaking something and haven't really had the time yet to
investigate it more thoroughly. :) Does anyone know a reliable way of
disabling this feature?

Thanks!

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 5 Dec 1999 06:36:47 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA11334;
Sun, 5 Dec 1999 06:36:46 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA06104;
Sun, 5 Dec 1999 06:36:45 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA12105;
Sun, 5 Dec 1999 06:35:12 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA59670
for <[email protected]>; Sun, 5 Dec 1999 06:31:09 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA30719
for <[email protected]>; Sun, 5 Dec 1999 06:31:08 -0800
Received: from alephminus1.ii.com (alephminus1.ii.com [216.44.169.226])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id JAA13802;
Sun, 5 Dec 1999 09:31:06 -0500 (EST)
Message-Id: <Pine.WNT.4.21.9912050917530.-485937@alephminus1>
Date: Sun, 5 Dec 1999 09:22:20 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: delete empty folders fom PINE
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-03 David A. Desrosiers <[email protected]> wrote:
> That would definately be a very *VERY* bad thing, since I use
> procmail and fetchmail to gather, sort, and batch my mail into my
> 40-odd-folders I keep. If I had them auto-deteleted when empty, I'd screw
> up my nice clean recipies in procmail. They're not autocreated, so
> auto-deleting them is not a good option. Perhaps a message counter next to
> the folder in list view would be nice.

Procmail 13.3.1 *does* autocreate folders if they don't already
exist. I know this because I regularly download my incoming
folders to my PC using ftp and then they all get recreated by
procmail as the messages arrive. I think this has been true the
whole time I've been using procmail, which has been since 1994.

Nancy

--
For Procmail info, see www.ii.com/internet/robots/procmail/qs/
For Pine links, see http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
--= Sent via PINE 4.21: Internet News & Email for Win/Unix =--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 5 Dec 1999 07:32:43 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA12704;
Sun, 5 Dec 1999 07:32:42 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA08442;
Sun, 5 Dec 1999 07:32:42 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA02079;
Sun, 5 Dec 1999 07:31:25 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA84678
for <[email protected]>; Sun, 5 Dec 1999 07:27:02 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA18114
for <[email protected]>; Sun, 5 Dec 1999 07:27:02 -0800
Received: (qmail 17566 invoked from network); 5 Dec 1999 15:27:01 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 5 Dec 1999 15:27:01 -0000
Message-Id: <[email protected]>
Date: Sun, 5 Dec 1999 08:28:10 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: bringing back an old thread Re: X-Sender
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nagilum <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I think that the best way to do this is not in pine, but in an
intermediate process between pine and sendmail (or whatever mail sending
agent is in use). A simple perl (or shell script, although I lean to Perl
as being at least a little less cryptic, and if I were writing it myself I
would write it in C, but that is a minority opinion)... Where was I? Oh
yes, a simple Perl script can remove the information that you want and
then forward the message to sendmail.

There is another mail program, which I don't like nearly as much as Pine,
that will allow you to edit the headers directly before sending. It is
called "mutt".

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Sun, 5 Dec 1999, Nagilum wrote:

> Hi, before I pose my question I want to first mention that this was
> already the subject of a message I found in the list archives:
>
> http://www.washington.edu/pine/pine-info/1998.07/msg00150.html
>
> My question is the same: is it possible to remove the X-Sender line from
> outbound messages?
>
> I believe the conclusion reached in that thread to be incorrect: I don't
> think the MTA is putting that line in there, but rather the MUA (Pine) is,
> and I'm looking for a way to prevent this. :)
>
> I've done enough testing with different settings and toying with my MTA to
> be reasonably confident that Pine is inserting this line. However, my
> reasons for wanting to remove it are different from those of the original
> poster's.
>
> It could be considered an issue of security in a sense. Also of
> convenience. Putting the X-Sender of the local userid who runs pine
> basically nullifies all the reason I have for appreciating Pine's Role
> support. Using a single instance of Pine for multiple accounts, and
> replying to them with different roles, is a great concept but your base
> username (and hence, your *other* e-mail address, which you may not want
> others to see) is exposed in the current implementation.
>
> This can also be a problem for sites which use an intermediary MTA to
> perform address-to-user translation, for instance, the
> 'Jim.Breton=nagilum' scheme is foiled by the X-Sender (or Sender) line in
> the headers.
>
> I've looked at the source a bit and tried a few variations, but I always
> end up breaking something and haven't really had the time yet to
> investigate it more thoroughly. :) Does anyone know a reliable way of
> disabling this feature?
>
> Thanks!
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 5 Dec 1999 21:08:34 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA19004;
Sun, 5 Dec 1999 21:08:32 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA18974;
Sun, 5 Dec 1999 21:08:31 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA13895;
Sun, 5 Dec 1999 21:05:17 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA11362
for <[email protected]>; Sun, 5 Dec 1999 20:59:52 -0800
Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA10631
for <[email protected]>; Sun, 5 Dec 1999 20:59:51 -0800
Received: from localhost (mbmiller@localhost)
by taxa.psyc.missouri.edu (8.9.3/8.9.0) with ESMTP id WAA20941
for <[email protected]>; Sun, 5 Dec 1999 22:59:50 -0600 (CST)
Message-Id: <[email protected]>
Date: Sun, 5 Dec 1999 22:59:50 -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: Mike Miller <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <Pine.OSF.4.21.9912021816550.26619-100000@goedel1.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO list <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 2 Dec 1999, Eduardo Chappa L. wrote:

> *** Mike Miller ([email protected]) wrote today:
>
> :) Why not make Y, U, @, S, and W also compatible, at least for those
> :) of us who select "Enable emacs key bindings" or somesuch?
> :)
>
> Well, you have a difficult opposition here. According to the source
> code, there is no way (and won't be implemented) to associate
> arbitrary keys with functions. So you are out of luck here.

I guess you mean that major changes to the code would have to be made.
Maybe you mean that there comments in the code stating that this will
never be implemented. OK, maybe I'll never have it. Maybe it's just too
tricky to make changes in some of the key bindings because it messes up
other ones.

> I think that adapting the source code to the needs of very advanced
> users is a big task. Some features may not come out if this does not
> happen, at least that is what I see from reading the source code.

How hard would it be for me to change the source code so that, while I'm
editing text in pine, ^Y does what ^U used to do, Meta-V does what ^Y used
to do, Meta-F does what ^@ (or Ctrl-space) used to do, and Meta-B does
"previous word." Maybe the "previous word" functionality would be hard to
add, but can't I change some of the others by changing a few lines of code
somewhere?

Thanks for your comments,

Mike

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 6 Dec 1999 09:06: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA01050;
Mon, 6 Dec 1999 09:06:21 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA32602;
Mon, 6 Dec 1999 09:06:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA08432;
Mon, 6 Dec 1999 09:01:52 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA38336
for <[email protected]>; Mon, 6 Dec 1999 08:56:30 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA27616
for <[email protected]>; Mon, 6 Dec 1999 08:56:30 -0800
Received: from goedel2.math.washington.edu ([email protected] [128.95.224.11])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id IAA15903;
Mon, 6 Dec 1999 08:56:25 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912060831510.22342-100000@goedel2.math.washington.edu>
Date: Mon, 6 Dec 1999 08:56:24 -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 L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: keybindings and "previous word"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello Mike,

Pico can be modified in several ways to do new (fixed) key-binding. There
are two files which you'll have to take a look at: pico/ebind.h and
pico/basic.c

In pico/ebind.h you will find the binding of keys and functions, eg:

{CTRL|'A', gotobol}

gotobol is a function (GOTO the Beginning Of the current Line), which you
will find in pico/basic.c. This is one way to hack the code to redefine
key functions. You can create your own functions. See basic.c to see what
are the parameters of the function. Pico and Pine are very well written,
so you should not have problems in finding the funtions that you need to
use in order to implement any functionality you like. I was thinking of
implementing the previous word function, but I guess I have to figure out
a key binding first. It's kind of tricky...

The above described way is my recommended way to add new/different
functionality for keys. Notice that keys are defined twice in this way in
ebind.h, that is because the funtionality of keys is different in pico and
pine (look at the definition of CTRL|'C').

If you want examples of how I have changed functionality of keys, look at
the patch for "delete paragraphs" in my web page (address below).

On the other hand, take a look at the file pico/main.c, you can also
change keybinding by changing code before the line execute_cmd in the
module main. This is only useful is you want to remap CTRL|'A' to be
CTRL|'E' or so, but I guess it is easier to hack pico/ebind.h (look at
my patch for actualized status line)

I do not recall where the key-binding of the function keys is, I can find
it if you are interested.

I hope this helps. Contact me if you think I can be of any help.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 6 Dec 1999 09:19:28 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00960;
Mon, 6 Dec 1999 09:19:26 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA32033;
Mon, 6 Dec 1999 09:19:26 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA02276;
Mon, 6 Dec 1999 09:16:27 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA34066
for <[email protected]>; Mon, 6 Dec 1999 09:12:00 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA05149
for <[email protected]>; Mon, 6 Dec 1999 09:12:00 -0800
Received: from goedel2.math.washington.edu ([email protected] [128.95.224.11])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id JAA16781;
Mon, 6 Dec 1999 09:11:59 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912060857120.22342-100000@goedel2.math.washington.edu>
Date: Mon, 6 Dec 1999 09:11: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: incoming folders (was Re: Ok, here I go again!)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Mike Miller <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Mike Miller ([email protected]) wrote on Dec 3, 1999:
:)
:) Eduardo--
:)
:) That looks like a great addition to pine. I won't use it though because I
:) have so much mail coming in from mailing lists that I don't want to hear
:) the bell dinging five times per minute. But if my situation were
:) different, I'd definitely use it. I hope they add it to pine as an
:) option.
:)

Thanks Mike for your comment, The patch actually only notifies you when
there is new mail in a folder, not when new mail arrives to it. Here is
the way the patch works. Say you have new mail in folder1, then you would
get a message saying:

[You have new mail in "folder1"]

and a beep would sound. Say you ignore this message and don't read your
new mail in folder1, and you receive a new message in folder1, then you
won't get a message about it, because you already received a message about
it before. I do not think it would be difficult to implement a message
every time a new message is received, but as you point out, sometimes this
would be more annoying than helpful.

Now say you did not read the new message in folder1 and receive a new
message in folder2, then you would receive the message:

[You have new mail in "folder1" and "folder2"]

and a beep would sound. It is easy to implement a configuration option
that won't make the beep sound on arrival of new messages, if this is all
you care (I'll add that to the patch, it seems to me a good sugegstion).

On the other hand the patch includes a key-binding for CTRL|'H', to
check for new mail in incoming folders other than INBOX, which would send
you either a message like the one above or "no new message in incoming
folders". Also if the message is too long to be displayed in the status
line a generic message warning you about existence of new mail will be
sent to you.

I'll add the feature that you requested to the patch, if yo are
interested I will let you knwo when I have it ready. Thanks again for your
comments and all feedback, bugs reports, suggestions,etc are appreciated,

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 6 Dec 1999 10:48: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03680;
Mon, 6 Dec 1999 10:48:51 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03197;
Mon, 6 Dec 1999 10:48:51 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA14828;
Mon, 6 Dec 1999 10:45:49 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA84558
for <[email protected]>; Mon, 6 Dec 1999 10:38:52 -0800
Received: from tunku.uady.mx (tunku.uady.mx [148.209.1.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA23867
for <[email protected]>; Mon, 6 Dec 1999 10:38:49 -0800
Received: from localhost (angel@localhost)
by tunku.uady.mx (8.9.1/8.9.1) with SMTP id MAA24834
for <[email protected]>; Mon, 6 Dec 1999 12:35:17 -0600 (CST)
Message-Id: <[email protected]>
Date: Mon, 6 Dec 1999 12:35:17 -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: =?ISO-8859-1?Q?Polanco_Rodr=EDguez_=C1ngel?= <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: suport please
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi to all,

I'm new in this list. We have a man network im our university.
We use PINE in our mail server and our users have PINE as client.
We have more or less 1,200 users.

The problem is:

Pine is generated files as .pine-debug, .pinerc an another files in the
/var/mail of users. Another files are example angel8765439876542 and these
files are bigs.
Some had problems as this?

Our operative system is solaris (netra-sun).

By the comments, thanks in advance.

************************************
| Q.B.B.ANGEL G. POLANCO RODRIGUEZ |
| UNIVERSIDAD AUTONOMA DE YUCATAN |
| DIRECCION GENERAL DE |
| DESARROLLO ACADEMICO |
| DEPARTAMENTO DE TELEINFORMATICA|
| CALLE 59 POR AV. ITZAEZ # 490 |
| MERIDA, YUCATAN, MEXICO |
| CODIGO POSTAL : 97 000 |
| TELEFONO:52 (99) 23 74 28 |
| E-mail: [email protected] |
************************************

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 6 Dec 1999 11:39:51 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05501;
Mon, 6 Dec 1999 11:39:49 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05001;
Mon, 6 Dec 1999 11:39:48 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA18316;
Mon, 6 Dec 1999 11:35:06 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA47588
for <[email protected]>; Mon, 6 Dec 1999 11:30:25 -0800
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02641
for <[email protected]>; Mon, 6 Dec 1999 11:30:24 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA17567;
Mon, 6 Dec 1999 11:30:24 -0800
Received: from localhost (hubert@localhost)
by shiva1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27438;
Mon, 6 Dec 1999 11:30:23 -0800
Message-Id: <Pine.GUL.4.30.9912061127530.23318-100000@shiva1.cac.washington.edu>
Date: Mon, 6 Dec 1999 11:30:23 -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: Tokens
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Collantes <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

David,
The way this works is that the tokens may be in the reply-indent-string,
but you can't add them manually by editing. Insted, the
reply-indent-string is detokenized before you are given the chance to edit
it. It makes sense that you might want to do what you're trying but we
didn't think of that when we designed it. Thanks.

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

On Thu, 2 Dec 1999, David Collantes wrote:

>
> Howdy!
>
> I have Pine 4.20 running (soon to be upgraded to 4.21) and I have set OM#
> as the reply indent string. On the Help I saw that I could use several
> tokens also. I have the allow editing of the string (^R), but when I type
> _FROM_ to be used as the string, no replacement is made, in other words,
> the message will read at the recipient client:
>
> _FROM_ In here the test of the message being replied.
> _FROM_ In here the test of the message being replied.
> _FROM_ In here the test of the message being replied.
>
> What I am doing wrong? Is that a bug or I am missing something? What
> should I do to be able to use the tokens?
>
> Cheers,
>
> ,----------------------------------.,-----------------------------------.
> | David Collantes || email: [email protected] |
> | Senior Systems Administrator, || phone: (407) 823-3418 |
> | Network Operations Manager || UCFBusiness - UCF, Orlando, FL |
> `----------------------------------'`-----------------------------------'

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 6 Dec 1999 14:49:04 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA06552;
Mon, 6 Dec 1999 14:49:03 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA11447;
Mon, 6 Dec 1999 14:49:03 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA10386;
Mon, 6 Dec 1999 14:46:00 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA54538
for <[email protected]>; Mon, 6 Dec 1999 14:41:56 -0800
Received: from mail.mankato.msus.edu (Mail.Mankato.MSUS.EDU [134.29.1.12])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA25159;
Mon, 6 Dec 1999 14:41:43 -0800
Received: from bs1.mankato.msus.edu ([email protected] [134.29.1.244])
by mail.mankato.msus.edu (8.9.3/8.9.3) with ESMTP id QAA20005;
Mon, 6 Dec 1999 16:41:33 -0600 (CST)
Message-Id: <[email protected]>
Date: Mon, 6 Dec 1999 16:41:30 -0600 (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: Jeffrey Hundstad <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Problem/Bug?: 4.21 by-recipient fcc fails if folder exists.
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
X-To: [email protected], [email protected],
[email protected]
X-Cc: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have this exact same problem. We're also are running Pine 4.21
against an SMS IMAP server.

When you try to send with FCC as sent-mail it says:

Folder "sent-mail" in <Mail on mail.mankato.msus.edu> doesn't exist. Creat?
when you say "Y" it responds with:

[Fcc Error: "Mailbox already exists". Message NOT sent or copied.]

If you set the FCC to:

{mail.mankato.msus.edu}inbox.sent-mail

it works just fine.

This folder also works fine with Pine 3.96 w/o the long format needed.

BTW: our exact version of SMS is:
Execmail IMAP4rev1 (2.1.2/199906021506)
* CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+
UIDPLUS NAMESPACE X-NON-HIERARCHICAL-RENAME
X-NO-ATOMIC-RENAME

Sincerely,

Jeffrey E. Hundstad
Linux/AS/400 System&Network/News/WWW/Anon. FTP/Majordomo/Admin.
Computer Services Box 45
Minnesota State University, Mankato
Mankato Minnesota, USA 56002-8400
44 8'N 93 59'W El. 1000'
[email protected]
http://www.mankato.msus.edu/jeffrey/
PGP Key fingerprint = FF EE F5 C0 3A A0 26 1A D2 73 AE 30 5F E2 2E 2C
GPG Key fingerprint = 34FB A7CA E40B B729 7135 26BC 5440 3E69 4787 3761
(507) 389-2516 Work
(507) 389-6115 Fax
(507) 625-7643 Home

On Tue, 30 Nov 1999, jan grant <[email protected]> wrote:
> I'm running Pine 4.21 against the SMS Imap server
>
> ( * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ OPTIMIZE-1
> X-NON-HIERARCHICAL-RENAME X-NO-ATOMIC-RENAME )
>
> and I'm running into the following problem when fcc-name-rule is
> by-recipient.
>
> If I compose an email to a user without a corresponding folder, I'm
> prompted that the folder doesn't exist. I can create it, and the fcc
> works.
>
> If I then send a second email to that use, I'm again prompted that the
> folder doesn't exist, but when I ask to create it I get an error (folder
> already exists).
>
> -From pine -d imap=4: (first time, unimportant bits elided)
>
> ---- COMPOSER ----
> [General preamble goes here]
>
> IMAP DEBUG 09:32:49 11/24: 0000000e LIST "" Inbox.jan
> IMAP DEBUG 09:32:49 11/24: 0000000e OK Completed
> Want_to read: RETURN (13)
> IMAP DEBUG 09:32:49 11/24: 0000000f Create Inbox.jan
> IMAP DEBUG 09:32:50 11/24: 0000000f OK Completed
> IMAP 09:32:50 11/24 mm_log babble: Completed
> Opened SMTP server "outgoing-smtp.blah.blah.blah"
> done.
> IMAP DEBUG 09:32:50 11/24: 00000010 APPEND Inbox.jan {403}
> IMAP DEBUG 09:32:50 11/24: + go ahead
> IMAP DEBUG 09:32:50 11/24:
> IMAP DEBUG 09:32:50 11/24: 00000010 OK [APPENDUID 943435970 1] Completed
> IMAP mm_notify NIL : {localhost:143/imap/user="jan"}inbox (inboxstream)
> : [APPENDUID 943435970 1] Completed
> === folder_screen called ====
>
> And the second time around:
>
> ---- COMPOSER ----
> [preamble deleted]
> IMAP DEBUG 09:32:59 11/24: 00000012 LIST "" Inbox.jan
> IMAP DEBUG 09:32:59 11/24: * LIST () "." Inbox.jan
> mm_list "{localhost}Inbox.jan": delim: '.',
> IMAP DEBUG 09:32:59 11/24: 00000012 OK Completed
> Want_to read: RETURN (13)
> IMAP DEBUG 09:33:00 11/24: 00000013 Create Inbox.jan
> IMAP DEBUG 09:33:00 11/24: * 7 EXISTS
> === mm_exists(7,{localhost:143/imap/user="jan"}inbox) called ===
> IMAP DEBUG 09:33:00 11/24: * 1 RECENT
> IMAP DEBUG 09:33:00 11/24: 00000013 NO Mailbox already exists
> IMAP 09:33:00 11/24 mm_log ERROR: Mailbox already exists
>
> What gives?
>
> Any help would be appreciated. It looks like Pine isn't recognising
> Inbox.jan as a valid folder.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 02:45:22 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA19648;
Tue, 7 Dec 1999 02:45:20 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA25245;
Tue, 7 Dec 1999 02:45:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA22019;
Tue, 7 Dec 1999 02:42:34 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA14160
for <[email protected]>; Tue, 7 Dec 1999 02:39:36 -0800
Received: from smtp2.nikoma.de (smtp2.nikoma.de [212.122.128.25])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA09201
for <[email protected]>; Tue, 7 Dec 1999 02:39:35 -0800
Received: from localhost.localdomain (ppp2-194.tnt01.ffm.nikoma.de [212.122.145.194])
by smtp2.nikoma.de (8.9.3/8.9.3) with ESMTP id MAA46718
for <[email protected]>; Wed, 8 Dec 1999 12:38:21 +0100 (CET)
(envelope-from [email protected])
Received: from localhost (claus@localhost)
by localhost.localdomain (8.9.3/8.9.3) with ESMTP id JAA00607
for <[email protected]>; Tue, 7 Dec 1999 09:05:05 +0100
Message-Id: <[email protected]>
Date: Tue, 7 Dec 1999 09:05:05 +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: Claus Atzenbeck <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: reading other's inbox
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: pine-info <[email protected]>
X-Authentication-Warning: localhost.localdomain: claus owned process doing -bs
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

I'm using pine as my mail reader. I have my own INBOX (owner "claus")
and the inbox of another user (named "ane"). Procmail is delivering
the mail to both inboxes. As root I've changed the owner of the other
user's inbox to my user name (in /var/spool/mail):

-rw------- 1 claus claus 555 Dec 6 11:18 ane

But every time procmail is putting new mail into this inbox, it
renames also the owner (actually it copies the old inbox to a new file
and creates a new file with the owner "ane":

-rw------- 1 claus claus 555 Dec 6 11:18 BOGUS.ane.gjW
-rw------- 1 ane ane 1939 Dec 7 07:49 ane

What can I do in order to be able to read ane's mail with pine?

Regards,
Claus.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 06:25: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA27679;
Tue, 7 Dec 1999 06:25:48 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA28793;
Tue, 7 Dec 1999 06:25:48 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA24862;
Tue, 7 Dec 1999 06:23:43 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA61362
for <[email protected]>; Tue, 7 Dec 1999 06:20:41 -0800
Received: from blkbox.com ([email protected] [206.109.97.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA30784
for <[email protected]>; Tue, 7 Dec 1999 06:20:41 -0800
Received: from localhost (swhatley@localhost)
by blkbox.com (8.8.7/8.8.7) with SMTP id IAA02746
for <[email protected]>; Tue, 7 Dec 1999 08:20:40 -0600 (CST)
Message-Id: <[email protected]>
Date: Tue, 7 Dec 1999 08:20:40 -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: Steven Whatley <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Compiling pine under Cygwin
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

HI all,

I was wondering if pine (specifically pico) has been compiled under
cygwin. For those who don't know, Cygwin is a UNIX API for Windows NT
from <http://sourceware.cygnus.com/cygwin/>. I know there is PC-Pine but
PC-Pine is not cygwin aware. I'd like to use the pico editor with tin.
Any info will be appreciated.

Thanks,
Steven

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 06:30:05 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA28179;
Tue, 7 Dec 1999 06:30:03 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA28851;
Tue, 7 Dec 1999 06:30:03 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA04524;
Tue, 7 Dec 1999 06:27:51 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA60152
for <[email protected]>; Tue, 7 Dec 1999 06:21:48 -0800
Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA12140
for <[email protected]>; Tue, 7 Dec 1999 06:21:48 -0800
Received: from eis.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP;
Tue, 7 Dec 1999 14:21:38 +0000
Received: from bristol.ac.uk (tribble.ilrt.bris.ac.uk [137.222.34.34]) by eis.bris.ac.uk (8.9.3/8.9.3)
with ESMTP id OAA23584; Tue, 7 Dec 1999 14:19:31 GMT
Message-Id: <[email protected]>
Date: Tue, 07 Dec 1999 14:19:30 +0000
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: jan grant <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: BUG: more folder creation problems with Pine 4.21
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Cc: [email protected]
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Again, running a vanilla Pine 4.21 on HP-UX 10.20 against SMS imapd
(which is a rebadged cyrus, as far as I can tell).

Had a complaint this morning from a user whose sentmail folder was
renamed sentmail-dec-99 (or whatever).

Pine created him a new sentmail folder, and now refuses to recognise it.

Composition of messages bombs out at the send with the two messages:

1. sentmail doesn't exist? Create?
to which you must answer "yes" to proceed, then:
2. Can't create folder (Folder "sentmail" already exists")
fcc fails, the send fails, and everyone grinds thei teeth.

Help!

jan

PS. I've tried this with and without the lame-list setting.
--
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 [email protected]
Unfortunately, I have a very good idea of how fast my keys are moving.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 09:31:58 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA19276;
Tue, 7 Dec 1999 09:31:57 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00533;
Tue, 7 Dec 1999 09:31:56 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA02652;
Tue, 7 Dec 1999 09:28:01 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA64278
for <[email protected]>; Tue, 7 Dec 1999 09:24:06 -0800
Received: from law.usc.edu (law.usc.edu [128.125.42.6])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA27536
for <[email protected]>; Tue, 7 Dec 1999 09:24:05 -0800
Received: from l2122.usc.edu (l2122 [128.125.42.67])
by law.usc.edu (Pro-8.9.3/8.9.3) with ESMTP id JAA11208
for <[email protected]>; Tue, 7 Dec 1999 09:24:39 -0800 (PST)
Message-Id: <[email protected]>
Date: Tue, 7 Dec 1999 09:23:49 -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: requested feature, unless I'm missing something
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi all,
I was wondering if there is a feature to separate attachments from
email, sort of like how Eudora has a directory to automatically move
attachments to a directory. If not, I request that this become a feature.
I am encountering many users who receive hundreds of attachments, and
keeping them in the same 'folder' as the email is causing lots of slowness
when they try to navigate among their folders. I would tell them to just
delete the attachment, but I don't think that's a feature either.
(Unless they reply the email to themselves and delete the original, but
that's pushing it for my users).

I was thinking something that would work the same in PC-Pine or regular
Pine, so maybe have an 'attach' directory in c:\pine and/or
~/user/attach. And then have a couple options like...

[Attachment Options]

[ ] enable-local-attachments (for PC-Pine only?)
[ ] enable-remote-attachments
[ ] search-all-attachment-folders
[ ] enable-copy-to-local-then-delete (again for PC-Pine only? for someone
who uses both - which is half my users)

Delete from remote after (this I guess could tie in to the
monthly sent-mail check?)
[ ] 1 week [ ] 2 weeks [ ] 1 month

Of course, this might necessitate creating an Attachment folder interface
(in addition to the mail folders and addressbooks) that's intelligent
enough to add a line in the email to show where the file actually went
(remote or local, depending on usage of PC-Pine.)

If this does become a feature, then I won't have to consider Eudora or
Netscape Mail as much when I review email clients next year and my users
won't have ammo to sway my bosses. ;) I also understand that this would
be a difficult and complicated task to complete, so my thanks to the Pine
team in advance for consideration.

Robert

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

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 12:20:33 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01548;
Tue, 7 Dec 1999 12:20:30 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05960;
Tue, 7 Dec 1999 12:20:30 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA05444;
Tue, 7 Dec 1999 12:16:58 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA11396
for <[email protected]>; Tue, 7 Dec 1999 12:13:08 -0800
Received: from dante06.u.washington.edu ([email protected] [140.142.15.8])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA18094;
Tue, 7 Dec 1999 12:13:06 -0800
Received: from localhost (leibrand@localhost)
by dante06.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA106512;
Tue, 7 Dec 1999 12:13:05 -0800
Message-Id: <Pine.A41.4.21.9912071209280.46250-100000@dante06.u.washington.edu>
Date: Tue, 7 Dec 1999 12:13:05 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something
In-Reply-To: <[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-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

There IS an option to remove an attachment from an e-mail without
re-sending it. Although this is by no means automatic as you'd like, you
may be able to make it so. Here's what you do:

Open the message and view the attachment list. Save the attachment to a
file as you would normally. Press D to delete the attachment. Press < to
get back to the message body, and press S to save the message. Choose the
folder it's already in, or another folder if you like. Confirm that you
want to save the message without its attachments, and then you'll have a
fresh copy of the messase, sans attachments, and the old copy will be
marked Deleted.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Tue, 7 Dec 1999, Robert Larmon wrote:

>
> Hi all,
> I was wondering if there is a feature to separate attachments from
> email, sort of like how Eudora has a directory to automatically move
> attachments to a directory. If not, I request that this become a feature.
> I am encountering many users who receive hundreds of attachments, and
> keeping them in the same 'folder' as the email is causing lots of slowness
> when they try to navigate among their folders. I would tell them to just
> delete the attachment, but I don't think that's a feature either.
> (Unless they reply the email to themselves and delete the original, but
> that's pushing it for my users).
>
> I was thinking something that would work the same in PC-Pine or regular
> Pine, so maybe have an 'attach' directory in c:\pine and/or
> ~/user/attach. And then have a couple options like...
>
> [Attachment Options]
>
> [ ] enable-local-attachments (for PC-Pine only?)
> [ ] enable-remote-attachments
> [ ] search-all-attachment-folders
> [ ] enable-copy-to-local-then-delete (again for PC-Pine only? for someone
> who uses both - which is half my users)
>
> Delete from remote after (this I guess could tie in to the
> monthly sent-mail check?)
> [ ] 1 week [ ] 2 weeks [ ] 1 month
>
> Of course, this might necessitate creating an Attachment folder interface
> (in addition to the mail folders and addressbooks) that's intelligent
> enough to add a line in the email to show where the file actually went
> (remote or local, depending on usage of PC-Pine.)
>
> If this does become a feature, then I won't have to consider Eudora or
> Netscape Mail as much when I review email clients next year and my users
> won't have ammo to sway my bosses. ;) I also understand that this would
> be a difficult and complicated task to complete, so my thanks to the Pine
> team in advance for consideration.
>
> Robert
>
>
>
> ```````````````````````````````````````````````````````````````````````
> ` Robert Larmon `
> ` PC Systems Analyst `
> ` USC Law School Computing Services `
> ` [email protected] `
> '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>
>
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 14:17:34 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA04404;
Tue, 7 Dec 1999 14:17:33 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA08725;
Tue, 7 Dec 1999 14:17:33 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA10804;
Tue, 7 Dec 1999 14:13:12 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA11294
for <[email protected]>; Tue, 7 Dec 1999 14:10:08 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA23294
for <[email protected]>; Tue, 7 Dec 1999 14:10:08 -0800
Received: from goedel2.math.washington.edu ([email protected] [128.95.224.11])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id OAA24674
for <[email protected]>; Tue, 7 Dec 1999 14:10:07 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912071407120.25609-100000@goedel2.math.washington.edu>
Date: Tue, 7 Dec 1999 14:10: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something (fwd)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I am forwarding this followup of an e-mail sent by Robert Larmon earlier
today.

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

>
> :) [Attachment Options]
> :)
> :) [ ] enable-local-attachments (for PC-Pine only?)
> :) [ ] enable-remote-attachments
> :) [ ] search-all-attachment-folders
> :) [ ] enable-copy-to-local-then-delete (again for PC-Pine only? for someone
> :) who uses both - which is half my users)
> :)
> :) Delete from remote after (this I guess could tie in to the
> :) monthly sent-mail check?)
> :) [ ] 1 week [ ] 2 weeks [ ] 1 month
> :)
> I do not have clear what all these feature mean by just reading their
> names, maybe you would have liked to have explained what each one does and
> how they all work together.

When I say 'local', I mean, for PC-Pine. Basically, I was thinking of
something that would work for both Pine and PC-Pine, since my users use
both. If you enable-local-attachments, it would create or add to a
directory called c:\pine\attachments, or (in my mind, a better place)
c:\my documents\attachments (see below for more comments on this).

The reason I put 'enable-local...' and 'enable-remote...' is that PC-Pine
has some features that Pine doesn't have, and I thought a logical
separation might be necessary.

The 'search-all-attach...' feature might search both local and remote
systems when you want to search for an attachment that you are looking
for. (Sort of like a customized Windows search combined with a Unix
search of just the user's directories and the results displayed in the
same window)

The '...copy-then-delete...' would have PC-Pine automatically check the
remote ~/attach directory, maybe after a set time limit that can be
changed in .pinerc. If there are files on ~/attach meeting the criteria,
then it would copy the files to c:\my documents\attachments automatically,
thus saving the user from having to manually copy the files over and
saving server space.

In addition, the 'delete from remote...' might tie in with the monthly
sent-mail check, asking the user if they want to move the files to their
hard drive in order to save space. Or, I was just thinking, you could
also have it check the attach directory size (greater than x megabytes,
the x settable by .pinerc), and then ask if it qualifies.

I was also thinking of having c:\my documents\attachments used as a
central repository for attaching/storing attachments. What do you
think? When you have 30 different apps saving to 30 different places,
it's nice to have one directory structure. It's also great for backups,
when you don't want to backup system/app files when you're just trying to
backup user files instead of the whole hard drive.

If you think this would benefit the list, please forward it to them.

Also, sorry for not fully communicating my thoughts on the options. I had
it all in my mind and got lazy :)

Robert

```````````````````````````````````````````````````````````````````````
` Robert Larmon `
` PC 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-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 20:45: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA08538;
Tue, 7 Dec 1999 20:45:13 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA18025;
Tue, 7 Dec 1999 20:45:12 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA26805;
Tue, 7 Dec 1999 20:41:56 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA38618
for <[email protected]>; Tue, 7 Dec 1999 20:39:19 -0800
Received: from itlinfosys.com (infosys.itlinfosys.com [206.236.143.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id UAA24886
for <[email protected]>; Tue, 7 Dec 1999 20:39:18 -0800
Received: from viruswall1 by itlinfosys.com (SMI-8.6/SMI-SVR4)
id UAA10238; Tue, 7 Dec 1999 20:39:15 -0800
Received: from 192.168.139.6 by viruswall1 (InterScan E-Mail VirusWall NT); Tue, 07 Dec 1999 20:45:58 -0800 (Pacific Standard Time)
Received: from kec-01-msg.kec.inf.com (KEC-01-MSG [204.4.54.41]) by gatemsg02.itlinfosys.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
id X8DWZVW5; Tue, 7 Dec 1999 20:32:32 -0800
Received: from [204.4.55.198] (204.4.55.198 [204.4.55.198]) by kec-01-msg.kec.inf.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
id YG1TLJHJ; Wed, 8 Dec 1999 10:07:54 +0530
Received: from infpc155 by [204.4.55.198]
via smtpd (for kec-01-msg.kec.inf.com [204.4.54.41]) with SMTP; 8 Dec 1999 04:39:48 UT
Received: from ipkpc275 (IDENT:ssaxena@ipkpc275 [206.236.134.125])
by sandesh.ntl.inf.com (8.9.3/8.9.3) with ESMTP id MAA09250
for <[email protected]>; Wed, 8 Dec 1999 12:40:13 +0400
Message-Id: <Pine.LNX.4.21.9912081003150.6557-100000@ipkpc275.infosys.ernet.in>
Date: Wed, 8 Dec 1999 10:10:13 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Shobhit Saxena <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something
In-Reply-To: <Pine.A41.4.21.9912071209280.46250-100000@dante06.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This sure is one way of getting rid of attachments from the messages.
However, i feel some enhancement in this Pine feature is still in order.
If some command analogous to the 'eXpunge' command of the message index
screen is introduced here, it would save all this effort of saving the
message in some folder to get rid of attachments. Then, we can just mark
the attachments as deleted and then eXpunge, so that the attachments are
deleted from the disk files as well. I don't know how feasible it is to
implement this new feature, but it would certainly be very useful.

--
Be warned that typing killall name may not have the desired
effect on non-Linux systems, especially when done by a privileged user.
(From the killall manual page)

On Tue, 7 Dec 1999, Scott Leibrand wrote:

> There IS an option to remove an attachment from an e-mail without
> re-sending it. Although this is by no means automatic as you'd like, you
> may be able to make it so. Here's what you do:
>
> Open the message and view the attachment list. Save the attachment to a
> file as you would normally. Press D to delete the attachment. Press < to
> get back to the message body, and press S to save the message. Choose the
> folder it's already in, or another folder if you like. Confirm that you
> want to save the message without its attachments, and then you'll have a
> fresh copy of the messase, sans attachments, and the old copy will be
> marked Deleted.
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 7 Dec 1999 23:49: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA25328;
Tue, 7 Dec 1999 23:49:19 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA20930;
Tue, 7 Dec 1999 23:49:19 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA02036;
Tue, 7 Dec 1999 23:47:53 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA47494
for <[email protected]>; Tue, 7 Dec 1999 23:43:45 -0800
Received: from rri.res.in ([email protected] [202.54.37.67])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA19177
for <[email protected]>; Tue, 7 Dec 1999 23:39:12 -0800
Received: from ias.ernet.in ([email protected] [202.41.122.11])
by rri.res.in (8.9.1/8.9.1) with ESMTP id LAA10639
for <[email protected]>; Wed, 8 Dec 1999 11:47:43 +0530 (IST)
Received: (from prakash@localhost) by ias.ernet.in (8.6.12/8.6.9) id LAA26226; Wed, 8 Dec 1999 11:53:57 +0500
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 11:53:57 +0500 (GMT+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: "N.A. Prakash" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi

I think this was brought up on this list before, but I never understood
the issue properly. Why was Pine designed to load entire folders into
memory rather than only the From, Date and Subject headers and only load
messages as they are opened? Would this not avoid slowness in opening
huge mail folders, especially on not-so-powerful systems where users run
Pine in telnet sessions (RAM can get filled and there's a lot of swapping
to disk)? I'm no programmer, so I can't even begin to imagine what this
might involve. So I'd be grateful for some explanation.

prakash
--
N. A. Prakash, Indian Academy of Sciences, Bangalore, India

On Tue, 7 Dec 1999, Robert Larmon wrote:

>
> attachments to a directory. If not, I request that this become a feature.
> I am encountering many users who receive hundreds of attachments, and
> keeping them in the same 'folder' as the email is causing lots of slowness
> when they try to navigate among their folders. I would tell them to just
...

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 06:50:18 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA25611;
Wed, 8 Dec 1999 06:50:17 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA28808;
Wed, 8 Dec 1999 06:50:16 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA23563;
Wed, 8 Dec 1999 06:48:40 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA59976
for <[email protected]>; Wed, 8 Dec 1999 06:44:02 -0800
Received: from CCGNV.NET (ccgnv.net [207.141.129.4])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id GAA17386
for <[email protected]>; Wed, 8 Dec 1999 06:44:01 -0800
Received: from 6swma [209.208.28.28] by CCGNV.NET
(SMTPD32-4.04) id AC52D1001D8; Wed, 08 Dec 1999 09:33:54 EST
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 09:43:47 -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: "TjL" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: RE: bringing back an old thread Re: X-Sender
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: "Nagilum" <[email protected]>,
"Pine Discussion Forum" <[email protected]>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

The bad news:
The only way I found to do this was by editing the PINE source code to
remove the Sender/X-Sender stuff.

The good news:
Editing the source code this way is relatively simple, and my patches (for
3.96 and 4.10, so they're not new, but should show you what is needed) are
available at:

http://www.peak.org/~luomat/patches/pine/

You need to edit send.c and reply.c (at least that was all as of 4.10).

The changes are pretty obvious (or were to me, and I'm not a programmer &
can't read C)

TjL

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 09:23:24 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA28269;
Wed, 8 Dec 1999 09:23:23 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA32498;
Wed, 8 Dec 1999 09:23:22 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA15142;
Wed, 8 Dec 1999 09:20:33 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA39182
for <[email protected]>; Wed, 8 Dec 1999 09:14:30 -0800
Received: from nimbus.anzio.com (IDENT:[email protected] [204.201.253.34])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA20479;
Wed, 8 Dec 1999 09:14:30 -0800
Received: from localhost (bezell@localhost)
by nimbus.anzio.com (8.8.7/8.8.7) with ESMTP id JAA19390;
Wed, 8 Dec 1999 09:12:22 -0800
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 09:12:22 -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: Bobby Ezell <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something
In-Reply-To: <Pine.A41.4.21.9912071209280.46250-100000@dante06.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Scott Leibrand <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

One of the issues on a similar subject - and perhaps this is what is meant
- is with "sent-mail". We often ship large files as attachments and
would rather not have the attachment saved into "sent-mail" with the
message as it fills up disk rather quickly. This would be a nice Setup
option.

Bobby Ezell
RSI Support

On Tue, 7 Dec 1999, Scott Leibrand wrote:

> There IS an option to remove an attachment from an e-mail without
> re-sending it. Although this is by no means automatic as you'd like, you
> may be able to make it so. Here's what you do:
>
> Open the message and view the attachment list. Save the attachment to a
> file as you would normally. Press D to delete the attachment. Press < to
> get back to the message body, and press S to save the message. Choose the
> folder it's already in, or another folder if you like. Confirm that you
> want to save the message without its attachments, and then you'll have a
> fresh copy of the messase, sans attachments, and the old copy will be
> marked Deleted.
>
> --
> Scott Leibrand
> [email protected]
> http://students.washington.edu/leibrand
> * RCW 19.190 notice: This email address is located in Washington State. *
> * Unsolicited commercial email may be billed $500 per message. *
>
> On Tue, 7 Dec 1999, Robert Larmon wrote:
>
> >
> > Hi all,
> > I was wondering if there is a feature to separate attachments from
> > email, sort of like how Eudora has a directory to automatically move
> > attachments to a directory. If not, I request that this become a feature.
> > I am encountering many users who receive hundreds of attachments, and
> > keeping them in the same 'folder' as the email is causing lots of slowness
> > when they try to navigate among their folders. I would tell them to just
> > delete the attachment, but I don't think that's a feature either.
> > (Unless they reply the email to themselves and delete the original, but
> > that's pushing it for my users).
> >
> > I was thinking something that would work the same in PC-Pine or regular
> > Pine, so maybe have an 'attach' directory in c:\pine and/or
> > ~/user/attach. And then have a couple options like...
> >
> > [Attachment Options]
> >
> > [ ] enable-local-attachments (for PC-Pine only?)
> > [ ] enable-remote-attachments
> > [ ] search-all-attachment-folders
> > [ ] enable-copy-to-local-then-delete (again for PC-Pine only? for someone
> > who uses both - which is half my users)
> >
> > Delete from remote after (this I guess could tie in to the
> > monthly sent-mail check?)
> > [ ] 1 week [ ] 2 weeks [ ] 1 month
> >
> > Of course, this might necessitate creating an Attachment folder interface
> > (in addition to the mail folders and addressbooks) that's intelligent
> > enough to add a line in the email to show where the file actually went
> > (remote or local, depending on usage of PC-Pine.)
> >
> > If this does become a feature, then I won't have to consider Eudora or
> > Netscape Mail as much when I review email clients next year and my users
> > won't have ammo to sway my bosses. ;) I also understand that this would
> > be a difficult and complicated task to complete, so my thanks to the Pine
> > team in advance for consideration.
> >
> > Robert
> >
> >
> >
> > ```````````````````````````````````````````````````````````````````````
> > ` Robert Larmon `
> > ` PC Systems Analyst `
> > ` USC Law School Computing Services `
> > ` [email protected] `
> > '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> >
> >
> >
> > --
> > -----------------------------------------------------------------
> > For information about this mailing list, and its archives, see:
> > http://www.washington.edu/pine/pine-info/
> > -----------------------------------------------------------------
> >
>

-------------------------------------------------------------------
Bobby Ezell E-Mail: [email protected]
Technical Sales Support V-Mail: 503-624-0360 (voice)
Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax)
10240 SW Nimbus Ave., Ste L9 http://www.anzio.com
Portland, OR 97223 http://www.anzio.com/~bezell
-------------------------------------------------------------------
AnzioLite and AnzioWin for all your telnet needs
Send sales & support questions to: [email protected]
-------------------------------------------------------------------
The information contained in this mail is confidential and intended
for the end-users use only.
===================================================================

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 09:41:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26525;
Wed, 8 Dec 1999 09:41:22 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00484;
Wed, 8 Dec 1999 09:41:22 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA01103;
Wed, 8 Dec 1999 09:39:31 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA33180
for <[email protected]>; Wed, 8 Dec 1999 09:34:38 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA19849
for <[email protected]>; Wed, 8 Dec 1999 09:34:37 -0800
Received: from goedel1.math.washington.edu ([email protected] [128.95.224.2])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id JAA13809;
Wed, 8 Dec 1999 09:34:36 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912080932580.15141-100000@goedel1.math.washington.edu>
Date: Wed, 8 Dec 1999 09:34:36 -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 L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Bobby Ezell <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Bobby Ezell ([email protected]) wrote today:

:)
:) One of the issues on a similar subject - and perhaps this is what is meant
:) - is with "sent-mail". We often ship large files as attachments and
:) would rather not have the attachment saved into "sent-mail" with the
:) message as it fills up disk rather quickly. This would be a nice Setup
:) option.
:)
Take a look at the option fcc-without-attachemnts in your configuration
file. I think the version of pine you are using supports this options.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 09:55:18 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA29368;
Wed, 8 Dec 1999 09:55:17 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00876;
Wed, 8 Dec 1999 09:55:17 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA23561;
Wed, 8 Dec 1999 09:52:03 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA43004
for <[email protected]>; Wed, 8 Dec 1999 09:48:22 -0800
Received: from nimbus.anzio.com (IDENT:[email protected] [204.201.253.34])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26204
for <[email protected]>; Wed, 8 Dec 1999 09:48:22 -0800
Received: from localhost (bezell@localhost)
by nimbus.anzio.com (8.8.7/8.8.7) with ESMTP id JAA20155;
Wed, 8 Dec 1999 09:46:12 -0800
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 09:46:12 -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: Bobby Ezell <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: requested feature, unless I'm missing something
In-Reply-To: <Pine.OSF.4.21.9912080932580.15141-100000@goedel1.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Eduardo Chappa L." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Oops, my fault. I had it set wrong and was assuming it still was not
working as I had anticipated. I cleared an old .pinerc and retried and it
works. Thanks.

On Wed, 8 Dec 1999, Eduardo Chappa L. wrote:

> *** Bobby Ezell ([email protected]) wrote today:
>
> :)
> :) One of the issues on a similar subject - and perhaps this is what is meant
> :) - is with "sent-mail". We often ship large files as attachments and
> :) would rather not have the attachment saved into "sent-mail" with the
> :) message as it fills up disk rather quickly. This would be a nice Setup
> :) option.
> :)
> Take a look at the option fcc-without-attachemnts in your configuration
> file. I think the version of pine you are using supports this options.
>
> Eduardo
> http://www.math.washington.edu/~chappa/pine/
>

-------------------------------------------------------------------
Bobby Ezell E-Mail: [email protected]
Technical Sales Support V-Mail: 503-624-0360 (voice)
Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax)
10240 SW Nimbus Ave., Ste L9 http://www.anzio.com
Portland, OR 97223 http://www.anzio.com/~bezell
-------------------------------------------------------------------
AnzioLite and AnzioWin for all your telnet needs
Send sales & support questions to: [email protected]
-------------------------------------------------------------------
The information contained in this mail is confidential and intended
for the end-users use only.
===================================================================

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 10:17:22 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA29795;
Wed, 8 Dec 1999 10:17:21 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01575;
Wed, 8 Dec 1999 10:17:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA02984;
Wed, 8 Dec 1999 10:13:16 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA70278
for <[email protected]>; Wed, 8 Dec 1999 10:09:16 -0800
Received: from watsol.cc.columbia.edu (IDENT:[email protected] [128.59.39.139])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01841
for <[email protected]>; Wed, 8 Dec 1999 10:09:15 -0800
Received: from localhost by watsol.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA15471;
Wed, 8 Dec 1999 13:09:10 -0500 (EST)
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 13:09:08 -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: Bino Gopal <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Suggestion
In-Reply-To: <Pine.OSF.4.21.9912031105030.12604-100000@goedel2.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: "Eduardo Chappa L." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 3 Dec 1999, Eduardo Chappa L. wrote:

> :) Also, how exactly does the Not (!) command work? If I say "! P"
> :) (Not Participant) does that search just headers (excluding
> :) Participants) or does it search headers and body (excluding
> :) Participants)? If it's the latter, this is a partial solution to
> :) Mike Miller's body-only searching request.
> :)
> This means that the Participant will not be what you specify later, so if
> you want to read mails where you have not participated you would make a
> search by:
>
> ; t ! P nancy CR
>
> The advantage of this is that now you can narrow your select to say all
> the ones that have the word "bug" in the subject so you would do:
>
> ; n t s bug CR
>
> and now eliminate replies by
>
> ; n t ! s Re: CR
>
> I hope this makes it clear...
>
> Eduardo
> http://www.math.washington.edu/~chappa/pine/

Oh god! That's SO AWESOME! They did it!! Forgive my excitement, but
I've been away for a while, and we haven't updated from 4.10 here, and I
see that the "NOT" that I so desperately asked for way back when (like
August) has been put in!! And Participant is awesome too! Yes, yes,
yes!!! THANK YOU Pine gods, thank you very, VERY much! Woohoo!

Now to stop everything else I'm doing and go get the code to compile the
new version... *grin*

BINO

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 12:29: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA20219;
Wed, 8 Dec 1999 12:29:47 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05628;
Wed, 8 Dec 1999 12:29:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA00302;
Wed, 8 Dec 1999 12:26:30 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA35482
for <[email protected]>; Wed, 8 Dec 1999 12:20:33 -0800
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA00373
for <[email protected]>; Wed, 8 Dec 1999 12:20:29 -0800
Received: (qmail 21439 invoked from network); 9 Dec 1999 06:09:40 +1100
Received: from trowel.geac.com.au (134.128.219.30)
by caveman.geac.com.au with SMTP; 9 Dec 1999 06:09:40 +1100
Received: (qmail 8449 invoked from network); 8 Dec 1999 18:13:38 +1100
Received: from fgh.geac.com.au (134.128.222.46)
by trowel.geac.com.au with SMTP; 8 Dec 1999 18:13:38 +1100
Received: from localhost (dave@localhost)
by fgh.geac.com.au?r with ESMTP id SAA12058
for <[email protected]>; Wed, 8 Dec 1999 18:14:30 +1100
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 18:14:30 +1100 (EST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Dave Horsfall <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Nicknames in distribution lists
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion List <[email protected]>
X-Authentication-Warning: fgh.geac.com.au: dave owned process doing -bs
X-No-Archive: Yes
X-Witty-Saying: "Tesseract - Enter at own risk"
X-Disclaimer: "Me, speak for us?"
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is there any way to get nicknames to be expanded in lists? I want to set
up sub-lists, as it were, and have them expanded at composition time, so
the actual addressee only needs to be stored once - fundamental database
principle - so it can be changed easily.

It would also be nice, when creating new lists, to do the opposite
i.e. have the nicknames expanded right away, so they can be pruned.

Currently using 4.21 under Slowaris.

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

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 14:53:05 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA03317;
Wed, 8 Dec 1999 14:53:03 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA10241;
Wed, 8 Dec 1999 14:53:03 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA08925;
Wed, 8 Dec 1999 14:51:02 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA74704
for <[email protected]>; Wed, 8 Dec 1999 14:47:42 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA00514
for <[email protected]>; Wed, 8 Dec 1999 14:47:42 -0800
Received: from aleph.ii.com (aleph.ii.com [165.254.18.8])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id RAA12286;
Wed, 8 Dec 1999 17:47:39 -0500 (EST)
Message-Id: <Pine.WNT.4.21.9912081739410.-164529@aleph>
Date: Wed, 8 Dec 1999 17:46:49 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: RE: bringing back an old thread Re: X-Sender
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-08 TjL <[email protected]> wrote:
> The bad news:
> The only way I found to do this was by editing the PINE source code to
> remove the Sender/X-Sender stuff.
>
> The good news:
> Editing the source code this way is relatively simple, and my patches (for
> 3.96 and 4.10, so they're not new, but should show you what is needed) are
> available at:
>
> http://www.peak.org/~luomat/patches/pine/
>
> You need to edit send.c and reply.c (at least that was all as of 4.10).
>
> The changes are pretty obvious (or were to me, and I'm not a programmer &
> can't read C)

According to:

http://www.washington.edu/pine/overview/legal.html

"Local modification of this release is permitted as follows, or by
mutual agreement: In order to reduce confusion and facilitate
debugging, we request that locally modified versions be denoted
by appending the letter "L" to the current version number, and
that the local changes be enumerated in the integral release
notes and associated documentation."

Can someone tell me where in the source I would need to change
"4.21" to "4.21L" and what doc files I would need to list my
changes in? Also, where in the source can I change the Message-ID
so it doesn't say my machine's name? Now that I have a Linux
machine I can start taking advantage of Pine's open-sourceness!

Thanks,
Nancy

--
For Pine links, see http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
--= Sent via PINE 4.21: Internet News & Email for Win/Unix =--

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 15:08:03 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA03408;
Wed, 8 Dec 1999 15:08:02 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA10710;
Wed, 8 Dec 1999 15:08:02 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA02901;
Wed, 8 Dec 1999 15:05:05 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA43906
for <[email protected]>; Wed, 8 Dec 1999 15:01:29 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30194
for <[email protected]>; Wed, 8 Dec 1999 15:01:28 -0800
Received: from goedel1.math.washington.edu ([email protected] [128.95.224.2])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id PAA14859;
Wed, 8 Dec 1999 15:01:25 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912081453550.5195-100000@goedel1.math.washington.edu>
Date: Wed, 8 Dec 1999 15:01: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: RE: bringing back an old thread Re: X-Sender
In-Reply-To: <Pine.WNT.4.21.9912081739410.-164529@aleph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Nancy this-address-is-valid McGough ([email protected]) wrote today:
:)
:) Can someone tell me where in the source I would need to change
:) "4.21" to "4.21L" and what doc files I would need to list my
:) changes in? Also, where in the source can I change the Message-ID
:) so it doesn't say my machine's name? Now that I have a Linux
:) machine I can start taking advantage of Pine's open-sourceness!
:)
Take a look at pine.h

pine.h:#define PINE_VERSION "4.21"

Also take look at the function

generate_message_id()

in the file pine/reply.c

Congrats for the linux machine. I have just started working in one (now I
can work in real linux :))), Thanks David!). I hope you don't forget about
PC-PINE, you are the most reliable source for it, around here.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 15:40:50 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA03371;
Wed, 8 Dec 1999 15:40:48 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA11524;
Wed, 8 Dec 1999 15:40:48 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA10929;
Wed, 8 Dec 1999 15:38:21 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA93376
for <[email protected]>; Wed, 8 Dec 1999 15:35:32 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04284
for <[email protected]>; Wed, 8 Dec 1999 15:35:31 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA11360
for <[email protected]>; Wed, 8 Dec 1999 15:35:31 -0800
Received: from dante41.u.washington.edu ([email protected] [140.142.15.201])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA20588
for <[email protected]>; Wed, 8 Dec 1999 15:35:30 -0800
Received: from localhost (leibrand@localhost)
by dante41.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA12666
for <[email protected]>; Wed, 8 Dec 1999 15:35:29 -0800
Message-Id: <Pine.A41.4.21.9912081531150.30594-100000@dante41.u.washington.edu>
Date: Wed, 8 Dec 1999 15:35:29 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Attachments and disk usage (fwd)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Here's a copy of a message I sent to the Pine Development Team that I
thought you guys might be interested in. Please let me know what you
think of my suggestions, or if you have anything you'd like to add.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

---------- Forwarded message ----------
Date: Wed, 8 Dec 1999 15:30:52 -0800 (PST)
Subject: Attachments and disk usage

Here at the UW, increasing numbers of large e-mail attachments are leading
to disk space problems for many users. Although such problems will be
temporarily alleviated by increasing disk quotas, it would be a good idea
to address possible solutions now. One specific problem I've noticed is
the difficulty of deleting e-mail attachments from messages in Pine, and
in managing attachments in general. To help address these issues, I
suggest the following features in the next release of Pine. Please let me
know what you think of them.

- In the Attachment View, there is currently a Delete option to delete
attachments. For the deletion to take effect, however, requires saving
the message to a folder (either the same one or another one). Since the
point of deleting an attachment is usually to free up disk space, not to
move the messsage, I would suggest (as others have on pine-info) an
eXpunge command in the Attachment View that allows you to delete the
attachment without the counterintuitive requirement of saving the message
to the folder it's already in. This new command could be implemented by
simply performing that save (which would mess up arrival sorts) or by a
more comprehensive method that would delete the attachment without moving
the message. In addition, configurable options could be added to prompt
about expunging deleted attachments when the Attachment View is closed and
to extend the expunge-without-confirm option to attachments.

Although the changes above would make it easy for Pine users to delete
attachments manually, a more automatic method would be required to make
much impact on global disk usage. Here are a couple suggestions:

- Since most Pine users at the UW use the View and Save commands to save
attachments to their home directories where they can be downloaded with
FTP, the attachment itself, embedded in the mail folder, is often no
longer needed. Therefore, it might be helpful to prompt users to delete
the attachment after exporting it (with a default of No, probably) to
prevent attachment duplication.

This still leaves attachment management entirely up to the user. A more
complete solution would be something along the lines of what Robert Larmon
mentioned on pine-info. Here's what I think would work best for the UW:

- In the case of users who use Unix Pine exclusively on the UA machines,
Pine could automatically (or configurably after confirmation) save all
incoming attachments to one of the user's directories, with the default
something like ~/attach/. For PC-Pine, a similar folder like "c:\my
documents\attachments\" could be used, but here confirmation would be
asolutely essential for users with slower connections. For users who use
both Unix Pine and desktop e-mail clients (including PC-Pine), attachments
must remain on the IMAP server until they can be downloaded by the desktop
e-mail client. Therefore I recommend that Pine (both unix and PC) save
attachments to the folder specified above, then only delete attachments
when configurable criteria are met, and (configurably) only after
confirmation. These criteria could include: After __ days
(0=immediately); When total attachment size exceeds ____; or When within
____ of disk quota.

Let me know what you think,
--
Scott Leibrand
Training Technical Support Lead
Computing & Communications
[email protected]

On Wed, 8 Dec 1999, David Wall wrote:

> FYI.
>
> --David Wall Computing & Communications...Client Services 206.543.8491
> Univ. of Washington Box 355670 [email protected]
>
>
> ---------- Forwarded message ----------
> Date: Tue, 7 Dec 1999 16:16:48 -0800 (PST)
> From: Ken Lowe <[email protected]>
> To: David Wall <[email protected]>,
> Robert Jamieson <[email protected]>,
> Hugh Sheets <[email protected]>
> Cc: [email protected], [email protected],
> [email protected]
> Subject: Re: raise quotas to 100 MB (fwd)
>
> User quotas have been upped from 50MB to 100MB on both dante and homer.
> It will take effect tomorrow morning during the 2am accounting run
> tonight.
>
> [snip]
>
> -Ken
>
> -----
>
> Date: Thu, 2 Dec 1999 15:57:44 -0800 (PST)
> From: Hugh Sheets <[email protected]>
> To: [email protected]
> Cc: [email protected], [email protected],
> [email protected]
> Subject: Re: raise quotas to 100 MB (fwd)
>
> Proceeding sounds good, and Client Services would be happy. And, more
> disk is coming down the road....
>
> Hugh
>
> On Thu, 2 Dec 1999, Ken Lowe wrote:
>
> > On homer, there are:
> >
> > 23637 accounts with a 50 MB limit
> > 660 of them are using 40MB or more.
> >
> > On dante, there are:
> >
> > 48917 accounts with a 50 MB limit
> > 1047 of them are using 40MB or more.
> >
> > Assuming those with 40MB or more will go up to 80MB or more and
> > those under 40MB would pretty much stay where they are, I figure
> > bumping everyone up to 100MB would consume about 40GB on homer
> > and about 60GB on dante in addition to the normal growth we're
> > seeing. Even if all that extra growth occurs on the deskmail
> > systems (likely) I think we'll still be okay.
> >
> > Shall I go ahead and bump them up and see what happens?
> >
> > -Ken
> >
> > -----
> >
> > Date: Thu, 18 Nov 1999 11:04:16 -0800 (PST)
> > From: Hugh Sheets <[email protected]>
> > To: [email protected], [email protected]
> > Cc: [email protected], [email protected]
> > Subject: raise quotas to 100 MB (fwd)
> >
> > Ken, Doug, you should see this, too. Do we have the disk space for this?
> >
> > Hugh
> >
> > ---------- Forwarded message ----------
> > Date: Thu, 18 Nov 1999 10:48:44 -0800 (PST)
> > From: David Wall <[email protected]>
> > To: Hugh Sheets <[email protected]>
> > Cc: Jim DeRoest <[email protected]>,
> > Oren Sreebny <[email protected]>
> > Subject: raise quotas to 100 MB
> >
> > We have discussed this at the Client Services meeting and would like to
> > recommend that quotas on Homer and Dante be bumped up to the 100 MB maximum
> > as was recently done on Aagaard. If it can't be done in both places, our
> > priority is for Homer.
> >
> > The reason is that a lot of time is wasted by users and and by our staff
> > dealing with over quota email conditions. There doesn't seem to be much
> > benefit of having an artificial limit.
> >
> > We are seeing more and more large email attachments as routine business
> > operations. We also see more people using desktop clients without a clue as
> > to where their folders live or the space they take up. There are a lot of
> > 'issues' about disk use. If we can't afford what they are using, then
> > someone should look at specific problems and ways to address those. But an
> > artificial 50MB limit is not productive.
> >
> >
> > --David Wall Computing & Communications...Client Services 206.543.8491
> > Univ. of Washington Box 355670 [email protected]
>
>
>
>

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 16:00:36 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA04925;
Wed, 8 Dec 1999 16:00:35 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA12102;
Wed, 8 Dec 1999 16:00:34 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA12323;
Wed, 8 Dec 1999 15:58:30 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA44592
for <[email protected]>; Wed, 8 Dec 1999 15:53:46 -0800
Received: from dfw.nationwide.net (dfw.nationwide.net [198.175.15.10])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA11684
for <[email protected]>; Wed, 8 Dec 1999 15:53:28 -0800
Received: from localhost (avolon@localhost)
by dfw.nationwide.net (8.9.3/8.9.3) with ESMTP id RAA13533
for <[email protected]>; Wed, 8 Dec 1999 17:52:48 -0600 (CST)
Message-Id: <[email protected]>
Date: Wed, 8 Dec 1999 17:52:44 -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: Dave Johnson <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: simple help
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have just started using pine again.
I am ussing pine4.10, and I have two basic questions.
When I send a message, pine creates a folder before it sends it.
A folder for each message I send.
How do I correct this?
Also, when i clear my messages from the home directory with rm,
it prompts me with yes or no.
How do I turn off this prompt?
Thanks for any help. Dave Johnson [email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 16:47: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA05848;
Wed, 8 Dec 1999 16:47:31 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA13541;
Wed, 8 Dec 1999 16:47:30 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA12213;
Wed, 8 Dec 1999 16:45:59 -0800
Received: from jason03.u.washington.edu ([email protected] [140.142.77.10])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA47414
for <[email protected]>; Wed, 8 Dec 1999 16:42:24 -0800
Received: from dante28.u.washington.edu ([email protected] [140.142.15.83])
by jason03.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA11764;
Wed, 8 Dec 1999 16:42:23 -0800
Received: from localhost (leibrand@localhost)
by dante28.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA45716;
Wed, 8 Dec 1999 16:42:23 -0800
Message-Id: <Pine.A41.4.21.9912081639320.99132-100000@dante28.u.washington.edu>
Date: Wed, 8 Dec 1999 16:42:23 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: simple help
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Dave Johnson <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

rm is not a Pine command, but you probably want to use rm's -f flag to
eliminate the confirmation prompt. Use the man rm command (that's short
for viewing the MANual pages on the RM command) to view all of rm's
options.

I'm not sure what's up with your other problem.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Wed, 8 Dec 1999, Dave Johnson wrote:

> I have just started using pine again.
> I am ussing pine4.10, and I have two basic questions.
> When I send a message, pine creates a folder before it sends it.
> A folder for each message I send.
> How do I correct this?
> Also, when i clear my messages from the home directory with rm,
> it prompts me with yes or no.
> How do I turn off this prompt?
> Thanks for any help. Dave Johnson [email protected]
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 8 Dec 1999 22:59:59 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA09334;
Wed, 8 Dec 1999 22:59:58 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA20186;
Wed, 8 Dec 1999 22:59:57 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA18013;
Wed, 8 Dec 1999 22:57:14 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA72836
for <[email protected]>; Wed, 8 Dec 1999 22:52:55 -0800
Received: from fn1.freenet.edmonton.ab.ca (IDENT:[email protected] [198.161.206.8])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA00688
for <[email protected]>; Wed, 8 Dec 1999 22:52:51 -0800
Received: from fn2.freenet.edmonton.ab.ca
([email protected] [198.161.206.7])
by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3)
with ESMTP id XAA117836
for <[email protected]>;
Wed, 8 Dec 1999 23:52:46 -0700
Received: from localhost
(azz@localhost)
by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3)
with SMTP id XAA85766
for <[email protected]>;
Wed, 8 Dec 1999 23:52:45 -0700
Message-Id: <Pine.A41.3.95.991208235127.48052D-100000@fn2.freenet.edmonton.ab.ca>
Date: Wed, 8 Dec 1999 23:52:44 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Please Help.
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Can someone please tell me how to transfer all my email to a floppy disk.

Thanks so much.

AL

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 01:58:31 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA13017;
Thu, 9 Dec 1999 01:58:30 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA22961;
Thu, 9 Dec 1999 01:58:29 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA21671;
Thu, 9 Dec 1999 01:56:54 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA16420
for <[email protected]>; Thu, 9 Dec 1999 01:52:39 -0800
Received: from randomc.com ([email protected] [130.205.85.40])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA14176
for <[email protected]>; Thu, 9 Dec 1999 01:52:39 -0800
Received: from localhost (dana@localhost)
by randomc.com (8.8.8/8.8.8/8.8.8) with ESMTP id EAA01557
for <[email protected]>; Thu, 9 Dec 1999 04:45:53 -0500 (EST)
Message-Id: <Pine.GSO.4.10.9912090442070.1542-100000@cluster2>
Date: Thu, 9 Dec 1999 04:45:52 -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: dana <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: have a problem in pine, and think it is a shell problem.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: dana@cluster2
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

they worked on the shell last night, and now this morning while i was
reading
news groups in pine, i keep getting this message, what is the chmod
command to fix this problem? think all my files in the home directory are
read only.

[Can't create backup news state /export/home/dana/.newsrc.old]
Pine finished -- Closed empty folder "INBOX"

what does this mean?

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 09:47: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA23454;
Thu, 9 Dec 1999 09:47:05 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA32654;
Thu, 9 Dec 1999 09:47:05 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA10721;
Thu, 9 Dec 1999 09:44:36 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA50150
for <[email protected]>; Thu, 9 Dec 1999 09:39:57 -0800
Received: from pop3.accessinter.net (pop3.accessinter.net [207.234.184.12])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA24952
for <[email protected]>; Thu, 9 Dec 1999 09:39:54 -0800
Received: from [207.234.184.77] by pop3.accessinter.net
(Post.Office MTA v3.5.3 release 223 ID# 0-59568U3000L300S0V35)
with SMTP id net for <[email protected]>;
Thu, 9 Dec 1999 12:36:33 -0500
Received: (qmail 6997 invoked by uid 500); 9 Dec 1999 17:40:06 -0000
Received: from localhost ([email protected])
by localhost with SMTP; 9 Dec 1999 17:40:06 -0000
Message-Id: <[email protected]>
Date: Thu, 9 Dec 1999 12:40:06 -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: Adam Price <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Building Pine on LinuxPPC/Yellowdog
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: linuxppc user <[email protected]>
X-Cc: [email protected]
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This question has been asked on l-u before, but there was never a
satisfactory reply. (Where "satisfactory" means "answers MY question".)

I am trying to build Pine 4.21,
# build slx
and things go along smoothly up until

/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status
make: *** [pico] Error 1

and the whole compiler bombs out, leaving no binary at all. lncurses is a
variable set in makefile.lnx
STDLIBS= -lncurses

I have tried changig it to -lcurses (because ...I don't know) but it
doesn't help.
1. What should this be changed to to allow pine to build.
OR
2. What do I have to do to repair my system so -lncurses will be found by
ld?

--
[email protected]

A lady came up to me on the street and pointed to my suede jacket. "You
know a cow was murdered for that jacket?" she sneered. I replied in a
psychotic tone, "I didn't know there were any witnesses. Now I'll have
to kill you too."
-- Jake Johansen

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 10:28:00 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA19218;
Thu, 9 Dec 1999 10:27:59 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01229;
Thu, 9 Dec 1999 10:27:58 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA12450;
Thu, 9 Dec 1999 10:25:05 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA76842
for <[email protected]>; Thu, 9 Dec 1999 10:20:51 -0800
Received: from proxy1.it.stsj.seagate.com (ns1.seagate.com [204.160.183.10])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03515
for <[email protected]>; Thu, 9 Dec 1999 10:20:48 -0800
Received: (from smap) by proxy1.it.stsj.seagate.com id SAA11466 for <[email protected]>; Thu, 9 Dec 1999 18:20:37 GMT
Received: from nodnsquery(10.30.144.100) by proxy1.it.stsj.seagate.com via smap (V5.0)
id xma011289; Thu, 9 Dec 99 18:19:59 GMT
Received: from kashmir.colo.seagate.com (kashmir [10.30.147.19])
by dilbert.colo.seagate.com (8.8.8+Sun/8.8.8) with SMTP id LAA10995
for <[email protected]>; Thu, 9 Dec 1999 11:17:04 -0700 (MST)
Received: from localhost by kashmir.colo.seagate.com (SMI-8.6/SMI-SVR4)
id LAA06111; Thu, 9 Dec 1999 11:19:55 -0700
Message-Id: <Pine.GSO.4.10.9912091110160.2150-100000@kashmir>
Date: Thu, 9 Dec 1999 11:19:55 -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: "Ajaz M. Siraj" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Using pipe command in Pine4.10
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: asiraj@kashmir
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

I just upgraded to pine4.10 from pine3.95. I am facing a problem with pipe
command that used to work previously. The new version returns the
following message:

[PIPE MESSAGE command completed with no output]

Am I missing something?

Regards
Ajaz

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 10:45:56 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25003;
Thu, 9 Dec 1999 10:45:55 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA01256;
Thu, 9 Dec 1999 10:45:55 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA13299;
Thu, 9 Dec 1999 10:42:10 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA47420
for <[email protected]>; Thu, 9 Dec 1999 10:38:01 -0800
Received: from mail.mankato.msus.edu (Mail.Mankato.MSUS.EDU [134.29.1.12])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03651
for <[email protected]>; Thu, 9 Dec 1999 10:37:56 -0800
Received: from bs1.mankato.msus.edu ([email protected] [134.29.1.244])
by mail.mankato.msus.edu (8.9.3/8.9.3) with ESMTP id MAA05334;
Thu, 9 Dec 1999 12:37:30 -0600 (CST)
Message-Id: <[email protected]>
Date: Thu, 9 Dec 1999 12:37:23 -0600 (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: Jeffrey Hundstad <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Building Pine on LinuxPPC/Yellowdog
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
X-To: [email protected]
X-Cc: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

You should install the ncurses package on your system. If you don't
want to do that you could alsotry changing the -lncurses to -ltermcap
instead.

Ncurses:

http://www.clark.net/pub/dickey/ncurses/ncurses.html

On 9 Dec, Adam Price wrote:
>
> This question has been asked on l-u before, but there was never a
> satisfactory reply. (Where "satisfactory" means "answers MY question".)
>
>
>
> I am trying to build Pine 4.21,
> # build slx
> and things go along smoothly up until
>
>
> /usr/bin/ld: cannot find -lncurses
> collect2: ld returned 1 exit status
> make: *** [pico] Error 1
>
> and the whole compiler bombs out, leaving no binary at all. lncurses is a
> variable set in makefile.lnx
> STDLIBS= -lncurses
>
> I have tried changig it to -lcurses (because ...I don't know) but it
> doesn't help.
> 1. What should this be changed to to allow pine to build.
> OR
> 2. What do I have to do to repair my system so -lncurses will be found by
> ld?
>
>
>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 12:11: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA27025;
Thu, 9 Dec 1999 12:11:48 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04229;
Thu, 9 Dec 1999 12:11:47 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA17075;
Thu, 9 Dec 1999 12:04:15 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA53130
for <[email protected]>; Thu, 9 Dec 1999 12:00:24 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA20239
for <[email protected]>; Thu, 9 Dec 1999 12:00:24 -0800
Received: from fn1.freenet.edmonton.ab.ca (IDENT:[email protected] [198.161.206.8])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA03896
for <[email protected]>; Thu, 9 Dec 1999 12:00:23 -0800
Received: from fn2.freenet.edmonton.ab.ca
([email protected] [198.161.206.7])
by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3)
with ESMTP id NAA126870
for <[email protected]>;
Thu, 9 Dec 1999 13:00:22 -0700
Received: from localhost
(azz@localhost)
by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3)
with SMTP id NAA67894
for <[email protected]>;
Thu, 9 Dec 1999 13:00:21 -0700
Message-Id: <Pine.A41.3.95.991209125906.48690A-100000@fn2.freenet.edmonton.ab.ca>
Date: Thu, 9 Dec 1999 13:00:20 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Please unsubscribe.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine help <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi, could you please help me to unsubscribe from PINE-help forum.

Thanks

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 12:44:41 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA27551;
Thu, 9 Dec 1999 12:44:40 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04835;
Thu, 9 Dec 1999 12:44:40 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA16383;
Thu, 9 Dec 1999 12:40:24 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA18250
for <[email protected]>; Thu, 9 Dec 1999 12:25:23 -0800
Received: from natsemi3-bh.nsc.com (natsemi3-bh.nsc.com [205.227.60.66])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA24593
for <[email protected]>; Thu, 9 Dec 1999 12:25:14 -0800
Received: (from uucp@localhost) by natsemi3-bh.nsc.com (8.8.8/8.6.11) id PAA17681 for <[email protected]>; Thu, 9 Dec 1999 15:25:01 -0500 (EST)
Received: from scmh1.nsc.com(139.187.179.130) by natsemi3-bh.nsc.com via smap (4.1)
id xma016757; Thu, 9 Dec 99 15:24:00 -0500
Received: from localhost by scmh1.nsc.com with ESMTP; Thu, 9 Dec 1999 12:23:58 -0800
Message-Id: <Pine.A41.4.21.9912091209550.43904-100000@scmh1>
Date: Thu, 9 Dec 1999 12:23: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: Marilyn Perry <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Bounce crash or hang (Pine 4.21)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: emxpsc@scmh1
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I am running pine 4.21 on AIX 4.3.2. I am attempting to bounce a large
message whose size is reported by pine 4.21 as 4,516 K, and I am unable to
do so. I press b, pine reports "Busy", then either one of two things
happens:

1. pine crashes and writes a core file
2. the spinning dial stops spinning, but psg shows that pine is gobbling
CPU time. kill PID has no effect, but I can use kill -9 PID to kill
pine.

I have tried to determine if this is a pine 4.21 regression by bouncing
this same large message using older versions of pine, pine 3.95 and pine
4.10. Pine 3.95 bounces the message with no problem. Pine 4.10 bounces
the message with only a cosmetic problem: "Sending 100%" continues to be
displayed after the operation is completed. So I believe this is a
regression introduced sometime after 4.10.

Marilyn Perry

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 12:45:44 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21607;
Thu, 9 Dec 1999 12:45:42 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA05196;
Thu, 9 Dec 1999 12:45:41 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA18804;
Thu, 9 Dec 1999 12:33:34 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA18240
for <[email protected]>; Thu, 9 Dec 1999 12:25:23 -0800
Received: from infra.novazen.com (infra.novazen.com [209.38.244.15])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA16007
for <[email protected]>; Thu, 9 Dec 1999 12:25:17 -0800
Received: from dustpuppy ([192.168.10.178])
by infra.novazen.com (8.8.8+Sun/8.8.8) with SMTP id NAA27506
for <[email protected]>; Thu, 9 Dec 1999 13:25:06 -0700 (MST)
Message-Id: <[email protected]>
Date: Thu, 09 Dec 1999 13:24:49 -0700
Reply-To: "Ian Hall-Beyer" <[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: "Ian Hall-Beyer" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Please unsubscribe.
In-Reply-To: <Pine.A41.3.95.991209125906.48690A-100000@fn2.freenet.edmonton.ab.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-To: "[email protected]" <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 9 Dec 1999 13:00:20 -0700 (MST), [email protected] wrote:

>Hi, could you please help me to unsubscribe from PINE-help forum.

Yes. Follow the instructions listed at the bottom of EACH AND EVERY
SINGLE MESSAGE posted to this list. Failing that, try reading the
instructions you were given when you signed up. (Hint: it said not to
delete that message. You deleted it, didn't you.)

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

How bloody hard is it to comprehend that a machine handles subscription
requests, and that machine does NOT read the traffic in the list
itself? surely this isn't rocket science, is it?

Or is there something about subscribing to a mailing list that is
incredibly esoteric and makes you forget how you got on in the first
place?

*grumble*

It's almost as bad as wading through spam.
--
<cosmo> wow, this is kinda nifty. the Win98 protocol stack is like a chinese puzzle, twist and turn in the right places, and it pops right off.
-Seen on EFNet IRC

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 14:11:09 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA29407;
Thu, 9 Dec 1999 14:11:08 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA07452;
Thu, 9 Dec 1999 14:11:07 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA01072;
Thu, 9 Dec 1999 14:08:37 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA26790
for <[email protected]>; Thu, 9 Dec 1999 14:03:21 -0800
Received: from dante11.u.washington.edu ([email protected] [140.142.15.21])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA37274;
Thu, 9 Dec 1999 14:03:20 -0800
Received: from localhost (leibrand@localhost)
by dante11.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA68228;
Thu, 9 Dec 1999 14:03:19 -0800
Message-Id: <Pine.A41.4.21.9912091402300.29644-100000@dante11.u.washington.edu>
Date: Thu, 9 Dec 1999 14:03: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: have a problem in pine, and think it is a shell problem.
In-Reply-To: <Pine.GSO.4.10.9912090442070.1542-100000@cluster2>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: dana <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I think you'll want to chmod the directory itself as well as that file (if
it exists) to give yourself write access.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Thu, 9 Dec 1999, dana wrote:

> they worked on the shell last night, and now this morning while i was
> reading
> news groups in pine, i keep getting this message, what is the chmod
> command to fix this problem? think all my files in the home directory are
> read only.
>
> [Can't create backup news state /export/home/dana/.newsrc.old]
> Pine finished -- Closed empty folder "INBOX"
>
> what does this mean?
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 14:47:18 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA29870;
Thu, 9 Dec 1999 14:47:16 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA08620;
Thu, 9 Dec 1999 14:47:15 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA03808;
Thu, 9 Dec 1999 14:43:47 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA39728
for <[email protected]>; Thu, 9 Dec 1999 14:36:20 -0800
Received: from randomc.com ([email protected] [130.205.85.40])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA19731;
Thu, 9 Dec 1999 14:36:19 -0800
Received: from localhost (dana@localhost)
by randomc.com (8.8.8/8.8.8/8.8.8) with ESMTP id RAA02022;
Thu, 9 Dec 1999 17:29:30 -0500 (EST)
Message-Id: <Pine.GSO.4.10.9912091728360.1996-100000@cluster2>
Date: Thu, 9 Dec 1999 17:29:29 -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: dana <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: have a problem in pine, and think it is a shell problem.
In-Reply-To: <Pine.A41.4.21.9912091402300.29644-100000@dante11.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Scott Leibrand <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: dana@cluster2
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

i think they have the problem fixed now. thanks for all the replys.
i have been on this list for a while, but haven't posted in here. just
learning about pine.

On Thu, 9 Dec 1999, Scott Leibrand wrote:

> Date: Thu, 9 Dec 1999 14:03:19 -0800 (PST)
> From: Scott Leibrand <[email protected]>
> To: dana <[email protected]>
> Cc: Pine Discussion Forum <[email protected]>
> Subject: Re: have a problem in pine, and think it is a shell problem.
>
> I think you'll want to chmod the directory itself as well as that file (if
> it exists) to give yourself write access.
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 15:30:36 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30723;
Thu, 9 Dec 1999 15:30:34 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA09787;
Thu, 9 Dec 1999 15:30:34 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA25454;
Thu, 9 Dec 1999 15:28:51 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA79940
for <[email protected]>; Thu, 9 Dec 1999 15:24:56 -0800
Received: from vax.area.com (vax110.area.com [165.90.20.110])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA27877
for <[email protected]>; Thu, 9 Dec 1999 15:24:49 -0800
Received: (qmail 29338 invoked by uid 1828); 9 Dec 1999 23:24:43 -0000
Message-Id: <Pine.GSO.4.20.9912091521130.29679-100000@vax>
Date: Thu, 9 Dec 1999 15:24: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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: does pine cache info about the inbox? big ramble
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Does pine cache info about the inbox?

I'm just wondering why the few GUI email clients I've used take FOREVER to
open my mailbox, but pine does it very quickly. I had hope with the new
Eudora version that supports IMAP, since the previous Eudora Lights I had
used were nice and quick.. But it took MINUTES to get the 900-something
messages on the server.. and I had to nuke the Inbox file it had and redo
it since it originally didn't have enough memory and unhelpfully gave me
a gazillion error messages, so I had to quit it -- and it ended up with
partially downloaded (or cached or whatever -- yes I'm using IMAP) messages
where I had the headers but couldn't get it to display some of the messages.

ANYWAY -- sorry for the ramble.. I'm just wondering if I'm being deluded
into thinking pine isn't caching all of the inbox.. Is it? If not, why is
it a zillion times faster than Eudora or OE? (From my first use of this
new Eudora with the light/pay/ad model, I actually think I may prefer OE when
I have to use a GUI client.)
--
[email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 15:48: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA31168;
Thu, 9 Dec 1999 15:48:25 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA10372;
Thu, 9 Dec 1999 15:48:24 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA21490;
Thu, 9 Dec 1999 15:46:26 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA53784
for <[email protected]>; Thu, 9 Dec 1999 15:42:33 -0800
Received: from dante39.u.washington.edu ([email protected] [140.142.15.199])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA09720
for <[email protected]>; Thu, 9 Dec 1999 15:42:31 -0800
Received: from localhost (leibrand@localhost)
by dante39.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA60884
for <[email protected]>; Thu, 9 Dec 1999 15:42:31 -0800
Message-Id: <Pine.A41.4.21.9912091540120.59222-100000@dante39.u.washington.edu>
Date: Thu, 9 Dec 1999 15:42: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: does pine cache info about the inbox? big ramble
In-Reply-To: <Pine.GSO.4.20.9912091521130.29679-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Are you running PC-Pine on your local PC, or are you telnetting in to a
unix box and running unix Pine? If you're doing the latter, that's why
it's so fast - all the work of loading the inbox is performed over the
very fast connections at the mail server end, whereas the other programs
you're using have to download the entire inbox over your slower internet
connection.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Thu, 9 Dec 1999 [email protected] wrote:

>
> Does pine cache info about the inbox?
>
> I'm just wondering why the few GUI email clients I've used take FOREVER to
> open my mailbox, but pine does it very quickly. I had hope with the new
> Eudora version that supports IMAP, since the previous Eudora Lights I had
> used were nice and quick.. But it took MINUTES to get the 900-something
> messages on the server.. and I had to nuke the Inbox file it had and redo
> it since it originally didn't have enough memory and unhelpfully gave me
> a gazillion error messages, so I had to quit it -- and it ended up with
> partially downloaded (or cached or whatever -- yes I'm using IMAP) messages
> where I had the headers but couldn't get it to display some of the messages.
>
> ANYWAY -- sorry for the ramble.. I'm just wondering if I'm being deluded
> into thinking pine isn't caching all of the inbox.. Is it? If not, why is
> it a zillion times faster than Eudora or OE? (From my first use of this
> new Eudora with the light/pay/ad model, I actually think I may prefer OE when
> I have to use a GUI client.)
> --
> [email protected]
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 16:15:43 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA31959;
Thu, 9 Dec 1999 16:15:42 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA11119;
Thu, 9 Dec 1999 16:15:41 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA22504;
Thu, 9 Dec 1999 16:14:00 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA13662
for <[email protected]>; Thu, 9 Dec 1999 16:10:43 -0800
Received: from tao.agoron.com (tao.agoron.com [206.181.233.66])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA25962
for <[email protected]>; Thu, 9 Dec 1999 16:10:42 -0800
Received: from tao.agoron.com (rem09.agoron.com [207.86.97.140])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id TAA06887
for <[email protected]>; Thu, 9 Dec 1999 19:10:37 -0500 (EST)
Message-Id: <[email protected]>
Date: Thu, 09 Dec 1999 19:14:32 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: does pine cache info about the inbox? big ramble
References: <Pine.A41.4.21.9912091540120.59222-100000@dante39.u.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Not only should we consider the fast connections on the mail server end, but
also consider that when pine reads a users /var/mail file its a local file, so
pine doesn't have to download anything, its just like opening a file in a text
editor.

PC-PINE I have noticed to be somewhat slower than other windows email clients,
but maybe with 4.10 its much faster!

---Andy

Scott Leibrand wrote:
>
> Are you running PC-Pine on your local PC, or are you telnetting in to a
> unix box and running unix Pine? If you're doing the latter, that's why
> it's so fast - all the work of loading the inbox is performed over the
> very fast connections at the mail server end, whereas the other programs
> you're using have to download the entire inbox over your slower internet
> connection.
>
> --
> Scott Leibrand
> [email protected]
> http://students.washington.edu/leibrand
> * RCW 19.190 notice: This email address is located in Washington State. *
> * Unsolicited commercial email may be billed $500 per message. *
>
> On Thu, 9 Dec 1999 [email protected] wrote:
>
> >
> > Does pine cache info about the inbox?
> >
> > I'm just wondering why the few GUI email clients I've used take FOREVER to
> > open my mailbox, but pine does it very quickly. I had hope with the new
> > Eudora version that supports IMAP, since the previous Eudora Lights I had
> > used were nice and quick.. But it took MINUTES to get the 900-something
> > messages on the server.. and I had to nuke the Inbox file it had and redo
> > it since it originally didn't have enough memory and unhelpfully gave me
> > a gazillion error messages, so I had to quit it -- and it ended up with
> > partially downloaded (or cached or whatever -- yes I'm using IMAP) messages
> > where I had the headers but couldn't get it to display some of the messages.
> >
> > ANYWAY -- sorry for the ramble.. I'm just wondering if I'm being deluded
> > into thinking pine isn't caching all of the inbox.. Is it? If not, why is
> > it a zillion times faster than Eudora or OE? (From my first use of this
> > new Eudora with the light/pay/ad model, I actually think I may prefer OE when
> > I have to use a GUI client.)
> > --
> > [email protected]
> >
> > --
> > -----------------------------------------------------------------
> > For information about this mailing list, and its archives, see:
> > http://www.washington.edu/pine/pine-info/
> > -----------------------------------------------------------------
> >

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 16:20:28 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28979;
Thu, 9 Dec 1999 16:20:27 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA11179;
Thu, 9 Dec 1999 16:20:27 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA00680;
Thu, 9 Dec 1999 16:18:37 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA79502
for <[email protected]>; Thu, 9 Dec 1999 16:13:59 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA06431
for <[email protected]>; Thu, 9 Dec 1999 16:13:58 -0800
Received: from jason01.u.washington.edu ([email protected] [140.142.70.24])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA10979
for <[email protected]>; Thu, 9 Dec 1999 16:13:58 -0800
Received: from dante24.u.washington.edu ([email protected] [140.142.15.74])
by jason01.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA48658
for <[email protected]>; Thu, 9 Dec 1999 16:13:57 -0800
Received: from localhost (leibrand@localhost)
by dante24.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA60310
for <[email protected]>; Thu, 9 Dec 1999 16:13:56 -0800
Message-Id: <Pine.A41.4.21.9912091612310.59206-100000@dante24.u.washington.edu>
Date: Thu, 9 Dec 1999 16:13: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: does pine cache info about the inbox? big ramble
In-Reply-To: <Pine.GSO.4.20.9912091602490.29679-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I don't know, then. I do know that Pine caches things like the address
book, but only for the current session. But to answer your question, I'd
have to know a lot more about how Pine and IMAP interact.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Thu, 9 Dec 1999 [email protected] wrote:

> On Thu, 9 Dec 1999, Scott Leibrand wrote:
>
> >Date: Thu, 9 Dec 1999 15:42:31 -0800 (PST)
> >From: Scott Leibrand <[email protected]>
> >To: Pine Discussion Forum <[email protected]>
> >Subject: Re: does pine cache info about the inbox? big ramble
> >
> >Are you running PC-Pine on your local PC, or are you telnetting in to a
> >unix box and running unix Pine? If you're doing the latter, that's why
> >it's so fast - all the work of loading the inbox is performed over the
> >very fast connections at the mail server end, whereas the other programs
> >you're using have to download the entire inbox over your slower internet
> >connection.
>
> I'm doing it on a UNIX shell..
>
> But I'm not running it on the SAME machine as the server.
>
> For example, I have UNIX pine on my MacOSX machine, and it gets
> mail from <machine>.apple.com
>
> GUI mailreaders ALSO get mail from <machine>.apple.com
>
> So why is pine so much faster?
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 17:42:45 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA00633;
Thu, 9 Dec 1999 17:42:44 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA13162;
Thu, 9 Dec 1999 17:42:43 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA00954;
Thu, 9 Dec 1999 17:40:49 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA39860
for <[email protected]>; Thu, 9 Dec 1999 17:36:16 -0800
Received: from vax.area.com (vax104.area.com [165.90.20.104])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id RAA23644
for <[email protected]>; Thu, 9 Dec 1999 17:36:10 -0800
Received: (qmail 11071 invoked by uid 1828); 10 Dec 1999 01:36:05 -0000
Message-Id: <Pine.GSO.4.20.9912091735380.29679-100000@vax>
Date: Thu, 9 Dec 1999 17:36: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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: does pine cache info about the inbox? big ramble
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 9 Dec 1999, Andy Malato wrote:
>Not only should we consider the fast connections on the mail server end, but
>also consider that when pine reads a users /var/mail file its a local file, so
>pine doesn't have to download anything, its just like opening a file in a text
>editor.

Wait, I'm talking about IMAP, and it's NOT on the same machine I'm running
pine on..

ohwell, I guess I started a big rambling discussion..

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 17:58: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA32379;
Thu, 9 Dec 1999 17:58:33 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA13450;
Thu, 9 Dec 1999 17:58:33 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA12476;
Thu, 9 Dec 1999 17:57:49 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA27826
for <[email protected]>; Thu, 9 Dec 1999 17:54:21 -0800
Received: from tao.agoron.com ([email protected] [206.181.233.66])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA26593
for <[email protected]>; Thu, 9 Dec 1999 17:54:21 -0800
Received: from tao.agoron.com (rem09.agoron.com [207.86.97.140])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id UAA10245
for <[email protected]>; Thu, 9 Dec 1999 20:54:19 -0500 (EST)
Message-Id: <[email protected]>
Date: Thu, 09 Dec 1999 20:58:14 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: does pine cache info about the inbox? big ramble
References: <Pine.GSO.4.20.9912091735380.29679-100000@vax>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

[email protected] wrote:

>
> Wait, I'm talking about IMAP, and it's NOT on the same machine I'm running
> pine on..
>

IMAP running on a different machine should still be fast, considering its on the
same local network as your PINE machine. Also IMAP is a bit faster than POP,
because of the fact it only downloads message headers and not that actual message
until you select that message for reading, as where the POP protocol downloads all
messages out of var/mail and removes them off the server by default.

I don't know why PINE is faster at doing this, but I do belive it is probably
because PINE was designed with IMAP capabilites in mind, where as other programs
such as outlook were designed for POP. I hope that says enough.

>
> ohwell, I guess I started a big rambling discussion..

Well that's how we all become a bit smarter and its a learning experience for all
:)

---Andy

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 9 Dec 1999 18:23:41 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA01163;
Thu, 9 Dec 1999 18:23:40 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA13948;
Thu, 9 Dec 1999 18:23:40 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA06096;
Thu, 9 Dec 1999 18:23:29 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA69920
for <[email protected]>; Thu, 9 Dec 1999 18:21:10 -0800
Received: from pipedream.smotrs.org (206-132-221-173.nas-1.RDL.primenet.com [206.132.221.173])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA27228
for <[email protected]>; Thu, 9 Dec 1999 18:21:08 -0800
Received: from localhost (skull@localhost)
by pipedream.smotrs.org (8.9.3/8.9.3) with ESMTP id SAA12255
for <[email protected]>; Thu, 9 Dec 1999 18:21:25 -0800
Message-Id: <[email protected]>
Date: Thu, 9 Dec 1999 18:21:24 -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: "S.Toms" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Colors
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Info <[email protected]>
X-Authentication-Warning: pipedream.smotrs.org: skull owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm wondering, what would prevent pine from displaying all 16 colors on
particular term's? If I use xterm, all 16 colors show no problem, if I use
rxvt or console, only the first 8 colors will show. I've tried compiling
the newest pine with the same results and have also eliminated app-default
files, as well as profile and bash files that set changes for terms but
still can only receive the first 8 colors (0-7).
I have a routine that shows all possible colors the term supports and it
displays all 16 colors as their supposed to be, but pine isn't recognizing
the colors 8-15, I can force it by changing the colors around and putting
the high intensity as 0-7 and low intensity as 8-15 but still, the colors
8-15 don't show up.

--
S.Toms - [email protected] - homepage is in the works
SuSE Linux v6.2+ - Kernel 2.2.13

A sine curve goes off to infinity or at least the end of the blackboard
-- Prof. Steiner

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 11 Dec 1999 23:00:20 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA13696;
Sat, 11 Dec 1999 23:00:19 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA05164;
Sat, 11 Dec 1999 23:00:18 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA01425;
Sat, 11 Dec 1999 22:59:45 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA28128
for <[email protected]>; Sat, 11 Dec 1999 22:54:10 -0800
Received: from betelgeuse.concentric.net (betelgeuse.concentric.net [207.155.183.76])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA23940
for <[email protected]>; Sat, 11 Dec 1999 22:54:10 -0800
Received: from qwestinternet.net (ts007d26.hil-ny.concentric.net [206.173.16.86])
by betelgeuse.concentric.net (8.8.5/)
id BAA04103; Sun, 12 Dec 1999 01:54:08 -0500 (EST)
[ConcentricHost MX Server]
Message-Id: <[email protected]>
Date: Sun, 12 Dec 1999 01:54:14 -0500
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: LINEart <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: how do i access comp.mail.pine?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

i've been trying unsuccessfully to access the PINE newsgroup referenced
by
http://www.washington.edu/pine/#Contact

this problem is redundant in Netscape Messenger, Outlook Express 5 and
PC-PINE 4.10
i can access other newsgroups without a problem. am i missing a
parameter in the server field?

i assume i'm supposed to enter comp.mail.pine and nothing more for the
server name . . .

thanks for your help

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 09:32: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA20469;
Sun, 12 Dec 1999 09:32:52 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA13721;
Sun, 12 Dec 1999 09:32:51 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA02613;
Sun, 12 Dec 1999 09:32:36 -0800
Received: from jason03.u.washington.edu ([email protected] [140.142.77.10])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA26864
for <[email protected]>; Sun, 12 Dec 1999 09:27:34 -0800
Received: from dante35.u.washington.edu ([email protected] [140.142.15.195])
by jason03.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA24698;
Sun, 12 Dec 1999 09:27:33 -0800
Received: from localhost (leibrand@localhost)
by dante35.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA91604;
Sun, 12 Dec 1999 09:27:33 -0800
Message-Id: <Pine.A41.4.21.9912120926360.25654-100000@dante35.u.washington.edu>
Date: Sun, 12 Dec 1999 09:27:33 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: LINEart <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

comp.mail.pine is a newsgroup, not a news server. You need to enter your
news server as per your ISP's instructions, and then select the
comp.mail.pine newsgroup.

Alternately, you can go to www.deja.com and do it all on the web.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Sun, 12 Dec 1999, LINEart wrote:

> i've been trying unsuccessfully to access the PINE newsgroup referenced
> by
> http://www.washington.edu/pine/#Contact
>
> this problem is redundant in Netscape Messenger, Outlook Express 5 and
> PC-PINE 4.10
> i can access other newsgroups without a problem. am i missing a
> parameter in the server field?
>
> i assume i'm supposed to enter comp.mail.pine and nothing more for the
> server name . . .
>
> thanks for your help
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 10:20:43 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA31559;
Sun, 12 Dec 1999 10:20:42 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14413;
Sun, 12 Dec 1999 10:20:41 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA28562;
Sun, 12 Dec 1999 10:20:29 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA26722
for <[email protected]>; Sun, 12 Dec 1999 10:15:26 -0800
Received: from jkazos.campus.vt.edu (IDENT:[email protected] [198.82.58.128])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14959
for <[email protected]>; Sun, 12 Dec 1999 10:15:25 -0800
Received: from localhost (IDENT:[email protected] [127.0.0.1])
by jkazos.campus.vt.edu (8.9.3/8.9.3) with ESMTP id NAA01838
for <[email protected]>; Sun, 12 Dec 1999 13:17:38 -0500
Message-Id: <[email protected]>
Date: Sun, 12 Dec 1999 13:17:38 -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: "John Anthony Kazos Jr." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Pine config of news server/login/groups
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

How can I specify a different news server user name than my local login?

How can I get it to automatically use a given name and password for news without prompting me every time?

Can I get it to add a newsgroup without downloading the full group list every time (or get it to not download the list more than once)? My server has 60,000+ groups.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 11:37: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA32115;
Sun, 12 Dec 1999 11:36:59 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA15471;
Sun, 12 Dec 1999 11:36:59 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA29809;
Sun, 12 Dec 1999 11:36:28 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA14190
for <[email protected]>; Sun, 12 Dec 1999 11:29:59 -0800
Received: from betelgeuse.concentric.net (betelgeuse.concentric.net [207.155.183.76])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA23480
for <[email protected]>; Sun, 12 Dec 1999 11:29:58 -0800
Received: from TATUM.WORKGROUP (ts004d32.nyh-ny.concentric.net [216.112.236.188])
by betelgeuse.concentric.net (8.8.5/)
id OAA09102; Sun, 12 Dec 1999 14:29:56 -0500 (EST)
[ConcentricHost MX Server]
Message-Id: <002001bf44d7$4ac8e340$bcec70d8@WORKGROUP>
Date: Sun, 12 Dec 1999 14:30:02 -0500
Reply-To: "LINEart" <[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: "LINEart" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
References: <Pine.A41.4.21.9912120926360.25654-100000@dante35.u.washington.edu>
X-To: "Pine Discussion Forum" <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

but my ISP never had to give me instructions on how to sign into Netscape's
newsgroup or Microsoft's betanews . .
that info was provided by Netscape and MS respectively.
shouldn't PINE be the most knowledgeable source for the data i need? After
all, i don't thnk that my ISP even knows about PINE.

ps (sorry this first posting replied directly to you and not the group Mr.
Leibrand)
----- Original Message -----
From: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Sent: Sunday, December 12, 1999 12:27 PM
Subject: Re: how do i access comp.mail.pine?

> comp.mail.pine is a newsgroup, not a news server. You need to enter your
> news server as per your ISP's instructions, and then select the
> comp.mail.pine newsgroup.
>
> Alternately, you can go to www.deja.com and do it all on the web.
>
> --
> Scott Leibrand
> [email protected]
> http://students.washington.edu/leibrand
> * RCW 19.190 notice: This email address is located in Washington State. *
> * Unsolicited commercial email may be billed $500 per message. *
>
> On Sun, 12 Dec 1999, LINEart wrote:
>
> > i've been trying unsuccessfully to access the PINE newsgroup referenced
> > by
> > http://www.washington.edu/pine/#Contact
> >
> > this problem is redundant in Netscape Messenger, Outlook Express 5 and
> > PC-PINE 4.10
> > i can access other newsgroups without a problem. am i missing a
> > parameter in the server field?
> >
> > i assume i'm supposed to enter comp.mail.pine and nothing more for the
> > server name . . .
> >
> > thanks for your help
> >
> > --
> > -----------------------------------------------------------------
> > For information about this mailing list, and its archives, see:
> > http://www.washington.edu/pine/pine-info/
> > -----------------------------------------------------------------
> >
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 11:46:36 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA19094;
Sun, 12 Dec 1999 11:46:35 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA16441;
Sun, 12 Dec 1999 11:46:34 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA24440;
Sun, 12 Dec 1999 11:45:56 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA44642
for <[email protected]>; Sun, 12 Dec 1999 11:41:38 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA19860
for <[email protected]>; Sun, 12 Dec 1999 11:41:38 -0800
Received: (qmail 138 invoked from network); 12 Dec 1999 19:41:37 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 12 Dec 1999 19:41:37 -0000
Message-Id: <[email protected]>
Date: Sun, 12 Dec 1999 12:42:23 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <002001bf44d7$4ac8e340$bcec70d8@WORKGROUP>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: LINEart <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Use Scott's "do it all on the Web" alternative, which doesn't require your
ISP's instructions.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Sun, 12 Dec 1999, LINEart wrote:

> but my ISP never had to give me instructions on how to sign into Netscape's
> newsgroup or Microsoft's betanews . .
> that info was provided by Netscape and MS respectively.
> shouldn't PINE be the most knowledgeable source for the data i need? After
> all, i don't thnk that my ISP even knows about PINE.
>
> ps (sorry this first posting replied directly to you and not the group Mr.
> Leibrand)
> ----- Original Message -----
> From: Scott Leibrand <[email protected]>
> To: Pine Discussion Forum <[email protected]>
> Sent: Sunday, December 12, 1999 12:27 PM
> Subject: Re: how do i access comp.mail.pine?
>
>
> > comp.mail.pine is a newsgroup, not a news server. You need to enter your
> > news server as per your ISP's instructions, and then select the
> > comp.mail.pine newsgroup.
> >
> > Alternately, you can go to www.deja.com and do it all on the web.
> >
> > --
> > Scott Leibrand
> > [email protected]
> > http://students.washington.edu/leibrand
> > * RCW 19.190 notice: This email address is located in Washington State. *
> > * Unsolicited commercial email may be billed $500 per message. *
> >
> > On Sun, 12 Dec 1999, LINEart wrote:
> >
> > > i've been trying unsuccessfully to access the PINE newsgroup referenced
> > > by
> > > http://www.washington.edu/pine/#Contact
> > >
> > > this problem is redundant in Netscape Messenger, Outlook Express 5 and
> > > PC-PINE 4.10
> > > i can access other newsgroups without a problem. am i missing a
> > > parameter in the server field?
> > >
> > > i assume i'm supposed to enter comp.mail.pine and nothing more for the
> > > server name . . .
> > >
> > > thanks for your help
> > >
> > > --
> > > -----------------------------------------------------------------
> > > For information about this mailing list, and its archives, see:
> > > http://www.washington.edu/pine/pine-info/
> > > -----------------------------------------------------------------
> > >
> >
> >
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 12:08: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32478;
Sun, 12 Dec 1999 12:08:26 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA15926;
Sun, 12 Dec 1999 12:08:26 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA00906;
Sun, 12 Dec 1999 12:08:07 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA42762
for <[email protected]>; Sun, 12 Dec 1999 12:02:49 -0800
Received: from betelgeuse.concentric.net (betelgeuse.concentric.net [207.155.183.76])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA15766
for <[email protected]>; Sun, 12 Dec 1999 12:02:49 -0800
Received: from TATUM.WORKGROUP (ts023d48.hil-ny.concentric.net [206.173.23.156])
by betelgeuse.concentric.net (8.8.5/)
id PAA13252; Sun, 12 Dec 1999 15:02:47 -0500 (EST)
[ConcentricHost MX Server]
Message-Id: <003201bf44db$e1453900$bcec70d8@WORKGROUP>
Date: Sun, 12 Dec 1999 15:02:52 -0500
Reply-To: "LINEart" <[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: "LINEart" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
References: <[email protected]>
X-To: "Pine Discussion Forum" <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

thanks mr Kurtzberg. i've spent the past 10 minutes at deja browsing
through different postings. i just hate having to wait on the web page to
refresh each time i want to go to a different message in the thread. if i
were on a T1 line it would be alright. but for now i'll stick with deja
anyway.
----- Original Message -----
From: Seth Kurtzberg <[email protected]>
To: LINEart <[email protected]>
Cc: Pine Discussion Forum <[email protected]>
Sent: Sunday, December 12, 1999 2:42 PM
Subject: Re: how do i access comp.mail.pine?

> Use Scott's "do it all on the Web" alternative, which doesn't require your
> ISP's instructions.
>
> Seth Kurtzberg
> Machine Independent Software
> Cell (602) 478-5511
> Fax: (480) 614-8909
> email: [email protected]
> pager: 888-605-9296 or email [email protected]
>
>
> On Sun, 12 Dec 1999, LINEart wrote:
>
> > but my ISP never had to give me instructions on how to sign into
Netscape's
> > newsgroup or Microsoft's betanews . .
> > that info was provided by Netscape and MS respectively.
> > shouldn't PINE be the most knowledgeable source for the data i need?
After
> > all, i don't thnk that my ISP even knows about PINE.
> >
> > ps (sorry this first posting replied directly to you and not the group
Mr.
> > Leibrand)
> > ----- Original Message -----
> > From: Scott Leibrand <[email protected]>
> > To: Pine Discussion Forum <[email protected]>
> > Sent: Sunday, December 12, 1999 12:27 PM
> > Subject: Re: how do i access comp.mail.pine?
> >
> >
> > > comp.mail.pine is a newsgroup, not a news server. You need to enter
your
> > > news server as per your ISP's instructions, and then select the
> > > comp.mail.pine newsgroup.
> > >
> > > Alternately, you can go to www.deja.com and do it all on the web.
> > >
> > > --
> > > Scott Leibrand
> > > [email protected]
> > > http://students.washington.edu/leibrand
> > > * RCW 19.190 notice: This email address is located in Washington
State. *
> > > * Unsolicited commercial email may be billed $500 per message.
*
> > >
> > > On Sun, 12 Dec 1999, LINEart wrote:
> > >
> > > > i've been trying unsuccessfully to access the PINE newsgroup
referenced
> > > > by
> > > > http://www.washington.edu/pine/#Contact
> > > >
> > > > this problem is redundant in Netscape Messenger, Outlook Express 5
and
> > > > PC-PINE 4.10
> > > > i can access other newsgroups without a problem. am i missing a
> > > > parameter in the server field?
> > > >
> > > > i assume i'm supposed to enter comp.mail.pine and nothing more for
the
> > > > server name . . .
> > > >
> > > > thanks for your help
> > > >
> > > > --
> > > > -----------------------------------------------------------------
> > > > For information about this mailing list, and its archives, see:
> > > > http://www.washington.edu/pine/pine-info/
> > > > -----------------------------------------------------------------
> > > >
> > >
> > >
> >
> >
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 12:42: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA22140;
Sun, 12 Dec 1999 12:42:00 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA16386;
Sun, 12 Dec 1999 12:42:00 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA25838;
Sun, 12 Dec 1999 12:41:24 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA28238
for <[email protected]>; Sun, 12 Dec 1999 12:36:15 -0800
Received: from chinet.com ([email protected] [209.219.112.20] (may be forged))
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA23504
for <[email protected]>; Sun, 12 Dec 1999 12:36:13 -0800
Received: from localhost (ahk@localhost)
by chinet.com (8.9.3/8.9.3) with ESMTP id OAA01850
for <[email protected]>; Sun, 12 Dec 1999 14:36:12 -0600
Message-Id: <[email protected]>
Date: Sun, 12 Dec 1999 14:36:12 -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: "Adam H. Kerman" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <002001bf44d7$4ac8e340$bcec70d8@WORKGROUP>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

>From: LINEart <[email protected]>
>Date: Sun, 12 Dec 1999 14:30:02 -0500

>but my ISP never had to give me instructions on how to sign into Netscape's
>newsgroup or Microsoft's betanews . .
>that info was provided by Netscape and MS respectively.
>shouldn't PINE be the most knowledgeable source for the data i need? After
>all, i don't thnk that my ISP even knows about PINE.

How would Netscape and MS know what news servers you are authorized by your ISP
to use? If your ISP failed to tell you, it's your responsibility to ask. If you
cannot get satisfactory customer support, drop them.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 15:25:33 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA01511;
Sun, 12 Dec 1999 15:25:31 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA19714;
Sun, 12 Dec 1999 15:25:31 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA09815;
Sun, 12 Dec 1999 15:24:53 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA53970
for <[email protected]>; Sun, 12 Dec 1999 15:20:40 -0800
Received: from vax.area.com (vax44.area.com [165.90.20.44])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id PAA26371
for <[email protected]>; Sun, 12 Dec 1999 15:20:39 -0800
Received: (qmail 24823 invoked by uid 1828); 12 Dec 1999 23:20:38 -0000
Message-Id: <Pine.GSO.4.20.9912121517110.21991-100000@vax>
Date: Sun, 12 Dec 1999 15:20:38 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 12 Dec 1999, John Anthony Kazos Jr. wrote:
>How can I specify a different news server user name than my local login?
>
>How can I get it to automatically use a given name and password for news
>without prompting me every time?

I don't know, but I sure wish that I could figure out how to get pine to
log into my mail account without prompting me. I mean, I of course
realize that then if anyone could log in as me, they could get to my email
and send email as me. I'm willing to take that risk, and people do it all
the time (including me) with GUI programs. Seems that pine should allow this
too.

>Can I get it to add a newsgroup without downloading the full group list every
>time (or get it to not download the list more than once)? My server has
>60,000+ groups.

You need to add a "Collection" for the news server. Then you can add
newsgroups to the list.

I finally can recompile trn on my machine at work some time, so I am more
interested in this for curiousity's sake, but I was using pine to read
some internal newsgroups for a while.

I never figured out how to get it to show me ALREADY READ messages. I mean,
as far as I could tell, I have to "Delete" messages just like pieces of email
to get them to not show up all of the time. But if I want to look at a
previously read message, how do I do it?

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 20:09:58 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA03361;
Sun, 12 Dec 1999 20:09:56 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA23986;
Sun, 12 Dec 1999 20:09:56 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA21241;
Sun, 12 Dec 1999 20:09:27 -0800
Received: from jason03.u.washington.edu ([email protected] [140.142.77.10])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA59382
for <[email protected]>; Sun, 12 Dec 1999 20:03:50 -0800
Received: from dante09.u.washington.edu ([email protected] [140.142.15.19])
by jason03.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA24776
for <[email protected]>; Sun, 12 Dec 1999 20:03:49 -0800
Received: from localhost (leibrand@localhost)
by dante09.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA48264
for <[email protected]>; Sun, 12 Dec 1999 20:03:49 -0800
Message-Id: <Pine.A41.4.21.9912121958590.105430-100000@dante09.u.washington.edu>
Date: Sun, 12 Dec 1999 20:03:49 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <Pine.GSO.4.20.9912121517110.21991-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 12 Dec 1999 [email protected] wrote:

> On Sun, 12 Dec 1999, John Anthony Kazos Jr. wrote:
> >How can I specify a different news server user name than my local login?

Normall, you add /user=username to the end of the hostname, like this:

news.u.washington.edu/user=leibrand

I assume that will work for news, too.

> >How can I get it to automatically use a given name and password for news
> >without prompting me every time?
>
> I don't know, but I sure wish that I could figure out how to get pine to
> log into my mail account without prompting me. I mean, I of course
> realize that then if anyone could log in as me, they could get to my email
> and send email as me. I'm willing to take that risk, and people do it all
> the time (including me) with GUI programs. Seems that pine should allow this
> too.

You can set up a Pine password file, but it requires either a hidden
configuration option or a compile-time option be changed. I think Nancy's
page has something on this.

Alternately, and far more securely, you can set up Pine to use SSH and set
up private and public keys for passwordless access. This requires that
your mail server supports SSH logins and gives you direct access to your
files. Reply if you'd like directions on doing this.

> I never figured out how to get it to show me ALREADY READ messages. I mean,
> as far as I could tell, I have to "Delete" messages just like pieces of email
> to get them to not show up all of the time. But if I want to look at a
> previously read message, how do I do it?
>

There's an unexclude command in News that basically undoes the expunge
command.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 20:15: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA03362;
Sun, 12 Dec 1999 20:15:27 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA22895;
Sun, 12 Dec 1999 20:15:26 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA16068;
Sun, 12 Dec 1999 20:14:51 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA16394
for <[email protected]>; Sun, 12 Dec 1999 20:08:50 -0800
Received: from dante09.u.washington.edu ([email protected] [140.142.15.19])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA16756
for <[email protected]>; Sun, 12 Dec 1999 20:08:49 -0800
Received: from localhost (leibrand@localhost)
by dante09.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA102456
for <[email protected]>; Sun, 12 Dec 1999 20:08:49 -0800
Message-Id: <Pine.A41.4.21.9912122004480.105430-100000@dante09.u.washington.edu>
Date: Sun, 12 Dec 1999 20:08:48 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Exactly. :)

At some point, either you, someone else, or a piece of software from your
ISP that you installed configured MS and Netscape to access your ISP's
mailserver. If either of them works to do newsgroups, go into its Options
or Preferences and look for your mail server's name.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Sun, 12 Dec 1999, Adam H. Kerman wrote:

> >From: LINEart <[email protected]>
> >Date: Sun, 12 Dec 1999 14:30:02 -0500
>
> >but my ISP never had to give me instructions on how to sign into Netscape's
> >newsgroup or Microsoft's betanews . .
> >that info was provided by Netscape and MS respectively.
> >shouldn't PINE be the most knowledgeable source for the data i need? After
> >all, i don't thnk that my ISP even knows about PINE.
>
> How would Netscape and MS know what news servers you are authorized by your ISP
> to use? If your ISP failed to tell you, it's your responsibility to ask. If you
> cannot get satisfactory customer support, drop them.
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 20:59:11 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA04184;
Sun, 12 Dec 1999 20:59:09 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA23567;
Sun, 12 Dec 1999 20:59:09 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA12661;
Sun, 12 Dec 1999 20:58:54 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA26784
for <[email protected]>; Sun, 12 Dec 1999 20:53:59 -0800
Received: from betelgeuse.concentric.net (betelgeuse.concentric.net [207.155.183.76])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA17173
for <[email protected]>; Sun, 12 Dec 1999 20:53:59 -0800
Received: from TATUM.WORKGROUP (ts005d09.nyh-ny.concentric.net [216.112.236.213])
by betelgeuse.concentric.net (8.8.5/)
id XAA00038; Sun, 12 Dec 1999 23:53:57 -0500 (EST)
[ConcentricHost MX Server]
Message-Id: <003001bf4526$14a821a0$d5ec70d8@WORKGROUP>
Date: Sun, 12 Dec 1999 23:53:59 -0500
Reply-To: "LINEart" <[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: "LINEart" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
References: <Pine.A41.4.21.9912122004480.105430-100000@dante09.u.washington.edu>
X-To: "Pine Discussion Forum" <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

hhmm.

not sure i understand. i, not an automatic wizard, had to configure all of
my mailsoftware to access any mail and/or news accounts i've ever had. (the
only time this was not true was within a network at school). i'm using pop3

for news.u.washington.edu, for example (and i'm not a univ. of washington
employee/student) i can gain access, at least to the level of contacting the
server so it gives me back a listing of available groups. the server that
i'm contacting is news.u.washington.edu, not my ISP. similarly, if i have
to access my school e-mail account which is served from an indy2 (unix) i've
got to enter the name of my school server in the appropriate field in my
mailsoftware options. this is not my ISP server's IP address.

of course MS and Netscape wouldn't know anything about the PINE server's IP
address, but why would my ISP? PINE should be the source for that, right?

are you suggesting, though, that my ISP could be denying my access to the
server name comp.mail.pine? i'm not getting an "access denied" message,
just a "server not found" one.

thanks kindly for all of your help
----- Original Message -----
From: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Sent: Sunday, December 12, 1999 11:08 PM
Subject: Re: how do i access comp.mail.pine?

> Exactly. :)
>
> At some point, either you, someone else, or a piece of software from your
> ISP that you installed configured MS and Netscape to access your ISP's
> mailserver. If either of them works to do newsgroups, go into its Options
> or Preferences and look for your mail server's name.
>
> --
> Scott Leibrand
> [email protected]
> http://students.washington.edu/leibrand
> * RCW 19.190 notice: This email address is located in Washington State. *
> * Unsolicited commercial email may be billed $500 per message. *
>
> On Sun, 12 Dec 1999, Adam H. Kerman wrote:
>
> > >From: LINEart <[email protected]>
> > >Date: Sun, 12 Dec 1999 14:30:02 -0500
> >
> > >but my ISP never had to give me instructions on how to sign into
Netscape's
> > >newsgroup or Microsoft's betanews . .
> > >that info was provided by Netscape and MS respectively.
> > >shouldn't PINE be the most knowledgeable source for the data i need?
After
> > >all, i don't thnk that my ISP even knows about PINE.
> >
> > How would Netscape and MS know what news servers you are authorized by
your ISP
> > to use? If your ISP failed to tell you, it's your responsibility to ask.
If you
> > cannot get satisfactory customer support, drop them.
> >
> >
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 21:14: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04297;
Sun, 12 Dec 1999 21:14:25 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA23798;
Sun, 12 Dec 1999 21:14:24 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA12864;
Sun, 12 Dec 1999 21:14:02 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA74686
for <[email protected]>; Sun, 12 Dec 1999 21:08:58 -0800
Received: from itlinfosys.com (infosys.itlinfosys.com [206.236.143.2])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id VAA31219
for <[email protected]>; Sun, 12 Dec 1999 21:08:57 -0800
Received: from viruswall1 by itlinfosys.com (SMI-8.6/SMI-SVR4)
id VAA02246; Sun, 12 Dec 1999 21:08:56 -0800
Received: from 192.168.139.6 by viruswall1 (InterScan E-Mail VirusWall NT); Sun, 12 Dec 1999 21:15:54 -0800 (Pacific Standard Time)
Received: from kec-01-msg.kec.inf.com (KEC-01-MSG [204.4.54.41]) by gatemsg02.itlinfosys.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
id X8DXCRRN; Sun, 12 Dec 1999 21:02:03 -0800
Received: from [204.4.55.198] (204.4.55.198 [204.4.55.198]) by kec-01-msg.kec.inf.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
id YG1TN336; Mon, 13 Dec 1999 10:37:34 +0530
Received: from infpc155 by [204.4.55.198]
via smtpd (for kec-01-msg.kec.inf.com [204.4.54.41]) with SMTP; 13 Dec 1999 05:10:03 UT
Received: from ipkpc275 (IDENT:ssaxena@ipkpc275 [206.236.134.125])
by sandesh.ntl.inf.com (8.9.3/8.9.3) with ESMTP id NAA24275
for <[email protected]>; Mon, 13 Dec 1999 13:10:54 +0400
Message-Id: <Pine.LNX.4.21.9912131034010.22763-100000@ipkpc275.infosys.ernet.in>
Date: Mon, 13 Dec 1999 10:40:25 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Shobhit Saxena <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <Pine.A41.4.21.9912122004480.105430-100000@dante09.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

As far as Netscape is concerned, the news server field is set to "news"
by default, unless configured otherwise. So, if the news server has an
alias "news" as well (as is the case in our Intranet also), no other
configuration is required to browse the NGs.

--
Sigh. I like to think it's just the Linux people who want to be on
the "leading edge" so bad they walk right off the precipice.
(Craig E. Groeschel)

On Sun, 12 Dec 1999, Scott Leibrand wrote:

> Exactly. :)
>
> At some point, either you, someone else, or a piece of software from your
> ISP that you installed configured MS and Netscape to access your ISP's
> mailserver. If either of them works to do newsgroups, go into its Options
> or Preferences and look for your mail server's name.
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 21:23:50 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04712;
Sun, 12 Dec 1999 21:23:49 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA23937;
Sun, 12 Dec 1999 21:23:48 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA22639;
Sun, 12 Dec 1999 21:23:25 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA31372
for <[email protected]>; Sun, 12 Dec 1999 21:19:09 -0800
Received: from dante28.u.washington.edu ([email protected] [140.142.15.83])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA19386;
Sun, 12 Dec 1999 21:19:08 -0800
Received: from localhost (leibrand@localhost)
by dante28.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA68750;
Sun, 12 Dec 1999 21:19:08 -0800
Message-Id: <Pine.A41.4.21.9912122117280.78648-100000@dante28.u.washington.edu>
Date: Sun, 12 Dec 1999 21:19:08 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <Pine.LNX.4.21.9912131034010.22763-100000@ipkpc275.infosys.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Shobhit Saxena <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Good point. I hadn't considered that, but it makes a lot of sense. If
you're running Pine on the same machine, try putting in just news as your
news server. Otherwise, the "alias" for news would probably be in the
LMHOSTS file or in the domain suffix search order in the DUN TCP/IP
properties. If it's the latter, then your news server is
news.yourdomainsuffix.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Mon, 13 Dec 1999, Shobhit Saxena wrote:

>
> As far as Netscape is concerned, the news server field is set to "news"
> by default, unless configured otherwise. So, if the news server has an
> alias "news" as well (as is the case in our Intranet also), no other
> configuration is required to browse the NGs.
>
> --
> Sigh. I like to think it's just the Linux people who want to be on
> the "leading edge" so bad they walk right off the precipice.
> (Craig E. Groeschel)
>
> On Sun, 12 Dec 1999, Scott Leibrand wrote:
>
> > Exactly. :)
> >
> > At some point, either you, someone else, or a piece of software from your
> > ISP that you installed configured MS and Netscape to access your ISP's
> > mailserver. If either of them works to do newsgroups, go into its Options
> > or Preferences and look for your mail server's name.
> >
> >
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 12 Dec 1999 21:29: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04628;
Sun, 12 Dec 1999 21:29:36 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA24023;
Sun, 12 Dec 1999 21:29:35 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA17535;
Sun, 12 Dec 1999 21:29:11 -0800
Received: from jason01.u.washington.edu ([email protected] [140.142.70.24])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA58394
for <[email protected]>; Sun, 12 Dec 1999 21:24:27 -0800
Received: from dante28.u.washington.edu ([email protected] [140.142.15.83])
by jason01.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA29842;
Sun, 12 Dec 1999 21:24:26 -0800
Received: from localhost (leibrand@localhost)
by dante28.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA41796;
Sun, 12 Dec 1999 21:24:25 -0800
Message-Id: <Pine.A41.4.21.9912122119120.78648-100000@dante28.u.washington.edu>
Date: Sun, 12 Dec 1999 21:24: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <003001bf4526$14a821a0$d5ec70d8@WORKGROUP>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: LINEart <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Ok. The important points here are these:

comp.mail.pine is just the name of a newsgroup. The way USENET is set up,
news servers on all the ISPs bounce news messages around between
themselves, and organize those messages by which newsgroup (like
comp.mail.pine) they were sent to. Therefore, you can't access
comp.mail.pine itself without going through a news server, because
comp.mail.pine is nothing more than a category under which messages are
sent.

News servers are set up like SMTP servers - each ISP has its own that is
only accessible by its own customers. That way passwords are not
required, but there is still control over who can post where.

Therefore, you need to access your ISP's mail server (or any other mail
server that will allow access from your domain) and get the messages that
are in the comp.mail.pine newsgroup. You can connect to
news.u.washington.edu, because it's a machine on the internet, but you
can't do anything there because you're not in the washington.edu
domain. The same would be true if I tried to access qwestinternet's news
server, whatever it's called.

Does that make sense?

Basically, this still boils down to getting the address of a news server
you have access to, which probably means your ISP's news server.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Sun, 12 Dec 1999, LINEart wrote:

> hhmm.
>
> not sure i understand. i, not an automatic wizard, had to configure all of
> my mailsoftware to access any mail and/or news accounts i've ever had. (the
> only time this was not true was within a network at school). i'm using pop3
>
> for news.u.washington.edu, for example (and i'm not a univ. of washington
> employee/student) i can gain access, at least to the level of contacting the
> server so it gives me back a listing of available groups. the server that
> i'm contacting is news.u.washington.edu, not my ISP. similarly, if i have
> to access my school e-mail account which is served from an indy2 (unix) i've
> got to enter the name of my school server in the appropriate field in my
> mailsoftware options. this is not my ISP server's IP address.
>
> of course MS and Netscape wouldn't know anything about the PINE server's IP
> address, but why would my ISP? PINE should be the source for that, right?
>
> are you suggesting, though, that my ISP could be denying my access to the
> server name comp.mail.pine? i'm not getting an "access denied" message,
> just a "server not found" one.
>
>
> thanks kindly for all of your help
> ----- Original Message -----
> From: Scott Leibrand <[email protected]>
> To: Pine Discussion Forum <[email protected]>
> Sent: Sunday, December 12, 1999 11:08 PM
> Subject: Re: how do i access comp.mail.pine?
>
>
> > Exactly. :)
> >
> > At some point, either you, someone else, or a piece of software from your
> > ISP that you installed configured MS and Netscape to access your ISP's
> > mailserver. If either of them works to do newsgroups, go into its Options
> > or Preferences and look for your mail server's name.
> >
> > --
> > Scott Leibrand
> > [email protected]
> > http://students.washington.edu/leibrand
> > * RCW 19.190 notice: This email address is located in Washington State. *
> > * Unsolicited commercial email may be billed $500 per message. *
> >
> > On Sun, 12 Dec 1999, Adam H. Kerman wrote:
> >
> > > >From: LINEart <[email protected]>
> > > >Date: Sun, 12 Dec 1999 14:30:02 -0500
> > >
> > > >but my ISP never had to give me instructions on how to sign into
> Netscape's
> > > >newsgroup or Microsoft's betanews . .
> > > >that info was provided by Netscape and MS respectively.
> > > >shouldn't PINE be the most knowledgeable source for the data i need?
> After
> > > >all, i don't thnk that my ISP even knows about PINE.
> > >
> > > How would Netscape and MS know what news servers you are authorized by
> your ISP
> > > to use? If your ISP failed to tell you, it's your responsibility to ask.
> If you
> > > cannot get satisfactory customer support, drop them.
> > >
> > >
> >
> >
>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 06:45:18 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA10372
for <[email protected]>; Mon, 13 Dec 1999 06:45:17 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA32664;
Mon, 13 Dec 1999 06:45:15 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA18064;
Mon, 13 Dec 1999 06:42:12 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA93240
for <[email protected]>; Mon, 13 Dec 1999 06:38:18 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA32050
for <[email protected]>; Mon, 13 Dec 1999 06:38:17 -0800
Received: from jason01.u.washington.edu ([email protected] [140.142.70.24])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA32551
for <[email protected]>; Mon, 13 Dec 1999 06:38:17 -0800
Received: from dante20.u.washington.edu ([email protected] [140.142.15.70])
by jason01.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA41036
for <[email protected]>; Mon, 13 Dec 1999 06:38:17 -0800
Received: from localhost (leibrand@localhost)
by dante20.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA45638
for <[email protected]>; Mon, 13 Dec 1999 06:38:16 -0800
Message-Id: <Pine.A41.4.21.9912130637540.43962-100000@dante20.u.washington.edu>
Date: Mon, 13 Dec 1999 06:38: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 12 Dec 1999 [email protected] wrote:

> On Sun, 12 Dec 1999, Scott Leibrand wrote:
> >You can set up a Pine password file, but it requires either a hidden
> >configuration option or a compile-time option be changed. I think Nancy's
> >page has something on this.
>
> I looked at that weeks or months ago the last time someone mentioned it..
> It was for PC Pine, not UNIX pine.

Same thing will work for Unix Pine. You just have to define the file and
create it.

> >Alternately, and far more securely, you can set up Pine to use SSH and set
> >up private and public keys for passwordless access. This requires that
> >your mail server supports SSH logins and gives you direct access to your
> >files. Reply if you'd like directions on doing this.
>
> Will this work on an IMAP account? I don't want "direct access to my files".
> I want IMAP access.
>
> Jeez, all I want is it to log in for me!
>

Yes. You still run Pine the same way as ever, but you need to be able to
place your public key file in the .ssh directory (in the .authorized_keys
file). That's all I meant by the direct file access thing.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 10:27: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA19033
for <[email protected]>; Mon, 13 Dec 1999 10:27:53 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA05451;
Mon, 13 Dec 1999 10:27:50 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA27745;
Mon, 13 Dec 1999 10:22:38 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA58496
for <[email protected]>; Mon, 13 Dec 1999 10:20:30 -0800
Received: from fn1.freenet.edmonton.ab.ca (IDENT:[email protected] [198.161.206.8])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26890
for <[email protected]>; Mon, 13 Dec 1999 10:20:30 -0800
Received: from fn2.freenet.edmonton.ab.ca
([email protected] [198.161.206.7])
by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3)
with ESMTP id LAA139710
for <[email protected]>;
Mon, 13 Dec 1999 11:20:28 -0700
Received: from localhost
(azz@localhost)
by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3)
with SMTP id LAA38866
for <[email protected]>;
Mon, 13 Dec 1999 11:20:27 -0700
Message-Id: <Pine.A41.3.95.991213111952.58686B-100000@fn2.freenet.edmonton.ab.ca>
Date: Mon, 13 Dec 1999 11:20:27 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: unsubscribe
In-Reply-To: <Pine.A41.4.21.9912130637540.43962-100000@dante20.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 10:44:28 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA11697;
Mon, 13 Dec 1999 10:44:27 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA07395;
Mon, 13 Dec 1999 10:44:26 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA14527;
Mon, 13 Dec 1999 10:41:26 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA59250
for <[email protected]>; Mon, 13 Dec 1999 10:39:48 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA06853
for <[email protected]>; Mon, 13 Dec 1999 10:39:48 -0800
Received: from jason01.u.washington.edu ([email protected] [140.142.70.24])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA05742
for <[email protected]>; Mon, 13 Dec 1999 10:39:48 -0800
Received: from dante07.u.washington.edu ([email protected] [140.142.15.9])
by jason01.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA20320
for <[email protected]>; Mon, 13 Dec 1999 10:39:47 -0800
Received: from localhost (leibrand@localhost)
by dante07.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA97956
for <[email protected]>; Mon, 13 Dec 1999 10:39:45 -0800
Message-Id: <Pine.A41.4.21.9912131016110.44250-100000@dante07.u.washington.edu>
Date: Mon, 13 Dec 1999 10: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <Pine.GSO.4.20.9912131015020.2327-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 13 Dec 1999 [email protected] wrote:

> On Mon, 13 Dec 1999, Scott Leibrand wrote:
>
> >On Sun, 12 Dec 1999 [email protected] wrote:
> >
> >> On Sun, 12 Dec 1999, Scott Leibrand wrote:
> >> >You can set up a Pine password file, but it requires either a hidden
> >> >configuration option or a compile-time option be changed. I think Nancy's
> >> >page has something on this.
> >>
> >> I looked at that weeks or months ago the last time someone mentioned it..
> >> It was for PC Pine, not UNIX pine.
> >
> >Same thing will work for Unix Pine. You just have to define the file and
> >create it.
>
> well, I could swear that the descriptions talked about weird Windows directories
> that don't exist on UNIX.. but I guess I'll look again.

Yeah, it does, but that's just because the page was written for PC-Pine.
If you change the directories to the appropriate Unix ones, I think it
should work.

> >> >Alternately, and far more securely, you can set up Pine to use SSH and set
> >> >up private and public keys for passwordless access. This requires that
> >> >your mail server supports SSH logins and gives you direct access to your
> >> >files. Reply if you'd like directions on doing this.
> >>
> >> Will this work on an IMAP account? I don't want "direct access to my files".
> >> I want IMAP access.
> >>
> >> Jeez, all I want is it to log in for me!
> >>
> >
> >Yes. You still run Pine the same way as ever, but you need to be able to
> >place your public key file in the .ssh directory (in the .authorized_keys
> >file). That's all I meant by the direct file access thing.
>
> ok, thanks.. so could you give the directions on doing this?
>

First, you have to set up passwordless access with SSH. That involves
running ssh-keygen to generate a private-public key pair, transfering the
public key to your mail server and putting it on its own line in the
~/.ssh/authorized_keys file.

Then put the following lines in your .pinerc:

# Sets the name of the command used to open a UNIX secure shell connection.
# Tyically this is /usr/local/bin/ssh.
ssh-path=/usr/local/bin/ssh

# Sets the format of the command used to open a UNIX secure
# shell connection. The default is "%s %s -l %s exec /etc/r%sd"
# NOTE: the 4 (four) "%s" entries MUST exist in the provided command
# where the first is for the command's path, the second is for the
# host to connnect to, the third is for the user to connect as, and the
# fourth is for the connection method (typically "imap")
ssh-command=%s %s -q -l %s exec /etc/r%sd

If you don't have those commented lines already (I know Pine 4.10 didn't),
do the same thing except use the rsh-path and rsh-command lines that
already exist. That will just trick Pine into thinking its using rsh when
it's using SSH, which has no effect on how it works.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 11:18:38 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA20585;
Mon, 13 Dec 1999 11:18:37 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA06894;
Mon, 13 Dec 1999 11:18:36 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA06822;
Mon, 13 Dec 1999 11:15:29 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA86512
for <[email protected]>; Mon, 13 Dec 1999 11:13:52 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA17269
for <[email protected]>; Mon, 13 Dec 1999 11:13:52 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA08388
for <[email protected]>; Mon, 13 Dec 1999 11:13:52 -0800
Received: from dante07.u.washington.edu ([email protected] [140.142.15.9])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA41002
for <[email protected]>; Mon, 13 Dec 1999 11:13:50 -0800
Received: from localhost (leibrand@localhost)
by dante07.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA17418
for <[email protected]>; Mon, 13 Dec 1999 11:13:49 -0800
Message-Id: <Pine.A41.4.21.9912131112340.52994-100000@dante07.u.washington.edu>
Date: Mon, 13 Dec 1999 11:13:49 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <Pine.GSO.4.20.9912131046340.2327-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

During your session, it's stored in memory. If you want to save your
password between sessions, you need to tell it where to save it by
defining the PASSFILE variable. Here's what it says at
<http://ism.ucdavis.edu/info/pine/installation.html>:

PASSFILE

WARNING! Turning this on is very dangerous and should probably not be
done, except on single user systems! For PC-Pine, this is turned on by
default and set to the filename PINE.PWD. You may enable it for Unix
systems by defining PASSFILE to be a filename which will be located in the
same directory as the pinerc file, usually the home directory. See
/pine/osdep/os-wnt.h for an example showing how to define it.

The file is used to save passwords from one session to the next. Even if
you define PASSFILE when you compile Pine, password saving will not be
enabled by default, but requires the existence of the file (the name of
which is the value of PASSFILE). Even with the existence of this file, the
user must still acknowledge a prompt before the password is saved to the
file. If Pine is configured to access several different IMAP servers, each
password entered will be kept (associated with the corresponding host
name) in memory during the current session, and optionally, in the
PASSFILE file for use in subsequent sessions.

WARNING! Use this feature with caution! It effectively makes the user's
mail no more secure than the physical security of the machine running
Pine. What's more, while the password is cloaked by a mild (some might
say, feeble) encryption scheme, it is nonetheless sitting in a file on the
disk and subject to cracking by anyone with access to it. BEWARE!

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Mon, 13 Dec 1999 [email protected] wrote:

>
> So where is my password stored? doesn't it have to be stored somewhere?
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 13:43:00 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA24547;
Mon, 13 Dec 1999 13:42:57 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA13088;
Mon, 13 Dec 1999 13:42:57 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA08146;
Mon, 13 Dec 1999 13:40:26 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA59742
for <[email protected]>; Mon, 13 Dec 1999 13:38:53 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA25513
for <[email protected]>; Mon, 13 Dec 1999 13:38:52 -0800
Received: from jason03.u.washington.edu ([email protected] [140.142.77.10])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA11191
for <[email protected]>; Mon, 13 Dec 1999 13:38:52 -0800
Received: from dante06.u.washington.edu ([email protected] [140.142.15.8])
by jason03.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA23004
for <[email protected]>; Mon, 13 Dec 1999 13:38:51 -0800
Received: from localhost (leibrand@localhost)
by dante06.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA18598
for <[email protected]>; Mon, 13 Dec 1999 13:38:50 -0800
Message-Id: <Pine.A41.4.21.9912131335060.99604-100000@dante06.u.washington.edu>
Date: Mon, 13 Dec 1999 13:38:50 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Quote Color
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Two questions:

Is it possible to change the indent string that Pine recognizes when it's
coloring quoted parts of a message? I'd like to make it recognize '.##.'
as well as '>'.

Can we make Pico use Pine's color scheme when we're composing a
message? That's when the quote coloring would be most useful, and it'd be
nice to be able to color specific headers, too, like we can do when
viewing a message.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 16:47:44 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA29669;
Mon, 13 Dec 1999 16:47:42 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA18929;
Mon, 13 Dec 1999 16:47:42 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA17393;
Mon, 13 Dec 1999 16:45:41 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA44548
for <[email protected]>; Mon, 13 Dec 1999 16:44:30 -0800
Received: from vax.area.com (vax58.area.com [165.90.20.58])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA05322
for <[email protected]>; Mon, 13 Dec 1999 16:44:20 -0800
Received: (qmail 15472 invoked by uid 1828); 14 Dec 1999 00:44:14 -0000
Message-Id: <Pine.GSO.4.20.9912131639120.2327-100000@vax>
Date: Mon, 13 Dec 1999 16:44:14 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: cosmetic bug regarding 'new message' display when deleting from
other IMAP client?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Ok, now I can't get this to reproduce at will..

But I use (at least) two mail clients on my work account, pine, plus often
a GUI client for the MIME-infected mail that is basically unreadable in pine.
(e.g. big tables, some necessary color viewing, etc..) The other client I use
is usually MailViewer, though I use Outlook Express on a MacOS (as opposed
to OSX) machine sometimes too..

Anyway, back to the topic.

I noticed that I saw "15 new messages! Most recent..."
at the bottom of the screen, but there really was only ONE new message, as
I had read and expunged others (presumably the rest of the 15) from another
client running simultaneously.

I can't get this to happen at will, because sending myself mail causes
the 'new mail to you' prompt to come up.. Though now I notice that I have
it saying _3_ new messages, but there are really 4 messages marked 'N', the
other one being the same "one new message" I mentioned above.

Is there a (minor, cosmetic) bug, or am I misinterpreting what it's trying
to tell me? The current "3 new messages" might be correct, if I had
actually done something else in pine (I don't think I did) and it's really
only saying new since I last interacted with it... but that certainly doesn't
fit with the Joe User expectation since I clearly see that 4 have N next to
them.

Uggh, a long rambling explanation for such a simple problem.

BTW, I'm using 4.20.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 13 Dec 1999 17:08:43 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA29519;
Mon, 13 Dec 1999 17:08:41 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA19453;
Mon, 13 Dec 1999 17:08:41 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA18203;
Mon, 13 Dec 1999 17:07:12 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA58578
for <[email protected]>; Mon, 13 Dec 1999 17:04:53 -0800
Received: from dante40.u.washington.edu ([email protected] [140.142.15.200])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA23428
for <[email protected]>; Mon, 13 Dec 1999 17:04:52 -0800
Received: from localhost (leibrand@localhost)
by dante40.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA36892
for <[email protected]>; Mon, 13 Dec 1999 17:04:52 -0800
Message-Id: <Pine.A41.4.21.9912131701090.109920-100000@dante40.u.washington.edu>
Date: Mon, 13 Dec 1999 17:04:52 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: cosmetic bug regarding 'new message' display when deleting from
other IMAP client?
In-Reply-To: <Pine.GSO.4.20.9912131639120.2327-100000@vax>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Not sure if this explains your problem, but...

Pine doesn't actually check for messages marked "new", but for "recent"
messages, which are ones that have shown up since the last time you opened
a folder. The new or recent status of a message becomes clear if you
change your inbox-format to contain the IMAPSTATUS item instead of the
regular STATUS one. (While you're at it, use SmartDate.) Here's what my
index-format looks like - try it out this way if you want:

index-format=ATT IMAPSTATUS MSGNO SMARTDATE(6) TIME12 FROMORTO(33%) SIZE SUBJECT(67%)

ATT is number of attachments.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Mon, 13 Dec 1999 [email protected] wrote:

>
> Ok, now I can't get this to reproduce at will..
>
> But I use (at least) two mail clients on my work account, pine, plus often
> a GUI client for the MIME-infected mail that is basically unreadable in pine.
> (e.g. big tables, some necessary color viewing, etc..) The other client I use
> is usually MailViewer, though I use Outlook Express on a MacOS (as opposed
> to OSX) machine sometimes too..
>
> Anyway, back to the topic.
>
> I noticed that I saw "15 new messages! Most recent..."
> at the bottom of the screen, but there really was only ONE new message, as
> I had read and expunged others (presumably the rest of the 15) from another
> client running simultaneously.
>
> I can't get this to happen at will, because sending myself mail causes
> the 'new mail to you' prompt to come up.. Though now I notice that I have
> it saying _3_ new messages, but there are really 4 messages marked 'N', the
> other one being the same "one new message" I mentioned above.
>
> Is there a (minor, cosmetic) bug, or am I misinterpreting what it's trying
> to tell me? The current "3 new messages" might be correct, if I had
> actually done something else in pine (I don't think I did) and it's really
> only saying new since I last interacted with it... but that certainly doesn't
> fit with the Joe User expectation since I clearly see that 4 have N next to
> them.
>
>
> Uggh, a long rambling explanation for such a simple problem.
>
> BTW, I'm using 4.20.
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Dec 1999 11:54:36 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA18234;
Tue, 14 Dec 1999 11:54:35 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA06521;
Tue, 14 Dec 1999 11:54:34 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA00319;
Tue, 14 Dec 1999 11:49:24 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA44188
for <[email protected]>; Tue, 14 Dec 1999 11:47:15 -0800
Received: from ursamajor.cisco.com (ursamajor.cisco.com [171.69.63.56])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA13925
for <[email protected]>; Tue, 14 Dec 1999 11:47:15 -0800
Received: from casner-pc.cisco.com (casner-pc.cisco.com [171.71.37.112]) by ursamajor.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id LAA27206; Tue, 14 Dec 1999 11:47:11 -0800 (PST)
Message-Id: <[email protected]>
Date: Tue, 14 Dec 1999 11:49:26 -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: Stephen Casner <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: URLs with tilde get mangled
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I've just upgraded from PC-Pine 4.10 to 4.21 and have noticed a couple
of things which I'll send in separate messages. First, a problem
which occurs on both '98 and an NT: When I try to view a URL in the
message which contains a tilde character, the URL that is given to
Netscape gets mangled:

The URL: http://www.math.washington.edu/~chappa/pine/
becomes: http://www.'http:.com//math.washington.edu/~chappa/pine/

This is with the following command line:

url-viewers = C:\Progra~1\Netscape\Communicator\Program\netscape.exe

I can avoid this problem if I follow a suggestion shown in an earlier
message on this list:

url-viewers = "C:\Progra~1\Netscape\Communicator\Program\netscape.exe -noraise -remote openURL\$_URL_,\\ new-window\$"

However, the "new window" part doesn't work -- the URL is viewed in an
existing Netscape window. The suggested syntax above was given for a
Solaris platform and I haven't been able to find a description of
command line options in Netscape's help, so I'm flying blind here.
Where does one find the syntax of "openURL"? I did try removing the
double backslash quoting, but it made no difference. I tried three
more possibilities:

"C:\Progra~1\Netscape\Communicator\Program\netscape.exe _URL_"
"C:\Progra~1\Netscape\Communicator\Program\netscape.exe"
C:\Progra~1\Netscape\Communicator\Program\netscape.exe "_URL_"

All of these still open the URL in an existing Netscape window. The
only one which doesn't is my original form above.

Any other suggestions? TIA,
-- Steve

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Dec 1999 12:06:43 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA18822;
Tue, 14 Dec 1999 12:06:42 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA06927;
Tue, 14 Dec 1999 12:06:41 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA27021;
Tue, 14 Dec 1999 12:03:05 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA77008
for <[email protected]>; Tue, 14 Dec 1999 12:01:53 -0800
Received: from ursamajor.cisco.com (ursamajor.cisco.com [171.69.63.56])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA12504
for <[email protected]>; Tue, 14 Dec 1999 12:01:53 -0800
Received: from casner-pc.cisco.com (casner-pc.cisco.com [171.71.37.112]) by ursamajor.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id MAA27515; Tue, 14 Dec 1999 12:01:50 -0800 (PST)
Message-Id: <[email protected]>
Date: Tue, 14 Dec 1999 12:04:04 -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: Stephen Casner <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Colors and "reverse"
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

The colors in 4.21 are a nice feature, but I have not been able to
figure out if it can do exactly what I want. In past versions, I have
used black text on white background for the normal text color and blue
text on white background for the "reverse" color because I prefer that
to actually reversing the video.

The same coloration carried over to 4.21 until I set some index-line
colors. I wanted selected messages to change to black text on yellow
background, as if highlighted with a marker. However, when the cursor
is on one of those messages, Pine ignores my "reverse" color setting
and inverts that line (yellow text on black background). What I
wanted was blue text on yellow background.

Is there a way to configure the behavior I want? Perhaps what's
needed is a way to specify "transparent" for the background on the
"reverse" color as an indication that just the foreground color should
be substituted.
-- Steve

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Dec 1999 12:25:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA26168;
Tue, 14 Dec 1999 12:25:22 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA09839;
Tue, 14 Dec 1999 12:25:22 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA28379;
Tue, 14 Dec 1999 12:22:22 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA57914
for <[email protected]>; Tue, 14 Dec 1999 12:21:40 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA20825
for <[email protected]>; Tue, 14 Dec 1999 12:21:39 -0800
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id MAA03944;
Tue, 14 Dec 1999 12:21:30 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912141218450.6516-100000@goedel3.math.washington.edu>
Date: Tue, 14 Dec 1999 12:21:30 -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 L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: URLs with tilde get mangled
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Stephen Casner <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Stephen Casner ([email protected]) wrote today:

:)
:) url-viewers =
:) "C:\Progra~1\Netscape\Communicator\Program\netscape.exe -noraise
:) -remote openURL\$_URL_,\\ new-window\$"
:)
:) However, the "new window" part doesn't work -- the URL is viewed in an
:) existing Netscape window. The suggested syntax above was given for a
:) Solaris platform and I haven't been able to find a description of
:) command line options in Netscape's help, so I'm flying blind here.
:) Where does one find the syntax of "openURL"? I did try removing the
:) double backslash quoting, but it made no difference. I tried three
:) more possibilities:

Dear Steve,

Take a look at the following address:

http://www.netscape.com/newsref/std/x-remote.html

There you will find the explanation of all the options of the -remote
switch.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 14 Dec 1999 15:46: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA23577;
Tue, 14 Dec 1999 15:46:18 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA12876;
Tue, 14 Dec 1999 15:46:18 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA25482;
Tue, 14 Dec 1999 15:44:04 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA14276
for <[email protected]>; Tue, 14 Dec 1999 15:42:40 -0800
Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA18368
for <[email protected]>; Tue, 14 Dec 1999 15:42:40 -0800
Received: from eis.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP;
Tue, 14 Dec 1999 23:42:31 +0000
Received: from mail.ilrt.bris.ac.uk (mail.ilrt.bris.ac.uk [137.222.34.22]) by eis.bris.ac.uk (8.9.3/8.9.3)
with ESMTP id XAA06754; Tue, 14 Dec 1999 23:41:28 GMT
Received: from localhost (cmjg@localhost) by mail.ilrt.bris.ac.uk (8.8.7/8.8.8)
with ESMTP id XAA16432; Tue, 14 Dec 1999 23:41:27 GMT
Message-Id: <[email protected]>
Date: Tue, 14 Dec 1999 23:41:27 +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: Jan Grant <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: BUGFIX: pine by-recipient fcc failing?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

If you remember I reported an issue with fcc by-recipient failing when
the destination folder existed; this problem could be replicated by
running pine 4.21 against the latest Cyrus imapd.

I _think_ this patch solves the problem, but I've not had a chance to
look deeply at Pine. Are there any problems that it might cause? Does it
do what I think it does?

6711c6711
< if(((flags & FI_DIR) && f->isdir) || ((flags & FI_FOLDER) && !f->isdir)){
---
> if(((flags & FI_DIR) && f->isdir) || ((flags & FI_FOLDER) && f->isfolder)){

Thanks in advance,

jan
--
Bolstered by my success with vi, I proceeded to learn C with 'learn c'
Jan Grant, ILRT. +44(0)117-9287163

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 02:20:53 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA32532;
Wed, 15 Dec 1999 02:20:51 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA23785;
Wed, 15 Dec 1999 02:20:51 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA14618;
Wed, 15 Dec 1999 02:19:14 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA76896
for <[email protected]>; Wed, 15 Dec 1999 02:17:55 -0800
Received: from mail.cs.tu-berlin.de ([email protected] [130.149.17.13])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA22452
for <[email protected]>; Wed, 15 Dec 1999 02:17:54 -0800
Received: from swamp.bayern.net (gator.isdn.cs.tu-berlin.de [130.149.148.15])
by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id LAA18367
for <[email protected]>; Wed, 15 Dec 1999 11:02:57 +0100 (MET)
Received: (from gator@localhost)
by swamp.bayern.net (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id KAA01520;
Wed, 15 Dec 1999 10:27:32 +0100
Message-Id: <[email protected]>
Date: Wed, 15 Dec 1999 10:27:31 +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: Peter Daum <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: PC-Pine 4.21 IMAP Authentification
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

I am currently employing PC-Pine 4.10 in an IMAP based
environment. When I tried version 4.21 with exactly the same
setup, I ran into a pretty annoying problem:

When I start the program, it presents the login prompt as
usually. As soon as I try to open an IMAP folder, it asks for the
password again. Switching to another folder, the procedure is
repeated - it looks, like Pine demands for the username/password
for every single IMAP transaction...

Is this a known problem? I couldn't find anything similar in this
mailing list. It obviously isn't a configuration problem, since
Pine 4.10 works.

regards,
Peter
--
__o
Peter Daum <gator at cs.tu-berlin.de> _'\<_
- pgp messages welcome - ____(_)/(_)

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 02:35:40 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA32146;
Wed, 15 Dec 1999 02:35:35 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA24064;
Wed, 15 Dec 1999 02:35:34 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA14814;
Wed, 15 Dec 1999 02:34:31 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA72818
for <[email protected]>; Wed, 15 Dec 1999 02:33:17 -0800
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA23163
for <[email protected]>; Wed, 15 Dec 1999 02:33:16 -0800
Received: from cerebus.fokus.gmd.de (cerebus [193.175.135.160])
by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA19761
for <[email protected]>; Wed, 15 Dec 1999 11:33:09 +0100 (MET)
Message-Id: <[email protected]>
Date: Wed, 15 Dec 1999 11:33:13 +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: Andreas Kraft <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <Pine.A41.4.21.9912131112340.52994-100000@dante07.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

On Mon, 13 Dec 1999, Scott Leibrand wrote:

> <http://ism.ucdavis.edu/info/pine/installation.html>:
> PASSFILE
> [...]
> The file is used to save passwords from one session to the next. Even if
> you define PASSFILE when you compile Pine, password saving will not be
> enabled by default, but requires the existence of the file (the name of
> which is the value of PASSFILE). Even with the existence of this file, the
> user must still acknowledge a prompt before the password is saved to the
> file. If Pine is configured to access several different IMAP servers, each
> password entered will be kept (associated with the corresponding host
> name) in memory during the current session, and optionally, in the
> PASSFILE file for use in subsequent sessions.
> [...]

I am using PC-Pine (4.21) to access my regular emails on an IMAP server.
Here, everything works fine. But I am also have another INBOX on
a POP3 account. Here, PC-Pine asks me for the password for this account
and also aks me whether I want to store it in the PASSFILE. The
problem is that it is either not stored or not correctly retrieved
because PC-Pine is asking me for the password every time I am
accessing this INBOX. Is this a known problem?

Best regards,

Andreas

--
o _ Andreas Kraft
(\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
T> ] [ The sky is the limit

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 03:40:10 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA03408;
Wed, 15 Dec 1999 03:40:08 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA27869;
Wed, 15 Dec 1999 03:40:08 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id DAA15288;
Wed, 15 Dec 1999 03:38:49 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id DAA13822
for <[email protected]>; Wed, 15 Dec 1999 03:37:17 -0800
Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA22950
for <[email protected]>; Wed, 15 Dec 1999 03:37:16 -0800
Received: from eis.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP;
Wed, 15 Dec 1999 11:37:02 +0000
Received: from bristol.ac.uk (tribble.ilrt.bris.ac.uk [137.222.34.34]) by eis.bris.ac.uk (8.9.3/8.9.3)
with ESMTP id LAA13506; Wed, 15 Dec 1999 11:34:51 GMT
Message-Id: <[email protected]>
Date: Wed, 15 Dec 1999 11:34:11 +0000
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: jan grant <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Doh: BUGFIX: pine by-recipient fcc failing?
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Sender: [email protected]
X-Cc: [email protected]
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

PS. This should be applied to pine/folder.c

6711c6711
< if(((flags & FI_DIR) && f->isdir) || ((flags & FI_FOLDER) &&
!f->isdir)){
---
> if(((flags & FI_DIR) && f->isdir) || ((flags & FI_FOLDER) && f->isfolder)){

--
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 [email protected]
Unfortunately, I have a very good idea of how fast my keys are moving.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 05:12:42 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA06812;
Wed, 15 Dec 1999 05:12:40 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA29519;
Wed, 15 Dec 1999 05:12:40 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA24660;
Wed, 15 Dec 1999 05:11:23 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA86410
for <[email protected]>; Wed, 15 Dec 1999 05:10:35 -0800
Received: from tunku.uady.mx (tunku.uady.mx [148.209.1.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA27641
for <[email protected]>; Wed, 15 Dec 1999 05:10:34 -0800
Received: from localhost (angel@localhost)
by tunku.uady.mx (8.9.1/8.9.1) with SMTP id HAA01998;
Wed, 15 Dec 1999 07:12:26 -0600 (CST)
Message-Id: <[email protected]>
Date: Wed, 15 Dec 1999 07:12:26 -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: =?ISO-8859-1?Q?Polanco_Rodr=EDguez_=C1ngel?= <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: URLs with tilde get mangled
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Stephen Casner <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello to all,

Sorry, some know a option of pine to implement quotes?. This is to the
administration of space on disk of the users.

Alguien sabe de alguna opcion de pine para implementar quotas?. Esto es
para la administracion del espacio en disco de los usuarios.

Some body have experience in scripts?
Alguien ha manejado scripts?

Thanks a lot from Mexico.

************************************
| Q.B.B.ANGEL G. POLANCO RODRIGUEZ |
| UNIVERSIDAD AUTONOMA DE YUCATAN |
| DIRECCION GENERAL DE |
| DESARROLLO ACADEMICO |
| DEPARTAMENTO DE TELEINFORMATICA|
| CALLE 59 POR AV. ITZAEZ # 490 |
| MERIDA, YUCATAN, MEXICO |
| CODIGO POSTAL : 97 000 |
| TELEFONO:52 (99) 23 74 28 |
| E-mail: [email protected] |
************************************

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 11:56:05 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA13688;
Wed, 15 Dec 1999 11:56:04 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA03921;
Wed, 15 Dec 1999 11:56:03 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA22798;
Wed, 15 Dec 1999 11:53:43 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA72674
for <[email protected]>; Wed, 15 Dec 1999 11:51:56 -0800
Received: from betelgeuse.concentric.net (betelgeuse.concentric.net [207.155.183.76])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA21422
for <[email protected]>; Wed, 15 Dec 1999 11:51:55 -0800
Received: from TATUM.WORKGROUP (ts005d07.nyh-ny.concentric.net [216.112.236.211])
by betelgeuse.concentric.net (8.8.5/)
id OAA26048; Wed, 15 Dec 1999 14:51:53 -0500 (EST)
[ConcentricHost MX Server]
Message-Id: <003c01bf4735$dc2ae260$d3ec70d8@WORKGROUP>
Date: Wed, 15 Dec 1999 14:52:01 -0500
Reply-To: "LINEart" <[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: "LINEart" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
References: <[email protected]>
X-To: "Pine Discussion Forum" <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I wonder if this has anything to do with POP3 not being supported for "new"
messages while in-session.

as you know, you cannot view "new" messages that arrive in a POP3 box
without exiting PINE and re-entering. I wonder if it's asking you for a
password because when you leave the POP Inbox you're in effect "closing" the
PINE session and upon re-entry, you're "starting" the PINE application
again. . .

----- Original Message -----
From: Andreas Kraft <[email protected]>
To: Pine Discussion Forum <[email protected]>
Sent: Wednesday, December 15, 1999 5:33 AM
Subject: Re: Pine config of news server/login/groups

> Hi,
>
> On Mon, 13 Dec 1999, Scott Leibrand wrote:
>
> > <http://ism.ucdavis.edu/info/pine/installation.html>:
> > PASSFILE
> > [...]
> > The file is used to save passwords from one session to the next. Even if
> > you define PASSFILE when you compile Pine, password saving will not be
> > enabled by default, but requires the existence of the file (the name of
> > which is the value of PASSFILE). Even with the existence of this file,
the
> > user must still acknowledge a prompt before the password is saved to the
> > file. If Pine is configured to access several different IMAP servers,
each
> > password entered will be kept (associated with the corresponding host
> > name) in memory during the current session, and optionally, in the
> > PASSFILE file for use in subsequent sessions.
> > [...]
>
> I am using PC-Pine (4.21) to access my regular emails on an IMAP server.
> Here, everything works fine. But I am also have another INBOX on
> a POP3 account. Here, PC-Pine asks me for the password for this account
> and also aks me whether I want to store it in the PASSFILE. The
> problem is that it is either not stored or not correctly retrieved
> because PC-Pine is asking me for the password every time I am
> accessing this INBOX. Is this a known problem?
>
> Best regards,
>
> Andreas
>
> --
> o _ Andreas Kraft
> (\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
> T> ] [ The sky is the limit
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 15:04:29 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA15944;
Wed, 15 Dec 1999 15:04:28 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA12450;
Wed, 15 Dec 1999 15:04:28 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA08105;
Wed, 15 Dec 1999 15:02:41 -0800
Received: from jason02.u.washington.edu ([email protected] [140.142.76.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA80558
for <[email protected]>; Wed, 15 Dec 1999 15:01:23 -0800
Received: from dante31.u.washington.edu ([email protected] [140.142.15.213])
by jason02.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA15102
for <[email protected]>; Wed, 15 Dec 1999 15:01:22 -0800
Received: from localhost (leibrand@localhost)
by dante31.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA34530
for <[email protected]>; Wed, 15 Dec 1999 15:01:21 -0800
Message-Id: <Pine.A41.4.21.9912151458560.72022-100000@dante31.u.washington.edu>
Date: Wed, 15 Dec 1999 15:01: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I don't know if it's a "known" problem, but I'm certainly seeing a lot of
posts about it. The general trend seems to be that if you're accessing a
mailbox with a different uid than you're running Pine under, Pine no
longer remembers that you've already logged in.

I'm going to do some comprehensive testing soon to see if I can get a more
precise description of the conditions under which the problem occurs.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Wed, 15 Dec 1999, Andreas Kraft wrote:

> Hi,
>
> On Mon, 13 Dec 1999, Scott Leibrand wrote:
>
> > <http://ism.ucdavis.edu/info/pine/installation.html>:
> > PASSFILE
> > [...]
> > The file is used to save passwords from one session to the next. Even if
> > you define PASSFILE when you compile Pine, password saving will not be
> > enabled by default, but requires the existence of the file (the name of
> > which is the value of PASSFILE). Even with the existence of this file, the
> > user must still acknowledge a prompt before the password is saved to the
> > file. If Pine is configured to access several different IMAP servers, each
> > password entered will be kept (associated with the corresponding host
> > name) in memory during the current session, and optionally, in the
> > PASSFILE file for use in subsequent sessions.
> > [...]
>
> I am using PC-Pine (4.21) to access my regular emails on an IMAP server.
> Here, everything works fine. But I am also have another INBOX on
> a POP3 account. Here, PC-Pine asks me for the password for this account
> and also aks me whether I want to store it in the PASSFILE. The
> problem is that it is either not stored or not correctly retrieved
> because PC-Pine is asking me for the password every time I am
> accessing this INBOX. Is this a known problem?
>
> Best regards,
>
> Andreas
>
> --
> o _ Andreas Kraft
> (\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
> T> ] [ The sky is the limit
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 15:09:04 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA18464;
Wed, 15 Dec 1999 15:09:02 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA12619;
Wed, 15 Dec 1999 15:09:02 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA08369;
Wed, 15 Dec 1999 15:07:23 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA85000
for <[email protected]>; Wed, 15 Dec 1999 15:06:33 -0800
Received: from dante31.u.washington.edu ([email protected] [140.142.15.213])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA41864;
Wed, 15 Dec 1999 15:06:32 -0800
Received: from localhost (leibrand@localhost)
by dante31.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA22768;
Wed, 15 Dec 1999 15:06:31 -0800
Message-Id: <Pine.A41.4.21.9912151502160.72022-100000@dante31.u.washington.edu>
Date: Wed, 15 Dec 1999 15:06: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: URLs with tilde get mangled
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-To: =?ISO-8859-1?Q?Polanco_Rodr=EDguez_=C1ngel?= <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I think you meant quotas, not quotes.
Creo que debe decir quotas en vez de quotes.

In English, these "" are quotes.
En ingles, estos "" son quotes.

But your English is way better than my Spanish. :)
Pero su Ingles es mucho mas mejor que mi espanol. :)

--=20
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Wed, 15 Dec 1999, [ISO-8859-1] Polanco Rodr=EDguez =C1ngel wrote:

>=20
> Hello to all,
>=20
> Sorry, some know a option of pine to implement quotes?. This is to the
> administration of space on disk of the users.
>=20
> Alguien sabe de alguna opcion de pine para implementar quotas?. Esto es
> para la administracion del espacio en disco de los usuarios.
>=20
> Some body have experience in scripts?
> Alguien ha manejado scripts?
>=20
> Thanks a lot from Mexico.
> =20
> ************************************
> | Q.B.B.ANGEL G. POLANCO RODRIGUEZ | =20
> | UNIVERSIDAD AUTONOMA DE YUCATAN |
> | DIRECCION GENERAL DE | =20
> | DESARROLLO ACADEMICO | =20
> | DEPARTAMENTO DE TELEINFORMATICA|
> | CALLE 59 POR AV. ITZAEZ # 490 |
> | MERIDA, YUCATAN, MEXICO | =20
> | CODIGO POSTAL : 97 000 | =20
> | TELEFONO:52 (99) 23 74 28 |
> | E-mail: [email protected] |
> ************************************
>=20
> =20
>=20
> =20
>=20
>=20
>=20

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 18:15:48 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA09047;
Wed, 15 Dec 1999 18:15:47 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA17547;
Wed, 15 Dec 1999 18:15:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA07364;
Wed, 15 Dec 1999 18:14:00 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA28302
for <[email protected]>; Wed, 15 Dec 1999 18:12:05 -0800
Received: from cc0190.pc.nus.edu.sg (IDENT:root@[137.132.6.190])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA23976
for <[email protected]>; Wed, 15 Dec 1999 18:12:03 -0800
Received: from localhost (cceyeoeh@localhost)
by cc0190.pc.nus.edu.sg (8.9.3/8.9.3) with ESMTP id KAA01492
for <[email protected]>; Thu, 16 Dec 1999 10:09:37 +0800
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 10:09:37 +0800 (SGT)
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: Yeo Eng Hee <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Displaying 'raw' mail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: cc0190.pc.nus.edu.sg: cceyeoeh owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have often received mails from certain sites that contains several
attachments, which turn out to be just header information. Can I tell
Pine not to pre-format these mails and just display them as raw?

Anyone using Pine to read emails sent from the Hewlett-Packard email
system will normally encounter such problems.

Yeo Eng Hee

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 18:54:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA23891;
Wed, 15 Dec 1999 18:54:22 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA18180;
Wed, 15 Dec 1999 18:54:22 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA19789;
Wed, 15 Dec 1999 18:52:42 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA70090
for <[email protected]>; Wed, 15 Dec 1999 18:51:38 -0800
Received: from cc0190.pc.nus.edu.sg (IDENT:[email protected] [137.132.6.190])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA29072
for <[email protected]>; Wed, 15 Dec 1999 18:51:37 -0800
Received: from localhost (cceyeoeh@localhost)
by cc0190.pc.nus.edu.sg (8.9.3/8.9.3) with ESMTP id KAA01523;
Thu, 16 Dec 1999 10:49:08 +0800
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 10:49:08 +0800 (SGT)
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: Yeo Eng Hee <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Displaying 'raw' mail
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Ed Arnold <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: cc0190.pc.nus.edu.sg: cceyeoeh owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is what's troublesome. If I can see everything in raw, without
having to keep saving the attachments and finding out that they are
not useful, it would be save me lots of time, especially if I have
lots of mail to clear.

Regards,

Yeo Eng Hee

On Wed, 15 Dec 1999, Ed Arnold wrote:

> Date: Wed, 15 Dec 1999 19:31:28 -0700 (MST)
> From: Ed Arnold <[email protected]>
> To: Yeo Eng Hee <[email protected]>
> Subject: Re: Displaying 'raw' mail
>
> When I get mail like this, I just use the 'S' command to save it
> to a file, then read it with a text editor or whatever.
>
>
> > I have often received mails from certain sites that contains several
> > attachments, which turn out to be just header information. Can I tell
> > Pine not to pre-format these mails and just display them as raw?
> >
> > Anyone using Pine to read emails sent from the Hewlett-Packard email
> > system will normally encounter such problems.
> >
> > Yeo Eng Hee
> >
> > --
> > -----------------------------------------------------------------
> > For information about this mailing list, and its archives, see:
> > http://www.washington.edu/pine/pine-info/
> > -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 20:28: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA24895;
Wed, 15 Dec 1999 20:28:53 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA16270;
Wed, 15 Dec 1999 20:28:52 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA24524;
Wed, 15 Dec 1999 20:27:07 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA79454
for <[email protected]>; Wed, 15 Dec 1999 20:25:24 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id UAA32238
for <[email protected]>; Wed, 15 Dec 1999 20:25:23 -0800
Received: (qmail 1050 invoked from network); 16 Dec 1999 04:25:23 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 16 Dec 1999 04:25:23 -0000
Message-Id: <[email protected]>
Date: Wed, 15 Dec 1999 21:25:58 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Copy and Paste in Xwindows
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello all,

I'm using Pine (version 4.10) under Linux and under Solaris. I'm using
Pine in an xterm or a CDE terminal. When I highlight text with the mouse,
I am able to paste that text to another xterm. However, if I try to paste
it to Pine, the buffer is empty. In order to copy and paste in Pine, I
have to copy, paste to another program (or just onto a xterm command
line), and then copy from the xterm and paste into Pine.

For example, I want to copy an address from an email, start a new message,
and paste that address onto the "To" line. I copy the address, and then
type C for compose. However, there is nothing to paste to the "To" line.
I can copy the address, paste it to another xterm, start the compose, copy
from the other xterm, and paste to Pine.

So, clearly, the copy buffer is purged when I go from reading a mail
message to composing. Is there a way to modify this behavior? The
behavior is the same regardless of whether enable-mouse-in-xterm is
enabled. In Pine 4.04, turning enable-mouse-in-xterm **off** (!?!) made
this behavior go away and copy and paste worked.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 15 Dec 1999 22:16:47 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA18966;
Wed, 15 Dec 1999 22:16:46 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA21519;
Wed, 15 Dec 1999 22:16:45 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA23890;
Wed, 15 Dec 1999 22:14:59 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA91958
for <[email protected]>; Wed, 15 Dec 1999 22:14:05 -0800
Received: from n2.net-uno.net ([206.49.154.35])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA09824
for <[email protected]>; Wed, 15 Dec 1999 22:14:04 -0800
Received: from eth0 ([172.16.13.204]) by n2.net-uno.net
(Post.Office MTA v3.5.2 release 221 ID# 0-60710U4100L500S0V35)
with ESMTP id net for <[email protected]>;
Thu, 16 Dec 1999 02:14:04 -0400
Message-Id: <Pine.LNX.4.20.9912152139070.897-100000@bjork>
Date: Wed, 15 Dec 1999 21:41:19 -0400 (VET)
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: "Diego A. Puertas F." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Multiple mail account (INBOXes)
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Lista: pine-info" <[email protected]>
X-Sender: dapf@bjork
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I have 4 mail accounts so, how can I read from multiple INBOXes in pine?

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 02:53: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA28654;
Thu, 16 Dec 1999 02:53:25 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA22354;
Thu, 16 Dec 1999 02:53:24 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA16680;
Thu, 16 Dec 1999 02:51:45 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA59378
for <[email protected]>; Thu, 16 Dec 1999 02:48:57 -0800
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA32198
for <[email protected]>; Thu, 16 Dec 1999 02:48:55 -0800
Received: from cerebus.fokus.gmd.de (cerebus [193.175.135.160])
by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA27177
for <[email protected]>; Thu, 16 Dec 1999 11:48:46 +0100 (MET)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 11:48:49 +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: Andreas Kraft <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <Pine.A41.4.21.9912151458560.72022-100000@dante31.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Scott,

thank you for your answer.

On Wed, 15 Dec 1999, Scott Leibrand wrote:
> I don't know if it's a "known" problem, but I'm certainly seeing a lot of
> posts about it. The general trend seems to be that if you're accessing a
> mailbox with a different uid than you're running Pine under, Pine no
> longer remembers that you've already logged in.

Maybe I should describe my scenario:
Normally I am "logged" on to the IMAP server of my company with my uid.
I have also another account at another ISP which I want to check
regulary. This ISP offers only POP3 mail access. The username there is the
same. I therefore added another incoming-folder:

user-id=myuid
incoming-folders="other inbox" {otherisp.de/user=myuid/pop3}INBOX

So, I am using the same uids for both accounts.

I hope that helps,

Andreas

--
o _ Andreas Kraft
(\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
T> ] [ The sky is the limit

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 02:56: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA26272;
Thu, 16 Dec 1999 02:56:06 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA22403;
Thu, 16 Dec 1999 02:56:06 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA28210;
Thu, 16 Dec 1999 02:54:26 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA12412
for <[email protected]>; Thu, 16 Dec 1999 02:52:55 -0800
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA32388
for <[email protected]>; Thu, 16 Dec 1999 02:52:54 -0800
Received: from cerebus.fokus.gmd.de (cerebus [193.175.135.160])
by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA27568
for <[email protected]>; Thu, 16 Dec 1999 11:52:46 +0100 (MET)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 11:52:50 +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: Andreas Kraft <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <003c01bf4735$dc2ae260$d3ec70d8@WORKGROUP>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

On Wed, 15 Dec 1999, LINEart wrote:
> as you know, you cannot view "new" messages that arrive in a POP3 box
> without exiting PINE and re-entering. I wonder if it's asking you for a
> password because when you leave the POP Inbox you're in effect "closing" the
> PINE session and upon re-entry, you're "starting" the PINE application
> again. . .

Is it really necessary to leave Pine or is it OK to just close the
incoming folder (eg. open the inbox of another email account) and open
it again?
I don't think that Pine "forgets" my uid because I can still access
my email on the IMAP server I am usually connected to.

Best regards,

Andreas

--
o _ Andreas Kraft
(\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
T> ] [ The sky is the limit

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 07:20:40 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA32692;
Thu, 16 Dec 1999 07:20:39 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA26796;
Thu, 16 Dec 1999 07:20:38 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA05489;
Thu, 16 Dec 1999 07:19:20 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA30956
for <[email protected]>; Thu, 16 Dec 1999 07:18:13 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA19614
for <[email protected]>; Thu, 16 Dec 1999 07:18:12 -0800
Received: from alephminus2.ii.com ([email protected] [216.44.169.227])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id KAA04813;
Thu, 16 Dec 1999 10:18:07 -0500 (EST)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 10:17:32 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: URLs with tilde get mangled
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Stephen Casner <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-14 Stephen Casner <[email protected]> wrote:
> url-viewers = C:\Progra~1\Netscape\Communicator\Program\netscape.exe

In PC-Pine you should not need to set the Pine url-viewers
variable at all; leaving it blank, which shows up as

url-viewers = <No Value Set>

in the Pine Config screen, will make PC-Pine use your
default web browser, which is set in the Windows registry. What
happens when you have the following in your pinerc:

url-viewers=

Good luck,
Nancy

--
Pine info & links @ http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
-----== Sent via Pine 4.21 running on Debian GNU/Linux ==-----

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 07:26:26 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA03619;
Thu, 16 Dec 1999 07:26:25 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA30318;
Thu, 16 Dec 1999 07:26:25 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA03089;
Thu, 16 Dec 1999 07:25:11 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA12518
for <[email protected]>; Thu, 16 Dec 1999 07:24:29 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA21429
for <[email protected]>; Thu, 16 Dec 1999 07:24:28 -0800
Received: from alephminus2.ii.com ([email protected] [216.44.169.227])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id KAA04870;
Thu, 16 Dec 1999 10:24:25 -0500 (EST)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 10:23:50 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Andreas Kraft <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-15 Andreas Kraft <[email protected]> wrote:
> I am using PC-Pine (4.21) to access my regular emails on an
> IMAP server. Here, everything works fine. But I am also have
> another INBOX on a POP3 account. Here, PC-Pine asks me for the
> password for this account and also aks me whether I want to
> store it in the PASSFILE. The problem is that it is either not
> stored or not correctly retrieved because PC-Pine is asking me
> for the password every time I am accessing this INBOX. Is this
> a known problem?

Make sure you put "/user=userid" in *all* your server
specifications in your pinerc, e.g.:

your.pop.server/user=userid
your.imap.server/user=userid2

This includes specifications of remote folder collections and
IMAP-accessible address book. I have examples of this in my
PC-Pine page, which is a link in the URL in my sig below.

Good luck,
Nancy

--
Pine info & links @ http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
-----== Sent via Pine 4.21 running on Debian GNU/Linux ==-----

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 07:39:30 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA04925;
Thu, 16 Dec 1999 07:39:28 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA27136;
Thu, 16 Dec 1999 07:39:28 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA03478;
Thu, 16 Dec 1999 07:37:47 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA44156
for <[email protected]>; Thu, 16 Dec 1999 07:36:56 -0800
Received: from mail3.new-york.net ([email protected] [165.254.2.58])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA14590
for <[email protected]>; Thu, 16 Dec 1999 07:36:55 -0800
Received: from alephminus2.ii.com ([email protected] [216.44.169.227])
by mail3.new-york.net (8.8.8/8.8.8/NYNET-2.2-NORELAY) with ESMTP id KAA04991;
Thu, 16 Dec 1999 10:36:52 -0500 (EST)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 10:36:17 -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: Nancy this-address-is-valid McGough <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: how do i access comp.mail.pine?
In-Reply-To: <003001bf4526$14a821a0$d5ec70d8@WORKGROUP>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-To: LINEart <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 99-12-12 LINEart <[email protected]> wrote:
> not sure i understand. i, not an automatic wizard, had to
> configure all of my mailsoftware to access any mail and/or news
> accounts i've ever had. (the only time this was not true was
> within a network at school). i'm using pop3 for
> news.u.washington.edu, for example (and i'm not a univ. of
> washington employee/student) i can gain access, at least to the
> level of contacting the server so it gives me back a listing of
> available groups. the server that i'm contacting is
> news.u.washington.edu, not my ISP.

I think the confusion here is that news.u.washington.edu is not a
public news server but both Microsoft and AOL/Netscape do have
public news servers, namely:

msnews.microsoft.com
news.mozilla.org

or at least this is what they used to be because I have these
in my pinerc news-collections lists and they worked at one time.
Anyway, these two news servers have newsgroups where people
discuss MS and Mozilla stuff, respectively. If you want to
participate in comp.mail.pine, you need to access a news server
that gets a regular Usenet news feed. Most, but not all, ISPs do
provide Usenet news so you need to ask your ISP:

1) Do you provide access to Usenet news?
2) If yes, what is your news server name?

And then put that info in your pinerc as your nntp-server and add
it to your list of news-collections.

Hope this helps,
Nancy

--
Pine info & links @ http://www.ii.com/internet/messaging/pine/

�Nancy McGough http://www.ii.com/ Infinite Ink
-----== Sent via Pine 4.21 running on Debian GNU/Linux ==-----

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 08:52:50 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA06359;
Thu, 16 Dec 1999 08:52:48 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA28921;
Thu, 16 Dec 1999 08:52:48 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA24092;
Thu, 16 Dec 1999 08:51:08 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA55910
for <[email protected]>; Thu, 16 Dec 1999 08:49:44 -0800
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA32001
for <[email protected]>; Thu, 16 Dec 1999 08:49:43 -0800
Received: from cerebus.fokus.gmd.de (cerebus [193.175.135.160])
by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id RAA12969
for <[email protected]>; Thu, 16 Dec 1999 17:49:36 +0100 (MET)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 17:49:41 +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: Andreas Kraft <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
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-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Nancy,

thank you for your answer. However, what you recommend doesn't work.

On Thu, 16 Dec 1999, Nancy this-address-is-valid McGough wrote:
> Make sure you put "/user=userid" in *all* your server
> specifications in your pinerc, e.g.:
>
> your.pop.server/user=userid
> your.imap.server/user=userid2

I changed the inbox-path to the following:

inbox-path = {mymailhost/user=uid}INBOX

and did the same for my address books on the IMAP server. Pine still
asks me for a password every time I try to access my POP3 mailbox.

> This includes specifications of remote folder collections and
> IMAP-accessible address book. I have examples of this in my
> PC-Pine page, which is a link in the URL in my sig below.

I actually got the ideas for the POP3 configuration from your
excellent descriptions (btw: thanks for all the efforts you put into these
pages!).

> Good luck,

Thanks. I keep trying :-)

Andreas

--
o _ Andreas Kraft
(\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
T> ] [ The sky is the limit

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 09:38:39 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA06984;
Thu, 16 Dec 1999 09:38:37 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00902;
Thu, 16 Dec 1999 09:38:37 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA07604;
Thu, 16 Dec 1999 09:36:22 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA72346
for <[email protected]>; Thu, 16 Dec 1999 09:35:12 -0800
Received: from dante24.u.washington.edu ([email protected] [140.142.15.74])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA18792
for <[email protected]>; Thu, 16 Dec 1999 09:35:11 -0800
Received: from localhost (leibrand@localhost)
by dante24.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA20650
for <[email protected]>; Thu, 16 Dec 1999 09:35:09 -0800
Message-Id: <Pine.A41.4.21.9912160933200.17070-100000@dante24.u.washington.edu>
Date: Thu, 16 Dec 1999 09:35:09 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Pine config of news server/login/groups
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

In your case, where the POP3 inbox is not your primary inbox, it should be
ok just to close the folder and reopen it. The real annoyance is for
people whose main inbox is their POP3 inbox, because you can't close that.

If you can, try Pine 4.10 and see if you have the same problem. It seems
that all the new problems with multiple uid/passwd prompts have come up
using 4.2x, but I'd like to confirm that.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Thu, 16 Dec 1999, Andreas Kraft wrote:

> Hi,
>
> On Wed, 15 Dec 1999, LINEart wrote:
> > as you know, you cannot view "new" messages that arrive in a POP3 box
> > without exiting PINE and re-entering. I wonder if it's asking you for a
> > password because when you leave the POP Inbox you're in effect "closing" the
> > PINE session and upon re-entry, you're "starting" the PINE application
> > again. . .
>
> Is it really necessary to leave Pine or is it OK to just close the
> incoming folder (eg. open the inbox of another email account) and open
> it again?
> I don't think that Pine "forgets" my uid because I can still access
> my email on the IMAP server I am usually connected to.
>
> Best regards,
>
> Andreas
>
> --
> o _ Andreas Kraft
> (\_|_) GMD FOKUS, [email protected], +49 30 3463-7232
> T> ] [ The sky is the limit
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 09:38:56 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA02975;
Thu, 16 Dec 1999 09:38:52 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00919;
Thu, 16 Dec 1999 09:38:52 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA07640;
Thu, 16 Dec 1999 09:37:17 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA16790
for <[email protected]>; Thu, 16 Dec 1999 09:36:43 -0800
Received: from dante24.u.washington.edu ([email protected] [140.142.15.74])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA16892
for <[email protected]>; Thu, 16 Dec 1999 09:36:42 -0800
Received: from localhost (leibrand@localhost)
by dante24.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA27610
for <[email protected]>; Thu, 16 Dec 1999 09:36:41 -0800
Message-Id: <Pine.A41.4.21.9912160936110.17070-100000@dante24.u.washington.edu>
Date: Thu, 16 Dec 1999 09:36:41 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Multiple mail account (INBOXes)
In-Reply-To: <Pine.LNX.4.20.9912152139070.897-100000@bjork>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

You'll want to enable-incoming-folders in Setup, Config, and then add an
incoming folder for each inbox.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Wed, 15 Dec 1999, Diego A. Puertas F. wrote:

> I have 4 mail accounts so, how can I read from multiple INBOXes in pine?
>
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 11:15:29 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA09676;
Thu, 16 Dec 1999 11:15:28 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA03926;
Thu, 16 Dec 1999 11:15:17 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA29841;
Thu, 16 Dec 1999 11:12:23 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA64414
for <[email protected]>; Thu, 16 Dec 1999 11:11:00 -0800
Received: from vax.area.com (vax109.area.com [165.90.20.109])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id LAA24820
for <[email protected]>; Thu, 16 Dec 1999 11:10:22 -0800
Received: (qmail 568 invoked by uid 1828); 16 Dec 1999 19:09:38 -0000
Message-Id: <Pine.GSO.4.20.9912161107350.26453-100000@vax>
Date: Thu, 16 Dec 1999 11:09:38 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: keep "attachments" in message when replying
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: mattack@vax
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I put 'attachments' in quotes because from a user point of view they're
not attachments, they're just the text of the message.

I may have asked this before, but maybe Alzheimers is kicking in early.. heh.

Anyway, one thing about pine that bugs the heck out of me is that it will
show me text and html attachments when VIEWING the message, but when
I _reply_ I get a blank message, with attached files..

I don't want that! (In this specific case, I'm complaining about spam, and
want the main text to be shown there..)

Now, maybe the recipient will see the attachments as the 'regular message'
just like I did.. but I don't know... So is there any way I can have them
just part of the guts of the message??

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 16 Dec 1999 14:17:57 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA13917;
Thu, 16 Dec 1999 14:17:56 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA02458;
Thu, 16 Dec 1999 14:17:55 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA19013;
Thu, 16 Dec 1999 14:15:43 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA56012
for <[email protected]>; Thu, 16 Dec 1999 14:14:14 -0800
Received: from ursamajor.cisco.com (ursamajor.cisco.com [171.69.63.56])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27849
for <[email protected]>; Thu, 16 Dec 1999 14:14:14 -0800
Received: from casner-pc.cisco.com (casner-pc.cisco.com [171.71.37.112]) by ursamajor.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id OAA03162; Thu, 16 Dec 1999 14:14:08 -0800 (PST)
Message-Id: <[email protected]>
Date: Thu, 16 Dec 1999 14:16:23 -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: Stephen Casner <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: URLs with tilde get mangled
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Nancy this-address-is-valid McGough <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 16 Dec 1999, Nancy this-address-is-valid McGough wrote:

> In PC-Pine you should not need to set the Pine url-viewers
> variable at all; leaving it blank, which shows up as
>
> url-viewers = <No Value Set>
>
> in the Pine Config screen, will make PC-Pine use your
> default web browser, which is set in the Windows registry.

Thanks for the suggestion, but that also results in an existing
Netscape window being re-used. I vaguely recall discovering back in
the 3.96 or 4.05 timeframe that I could get a new window by putting in
the full C:\Progra~1\Netscape\Communicator\Program\netscape.exe
pathname (without quotes). I don't recall whether I tested at that
time with and without quotes or with and without "_URL".

So, I still have not figured out a way to avoid having a URL get
mangled if it contains a tilde and at the same time have the URL be
opened in a new Netscape window. Some processing of the URL must have
been "improved" in 4.2x because the unadorned full pathname used to
work for this in 4.10.
-- Steve

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 17 Dec 1999 02:15:32 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA24347;
Fri, 17 Dec 1999 02:15:30 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA15915;
Fri, 17 Dec 1999 02:15:30 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA04745;
Fri, 17 Dec 1999 02:13:01 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA27154
for <[email protected]>; Fri, 17 Dec 1999 02:11:32 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA24711
for <[email protected]>; Fri, 17 Dec 1999 02:11:32 -0800
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id CAA19347;
Fri, 17 Dec 1999 02:11:32 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912170148180.25818-100000@goedel3.math.washington.edu>
Date: Fri, 17 Dec 1999 02:11: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: announcing a new patch!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine developers team <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello,

I am sending this e-mail to announce a new patch for pine4.21. This
patch is intended to server better to advanced users of pine, rather than
to newbies. The idea of the patch is to optimize pine to make it more
flexible in certain rules. For example, sometimes you may want to save
e-mail from Fred Flinstones in folder Fred, but messages from this list in
Unix/pine. There is no rule to make pine to uniformily offer "Fred" as the
folder to save messages from "Fred Flinstones" and at the same time to
save messages of this list in say "Unix/pine". This is where this patch
comes into play, you can make saving rules very flexible. The rule after
this is that there are no rules!, you make the rules!.

Among other features you can obtain are the following:

* automatic sort order when opening a folder (different from your default)

* You can make the reply-leadin-string personalised or folder dependent
(you can do the personalised reply-leadin-string with roles, but it's not
the same, after you see how this works, you'll see this is the right way
to do it)

* You can make a different index-format for each folder.

* You can "trim" a subject and a from, by removing unwanted strings in
them when displayed in the index. For example in the mailing list of lynx
developers, almost every e-mail has the string "lynx-dev". You can use
this patch to remove that string and make the subject longer, and the same
can be said about the "From" field.

If you want to try/test the patch pick it up from the address below and
look for under: "Define your own rules and make pine flexible!". Please
notify me of any problem you have with the patch.

Thanks,

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 17 Dec 1999 08:04:12 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA19972;
Fri, 17 Dec 1999 08:04:10 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA21767;
Fri, 17 Dec 1999 08:04:10 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA27034;
Fri, 17 Dec 1999 08:02:24 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA38070
for <[email protected]>; Fri, 17 Dec 1999 08:01:07 -0800
Received: from smtp1.libero.it (smtp1.libero.it [193.70.192.51])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA15921
for <[email protected]>; Fri, 17 Dec 1999 08:00:58 -0800
Received: from localhost.localhost (151.15.9.157) by smtp1.libero.it; 17 Dec 1999 17:00:44 +0100
Received: from kiwi (IDENT:root@kiwi [127.0.0.1])
by localhost.localhost (8.9.3/8.9.3) with ESMTP id QAA01888
for <[email protected]>; Fri, 17 Dec 1999 16:58:46 +0100
Message-Id: <Pine.LNX.4.21.9912171656570.1869-100000@kiwi>
Date: Fri, 17 Dec 1999 16:58:45 +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: Carlo Maupoil <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Will pine be >>> Disposition-Notification-To: <<< compliant?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: root@kiwi
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

A lot of email programs recognize the
Disposition-Notification-To: [email protected]
header:
programs like Eudora, Netscape Mail, Outlook (...) usually ask the user
for permission to send a standard return receipt to the sender upon the
visualization of messages containing this header.

Will Pine endorse this ~"standard"?

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 17 Dec 1999 08:59:02 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA00339;
Fri, 17 Dec 1999 08:59:01 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA23235;
Fri, 17 Dec 1999 08:59:00 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA14134;
Fri, 17 Dec 1999 08:56:48 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA14590
for <[email protected]>; Fri, 17 Dec 1999 08:54:52 -0800
Received: from mail.living-source.com (blackice.living-source.com [195.52.135.33] (may be forged))
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA01648
for <[email protected]>; Fri, 17 Dec 1999 08:54:50 -0800
Received: (qmail 31029 invoked from network); 17 Dec 1999 17:26:37 -0000
Received: from mail.living-source.com (195.52.133.27)
by mail.living-source.com with SMTP; 17 Dec 1999 17:26:37 -0000
Message-Id: <Pine.LNX.4.10.9912171820560.30787-100000@localhost>
Date: Fri, 17 Dec 1999 18:26:31 +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: Adi Sieker <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: announcing a new patch!
In-Reply-To: <Pine.OSF.4.21.9912170148180.25818-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: adi@localhost
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 17 Dec 1999, Eduardo Chappa L. wrote:

> Hello,
>
[decription of a very interesting patch]

>
> If you want to try/test the patch pick it up from the address below and
> look for under: "Define your own rules and make pine flexible!". Please
> notify me of any problem you have with the patch.
>
Is there any chances of getting a PC-Pine Version with this patch
activated??
AFAIR, it's not possible to get PC-Pine sources.

Regards
Adi

--
/e2fsck: Illegal triply indirect block found while reading bad blocks
inode. This doesn't bode well, but we'll try to go on...
~
[email protected] tel:+761 / 15 25 8-13
http://www.living-source.com fax:+761 / 15 25 8-50

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 17 Dec 1999 13:04:57 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05432;
Fri, 17 Dec 1999 13:04:56 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA30874;
Fri, 17 Dec 1999 13:04:56 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA22933;
Fri, 17 Dec 1999 13:00:17 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA82960
for <[email protected]>; Fri, 17 Dec 1999 12:57:58 -0800
Received: from dante29.u.washington.edu ([email protected] [140.142.15.211])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA18916
for <[email protected]>; Fri, 17 Dec 1999 12:57:54 -0800
Received: from localhost (leibrand@localhost)
by dante29.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA91338
for <[email protected]>; Fri, 17 Dec 1999 12:57:48 -0800
Message-Id: <Pine.A41.4.21.9912171256410.38204-100000@dante29.u.washington.edu>
Date: Fri, 17 Dec 1999 12:57:48 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: announcing a new patch!
In-Reply-To: <Pine.LNX.4.10.9912171820560.30787-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Nope, the PC-Pine source is not available publicly.

You'll have to ask the Pine developers really nicely if they'd be willing
to compile Pine for you with the patch.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Fri, 17 Dec 1999, Adi Sieker wrote:

> On Fri, 17 Dec 1999, Eduardo Chappa L. wrote:
>
> > Hello,
> >
> [decription of a very interesting patch]
>
> >
> > If you want to try/test the patch pick it up from the address below and
> > look for under: "Define your own rules and make pine flexible!". Please
> > notify me of any problem you have with the patch.
> >
> Is there any chances of getting a PC-Pine Version with this patch
> activated??
> AFAIR, it's not possible to get PC-Pine sources.
>
>
> Regards
> Adi
>
> --
> ./e2fsck: Illegal triply indirect block found while reading bad blocks
> inode. This doesn't bode well, but we'll try to go on...
> ~
> [email protected] tel:+761 / 15 25 8-13
> http://www.living-source.com fax:+761 / 15 25 8-50
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 18 Dec 1999 12:25:12 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA25087;
Sat, 18 Dec 1999 12:25:11 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21251;
Sat, 18 Dec 1999 12:25:11 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA21956;
Sat, 18 Dec 1999 12:21:25 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA58540
for <[email protected]>; Sat, 18 Dec 1999 12:19:44 -0800
Received: from pipedream.smotrs.org (206-132-221-170.nas-1.RDL.primenet.com [206.132.221.170])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04463
for <[email protected]>; Sat, 18 Dec 1999 12:19:43 -0800
Received: from localhost (skull@localhost)
by pipedream.smotrs.org (8.9.3/8.9.3) with ESMTP id MAA09763
for <[email protected]>; Sat, 18 Dec 1999 12:21:30 -0800
Message-Id: <[email protected]>
Date: Sat, 18 Dec 1999 12:21:30 -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: "S.Toms" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: ACCESS ERROR
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Pine Info <[email protected]>
X-Authentication-Warning: pipedream.smotrs.org: skull owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

What would cause the following error to occur?
[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]

Inbox is set to the following
inbox-path = ~/mail/Inbox

and I have procmail moving my mail when received. It would help in
narrowing down the roblem if I knew what caused the error in the first
place. It also only happens to the Inbox, all other folders are
unaffected. I also don't know if this could cause me to lose mail if it
creates a write problem and prevents procmail from writing to it, I have
checked the MB-file with 'ls -l' and it shows it has the rw permissions
even while that error is still showing.
Any thoughts??

--
S.Toms - [email protected] - homepage is in the works
SuSE Linux v6.2+ - Kernel 2.2.13

"You can do this in a number of ways. IBM chose to do all of them.
Why do you find that funny?"
-- D. Taylor, Computer Science 350

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 18 Dec 1999 13:48: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA26385;
Sat, 18 Dec 1999 13:48:00 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA26229;
Sat, 18 Dec 1999 13:48:00 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA23411;
Sat, 18 Dec 1999 13:45:44 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA77968
for <[email protected]>; Sat, 18 Dec 1999 13:43:55 -0800
Received: from n2.net-uno.net ([206.49.154.35])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA08842
for <[email protected]>; Sat, 18 Dec 1999 13:43:54 -0800
Received: from eth0 ([172.16.13.204]) by n2.net-uno.net
(Post.Office MTA v3.5.2 release 221 ID# 0-60710U4100L500S0V35)
with ESMTP id net for <[email protected]>;
Sat, 18 Dec 1999 17:43:57 -0400
Message-Id: <Pine.LNX.4.20.9912181213520.538-100000@bjork>
Date: Sat, 18 Dec 1999 12:18:50 -0400 (VET)
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: "Diego A. Puertas F." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Problems in FROM field
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Lista: pine-info" <[email protected]>
X-Sender: dapf@bjork
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

The FROM field of the messages I send to mailing lists (the messages that
came back from the list) don't show the sender (myself), instead they show
the TO field (the addres to wich I have send the mails). This only happens
with Pine, it does not happen with elm nor mutt.

What is going on?

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 18 Dec 1999 14:16: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA26484;
Sat, 18 Dec 1999 14:16:28 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA26645;
Sat, 18 Dec 1999 14:16:27 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA17989;
Sat, 18 Dec 1999 14:13:53 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA93272
for <[email protected]>; Sat, 18 Dec 1999 14:12:07 -0800
Received: from ns1.syntegra.com (ns1.syntegra.com [150.143.16.2])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA24682
for <[email protected]>; Sat, 18 Dec 1999 14:12:06 -0800
Received: from [129.179.17.10] by ns1.cdc.com with ESMTP; Sat, 18 Dec 1999 16:12:01 -0600
Received: from localhost by calvin.twntpe.cdc.com with ESMTP; Sun, 19 Dec 1999 06:11:57 +0800
Message-Id: <[email protected]>
Date: Sun, 19 Dec 1999 06:11:57 +0800 (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: Edward M Greshko <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: Problems in FROM field
In-Reply-To: <Pine.LNX.4.20.9912181213520.538-100000@bjork>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Diego A. Puertas F." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sat, 18 Dec 1999, Diego A. Puertas F. wrote:

> The FROM field of the messages I send to mailing lists (the messages that
> came back from the list) don't show the sender (myself), instead they show
> the TO field (the addres to wich I have send the mails). This only happens
> with Pine, it does not happen with elm nor mutt.
>
> What is going on?

Working as designed....

Pine will display the To: addresses when it determines that the From: is
you. It assumes that you know you've sent the message and the maybe you'd
rather see who you sent it To:.

Fear not, everyone else will see that it is From: you.

Ed

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 19 Dec 1999 15:29:04 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA13003;
Sun, 19 Dec 1999 15:29:02 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA11360;
Sun, 19 Dec 1999 15:29:02 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA10244;
Sun, 19 Dec 1999 15:27:05 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA15282
for <[email protected]>; Sun, 19 Dec 1999 15:24:17 -0800
Received: from tao.agoron.com ([email protected] [206.181.233.66])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA24905
for <[email protected]>; Sun, 19 Dec 1999 15:24:17 -0800
Received: from tao.agoron.com (dosman.agoron.com [207.86.97.180])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id SAA04602
for <[email protected]>; Sun, 19 Dec 1999 18:24:15 -0500 (EST)
Message-Id: <[email protected]>
Date: Sun, 19 Dec 1999 18:28:33 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: header question:
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I noticed that on some systems, typically Solaris, Pine seems to insert the
following header:

X-Authentication-Warning:
somehost.somedomain.com: someuser owned process doing -bs

What exactly does this mean, what does this do? and is it caused by compiling
PINE with a certain parameter?

thanks in adavance!

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 19 Dec 1999 17:04:47 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA15401;
Sun, 19 Dec 1999 17:04:46 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA12622;
Sun, 19 Dec 1999 17:04:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA29150;
Sun, 19 Dec 1999 17:03:33 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA91950
for <[email protected]>; Sun, 19 Dec 1999 17:01:45 -0800
Received: from smtp2.cybersurf.net (smtp2.cybersurf.net [209.197.145.112])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02257
for <[email protected]>; Sun, 19 Dec 1999 17:01:45 -0800
Received: from webserver ([209.197.156.213]) by
smtp2.cybersurf.net (Netscape Messaging Server 4.05) with SMTP
id FN0LMR00.3YG for <[email protected]>; Sun, 19 Dec
1999 18:04:03 -0700
Message-Id: <000601bf4a8e$6c0a77a0$d59cc5d1@webserver>
Date: Sun, 19 Dec 1999 14:59:42 -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: "Duke Normandin" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: PC-Pine & Standalone Win95 box
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm pissing off too many people on *nix based mailing lists using Microsoft
& Netscape email clients. ;) I'm not on a LAN -- just a dialin to an ISP.
Besides PC-Pine, what do I need to get/do to have a Unix-compatible email
system on my box? TIA!!

later..........duke

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 19 Dec 1999 17:58:44 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA30991;
Sun, 19 Dec 1999 17:58:42 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA16909;
Sun, 19 Dec 1999 17:58:42 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA29689;
Sun, 19 Dec 1999 17:56:20 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA32840
for <[email protected]>; Sun, 19 Dec 1999 17:54:42 -0800
Received: from hal9k.org (PPP3-235.bom.vsnl.net.in [202.54.3.235])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA04797
for <[email protected]>; Sun, 19 Dec 1999 17:54:37 -0800
Received: from localhost (IDENT:satyap@localhost [127.0.0.1])
by hal9k.org (8.9.3/8.8.7) with ESMTP id HAA11052
for <[email protected]>; Mon, 20 Dec 1999 07:17:43 +0530
Message-Id: <[email protected]>
Date: Mon, 20 Dec 1999 07:17:43 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PC-Pine & Standalone Win95 box
In-Reply-To: <000601bf4a8e$6c0a77a0$d59cc5d1@webserver>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Dec 19, 1999 at 14:59, Duke Normandin wrote:

> I'm pissing off too many people on *nix based mailing lists using Microsoft
> & Netscape email clients. ;) I'm not on a LAN -- just a dialin to an ISP.
> Besides PC-Pine, what do I need to get/do to have a Unix-compatible email
> system on my box? TIA!!

In your MS/Netscape clients, you've probably got settings _other_ than:
send in plain text
line wrap 72 (or 75)
no MS-mime-ole (or whatever, see 1st point)

at least.

--
Satya. http://satyaonline.cjb.net/
Beta test of Mumbai bus guide at http://satyaonline.cjb.net/ !
FREE! Email reminder service at http://satyaonline.cjb.net/rem.html
<<< Hi! I'm a tagline virus! Steal me & join in the fun! >>>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 19 Dec 1999 17:59:19 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA15853;
Sun, 19 Dec 1999 17:59:18 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA13361;
Sun, 19 Dec 1999 17:59:18 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA08296;
Sun, 19 Dec 1999 17:58:07 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA18262
for <[email protected]>; Sun, 19 Dec 1999 17:54:46 -0800
Received: from hal9k.org (PPP3-235.bom.vsnl.net.in [202.54.3.235])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA04799
for <[email protected]>; Sun, 19 Dec 1999 17:54:43 -0800
Received: from localhost (IDENT:satyap@localhost [127.0.0.1])
by hal9k.org (8.9.3/8.8.7) with ESMTP id HAA11049
for <[email protected]>; Mon, 20 Dec 1999 07:15:15 +0530
Message-Id: <[email protected]>
Date: Mon, 20 Dec 1999 07:15:13 +0530 (IST)
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Satya <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: header question:
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Dec 19, 1999 at 18:28, Andy Malato wrote:

> I noticed that on some systems, typically Solaris, Pine seems to insert the
> following header:
>
> X-Authentication-Warning:
> somehost.somedomain.com: someuser owned process doing -bs

AFAICT, it's caused by setting user-domain in S)etup C)onfig (2nd line).
This is usually set if your email address' domain is different from your
machine's domain. (Like mine, but i hack sendmail.cf)

I used to get this but it went away after I hacked (more like 'slashed
blindly at') sendmail.cf and reset user-domain.

--
Satya. http://satyaonline.cjb.net/
Beta test of Mumbai bus guide at http://satyaonline.cjb.net/ !
FREE! Email reminder service at http://satyaonline.cjb.net/rem.html
<<< Hi! I'm a tagline virus! Steal me & join in the fun! >>>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sun, 19 Dec 1999 18: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA00474;
Sun, 19 Dec 1999 18:06:13 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA17075;
Sun, 19 Dec 1999 18:06:12 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA29938;
Sun, 19 Dec 1999 18:05:12 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA31110
for <[email protected]>; Sun, 19 Dec 1999 18:03:43 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id SAA00356
for <[email protected]>; Sun, 19 Dec 1999 18:03:43 -0800
Received: (qmail 23 invoked from network); 20 Dec 1999 02:03:42 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 20 Dec 1999 02:03:42 -0000
Message-Id: <[email protected]>
Date: Sun, 19 Dec 1999 19:04:05 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: PC-Pine & Standalone Win95 box
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Satya <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I wouldn't say that it is necessary to supress MIME encoding to stay
compatible with UNIX users. There are a lot of UNIX tools around that
handle MIME encoded mail. I usually include both MIME and plain text, and
I haven't received complaints from other UNIX users. Of course, that may
be because they don't bother to read my mail...

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Mon, 20 Dec 1999, Satya wrote:

> On Dec 19, 1999 at 14:59, Duke Normandin wrote:
>
> > I'm pissing off too many people on *nix based mailing lists using Microsoft
> > & Netscape email clients. ;) I'm not on a LAN -- just a dialin to an ISP.
> > Besides PC-Pine, what do I need to get/do to have a Unix-compatible email
> > system on my box? TIA!!
>
> In your MS/Netscape clients, you've probably got settings _other_ than:
> send in plain text
> line wrap 72 (or 75)
> no MS-mime-ole (or whatever, see 1st point)
>
> at least.
>
> --
> Satya. http://satyaonline.cjb.net/
> Beta test of Mumbai bus guide at http://satyaonline.cjb.net/ !
> FREE! Email reminder service at http://satyaonline.cjb.net/rem.html
> <<< Hi! I'm a tagline virus! Steal me & join in the fun! >>>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 20 Dec 1999 12:14:22 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21136;
Mon, 20 Dec 1999 12:14:20 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA03822;
Mon, 20 Dec 1999 12:14:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA29888;
Mon, 20 Dec 1999 12:12:56 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA28396
for <[email protected]>; Mon, 20 Dec 1999 12:11:30 -0800
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA28826
for <[email protected]>; Mon, 20 Dec 1999 12:11:30 -0800
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA02534;
Mon, 20 Dec 1999 12:11:29 -0800
Received: from localhost (hubert@localhost)
by shiva1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA17936;
Mon, 20 Dec 1999 12:11:29 -0800
Message-Id: <Pine.GUL.4.30.9912201208540.16978-100000@shiva1.cac.washington.edu>
Date: Mon, 20 Dec 1999 12:11:28 -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: header question:
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Andy Malato <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

That is being inserted by the sendmail on your system. By default,
sendmail thinks it should add that if you execute sendmail with the
"-bs" argument, which pine does by default. (Why that should cause an
authentication warning I don't know.) You can make it go away by adjusting
PrivacyOptions in sendmail.cf. Or you can make pine access sendmail
differently. If you have an smtp daemon running on your localhost you can
add smtp-server=localhost in Setup/Config. Or you could use a different
smtp server.

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

On Sun, 19 Dec 1999, Andy Malato wrote:

> I noticed that on some systems, typically Solaris, Pine seems to insert the
> following header:
>
> X-Authentication-Warning:
> somehost.somedomain.com: someuser owned process doing -bs
>
> What exactly does this mean, what does this do? and is it caused by compiling
> PINE with a certain parameter?
>
> thanks in adavance!
>
> ---Andy
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 21 Dec 1999 16:33:05 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA03988;
Tue, 21 Dec 1999 16:33:03 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA04102;
Tue, 21 Dec 1999 16:33:02 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA29729;
Tue, 21 Dec 1999 16:31:52 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA16548
for <[email protected]>; Tue, 21 Dec 1999 16:29:56 -0800
Received: from smtp1.cybersurf.net (smtp1.cybersurf.net [209.197.145.111])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA30940
for <[email protected]>; Tue, 21 Dec 1999 16:29:55 -0800
Received: from webserver ([209.197.153.111]) by
smtp1.cybersurf.net (Netscape Messaging Server 4.05) with SMTP
id FN49FQ00.L57 for <[email protected]>; Tue, 21 Dec
1999 17:31:02 -0700
Message-Id: <002001bf4c1c$4ff7d320$6f99c5d1@webserver>
Date: Tue, 21 Dec 1999 17:27:40 -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: "Duke Normandin" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: PC-Pine PINERC
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: <[email protected]>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

In PINERC "inbox-path=", what can I put in there to have Pine "inbound"
mail from the local folder stuffed by my mail transport program? Any
fully qualified path that I use simply gives me "Permission Denied".

What about "outbound" mail -- can Pine be forced to just save the mail in
a particular folder for my mail transport to handle?

TIA......duke

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Dec 1999 09:20:03 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA09985;
Fri, 24 Dec 1999 09:20:02 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA09691;
Fri, 24 Dec 1999 09:20:02 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA23076;
Fri, 24 Dec 1999 09:18:11 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA35594
for <[email protected]>; Fri, 24 Dec 1999 09:15:04 -0800
Received: from mtiwmhc02.worldnet.att.net (mtiwmhc02.worldnet.att.net [204.127.131.37])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA22810
for <[email protected]>; Fri, 24 Dec 1999 09:15:04 -0800
Received: from 122.reno-03-04rs16rt.nv.dial-access.att.net
([12.72.145.122]) by mtiwmhc02.worldnet.att.net
(InterMail v03.02.07.07 118-134) with ESMTP
id <19991224171503.FXVJ1914@122.reno-03-04rs16rt.nv.dial-access.att.net>
for <[email protected]>; Fri, 24 Dec 1999 17:15:03 +0000
Message-Id: <[email protected]>
Date: Fri, 24 Dec 1999 09: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: James <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: HTML attachments?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm using PC-Pine 4.21. When I get a message with an HTML attachment,
and try to view the attachment, Pine tries to start a copy of MS
Internet Explorer. How do I get it to view the code with my choice of
viewer? I want to see the actual HTML code, not have it displayed.

As it happens, this particular message was a link that supposedly would
download a worm program to my machine. I'm not so foolish as to view
such messages while on-line, so no harm was done, but I'd still like to
remove the possibility of it happening in the future.

James

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Dec 1999 09:37:12 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA08646;
Fri, 24 Dec 1999 09:37:11 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA09884;
Fri, 24 Dec 1999 09:37:10 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA23329;
Fri, 24 Dec 1999 09:35:49 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA28094
for <[email protected]>; Fri, 24 Dec 1999 09:34:46 -0800
Received: from mail.neta.com (nfs.neta.com [206.124.164.2])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA23866
for <[email protected]>; Fri, 24 Dec 1999 09:34:46 -0800
Received: (qmail 12853 invoked from network); 24 Dec 1999 17:34:45 -0000
Received: from gurd.cql.com (HELO maris.cql.com) ([email protected])
by nfs.neta.com with SMTP; 24 Dec 1999 17:34:45 -0000
Message-Id: <[email protected]>
Date: Fri, 24 Dec 1999 10:34:57 -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: Seth Kurtzberg <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: HTML attachments?
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: James <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

There is an option, "url-viewers", that you can use to specify a browser.

Seth Kurtzberg
Machine Independent Software
Cell (602) 478-5511
Fax: (480) 614-8909
email: [email protected]
pager: 888-605-9296 or email [email protected]

On Fri, 24 Dec 1999, James wrote:

> I'm using PC-Pine 4.21. When I get a message with an HTML attachment,
> and try to view the attachment, Pine tries to start a copy of MS
> Internet Explorer. How do I get it to view the code with my choice of
> viewer? I want to see the actual HTML code, not have it displayed.
>
> As it happens, this particular message was a link that supposedly would
> download a worm program to my machine. I'm not so foolish as to view
> such messages while on-line, so no harm was done, but I'd still like to
> remove the possibility of it happening in the future.
>
> James
>
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Dec 1999 11:56:27 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA11578;
Fri, 24 Dec 1999 11:56:26 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA11934;
Fri, 24 Dec 1999 11:56:26 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA29780;
Fri, 24 Dec 1999 11:55:25 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA28138
for <[email protected]>; Fri, 24 Dec 1999 11:54:23 -0800
Received: from fd0man.pentanet.net (IDENT:[email protected] [205.133.169.96])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA24228
for <[email protected]>; Fri, 24 Dec 1999 11:54:20 -0800
Received: from localhost (fd0man@localhost)
by fd0man.pentanet.net (8.9.3/8.9.3) with ESMTP id PAA18605
for <[email protected]>; Fri, 24 Dec 1999 15:58:42 -0500
Message-Id: <[email protected]>
Date: Fri, 24 Dec 1999 15:58:42 -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: "Michael B. Trausch" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Unable to set external filters...
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-Authentication-Warning: fd0man.pentanet.net: fd0man owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi all,

I have Pine version 4.21, and I have configured a set of external filters
for use with the PGP system for Linux. However, Pine ignores those
settings. Here is the options that I have enabled for this configuration:

[X] compose-send-offers-first-filter
display-filters = _LEADING("-----BEGIN PGP")_ /usr/bin/pgp4pine -d -i _TMPFILE_
sending-filters = /usr/local/bin/pgp4pine -e -i _TMPFILE_ -t /tmp/pgp4pine.tmp -r _RECIPIENTS_

I looked at the help file, and it seems to insist that
compose-send-offers-first-filter is the key part to get the
display-filters and sending-filters to work. I have a feeling that either
the help file is right and that there is a minor bug in Pine 4.21 (maybe a
code snippet was commented out for debugging and not put back) or that the
options were changed a bit and the help file wasn't updated to reflect
that. I've gone up and down the Setup --> Configuration screen a few
times now and I'm not seeing any additional options to allow this. Also,
when I go to send a message, here's what shows up in the final lines of
the screen:

Send message?
? Help Y [Yes] ^R Background
^C Cancel N No D DSNOpts

After pressing ^X. No mention of the PGP stuff.

Help, please?

I'm running PINE 4.21, on Red Hat Linux 6.1 (Kernel Version 2.2.12-20),
pgp4pine 1.56, PGP 6.5.2, bash 2.02. I can't think of anything else that
may help y'all out... ask, and I will tell ya, tho.

Thanks!

- Mike Trausch

--
,-._.-._.-._.-._.-.
`-. ,-'
| | Michael B. Trausch
.----------------------. | | [email protected]
| I love Linux! In | | | AIM: CSMFSOBW
| fact, so does my mom! | | | ----------------------
| | ,';".________.-. Need your computer
| Wait'll I tell Big | ;';_' )] upgraded or repaired?
| Bill that my mom | ; `-| E-mail me!
| uses Linux! `. `T- | ----------------------
`----------------------._ \ | |
`-; | |
|..________..-|
/\/ |________..|
,'`./ >,( |
\_.-|_/,-/ ii | |
`."' `-/ .-"""|| |
/`^"-; | ||____|
/ / `.__/ | ||
/ | ||
| ||

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 24 Dec 1999 22:50:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA12727;
Fri, 24 Dec 1999 22:50:21 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA20334;
Fri, 24 Dec 1999 22:50:21 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA26021;
Fri, 24 Dec 1999 22:49:11 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA78020
for <[email protected]>; Fri, 24 Dec 1999 22:48:12 -0800
Received: from seashell.sasquatch.com (IDENT:[email protected] [165.90.7.18])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA31089
for <[email protected]>; Fri, 24 Dec 1999 22:48:11 -0800
Received: (qmail 16842 invoked by uid 4803); 25 Dec 1999 06:48:10 -0000
Message-Id: <[email protected]>
Date: Fri, 24 Dec 1999 22:48:10 -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: Len Burns <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: An Unusual need for a reply-leadin
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi,

I have a request from one of my users who has fairly severe
limitations on hand movement as well as vision that I seem unable to
fulfill. In earlier versions of pine, when one hit reply, the cursor
was positioned below the dashed line dividing the message from the
headers, then there were a couple of blank lines, and then the
included message. In recent times, this behavior has changed
slightly. Assuming no role is defined, there is no longer any
vertical space between the cursor, and the beginning of the included
message. For disability reasons that are complicated to explain, what
she needs to best work with her mail is the old behavior. She need
the cursor placed just below the dashed line, 2 blank lines, and then
the included text. I have to believe there is a way to do this, but I
am certainly at a loss. I have looked closely at the reply-leadin
variable, but see no obvious way to embed blank lines in it. First I
thought perhaps a role wiht a template file, no dice, it places the
cursor below the blank lines. Your wisdom would be deeply
appreciated. TIA

-Len

--
Len Burns,
Site Engineer for Sasquatch Computer
[email protected]
Voice: 831-420-1053
Fax: 831-420-0468

Murphy's Eighth Law: If everything seems to be going well, you have
obviously overlooked something.

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Sat, 25 Dec 1999 07:58:30 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA19098;
Sat, 25 Dec 1999 07:58:29 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA30784;
Sat, 25 Dec 1999 07:58:29 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA10580;
Sat, 25 Dec 1999 07:57:28 -0800
Received: from jason03.u.washington.edu ([email protected] [140.142.77.10])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA30994
for <[email protected]>; Sat, 25 Dec 1999 07:56:11 -0800
Received: from dante21.u.washington.edu ([email protected] [140.142.15.71])
by jason03.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA19256
for <[email protected]>; Sat, 25 Dec 1999 07:56:10 -0800
Received: from localhost (leibrand@localhost)
by dante21.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA93936
for <[email protected]>; Sat, 25 Dec 1999 07:56:10 -0800
Message-Id: <Pine.A41.4.21.9912250754080.70474-100000@dante21.u.washington.edu>
Date: Sat, 25 Dec 1999 07:56:09 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: An Unusual need for a reply-leadin
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

You could try putting the signature at the top (like mine) and embedding
your blank lines in the top of that. I think you just need to uncheck
signature-at-bottom in Pine's config. Although my sig has no blank lines
at the beginning and I still get two lines before it starts, whether or
not I'm using roles.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Fri, 24 Dec 1999, Len Burns wrote:

> Hi,
>
> I have a request from one of my users who has fairly severe
> limitations on hand movement as well as vision that I seem unable to
> fulfill. In earlier versions of pine, when one hit reply, the cursor
> was positioned below the dashed line dividing the message from the
> headers, then there were a couple of blank lines, and then the
> included message. In recent times, this behavior has changed
> slightly. Assuming no role is defined, there is no longer any
> vertical space between the cursor, and the beginning of the included
> message. For disability reasons that are complicated to explain, what
> she needs to best work with her mail is the old behavior. She need
> the cursor placed just below the dashed line, 2 blank lines, and then
> the included text. I have to believe there is a way to do this, but I
> am certainly at a loss. I have looked closely at the reply-leadin
> variable, but see no obvious way to embed blank lines in it. First I
> thought perhaps a role wiht a template file, no dice, it places the
> cursor below the blank lines. Your wisdom would be deeply
> appreciated. TIA
>
> -Len
>
> --
> Len Burns,
> Site Engineer for Sasquatch Computer
> [email protected]
> Voice: 831-420-1053
> Fax: 831-420-0468
>
> Murphy's Eighth Law: If everything seems to be going well, you have
> obviously overlooked something.
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Mon, 27 Dec 1999 22:24:41 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA14189;
Mon, 27 Dec 1999 22:24:39 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA20992;
Mon, 27 Dec 1999 22:24:38 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA10515;
Mon, 27 Dec 1999 22:23:26 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA54602
for <[email protected]>; Mon, 27 Dec 1999 22:19:21 -0800
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA24022
for <[email protected]>; Mon, 27 Dec 1999 22:19:21 -0800
Received: from jason02.u.washington.edu ([email protected] [140.142.76.8])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA20924
for <[email protected]>; Mon, 27 Dec 1999 22:19:21 -0800
Received: from dante32.u.washington.edu ([email protected] [140.142.15.214])
by jason02.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA30342
for <[email protected]>; Mon, 27 Dec 1999 22:19:20 -0800
Received: from localhost (leibrand@localhost)
by dante32.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA49266
for <[email protected]>; Mon, 27 Dec 1999 22:19:20 -0800
Message-Id: <Pine.A41.4.21.9912272211370.65646-100000@dante32.u.washington.edu>
Date: Mon, 27 Dec 1999 22:19:17 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Filtering out my own postings
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I just set up a Pine Filter to try to filter out all my own postings to
this newsgroup. The filter looks like this:

>From pattern = leib
Current Folder Type =
(*) News
Filter Action =
(*) Delete

It successfully deletes all my own postings so I don't see them, but I've
got comp.mail.pine set up as an incoming folder, and it keeps insisting I
have two recent messages every time I open comp.mail.pine. It never seems
to "delete" them like it should, and it never gives me a chance to do it
manually, since they get deleted from the index. Does anyone know if it's
possible to make Pine's filters work right on an incoming-folder
newsgroup?

BTW, the newsgroup is defined in the incoming-folder-list as:

"comp.mail.pine" {news.u.washington.edu/nntp}comp.mail.pine

Thanks,
--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 18:46: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA30348;
Tue, 28 Dec 1999 18:46:20 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA12728;
Tue, 28 Dec 1999 18:46:20 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA29865;
Tue, 28 Dec 1999 18:45:17 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA27828
for <[email protected]>; Tue, 28 Dec 1999 18:41:51 -0800
Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA23590
for <[email protected]>; Tue, 28 Dec 1999 18:41:50 -0800
Received: (from daemon@localhost)
by smtp01.primenet.com (8.9.3/8.9.3) id TAA08728
for <[email protected]>; Tue, 28 Dec 1999 19:41:34 -0700 (MST)
Received: from usr06.primenet.com(206.165.6.206)
via SMTP by smtp01.primenet.com, id smtpdAAAvlay8q; Tue Dec 28 19:41:25 1999
Received: from localhost (fairall@localhost)
by usr06.primenet.com (8.8.5/8.8.5) with ESMTP id TAA26942
for <[email protected]>; Tue, 28 Dec 1999 19:41:38 -0700 (MST)
Message-Id: <[email protected]>
Date: Tue, 28 Dec 1999 21:41:38 -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: Leslie Fairall <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: return receipt feature
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: usr06.primenet.com: fairall owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hello:

I turned on the return-receipt feature by typing the line:

return-receipt-to: [email protected]

in my custom headers. I recceive a receipt from some ISPs, but not
from others. I am an on an ISP that also uses pine that will not generate
a return receipt. I have also noticed that if I send a message to myself
or someone else on the same ISP, I will not get a receipt either. Does
anyone know why this may be happening?

***** **************************************************
"Contrary to popular belief, Unix is user friendly. It's
just very particular about who it makes friends with."

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 19:08:11 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03519;
Tue, 28 Dec 1999 19:08:10 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA10123;
Tue, 28 Dec 1999 19:08:09 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA08461;
Tue, 28 Dec 1999 19:07:05 -0800
Received: from jason04.u.washington.edu ([email protected] [140.142.78.5])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA27872
for <[email protected]>; Tue, 28 Dec 1999 19:04:27 -0800
Received: from dante29.u.washington.edu ([email protected] [140.142.15.211])
by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA23892
for <[email protected]>; Tue, 28 Dec 1999 19:04:26 -0800
Received: from localhost (leibrand@localhost)
by dante29.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA106566
for <[email protected]>; Tue, 28 Dec 1999 19:04:26 -0800
Message-Id: <Pine.A41.4.21.9912281903210.96420-100000@dante29.u.washington.edu>
Date: Tue, 28 Dec 1999 19:04:26 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Check out section 3.2 of the Pine FAQ, entitled: Can I get a
"return-receipt" when sending a message with Pine? It's at
<http://www.washington.edu/pine/faq/problems.html#xtocid1175413>.

Basically, Pine was designed to not respond to return receipt requests.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Tue, 28 Dec 1999, Leslie Fairall wrote:

> Hello:
>
> I turned on the return-receipt feature by typing the line:
>
> return-receipt-to: [email protected]
>
> in my custom headers. I recceive a receipt from some ISPs, but not
> from others. I am an on an ISP that also uses pine that will not generate
> a return receipt. I have also noticed that if I send a message to myself
> or someone else on the same ISP, I will not get a receipt either. Does
> anyone know why this may be happening?
>
>
>
>
>
> ***** **************************************************
> "Contrary to popular belief, Unix is user friendly. It's
> just very particular about who it makes friends with."
>
> --
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see:
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 19:50:54 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA01230;
Tue, 28 Dec 1999 19:50:53 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA10715;
Tue, 28 Dec 1999 19:50:52 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA08332;
Tue, 28 Dec 1999 19:49:41 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA34242
for <[email protected]>; Tue, 28 Dec 1999 19:46:56 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA27728
for <[email protected]>; Tue, 28 Dec 1999 19:46:56 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA10649;
Tue, 28 Dec 1999 19:46:55 -0800
Received: from dante11.u.washington.edu ([email protected] [140.142.15.21])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA26944;
Tue, 28 Dec 1999 19:46:55 -0800
Received: from localhost (leibrand@localhost)
by dante11.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA12738;
Tue, 28 Dec 1999 19:46:54 -0800
Message-Id: <Pine.A41.4.21.9912281912390.81034-100000@dante11.u.washington.edu>
Date: Tue, 28 Dec 1999 19:46:51 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Passwordless Pine FAQ candidate
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Two FAQ candidates. Please tell me what you think:

Title: Eliminating repeated password prompts in Pine.

Question: How come Pine keeps asking for my password every time I open a
folder?

Answer: Probably because it is confused about who to log in as.

To clear up the confusion, edit your .pinerc and /user=yourusername to
every instance of your mail server address. For example,
{mail.mydomain.com}INBOX would become
{mail.mydomain.com/user=myusername}INBOX.

No matter what you do to try and save your password, it won't work unless
you fix this problem first.

Title: Using Pine with SSH for passwordless access.

Question: I'm running Pine on a Unix machine with my mail on an IMAP
server, and I have to type in a password every time I want to read my
mail. Is there any way I can set it up so I don't have to type my
password?

Answer: Yes, but how secure your password is depends on how you do it.

The traditional way to do this has been to create a PASSFILE that contains
a very weakly encrypted copy of your password. This works fine, except
that your password is no more secure than the PASSFILE. If you want to
set up a PASSFILE anyway, you can find directions at
<http://www.washington.edu/pine/tech-notes/installation.html>.

A much better way is to use the Secure Shell (SSH) protocol and set up a
public-private key pair to allow passwordless connections between two
trusted servers. All connections with SSH are encrypted and unreadable by
password sniffers, so your password is much safer than if you typed in
your password the old-fashioned way. One other nice thing about using SSH
is that you can open a telnet-style connection between hosts and even
forward X11 (X-term) connections between hosts, all without having to
type in your password. And if you're really lazy, you can even use Tera
Term Pro with TTSSH (see Nancy McGough's links at
<http://www.ii.com/internet/messaging/pine/index.html#telnet>) and get
passwordless telnet access from your PC. But I digress. :)

For Pine to use SSH, both hosts involved (the machine you run Pine on and
the IMAP server) must support SSH, and you must have access to the
~/.ssh/authorized_keys file on your IMAP server. It's easiest to set
things up if you have access to a shell on your IMAP server as well, but
it's not absolutely necessary.

First, you need to set up a public-private key pair. This is usually done
using ssh-keygen, which you run on the client computer (the one you run
Pine on):

- From a shell prompt, type ssh-keygen.
- ssh-keygen will generate some random numbers, then ask you where to put
the private key. The default should be fine, in most cases.
- Next it asks for a "passphrase" and ask you to confirm it. This is
basically a password to go with your key. If you want passwordless
access, you'll want to leave the passphrase blank. This will mean that
anyone who gets a-hold of your private key can access your account, though,
so be careful about what you do with it.
- Then it will generate the file you specified, and another file in the
same place with .pub on the end. This is your public key - the one you
want to put on the IMAP server.

To authorize connections from your Pine machine to the IMAP server, you
need to insert the contents of your public key into the
~/.ssh/authorized_keys file on the IMAP server. You can have more than
one public key in that file, but each needs to be on its own line, and NOT
WORD WRAPPED. That means using the -w flag if you edit it with Pico.

Once you've got your keys in the right place, test the connection by
typing:

ssh my.imap.server

from a shell prompt on your Pine machine. It should connect without
requiring a password. If it does require a password, then your keys
aren't set up right.

If the connection goes through, you'll want to tell Pine to use SSH now.
To do so, edit your .pinerc and edit the following lines (use the correct
path to ssh, of course. You can usually determine it by typing "which
ssh"):

# Sets the name of the command used to open a UNIX secure shell
# connection. Typically this is /usr/local/bin/ssh.
ssh-path=/usr/local/bin/ssh

# Sets the format of the command used to open a UNIX secure
# shell connection. The default is "%s %s -l %s exec /etc/r%sd"
# NOTE: the 4 (four) "%s" entries MUST exist in the provided command
# where the first is for the command's path, the second is for the
# host to connect to, the third is for the user to connect as, and the
# fourth is for the connection method (typically "imap")
ssh-command=%s %s -q -l %s exec /etc/r%sd

Once that is set, you should have passwordless access to your mail in
Pine. Now you can start playing with other applications of SSH... :)

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 21:14:14 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04083;
Tue, 28 Dec 1999 21:14:13 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA11917;
Tue, 28 Dec 1999 21:14:13 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA10510;
Tue, 28 Dec 1999 21:13:01 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA39382
for <[email protected]>; Tue, 28 Dec 1999 21:11:27 -0800
Received: from vax.area.com (vax.area.com [216.218.218.27])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA09594
for <[email protected]>; Tue, 28 Dec 1999 21:11:26 -0800
Received: (qmail 21151 invoked by uid 1828); 29 Dec 1999 05:11:20 -0000
Message-Id: <[email protected]>
Date: Tue, 28 Dec 1999 21:11:20 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Leslie Fairall <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Dec 1999, Leslie Fairall wrote:

>Date: Tue, 28 Dec 1999 21:41:38 -0500 (EST)
>From: Leslie Fairall <[email protected]>
>To: Pine Discussion Forum <[email protected]>
>Subject: return receipt feature
>
>Hello:
>
>I turned on the return-receipt feature by typing the line:
>
>return-receipt-to: [email protected]
>
>in my custom headers. I recceive a receipt from some ISPs, but not
>from others. I am an on an ISP that also uses pine that will not generate

Where are the custom headers? Is this just a receipt for when the
message _arrives_ or when it's read?

If for when it arrives, isn't the lack of an almost immediate bounce
good circumstantial evidence that it got there? I'm not meaning to argue,
I'm curious.

About the _only_ feature of the awful QuickMail we used to use at work that
I miss is the ability to actually see when someone READ the message you sent.
(Via return receipts, and I think you could also effectively open the message
from your sent mail to check it that way too.) I realize a lot of people
spaz out about privacy about things like this, but it's convenient as hell.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 21:17:57 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04265;
Tue, 28 Dec 1999 21:17:55 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA14907;
Tue, 28 Dec 1999 21:17:55 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA10663;
Tue, 28 Dec 1999 21:16:56 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA15936
for <[email protected]>; Tue, 28 Dec 1999 21:15:32 -0800
Received: from vax.area.com (vax.area.com [216.218.218.27])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA09863
for <[email protected]>; Tue, 28 Dec 1999 21:15:30 -0800
Received: (qmail 21301 invoked by uid 1828); 29 Dec 1999 05:15:24 -0000
Message-Id: <[email protected]>
Date: Tue, 28 Dec 1999 21:15:24 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: ignore my last message Re: return receipt feature
In-Reply-To: <Pine.A41.4.21.9912281903210.96420-100000@dante29.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Scott Leibrand <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Argh, ignore my last message. I don't know what I was searching for
the first time, but I just found "customized-hdrs".

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 21:37: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04632;
Tue, 28 Dec 1999 21:37:28 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA15144;
Tue, 28 Dec 1999 21:37:27 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA12138;
Tue, 28 Dec 1999 21:35:48 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA18214
for <[email protected]>; Tue, 28 Dec 1999 21:34:19 -0800
Received: from fd0man.pentanet.net (IDENT:[email protected] [205.133.169.50])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA20304
for <[email protected]>; Tue, 28 Dec 1999 21:34:17 -0800
Received: from localhost (fd0man@localhost)
by fd0man.pentanet.net (8.9.3/8.9.3) with ESMTP id BAA07962;
Wed, 29 Dec 1999 01:39:02 -0500
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 01:39:02 -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: "Michael B. Trausch" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: [email protected]
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: fd0man.pentanet.net: fd0man owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 28 Dec 1999 [email protected] wrote:
>
> About the _only_ feature of the awful QuickMail we used to use at work
> that I miss is the ability to actually see when someone READ the
> message you sent. (Via return receipts, and I think you could also
> effectively open the message from your sent mail to check it that way
> too.) I realize a lot of people spaz out about privacy about things
> like this, but it's convenient as hell.
>

I would be one of those people, depending on what it is. Right now, of
course, since I read this thread, I'm doing a little experiment on Pine's
way of managing return reciepts, but I almost never request a return
reciept, becuase I feel that if someone wants me to know that they got an
email, that they'll tell me.

I would like to see various email clients have the ability to send a
return reciept when someone reads a message, sometimes, as with urgent
messages, that would be a good thing.

Now that I think on it, the only time I have ever attached a return
reciept request to an email was to test someone's credibility -- I had a
boyfriend that kept insisting that he wasn't getting *any* of my emails at
*any* of his email addresses, and so I sent three individual emails to him
at those addresses, with an extended DSN header on them requesting a
return recipt, and I got three return reciepts back stating that the
message was successfully delivered to the mailbox, and on the two that his
mail client (Netscape Communicator) downloaded the messages on, it sent a
*second* return recipt stating that it was, in fact, downloaded and
potentially read.

So I found out that he was full of bullshit.

But other than that, and the little experiment that I'm doing at the
moment, I've never used return reciepts.

--
,-._.-._.-._.-._.-.
`-. ,-'
.----------------------. | | Michael B. Trausch
| Dilbert's Comment | | | [email protected]
| Corner | | | AIM: CSMFSOBW
|------------------------| | | ----------------------
| Pschitt - A real life | ,';".________.-. Need your computer
| German drink that | ;';_' )] upgraded or repaired?
| doesn't sound too | ; `-| E-mail me!
| appetizing. `. `T- | ----------------------
`----------------------._ \ | |
`-; | |
|..________..-|
/\/ |________..|
,'`./ >,( |
\_.-|_/,-/ ii | |
`."' `-/ .-"""|| |
/`^"-; | ||____|
/ / `.__/ | ||
/ | ||
| ||

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Tue, 28 Dec 1999 22:07:24 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA03817;
Tue, 28 Dec 1999 22:07:23 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA12733;
Tue, 28 Dec 1999 22:07:22 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA10480;
Tue, 28 Dec 1999 22:06:07 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA14140
for <[email protected]>; Tue, 28 Dec 1999 22:02:58 -0800
Received: from tao.agoron.com ([email protected] [206.181.233.66])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA01521
for <[email protected]>; Tue, 28 Dec 1999 22:02:57 -0800
Received: from tao.agoron.com (dosman.agoron.com [207.86.97.180])
by tao.agoron.com (8.8.7/8.8.7) with ESMTP id BAA19065;
Wed, 29 Dec 1999 01:03:05 -0500 (EST)
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 01:06:51 -0500
Sender: [email protected]
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:[email protected]?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:[email protected]?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:[email protected]> (Human contact for the list)
List-Post: <mailto:[email protected]>
From: Andy Malato <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: "Michael B. Trausch" <[email protected]>,
Pine Discussion Forum <[email protected]>
X-Accept-Language: en
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Ok that's one use for return receipt -- although that's something I've never
heard before, I'm sure the folks at UW will be happy that they included return
receipt capablilites in PINE to help you trackdown the BullS* artist!!

---Andy

"Michael B. Trausch" wrote:
>
> On Tue, 28 Dec 1999 [email protected] wrote:
> >

> boyfriend that kept insisting that he wasn't getting *any* of my emails at
> *any* of his email addresses, and so I sent three individual emails to him
> at those addresses, with an extended DSN header on them requesting a
> return recipt, and I got three return reciepts back stating that the
> message was successfully delivered to the mailbox, and on the two that his
> mail client (Netscape Communicator) downloaded the messages on, it sent a
> *second* return recipt stating that it was, in fact, downloaded and
> potentially read.
>
> So I found out that he was full of bullshit.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 04:46:37 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA16010;
Wed, 29 Dec 1999 04:46:35 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA19360;
Wed, 29 Dec 1999 04:46:35 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id EAA15614;
Wed, 29 Dec 1999 04:45:34 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA09716
for <[email protected]>; Wed, 29 Dec 1999 04:43:44 -0800
Received: from smtp1.libero.it (smtp1.libero.it [193.70.192.51])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA08208
for <[email protected]>; Wed, 29 Dec 1999 04:43:43 -0800
Received: from localhost.localhost (151.15.36.18) by smtp1.libero.it; 29 Dec 1999 13:43:38 +0100
Received: from kiwi (IDENT:root@kiwi [127.0.0.1])
by localhost.localhost (8.9.3/8.9.3) with ESMTP id NAA01953
for <[email protected]>; Wed, 29 Dec 1999 13:16:25 +0100
Message-Id: <Pine.LNX.4.21.9912291147370.1410-100000@kiwi>
Date: Wed, 29 Dec 1999 13:16:24 +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: Carlo Maupoil <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature - Re: Will pine be >>> Disposition-Notification-To:
<<< compliant?
In-Reply-To: <Pine.LNX.4.21.9912171656570.1869-100000@kiwi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-Sender: root@kiwi
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Time ago I asked about
"Disposition-Notification-To:" feature.

On Netscape Communicator there are some return receipt feature options:
(see the menu "Netscape/Preferences/Mail & Newsgroups/Return Receipts")
DSN: to obtain a delivery receipt from the receiving _server_ (that's
already supported by Pine)
MDN: to obtain an automatic notification upon the displaying of
the message body by the _mail program_ of the addressee

Some RFCs regarding these features are: RFC2298, RFC1894, RFC2530
see http://www.faqs.org/rfcs/rfc2298.html
http://www.landfield.com/rfcs/rfc2530.html

I would like the MDN implemented on Pine: of course this feature
should be optional.

Currently with Pine I can send email with the
"Disposition-Notification-To: <myaddress>" header simply by adding it in
the
"customized-hdrs"; but on the other side Pine doesn't generate
notification messages upon MDN
requests.

Thanks,
Carlo

On Fri, 17 Dec 1999, Carlo Maupoil wrote:

> A lot of email programs recognize the
> Disposition-Notification-To: [email protected]
> header:
> programs like Eudora, Netscape Mail, Outlook (...) usually ask the user
> for permission to send a standard return receipt to the sender upon the
> visualization of messages containing this header.
>
> Will Pine endorse this ~"standard"?

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 05:11:43 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA16085;
Wed, 29 Dec 1999 05:11:42 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA22620;
Wed, 29 Dec 1999 05:11:41 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA16166;
Wed, 29 Dec 1999 05:10:39 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA34090
for <[email protected]>; Wed, 29 Dec 1999 05:09:24 -0800
Received: from fd0man.pentanet.net (IDENT:[email protected] [205.133.169.45])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA20541
for <[email protected]>; Wed, 29 Dec 1999 05:09:23 -0800
Received: from localhost (fd0man@localhost)
by fd0man.pentanet.net (8.9.3/8.9.3) with ESMTP id JAA09280;
Wed, 29 Dec 1999 09:13:52 -0500
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 09:13:52 -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: "Michael B. Trausch" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Andy Malato <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: fd0man.pentanet.net: fd0man owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 29 Dec 1999, Andy Malato wrote:
>
> Ok that's one use for return receipt -- although that's something I've
> never heard before, I'm sure the folks at UW will be happy that they
> included return receipt capablilites in PINE to help you trackdown the
> BullS* artist!!
>

That's really the only practical use I can think of for return reciepts,
other than ensuring that urgent messages get through (especially in
corporate environments). I was talking to someone at my school and they
want to create an edited version of pine that send return reciepts when
messages are read (after saying, "This message has a return reciept
request, do you wish to send a return reciept?"). I rather like the idea,
because I can send an email to my teacher or supervisor and say "Yo, this
is urgent" and know when they read it.

--
,-._.-._.-._.-._.-.
`-. ,-'
.----------------------. | | Michael B. Trausch
| Dilbert's Comment | | | [email protected]
| Corner | | | AIM: CSMFSOBW
|------------------------| | | ----------------------
| Pschitt - A real life | ,';".________.-. Need your computer
| German drink that | ;';_' )] upgraded or repaired?
| doesn't sound too | ; `-| E-mail me!
| appetizing. `. `T- | ----------------------
`----------------------._ \ | |
`-; | |
|..________..-|
/\/ |________..|
,'`./ >,( |
\_.-|_/,-/ ii | |
`."' `-/ .-"""|| |
/`^"-; | ||____|
/ / `.__/ | ||
/ | ||
| ||

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 11:23: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA22098;
Wed, 29 Dec 1999 11:23:12 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30789;
Wed, 29 Dec 1999 11:23:11 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA22473;
Wed, 29 Dec 1999 11:22:04 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA11504
for <[email protected]>; Wed, 29 Dec 1999 11:19:08 -0800
Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA24627
for <[email protected]>; Wed, 29 Dec 1999 11:18:46 -0800
Received: (from daemon@localhost)
by smtp01.primenet.com (8.9.3/8.9.3) id MAA19766;
Wed, 29 Dec 1999 12:18:32 -0700 (MST)
Received: from usr08.primenet.com(206.165.6.208)
via SMTP by smtp01.primenet.com, id smtpdAAA.caOEM; Wed Dec 29 12:18:19 1999
Received: from localhost (fairall@localhost)
by usr08.primenet.com (8.8.5/8.8.5) with ESMTP id MAA27763;
Wed, 29 Dec 1999 12:18:30 -0700 (MST)
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 14:18:29 -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: Leslie Fairall <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Michael B. Trausch" <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: usr08.primenet.com: fairall owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi All:

The main reason why I would like to use return-receipts is for
school-related also. I am a graduate student that emails a lot of my
assignments. Last semester I kept asking one of my professors if he had
received my assignment. He kept saying he had to check his email first. I
figure that if I can get a return receipt when my professors read the
message, I will have a confirmation that he/she received my email and can
keep it in a folder for my records until the end of the semester. I think
that's a legitimate use for return receipts.

On Wed, 29 Dec 1999, Michael B. Trausch wrote:

> On Wed, 29 Dec 1999, Andy Malato wrote:
> >
> > Ok that's one use for return receipt -- although that's something I've
> > never heard before, I'm sure the folks at UW will be happy that they
> > included return receipt capablilites in PINE to help you trackdown the
> > BullS* artist!!
> >
>
> That's really the only practical use I can think of for return reciepts,
> other than ensuring that urgent messages get through (especially in
> corporate environments). I was talking to someone at my school and they
> want to create an edited version of pine that send return reciepts when
> messages are read (after saying, "This message has a return reciept
> request, do you wish to send a return reciept?"). I rather like the idea,
> because I can send an email to my teacher or supervisor and say "Yo, this
> is urgent" and know when they read it.
>
> --
> ,-._.-._.-._.-._.-.
> `-. ,-'
> .----------------------. | | Michael B. Trausch
> | Dilbert's Comment | | | [email protected]
> | Corner | | | AIM: CSMFSOBW
> |------------------------| | | ----------------------
> | Pschitt - A real life | ,';".________.-. Need your computer
> | German drink that | ;';_' )] upgraded or repaired?
> | doesn't sound too | ; `-| E-mail me!
> | appetizing. `. `T- | ----------------------
> `----------------------._ \ | |
> `-; | |
> |..________..-|
> /\/ |________..|
> ,'`./ >,( |
> \_.-|_/,-/ ii | |
> `."' `-/ .-"""|| |
> /`^"-; | ||____|
> / / `.__/ | ||
> / | ||
> | ||
>
>

***** **************************************************
"Contrary to popular belief, Unix is user friendly. It's
just very particular about who it makes friends with."

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 11:47:33 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA22444;
Wed, 29 Dec 1999 11:47:31 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA28505;
Wed, 29 Dec 1999 11:47:31 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA25111;
Wed, 29 Dec 1999 11:46:24 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA56038
for <[email protected]>; Wed, 29 Dec 1999 11:41:23 -0800
Received: from fd0man.pentanet.net (IDENT:[email protected] [205.133.169.69])
by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA30973
for <[email protected]>; Wed, 29 Dec 1999 11:41:21 -0800
Received: from localhost (fd0man@localhost)
by fd0man.pentanet.net (8.9.3/8.9.3) with ESMTP id PAA10507;
Wed, 29 Dec 1999 15:46:10 -0500
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 15:46:09 -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: "Michael B. Trausch" <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: return receipt feature
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: [email protected]
X-To: Leslie Fairall <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Authentication-Warning: fd0man.pentanet.net: fd0man owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 29 Dec 1999, Leslie Fairall wrote:
>
> The main reason why I would like to use return-receipts is for
> school-related also. I am a graduate student that emails a lot of my
> assignments. Last semester I kept asking one of my professors if he had
> received my assignment. He kept saying he had to check his email first. I
> figure that if I can get a return receipt when my professors read the
> message, I will have a confirmation that he/she received my email and can
> keep it in a folder for my records until the end of the semester. I think
> that's a legitimate use for return receipts.
>

Yep. Return reciepts are one of those things that is a great little
thing, when used right. But I knew a guy that had me on his mailing list
w/ a RR request on EVERY email he sent out, and I didn't appreciate it, so
I told him to bugger off so that I didn't have to put up with it; I
personally consider it a violation of privacy unless it's important.

- Mike

--
,-._.-._.-._.-._.-.
`-. ,-'
.----------------------. | | Michael B. Trausch
| Dilbert's Comment | | | [email protected]
| Corner | | | AIM: CSMFSOBW
|------------------------| | | ----------------------
| Pschitt - A real life | ,';".________.-. Need your computer
| German drink that | ;';_' )] upgraded or repaired?
| doesn't sound too | ; `-| E-mail me!
| appetizing. `. `T- | ----------------------
`----------------------._ \ | |
`-; | |
|..________..-|
/\/ |________..|
,'`./ >,( |
\_.-|_/,-/ ii | |
`."' `-/ .-"""|| |
/`^"-; | ||____|
/ / `.__/ | ||
/ | ||
| ||

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 11:52:16 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA22913;
Wed, 29 Dec 1999 11:52:15 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA28619;
Wed, 29 Dec 1999 11:52:14 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA23439;
Wed, 29 Dec 1999 11:51:03 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA34222
for <[email protected]>; Wed, 29 Dec 1999 11:48:43 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA28243
for <[email protected]>; Wed, 29 Dec 1999 11:48:43 -0800
Received: from jason02.u.washington.edu ([email protected] [140.142.76.8])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA28528
for <[email protected]>; Wed, 29 Dec 1999 11:48:43 -0800
Received: from dante40.u.washington.edu ([email protected] [140.142.15.200])
by jason02.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA15902;
Wed, 29 Dec 1999 11:48:42 -0800
Received: from localhost (leibrand@localhost)
by dante40.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA60892;
Wed, 29 Dec 1999 11:48:41 -0800
Message-Id: <Pine.A41.4.21.9912291147120.89738-100000@dante40.u.washington.edu>
Date: Wed, 29 Dec 1999 11:48:36 -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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: two questions about Pine and IMAP servers
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jordi Castro <[email protected]>
X-Cc: Pine Info Mailing List <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Here are some clues:

http://www.google.com/search?q=message+to+save+shrank&num=10

But I don't know the answer.

Anyone else know what to do about the "message to save shrank" error in
Pine 4?

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Wed, 29 Dec 1999, Jordi Castro wrote:

> Hello
>
> Thank you very much for your answer to my first question.
>
> Do you have some idea for my second question? Do you believe is
> a problem of my University IMAP server?
>
> > 2) I have problems when saving a message from INBOX (located
> > in the IMAP server) to a local folder. Pine prompts a message stating
> > that "the message have shrank (original number of bytes --> final number
> > of bytes)", and does not save the message. However the export function
> > works correctly, and the message can be saved to a local file.
> > I experienced the same problem with pine 4.05 running on a Suse 6.0 Linux
> > box, and with pine 4.21 installed on a Sun Solaris server. Can anyone
> > tell me what I am doing wrong and what should I do?
>
> Thanks in advance.
>
>
> =========================================================================
> Jordi Castro
> Statistics and Operations Research Dept. Phone: +34-93-4015867
> Universitat Politecnica de Catalunya Fax: +34-93-4015855
> Campus Sud, Pau Gargallo 5 E-mail: [email protected]
> 08028 Barcelona (Spain) http://www-eio.upc.es/~jcastro
> ==========================================================================
>
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 12:00: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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21957;
Wed, 29 Dec 1999 12:00:07 -0800 (PST)
Received: from lists2.u.washington.edu ([email protected] [140.142.56.1])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA31841;
Wed, 29 Dec 1999 12:00:06 -0800
Received: from host ([email protected] [140.142.56.13])
by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA16910;
Wed, 29 Dec 1999 11:59:01 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA70668
for <[email protected]>; Wed, 29 Dec 1999 11:57:01 -0800
Received: from euler.math.washington.edu ([email protected] [128.95.224.1])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA20066
for <[email protected]>; Wed, 29 Dec 1999 11:57:01 -0800
Received: from goedel3.math.washington.edu ([email protected] [128.95.224.12])
by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id LAA21156;
Wed, 29 Dec 1999 11:57:00 -0800 (PST)
Message-Id: <Pine.OSF.4.21.9912291150470.18089-100000@goedel3.math.washington.edu>
Date: Wed, 29 Dec 1999 11:57: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: "Eduardo Chappa L." <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: New key please
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine developers team <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Dear Pine Team

I have started since a few days reading mailing lists and newsgroup
ordered in Ordered Subject (all others by arrival). I find it quite
useful. I have one problem though. If I want to pass to the next NEW mail,
I have to press the TAB key, because the "down arrow" key only takes me to
the next message in the order. Tab works great, but I would like also to
reverse the direction of the TAB key and go to the previous NEW
message. It is a little bit complicated to go back to the previous new
message, to say the least, unless I am missing something. If I am not,
could you please add a key binding to go to the "previous new message"?

Thanks

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

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 13:18:18 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA14394;
Wed, 29 Dec 1999 13:18:16 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA30717;
Wed, 29 Dec 1999 13:18:16 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA26286;
Wed, 29 Dec 1999 13:17:19 -0800
Received: from jason05.u.washington.edu ([email protected] [140.142.78.6])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA18382
for <[email protected]>; Wed, 29 Dec 1999 13:15:39 -0800
Received: from dante33.u.washington.edu ([email protected] [140.142.15.215])
by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA23402;
Wed, 29 Dec 1999 13:15:38 -0800
Received: from localhost (leibrand@localhost)
by dante33.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA57282;
Wed, 29 Dec 1999 13:15:37 -0800
Message-Id: <Pine.A41.4.21.9912291314370.13888-100000@dante33.u.washington.edu>
Date: Wed, 29 Dec 1999 13:15: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: Scott Leibrand <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: New key please
In-Reply-To: <Pine.OSF.4.21.9912291150470.18089-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Eduardo Chappa L." <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I think Shift-TAB would be ideal for this, if It can be used. Using
shift-tab will be totally intuitive to people used to using tab to advance
and shift-tab to go back in forms.

--
Scott Leibrand
[email protected]
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *

On Wed, 29 Dec 1999, Eduardo Chappa L. wrote:

> Dear Pine Team
>
> I have started since a few days reading mailing lists and newsgroup
> ordered in Ordered Subject (all others by arrival). I find it quite
> useful. I have one problem though. If I want to pass to the next NEW mail,
> I have to press the TAB key, because the "down arrow" key only takes me to
> the next message in the order. Tab works great, but I would like also to
> reverse the direction of the TAB key and go to the previous NEW
> message. It is a little bit complicated to go back to the previous new
> message, to say the least, unless I am missing something. If I am not,
> could you please add a key binding to go to the "previous new message"?
>
> Thanks
>
> Eduardo
> http://www.math.washington.edu/~chappa/pine/
>
>

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 13:35:06 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA24908;
Wed, 29 Dec 1999 13:35:04 -0800 (PST)
Received: from lists4.u.washington.edu ([email protected] [140.142.56.2])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA31124;
Wed, 29 Dec 1999 13:35:04 -0800
Received: from host ([email protected] [140.142.56.13])
by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA26718;
Wed, 29 Dec 1999 13:33:42 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA12312
for <[email protected]>; Wed, 29 Dec 1999 13:30:51 -0800
Received: from sttlpop3.sttl.uswest.net (sttlpop3.sttl.uswest.net [206.81.192.3])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA32179
for <[email protected]>; Wed, 29 Dec 1999 13:30:50 -0800
Received: (qmail 12919 invoked by alias); 29 Dec 1999 21:30:50 -0000
Received: (qmail 12900 invoked by uid 0); 29 Dec 1999 21:30:50 -0000
Received: from pdsl174.sttl.uswest.net (209.181.139.174)
by sttlpop3.sttl.uswest.net with SMTP; 29 Dec 1999 21:30:50 -0000
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 13:29:06 -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: Terry Gray <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: two questions about Pine and IMAP servers
In-Reply-To: <Pine.A41.4.21.9912291147120.89738-100000@dante40.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <[email protected]>
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> Anyone else know what to do about the "message to save shrank" error in
> Pine 4?

This error usually indicates a problem with the IMAP server.
Early versions of Exchange with IMAP support were known offenders.

-teg

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Wed, 29 Dec 1999 16:39:48 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28496;
Wed, 29 Dec 1999 16:39:46 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA03541;
Wed, 29 Dec 1999 16:39:46 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA03707;
Wed, 29 Dec 1999 16:37:49 -0800
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA76908
for <[email protected]>; Wed, 29 Dec 1999 16:35:41 -0800
Received: from vax.area.com (vax.area.com [216.218.218.27])
by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA04357
for <[email protected]>; Wed, 29 Dec 1999 16:35:41 -0800
Received: (qmail 7406 invoked by uid 1828); 30 Dec 1999 00:35:33 -0000
Message-Id: <[email protected]>
Date: Wed, 29 Dec 1999 16:35:33 -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: [email protected]
To: Pine Discussion Forum <[email protected]>
Subject: Re: New key please
In-Reply-To: <Pine.A41.4.21.9912291314370.13888-100000@dante33.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Scott Leibrand <[email protected]>
X-Cc: Pine Discussion Forum <[email protected]>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 29 Dec 1999, Scott Leibrand wrote:
>I think Shift-TAB would be ideal for this, if It can be used. Using
>shift-tab will be totally intuitive to people used to using tab to advance
>and shift-tab to go back in forms.

This would not work on the UNIX version of pine, because modifiers are
not sent with regular terminal emulations.

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Thu, 30 Dec 1999 12:04:42 -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.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA07459;
Thu, 30 Dec 1999 12:04:41 -0800 (PST)
Received: from lists5.u.washington.edu ([email protected] [140.142.56.6])
by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA26978;
Thu, 30 Dec 1999 12:04:40 -0800
Received: from host ([email protected] [140.142.56.13])
by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA21872;
Thu, 30 Dec 1999 12:03:29 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA25728
for <[email protected]>; Thu, 30 Dec 1999 12:00:43 -0800
Received: from mtiwmhc09.worldnet.att.net (mtiwmhc09.worldnet.att.net [204.127.131.18])
by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA13352
for <[email protected]>; Thu, 30 Dec 1999 12:00:43 -0800
Received: from 118.reno-03-04rs16rt.nv.dial-access.att.net
([12.72.145.118]) by mtiwmhc09.worldnet.att.net
(InterMail v03.02.07.07 118-134) with ESMTP
id <19991230200042.XYUF10418@118.reno-03-04rs16rt.nv.dial-access.att.net>
for <[email protected]>; Thu, 30 Dec 1999 20:00:42 +0000
Message-Id: <[email protected]>
Date: Thu, 30 Dec 1999 12:01:50 -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: James <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Re: two questions about Pine and IMAP servers
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 29 Dec 1999, Terry Gray wrote:

> > Anyone else know what to do about the "message to save shrank" error in
> > Pine 4?
>
> This error usually indicates a problem with the IMAP server.
> Early versions of Exchange with IMAP support were known offenders.

I don't know what to do about it, but I see it quite a bit. My ISP uses
POP for incoming mail, and it seems to happen when a new message arrives
while PINE is getting the mail that's already in the inbox.

James

From [email protected] Sun ??? 0 00:00:00 1970 +0000
Return-Path: <[email protected]>
Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+pine-info; Fri, 31 Dec 1999 09:54:03 -0800 (PST)
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26291;
Fri, 31 Dec 1999 09:54:02 -0800 (PST)
Received: from lists3.u.washington.edu ([email protected] [140.142.56.3])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA13568;
Fri, 31 Dec 1999 09:54:01 -0800
Received: from host ([email protected] [140.142.56.13])
by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA12904;
Fri, 31 Dec 1999 09:52:28 -0800
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA22336
for <[email protected]>; Fri, 31 Dec 1999 09:50:10 -0800
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1])
by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA18520
for <[email protected]>; Fri, 31 Dec 1999 09:50:09 -0800
Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12])
by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA13513
for <[email protected]>; Fri, 31 Dec 1999 09:50:08 -0800
Received: from [128.130.111.10] (nunki [128.130.111.10])
by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id SAA11233
for <[email protected]>; Fri, 31 Dec 1999 18:50:07 +0100 (MET)
Message-Id: <[email protected]>
Date: Fri, 31 Dec 1999 18:50:05 +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: Gerald Pfeifer <[email protected]>
To: Pine Discussion Forum <[email protected]>
Subject: Support for RFC2015 (PGP MIME)?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: [email protected]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Are there any plans to support

RFC 2015 MIME Security with Pretty Good Privacy (PGP). M. Elkins.
October 1996. (Format: TXT=14223 bytes)
(Status: PROPOSED STANDARD)

in the near future? Or has anyone already a patch to support that?

The problem is that messages encoded like that cannot be caught and
processed by Pine's display filters, so Pine users are getting "cut
off" as far as PGP is concerned.

Gerald
--
Gerald "Jerry" [email protected] http://www.dbai.tuwien.ac.at/~pfeifer/

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